[imp] imp Digest, Vol 3374, Issue 1
Michael M Slusarz
slusarz at horde.org
Wed Jun 19 23:08:39 UTC 2013
Quoting R Phillips <R.I.Phillips at bath.ac.uk>:
>> 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>
I can verify that both of these display fine on my system. And there
would be no reason why these would be parsed incorrectly.
> 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}
That all looks fine. And I can verify that this FETCH response (at
least the ENVELOPE part) causes this code
in imp/lib/Message.php (getFrom()):
$addrs = $ob->from;
// Debug line
print_r($addrs);
To be:
Horde_Mail_Rfc822_List Object
(
[_data:protected] => Array
(
[0] => Horde_Mail_Rfc822_Address Object
(
[comment] => Array
(
)
[mailbox] => email
[_host:protected] => engage.redhat.com
[_personal:protected] => Red Hat
)
)
[_filter:protected] => Array
(
)
[_ptr:protected] =>
)
And thus the later !count($addrs) will return false and Invalid
Address will not be printed. So I have no idea what is broken on your
system. You will have to debug on your system since there is no
indication anything is wrong in Horde/IMP code.
michael
___________________________________
Michael Slusarz [slusarz at horde.org]
More information about the imp
mailing list