>Without any other extenuating requirements to have the user database in a >SQL database (like billing software or some other integration requirements), >I would have to agree with your assessment that the registry is a better, >more efficient, solution for IMail then is a SQL database.
If I were needing SQL, my objective would be to run the business on SQL and export SQL domains and users to Imail (imail slaved to SQL), so that Imail ran best, and both ran in parallel and without depending on each other. The redundancy would give best performance of each server and of total system throughput, and maximum uptime. Anyway, the registry vs SQL argument is kinda dumb if the mailbox administrator insists anyway on exposing his server to Internet as the MX host, and insists on making the high-volume mailbox/webmail server also do all its own SMTP plumbing, filtering, anti-abusing, defending, scanning rather than using a gateway. Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse 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/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
