Closed
Bug 28246
Opened 25 years ago
Closed 25 years ago
SMTP server field in wizard should be greyed out if a server already set up
Categories
(SeaMonkey :: MailNews: Account Configuration, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: sol, Assigned: alecf)
Details
(Whiteboard: [PDT+] 2/18)
In the Account Setup wizard, when setting up a second (or later) account, if the
user already has already configured Mail to work with an SMTP server, then the
wizard should show the SMTP server name, but the name should be greyed out
(i.e., non-editable). The user should be instructed that they can change their
SMTP server by going to "Mail/News Account Settings | Outgoing (SMTP) Server".
Build ID - 2000-02-14-16.
Steps to reproduce:
1. Launch Mail (Tasks | Mail)
2. Open Mail/News Account Settings (Edit | Mail/News Account Settings)
3. Create New Account (press "New Account" button to launch Account Setup wizard
4. Proceed through the wizard to the "Server Information Screen"
Actual result: name of current SMTP server is pre-populated in an editable field
under the label "Outgoing (SMTP) Server"
Desired result: name of current SMTP server is pre-populated in a *non-editable*
field under the label "Outgoing (SMTP) Server".
Note: If the user has *not* set up an SMTP server yet (e.g., on a fresh
install), the SMTP server field should be editable.
Note: The SMTP server field should include a note telling users that "Your
ability to send messages using a particular outgoing (SMTP) server usually
depends on your connection to the Internet. If you would like to change the
settings for this server, go to *Mail/News Account Settings | Outgoing (SMTP)
Server*."
cc:ing Simone for better language for the above note.
Nominating for beta1. Our testing indicated that end users type in a new SMTP
server name, not knowing that - unless they have changed their connection type
to the Internet - sending outgoing messages will fail.
For end users upgrading from 4.x, failure to fix this bug will result in many
users being unable to send messages. These users will perceive that mail is
"broken". Because this problem is high frequency (most users who test out
multiple accounts functionality) with a bad result (can no longer send
messages), this must be fixed in beta1.
Keywords: beta1
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Assignee | ||
Comment 3•25 years ago
|
||
Fix is almost done - I have the proper behavior, just have to enter the actual
strings that we decided on.
Whiteboard: [PDT+] → [PDT+] 2/18
Assignee | ||
Comment 4•25 years ago
|
||
ok, implemented and checked in as per our discussions over e-mail.
if wording changes, we just need to update
http://lxr.mozilla.org/seamonkey/source/mailnews/base/prefs/resources/locale/en-US/aw-server.dtd
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•25 years ago
|
||
reopening and reclosing because this keeps coming up on my queries
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•25 years ago
|
||
fixed again
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
FYI -In the interests of good record-keeping, I'm entering the suggested
rewording here:
Your outgoing (SMTP) server is currently set to "<smtp.server.name>".
For multiple mail accounts, only one outgoing server needs to be specified. For
most
Internet Service Providers, you should use the SMTP server associated with the
account you use most often to connect to the Internet.
If you can use your SMTP server from any Internet connection, choose Preferences
from the Edit menu and then select Account Settings to configure another SMTP
server
for this account.
Comment 8•25 years ago
|
||
Build 2000-02-23-08M14: NT4, Linux, Mac
Reopening since the text should be updated to correspond with Simone's statement
on 2/22.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I think the Wizard has the correct language, and Simone's submission was from a
prior email exchange. I think the bug should stay "Fixed".
Assignee | ||
Comment 10•25 years ago
|
||
the first two paragraphs match the wizard.
The second paragraph above wrong for beta1 because this stuff is not in
preferences for beta1. I don't really have time to deal with this right now and
it's going to be PDT-'d if we don't close it soon.
I'm going to re-mark this fixed because it is a PDT+ bug and I've fixed it
"close enough" for beta1. :)
Ninoschka, can we open a new bug for to fix the wording? I'll target it for
after beta1
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•