Closed Bug 1025879 Opened 11 years ago Closed 11 years ago

Email subjects >61 characters in length prefixed with "********: " after sending

Categories

(MailNews Core :: MIME, defect)

x86_64
Windows 8.1
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1022723

People

(Reporter: emorley, Unassigned)

Details

(Keywords: regression)

STR: 1) Compose a new email with a subject of >62 characters length (body can be blank, pick any recipient). 2) Send email. 3) Look in sent items for the email. Expected: The subject of the email in sent items matches that chosen in #1. Actual: The subject is that from #1, but with a prefix of "********: " eg: With a subject of "nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn" Message-ID: <539EE4DB.3020200@mozilla.com> Date: Mon, 16 Jun 2014 13:36:43 +0100 From: Ed Morley <emorley@~snip~> Organization: Mozilla User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Thunderbird/33.0a1 MIME-Version: 1.0 To: emorley@~snip~ Subject: ********: nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Additional info: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Thunderbird/33.0a1 Application Build ID 20140615030201 Built from https://hg.mozilla.org/mozilla-central/rev/a6a457fe2a2a Previously used the 'Thunderbird Conversations' addon, but this repos with it disabled. First seen when sending an email on 11th June, and I successfully sent a long-subject email on the 9th June - however Daily may have been a day or so behind, depending on when it last updated. KaiRo also had this happen to him using SeaMonkey (on 9th June), which is why I'm filing this in mailnews core.
I was going to try using mozregression, but: $ mozregression --app=thunderbird --good=2014-06-06 --bad=2014-06-11 No builds available for 64 bit Windows (try specifying --bits=32) Exception AttributeError: "'ThunderbirdNightly' object has no attribute 'persist'" in <bound method ThunderbirdNightly.cleanup of <mozregression.runnightly.ThunderbirdNightly object at 0x02F57370>> ignored
For regression range: 6/4 I sent a very long subject correctly, 6/9 the stability mtg invite had the bug. I usually rebuild my SeaMonkey daily, so on 6/9 my build probably had code checked in up to around noon Central European Time, while Ed's Daily might have had code from earlier that night or the night before. I would have suspected work like bug 858337 or bug 790855, which landed on 6/4, though. Still, I don't see any landings on c-c between that and 6/9 that would obviously jump out to affect this, so I still bet on Joshua's changes to have caused/triggered this bug.
Doh, in the console the exception masked the real message & suggested param change. Filed bug 1025887 to against mozregression to catch that exception. However I then got another, for which I've filed bug 1025892.
for me, it happens at >61 characters, not >62
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
I forgot to remove 1 from the column number in my editor :-)
Summary: Email subjects >62 characters in length prefixed with "********: " after sending → Email subjects >61 characters in length prefixed with "********: " after sending
You need to log in before you can comment on or make changes to this bug.