On 13-08-30 5:34 AM, Cedric Foll wrote:
I've found the email which produce this problem.
The destination adress in the header look like that:
To: "mb >> \"MB Mxxx.yyy\"" <[email protected]>
It may be the cause of the problem?
Probably, can you open a bug with a sample mail that triggers this behavior?
Make that bug private if you must attach the real mail.
Thanks.
Regards
Le 30 août 2013 à 10:04, Cedric Foll <[email protected]> a écrit :
Hi,
One of my users can't access to his mails when he open his INBOX, his others
imap folder work corectly
On solo.log I have this errors:
Aug 30 09:32:32 sogod [32375]: <0x0x7f44411840a0[NGImap4ResponseParser]>
WARNING: IMAP4 envelope address not properly closed (c0=M,c1=i): (null)
Aug 30 09:32:32 sogod [32375]: <0x0x7f444117d270[NGImap4Client]>
ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser
exception NGImap4ParserException: unsupported fetch key: nil
Aug 30 09:32:32 sogod [32375]: [ERROR] <0x0x7f4441169d20[NGImap4Connection]>
could not fetch 97 uids for url: imap://xxx.yyy@imap/INBOX/
Any idea?
Regards
--
Cedric Foll
Architecte infrastructures
Direction des Systèmes d'Information
Bureau A2-177
Université Charles de Gaulle - Lille 3
Domaine universitaire du Pont de bois
BP 60149
59653 Villeneuve d'Ascq
Tel : 03 20 41 64 35
Fax : 03 20 41 60 01
Portable : 06 37 24 06 55
--
[email protected]
https://inverse.ca/sogo/lists
