Ubuntu
thunderbird package

Thunderbird's mdn (receipt) message may contain 822bis-violating bare lf which is rejected by Qmail

Bug #233990 reported by André Pirard
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mozilla Thunderbird
New
Unknown
thunderbird (Ubuntu)
Triaged
Low
Unassigned

Bug Description

C de-Avillez:
TESTED: Thunderbird 2.0.0.23 (Karmic)
              Thunderbird Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7pre) Gecko/20091214 Shredder/3.0.1pre (MozillaTeam PPA)

WORKAROUND: Do not use accented characters on the email's display name.

André Pirard: Update:
As I mentioned it before, in addition to requesting people to make spelling mistakes, this so-called WORKAROUND only works for sent e-mail and only when the error comes from the From: line, so that the person you send the e-mail to did not encounter the error if ever he runs Thunderbird through Qmail.
It does not work at all if the error comes from the Subject line or for any case of e-mail being received.

Original Report:
Thunderbird 2.0.0.14 sends the attached Receipt message.
(file as stolen from /tmp)
qmail-ldap-1.03 complains that it contains a "bare lf".
See attached dialog box & http://cr.yp.to/docs/smtplf.html
Dialog box is acknowledged.
Thunderbird just disappears.
Receipt never arrives and Thunderbird forgets about it.
Apport on strike but segfaults spotted, see attached syslog.

Update :
Please note that the (main) point of this report is *not* a Thunderbird crash but qmail's refusal to transmit the message, which is absolutely repeatable.
The crash itself is not repeatable and may or may not be a side effect.
Thunderbird most often exhibits the bare lf problem without crashing.
I changed the title of this report accordingly.
The whole story is in the attached mdnmsg file.

Update 2 :

1) I've been accused to have made a bad report because I did no follow :
http://help.ubuntu.com/community/ReportingBugs#Writing a useful report

2) C de-Avillez wants to see the bare linefeeds but he refuses to download the file and run grep.

Let us recall that everything is in the mdnmsg file which will show the problem to a developer in 1 minute.
But I will spend 2 hour instead to administratively unlock this case and I do hope it will.

Let's go.

> Writing a useful report
>
> 1. What you expected to happen
>
   1. switch on the HP Compaq 6270s computer (or any?)
   2. launch Ubuntu 8.10 (or any?)
   3. launch Thunderbird 2.0.0.14 (or any?)
   4. write the message contained in the attached mdn file
   5. send that message
   6. display my IMAP INBOX
   7. find that message
   8. open it
   9. click Yes to send the Return Receipt
  10. read the message and be happy
  11. close the message
  12. display the IMAP INBOX again
  13. find the Return Receipt contained in the attached mdn file
  14. open the Return Receipt
  15. make sure by reading the Receipt that I read the message
  16. close the Receipt
  17. close Thunderbird
  18. shutdown the computer
  19. watch the TV
>
> 2. What actually happened
>
   1. switch on the HP Compaq 6270s computer
   2. launch Ubuntu 8.10
   3. launch Thunderbird 2.0.0.14
   4. write the message contained in the attached mdn file
   5. send that message
   6. display my IMAP INBOX
   7. find that message
   8. open it
   9. click Yes to send the Return Receipt (which should be sent AFTER reading the message BTW)
  10. receive the error message in the attached Screenshot-Alert.png
  11. read the error message and be unhappy
  12. save /tmp/mdnmsg for bug reporting sake
  13. close the error message
  14. read the message and be happy anyway
  15. display the IMAP INBOX of the sender
  16. could not find any Return Receipt and never will
  17. sent mdnmsg and Screenshot-Alert.png to bugs.launchpad
  18. told them that mdnmsg contains the message I sent
  19. and the Receipt that failed to be sent
  20. and that Screenshot-Alert contains the error message
  21. read that they don't understand and that I'm a bad reporter
  22. wanted to quit the business
  23. wrote this instead on request
  24. did not shutdown the computer
  25. did not watch the TV

> 1. The minimal series of steps necessary to make it happen, where step 1 is "start the program"

   1. "start the program"
   2. in the correct environment, send a similar message to the one contained in mdnmsg
   3. receive and read the message, try to send the Receipt, you must get an error if it goes trough qmail

Alternative

> 1. The minimal series of steps necessary to make it happen, where step 1 is "start the program"

   1. "start the program"
   2. run TB in session A with e-mail account A requesting Return Receipts
   3. create Ubuntu user profile T
   4. in T, create a TB account T with a provider using SSL and/or, best, Qmail
   5. !!! never have TB "remember" this SSL password !!!
   6. from A, send an e-mail to T (requesting RR)
   7. check mail in T, open the e-mail, the SSL password is asked, do no answer yet
       or, without SSL and with Qmail an Alert box must be acknowledged in case of error
   8. make a copy of /tmp/mdnmsg, that's a copy of the Return Receipt being sent
   9. now or later, run the grep command on mdnmsg to spot bare linefeeds
  10. answer SSL password or ack Alert and see if Return Receipt is sent
  11. repeat from 6 with various test cases

Note : to determine the "correct environment", you will have to read mdnmsg first.
After reading it, you will most probably understand the bug and not want to "make it happen".

> Fill in the description field with as much information as you can, including the release of Ubuntu you are using and steps for someone else to recreate the bug. It is better to have too much information in the description than not enough.

Is this enough information?
If yo need anything else, please be specific.

> Add supporting attachments to explain or help others reproduce your bug. This might include a screenshot or video capture of the problem or a sample document that triggers the fault. To add an attachment to the bug use the Include an attachment section of the bug form. Additional attachments, if necessary, can be added after the bug is reported via Add a comment/attachment at the bottom of the page.

Risking ro be repetitive : everything is in mdnmsg.
I sent a screenshot from the very start and the answer to s.o.'s "can you please send one" is "look twice".
About sending a video, the answer is : nothing is moving, especially not this bug report.

Regarding the question "what are bare linefeed" or "where are they", whatever that means :
I fetched and re-uploaded the various mdnmsg samples with numbered names.
And I ran the grep command as follows, remark below.

$ grep -P '[^\r]\n' mdnmsg0.eml | tee /dev/tty | hd
To: =?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=
 <email address hidden>
00000000 54 6f 3a 20 3d 3f 55 54 46 2d 38 3f 42 3f 51 57 |To: =?UTF-8?B?QW|
00000010 35 6b 63 73 4f 70 49 46 42 70 63 6d 46 79 5a 41 |5kcsOpIFBpcmFyZA|
00000020 3d 3d 3f 3d *0a* 20 3c 41 5f 50 69 72 61 72 64 40 |==?=. <A_Pirard@|
00000030 68 6f 74 6d 61 69 6c 2e 63 6f 6d 3e 0d 0a |hotmail.com>..|
0000003e

