We have solved this difficulty in VOPmail by requiring ESMTP authentication
before opening an unapproved IP for relay. This of course requires your
customer to use a mail client that supports ESMTP authentication.
If your NTMail user repository is stored in either the NT SAM or an ODBC
DSN, we have just introduced a light, relay-only version of VOPmail for
$175. This version could authenticate against your NTMail user repository
and be used only by your roaming users.
Regards,
Steve Velosa.
Vircom, Inc.
> -----Original Message-----
> From: ntisp-request@iea-software.com
> [mailto:ntisp-request@iea-software.com]On Behalf Of Sam Lowe
> Sent: Thursday, March 25, 1999 9:37 PM
> To: ntisp@iea-software.com
> Subject: [NTISP] E-mail solutions
>
>
> I am really at my wits end with e-mail. We run NTMail for our
> users, and to
> prevent relay and other unauthorized use, we selectively permit
> e-mail to be
> sent from certain ip ranges. This is fine until a user travels
> and want to
> send e-mail while logged into another service which issues an ip
> foreign to
> my "approved" range.
>
> Any experiences with this arrangement? I am about ready to set up another
> server to authenticate outgoing e-mail by password, but hate to go to this
> expense for a few clients. At the same time, I hate to subject
> the rest of
> the user database to having to do this, thus the separate server.
>
> We've been used for e-mail relay in the past, and I really don't want this
> problem again.
>
> TIA.
>
> Samuel S. Lowe
> Director, Data Network Services
> UniversalCom, Inc
> Voice 850-837-0077 VM x116
> FAX 850-654-1794
> slowe@universalcom.net
>
>
> For more information about this list, including removal,
> see this url: http://www.iea-software.com/maillist.html
>
For more information about this list, including removal,
see this url: http://www.iea-software.com/maillist.html