Closed Bug 408556 Opened 17 years ago Closed 17 years ago

replying or forwarding mails from outlook clients removes thread view and adds useless strings to subject line

Categories

(Thunderbird :: Message Compose Window, defect)

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 194788

People

(Reporter: mozillabugs, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071204 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11 Build Identifier: Thunderbird Version 2.0.0.6 (20071022) - ubuntu Linux 7.10 and 2.0.0.9 on MacOSX When replying to mails sent from localized mailers thunderbird adds Re: after the localized version of the "Re" thus leading to subject lines such as: "Re: AW: AW: something in subject" This destroy the threaded message view if the mail is replied again leading to "AW: Re: AW: AW: something in subject" Same happens with forwarded messages that were forwarded to me giving a subject such as "Fwd: WG: Re: something". Reproducible: Always Steps to Reproduce: 1. Reply or forward an email from a Microsoft Outlook/Exchange/Novell client that doesn't use Re: Fwd: but localized versions such as AW: (german reply), WG: (german Fwd) Expected Results: Replying to mails in threaded view should strip the subject line to contain only one Re: flag. "AW: AW: something in subject" will become "Re: something in subject" thus preserving the possibility to view all related messages in a threaded view. The same should apply to forwarded messages: "Fwd: WG: Re: something" will become "Fwd: Re: something". Maybe this problem arises with all localized versions and can be solved by adding a locale specific list of Re:/Fwd:-synonyms to be replaced automatically when replying or forwarding messages.
For reply, set mailnews.localizedRe to a comma separated list of localized prefixes. Bug 319037 is about providing a default list for this. For forward, no luck yet, it's bug 194788.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.