$ grep -P '[^\r]\n' mdnmsg1.eml | tee /dev/tty | hd
To: =?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=
 <email address hidden>
00000000 54 6f 3a 20 3d 3f 55 54 46 2d 38 3f 42 3f 51 57 |To: =?UTF-8?B?QW|
00000010 35 6b 63 73 4f 70 49 46 42 70 63 6d 46 79 5a 41 |5kcsOpIFBpcmFyZA|
00000020 3d 3d 3f 3d *0a* 20 3c 41 5f 50 69 72 61 72 64 40 |==?=. <A_Pirard@|
00000030 68 6f 74 6d 61 69 6c 2e 63 6f 6d 3e 0d 0a |hotmail.com>..|
0000003e

$ grep -P '[^\r]\n' mdnmsg2.eml | tee /dev/tty | hd
Subject: Return Receipt (displayed) - =?UTF-8?B?RG9zc2llciBGMjAwOTA0MDEwMCAgIHLDqWYuIDogTE0v?=
 =?UTF-8?B?MjAwOS8wOTUy?=
00000000 53 75 62 6a 65 63 74 3a 20 52 65 74 75 72 6e 20 |Subject: Return |
00000010 52 65 63 65 69 70 74 20 28 64 69 73 70 6c 61 79 |Receipt (display|
00000020 65 64 29 20 2d 20 3d 3f 55 54 46 2d 38 3f 42 3f |ed) - =?UTF-8?B?|
00000030 52 47 39 7a 63 32 6c 6c 63 69 42 47 4d 6a 41 77 |RG9zc2llciBGMjAw|
00000040 4f 54 41 30 4d 44 45 77 4d 43 41 67 49 48 4c 44 |OTA0MDEwMCAgIHLD|
00000050 71 57 59 75 49 44 6f 67 54 45 30 76 3f 3d *0a* 20 |qWYuIDogTE0v?=. |
00000060 3d 3f 55 54 46 2d 38 3f 42 3f 4d 6a 41 77 4f 53 |=?UTF-8?B?MjAwOS|
00000070 38 77 4f 54 55 79 3f 3d 0d 0a |8wOTUy?=..|
0000007a

$ grep -P '[^\r]\n' mdnmsg3.eml | tee /dev/tty | hd
Subject: Return Receipt (displayed) - =?ISO-8859-1?Q?Re:_WiFi_=28liaison_de_donn=E9es_par_radio=29_pou?=
 =?ISO-8859-1?Q?r_Th=E9r=E8se,_3*20?=
00000000 53 75 62 6a 65 63 74 3a 20 52 65 74 75 72 6e 20 |Subject: Return |
00000010 52 65 63 65 69 70 74 20 28 64 69 73 70 6c 61 79 |Receipt (display|
00000020 65 64 29 20 2d 20 3d 3f 49 53 4f 2d 38 38 35 39 |ed) - =?ISO-8859|
00000030 2d 31 3f 51 3f 52 65 3a 5f 57 69 46 69 5f 3d 32 |-1?Q?Re:_WiFi_=2|
00000040 38 6c 69 61 69 73 6f 6e 5f 64 65 5f 64 6f 6e 6e |8liaison_de_donn|
00000050 3d 45 39 65 73 5f 70 61 72 5f 72 61 64 69 6f 3d |=E9es_par_radio=|
00000060 32 39 5f 70 6f 75 3f 3d *0a* 20 3d 3f 49 53 4f 2d |29_pou?=. =?ISO-|
00000070 38 38 35 39 2d 31 3f 51 3f 72 5f 54 68 3d 45 39 |8859-1?Q?r_Th=E9|
00000080 72 3d 45 38 73 65 2c 5f 33 2a 32 30 3f 3d 0d 0a |r=E8se,_3*20?=..|
00000090

$ grep -P '[^\r]\n' mdnmsg4.eml | tee /dev/tty | hd
Subject: Return Receipt (displayed) - Joyeux =?UTF-8?B?Tm/Dq2wgOiBVbiDDqXRvbm5hbnQgb3JkaSBzb3VzIGxlIHNh?=
 =?UTF-8?B?cGlu?=
To: =?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=
 <email address hidden>
00000000 53 75 62 6a 65 63 74 3a 20 52 65 74 75 72 6e 20 |Subject: Return |
00000010 52 65 63 65 69 70 74 20 28 64 69 73 70 6c 61 79 |Receipt (display|
00000020 65 64 29 20 2d 20 4a 6f 79 65 75 78 20 3d 3f 55 |ed) - Joyeux =?U|
00000030 54 46 2d 38 3f 42 3f 54 6d 2f 44 71 32 77 67 4f |TF-8?B?Tm/Dq2wgO|
00000040 69 42 56 62 69 44 44 71 58 52 76 62 6d 35 68 62 |iBVbiDDqXRvbm5hb|
00000050 6e 51 67 62 33 4a 6b 61 53 42 7a 62 33 56 7a 49 |nQgb3JkaSBzb3VzI|
00000060 47 78 6c 49 48 4e 68 3f 3d *0a* 20 3d 3f 55 54 46 |GxlIHNh?=. =?UTF|
00000070 2d 38 3f 42 3f 63 47 6c 75 3f 3d 0d 0a 54 6f 3a |-8?B?cGlu?=..To:|
00000080 20 3d 3f 55 54 46 2d 38 3f 42 3f 51 57 35 6b 63 | =?UTF-8?B?QW5kc|
00000090 73 4f 70 49 46 42 70 63 6d 46 79 5a 41 3d 3d 3f |sOpIFBpcmFyZA==?|
000000a0 3d *0a* 20 3c 41 5f 50 69 72 61 72 64 40 68 6f 74 |=. <A_Pirard@hot|
000000b0 6d 61 69 6c 2e 63 6f 6d 3e 0d 0a |mail.com>..|
000000bb

$ grep -P '[^\r]\n' mdnmsg5.eml | tee /dev/tty | hd
To: =?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=
 <email address hidden>
00000000 54 6f 3a 20 3d 3f 55 54 46 2d 38 3f 42 3f 51 57 |To: =?UTF-8?B?QW|
00000010 35 6b 63 73 4f 70 49 46 42 70 63 6d 46 79 5a 41 |5kcsOpIFBpcmFyZA|
00000020 3d 3d 3f 3d *0a* 20 3c 41 5f 50 69 72 61 72 64 40 |==?=. <A_Pirard@|
00000030 68 6f 74 6d 61 69 6c 2e 63 6f 6d 3e 0d 0a |hotmail.com>..|
0000003e

$ grep -P '[^\r]\n' mdnmsgN0.eml | tee /dev/tty | hd

$ grep -P '[^\r]\n' mdnmsgN1.eml | tee /dev/tty | hd
To: =?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=
 <email address hidden>
00000000 54 6f 3a 20 3d 3f 55 54 46 2d 38 3f 42 3f 51 57 |To: =?UTF-8?B?QW|
00000010 35 6b 63 73 4f 70 49 46 42 70 63 6d 46 79 5a 41 |5kcsOpIFBpcmFyZA|
00000020 3d 3d 3f 3d *0a* 20 3c 41 2e 50 69 72 61 72 64 40 |==?=. <A.Pirard@|
00000030 75 6c 67 2e 61 63 2e 62 65 3e 0d 0a |ulg.ac.be>..|
0000003c

$ grep -P '[^\r]\n' mdnmsgN2.eml | tee /dev/tty | hd
Subject: Return Receipt (displayed) - Joyeux =?UTF-8?B?Tm/Dq2wgOiBVbiDDqXRvbm5hbnQgb3JkaSBzb3VzIGxlIHNh?=
 =?UTF-8?B?cGlu?=
00000000 53 75 62 6a 65 63 74 3a 20 52 65 74 75 72 6e 20 |Subject: Return |
00000010 52 65 63 65 69 70 74 20 28 64 69 73 70 6c 61 79 |Receipt (display|
00000020 65 64 29 20 2d 20 4a 6f 79 65 75 78 20 3d 3f 55 |ed) - Joyeux =?U|
00000030 54 46 2d 38 3f 42 3f 54 6d 2f 44 71 32 77 67 4f |TF-8?B?Tm/Dq2wgO|
00000040 69 42 56 62 69 44 44 71 58 52 76 62 6d 35 68 62 |iBVbiDDqXRvbm5hb|
00000050 6e 51 67 62 33 4a 6b 61 53 42 7a 62 33 56 7a 49 |nQgb3JkaSBzb3VzI|
00000060 47 78 6c 49 48 4e 68 3f 3d *0a* 20 3d 3f 55 54 46 |GxlIHNh?=. =?UTF|
00000070 2d 38 3f 42 3f 63 47 6c 75 3f 3d 0d 0a |-8?B?cGlu?=..|
0000007d

$ grep -P '[^\r]\n' mdnmsgN3.eml | tee /dev/tty | hd
Subject: Return Receipt (displayed) - Joyeux =?UTF-8?B?Tm/Dq2wgOiBVbiDDqXRvbm5hbnQgb3JkaSBzb3VzIGxlIHNh?=
 =?UTF-8?B?cGlu?=
To: =?UTF-8?B?QW5kcsOpIFBpcmFyZA==?=
 <email address hidden>
00000000 53 75 62 6a 65 63 74 3a 20 52 65 74 75 72 6e 20 |Subject: Return |
00000010 52 65 63 65 69 70 74 20 28 64 69 73 70 6c 61 79 |Receipt (display|
00000020 65 64 29 20 2d 20 4a 6f 79 65 75 78 20 3d 3f 55 |ed) - Joyeux =?U|
00000030 54 46 2d 38 3f 42 3f 54 6d 2f 44 71 32 77 67 4f |TF-8?B?Tm/Dq2wgO|
00000040 69 42 56 62 69 44 44 71 58 52 76 62 6d 35 68 62 |iBVbiDDqXRvbm5hb|
00000050 6e 51 67 62 33 4a 6b 61 53 42 7a 62 33 56 7a 49 |nQgb3JkaSBzb3VzI|
00000060 47 78 6c 49 48 4e 68 3f 3d *0a* 20 3d 3f 55 54 46 |GxlIHNh?=. =?UTF|
00000070 2d 38 3f 42 3f 63 47 6c 75 3f 3d 0d 0a 54 6f 3a |-8?B?cGlu?=..To:|
00000080 20 3d 3f 55 54 46 2d 38 3f 42 3f 51 57 35 6b 63 | =?UTF-8?B?QW5kc|
00000090 73 4f 70 49 46 42 70 63 6d 46 79 5a 41 3d 3d 3f |sOpIFBpcmFyZA==?|
000000a0 3d *0a* 20 3c 41 2e 50 69 72 61 72 64 40 75 6c 67 |=. <A.Pirard@ulg|
000000b0 2e 61 63 2e 62 65 3e 0d 0a |.ac.be>..|

We have now saved a developer 10 minutes by telling that what he will find in the mdnmsg file is that a bare linefeed occurs when an encoded header line is split. We could lose a few more hours trying to find if this occurs only to mdn messages, only to UTF encoding etc... but a developer will make all these findings from the code right away.
I've just counted that in the time I've spent for this bug alone, I would have helped solving 15 bugs at the rate I've just met with another recent report (2 days and 4 hours from bug filing to fix on distribution server).

Thanks to all for the Ubuntu delight and may Ubuntu be with you and with even more people over the years.
Merry Xub^H^Hmas and Happy New Year.

See original description
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

what is the bare lf in the example you attached?

Changed in thunderbird:
status: New → Incomplete
Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Bare lf in mdn message from crashing thunderbird
  • mdnmsg Edit (2.5 KiB, text/plain; name="mdnmsg")
Revision history for this message
André Pirard (a.pirard) wrote : Re: Bare lf in mdn message from crashing thunderbird

"what" is a bare lf is fully explained in the aforementioned http://cr.yp.to/docs/smtplf.html
Just care to open (and read) it.

Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Bare lf in mdn message from crashing thunderbird

This bug is obvious and all proof material has been collected and provided.
It's bee added to this database six months ago.
Since then, it's been visited twice.
Could it be set to confirmed instead of threat of removal in 60 days?
Does Ubuntu really wants to improve?
What's the game?

Revision history for this message
André Pirard (a.pirard) wrote : Re: Bare lf in mdn message from crashing thunderbird

Again, why does this report remain "Incomplete" 10 months after having been introduced and all obvious proofs have been given?
Does Ubuntu really appreciate bug reports?

Revision history for this message
John Vivirito (gnomefreak) wrote :

http://cr.yp.to/docs/smtplf.html does not show a dialog box. can you please give us a screenshot of the problem.
I do not see anything in any of the links that shows us your problem.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Does this happen if you make a new profile with thunderbird-2.0.0.21?
I'm sorry you feel we are not getting to your bugs in a timely manner, however we have from thousands to tens of thousands of bugs to look after we cant get to all in a timely manner.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Thunderbird is not listed http://cr.yp.to/docs/smtplf.html
Can you please file this bug upstream with Mozilla as this is something they need to fix or its msn problem.
We are unable to do this fix since it is not a Ubuntu packaging problem.

Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Bare lf in mdn message from crashing thunderbird

