Closed Bug 18184 Opened 25 years ago Closed 24 years ago

[FEATURE] Multiple SMTP server support

Categories

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

Product:
SeaMonkey
Component:
MailNews: Account Configuration
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: bratell, Assigned: alecf)

References

Details

(Whiteboard: fix in hand) 

Each account should be able to have it's own outgoing smtp server even if there
could be a default to use when none is specified. That is because most public
smtp servers don't accept mails coming from other domains than their own (unless
addressed to a local account), so each address might need it's own outgoing smtp
server.
Status: NEW → ASSIGNED
Summary: Should be able to have seperate outgoing smtp servers for each account → [FEATURE] Multiple SMTP server support
Target Milestone: M14
This isn't quite right:
The SMTP server you use is dependant on your physical connection to the
internet, not the e-mail address you're sending as. This means if I have two
ISPs, isp1 and isp2, and I connect through isp1, then I should be using
smtp.isp1.com no matter what my identity is, even if I'm using userid@isp2.com.
Once I am physically connected inside the "isp1.com" domain, I can freely use
smtp.isp1.com.

I've debated this with many people, and I have done the testing with a number of
major ISPs to back up this claim.

what we're going to do is this: You can have a 'pool' of SMTP servers, with one
of the SMTP servers marked as the "default" server. At message compose time, we
will expose the list of SMTP servers in a menu, and you will be able to choose
an SMTP server to send with. If you choose something through the menu that's not
 the "default" server, then the newly chosen server is marked as the
"session-default" server, meaning it is the default server until you quit and
restart mozilla. There may be slight tweaks to this behavior before the product
actually goes out the door.

I don't have a feature bug yet for the behavior I've just described, so I'm
going to make this the feature bug. However, we've already decided that this
feature will not make it into the first beta/alpha/whatever, so I'm going to put
the target milestone as M14 for now.
Blocks: 10791
OS: Windows NT → All
QA Contact: lchiang → nbaca
Hardware: PC → All
Target Milestone: M14 → M15
There might be cases where you'd like to use different isp's for different
accounts regardless of which isp you connect to.  Eg, your university email
policy prohibits commercial use of their servers, so you want to send everything
related to your small business through a separate server.  Windows is probably
smart enough to dial the right number depending on which sevrer you want to
reach; linux could probably be tweaked to do the same (with diald).  Then
there's the issue of laptops connected to differnet networks, where the SMTP
server could maybe be linked to the (assigned) IP address of the machine (ie, if
the machine's IP is x, SMTP1 is used; if it's y, SMTP2 is used).
I need this feature as well. I don't want to send other business/personal mail
through the company smtp server, as all the mail is logged.
SMTP servers allow us to differntiate between the personal and business mails
and also define what mails we want sent using what server
It makes lot of sense to allow sending different kinds of mails thru different
servers coz some businesses track the incoming and outgoing mails for a user
and lot of people don't want to fall in this trap.
I should add that I've already implemented the backend for this. We just won't
have a UI until post-beta1

*** Bug 28719 has been marked as a duplicate of this bug. ***
*** Bug 28719 has been marked as a duplicate of this bug. ***
*** Bug 28719 has been marked as a duplicate of this bug. ***
*** Bug 28719 has been marked as a duplicate of this bug. ***
*** Bug 28719 has been marked as a duplicate of this bug. ***
Adding dependancy for per-identity smtp support (to be checked in soon)
Depends on: 28898
Priority: P3 → P2
Priority: P2 → P3
this should probably go on the feature list for beta 2. CC'ing selmer
Depends on: 34279
Syncing priority with marketing.  Moving to P2 to connote "In" for beta2.
Priority: P3 → P2
move to M16.  Not M15 stoppers
Target Milestone: M15 → M16
Mass-update: setting P1 on M16 bugs for scheduling
Priority: P2 → P1
Since there are many duplicates, a working backend and several votes on this, 
I nominate this for nsbeta2.
Keywords: nsbeta2
A small mistake was pointed out for me (thanks BenB) so I want to change my 
statement above to: "since there are many tries to mark the one duplicate as 
duplicate..." :-) 

But I still think this should be nsbeta2. I don't know how much work is left 
before closing this bug. There is a blocker, but that one (bug 34081) is not 
accessible for me.


I should add that I have, in my tree and ready to check in:
- the completed datasource so I can reflect the serverlist into any UI
- updated code for the compose window to put the server list into the menu
Whiteboard: fix in hand
ok, all the backend work is in, so I'm going to delclare this "feature complete" 
so that all other bugs are just bugs :)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
lol, finally somebody, who says it straight :)


Verified. I will use bug# 28898 to test its functionality.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.