On Thu, Jan 16, 2020 at 10:56:08PM -0500, John C Klensin wrote:
> However, 5321 also makes it very clear that SMTP-conformant
> servers are not supposed to be tampering with message payloads
> (everything that follows the DATA command up to the "." CRLF,
> often called "content", but I'm trying
--On Thursday, January 16, 2020 16:40 -0500 Viktor Dukhovni via
Exim-users wrote:
> We'll have to disagree on this, because given non-conformant
> (with RFC5322 Section 2.1.1) input we're free to do whatever
> is reasonably pragmatic and yields a conformant message for
> delivery to the next
We'll have to disagree on this, because given non-conformant
(with RFC5322 Section 2.1.1) input we're free to do whatever
is reasonably pragmatic and yields a conformant message for
delivery to the next hop. Perhaps not surprisingly, users
preferred delivery over bounces.
> On Jan 16, 2020, at
Of course, Postfix is out of conformance with the standard and,
maybe more important, breaking any signatures over the message
body text, by doing this. Basically you can't win.
And that requirement is in the standard, not only because of the
historical reason of some implementations needing to
> On Jan 16, 2020, at 1:12 PM, Jeremy Harris via Exim-users
> wrote:
>
>> Does anyone know of anything that Exim can do to modify the message as
>> it is routed through
>
> Exim can't; it's a policy decision in what it regards it's job
> as being. That covers things like not converting from
On 16/01/2020 17:40, Paul Tansom via Exim-users wrote:
> Does anyone know of anything that Exim can do to modify the message as
> it is routed through
Exim can't; it's a policy decision in what it regards it's job
as being. That covers things like not converting from 8-bit-dirty
to uuencoded,
