From: Sunil S. <sh...@bo...> - 2005-12-24 06:29:14
|
Quoting from Frederik's mail on Fri, Dec 23, 2005: > Since tonight, I'm suffering from "message [...] was not the expected > length" errors. I see it on one mailbox on my ISP (the other mailbox is > unaffected though), and it makes fetchmail completely fail to retrieve > mails from the mailbox concerned. > > I tried my ISP's webmail, and could access my mailbox without any > problems. I deleted the whole contents of the mailbox, in the hope that it > was one particual mail causing the problem. Unfortunately, on the first > mail which arrived, the problem was there again. > > I have this problem with both fetchmail from sarge (6.2.5-12sarge3), and > with self compiled fetchmail 6.3.1. > > Here's part of the output of an /etc/init.d/fetchmail debug-run: > > fetchmail: 6.2.5 querying pop.pandora.be (protocol POP3) at Fri 23 Dec > 2005 07:24:18 PM CET: poll started ... > fetchmail: forwarding to localhost > fetchmail: SMTP> MAIL FROM:<coo...@ma...> SIZE=4693 > fetchmail: SMTP< 250 OK > fetchmail: SMTP> RCPT TO:<frederik@localhost> > fetchmail: SMTP< 250 Accepted > fetchmail: SMTP> DATA > fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself > #**********************************.****************fetchmail: message > use...@po...:1 was not the expected length (4803 actual != 4693 > expected) fetchmail: SMTP>. (EOM) > fetchmail: terminated with signal 2 Please try adding the "forcecr" option to your fetchmailrc. In case it doesn't work, please send the output of "fetchmail -V" and the details of your smtp server. Is the "message ... was not the expected length" error coming on every mail or on specific mails only? -- Sunil Shetye. |