Unwanted empty lines in reply/forward headers in plain-text emails #54

ckeydel · 2020-02-14T08:19:51Z

Normally I use HTML emails and I have set my reply and forward headers the way I want them, with the "Use HTML" checkbox checked, the "Replace line breaks with " unchecked (per the author's suggestion), and the tags put directly in the quote header.
With some people, I want to use plain-text format in replies because they send such emails to me and have requested that I reply in kind. So as usual in TB, I keep the <Shift> key pressed while hitting the reply or forward button to compose the email in plain-text format. This works in principle but two issues:

in the compose window there is a huge amount of white space before the signature, and also more white space than usual after the signature
there are extra empty lines between "From:", "Sent:" etc.

The extra lines in the reply header come from the HTML header's tags plus the regular line breaks. In HTML, they are interpreted correctly, i.e. don't lead to extra line breaks. In plain text, both are interpreted as line breaks. I guess that same thing happens with the HTML signature.

I can work around it by making the HTML reply header one super-long single line with tags in between but it's not exactly nice. The regular line breaks should be simply ignored for plain-text emails if it is a "Use HTML" header.

BTW this doesn't happen if "Replace line breaks with " is checked and I remove the tags. But I don't want to use this option anymore because of other issues.

RealRaven2000 · 2020-02-14T09:57:32Z

It would be helpful if you could export your account settings using the save template feature:

and also your signature. You may send them to me directly off github to preserve privacy. But you can make a screenshot here of your Composition & Addressing settings in Tb accounts:

ckeydel · 2020-02-14T10:14:58Z

Just sent this to you using GitHub direct email.

RealRaven2000 · 2020-02-14T10:37:56Z

hmm, not sure if I got that... can you send it to realraven2000@hotmail.com?

ckeydel · 2020-02-14T10:46:29Z

done.

RealRaven2000 · 2020-02-15T13:58:34Z

thanks, I got it now. Turns out Hotmail now also have a aggressive anti Spam policy like google, so I to recover the mail to see it on my POP3 account. I understand your default is HTML (like most) and you force plaintext by holding SHIFT when clicking on the reply button..

Should be easy enough to replicate. plaint text is the unloved stepchild of the SmartTemplate developer team (me). ;)

RealRaven2000 · 2020-02-15T16:23:08Z

Ok, I managed to load your template, let's have a look at the output when I force text mode with SHIFT:

it looks like there is additional space on the quote header lines (From: , Sent: , Cc: etc.). In source code it looks quite innocuous:

<!DOCTYPE html><html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body style="font-family: -moz-fixed; white-space: pre-wrap; width: 72ch;" smarttemplateinserted="true">
      <div id="smartTemplate4-template"><p> </p></div>
      <div id="smartTemplate4-quoteHeader">
<hr>
<b>From:</b> Axel (Thunderbird Daily 67) &lt;thunderbirddaily67@gmail.com&gt;<br>
<b>Sent:</b>  Saturday, 15.02.2020 16:13 UTC<br>
<b>To:</b> Axel (Development) &lt;development@quickfolders.org&gt;<br>
<b>Cc:</b> <br>
<b>Subject:</b> [SmartTemplate4] test - issue 54 (unwanted empty lines in plain-text)<br>
</div>

<span style="white-space: pre-wrap; display: block; width: 98vw;">&gt; Dear Axel (Thunderbird Daily 67)<br>

Once I delete the extra line breaks in editor, this removers the
parts. Relevant code portion:

<hr>
<b>From:</b> Axel (Thunderbird Daily 67) &lt;thunderbirddaily67@gmail.com&gt;
<b>Sent:</b>  Saturday, 15.02.2020 16:13 UTC
<b>To:</b> Axel (Development) &lt;development@quickfolders.org&gt;
<b>Cc:</b> 
<b>Subject:</b> [SmartTemplate4] test - issue 54 (unwanted empty lines in plain-text)<br>
</div>

So this means the text node treats textual line breaks (and not just   tags) as line breaks (unlike HTML source code). I need to find out which part of the "mail-building" code inserts the
or the line breaks.

