On Fri, 6 Oct 2000, Michael T. Babcock wrote:
It's probably a corrupted MIME message messing things up. Take a look at
the actual message on the server, and delete it, if necessary.
The log entry:
Oct 6 21:38:23 web imaplogin: Connection, ip=[::ffff:216.168.105.34]
Oct 6 21:38:23 web imaplogin: LOGIN, user=mbab...@fibrespeed.net,
ip=[::ffff:216.168.105.34]
Oct 6 21:38:24 web imaplogin: IMAP FETCH ERROR: unexpected EOF, uid=514,
filename=970174860.15364.web.fibrespeed.net:2,: BODY.PEEK[HEADER.FIELDS
("References" "X-Ref" "X-Priority" "X-MSMail-Priority" "X-MSOESRec"
"Newsgroups")]
The file:
cat Maildir/cur/970174860.15364.web.fibrespeed.net:2,
Return-Path: <ro...@fibrespeed.net>
Delivered-To: fibr...@fibrespeed.net
Received: (qmail 15362 invoked by uid 0); 28 Sep 2000 21:01:00 -0000
Date: 28 Sep 2000 21:01:00 -0000
Message-ID: <2000...@mstore.fibrespeed.net>
From: ro...@fibrespeed.net
Cc: recipient list not shown: ;
The problem seems fairly obvious now. Courier-IMAP expects to find headers
that don't necessarily exist. If I delete the messages that have no body,
etc., the log moves on to the next 'broken' message. These messages were
retrieved fine by Courier 0.36. Although a header might be considered
necessary, if it doesn't find it, the message should be ignored, the server
shouldn't just quit downloading messages on me ...
If I had a Subject: line as well as a "testing 1-2-3" after that, it no
longer reports the message as broken.
The fact that there were several dozen of these messages in my Inbox made
this interesting work ...
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier-IMAP mess...
