On Mon, Oct 17, 2022 at 9:07 PM Grant Taylor via mailop <mailop@mailop.org> wrote:
> On 10/17/22 9:11 PM, Brandon Long via mailop wrote: > > Certainly, but do you consider some edge cases like composing bounces > > or relaying messages as generating messages? > > Yes, generating a DSN is generation of a message. No, /relaying/ is not > generating a message. > Right, but you can't stick a non-compliant message into a DSN directly and have that be a compliant message... so you either make the non-compliant message compliant when you stick it into the DSN, or you figure that a sender who sends a non-compliant message can handle a non-compliant response. And while this particular case of re-wrapping lines is fairly easy to fixup when generating the DSN, other cases like embedded non-utf8 8bit characters are more complicated... just auto-detect the language, convert to utf8 and embed in a message/global, I'm sure their system will know what to do with that ;) Or that you autowrap the lines to generate the DSN, and then bounce it for too longer headers, and they go "oh, your engineers can't even properly count the number of characters on a line, clearly there isn't a line here that's too long, let me add that to my manifesto" Brandon
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