Oh my God.
I sent you the SMTP file that the receiving SMTP server complains with.
That file contains everything a developer needs to spot and correct this
bug.
Reporting bugs to Launchpad is what Ubuntu asks us and it has been done
perfectly.
Could Ubuntu take care of the linking of such reports with so-called
upstream sources?
(while I'm dealing with many other problems)
Ubuntu staff is administratively much more competent than us to do that.
I will of course heartily welcome any e-mail from someone working on
this bug.
I hope I will have spent my time to help Open Software effectively.
Thank you.

Revision history for this message
André Pirard (a.pirard) wrote :

> Does this happen if you make a new profile with thunderbird-2.0.0.21?
>
Wouldn't it be more efficient for the sake of Open Software and
everybody's time that a developer looked at my report, found the mistake
which is very very obvious, made a patch in one hour or so and told us
that it's done, rather than your asking my test of every other
Thunderbird release with a new profile in hope the problem be fixed by
chance?
> I'm sorry you feel we are not getting to your bugs in a timely manner, however we have from thousands to tens of thousands of bugs to look after we cant get to all in a timely manner.
>
Fortunately, you are helped by people like me who spend much time in
analyzing bugs and providing the needed material to either go on with a
fix like in this case or go on with deeper analysis at the request of a
developer.
All that remains to do is 1) believe 2) link to upstream 3) listen to
their fix announcement.
Not even deal with further analysis, which I can do with the developer
ifever he comes.

Revision history for this message
John Vivirito (gnomefreak) wrote : Re: Bare lf in mdn message from crashing thunderbird

Here is a list of upstream bugs that may be related to yours. Can you please take a look and make sure none are yours
https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=mdn

Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Bare lf in mdn message from crashing thunderbird

On 2009-03-21 19:53, John Vivirito wrote :
> http://cr.yp.to/docs/smtplf.html does not show a dialog box.
 That is obviously not the description of the bug.
It's a description of the rule that Thunderbird is violating.
The bug is described in
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/233990
> can you please give us a screenshot of the problem.
>
 Do you need any other shot than the error message I attached in
Screenshot-Alert.png?
Feel free to ask a screenshot of a normally running Thunderbird (before
the crash) and/or of an empty desktop (after the crash), I can make them.
> I do not see anything in any of the links that shows us your problem.
>
 Do you think the 6 messages like this one in the syslog file excerpt I
attached are normal?
> /var/log/kern.log:May 22 12:36:52 daria-ubuntu kernel: [52297.778220]
> thunderbird-bin[27840]: segfault at 4072c00c eip b6e4f6e4 esp bff1cfb0
> error 4
> what is the bare lf in the example you attached?
 A bare linefeed is not a nudist fisher but a LF that is not preceded by
a CR.
In order to find a bare linefeed in the mdnmsg message file I attached,
you need to look inside the file to find it, for example, by doing this :

$ hd mdnmsg
00000000 44 61 74 65 3a 20 54 68 75 2c 20 32 32 20 4d 61 |Date: Thu,
22 Ma|
00000010 79 20 32 30 30 38 20 31 33 3a 31 37 3a 33 35 20 |y 2008
13:17:35 |
00000020 2b 30 32 30 30 0d 0a 46 72 6f 6d 3a 20 41 2e 50
|+0200..From: A.P|
 ... ----- (fully clothed)
000000b0 70 63 6d 46 79 5a 41 3d 3d 3f 3d 0a 20 3c 41 5f
|pcmFyZA==?=. <A_|
 ... -- (bare)

Once again, if you showed my bug description to a developer, he would
not ask all those questions but he would make a patch in less than one
hour. Almost one year ago.
I hope you're in the believing state now.
And that the bug is in the confirmed state.
Thank you.

Revision history for this message
André Pirard (a.pirard) wrote :

On 2009-03-22 14:58, John Vivirito wrote :
> Here is a list of upstream bugs that may be related to yours. Can you please take a look and make sure none are yours
> https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=mdn
>
 I displayed that page.
I set my browser's search to "bare", "lf", "linefeed" and "crash"
successively.
I got no result.
Hoping this will help.

Revision history for this message
Alain EMPAIN (alain-empain) wrote : Re: [Bug 233990] Re: Bare lf in mdn message from crashing thunderbird

> On 2009-03-21 19:53, John Vivirito wrote :
>> http://cr.yp.to/docs/smtplf.html does not show a dialog box.
> That is obviously not the description of the bug.
> It's a description of the rule that Thunderbird is violating.
> The bug is described in
> https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/233990
>> can you please give us a screenshot of the problem.
>>
> Do you need any other shot than the error message I attached in
> Screenshot-Alert.png?
> Feel free to ask a screenshot of a normally running Thunderbird (before
> the crash) and/or of an empty desktop (after the crash), I can make them.
>> I do not see anything in any of the links that shows us your problem.
>>
> Do you think the 6 messages like this one in the syslog file excerpt I
> attached are normal?
>> /var/log/kern.log:May 22 12:36:52 daria-ubuntu kernel: [52297.778220]
>> thunderbird-bin[27840]: segfault at 4072c00c eip b6e4f6e4 esp bff1cfb0
>> error 4
>> what is the bare lf in the example you attached?
> A bare linefeed is not a nudist fisher but a LF that is not preceded by
> a CR.
> In order to find a bare linefeed in the mdnmsg message file I attached,
> you need to look inside the file to find it, for example, by doing this :
>

André,

si ton correspondant n'a pas le sens de l'humour, il va maintenant essayer
de comprendre tes jeux de mots ! Et c'est reparti pour un tour épicé
d'autres blagues qu'il va essayer de décrypter au premier niveau.

Et te demander qu'est ce qu'un nudiste vient faire pêcher ici ;-)

J'ai bien rigolé...

A+

Alain

> $ hd mdnmsg
> 00000000 44 61 74 65 3a 20 54 68 75 2c 20 32 32 20 4d 61 |Date: Thu,
> 22 Ma|
> 00000010 79 20 32 30 30 38 20 31 33 3a 31 37 3a 33 35 20 |y 2008
> 13:17:35 |
> 00000020 2b 30 32 30 30 0d 0a 46 72 6f 6d 3a 20 41 2e 50
> |+0200..From: A.P|
> ... ----- (fully clothed)
> 000000b0 70 63 6d 46 79 5a 41 3d 3d 3f 3d 0a 20 3c 41 5f
> |pcmFyZA==?=. <A_|
> ... -- (bare)
>
> Once again, if you showed my bug description to a developer, he would
> not ask all those questions but he would make a patch in less than one
> hour. Almost one year ago.
> I hope you're in the believing state now.
> And that the bug is in the confirmed state.
> Thank you.
>
>
>

Revision history for this message
Alain EMPAIN (alain-empain) wrote :

