We are small scale, but I think this might help.
We have clients that "roam" quite a bit.
We secure our server(s) with IPs (Local Host Only) and our roaming users
have one of two options.
1) Using a client software, they must authenticate themselves to pass
traffic.
2) Using the web interface.
Hope this helps,
-Pete
----- Original Message -----
From: Craig <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, August 15, 1999 6:18 PM
Subject: [IMail Forum] SMTP security question
> I just wanted to pose a question and see how some of you handle
> smtp security (or your recommendations for our situation).
>
> Background info:
> We cannot employ security by IP address, we provide hosting
> services but no dialup so our customers are literally all over the
> world. With that in mind we have implemented security using "local
> user" authentication (not local host).
>
> This works fine but I was wondering how some of you with similar
> setups handle aliases. Aliases are not recognized as a valid local
> user and thus must be included in the "accept.txt" file or have a
> "real" user account created for each alias. We are currently using
> the accept.txt method and it is growing a little unwieldly.
>
> This becomes more interesting if you have some domains with their
> own host administrator (which we do). They add an alias and we
> don't know about it... it doesn't work and we get a phone
> call/email unless we catch it in the logs right away. We review the
> logs diligently because of this.
>
> Any suggestions on a better way to handle/implement this. I've
> been on this list for quite some time and know there are *a lot* of
> very talented imail admins here...
>
> Thanks for your suggestions...
>
> Craig
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
