Quoting Timo Sirainen t...@iki.fi:
On Wed, 2013-05-22 at 09:38 -0600, Michael M Slusarz wrote:
Quoting Michael M Slusarz slus...@curecanti.org:
Quoting Timo Sirainen t...@iki.fi:
Anyway .. the BINARY APPEND converts only the MIME parts that you
send with Content-Transfer-Encoding: binary.
Quoting Michael M Slusarz slus...@curecanti.org:
It is concerning because RFC 4466 indicates that literal8's are
allowed for both APPEND and MULTIAPPEND, which is essentially an
extended APPEND. But RFC 4469 defines CATENATE TEXT as literal only:
RFC 4466:
append-data = literal /
On Wed, 2013-05-22 at 09:38 -0600, Michael M Slusarz wrote:
Quoting Michael M Slusarz slus...@curecanti.org:
Quoting Timo Sirainen t...@iki.fi:
Anyway .. the BINARY APPEND converts only the MIME parts that you
send with Content-Transfer-Encoding: binary. Are you sending such
Quoting Michael M Slusarz slus...@curecanti.org:
Quoting Timo Sirainen t...@iki.fi:
Anyway .. the BINARY APPEND converts only the MIME parts that you
send with Content-Transfer-Encoding: binary. Are you sending such
header to Dovecot?
I can verify this isn't working as you described
Using 2.2.2, I see this:
C: 6 APPEND INBOX (\seen) 16-May-2013 22:05:14 -0600 CATENATE (URL
/INBOX;UIDVALIDITY=1255685337/;UID=48812/;SECTION=HEADER TEXT ~{40}
S: 6 NO [UNKNOWN-CTE] Binary input allowed only when the first part is binary.
Why is there this limitation? It seems to me that
On 21.5.2013, at 9.40, Michael M Slusarz slus...@curecanti.org wrote:
Using 2.2.2, I see this:
C: 6 APPEND INBOX (\seen) 16-May-2013 22:05:14 -0600 CATENATE (URL
/INBOX;UIDVALIDITY=1255685337/;UID=48812/;SECTION=HEADER TEXT ~{40}
S: 6 NO [UNKNOWN-CTE] Binary input allowed only when the
Quoting Timo Sirainen t...@iki.fi:
On 21.5.2013, at 9.40, Michael M Slusarz slus...@curecanti.org wrote:
Using 2.2.2, I see this:
C: 6 APPEND INBOX (\seen) 16-May-2013 22:05:14 -0600 CATENATE
(URL /INBOX;UIDVALIDITY=1255685337/;UID=48812/;SECTION=HEADER
TEXT ~{40}
S: 6 NO [UNKNOWN-CTE]
On 21.5.2013, at 21.24, Michael M Slusarz slus...@curecanti.org wrote:
Or are you saying that the error is fine if the text contains NULs, but
simply should be allowed as long as it doesn't?
This. As mentioned before, it seems the code is simply assuming that the
text part contains NULs
Quoting Timo Sirainen t...@iki.fi:
Anyway .. the BINARY APPEND converts only the MIME parts that you
send with Content-Transfer-Encoding: binary. Are you sending such
header to Dovecot?
I don't think so. I noticed the CATENATE error when I was stripping a
simple text/html part out of a
