Closed Bug 97202 Opened 24 years ago Closed 24 years ago

Send Message Error when sending mail after installing with cleaned profiles

Categories

(MailNews Core :: Networking: SMTP, defect)

defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: ktrina, Assigned: mscott)

References

Details

Attachments

(1 file)

Receiving "Send Message Error" when sending mail after installing today's builds with cleaned profiles. I will attach a screen shot of this error message. All platforms/trunk builds: Win 2001082706, Mac 2001082708, Linux 2001082703 Steps to reproduce: - Clean your profiles - Install today's trunk build - Go through Activation steps - Launch - Compose mail, send and error message will appear Reproducibility: Always
Attached image Send Error Message
K'Trina, can you go to: Edit / Mail News Account Settings then click on Outgoing SMTP server. Under the heading: "Use secure connection (SSL):" does it say Never or When Available? If the later, does setting it to Never make it work for you?
"Use secure connection (SSL):" is already set to Never. Strange. I figured out a couple work arounds. Clean your profiles then install an older build, or you can cancel out of Activation with today's builds.
ccing Bhuvan and Todd in case this is an Activation related issue
I created a new account in Activation with today's trunk builds (instead of activating an existing account) and it gave me the same error message when sending mail. Blocker?
K'trina, are you sending email over an activated webmail or aol mail account? Or are you trying to send mail through say dredd, or nsmail-1?
I'm sending email over my Netscape mail account and I sent it through judge (my migrated default server) and originally I even tried nsmail-1 and nsmail-2 to make sure it wasn't a server problem on judge.
ccing varada (per bhuvan)
QA Contact: nbaca → sheelar
It will be useful to know about the other conditions that can lead to this error message (besides the server is down) when user sends a message. Varada might be aware of such cases.
Which account you activating? it's a webmail account or nsmail-1 account?
Or are you trying to use the webmail account and use other SMTP server (e.g. nsmail-1)? Can you describe more clear from your account setting info and your SMTP info?
It's a Netcenter Webmail account (netscape.net), but we were sending mail from our netscape.com accounts. I didn't try to send mail from my netscape.net account though. I'll give that a shot as well.
I am seeing this problem as well with nsmail-2 as both IMAP and SMTP server in my gbush@netscape.com account. If I activate this profile, I cannot use mail, which limits what testing we can do with Profiles/Activation etc. changing severity to critical K'Trina - should we nominate for nsBranch?
Severity: normal → critical
Scott, This bug is an annoyance for Installation/Profile/Activation testing. We cannot use the product if we Activate which we obviously must do. Nominating - would like to mark blocker but there is a workaround for us- we can create another unactivated profile- 'the major annoyance'
Keywords: nsbranch
There is no doubt that new customers will go through the Activation process and existing customers will enter existing account information. In both cases they will not be able to send mail. I agree, this is a blocker.
Blocks: 99230
this is a dup of another bug we are working on in bugscape that was filed by someone in netcenter. We need to dup this and move it into bugscape.
Keywords: nsbranchnsbranch+
This is a dupe of bugscape bug 9178. I could not find the bug that was filed by someone in netcenter.
See http://bugscape/show_bug.cgi?id=9178 (disregard link on my previous comment)
bugscape Bug #9264 is the one i was referring to. Marking this as won't fix so we can continue the discussion in 9264. If after reading that bug you think it's a separate issue, let me know and we'll start again!
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Verified. Bugscape bug 9264 is not a separate issue.
Status: RESOLVED → VERIFIED
As I mentioned, something is missing during the migration and activation process. The SMTP2 never get created from this scenario. user_pref("mail.smtpserver.smtp2.hostname", "smtp.netscape.net"); user_pref("mail.smtpserver.smtp2.redirector_type", "netscape"); user_pref("mail.smtpserver.smtp2.username", "karenlh1125"); user_pref("mail.smtpservers", "smtp1,smtp2"); Bug 9264 actually is dup of bug 9178. Let's keep one bug (bug 9178) for tracking this problem.....
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: