Closed Bug 445742 Opened 17 years ago Closed 17 years ago

An odd space in the text of received message

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bernard.thoorens, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 Build Identifier: version 2.0.0.14 (20080421) there are 2 unexpected spaces in the text of the message received : Un commercial efficace pour v otre business ! (v space otre) and Pour acqu&eac ute;rir un commercial efficace et obtenir plus d'informations : (acqué space rir) Reproducible: Always Steps to Reproduce: 1. an ad message composed with an HTML editor, sent to me as a test before mass-mailing 2. this message appears in thunderbird with two spaces in the text 3. sent as a mass-mailing: the same problem appears 4. received in Gmail, result: doesn't bug Actual Results: The text as it appears in TB window (copied-pasted from TB window): "Un commercial efficace pour v otre business !" but the source code is correct: "Un commercial efficace pour votre business&nbsp;!" A second space appears in the text: "Pour acqu&eac ute;rir un commercial efficace et obtenir plus d'informations :" and the source is: "<p>Pour acqu&eac ute;rir un commercial efficace et obtenir plus d'informations&nbsp;:<br />..." Expected Results: no spaces in the read text when not written if you want to see a hard copy or the forwarded message, don't hesitate to ask me, it will be with pleasure bernard.thoorens@ventsolaire.net
> 3. sent as a mass-mailing: the same problem appears > 4. received in Gmail, result: doesn't bug Sounds like your mailing-list software or smtp server does something it shouldn't. Are the odd space in the copy of the mail in your sent folder?
no
Then it's not thunderbird, but some server along the way that modifies it incorrectly. ->INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.