>> that it could not deliver to this local account in the first place? I
>> don't see anything in the logs that indicates any delivery problems right
>> before the account gets blacklisted.
>Then keep looking until you find it. It is there. May not have happened
>the minute before. It might've happened as long as two hours earlier.
You are of course correct. I looked harder, and found that timeouts in spam
filtering are causing courier to blacklist addresses. Apparently I
occasionally receive messages that spamd takes unusually long to process,
and the timeout causes my problem. Really egregious messages sit in the
queue, create a timeout every time delivery is attempted, and cause the
account to be blacklisted for a while.
Ok, so I just need to figure out how to prevent these timeouts from creating
problems.
Here are the guts of my maildroprc (some extraneous stuff removed):
import USER
exception
{
xfilter "/usr/bin/spamc -u $USER"
}
if (/^X-Spam-Status: Yes/:h)
{
`test -d "./Maildir/.Spam/"`
if ($RETURNCODE != 0)
{
`cp -Rp /home/courier/skel/Maildir/.Spam ./Maildir/`
}
to "./Maildir/.Spam/."
}
Any suggestions on how to fix?
Thanks!
Matt
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
