276333 - email address processed differently when sent from the outbox folder and from the compose window

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: SMTP, defect)

Description

[:aceman]

I have an email address that causes permanent problems when sending a message to it.

I received this address in a message in the form:
From: Xxxxx =?ISO-8859-1?Q?Yyyyyyyy=FD?= <[e-mail]>
- is that correct syntax? The sending useragent was Mozilla 0.9.7 :)

When replying to that mail, the address is changed by Mozilla to:
To: =?ISO-8859-1?Q?Xxxxx_Yyyyyyyy=FD?= <[e-mail]>

When sending this out, the problem appears:

When sending the message from the Outbox folder, the SMTP communicatoin is as
follows:
0[771e20]: SMTP Send: RCPT TO:<"XxxxxYyyyyyyyý<uuuu\"@ddddddd.ss>">

0[771e20]: SMTP entering state: 0
0[771e20]: SMTP Response: 513 Syntax error.

Then the message is 'edited as new', and immediatelly sent (with no changes)
from the compose window, the SMTP communication is as follows:
0[771e20]: SMTP Send: RCPT TO:<[e-mail]>

0[771e20]: SMTP entering state: 0
0[771e20]: SMTP Response: 250 Ok.

So, is the SMTP communication different, or was the recipient address
changed in the subsequent editation? But the mail was originally created in the
same compose (reply) dialog, so the address processing should be the same.

The real address was censored, I hope it doesn't break the test case :)

Comment 1

[Mike Cowperthwaite]

Which version of Mozilla are you seeing this in?  The bug is filed against the 
1.7 branch -- are you seeing this in 1.7.5?  Is it *new* in 1.7.5 or has it been 
seen in earlier versions?  What about in 1.8a builds?  Thunderbird?

I'm unable to reproduce this problem with 1.7.5, Win2K.



(In reply to comment #0)
> I received this address in a message in the form:
> From: Xxxxx =?ISO-8859-1?Q?Yyyyyyyy=FD?= <[e-mail]>
> - is that correct syntax? The sending useragent was Mozilla 0.9.7 :)

Yes, that's valid.

> When replying to that mail, the address is changed by Mozilla to:
> To: =?ISO-8859-1?Q?Xxxxx_Yyyyyyyy=FD?= <[e-mail]>

Also valid, more or less the same thing.

Comment 2

[:aceman]

I can see it in 1.7.3 and below, but I don't know when it appeared. But it was
in 1.5 and 1.6. I will test 1.7.5 soon, but I can't check 1.8 (until final) or
thunderbird.

Comment 3

[Gervase Markham [:gerv]]

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 4

[Gervase Markham [:gerv]]

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.

Comment 5

[:aceman]

Still there in seamonkey 1.0.2.

Comment 6

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 7

[:aceman]

I can no longer reproduce the bug with the testcase provided by me. In seamonkey 1.1.2. Simultaneously, I tested it again on mozilla 1.7.x with the same testemail. The problem appears there (the same PC and mailserver). Closing for now...