...
*Note: I just found where I was getting duplicate scans when using Maildrop. The file /etc/maildroprc had the following call to user's $HOME/.mailfilter to check & run it's $HOME/.mailfilter. My xfilter spamc trigger is contained in $HOME/.mailfilter. It seems $HOME/.mailfilter is read automatically by maildrop. As such, commenting this code in /etc/maildroprc should fix this.
| No Format |
|---|
/etc/maildroprc |
...
#
# Include any rules set up for the user - this gives the
# administrator a way to override the domain's mailfilter file
#
# this is also the "suggested" way to set individual values
# for maildrop such as quota. (why do you need quota on your own PC?)
#
...
## WE'RE CALLING SPAMASSASSIN TWICE. Once here and once ~/.mailfilter.
## $HOME/.mailfilter is being automatically read by maildrop and this check isn't needed.
#
# Include any rules set up for the user - this gives the
# administrator a way to override the domain's mailfilter file
#
# this is also the "suggested" way to set individual values
# for maildrop such as quota. (why do you need quota on your own PC?)
#
#`test -r $HOME/.mailfilter`
#if( $RETURNCODE == 0 )
# {
# log "(==) Including $HOME/.mailfilter"
# exception {
# include $HOME/.mailfilter
# }
# }
|
...