Re[2]: [vps-mail] analysing maillog on new vps2

[tim <email@xxxxxxxxxxxxxxxx>]

I'd go with that...

But then the default installation of spamassassin and clamav create it
that way, as I have not yet touched the systemwide procmailrc

It indeed has
DROPPRIVS=yes
at the top and then the recipes for the scanners.

So to get around it,
create a universal log, call it by LOGFILE at the beginning, and then
do the DROPPRIVS=yes after? Delete the individual logfiles per recipe
created by those scripts?

But even then as the permissions change to the users, can procmail
continue writing to the logfile?

I will try this, but comments welcome.
Thanks for the assistance,
tim.

Wednesday, December 1, 2004, 1:23:40 PM, you wrote:

GS> On Wed, 1 Dec 2004 12:44:32 +0100, tim
GS> <email@xxxxxxxxxxxxxxxx> wrote:

>> first it seems procmail does not have right to write to /var/log
>> Dec  1 11:35:19 email procmail[80561]: Error while writing to "/var/log/procmail.clamav"
>> Dec  1 11:35:19 email procmail[80561]: Error while writing to "/var/log/procmail.log"
>> 
>> as procmail does not seem to be a user on the system (vps2) I was
>> wondering if it should be? I installed it as local delivery agent, for
>> spamassassin and clamav processing.

GS> At a guess I'd say that you're attempting to write to the logfile *after* a
GS> DROPPRIVS=yes in your procmailrc. This means that procmail is running as the
GS> local user for whom the mail is intended and it's *that* user who doesn't
GS> have write permissions on the log file.




-- 
Best regards,
 tim                            mailto:email@xxxxxxxxxxxxxxxx

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).