RealRaven2000 · 2020-02-16T21:54:42Z

If you want to hear an amusing episode, I was just debugging SmartTempalte4 (this particular bug) while error checking a broken folder and listening to a YouTube video (talk about multi-tasking). Incidentally the SmartTemplate/Support folder was broken...
.... and then I got a BSOD

with a hard stop, not even being able to dump the memory. After hard restarting I had to find that my main HD (2 terabytes, divided into 2 equally sized partitions, D: for music/studio recording and E: for development) had decided to go to the happy hunting grounds in the sky.

Unfortunately, I didn't do a complete backup, but most of the current Add-on projects were saved. My recording system was not so lucky so I proceeded to call off all studio projects for the next week... I am still committed to fixing this bug but it will be a little delayed as I need to dedicate a major part of my energy to "getting up and running again".

Pretty happy that this particular issue (Unwanted empty lines, not the dat loss) should be easy to fix though. Onwards and upwards, I guess.

RealRaven2000 · 2020-02-17T00:50:21Z

... having said this: I just reserved some space on another partition with some restored data, so here is a test version with an attempted fix:

smartTemplate-fx-2.9.2pre5.zip

It only will fix the quote text if the following conditions apply

the Editor is in text only mode
the quote contains
or
elements. I take this as an assumption that you are not interested in replacing line breaks. (should probably use the [x] replace line breaks option instead, but this is quick and dirty and works for your example) - I need to think this through more...

  if (!IsHTMLEditor()) {
    // [issue 54] extra line spaces in (html) quote header when replying text only.
    // if template contains <br> or <p> let's strip out "formatting" text content line breaks.
    if (quoteHeader.includes("<br>") || quoteHeader.includes("<p>"))
      quoteHeader =  quoteHeader.replace(/\n/gm,"")
  }

ckeydel · 2020-02-17T08:09:17Z

Sorry to hear about your hard drive incident! I still have some stickers somewhere to help prevent future such catastrophes. Wait ... where are they. Ah, yes, here:

Sorry, couldn't resist! ;-)
Seriously, though, glad you got up and running relatively fast.

ckeydel · 2020-02-17T08:46:10Z

I tried v2.9.2pre5 (still reported as v2.9.1). Two issues:
First, in my reply header, the last two lines are:

Cc: %cc% 
Subject: %subject% 

but in the plain-text response email, there is no extra empty line between the reply header and the body text, which is odd:

Cc: Some Name <some@email.de>
Subject: Re: Whatever subject
> Yes! Some body text.

Since there will never be a case where the first line of body text is appended to the subject line, the last in the reply header should mean that there is one empty line. This would also be consistent with the HTML handling where there is also some space between the last line of the header and the first line of body text.

Secondly, the changes did nothing for the large amount of extra white space around the signature, "where you write your response text".

RealRaven2000 · 2020-02-17T09:58:00Z

I tried v2.9.2pre5 (still reported as v2.9.1). Two issues:
First, in my reply header, the last two lines are:

Cc: %cc% 
Subject: %subject% 

but in the plain-text response email, there is no extra empty line between the reply header and the body text, which is odd:

Cc: Some Name <some@email.de>
Subject: Re: Whatever subject
> Yes! Some body text.

That looks like what you asked it to do.... blockquote starts straight after the last (single)   . Why should SmartTemplate insert additional brs in plaintext?

Since there will never be a case where the first line of body text is appended to the subject line

You mean quoted text, right? Blockquote is a display:block level element and as such it always is in a separate line. So thinking about this in html layout there should probably be an empty line visible. Try adding a   after the last  

, the last
in the reply header should mean that there is one empty line. This would also be consistent with the HTML handling where there is also some space between the last line of the header and the first line of body text

I think this is just margin-top of blockquote. I don't think Smarttemplate should always insert an extra empty line before the quote.
.

Secondly, the changes did nothing for the large amount of extra white space around the signature, "where you write your response text".

??? Your template made no sense to me- it's only %sig(2)% and noting else - no salutation, no cursor - why? Where do you write, above or below your signature?

Also i don't believe i have your signature, is it HTML or plain text?

