Closed
Bug 208536
Opened 21 years ago
Closed 19 years ago
switching profiles causes smtp errors
Categories
(MailNews Core :: Networking: SMTP, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: farcusnz, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 If I switch from one profile to another without closing Mozilla and then try to send an email I get an smtp error message 'could not connect to the smtp server - check your settings and try again.' Reproducible: Always Steps to Reproduce: 1.switch profiles 2.compose email and try to send 3.cannot send email and get error window. 4.save message - close Mozilla - relaunch and send email - no problem Expected Results: Mail should be sent without any problems.
Comment 1•21 years ago
|
||
Are you sure that you have SMPT settings for both profiles, and that both of them work correctly (in other words, if you start from scratch with that profile, does mail sending work OK? WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030606
yes, both profiles have separate smtp settings - one has an australian yahoo smtp setting and the other (my partners profile) a Japanese yahoo smtp setting. The only difference in the settings is that while mine ends in .com.au the other ends in .co.jp Both smtp settings work 100% every time if the profile is started from scratch - and fail 100% every time if called in the same session that a profile has been switched. To test I created a new profile with an smtp setting from my isp but I still see the same behaviour in the new profile.
Updated•20 years ago
|
Product: MailNews → Core
Comment 3•19 years ago
|
||
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•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•