Package: python2.5
Version: 2.5.2-4
Severity: normal
While fetching an email from an etch courier imapd (4.1.1.20060828-5)
It might well be a courier defect, too - I don't know. But I can read
the mail just fine with the Horde3 Webmail, which uses the PHP IMAP
extensions.
imap: 14:17.68 > DMGK22 UID FETCH 6196 (BODY.PEEK[])
imap: 14:17.76 < * 26 FETCH (UID 6196 BODY[] {176752}
imap: 14:17.76 matched r'\* (?P<data>\d+) (?P<type>[A-Z-]+)(
(?P<data2>.*))?' => ('26', 'FETCH', ' (UID 6196 BODY[] {176752}', '(UID 6196
BODY[] {176752}')
imap: 14:17.76 matched r'.*{(?P<size>\d+)}$' => ('176752',)
imap: 14:17.76 read literal size 176752
imap: 14:17.88 untagged_responses[FETCH] 0 += ["('26 (UID 6196 BODY[]
{176752}', 'Return-Path: <[EMAIL PROTECTED] Base64 mail body
contents...]4Omfh3pXh+1u7H4c+Iby5mBM1supxq')"]
imap: 14:17.97 < 1vg8fMY8
imap: 14:17.97 untagged_responses[FETCH] 1 += ["1vg8fMY8"]
imap: 14:17.97 <
NnrxX4V3Ou3V1pFjbPJbKmmK8UASFVkCyEs25gMvz/eyRnAqqs7y2qpI0pihB24xhWJ5x7cV
abort: command: UID => unexpected response:
'NnrxX4V3Ou3V1pFjbPJbKmmK8UASFVkCyEs25gMvz/eyRnAqqs7y2qpI0pihB24xhWJ5x7cV'
As you can see, the mail transfer is broken into multiple chunks.
Sometimes this happens (in the same email) slightly earlier, in the mail
headers. I tried python2.4 and it didn't work either.
As mentioned above, I can access that email with a PHP based Webmail. I
figure I know too little about the IMAP protocol to be able to tell
Here's another run:
imap: 34:24.42 > EEFF19 UID FETCH 6196 (BODY.PEEK[])
imap: 34:24.61 < * 26 FETCH (UID 6196 BODY[] {176752}
imap: 34:24.61 matched r'\* (?P<data>\d+) (?P<type>[A-Z-]+)(
(?P<data2>.*))?' => ('26', 'FETCH', ' (UID 6196 BODY[] {176752}', '(UID 6196
BODY[] {176752}')
imap: 34:24.61 matched r'.*{(?P<size>\d+)}$' => ('176752',)
imap: 34:24.61 read literal size 176752
imap: 34:24.62 untagged_responses[FETCH] 0 += ["('26 (UID 6196 BODY[]
{176752}', 'Return-Path: <[EMAIL PROTECTED] more headers ...]\r\nReceived: from
fluffy.cdtm.de (fluffy.cdtm.de [129.187.150.78])\r\n\tby legolas.drinsama.de
(Postfix) with ES')"]
imap: 34:24.62 < MTP id 83C2FC4C083
imap: 34:24.62 untagged_responses[FETCH] 1 += ["MTP id 83C2FC4C083"]
imap: 34:24.62 < for <[EMAIL PROTECTED]>; Tue, 6 May 2008 11:49:44
+0200 (CEST)
abort: command: UID => unexpected response: ' for <[EMAIL PROTECTED]>; Tue,
6 May 2008 11:49:44 +0200 (CEST)'
As you can see, it again looks like the body transfer was interrupted
somewhere, causing part of the transfer to be interpreted as a new reply.
I tried to get a network capture, but after disabling SSL or maybe because of
the web mail access, it now worked just fine again, the mail was correctly
transferred.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.25-rc6
Debian Release: lenny/sid
500 unstable www.debian-multimedia.org
500 unstable ftp.de.debian.org
1 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=========================================-+-====================
libbz2-1.0 | 1.0.5-0.1
libc6 (>= 2.7-1) | 2.7-10
libdb4.5 (>= 4.5.20-3) | 4.5.20-11
libncursesw5 (>= 5.6+20071006-3) | 5.6+20080419-2
libreadline5 (>= 5.2) | 5.2-3
libsqlite3-0 (>= 3.5.7) | 3.5.8-3
libssl0.9.8 (>= 0.9.8f-5) | 0.9.8g-8
mime-support | 3.40-1.1
python2.5-minimal (= 2.5.2-4) | 2.5.2-4
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
