Closed Bug 17179 Opened 25 years ago Closed 25 years ago

[dogfood] [BLOCKER] Sending a message does not work

Categories

(MailNews Core :: Backend, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nbaca, Assigned: jefft)

Details

Build 1999102509 M11: Win32/NT4

Overview: I can compose a message and it appears to send it because the compose
window disappears but the message is never recieved.

Additional Information:
- I tried receiving the message using 4.7 and it never arrived.
- I tried receiving the message using 5.0 and it never arrived.
- Using the 10/18 build I was able to send a message

I will investigate further.
Assignee: phil → mscott
Assigning to mscott per lisa's suggestion.
I just tried this out on a linux build from Saturday and send mail is working
fine.

I'll grab a release build today for windows and try it out too.
Severity: normal → blocker
Component: Front End → Back End
Thanks, Scott.
This works for me on today's windows builds too (10/25).
I believe the problems she's having stem from the pref migration problems she's

having as well.

nbaca, can you mark this as a duplicate of the profile migration bug when you
file it? I'm thinking that' the source of your problems.
Scott - marina in int'l QA also is having this problem.
Win_nt 4.0 (1999-10-25-09 M11)
I did not migrate using this build. I compose and send both on POP and IMAP
using plain text and Html editor. Send works and receives fine.
Hmm.  Well, I just installed today's win32 apprunner on my NT box (freshly
installed less than two weeks ago, first installation of apprunner on it), I
created a new profile, started up mail, did the initial mail setup, tried to
send a new message and while it appeared to work, I still haven't received it
yet (in 4.7).
This worked for me as long as I didn't create a new profile by
throwing away the mozregistry.dat. But once I threw away the
mozregustry.dat, I got this error notification from my server:

===================================
This Message was undeliverable due to the following reason:

The following destination addresses were unknown (please check
the addresses and re-mail the message):

SMTP </momoi3@kaze.mcom.com>

Please reply to Postmaster@kaze.mcom.com
if you feel this message to be in error.

==========================================

Note the "/" we are inserting.
Ahhh excellent catch Kat. I believe this problem may have been introduced by
some changes from jefft for Bug #11892. Adding him to the cc list. That seems
to be the only code that changed between Friday and today involving the sender's
name for outgoing mail.
the tree is being held closed for this bug.
Summary: Sending a message does not work → [BLOCKER] Sending a message does not work
Here are two possible workarounds. Still investigating:
1. If you address the message "To" someone and "Cc" a second person then the
message is received by the person Cc'd. Note: The "To" person does not receive
the messsage.
2. Instead of typing the full email address let the application perform
auto-complete. This works for Fenella
Win_nt 4.0 (1999-10-25-09 M11)
The send works for me when I use auto-complete. But if I type the full email Id
in the To: field, I get the Mail System Error-Return Mail. And the receipient
name is added a "/" in front of it. And mail was not sent.
Summary: [BLOCKER] Sending a message does not work → [dogfood] [BLOCKER] Sending a message does not work
It looks like there a problem with auto-complete: in today's build i just typed
in the "To" field : iqatest1 relying on the auto-complete without hitting
"Enter" to go to the "Subject" fieldd (it was working in the Friday's build) but
not today (you have to type "iqatest1" and then hit enter,you'll receive this
mail). If you do not hit enter after you type the addressee (assuming it adds
the "netscape.com" domain) it does it in a wrong way and all you'll get will be
Mailsending error
Assignee: mscott → jefft
Jefft has the fix for this. Re-assigning to him. Since they just reclosed the
tree for some Mac problems we're going to go ahead and check this fix in before
it re-opens.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fix checked in. nsMsgSend.cpp , nsSmtpUrl.cpp modified.
Status: RESOLVED → VERIFIED
Build 1999102516M11: Win32/NT4, Linux 6.0
Fixed

I am now able to send a message.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.