> On 2009-03-22 14:58, John Vivirito wrote :
>> Here is a list of upstream bugs that may be related to yours. Can you
>> please take a look and make sure none are yours
>> https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=mdn
>>
> I displayed that page.
> I set my browser's search to "bare", "lf", "linefeed" and "crash"
> successively.
> I got no result.
> Hoping this will help.
>
>
Correction : j'ai toujours trouvé qu'une preuve fondamentale que Billy
était un crétin est qu'il a décidé 'd'habiller' les marqueurs de fin de
ligne comme s'il n'avait pas encore compris que la révolution informatique
avait enterré la machine à écrire et qu'il y avait belle lurette qu'on ne
tournait plus le rouleau ni ne ramenait le charriot au départ de la ligne.

CR-LF = 'La ligne est finie les gars, attention elle est bien finie',
comme si on n'avait pas compris.

Apple a lui bien compris, mais pour varier sur son prédécesseur UNIX a
choisi CR, rien que pour rigoler un peu.

Donc, pas de 'bare LF' vs LF mais LF vs 'dressed LF' ;-)

Alain

Revision history for this message
André Pirard (a.pirard) wrote : Re: Bare lf in mdn message from crashing thunderbird

In hope someone will look at my obvious bug report and confirm it after 1 year, here is another case where the sender didn't get his Receipt.

Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Bare lf in mdn message from crashing thunderbird
  • mdnmsg Edit (4.5 KiB, text/plain; name="mdnmsg")

1) new example attached
2) why don't you reply and does the status remain incomplete?
3) is it really necessary to threaten me with bug expiration (esp in
that case)?
4) does it really help to report bugs?

Revision history for this message
André Pirard (a.pirard) wrote : Re: Bare lf in mdn message from crashing thunderbird

Do you need anything else than those obvious proofs to start considering the problem more than one year after it has been reported?
Could you please stop marking it for expiration? It's frustrating. Thanks.

Matthew Paul Thomas (mpt)
Changed in thunderbird (Ubuntu):
status: Incomplete → New
Aaron C. de Bruyn (darkpixel2k)
Changed in thunderbird (Ubuntu):
status: New → Confirmed
André Pirard (a.pirard)
summary: - Bare lf in mdn message from crashing thunderbird
+ Thunderbird's mdn (receipt) message may contain 822bis-violating bare
+ lf which is rejected by Qmail
description: updated
Revision history for this message
C de-Avillez (hggdh2) wrote :

Well. I got here via André's email to BugSquad. Some comments and requests:

0. Being aggressive does not help. I actually stopped to consider if I should look at it, and eventually (and nevertheless) decided to. But, as far as I can understand, you *did* succeed in getting all involved not really interested in helping. Next time please keep in mind that most of us are *volunteers*. We have no obligation to help.

1. No, it was not clear *where* the problem was (apart from "being in the MDN"). Also, I am pretty sure asac wanted to ask the you 'where' instead of 'what'.

2. I see no reason why I should spend time to search for a bare LF that you did not think important enough to point out, in a file full of characters.

3. Nevertheless I did it. I found (and I did *not* look carefully) one single bare LF, in the initial headers. So, I wonder:

3.1. Can you repeat every time this error?
3.2. Just for grins, could you try again, after changing your email name so that it will not have an accented 'e'? This is an area where I have seen a lot of issues in the past, and I am curious.
3.3. finally what is your current Thunderbird version? Full version string, please.

4. Finally, no, I do not run Thunderbird, nor QMail. I am not interested in running either (even though usually anything written by DJ Berstein is really good).

Revision history for this message
C de-Avillez (hggdh2) wrote :

Interesting. Your last example does not show a bare LF anywhere I can see. But I *do* see a bare CR, at the very last line.

André Pirard (a.pirard)
description: updated
description: updated
Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Thunderbird's mdn (receipt) message may contain 822bis-violating bare lf which is rejected by Qmail
  • unnamed Edit (2.8 KiB, multipart/report; report-type=disposition-notification; boundary="------------mdn050009040207090709060809")
  • unnamed Edit (2.8 KiB, multipart/report; report-type=disposition-notification; boundary="------------mdn050009040207090709060809")
  • unnamed Edit (4.7 KiB, multipart/report; report-type=disposition-notification; boundary="------------mdn000103090409050306010000")
  • unnamed Edit (5.4 KiB, multipart/report; report-type=disposition-notification; boundary="------------mdn080405030608030201070102")
  • unnamed Edit (3.6 KiB, multipart/report; report-type=disposition-notification; boundary="------------mdn080809020004040603000607")
  • unnamed Edit (2.8 KiB, multipart/report; report-type=disposition-notification; boundary="------------mdn050908010905040300030000")
Download full text (4.4 KiB)

Thanks to Aaron for setting this bug to /confirmed/ at last.

On 2009-12-03 02:54, C de-Avillez wrote :
> Well. I got here via André's email to BugSquad. Some comments and
> requests:
 Thanks for coming, C.
> 0. Being aggressive does not help.
 I'm not aggressive at all.
I'm very calmly coming back from solving another bug with a developer.
*2 days 4 hours* from my filing the bug to his fix *in the distribution*.
We did a great job and we waved a see you back.
I horribly feel like losing my time with this case in comparison.
I counted I could have solved 15 bugs at the other one's rate instead.
> I actually stopped to consider if I
> should look at it, and eventually (and nevertheless) decided to.
 Yes, I know that feeling exactly.
It hit me a dozen times along those 1 1/2 year for this bug alone.
> But, as
> far as I can understand, you *did* succeed in getting all involved not
> really interested in helping. Next time please keep in mind that most of
> us are *volunteers*. We have no obligation to help.
 Thanks again.
Correct. I am a volunteer having no obligation to help Ubuntu.
I do it because I love Ubuntu and I hate hearing speak about its bugs.
And I help many people using it. Very busy.
Nobody's obliged to think alike. Not even to thank me.
> 1. No, it was not clear *where* the problem was (apart from "being in
> the MDN"). Also, I am pretty sure asac wanted to ask the you 'where'
> instead of 'what'.
 I have answered all your questions only by taking data out of the mdnmsg
files.
A Thunderbird developer needs nothing more than it & the Qmail's error
message.
That's what I'm saying since 1 1/2 years.
> 2. I see no reason why I should spend time to search for a bare LF that
> you did not think important enough to point out, in a file full of
> characters.
 You should not.
You should believe D. J. Bernstein <http://cr.yp.to/djb.html> that there
*is* one.
There should *never* be a bare linefeed in SMTP transmission.
Hence, if there is one, it *must* be a bug.
It's *only* the developer's concern *where *that bare lf is.
If I meet a dev like the one I just left, he may find questions to ask me.
Questions he only knows.
But I even doubt there's any question to ask.
Because every information is in the mdnmsg files.
I'm all his for testing fixes, of course, like I tested it lately.
> 3. Nevertheless I did it. I found (and I did *not* look carefully) one
> single bare LF, in the initial headers. So, I wonder:
 Because it looks all so difficult, I have
1) uploaded numbered versions of the files so that we don't get all mixed up
2) run a grep command on them
3) washed my sins away by following the reporting instructions exactly
4) updated the bug description with the above
> 3.1. Can you repeat every time this error?
 Yes. It happened many more than shown, of which 4 descriptions were
