Closed
Bug 69630
Opened 25 years ago
Closed 23 years ago
Duplicate default smtp mailers
Categories
(MailNews Core :: Networking: SMTP, defect)
Tracking
(Not tracked)
People
(Reporter: pstephen_murphy, Assigned: mscott)
References
()
Details
Attachments
(3 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-15mdk i686; en-US; 0.8) Gecko/20010215
BuildID: 2001021503
While attempting to send a email, I was denied because
"An error occured while sending mail. The mail server responded: yahoo.com
closing transmission channel.
You must be pop-authenicated before you can use this smtp server........."
I had been user this account all day what happened? I immediately went to
"Mail/News Account Settings ..."
and select the "Outgoing (SMTP) Server" tab and found I had two default smtp
mailers (which were the same) and
my other two smtp mailers were gone.
Reproducible: Couldn't Reproduce
Steps to Reproduce:
| Reporter | ||
Comment 1•25 years ago
|
||
| Reporter | ||
Comment 2•25 years ago
|
||
| Reporter | ||
Comment 3•25 years ago
|
||
Comment 4•25 years ago
|
||
I just ran into this today with build 2001-02-20-08 as well.
It looks to me like any time there is an error sending through a server the
server entry is duplicated.
| Reporter | ||
Comment 5•25 years ago
|
||
Work around. I edited my prefs.js and removed all
"user_pref(mail.smtpserver.smtp*.*)" entries. I removed all references to those
servers by
removing the "user_prefs(mail.identity.id*.smtpServer, *) entries. I restarted
Moz. I re-added the smtp mailers and re-associated the mail identities with
the new smtp mailers.
| Reporter | ||
Comment 6•25 years ago
|
||
Boris,
It's more than duplicated smtp mailers. If you look at my pref.js files I
submitted. You'll see that Moz is completely confused about my smtp servers.
This is an excerpt from my original prefs.js:
user_pref("mail.smtpserver.smtp1.auth_method", 1);
user_pref("mail.smtpserver.smtp1.hostname", "smtp.mail.yahoo.com");
user_pref("mail.smtpserver.smtp1.try_ssl", 1);
user_pref("mail.smtpserver.smtp1.username", "ps_murphy");
user_pref("mail.smtpserver.smtp2.auth_method", 1);
user_pref("mail.smtpserver.smtp2.hostname", "smtp-server.san.rr.com");
user_pref("mail.smtpserver.smtp2.try_ssl", 1);
user_pref("mail.smtpserver.smtp2.username", "smurphy");
user_pref("mail.smtpserver.smtp3.auth_method", 1);
user_pref("mail.smtpserver.smtp3.hostname", "mail.medimpact.com");
user_pref("mail.smtpserver.smtp3.try_ssl", 1);
user_pref("mail.smtpserver.smtp3.username", "smurphy");
user_pref("mail.smtpservers", "smtp1,smtp3") <----------- Notice this line. What
happened to "smpt2"?
I think the above is the starting place of my troubles.
Comment 8•25 years ago
|
||
Marking NEW based on confirmation.
Comment 9•25 years ago
|
||
Marking NEW based on confirmation.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•25 years ago
|
||
Here's what I've noticed, and it may be reproducable enough to track down the
problem.
1) Set up a different smtp server per account (I've got five set up, and on the
Outgoing Server advanced settings, have the second server set as the default)
2) Send a test mail message from each account -- seems to work fine (I use
netstat -c -a -p --inet on linux to monitor the connections being opened)
3) Go to Account Settings, notice that the correct settings are present in both
the smtp server per account, and the "Outgoing Server" advanced settings.
4) Exit and restart
5) Repeat step 2 -- everything is still fine
6) Go to Account Settings. Click on "Outgoing Server", Advanced. For some reason
the Advanced button doesn't respond to mouse clicks the first time (this may not
be relevant), so click on one of the other accounts and then back to "Outgoing
Server", Advanced. Now I see my first smtp server has been removed from the
list. If I click on the account that was previously set up to use that server,
it has reverted to "use default server". However, if I exit all the prefs
dialogs using "Cancel", the previous settings work fine. If I exit the dialogs
using "OK", this account breaks.
It seems the problem is in the "preferences editing" code (as opposed to the
"preferences using" code).
In the past, I have also seen the problem where the "Outgoing Server",Advanced
lists the same server multiple times. I suspect it's all related.
Comment 11•24 years ago
|
||
Comment 12•24 years ago
|
||
*** Bug 85359 has been marked as a duplicate of this bug. ***
Comment 13•24 years ago
|
||
i have the same problems with Build 20022053012, v 1.0 (W9x). I guess the
problem is the password-manager. i created new smtp servers but was never asked
for passwords. i deleted all passwords but Mozilla never asked for new ones for
the smtp servers. maybe he tries to use wrong passwords and this initiates the
errors while sending emails.
Comment 14•24 years ago
|
||
I have the same problem. This is a showstopper for me. I cannot use Mozilla mail
with this problem and will have to go back to Outlook which handles this
situation with ease.
In essence, the Mozilla dialogs do not show me the settings for SMTP that
Mozilla mail is actually using. There appears to be no way for me to tell
Mozilla which SMTP server to use for each account I want to send from. As a
result I can no longer send mail when I am in the UK, at my desk or at my home.
This is a grade 1 bug.
Comment 15•24 years ago
|
||
One more dupe? http://bugzilla.mozilla.org/show_bug.cgi?id=154453
Comment 16•24 years ago
|
||
I forgot to say that I have this problem with build 2002071408 and Win98 SE.
Comment 17•24 years ago
|
||
*** Bug 156919 has been marked as a duplicate of this bug. ***
Comment 18•24 years ago
|
||
Mac OS X, Mozilla 1.0 release & Mozilla 1.1b.
Reproducible:
1. Create the primary account, set SMTP server to require SSL & Auth.
2. Create another account, do not do anything WRT the SMTP server.
3. Send mail from both accounts; it goes via e.g. FirstID@FirstSMTPServer.org.
4. Quit.
5. Start and try to send mail, error in both accounts:
Enter password for SecondID@FirstSMTPServer.org
6. Look at the SMTP config, there are duplicate default SMTP; one looks right.
7. Add another SMTP, make it default, delete one of the duplicates and both go.
8. Fix the new default SMTP, now the error in both accounts is:
Cannot find server %s@FirstSMTPServer.org
Workaround was to hand edit the prefs.js. BTW line breaks in that file are
incorrect for this platform.
Comment 19•23 years ago
|
||
I have noticed that when you create a new mail account and choose the default
SMTP server isntead of "always use default SMTP", a new instance of the SMTP
server appears on the list.
At some point, it becomes impossible to send mail. Changing from the default
server to "always use default" and deleting all but one instance of the server
corrects the problem.
Hope this helps to sort it out.
(win98SE)
Comment 20•23 years ago
|
||
This should have been solved in Mozilla 1.2b, I think together with bug 146488
and bug 167834.
Comment 21•23 years ago
|
||
Hello,
Recently I came across this little problem / bug / feature-
I need to have multiple email accounts each with an outgoing mail server. The
problem is with the advanced settings, they do not work 100% of the time, plus
it appears to be confusing when I'm trying to assist other people (for example,
my sister) in setting up her system to mimic my machine.
For example:
I need to check the email from these accounts; Webmaster, info, and fans, plus
my own personal account(s).
The server is setup only to allow email sent if the userid and address match, so
I can not send email from webmaster via fans's account, nor would I want to have
my mail set from katemichaels' domain (or vice versa).
Here's my solution to the problem:
For each account add the item on the Server Settings panel to have an outgoing
server with the option of using a globally defined account.
This way you can have multiple outgoing mail servers and not be confused as to
what account is sending what email.
Who do I now bug?
Comment 22•23 years ago
|
||
Bug 96207 is about a very similar and at least for some of you maybe identical
problem. I've done some inspection and filed a patch for this bug yesterday.
I suspect that the behaviour described in bug 96207, comment 56 ff. may be
reproducable by some of you and the patch could help these users.
So it would be nice if you could read this through and drop me a note if you can
reproduce this or even the patch helps you.
Comment 23•23 years ago
|
||
Bug 96207 has been fixed now (details see there). I think the problems described
here are at least connected with, if not the same as in that bug.
So it would be very helpful if someone of you, who added comments here could
test the issue of this bug again and say if it still exists or not.
Otherwise I think I'll close this bug as duplicate.
Comment 24•23 years ago
|
||
*** This bug has been marked as a duplicate of 96207 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•