ckeydel · 2020-02-17T11:31:30Z

Yes, adding a second  after %subject% will create the right amount of spacing in both cases - plain-text and HTML, so this part can be considered closed IMO.

My default signature I sent you in my email on 2/14, both as screenshot and as HTML text. There is nothing special in it but it is in HTML format and therefore difficult to post here because the tags are getting removed. %cursor% is part of that signature not the template, I believe you sent me that whole signature as a suggestion in the past and I just copied it. I am writing above the signature - again, this info was in my email. I am using the same composition settings as you do.

Yes, I only use %sig(2)% here and add anything else myself on a case-by-case basis. Shouldn't be a problem, should it?

RealRaven2000 · 2020-02-17T11:40:34Z

but in the plain-text response email, there is no extra empty line between the reply header and the body text, which is odd:

Cc: Some Name some@email.de
Subject: Re: Whatever subject

Yes! Some body text.

(now on my desktop browser) this looks correct to me. This is the default behavior, with SmartTemplate disabled:

so as you can see - no extra space between the quote header "On 15/02/2020 16:13, Thunderbirddaily 67 wrote:" and the quoted text "> Dear Axel (Thunderbird Daily 67)..."

So the new line removal seems to work fine. and SmartTemplate is replacing the quote header line with whatever you give it. In source code (plain text) that Thunderbird standard quote header followed by blockquote part looks like this:

<div class="moz-cite-prefix">On 15/02/2020 16:13, Thunderbirddaily 67 wrote: </div>

In source, there is an extra   put there by Thunderbird but id doesn't show as an empty line as it is collapsed within the line break of the closing <div>. To uncollapse, you can force the empty line to show up by adding a non-breaking space after the   like this:

<div class="moz-cite-prefix">On 15/02/2020 16:13, Thunderbirddaily 67 wrote:  </div>

which will give you this result:

ckeydel · 2020-02-17T12:10:39Z

Yes, you're right, the   works, too. Something new learned today... :-)
So the reply header handling for plain-text emails is "good" now I think.

RealRaven2000 · 2020-02-17T12:18:32Z

Yes, adding a second
after %subject% will create the right amount of spacing in both cases - plain-text and HTML, so this part can be considered closed IMO.

My default signature I sent you in my email on 2/14, both as screenshot and as HTML text. There is nothing special in it but it is in HTML format and therefore difficult to post here because the tags are getting removed.

alright - in the future just use highlight any code and then use the <> button to wrap it so it doesn't actually get removed. It's hard to do on a mobile phone (which I replied to with earlier, so I had to edit on my desktop browser).

%cursor% is part of that signature not the template, I believe you sent me that whole signature as a suggestion in the past and I just copied it.

I think that's a little bit unfortunate, I would instead take it out of the signature and would instead change the template to something like this:

%cursor% <br>
%sig(2)%

I am writing above the signature - again, this info was in my email.

Yeah I didn't dig out the email, I get soo much support mail that it is hard to keep track :)

Yes, I only use %sig(2)% here and add anything else myself on a case-by-case basis. Shouldn't be a problem, should it?

Not a problem, just semantically what you are doing is "writing in the signature" and not in the template, so it may present some problems if you try to style in HTML later. Personally my default (and recommended) pattern is like this:

<style> ... (all my CSS rules for my mail body) </style>
<div id="mytemplate">
  <p> (automated salutation) </p>
  <p> %cursor% </p>
  <p> yours sincerely, </p>
  %sig(html)%
</div>

I can use that as a common template with different signatures - you obviously do not need the following optional parts:

styling (if you trust Thunderbird to do that for you and don't care what it looks like or want the defaults of the mail client person you send to decide)
first line (salutation) - I usually have %from(name)% in a reply because I am lazy. I think you prefer to type it manually.
third line (the goodbye line) - again, me being lazy
 for writing all my email text within Paragraphs, I like that because it provides more natural spacing than mashing the new line twice every time, of course you can do this "type writer style" editing too, but I always tend to think my style rules should determine the space between paragraphs. Also I dislike using   for "layout".
And I am lazy :)

