Closed Bug 195815 Opened 23 years ago Closed 20 years ago

wrong Return-Path + smtp-server not assignable

Categories

(MailNews Core :: Networking: SMTP, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: sven_tewens, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.2.1) Gecko/20021130 The following situation: My girl-friend and I we both have individual accounts at gmx. Therefore I tried to set up two separate accounts in Mozilla-Mail for both of us on my PC. => It's not possible to choose the right SMTP-server via dialog => Mozilla sometimes chooses the wrong Return-Path!!! Example: Account 1: POP3 pop.gmx.net User-ID 1000 email 1@gmx.de SMTP mail.gmx.net Account 2: POP3 pop.gmx.net User-ID 2000 email 2@gmx.de SMTP mail.gmx.net => Errors: (1) You can't choose the right SMTP / User-ID in dialogue. Pressing the advanced button you get two times the choice "mail.gmx.net" but you don't know which one to choose for which user. To make a proper assignment you have to manually edit prefs.js (e.g. identify ("mail.smtpserver.smtp1")/("mail.smtpserver.smtp1") do assignment ("mail.identity.id1.smtpServer", "smtp1") / ("mail.identity.id2.smtpServer", "smtp2") (2) Write one mail under account 1 (+ send later), write another mail under account 2 (+ send later); then choose command "send unsent messages" => both mails will get the _same_ Return-Path!!! Do the same but send the messages immediately and each one will get its own correct Return-Path!!! Reproducible: Always Steps to Reproduce: see details Actual Results: see details Expected Results: show not only SMTP-Server name but server-name + user-id so than we can choose the right combination via dialog send the correct return-path in both cases
Product: MailNews → Core
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/
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: 20 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.