[imp] imp Digest, Vol 3374, Issue 1
R Phillips
R.I.Phillips at bath.ac.uk
Wed Jun 19 12:20:54 UTC 2013
> Message: 2
> Date: Tue, 18 Jun 2013 11:43:19 -0600
> From: Michael M Slusarz <slusarz at horde.org>
> To: imp at lists.horde.org
> Subject: Re: [imp] Invalid Address in From:
> Message-ID:
> <20130618114319.Horde.6aqzuN3YlpBh88SHl4tqEQ4 at bigworm.curecanti.org>
> Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
>
> Quoting R Phillips <R.I.Phillips at bath.ac.uk>:
>
>> Having installed Groupware 5.1 I am seeing "Invalid Address" in all
>> folder presentations (and in view modes) for any From: address that is
>> proceeded by any content.
>>
>> The "Invalid Address" are either:
>>
>> "A.N.Other" <a.n.other at example.com>
>> or:
>>
>> another <a.n.other at example.com>
>>
>> From: addresses like:
>> imp at lists.horde.org
>>
>> ...display as expected. Also opening up a view window renders the From:
>> address "correctly" for all formats.
>>
>> I'm using imap c-client 2007f with httpd 2.4.4, PHP 5.4.14 with
>> squirrelmail-imap_proxy-1.2.7
>
> Almost certainly it is your IMAP server that is broken - it is not
> correctly parsing those addresses and is returning garbage/invalid
> values in an IMAP ENVELOPE FETCH response. You would need to provide
> an IMAP log of the FETCH to verify.
>
> michael
>
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
Apologies for not correctly threading this message, I'm replying to the
digest.
I'm curious to the discrepancy in handling as our existing production
IMP deployment doesn't display this behaviour - nor do any other mail
clients connected to it.
I'm not an IMAP expert myself, is this an example of what you were after?
S: * 35 FETCH (FLAGS (\Seen) UID 219080 RFC822.SIZE 57341 ENVELOPE ("7
Jun 2013 07:00:23 -0400" "Fedora Beta Release - Blog Posts on Open Cloud
- Red Hat Summer Training Promotion" (("Red Hat" NIL "email"
"engage.redhat.com")) (("Red Hat" NIL "email" "engage.redhat.com"))
(("Red Hat" NIL "feedback-emea" "redhat.com")) ((NIL NIL "ccsrip"
"bath.ac.uk")) NIL NIL NIL "<c5e29b1a15f04b6481589b90b5ccd713 at 1795>")
BODY[HEADER.FIELDS (IMPORTANCE LIST-POST X-PRIORITY CONTENT-TYPE)] {107}
S: Content-Type: multipart/alternative;
boundary=--boundary_1263727_22e0c9fe-330e-43d4-bdd3-57f889e4d31b
Here is an example of an address that renders as I would expect:
S: * 47 FETCH (FLAGS (\Seen) UID 219339 RFC822.SIZE 18563 ENVELOPE
("Wed, 12 Jun 2013 11:10:36 +0000" "imp Digest, Vol 3368, Issue 1" ((NIL
NIL "imp-request" "lists.horde.org")) ((NIL NIL "imp-bounces"
"lists.horde.org")) ((NIL NIL "imp" "lists.horde.org")) ((NIL NIL "imp"
"lists.horde.org")) NIL NIL NIL
"<mailman.3526.1371035436.12665.imp at lists.horde.org>")
BODY[HEADER.FIELDS (IMPORTANCE LIST-POST X-PRIORITY CONTENT-TYPE)] {89}
S: Content-Type: text/plain; charset="us-ascii"
List-Post: <mailto:imp at lists.horde.org>
With apologies for the text wrapping. This is from the debug_raw
output. I can possibly get telemetry from the IMAP server itself.
What format should I expect?
More information about the imp
mailing list