so at its core you are left with this minimal approach:

 <div id="ck">
   %cursor%<br>
   %sig(html)%
 </div>

The quote would be displayed separate to the <div> which representing your reply, above or below according to your composition settings in Thunderbird.

And then you can do a bit of trickery for styling stuff in your way (hence id="ck", so it doesn't affect your quoted mail) and you can just start typing above the signature like you used to. I am actually planning to implement a new %style(path)% command for the future so I can share a style sheet between different templates for the same product.

ckeydel · 2020-02-17T19:28:59Z

That's nice! I started playing with it and it really is better.
Only the indentation, that doesn't play nice with plain-text emails because they are put before the cursor and the signature as real spaces.

ckeydel · 2020-02-17T20:00:23Z

Nah, for the signature the spacing is still too big. I have used your core/minimal approach for the ST4 signature, just removing the identation and I have defined a really simple signature in TB for testing:
Best Regards, 
Chris

So the "Chris" should be in the next line after "Best Regards", right? This is indeed the case when replying normally as HTML:

But as plain-text reply, this looks like this:

So yes, there is still a full line between "Best Regards" and "Chris". And an extra line after "Chris". And an extra line between the cursor and "Best Regards".

ckeydel · 2020-02-17T20:01:46Z

Oh, and an extra line before the cursor as well.

RealRaven2000 · 2020-02-17T20:31:35Z

to get a better idea of what is really happening, I highly recommend installing the Add-on ThunderHtmlEdit, where you can switch back and forth between the view and the HTML behind that.

Now with the HTML editor you an actually influence the distance for the <div> by using some css css rules such as margin-bottom and they only affect the HTML result but not the plain text one. Plain text is always working in terms of "whole lines" and there is nothing you can do about it. Bt you can avoid the extra line break for instance by removing the   (non breaking space) after the   or using less   elements. You can then add additional vertical space to the bottom of the div with margin-bottom.

Example:

<style>
#ck { 
  margin-bottom: 12px;
}
</style>
 <div id="ck">
   %cursor%<br>
   %sig(html)%
 </div>

Now it obviously depends on the content of your sig on what's at the bottom and may generate extra spacing towards your quote header. You will only know when looking into the "generated HTML" in ThunderHTMLEdit (within Thunderbird Composer). You can check the actual values using the "inspector" tool of the main Thunderbird window (tools menu).

You can then select the composer document from the document chooser on the top right:

you can then use the "inspector" top left for clicking on elements in the composer window and the "Layout" tab on the right to tell us about what it does distance-wise:

the "box model" tells us the full truth:

as you see, this stuff isn't exactly easy or easy to explain, but it's well worth the learning curve...

ckeydel · 2020-02-17T20:44:22Z

I remember this working really well, waaay back with old versions of TB and the predecessor of your add-on. And then, little by little, as TB "progressed", it all fell apart.

Anyway, thanks for your explanations and I will look into it, but my main problem seems to be that I can't find a way to have HTML signatures where individual lines don't get separated by extra lines in plain text emails. Do you have an idea for this? Just multiple lines in HTML that stay that way in plain text.

RealRaven2000 · 2020-02-17T21:18:58Z

maybe we have the same problem as in your quote header (I had to do some modifications to deal with that)?

Can you put your signature here (just mask personal info such as email addresses with ***)

You can easily post multi-line code in github and then highlight and press the insert code button afterwards, which will wrap it with "triple apostrophes" which is markdown for "leave this alone" ;)

(check the preview tab to try it out). Example for a sig (css rules stripped for brevity):

