severity 338007 wishlist
retitle 338007 fetchmail: handle IMAP servers that send crap after header better
thanks
On Wed, 09 Nov 2005, Nathaniel W. Turner wrote:
> On Monday 07 November 2005 08:27 pm, Matthias Andree wrote:
> > Does the problem also affect 6.2.9-rc7?
>
> Yes, I see the same problem with 6.2.9-rc7. The results of running fetchmail
> 6.2.9-rc7 against the same test messages are attached to this message.
This is not a fetchmail bug. Using your first test message, I see this
with Courier-IMAP, prefixing each line by "| " in my output so it's more
easily legible. As you can see, Courier-IMAP sends the whole message
rather than just the header.
fetchmail does not need to handle such broken server behavior.
(fetchmail tries to swallow the crap, but stops doing so at the line
containing OK, taking it for the server reply.)
I'm demoting this to "wishlist" because fetchmail could indeed skip
forward to this sequence (ABNF): ")" CR LF tag OK rather than looking
for just OK.
| . fetch 1 rfc822.header
| * 1 FETCH (RFC822.HEADER {429}
| Message-Id: <[EMAIL PROTECTED]>
| Date: Thu, 03 Nov 2005 07:06:30 -0600
| To: <[EMAIL PROTECTED]>
| From: <[EMAIL PROTECTED]>
| Subject: testcase 1 (fails)
| Mime-Version: 1.0
| Content-Type: text/plain
|
| This is the message body. The preceding blank line ends with \r\n, as do
| all the other lines in this message.
| This line contains the word OK somewhere in it.
|
| This message will cause fetchmail to choke.
| )
| . OK FETCH completed.
Now compare this against Dovecot output:
| . fetch 1 rfc822.header
| * 1 FETCH (RFC822.HEADER {208}
| Message-Id: <[EMAIL PROTECTED]>
| Date: Thu, 03 Nov 2005 07:06:30 -0600
| To: <[EMAIL PROTECTED]>
| From: <[EMAIL PROTECTED]>
| Subject: testcase 1 (fails)
| Mime-Version: 1.0
| Content-Type: text/plain
|
| )
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
