From: James M. <ji...@so...> - 2004-07-21 19:14:20
|
Hello, fetchmail release 6.2.4+SSL+NLS I have fetchmail forward mail to a bayseian mail classifier, assp (anti-spam smtp proxy). One of assp's features is to block messages with executable attachments. If one is found, it rejects the message and returns an status code of 500 to the sender (fetchmail). Apparently assp closes the connection after returning the error message since signal 13 (broken pipe) is raised in fetchmail. At which time fetchmail terminates. It looks like this happens on the *next* connection attempt with assp. What is more worrisome is that just before the abort, fetchmail says the message was flushed, implying a lost message. Is there some way to have fetchmail re-connect with assp rather than abort? fetchmail: reading message moe...@lo...:2 of 2 (42695 octets) fetchmail: SMTP error: 500 Executable attachments are not allowed -- Compress before mailing. fetchmail: SMTP listener refused delivery fetchmail: flushed fetchmail: 1 message for cherie at localhost (5458 octets). fetchmail: reading message ch...@lo...:1 of 1 (5458 octets) fetchmail: flushed fetchmail: terminated with signal 13 -- jimoe at sohnen-moe dot com |