uploaded.
One more, and file #5 is a bare case replayable at will.
You can even send me an e-mail like cases 2, 3 and 4 and I'll return you
the mdnmsg file.
So that you may upload one with your own name in it ;-)
> 3.2. Just for grins, could you try again, after changing your email
> name so that it will not have an accented 'e'? This is an area where I
> have...

Read more...

Revision history for this message
André Pirard (a.pirard) wrote :

My goodness.
I attached numbered files to my message.
To be clear.
As follows.

Content-Type: message/rfc822;
 name="mdnmsg0.eml"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="mdnmsg0.eml"

And it didn't find the name !!!
And most probably shuffled them.

Please someone file a bug.
Not me, sorry.

Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :

Thank you. Again, I ask you:

3.1. Can you repeat every time this error?

3.2. Just for grins, could you try again, after changing your email name so that it will not have an accented 'e'? This is an area where I have seen a lot of issues in the past, and I am curious.

To make it clearer: instead of 'André Pirard', 'Andre Pirard'. Note there is no acute accent (or *any* accented letter at all).

3.3. finally what is your current Thunderbird version? Full version string, please.

Actually, just paste here the output of 'apt-cache policy thunderbird' (or whatever is your Thunderbird package name).

Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :

On 2009-12-13 17:55, C de-Avillez wrote :
> Thank you. Again, I ask you:

I have answered all those questions before and the answers are stored at
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/233990/comments/22

Could you PLEASE PLEASE try to understand that you can send me *any*
test mail you want.
I will ack the Return Receipt request and you will :

    * either receive the Return Receipt if it worked
    * or receive the mdnmsg file with a bare linefeed I will send you

> 2. I see no reason why I should spend time to search for a bare LF that
> you did not think important enough to point out, in a file full of
> characters.
Must I also send you the result of the grep command on those files I'll
send you?
> Actually, just paste here the output of 'apt-cache policy thunderbird'
> (or whatever is your Thunderbird package name).
$ apt-cache policy thunderbird
thunderbird:
  Installed: 2.0.0.21+nobinonly-0ubuntu0.8.10.1
  Candidate: 2.0.0.23+build1+nobinonly-0ubuntu0.8.10.1
  Version table:
     2.0.0.23+build1+nobinonly-0ubuntu0.8.10.1 0
        500 http://ubuntu.mirrors.skynet.be intrepid-updates/main Packages
        500 http://security.ubuntu.com intrepid-security/main Packages
 *** 2.0.0.21+nobinonly-0ubuntu0.8.10.1 0
        100 /var/lib/dpkg/status
     2.0.0.17+nobinonly-0ubuntu1 0
        500 http://ubuntu.mirrors.skynet.be intrepid/main Packages

As ma previous answer looks very ugly on site, I stored the html
version html_answer.eml.

Thanks.

André.

> 3.1. Can you repeat every time this error?
>
> 3.2. Just for grins, could you try again, after changing your email name
> so that it will not have an accented 'e'? This is an area where I have
> seen a lot of issues in the past, and I am curious.
>
> To make it clearer: instead of 'André Pirard', 'Andre Pirard'. Note
> there is no acute accent (or *any* accented letter at all).
>
> 3.3. finally what is your current Thunderbird version? Full version
> string, please.
>
> Actually, just paste here the output of 'apt-cache policy thunderbird'
> (or whatever is your Thunderbird package name).

Revision history for this message
C de-Avillez (hggdh2) wrote :

<SystemCleanup>
Some pout-pourri on previous comments:

> There should *never* be a bare linefeed in SMTP transmission.
> Hence, if there is one, it *must* be a bug.

I do not remember stating anything else. And, yes, I do know the requirements in the RFCs.

> It's *only* the developer's concern *where *that bare lf is.

Pretty much all that *tried* to work with you are -- gasp! -- developers. Still, you threw them all away.

> If I meet a dev like the one I just left, he may find questions to ask me.
> Questions he only knows.

Indeed. Since now I know I am not a developer, I guess I should not try to ask you any questions. Even those that only I know.

> As ma previous answer looks very ugly on site, I stored the html
> version html_answer.eml.

Oh, you finally noticed, good. I thought, until now, that I was the only one (and, probably, indeed, was).

</SystemCleanup>

Now, back to business.

I did send an email with a MDN request to André, and -- guess what? -- I got my MDN. As I very much expected, by the way. I was already suspecting the UTF-8 encoding in the headers (of André's name) as the cause but, unfortunately, André was unable to understand it.

Ah well.

So now we know where it happens, and how to workaround the issue meanwhile. I will even go ahead and test it on TB3, just for grins.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Does not seem to happen on TB3. All lines of the MDN seem to be correctly terminated.

Revision history for this message
In , C de-Avillez (hggdh2) wrote :

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7pre) Gecko/20091215 Ubuntu/9.10 (karmic) Shiretoko/3.5.7pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7pre) Gecko/20091214 Shredder/3.0.1pre

Original Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/233990

Tested on TB 3.0.1pre1 and TB 2.0.0.23.

When a MDN (return receipt) is sent, the UTF-8 encoding of the 'To:' address is inserted with a bare LF at the end.

This breaks RFC822. Although not all SMTP servers are picky, at least QMail refuses to send the message.

This does not happen if the display name of the email address can be represented in ASCII.

For example, the following is an excerpt of a sniffer trace ran on a SMTP session, showing the error:

00b0 6d 3e 0d 0a 53 75 62 6a 65 63 74 3a 20 52 65 74 m>..Subject: Ret
00c0 75 72 6e 20 52 65 63 65 69 70 74 20 28 64 69 73 urn Receipt (dis
00d0 70 6c 61 79 65 64 29 20 2d 20 74 65 73 74 20 4d played) - test M
00e0 44 4e 20 35 20 54 42 33 0d 0a 54 6f 3a 20 3d 3f DN 5 TB3..To: =?
00f0 55 54 46 2d 38 3f 42 3f 55 32 46 75 64 4d 4f 70 UTF-8?B?U2FudMOp
0100 49 47 52 6c 4c 55 46 32 61 57 78 73 5a 58 6f 3d IGRlLUF2aWxsZXo=
0110 3f 3d *0a* 20 3c 68 67 67 64 68 32 40 75 62 75 6e ?=. <hggdh2@ubun
0120 74 75 2e 63 6f 6d 3e 0d 0a 52 65 66 65 72 65 6e tu.com>..Referen

Note offset 0x111 and 0x112 -- a bare LF is there, in between the UTF-8 encoding and the email address.
This is the UTF-8 for 'Santé...". The encoding is still inserting a bare LF in the stream.

