On 1/26/20 4:43 PM, Allan Hansen wrote:
MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text.
The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list.\r\n -------------------------- ----------------------------------------------------------------------\r\n From: Allan Hansen <allan_hansen@icloud.com <mailto:allan_hansen@icloud.com>> Subject: [Testlist] wrap with divider and BLANKLINE
Which coding option am I missing? I have searched for one online.
I assume you are entering your text in Postorius in the DMARC wrapped message text box.
There are a number of things going on here. Postorius is wrapping and filling the text and stripping trailing whitespace. If you want more whitespace, I suggest following your text with one or more empty lines and a single dot as in
The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list.
.
In the above, the blank lines before and after the line of dashes will be preserved as will the final dot which should be unobtrusive enough.
More importantly, the rendering of the received message is up to your mail client. Your's apparently begins the wrapped message immediately after the wrapper's text, but many will not do that. Unless you actually view the received message in every mail client used by your user's, you won't know what they actually see.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan