> I'll be installing iMail on a machine named
> neptune.castleweb.com. Based on the manual, this is the "primary host"
> (manual, p.18). However, there are no real accounts here --
> mail will all be for other domains. I have
> [EMAIL PROTECTED] forwarding to my real e-mail account.
You don't need your "primary host" to be the actual machine, unless
someone will actually be sending mail to that machine name. I'd recommend
making your company domain the primary host for simplicity's sake.
> iMail will process mail for several domains (a.com, b.com,
> c.com, etc.). All have MX records aliased
Hope you don't mean CNAMES. CNAMES and MX records don't mix accd. to the
RFCs.
> to the same IP
> address as neptune.castleweb.com (mail.a.com, mail.b.com,
> etc.). I can change the mail.a.com IP addresses to be
> different, but would prefer not to for ease of maintenance.
Just have the MX record of each virtual domain point to
"neptune.castleweb.com", or "mail.castelweb.com" (more conventional for a
primary host).
> Questions:
Oh sorry, I thought we were already into the questions. :)
> 1. When adding a.com to iMail, I prefer to add "a.com" rather
> than "mail.a.com", since this domain is what is displayed
> in the Web interface. Is this acceptable, or must I add
> "mail.a.com" and setup an alias "a.com"?
Your preferred method is perfectly acceptable, and is the way most of us
do it. Makes for nicer default reply-to addresses ("[EMAIL PROTECTED]"
instead of "[EMAIL PROTECTED]") and nicer webmail display. Just add
"mail.a.com" as a Host Alias (you can add more if necessary, using a space
as the delimiter).
> 2. When adding a.com, b.com, etc., should I add these as
> virtual domains? iMail lets me add them as either virtual or
> IP. The documentation leads me to believe that they must be virtual.
If you have an endless supply of IPs, you can certainly use them, but most
of us here go completely virtual for simplicity.
> 3. When accessing mail through WebMail, will it make a
> difference in what the user sees if I use virtual or IP-based?
> That is, will a user from a.com see the URL in their browser as
> neptune.castleweb.com (the primary host) or mail.a.com
> when they connect? I'd prefer the latter, of course.
The URL they see is up to your config and your DNS. The only difference
between virtual and IP'd domains in regards to web msg is that users going
to a virtual, non-IP'd domain will see the Login page from the web
templates of the primary host, and will need to login with their complete
email address instead of just their username. In other words, IMail's web
msg service doesn't look at the URL when determining where they want to
go. As most ISPs like to give each virtual domain their own login screen
look and feel, including logo, this is a bit of a problem. In our Killer
and Classic templates, we use a JavaScript trick to auto-submit a bogus
login attempt to the domain specified in the URL, so that custom logos and
templates can be pulled up even for non-IP'd virtual domains.
Hope that gets you started...
Ron Hornbaker
- http://humankindsystems.com - 2,461 admins can't be wrong
- http://AnswerTrack.com - eCRM email tracking & routing
- http://KillerWebMail.com - the name says it all
- Buy IMail from us, get KillerWebMail FREE!
- 1-888-952-4888 or [EMAIL PROTECTED]
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/
