RE: SMTP exit program?

How are your remote users connection to your mail server for sending
outbound mail?  Are they connecting directly to the SMTP port from anywhere
on the internet without being required to logon to your system?  If so, I
would give them a VPN solution, add your list of VPN IP address to your
Relay list and block direct connections from the internet unless they are
sent to one of your receiving domains.  That way your people are
authenticated on your network prior to sending e-mails.  Now Exchange will
allow you to require people to log in to the SMTP to relay and I cannot find
the same with IBM's OS400 SMTP server.  

Good Luck,

Chris Bipes

-----Original Message-----
From: Tom Hightower [mailto:tomh@simas.com]

As a courtesy to our subscription customers, we set up an email server for
them (with their own domain name) on our Notes server.  Who knows from where
they will receive email; anyone from anywhere can send them email.
Likewise, they can send email to anyone, anywhere.  I just want to tighten
up the server so that the email is either a) FROM someone in my list, or b)
TO someone in my list.  My list will be all of the user accounts that I've
set up (a couple hundred at most).  If the incoming email fails both tests,
it will be rejected.

Now, if everyone just stayed put in their office and sent email from a
never-changing static connection everthing would be easy.  But alas such is
not the case; many of our customers (ourselves included) have roaming users
who connect to an ISP in who-knows-where, and they still need to be able to
send their email, which means that I need to allow some relays.  I have set
up some relay restrictions already (in both Notes and on the 400), and for
the most part it works alright.  But some relay still gets thru. Requiring
that the email meet both tests above should put a complete stop to unwanted
relays.

The GUI interface in Ops Nav will allow me to enforce the first requirement
but not the second.  I can't use one without the other, so I use neither.