>Hmmm. I'm not sure. It would seem that it doesn't need it. Can you set
>up a separate DNS for each domain? My clients (albeit all virtual) can
>access their web mail from http://mail.domain.com/. Therefore, if it's
>tied to a IP, they wouldn't need a the "virtual" login. And you can have
>a separate web template for each.
>
>Needless to say, I don't really know since I haven't actually done this.
The was the consensus long ago in this list, but for newbies it bears
repeating:
In Imail:
mail hostname : domain.com
mail hostname alias: mail.domain.com (and/or smtp and/or pop3 and/or imap4
and/or webmail)
DNS forward zone:
domain.com MX 10 mail.domain.com
mail.domain.com MX 10 mail.domain.com
smtp.domain.com MX 10 mail.domain.com
domain.com A ip.ad.re.ss
mail.domain.com A ip.ad.re.ss
smtp.domain.com A ip.ad.re.ss
pop.domain.com A ip.ad.re.ss
imap.domain.com A ip.ad.re.ss
webmail.domain.com A ip.ad.re.ss
ALL, repeat ALL, mail hostnames and their alieas defined in Imail must have
both MX and A records to be acceptable to the widest range of most
restrictive mail servers doing anti-spam checking and DNS validations.
Then, for your clients in their mail programs:
outgoing mail SMTP server: mail.domain.com or smtp.domain.com
incoming mail POP3 server: pop.domain.com
incoming mail IMAP4 server: imap.domain.com
Webmail url: webmail.domain.com
The advantage of having separate hostnames for (mail and smtp) vs (pop and
imap) and webmail is that when your traffic gets heavy, you can have
separate machines / ip's for smtp and pop/imap and web messaging traffic,
with your clients making no change in their mail programs.
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/
