MKlinke <mklinke(_at_)axsi(_dot_)com> wrote:
.. have been noticing entries in my maillog that indicate
"incorrect header line found while scanning headers." These messages
are left on the server in spite of the -fetchall option specification.
I find that I have to log directly into the mail server with Outlook
or some other MUA in order to retrieve the messages from the server.
Fetchmail retrieves typically about 1000 messages per day from the
same server and perhaps 50 of these show this error.
[...]
Is there something I can supply to the list that would help to determine
what it is about these messages that are triggering the maillog entry?
Regards, Mike Klinke
The problem is the absence of separation between body and header.. In the
first message, immediately after the X-MSMail-Priority header is another
'header' titled "Allan"... This is b0rking fetchmail. In the second message,
fetchmail is interpreting the 'sullivan' line as another (illegal) header.
The spammer is probably doing it on purpose.
As for a resolution with fetchmail, I have no idea, I'm afraid.
I came across the same problem, "incorrect header line found while
scanning headers" so I telnetted into the pop3 server and discovered a
number of emails with no headers whatsoever!
Heaven knows how they arrived in the mailbox in the first place.
------------------- 1st Message ------------------------
[...]
Message-Id:
<8agqfi7q$9$7127vex3e84l6wq(_dot_)liscanomed(_at_)mailcity(_dot_)com>
X-Sender: liscanomed(_at_)mailcity(_dot_)com (atalo peeters)
Importance: Normal
X-MSMail-Priority: Normal
Allan <---------
Viagra valium prozac.