>1. The vhost --- mydomain.com
>2. The account --- <mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]
>3. Mail host alias ---- mail.mydomain.com
To simplify life for your clients, you could do this:
mydomain.com MX 10 Imail.ISPdomain.com
smtp.mydomain.com MX 10 Imail.ISPdomain.com
pop3.mydomain .com A ip.ad.re.ss ;
of Imail.ISPdomain.com
So when they are trying to setup their mail programs, for their "SMTP
outgoing mail server", they enter: smtp.mydomain.com
and for their "POP3 incoming mail server", they enter: pop3.mydomain .com
The fact that pop3.mydomain .com and smtp.mydomain.com actually resolve to
the same ip address (of the Imail box) doesn't matter, giving the users two
hostnames for two different fields in their mail program might help them
(or maybe not, sometimes you just don't know).
Of course, if you offer IMAP4, then create a host of
imap4.mydomain.com A ip.ad.re.ss ;
of Imail.ISPdomain.com
However, you might have advantages by using two different hostnames for
SMTP and POP3 / IMAP4 services, since later you could have one machine
handling all outgoing SMTP traffic (a relay-only mail hub) but holding no
POP3 mailboxes, and keep Imail as the POP3 server.
When you make such a break out, your users don't have to change anything in
their mail clients, all you do is change the A record for those
smtp.mydomain.com to the ip of your outgoing mail hub. The users keep
sending mail to smtp.mydomain.com which is now your mail hub, and keep
reading their mail at pop3.mydomain.com which is your Imail box.
Len
http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4
http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
