Christopher:
Not only can you do this for multiple domains, but
also for as many virtual hosts as you want, where no IP address is
available.
In fact, in my opinion, it has many advantages over
the LDAP configuration insofar as:
- its easier to manipulate
- you can then do other things with the database (like multiple e-mails to customers using ASP or Coldfusion or similar
- you can easily retrieve lost "passwords"
- you can easily set up new accounts through a web interface without touching I-Mail
- you can also update Windows User LDAP as well from the web form
Get your SQL database prepared and just select the
Configure External Database
The following parameters are required
Datasource Name which should be of
the form: IMAILSECDB;UID="UserID";PWD="Password" (UserID and Password refer to
the system account for the database system you are using
Implementation DLL which should be
something like:
C:\IMail\odbcuser.dll or wherever you keep that
DLL
Table Name
Make it what you like. I have used the default with
no problems
IMail sets up the tables itself. You will need to
set up the DSN on your app server and point it to the appropriate Database
server. From then you can replicate to your hearts content. Now the database
does not store the actual e-mails, just all the account related parameters, so
you can't back up actual e-mails this way.
Probably the Imail afficionados will cringe, but I
prefer it to the LDAP as it provides lots more flexibility and if things go
wrong, its much easier to trace the problem. If you are really keen you can
write ASP or CF code to access the LDAP, but you lose a lot of
flexibility.
In fact what I do is have a registration page on
the web site for new users. When they register the web form updates the SQL
table attached to IMail and the new IMail account is set up instantly with no
effort or input from my side at all, which is really great otherwise I'd have to
employ someone almost full time to just manage the new the email
accounts.
You can write code to extract info from the SQL
database, for example, to automatically delete users who have not logged in for
specific periods etc .
Most of my e-mail "domains" are virtual. I think I
have something like 20 of them hanging off just 2 IP addresses. Seems to work
just fine.
Cheers
Ted Daniels
----- Original Message -----
From: "Christopher Jones" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, May 15, 2005 6:05 PM
Subject: [IMail Forum] Multiple email domains &
Windows NT Database
>
> We host 4 email domains that are all setup using their own IP Address. I
> would like to use a Windows NT Database instead of the standard Imail
> database.
>
> We have a Disaster Recovery Email Server which is sitting alongside the
> current email server. At the moment we have to manually import registry
> settings and change IPs to failover to the DR server.
>
> If I were to use an NT Database, I was hoping I could make both servers a
> member of their own Active Directory Domain, that way any new account
> created on one would be replicated to the other. It would definitely keep
> the auditors happy in regards to our DR Plan.
>
> My question is, is there a way to do this with multiple domains? Having only
> one email domain seems to make it very simple, but how do you accomplish
> this with multiple domains?
>
> Can Imail distinguish between accounts in the one domain?
>
> If Imail could use Active Directory then I could simply create separate OU's
> for each of the domains and then direct Imail as to which OU to use for each
> domain.
>
> Has anyone been able to accomplish anything similar to this? I'd be
> interested to hear.
>
> Thanks.
>
> Chris Jones
> IT Support & Security
> Rural Press Limited
> Sydney, Australia
>
>
> To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
> List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
> Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
>
