On Montag, 25. Januar 2016 12:36:07 CEST, Jan Kundrát wrote:
On Monday, 25 January 2016 04:47:41 CET, SagaXu wrote:
* 1 FETCH (UID 1325373061 INTERNALDATE "22-Dec-2015 15:57:52
+0800" ENVELOPE ("22-Dec-2015 15:57:50 +0800"
"=?UTF-8?B?UmU6IFFBIENsYXJpZmljYXRpb25z?="
(("=?UTF-8?B?U2FnYVh1?=" NIL "saga.xu" "avantport.com")) NIL
NIL
(("=?UTF-8?B?UWl0b25nIFh1?=" NIL "QXu" "roamdata.com")) NIL
NIL ((NIL NIL "ECD46103-4C38-4183-8D0F-FB47AD528DD9"
"roamdata.com")) "") BODYSTRUCTURE ("text" "plain" ("charset"
"US-ASCII") NIL NIL "7bit" 1548 40 NIL NIL NIL)
RFC822.SIZE 3216 BODY[HEADER.FIELDS (REFERENCES LIST-POST)]
{139} References: )
Hi, thanks for your bugreport. This IMAP server is broken on several fronts:
1) It's trying to send the "env-in-reply-to" field using a
similar syntax as the from/cc/... fields, which is a bug. It
MUST be sent as a string.
2) The format of the date doesn't follow RFC5322, but is
instead using something similar to IMAP's INTERNALDATE. That's
also a bug.
3(?) - is an empty message ID (looks like?) legal at all? (or is this maybe
just broken with the in-reply-to mess?)
Also, (risking to go off topic) rfc3501 seems to state that "sender" and "reply-to"
cannot be NIL, but must equal "from" in doubt?
Cheers,
Thomas
PS, "FUBAR", not "SNAFU" ;-)
