Closed Bug 14094 Opened 25 years ago Closed 24 years ago

UI: Missing advanced SMTP settings

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Account Configuration
Platform:
All
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: nbaca, Assigned: alecf)

Details

Build 1999091509M1: Win32/NT4, Linux/Redhat 5.0, Mac 8.5.1

Overview: In Account Settings dialog there is no panel for "Advanced".

Expected Results: According to the Account Setup Spec,
http://gooey/client/5.0/specs/mail/accountSetup/accountSetup.html, there should
be a panel titled "Advanced" indented under the "Outgoing (SMTP) Server"
panel.For instance:

- Outgoing (SMTP) Server
  - Advanced

Once the Advanced panel is selected on the left then the right panel would be
titled "Outgoing (SMTP) Server Settings - Advanced".
QA Contact: lchiang → nbaca
Summary: Account Settings Dialog: Panel Missing, Advanced → Account Settings Dialog: Panel Missing, Advanced
Setting QA Contact to nbaca.
Target Milestone: M11
Blocks: 11091
(target milestone is M11 or M12 - add to beta tracking bug)
Target Milestone: M11 → M14
not doing advanced for PR1.
No longer blocks: 11091
Ok, removing from beta 1 tracking bug :-)
oops..thanks lisa!
Component: Front End → Account Manager
Summary: Account Settings Dialog: Panel Missing, Advanced → Missing advanced SMTP settings
Target Milestone: M14 → M17
What was I thinking. This is like an m17 task
Summary: Missing advanced SMTP settings → UI: Missing advanced SMTP settings
the spec has changed, but the advanced now exists under the "Advanced" button
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Build 2000-05-24-08M16: Win95, Linux 6.0, Mac 9.04
Verified Fixed. In Edit|Mail/News Account Settings, go to the Outgoing (SMTP) 
Server panel. There is now an "Advanced" button which opens an "Advanced 
Outgoing (SMTP) Server Settings" dialog.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.