John Wilkins wrote:
Not so sure about that. I've only begun looking at fetchmail for some things I need, but it seems that the "preconnect" directive, used to invoke mailfilter/spamassassin (or similar) might do the trick here. But the essential idea is: have fetchmail pass each message through a filter before flinging it at Courier.On 1/1/1970, "Sam Varshavchik" <[EMAIL PROTECTED]> wrote:John Wilkins writes:Fetchmail receives the "550 Spam refused" and reports that courier refused delviery then sends an RSET. Courier responds to the RSET but - it appears - often not for 20-70 seconds. When the delay is >60 seconds, the upstream ISP pop3 connection has timed out (it seems to have a 60 second timeout).The first time a message is rejected, the response to the next command is delayed by 8 seconds. If subsequent messages continue to be rejected, the delay gets progressively increased. The delay gets reset only when a message is succesfully accepted. Therefore, when someone starts flinging spam at Courier, non-stop, the sender will be quickly tarpitted. Solution: don't start throwing spam at Courier.I guess I have two choices....
------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
