Quoting Mike Abbott :
It's the inconsistency that bothers me. Plain old APPEND doesn't
allow empty messages but CATENATE does?
I don't recall/see anything in RFC 3501 that prevents a zero-length message:
append = "APPEND" SP mailbox [SP flag-list] [SP date-time] SP
It's the inconsistency that bothers me. Plain old APPEND doesn't allow empty
messages but CATENATE does?
Quoting Timo Sirainen :
On 30.4.2013, at 0.12, Timo Sirainen wrote:
This could be changed I guess, but I don't think it's a bug. I
don't see anything in RFC 3501 prohibiting saving empty messages.
Only the MULTIAPPEND RFC says:
A zero-length message literal argument is an error, and
On 30.4.2013, at 0.12, Timo Sirainen wrote:
> On 29.4.2013, at 21.40, Mike Abbott wrote:
>
>> Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE:
>> b1 append inbox catenate (text {0+}
>> )
>> b1 OK [APPENDUID 1366726248 12] Append completed.
>>
>> Contrast this with r
On 29.4.2013, at 21.40, Mike Abbott wrote:
> Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE:
> b1 append inbox catenate (text {0+}
> )
> b1 OK [APPENDUID 1366726248 12] Append completed.
>
> Contrast this with regular APPEND:
> b2 append inbox {0+}
> b2 NO Can't save
Something ate an important leading space from my message.
> b3 append inbox catenate (text {0+}
> text {8+}
> foobar
> )
> b3 OK [APPENDUID 1366726248 13] Append completed.
There was and should be a single space before the "text {8+}" above.
Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE:
b1 append inbox catenate (text {0+}
)
b1 OK [APPENDUID 1366726248 12] Append completed.
Contrast this with regular APPEND:
b2 append inbox {0+}
b2 NO Can't save a zero byte message.
Note that zero-size literals are OK bu
