Follow Up: Can't open key file /var/spool/amavis/maia.key

Greetings all,

I received a few emails in the last two days asking if I
found a
solution.  Yes, I did, and per request I'm posting the
findings here.

It appears something in a recent SuSE YaST update changed
the access
rights needed to reach /var/spool/amavis/maia.key  I needed
to reset the
ownership of the file to vscan:vscan, and issue 755 rights
to the file.


My clue was in moving the existing maia.key file to /tmp and
pointing
Maia to it.  This worked instantly.  My guess is that the
'others' read
write was not present for apache to access it.  

The other people who have emailed me directly all had the
update
'apache-mod-php4' applied to their system when the problem
began.  I've
not looked into the file to determine if something in this
update is
responsible.

One of the users who wrote me applied this change to their
system and it
fixed their problem.  Hope this helps others out there.

Thank you 


-----Original Message-----
From: Michael Weremecki 
Sent: Wednesday, November 15, 2006 2:53 PM
To: 'maia-usersrenaissoft.com'
Subject: Can't open key file /var/spool/amavis/maia.key

Greetings,

Today my users report the following error when they click on
a mail
message inside the Maia interface:

Can't open key file /var/spool/amavis/maia.key

I have verified that the maia.key file is there, and the
date and
permissions have not changed.  I also restored a backup copy
of my
maia.key file.

Nothing has changed on my system (configurations that is). 
It is
possible that a system update has taken place (SuSE
automatic updates).

Can anyone point to a reason?  

Thanks,

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Weremecki wrote:

> It appears something in a recent SuSE YaST update
changed the access
> rights needed to reach /var/spool/amavis/maia.key  I
needed to reset the
> ownership of the file to vscan:vscan, and issue 755
rights to the file.

The important thing to remember is that the key file needs
to be
readable by two different users--your amavisd/maia user (who
runs
amavisd-maia and the associated Perl scripts) and your web
server user
(who runs the PHP scripts).  If you host everything on a
single machine,
then you need to set up the permissions in such a way that
both of these
users can read the key file.

- --
Robert LeBlanc <rjlrenaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamail
guard.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFbIOSGmqOER2NHewRAnFhAJ0SaULV1hYZbdCqyo5Jv84Wa69glACe
OlXe
1uAkY+rS8CH5hULTjOLRGlw=
=xna7
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users