[Users] error in display of empty quoted lines

[Dave Howorth]

On Sat, 7 Apr 2018 22:14:49 +0200
wwp <subscript at free.fr> wrote:

> Hello Dave,
> 
> 
> On Sat, 7 Apr 2018 21:05:37 +0100 Dave Howorth <dave at howorth.org.uk>
> wrote:
> 
> > On Sat, 7 Apr 2018 17:17:41 +0200
> > Andrej Kacian <ticho at claws-mail.org> wrote:
> >   
> > > On Sat, 7 Apr 2018 12:31:34 +0100
> > > Dave Howorth <dave at howorth.org.uk> wrote:
> > >     
> > > > Hmm, claws displays my mail as I would hope, so there's
> > > > something more complicated going on. What other information
> > > > does the display depend upon than the characters actually in
> > > > the text?      
> > > 
> > > It would probably help if you were able to forward (as
> > > attachment) an example message - if it's not something private,
> > > of course.    
> > 
> > Indeed, but I didn't write the original message and don't have
> > permission to reproduce it. I'll see if I can get it.  
> 
> Make a copy of the email file itself, replace recipients, body text
> and other sensible words with random ones, what matters is the text
> structure, not the words themselves, and we don't care about
> sender/recipients.
> 
> Regards,

OK, there's a hacked about version attached.

BTW, I discovered that the message I sent to the claws-mail list was 

Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

but what the list sent back to me was

Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

I have no idea why the list software would do that.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: orig.txt
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20180407/978569cb/attachment.txt>