<div id="mySignature">
  <b class="myName">%identity(name,link)%</b>
  <br/>Thunderbird Daily
  <br/>
  <span class="AddonList">(<a href="https://addons.thunderbird.net/thunderbird/addon/quickfolders-tabbed-folders/">QuickFolders</a>, 
  <a href="https://addons.thunderbird.net/thunderbird/addon/quickfilters/">quickFilters</a>, 
  <a href="https://addons.mozilla.org/firefox/addon/quickpasswords/">QuickPasswords</a>, 
  <a href="https://addons.thunderbird.net/thunderbird/addon/zombie-keys/">Zombie Keys</a>, 
  <a href="https://addons.thunderbird.net/thunderbird/addon/smarttemplate4/">SmartTemplate⁴</a>)</span>
  <br/>
  Visit my <a href="https://www.youtube.com/c/thunderbirddaily">YouTube Channel</a> for email productivity tips

  <img style="margin-top: 1em; float: right; box-shadow: 1px 1px 2px rgba(20, 20, 20, 0.4);" 
      moz-do-not-send="false"
      class="myLogo"  
      src="file:///C:/Users/Axel/Documents/Thunderbird/Signatures/thunderbird_blog2.png" 
      alt="Get Thunderbird!" 
      height="15" 
      width="94">
</div>

