From: Johann 'M. O. <myr...@ai...> - 2012-01-30 17:00:11
|
Hi all, I have a few emails with broken headers in my yahoo mailbox and fetchmail refuses to retrieve/forward them. I have repeated examples of fetchmail: reading message myr...@po...:3695 of 21103 (3139 octets) (log message incomplete) fetchmail: incorrect header line found while scanning headers fetchmail: not flushed In my log file. And yes, you're right. I do have 21k emails, and I'm not deleting them from my mailbox. Interestingly enough, that particular mail is now being skipped by fetchmail, though it does have a broken header: X-YahooFilteredBulk: 206.40.205.124 smedley.info> X-Originating-IP: [206.40.205.124] Checking the UIDL in a manual POP3 session: UIDL 3639 +OK 3639 AMZEv9EAAUj4R3RxaQBpvXThslA And test to see if it's been retrieved. % grep AMZEv9EAAUj4R3RxaQBpvXThslA .fetchids myr...@po... AMZEv9EAAUj4R3RxaQBpvXThslA Yet I can not find it anywhere when I grep for the message id: find . -exec grep 47797E8A.3040107 '{}' + So, apparently there are two issues I'm running into. One is that I have broken headers and somehow would like Fetchmail to handle that. Going manually through the log file and picking them out is not really what I want to do. Once, maybe, but there are several such mails (I suspect a broken port of Thunderbird to the OS/2 operating system) and it can happen again. Two, for some reason fetchmail has marked a broken message as downloaded even though it can't be found locally. I'm using maildrop as an mda and I somehow doupt that is the fault - maildrop has been very good at complaining when I managed to misconfigure it. Of course I did not put that particular mail through it just to see what it does -- yet. Going back to the former issue. Is there a way to get fetchmail do somehow fix/download broken mail? Perhaps take broken header lines and prefix them with X-Fetchmail-Broken-Header: ? Here is the last such message from my log file. Apparently I haven't gotten a broken mail for some time now: fetchmail: reading message myr...@po...:13512 of 21115 (306940 octets) (log message incomplete) fetchmail: incorrect header line found while scanning headers fetchmail: not flushed And here are both messages from manual POP3 sesssions: http://www.myrkraverk.com/~johann/3649.invalid.header http://www.myrkraverk.com/~johann/13512.invalid.header Johann |