Closed Bug 6315 Opened 25 years ago Closed 25 years ago

smoke test blocker: Send mail does not work

Categories

(MailNews Core :: Backend, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lchiang, Assigned: bugzilla)

Details

smoke test blocker: Send mail does not work 1999-05-09-12 release build Linux 1999-05-09-12 release build Mac No Win32 relase build to try yet. 1) Start Messenger 2) Compose message - notice that an HTML compose window appears 3) Enter recipient, subject, and body 4) Click Send 5) Get message. No new mail comes in. Even if you send to an account and retrieve the message in 4.x, no new mail comes in. QA Blocker.
Status: NEW → ASSIGNED
Priority: P3 → P1
Target Milestone: M6
the bug occurrs on windows too. looks like we aren't getting any recipients from the compose widget to send the message too. i'm still investigating.
Adding alecf and ducarroz to the cc list in case they have any insight. Turns out the networking code isn't involved at all. When the compose app core is sending the msg, it is querying the dom: res = domDoc->GetElementsByTagName("input", getter_AddRefs(nodeList)); The node list we get back has 0 elements in it. So we never get the to, cc, subject, etc from the compose window. As a result when we go to send the msg, we have no recipients to send it to. I'm not sure if the bug is ender, dom or compose related. So I am open to suggestions if someone has any =)
Assignee: mscott → ducarroz
Status: ASSIGNED → NEW
re-assigning to ducarroz. the code calling for the dom list is C++ code --> nsComposeAppCore::SendMessage2.
This might be an nsCOMPtr() problem - maybe the getter doesn't addref? try it with native pointers, see if that makes a difference..
Status: NEW → ASSIGNED
Ok, I found the problem. HTML tag name are now capitalized in the DOM. Therefore when I was looking for elements named "input" I didn't find them. Looking for "INPUT" work much better! I am Waiting for authorization to check in.
shame on the dom folks for making this change yesterday and not broadcasting the fact that the html dom elements now have to have uppercase names to people!!!!
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
don't need an authorization anymore, the tree just open... Fixed and Check in.
Status: RESOLVED → VERIFIED
This has been verified on last Friday's builds. Today's Win32 and Linux builds are fine too. Mac hasn't come out yet.
Status: VERIFIED → REOPENED
Does anyone know why this bug just got re-opened?
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
The bug activity shows ramar@cnet.com has reopened this bug. I'll cc: ramar@cnet.com. Meanwhile, I'm remarking this bug to be fixed until we hear comments. ramar@cnet.com - if you are seeing this problem, it may be better to open up a new bug on this.
ramar@cnet.com seems to be going on a minor rampage. This isn't the only bug he has REOPENED without comment, and he randomly tweaked several fields on yet another bug. His Bugzilla account has been disabled until he can explain his actions.
Status: RESOLVED → VERIFIED
Wow. Marking this bug verified.
Cannot send email even though it seemed like Mozilla nightly build 02/11/99 does send it. Verified using Netscape Communicator 4.7. No mail to recevie. Sent email from Outlook Express to myself, I had to enter in my userid and password to send email to myself. In conclusion, sending email in Mozilla may work for some but not others because some SMTP accounts require a password authentication before the email can be received. This is the case with Time Warner's Road Runner cable. Once I sent email in Outlook Express, I was able to retrieve it in Mozilla Mail/News just fine.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Target Milestone: M6 → M14
danmorg, you're asking for smtp authentication support which is separate from this bug where send mail wasn't working one day. Re-closing this bug. You may want to add yourself to Bug # 25974 if you'd like to track the progress of authenticated smtp. reclosing
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
marking verified once again. This bug was for M6 so I'm going to correct it back. danmorg@ingress.com - in general, we don't usually reopen a bug that has been fixed and verified about 8 milestones ago. It's best to file a new bug when you find a bug that just occurred rather than reopen a bug fixed many months ago. Thanks.
Status: RESOLVED → VERIFIED
Target Milestone: M14 → M6
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.