On Monday 20 October 2003 09:11 am, Praedor Atrebates wrote:
<snipped>
Okay, we don't see the Postfix error code but based upon the text of the
message, my guess is that Postfix is rejecting this message upon the delivery
attempt by Fetchmail, fetchmail is then sending a failure message to let you
know but the message is not being deleted so upon the next poll attempt, it
tries to deliver the message again.
The fetchmail log should be telling you what the error code is from Postfix
but if I had to guess, I would say it is a 501, fetchmail normally counts 55?
codes as spam rejects by default.
So, one way to deal with this is to add the 501 error message to your
fetchmail config file as a spam reject, in which case, it will delete the
message from the server. That is what I do for my accounts since I don't
want to receive improperly formatted or addressed messages anyway. Your
mileage may vary.
Under your poll line in .fetchmailrc, add the option
antispam 554,550,501
Line should show:
poll mail.whatever.com with proto whatever
user '[EMAIL PROTECTED]' there with password 'password' is 'localuser' here
antispam 554,550,501
Add that line and you should no longer see those errors or have misconfigured
spam piling up in your inbox. Only other way that I know of is to run
Fetchmail configured to flush the box which removes all messages that were
seen but no delivered. This is dangerous and could result in your losing
messages due to Postfix being down when fetchmail tries to pick up mail.
Another option is to periodically run fetchmail to pick up mail, then reload
fetchmail in flush mode to flush misconfigured messages, then rerun fetchmail
in normal mode. You could do this once a week but in the meantime would get
all those errors in your syslog. Last option is to simply bitbucket all
fetchmail-daemon notifications with procmail.
Again, all of this is just a guess on my part without having access to the
logs running at a sufficient detail level to record the actual error. The
changes I have suggested will only result in your dropping messages that are
not correctly configured or addressed or coming from valid hosts.
--
Bryan Phinney
Software Test Engineer
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