that one gets nicely "stripped down" in plain text mode here (I probably have to set up my test identity better so that %identity(name)% is properly resolved, but it may be another bug i need to investigate:

-- 
*%identity(name,link)%*
Thunderbird Daily
(QuickFolders
<https://addons.thunderbird.net/thunderbird/addon/quickfolders-tabbed-folders/>,
quickFilters
<https://addons.thunderbird.net/thunderbird/addon/quickfilters/>,
QuickPasswords
<https://addons.mozilla.org/firefox/addon/quickpasswords/>, Zombie Keys
<https://addons.thunderbird.net/thunderbird/addon/zombie-keys/>,
SmartTemplate⁴
<https://addons.thunderbird.net/thunderbird/addon/smarttemplate4/>)
Visit my YouTube Channel <https://www.youtube.com/c/thunderbirddaily>
for email productivity tips Get Thunderbird!

RealRaven2000 · 2020-02-17T21:27:33Z

Ok I spoke too soon - I actually tested while I had the template disabled on the accounbt, I am getting a very interesting "bastardized" mixture in plain text mode. First in HTML , for comparison:

and now in "plain text" (ish) mode - holding down SHIFT while replying:

So there still are plenty of extra lines in the signature box and even the body of the template itself,. Looks like I only solved the problem for the quote header. but that's to be expected when we fix a single thing only. I will keep testing. Still don't quite understand why there is even styling shown in a "plain text" window...

plain text, the unloved stepchild of SmartTemplate4 ;)

I believe all extra line breaks are "HTML formatting" which can be stripped out, as I did in the quote header.

RealRaven2000 · 2020-02-17T22:25:38Z

OK, here is a trial version:

smartTemplate-fx-2.9.2pre15.zip

... which is hopefully a little bit better in plain text. (not quite there yet, but closer)

improved output in plain text mode, with definitely a lot less uselss line breaks:

ckeydel · 2020-02-18T08:56:09Z

Yes, this version fixes it for me - great!

Why do you say "not quite there yet"? AFAICS this version handles line breaks perfectly - I am getting exactly the same in both HTML and plain-text responses.

BTW the fact that one is getting HTML-fomatted text for the reply header, signature etc. in a plain-text compose window is one of the oddities that TB introduced at some point. I remember "back in the old days", a plain-text compose window really meant plain-text when writing your email. But honestly, as long as I can rely on the format being ok when the email goes out, I don't care anymore. Just one more strange thing to live with I guess.

RealRaven2000 · 2020-02-18T16:17:32Z

Why do you say "not quite there yet"? AFAICS this version handles line breaks perfectly - I am getting exactly the same in both HTML and plain-text responses.

If you look at the screenshot of the signature there is a line break after the "Quickpasswords" Hyperlink. AFAIK it should break after 72 characters, so this looks a little early to me. Also the leading spaces are definitely ugly. I wonder if HTML should at least "collapse" all white spaces to a single one. Finally replacing newlines with nothing may lead to stuff "caking together" so replacement with a single space may be better. My safeguard at the moment is (not ideal) that I only do these replacements if the HTML snippet contains   or  tags (which may be overly cautious).

BTW the fact that one is getting HTML-fomatted text for the reply header, signature etc. in a plain-text compose window is one of the oddities that TB introduced at some point. I remember "back in the old days", a plain-text compose window really meant plain-text when writing your email. But honestly, as long as I can rely on the format being ok when the email goes out, I don't care anymore. Just one more strange thing to live with I guess.

it would be nice to have an alternative (text-only) alternative signature for this case but that also means additional identity management work for the user. The whole point about using CSS rules for HTML is that it "degrades gracefully" so that it still looks meaningful and well layouted when a mail client can only display text-only mails.

ckeydel · 2020-02-18T17:38:47Z

Also the leading spaces are definitely ugly.

Pretty sure these come from the indentation in your HTML template. I have manually removed them in mine - the HTML works just as well without. But yes, it would be nice if they could stay in without affecting the plain-text version.

it would be nice to have an alternative (text-only) alternative signature for this case

True

RealRaven2000 · 2020-02-18T20:42:19Z

Also the leading spaces are definitely ugly.

Pretty sure these come from the indentation in your HTML template. I have manually removed them in mine - the HTML works just as well without. But yes, it would be nice if they could stay in without affecting the plain-text version.

Would it be fair to say these are only leading spaces following block level elements / elements that insert line breaks? There may be a regular expression to take care of that...

RealRaven2000 · 2020-02-18T20:48:27Z

So I found a regular expression for replacing the leading spaces (and tabs) too; here is the new replacement routine:

function cleanPlainTextNewLines(myHtml) {
  let lc = myHtml.toLocaleLowerCase();
  if (lc.includes("<br") || lc.includes("<p"))
    return myHtml.replace(/(\r\n)+|\r+|\n+|^[ \t]+/gm,""); 
  return myHtml;
}

Leading to a cleaner output (from the same HTML signature):

To force leading spaces, you can still use the   html entity. Tryout version:

smartTemplate-fx-2.9.2pre16.zip

ckeydel · 2020-02-20T08:32:04Z

Yes, good so far. Just noticed there are extra spaces in the plain-text reply header where there shouldn't be. For example, this is the HTML version:

And here is the plain-text version of the same replied-to email:

I marked the extra space in yellow. Why the extra space only in the "Sent:" line? Well, I am using this construct:

Sent: %X:=sent% %A%, %d%.%m%.%Y% %H%:%M% UTC 

Yes, there is a space before and after %X:=sent% and if I remove either one, it works as expected in both cases, e.g.:

Sent:%X:=sent% %A%, %d%.%m%.%Y% %H%:%M% UTC 

But is is different behaviour between HTML and plain-text, nonetheless, and may also happen with other constructs that I am not using.

RealRaven2000 · 2020-02-20T10:34:41Z

I marked the extra space in yellow. Why the extra space only in the "Sent:" line?

Because HTML automatically "collapses" all spaces (and line breaks and tabs) into one single space. I was debating with myself whether I should do this during the plain text conversion or not; obviously getting rid of leading space was already a good start. But should all spaces be collapsed?

Well, I am using this construct:

Sent: %X:=sent% %A%, %d%.%m%.%Y% %H%:%M% UTC 

Yes, there is a space before and after %X:=sent% and if I remove either one, it works as expected in both cases, e.g.:

Also there may be an additional difficulty because the plain text conversion happens before SmartTemplate replaces its variables (IIRC) so it won't know that there will be a double space. Notwithstanding of me fixing the space issue I would recommend this more comfortable way of writing that:

%X:=sent%Sent: %dateformat(A, d.m.Y H:M)% UTC 

In v 2.8, I have provided some multi-lingual examples on the variables tab, under the caption "Variables for customized 'Date format'":

you can just click them to insert into your template.

ckeydel · 2020-02-20T11:01:48Z

Yes, using %dateformat% is much nicer, thanks!

You're probably right - some people may want to use extra spacing.

ckeydel · 2020-02-21T08:42:35Z

OT: converter.html2txt.structs=false removes the TB-specific plain-text formatting such as using enclosing '*' for bold text:

so that it looks ... well, plain:

... just adding this here for those plain-text aficionados that may stumble across this.

RealRaven2000 · 2020-04-14T21:45:46Z

Fixed in 2.10.1 released on 14/04/2020

ckeydel closed this as completed Feb 17, 2020

ckeydel reopened this Feb 17, 2020

RealRaven2000 self-assigned this Feb 17, 2020

RealRaven2000 closed this as completed Apr 14, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unwanted empty lines in reply/forward headers in plain-text emails #54

Unwanted empty lines in reply/forward headers in plain-text emails #54

ckeydel commented Feb 14, 2020 •

edited

RealRaven2000 commented Feb 14, 2020

ckeydel commented Feb 14, 2020

RealRaven2000 commented Feb 14, 2020

ckeydel commented Feb 14, 2020

RealRaven2000 commented Feb 15, 2020

RealRaven2000 commented Feb 15, 2020

RealRaven2000 commented Feb 16, 2020

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 17, 2020

ckeydel commented Feb 17, 2020 •

edited

RealRaven2000 commented Feb 17, 2020 •

edited

ckeydel commented Feb 17, 2020 •

edited by RealRaven2000

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 17, 2020 •

edited by RealRaven2000

RealRaven2000 commented Feb 17, 2020 •

edited

ckeydel commented Feb 17, 2020

ckeydel commented Feb 17, 2020

ckeydel commented Feb 17, 2020

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 17, 2020

RealRaven2000 commented Feb 17, 2020

RealRaven2000 commented Feb 17, 2020 •

edited

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 18, 2020 •

edited

RealRaven2000 commented Feb 18, 2020 •

edited

ckeydel commented Feb 18, 2020

RealRaven2000 commented Feb 18, 2020

RealRaven2000 commented Feb 18, 2020 •

edited

ckeydel commented Feb 20, 2020

RealRaven2000 commented Feb 20, 2020 •

edited

ckeydel commented Feb 20, 2020

ckeydel commented Feb 21, 2020

RealRaven2000 commented Apr 14, 2020

Unwanted empty lines in reply/forward headers in plain-text emails #54

Unwanted empty lines in reply/forward headers in plain-text emails #54

Comments

ckeydel commented Feb 14, 2020 • edited

RealRaven2000 commented Feb 14, 2020

ckeydel commented Feb 14, 2020

RealRaven2000 commented Feb 14, 2020

ckeydel commented Feb 14, 2020

RealRaven2000 commented Feb 15, 2020

RealRaven2000 commented Feb 15, 2020

RealRaven2000 commented Feb 16, 2020

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 17, 2020

ckeydel commented Feb 17, 2020 • edited

RealRaven2000 commented Feb 17, 2020 • edited

ckeydel commented Feb 17, 2020 • edited by RealRaven2000

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 17, 2020 • edited by RealRaven2000

RealRaven2000 commented Feb 17, 2020 • edited

ckeydel commented Feb 17, 2020

ckeydel commented Feb 17, 2020

ckeydel commented Feb 17, 2020

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 17, 2020

RealRaven2000 commented Feb 17, 2020

RealRaven2000 commented Feb 17, 2020 • edited

RealRaven2000 commented Feb 17, 2020

ckeydel commented Feb 18, 2020 • edited

RealRaven2000 commented Feb 18, 2020 • edited

ckeydel commented Feb 18, 2020

RealRaven2000 commented Feb 18, 2020

RealRaven2000 commented Feb 18, 2020 • edited

ckeydel commented Feb 20, 2020

RealRaven2000 commented Feb 20, 2020 • edited

ckeydel commented Feb 20, 2020

ckeydel commented Feb 21, 2020

RealRaven2000 commented Apr 14, 2020

ckeydel commented Feb 14, 2020 •

edited

ckeydel commented Feb 17, 2020 •

edited

RealRaven2000 commented Feb 17, 2020 •

edited

ckeydel commented Feb 17, 2020 •

edited by RealRaven2000

ckeydel commented Feb 17, 2020 •

edited by RealRaven2000

RealRaven2000 commented Feb 17, 2020 •

edited

RealRaven2000 commented Feb 17, 2020 •

edited

ckeydel commented Feb 18, 2020 •

edited

RealRaven2000 commented Feb 18, 2020 •

edited

RealRaven2000 commented Feb 18, 2020 •

edited

RealRaven2000 commented Feb 20, 2020 •

edited