Reproducible: Always

Steps to Reproduce:
1. Set up your display name with accented characters, say "Liberté Equalité Fraternité", or "Ócio", or similar.
2. send an email to somebody else, setting Return Receipt
3. look at/sniff/whatever the actual SMTP stream (unfortunately it seems TB does not save the sent MDN -- or, at least, I cannot find it in my folders).
4. If the recipient of the MDN request is running under QMail, perfect, you will be able to see the QMail error.
Actual Results:
UTF-8 encoding of MDN inserts a bare LF in the stream

Expected Results:
either a CRLF is inserted, or no bare LF.

Revision history for this message
In , C de-Avillez (hggdh2) wrote :

Actually this affects other encodings as well. The Ubuntu original bug is encoding to ISO-8859*

Revision history for this message
C de-Avillez (hggdh2) wrote :

No, it does not work on TB3:

00b0 6d 3e 0d 0a 53 75 62 6a 65 63 74 3a 20 52 65 74 m>..Subject: Ret
00c0 75 72 6e 20 52 65 63 65 69 70 74 20 28 64 69 73 urn Receipt (dis
00d0 70 6c 61 79 65 64 29 20 2d 20 74 65 73 74 20 4d played) - test M
00e0 44 4e 20 35 20 54 42 33 0d 0a 54 6f 3a 20 3d 3f DN 5 TB3..To: =?
00f0 55 54 46 2d 38 3f 42 3f 55 32 46 75 64 4d 4f 70 UTF-8?B?U2FudMOp
0100 49 47 52 6c 4c 55 46 32 61 57 78 73 5a 58 6f 3d IGRlLUF2aWxsZXo=
0110 3f 3d *0a* 20 3c 68 67 67 64 68 32 40 75 62 75 6e ?=. <hggdh2@ubun
0120 74 75 2e 63 6f 6d 3e 0d 0a 52 65 66 65 72 65 6e tu.com>..Referen

This is the UTF-8 for 'Santé...". The encoding is still inserting a bare LF in the stream.

