Closed Bug 22579 Opened 25 years ago Closed 25 years ago

[DOGFOOD][Regression]Unable to send mail

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: fenella, Assigned: phil)

Details

Linux Redhat (1999-12-23-08 M13) Win_nt 4.0 (1999-12-23-08 M13) Mac (1999-12-23-08 M13) Steps: 1. Launch Messenger 2. Click New Msg to open a compose window 3. Compose the message and click Send Actual result: I get an Alert dialog saying "Sending of message failed". Message is not sent. Expect result: Should not have this dialog. Message should be sent. This occurs on all platforms in both IMAP and POP accounts.
Severity: normal → blocker
Summary: [Regression]Unable to send mail → [DOGFOOD][Regression]Unable to send mail
There were a lot of server problems (where the server was not accepting email around the date indicated). I also thought this was a "bug" until I found the *same* results using 4.x. Can you reproduce this in a current build while the server is up? Thanks, Jim
I'm sending mail fine on 1/3 NT builds. Are you still seeing this?
We'll try this. I think should be ok now, but we'll double check.
Linux Redhat (2000-01-03-08 M13) Win_nt 4.0 (2000-01-03-09 M13) I try it again using both IMAP and POP accounts and using Both Plain text and HTML compose windows: The problem still exists in Linux and Win_nt 4.0. However, this problem does not occur on Mac in both IMAP and POP accounts. Sending message is OK on Mac.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Linux Redhat (2000-01-03-08 M13) Win_nt 4.0 (2000-01-03-09 M13) Please see but 22930. My apology for not checking the account information first. I retested this bug and ensured account information was correctly entered. This bug no longer exists. Mark it worksforme.
Status: RESOLVED → VERIFIED
Since I am the reporter of this bug. I am going to close it .
*** Bug 33288 has been marked as a duplicate of this bug. ***
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.