Closed
Bug 280175
Opened 20 years ago
Closed 19 years ago
Problem sending mail in offline mode to recipient with accents in his name
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: michal-bugzilla, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0
Build Identifier: Thunderbird 1.0 (20041207) for Linux
In my setup I use LANG=cs_CZ system-wide, and compose messages in
ISO-8859-2 (Central European). Normally this works fine, but
when I compose a mail in offline mode to an address where the
recipient name contains some accented letters (e.g. to "Michál
<mludvig@localhost>"), send it via "Send Later", then exit Thunderbird
and next time, when going on-line and sending the queued messages
I get an error:
| An error occured while sending mail. The server responded: Bad
| address syntax.
I did some tests with my local postfix server and realised that
Thunderbird sends this wrong SMTP command:
RCPT TO:<"Mich?l<mludvig\"@localhost>">
Indeed there should be only:
RCPT TO:<mludvig@localhost>
All this happens only when I compose message to someone with some
specific accents in their name in offline mode, queue for sending
later and then exit thunderbird. Direct sending from online mode works
in all cases as well as does offline sending to addresses without
accents (e.g. to "Michal <mludvig@localhost>" it works in offline as
well). It also works when I don't exit Thunderbird before going
online.
The "problematic accents" include e.g. á (á) and í (í),
OTOH some other work fine, e.g. ž or ř
Reproducible: Always
Steps to Reproduce:
1. Go off-line in thunderbird
2. Compose message to "Michál <someone@somewhere>"
3. "Send later"
4. Exit Thbird.
5. Run Thbird
6. Go online and send messages.
Actual Results:
Message box:
| An error occured while sending mail. The server responded: Bad
| address syntax.
Expected Results:
Messages being sent
Happens at least on SuSE Linux 9.2 with LANG=cs_CZ
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•