At 11:34 2006-08-30 +0200, Jürgen Ladstätter wrote:
[snip]
DROPPRIVS=YES
This is only applicable for /etc/procmailrc invoked recipes - if you're
already delivering at the USER level (~/.procmailrc), then there's no need
to do this. If a procmail script in your home dir were being INCLUDERC'd
into the /etc/procmailrc, then the DROPPRIVS should really be done in the
/etc/procmailrc anyway for security purposes, rather than relying upon a
user-created script to relenquish privledge.
Either way, where exactly does the procmailrc file you posted reside, and
what user is it running as?
LOGFILE=/data/logs/procmail
.. which begs the question, what are the perms on the logfile, since it's
not within a user dir. Does one user or many users write to this?
:0
* ^X-Spam-Virus: Yes
/data/mail/web0p3/.maildir/
This is a curious path - why not /var/ ?
procmail: Unable to treat as directory "/data/mail/web0p3/.maildir/new"
This would happen if S_ISDIR macro doesn't see the S_IFDIR bit set on the
file mode (which wouldn't seem to be the case if the file flags you list
below are correct) , or if attempting to make the directory failed.
procmail: Skipped "/data/mail/web0p3/.maildir"
From <mailto:jl(_at_)pics(_dot_)co(_dot_)at>jl(_at_)pics(_dot_)co(_dot_)at
Tue Aug 29 16:09:12 2006
Subject: WG: eeest
Folder:
/data/mail/web0p1/.maildir/new/1156860553.14408_0.TSwebserve 16253
ALERT!! Note the username portion of that path: web0p1. NOT
web0p3. You're dealing with different directories and different users. If
these are being delivered via the SAME procmailrc file, then you have a
problem because the files for web0p3 are OWNED by web0p3, not web0p1. As
such, this must be an /etc/procmailrc file, not a user ~/.procmailrc, and
the DROPPRIVS should NOT be done at the top if you're going to deliver to
files owned by users other than who you're actually delivering for.
BTW, it's good practice when reporting that things don't work to announce
what version of procmail you're using, as well as what OS you're on. The
output of 'procmail -v' is a good starting place, as it also indicates
which locking strategies which procmail is compiled with.
drwx------ 9 web0p3 poponly 264 29. Aug 16:21 .
drwxr-x--- 3 web0p3 poponly 72 16. Aug 16:47 ..
drwx------ 2 web0p3 poponly 48 29. Aug 15:55 courierimapkeywords
-rw-r--r-- 1 web0p3 poponly 15 29. Aug 15:55 courierimapuiddb
drwx------ 2 web0p3 poponly 48 16. Aug 16:47 cur
drwx------ 6 web0p3 poponly 224 30. Aug 08:05 .Drafts
drwx------ 2 web0p3 poponly 48 16. Aug 16:47 new
drwx------ 6 web0p3 poponly 224 30. Aug 08:05 .Sent
drwx------ 2 web0p3 poponly 48 30. Aug 08:05 tmp
drwx------ 6 web0p3 poponly 224 30. Aug 08:05 .Trash
FTR, directory listings are so much easier to read when people send them in
fixed-width font. This happens automagically if you just send PLAINTEXT
emails to discussion groups. This is the norm for this list, which is for
a *nix-based tool.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail