On Sunday 08 June 2003 09:30, Rob MacGregor wrote:
From: Robin Lynn Frank <rlfrank(_at_)paradigm-omega(_dot_)com>
550 is a permanent error which will never be accepted by our local server,
yet
fetchmail won't flush from the remote server. How do I force it to flush?
[And leave the seat down ;-) ]
RTFM?
Been there, done that:
"The fetchmail code recognizes and discards the message on any of a list
of responses that defaults to [571, 550, 501, 554] but can be set with
the `antispam' option."
Has the term discard been issued a new meaning I am unaware of? I'll concede
that line doesn't actually say what it does with the message on the remote
server, but it is a bit ambiguous.
Have you tried looking at the spam options to tell fetchmail what to do
when it receives 550?
I suspect that means antispam 550 will resolve this, but leaves me with a
question. Why wouldn't the default action on a permanent error (5xx) be to
flush the message? What part of permanent makes fetchmail think permanent
expires before it awakens the next time?
It would be useful if you were to tell people what version of fetchmail you
were using when asking for help.
6.2.2
--
Sed quis custodiet ipsos custodes?
==========================================================================
Robin Lynn Frank - Director of Operations - Paradigm-Omega, LLC
Copyright and PGP/GPG info in mail or message headers.
Email acceptance policy at http://paradigm-omega.com/email_policy.html
==========================================================================