>OK, I searched the knowledge base and found this tidbit:
>
>Note, SMTP Authentication does not work for a shared-IP-address
>Virtual Host that uses an external user database.
http://support.ipswitch.com/kb/IM-20000117-DM01.htm and in red:
"Note, SMTP Authentication does not work for a shared-IP-address
Virtual Host that uses an external user database."
Even as I hesitate to go SQL due to the people who have have it
broken and don't get it fixed, I am still extremely disappointed
about the above, since I assumed Ipswitch would sooner rather than
later fix these fatal SMTP AUTH pb's. Now, even if they stabilize
SMTP AUTH, ip-less virtuals can't use SQL. sheet!!
>Well, that's just great. So, I presume it does work with the
>built-in Imail database or the registry?
if you're lucky, which seems to be the majority.
>And, now that I already have my clients setup in an external
>database, how do I go about moving them to the IMail database? And
>are there any drawbacks to using the IMail database?
I "think" the really big Imail sites, 100K+ accounts, use Imail
database. So "size doesn't matter", but it appears that SMTP AUTH
isn't yet totally stable, although it's confusing with so many
versions of Imail and some many browser versions as to what combo'
are really having specific SMTP AUTH failures.
>Seems I have no choice actually, if I want to utilize SPAM protection.
Just a nit: Relay-for-addresses and SMTP AUTH cobmine to "closeg
open relay" and provide "anti-relay-hijacking", it's not specifically
anti-spam, since that's handled by filtering. ACL's and DNS
validations also help against spammers.
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/
