| View previous topic :: View next topic |
| Author |
Message |
fieryred2k
n00b
Joined: 23 Mar 2004
Posts: 13
|
 Posted: Tue Mar 23, 2004 4:48 am Post subject: An occasionally reoccuring fetchmail problem... |
 |
|
After following the guide beowulf posted here I finally got postfix + procmail + fetchmail + courier-imap going (SHEESH took me 3 days, it was somethign simple stupid too). However every once in a while I get messages like this....
| Code: |
fetchmail: No mail for [SNIP] at mail.[SNIP].com
329 messages for [SNIP] at mail.[SNIP].com (1165180 octets).
[SNIP: lots of successful retrievals]
reading message [SNIP]@mail.[SNIP].com:124 of 329 (1671 octets) fetchmail: incorrect header line found while scanning headers
fetchmail: message delimiter found while scanning headers
flushed
fetchmail: client/server protocol error while fetching from mail.s2z.com
fetchmail: Query status=4 (PROTOCOL)
fetchmail: No mail for [SNIP] at mail.[SNIP].com
|
This seems to me like fetchmail is choking on some malformed email headers, which isn't really a good thing, as you know not everyone especially spammers won't always create a perfectly formed email header... and normally this wouldn't bother me but it stopped retrieval of the other 200 some emails... when I started fetchmail again it continued but why didn't it just continue on in the first place?
Is there a way to make fetchmail a little more forgiving on email headers? or at least make it so it doesn't stop outright like that?
and one other little question... because of the above mentioned people not using standard email headers, the date recieved field in some emails print out to be a full date, while others are just a time... Is there a way to make it update that date recieved field to be the date that fetchmail decided to retrieve it rather than the date recieved from the email headers? |
|
| Back to top |
|
 |
fieryred2k
n00b
Joined: 23 Mar 2004
Posts: 13
|
| Posted: Tue Mar 23, 2004 5:36 pm Post subject: |
|
|
| *bump* |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Tue Mar 23, 2004 5:42 pm Post subject: |
|
|
Try using the no dns option.
That helped me with a similar problem! |
|
| Back to top |
|
|
|
Networking & Security
