On Sun, Jan 29, 2006 at 06:25:42PM -0600, Justin Willmert wrote:
I am hoping somebody can help me solve a problem I am having with
procmail and spamassassin (specifically spamd). When spamassassin has
marked a message as spam, it gets sorted to a Junk folder, but the
problem is that it is owned by root:mail when it should be owned by the
user. When this happens, dovecot will not serve the email to the user. I
sort other emails into folders with simple matching rules and those work
fine. Spamassassin is the only rule that is piped out to a program.
This is sort of a side comment but using spamd with .procmailrc is not
the best approach in my opinion. I beleve the .procmailrc below
provides a better way to do this. The INCLUDERC line runs the
spamassassin program. Spamd should be turned off if you do this.
PATH=$HOME/bin:/usr/bin:/global/bin:/usr/ucb:/bin:/usr/local/bin:
SHELL=/bin/sh
MAILDIR = $HOME/Mail # You'd better make sure it exists
LOGFILE = $MAILDIR/procmail.log
LOCKFILE= $HOME/.lockmail
Using spamassassin rather than spamc gets around the SELinux issues, but
I've read there are performance gains if you use spamd. I guess using
spamassassin will work for me (my server isn't anywhere near being maxed
out), but I think it'd be a good idea to resolve this issue for others
to use later. I'm going to leave this open for a while, and if nothing
comes of it, I'll post my results to both lists like I mentioned in
another message.
How are you running spamassassin? Are you using anything like amavis?
If you have only procmail involved in the issue and use it on a per user
basis then it's really easy to handle.
$HOME/mail/spamjunk
As an example the above disposition line feeds the email to the user's
mail/spamjunk mbox file. Some appropriate rule ahead of the disposition
will tell procmail what to send to that folder.
I start my per user .procmailrc file with:
DROPPRIVS=yes
LOGNAME=procmail
I include likes like:
:0:
* ^From: Postmaster@xxxxxxxxxxxxxxxxxx
/dev/null
Re: Spamassassin emails have wrong perms ... When spamassassin has marked a message as spam, it gets sorted to a Junk folder, but the problem is that it is owned by root:mail when it should be owned by the user. ...Spamd should be turned off if you do this. ... If you have only procmail involved in the issue and use it on a per user basis then it's really easy to handle. ... (Fedora)
Re: Spamassassin emails have wrong perms ... When spamassassin has marked a message as spam, it gets sorted to a Junk folder, but the problem is that it is owned by root:mail when it should be owned by the user. ... Now all I have left to find is why spamd wants to ... (Fedora)
Re: Spamassassin emails have wrong perms ...procmail and spamassassin. ... When spamassassin has marked a message as spam, it gets sorted to a Junk folder, but the problem is that it is owned by root:mail when it should be owned by the user. ...Spamd should be turned off if you do this. ... (Fedora)
Re: Bug?/questions about spamassassin ... > When I run the newest version of spamassassin from the init.d ... Without that spamd runs in the foreground ... Generally, since it's not 100% accurate, people filter alleged spam into ... a separate mailbox (using procmail) for later review. ... (Fedora)
Re: i hate procmail ... will tag all messages with foo or bah. ...Procmail really is better. ...folder with that supplied tag added (I file several lists to one folder, ...=head1 SYNOPSIS... (RedHat)