Mike Yates <hctef(_at_)fonehelp(_dot_)co(_dot_)uk> writes:
Rob MacGregor wrote:-
Mike Yates wrote:
Well, then, there should be a configuration option to "accept mis-sized
mail", should there not?
Actually, it does - I've seen a number of messages that have been
received, where fetchmail complains about the POP/IMAP server getting
the size wrong. It's only a warning/information message.
In my case it isn't!
There's another reason than size mismatch for retaining the message on
the server.
Also notice the parsing of the "Received:" lines is requiring them to be
from a known mailserver or alias in every case, which is senseless, for
the reasons I gave before.
Yes. We should stop parsing Received in some future release.
Many ISPs pass incoming messages via a
special antivirus server between distribution and POP3 serving, so the "
for " will not be from any "alias" of the mailserver, quite correctly.
What makes you think they wouldn't load balance malware scanning?
In this case, there was a valid local address in the "To:" line, so why
was it parsing "Received:" anyway?
Because it MUST use the envelope address and nothing else, particularly
not random junk from headers. To and Cc are not routing relevant (if
they were, you'd see mail loops).
I now have put "checkalias" in .fetchmailrc and it still ignores valid "
for " addresses in bcc'ed messages for that reason.
Prove it.
fetchmail: line rejected, byworkwise.com is not an alias of the mailserver
[...]
fetchmail: incorrect header line found while scanning headers
That's the reason.
--
Matthias Andree