2 May
2013
2 May
'13
7:02 p.m.
Quoting Timo Sirainen tss@iki.fi:
On 30.4.2013, at 0.12, Timo Sirainen tss@iki.fi 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 MUST return a NO. This can be used to cancel the append.
But that doesn't prohibit zero-length CATENATE parameters.
Also another way to generate empty message is to give URL to an
empty MIME part. Should such APPENDs also fail? I think if there's
no good reason to disallow empty messages I'll just keep the code as
it is and allow them.
Some clients treat IMAP as a pseudo-filesystem (e.g. Kolab), so I
would agree that limiting what can be stored is a bad idea.
michael