If the body of the message contains a NUL character, the the CTE MUST be
"binary" NOT "8bit".
Cyrus WILL transcode a properly formatted MIME message on ingest, if
necessary.
On 07/24/2017 12:14 PM, Mikhail T. wrote:
On 24.07.2017 10:41, Merlin Hartley wrote:
NUL characters are not
> This is one of those weird inconsistencies between IMAP and SMTP protocols …
> as far as I remember, the NUL character restriction only applies to the IMAP
> protocol … so your MTA (e.g. sendmail) is not breaking the SMTP RFC by
> transferring them.
True, but it's breaking the Internet Message
On 24.07.2017 12:34, Merlin Hartley wrote:
In my Exim configuration I have some code which strips the NUL
characters from externally received messages and prohibits my local
users from submitting messages which contain them - you could probably
come-up with a similar thing for sendmail.
This
Hi Mikhail
This is one of those weird inconsistencies between IMAP and SMTP protocols … as
far as I remember, the NUL character restriction only applies to the IMAP
protocol … so your MTA (e.g. sendmail) is not breaking the SMTP RFC by
transferring them.
In my Exim configuration I have some
On 24.07.2017 10:41, Merlin Hartley wrote:
NUL characters are not permitted in e-mails …
https://helpdesk.pscs.co.uk/690163-Data-stream-contained-NUL-character
As the RFC for IMAP states:
https://tools.ietf.org/html/rfc3501#section-9
(3) The ASCII NUL character, %x00, MUST NOT be used at any
I received an e-mail consisting of a PNG-file -- not an
attachment, the body of the e-mail had content-type image/png. That
message ended up in my /var/mail/mi mailbox -- because deliver would
not accept it:
421 4.3.0 deliver: Trying to unput wrong character
Trying to upload the same
-- because deliver would not
accept it:
421 4.3.0 deliver: Trying to unput wrong character
Trying to upload the same message using mbox2imap, I get:
mbox2imap: (alert) IMAP protocol error
mbox2imap: (alert) Protocol response: NO
mbox2imap: (alert) Diagnostic message: ['Message contains NUL