C de-Avillez (hggdh2)
description: updated
Changed in thunderbird (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Bug Watch Updater (bug-watch-updater)
Changed in thunderbird:
status: Unknown → New
Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Thunderbird's mdn (receipt) message may contain 822bis-violating bare lf which is rejected by Qmail
Download full text (4.5 KiB)

On 2009-12-15 00:36, C de-Avillez wrote :
> <SystemCleanup>
> Some pout-pourri on previous comments:
>
>> There should *never* be a bare linefeed in SMTP transmission.
>> Hence, if there is one, it *must* be a bug.
>>
>
> I do not remember stating anything else. And, yes, I do know the
> requirements in the RFCs.
>

I never said that you stated anything else.
What I'm saying is that there's no reason to try to prove we are facing
a bug.
The perfect proof of it is contained within one single file.
Please send it where the bug will be fixed.

>> It's *only* the developer's concern *where *that bare lf is.
>>
>
> Pretty much all that *tried* to work with you are -- gasp! --
> developers. Still, you threw them all away.
>
Are you saying that bringing in a perfect bug report is throwing people
away?

In addition, I very calmly replied developers' unnecessary questions, like :
> http://cr.yp.to/docs/smtplf.html <http://cr.yp.to/docs/smtplf.html>
> does not show a dialog box.
 There shouldn't be a dialog box in D. J. Bernstein's explanation of what
a bare linefeed is.
> can you please give us a screenshot of the problem.
 I already sent you a screenshot in file Screenshot-Alert.png

> Thunderbird is not listed http://cr.yp.to/docs/smtplf.html
> <http://cr.yp.to/docs/smtplf.html>
Are you asking me to ask D. J. Bernstein's to add it?

> I do not see anything in any of the links that shows us your problem.
It's not in a link, it's in the mdnmsg file (fourth time) and
Screenshot-Alert.png

etc...
>
>> As ma previous answer looks very ugly on site, I stored the html
>> version html_answer.eml.
>
> Oh, you finally noticed, good. I thought, until now, that I was the only
> one (and, probably, indeed, was).
>
 Not my fault if the text version of my e-mail was stored instead of the
html one.
You may open a bug if you don't like what they're doing.

> </SystemCleanup>
>
> Now, back to business.
>
> I did send an email with a MDN request to André, and -- guess what? -- I
> got my MDN. As I very much expected, by the way. I was already
> suspecting the UTF-8 encoding in the headers (of André's name) as the
> cause but, unfortunately, André was unable to understand it.
>
Ah, and now *I* don't understand. That's the best yet ...
It's seems that *you* are unable to understand what I have written in
the bug's description :
> We have now saved a developer 1 minute by telling that what he will
> find in the mdnmsg file is that a bare linefeed occurs when an encoded
> header line is split. We could lose a few more hours trying to find if
> this occurs only to mdn messages, only to UTF encoding etc... but a
> developer will make all these findings from the code right away.

It's perfectly stupid to Say that "the UTF-8 encoding in the headers (of
André's name)" is the cause of the following bare linefeed case

> $ grep -P '[^\r]\n' mdnmsg3.eml | tee /dev/tty | hd
> Subject: Return Receipt (displayed) - =?ISO-8859-
>
> 1?Q?Re:_WiFi_=28liaison_de_donn=E9es_par_radio=29_pou?=
> =?ISO-8859-1?Q?r_Th=E9r=E8se,_3*20?=
>
First, that's not UTF-8 encoding but ISO-8859-1
and second, that's not my name in it but of my sister Thérèse.
Moreov...

Read more...

Revision history for this message
C de-Avillez (hggdh2) wrote :

Andre: please add your comments upstream. There is nothing else to be done here.

Revision history for this message
In , M-wada (m-wada) wrote :

On MS Win, inserted bytes was CRLF(0x0D0A) instead of LF.
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091129 Shredder/3.0.1pre

Original From: in mail with MDN=on. ({CRLF}==0x0D0A)
> From: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?= <email address hidden>{CRLF}
 Tb3 generated following To: in return receipt.
> To: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?={CRLF}
> <email address hidden>{CRLF}
 In this case, RFC2822 violation doesn't happen fortunately.

Inserted byte(s) looks "new line" used by OS.

Revision history for this message
In , A-pirard-hotmail (a-pirard-hotmail) wrote :

From the original bug reporter :

I attached to the aforementioned bug 233990 launchpad URL a number of self-explanatory eml files which are captures of the MDN message Thunderbird was trying to send when Qmail complained with bare linefeed. The URL itself contains grep output showing the bare linefeed.

Notice that the bare linefeed bug does not only affect the To: line but also the Subject: line.
It is a rare everyday-use event, although
- I cannot know how many of the e-mails I sent could not be acknowledged because of this
- I use a special configuration with which sending from my Thunderbird hotmail account to my Thunderbird ulg account can repeatedly be done with RR. Several of the eml files use that feature to test and demonstrate the problem (esp on the subject line).

André.

Revision history for this message
In , A-pirard-hotmail (a-pirard-hotmail) wrote :

WADA,

The original description says that there *may* be a bare linefeed in Return Receipt without saying where (seen in From and in Subject) nor why. It provides eml files for someone to find out why by analyzing them under light of the code. The ultimate reason will be known after that analysis.

If you want to reproduce the problem without analyzing first and if you don't succeed, you may want to find inspiration in these eml files from what really happened for sure.

I'm not sure what you're showing us (a From: and a To:).
Sending? Received? Return Receipt? Normal Mail?
Please provide full files showing everything you did, like mine do.

It wouldn't be surprising that the problem did not exist on Windows, because EOL is CRLF on Windows and LF on Linux. This is a Linux Thunderbird bug.

Revision history for this message
In , M-wada (m-wada) wrote :

Created an attachment (id=417890)
mail folder file

Attached mail folder file:
  mail-1 : Sent mail.
           Generated by Sm2 and Subject: is manually crafted.
           - Sm2 puts each rfc2047 encoded word in single header line.
           - Two header lines are merged into single herader line manually.
  mail-2 : Return receipt by Tb 3 on MS Win.

(In reply to comment #4)
> I'm not sure what you're showing us (a From: and a To:).
> Sending? Received? Return Receipt? Normal Mail?
> Please provide full files showing everything you did, like mine do.

You can't understand next?
> Original From: in mail with MDN=on. ({CRLF}==0x0D0A)
> (a) > From: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?= <email address hidden>{CRLF}
> Tb3 generated following To: in return receipt.
> (b) > To: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?={CRLF}
> > <email address hidden>{CRLF}

1. Some one(Tb, Seamonkey) sends a mail with From: of (a),
   with requesting return receipt.
2. Tb 3 receives the mail, and sent return receipt according to MDN request.
3. To: in the "return receipt sent by Tb3" was (b).
   {CRLF} was inserted at same position as {LF} in comment #0.

> It wouldn't be surprising that the problem did not exist on Windows, because
> EOL is CRLF on Windows and LF on Linux. This is a Linux Thunderbird bug.

Problem does exist in Tb 3 on MS Win too. {CRLF} was surely inserted by Tb 3.
On MS Win, inserted bytes was {CRLF}. So RFC2822 violation won't occur fortunately.
"unneeded folding of To:" was observed on MS Win too.
As From: (by Tb, Seamonly) is following,
> From: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?= <email address hidden>
 next is sufficient for To: of "return receipt"(shorter than the From:).
> To: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?= <email address hidden>
 Similar "folding after each RFC2047 encoded word" is also observed for Subject: header.
See attached mail folder data.

I guess that problem is "new line of OS is inserted upon header folding by Tb on any OS" instead of "Tb on Linux only inserts bare LF wrongly".
And, I guess the header folding is for avoiding RFC violation(e.g. too long header generated by original mail sender).
I think attached mail data indicates;
  Tb folds mail header after each rfc2047 encoded word.

Revision history for this message
In , M-wada (m-wada) wrote :

Oh, RFC2822 violation existed in return receipt produced by Tb3 on MS Win too.
  - spase only line in Subject: (space+{CRLF} line, fortunately I added a space)
  - {CRLF} only lines in Subject: => Mail header terminates at there
    original Subject : word-1 word-2{CRLF}
    after try to fold : word-1{CRLF} ({CRLF} is inserted)
                        word-2{CRLF} ({CRLF} is inserted)
                        {CRLF}

Revision history for this message
In , A-pirard-hotmail (a-pirard-hotmail) wrote :

I may come too late, but, I have added a more doable "Alternative, steps to reproduce" to launchpad description.
I have also added 4 msdnmsgN(f+s).eml samples, where f=1=From failure
and s=2:Subject failure

Please note msdnmsgN2.eml follows the proposed workaround but fails.
Do not overlook the Subject: line case

> You can't understand next?
I was wondering if the From belonged to the original mail or the RR.
Beware that the To: line of the RR comes from
Disposition-Notification-To: Wada Mitsuhiro <email address hidden>
not From: ...

I wonder why, being on Qmail and with an accent in my From:,
I haven't met the problem more often.

Thanks Wada, I had told Ubuntu that you would be fast and you are.

Revision history for this message
In , M-wada (m-wada) wrote :

André Pirard, sorry for my wrong comment.
I based on From:==Disposition-Notification-To: in my test.
I should have correctly presented next data instead of From: data.
> Disposition-Notification-To: =?ISO-2022-JP?B?GyRCT0JFRDh3OTAbKEI=?={CRLF}
> <email address hidden>
 Note: I used next in crated Subject: test(attached mail data).
      Sorry for my confusing/mis-leading comments/data.
> Disposition-Notification-To: Wada Mitsuhiro <email address hidden>

Revision history for this message
In , A-pirard-hotmail (a-pirard-hotmail) wrote :

問題ありません。 カワ
ありがとうございました

André Pirard (a.pirard)
description: updated
description: updated
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote :
Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 233990] Re: Thunderbird's mdn (receipt) message may contain 822bis-violating bare lf which is rejected by Qmail

On 2009-12-15 16:39, C de-Avillez wrote :

 > ** Bug watch added: Mozilla Bugzilla #534885
 > https://bugzilla.mozilla.org/show_bug.cgi?id=534885

Thanks a lot.

I have added a more affordable "Alternative, steps to reproduce" to
launchpad description.
I have also added 4 msdnmsgN(f+s).eml samples, where f=1=From failure
and s=2:Subject failure

Please note that msdnmsgN2.eml follows the proposed workaround but fails.

 > +
 > + WORKAROUND: Do not use accented characters on the email's display name.
 > +

The workaround must add "speak English" in the Subject lines or not use
Qmail or even not use Return Receipts, because...

As I mentioned it before, no local "display name" configuration changes
the way the Return Receipt is sent for an incoming message (that was
written by somebody else) like mdnmsg2.eml and mdnmsg3.eml.

As I mentioned it before, no local "display name" configuration changes
the way the Return Receipt is sent when the error is in the Subject
line, like mdnmsg2.eml, mdnmsg3.eml and mdnmsg4.eml.

One cannot decently ask people who use accented letters or their own
alphabet like Cyrillic, Greek or Arabic to change their name and to stop
writing Subject lines in their own language because of a Thunderbird bug.

That's easy to understand
The best would be to remove the WORKARAUND and speed up a fix.

André Pirard (a.pirard)
description: updated
Bug Watch Updater (bug-watch-updater)
Changed in thunderbird:
importance: Unknown → Medium
Bug Watch Updater (bug-watch-updater)
Changed in thunderbird:
importance: Medium → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.