> On Apr 22, 2024, at 23:31, Matus UHLAR - fantomas via Postfix-users > <postfix-users@postfix.org> wrote: > > On 22.04.24 22:55, Doug Hardie via Postfix-users wrote: >> This is probably not the right place to be asking this as it is not directly >> Postfix related, but I don't know a better group to ask. For years I have >> sent text messages and just let the lines run on. Only inserting a \n for >> the start of a new paragraph. I never exceed the 988 line length limit. My >> mail client does it's magic to make it smaller line lengths and the >> recipient's puts it back together again so that it fills whatever window >> size they are using. However, in the last couple days, something has >> changed. Looking at the raw sent text of the message, the lines are less >> than 80 bytes with an "=" at the end of each line that is not a line end. >> Going back through some of my email history, I see that occurring for years. >> It was never visible to me or any of my recipients. > > > >> I have a process that takes a portion of a received email and distributes it >> to a small recipient list. I am one of the recipients and It arrived with >> no cleanup. The = was at the end of every line. There was no reassembly of >> the original lines. The outgoing email had the following headers: >> >> Content-Type: text/plain; >> charset=us-ascii >> Content-Transfer-Encoding: quoted-printable >> >> I have searched the internet for some discussion of this and find nothing. >> The RFCs don't seem to address it either. Given the normal thoroughness of >> the RFCs I believe that just means I haven't found the right one. What >> controls this behavior and what is needed to get the reassembly to work >> again? > > this is quoted-printable MIME formatting which wraps lines to <80 characters > per line and uses = at the end of line as continuation character. > > see RFC 2045 section 6.7 for its definnition > > > I also recommend to look at the "format=flowed" option which is nicer > approach. > > RFC 3676 addresses this. >
That was an amazing and helpful response. RFC 2045 showed exactly what caused the problem. When the message was delivered to a file, the CRLFs were replaced by \n. An = followed by a \n is not a valid soft return. I am going to have to parse the text and fix that. Thanks, -- Doug _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
