The problem I found with simply using the RemoteAddrNotInNetwork is that while it does not relay spam, it does accept it and store it in the spam folder. There is no mechanism reporting back to the spam sender that "hey, I know you are spam, and I am not sending this email". Consequently, the spammer thinks you are an open relay and ends up filling your spam folder with 10s of thousands of files. Eventually, James (and Windows) gags on this folder. Also, if your users go to another machine and setup a new mail client, when they send a new email there is no report back to them that because of their new ip address, the email was rejected. This is probably IMHO the most serious of issues in a corporate environment - users need to _trust_ that no news is good news. ie if no error is reported back to you, then the email was successful.
Steve B. ----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Tuesday, May 07, 2002 6:57 AM Subject: RE: Help in JAMES SMTP Config > You can also turn on the RemoteAddrNotInNetwork mailet filter, and prevent > people from outside of your network (or even from off of localhost) from > sending e-mail except to people known to your server. > > One of my thoughts to handle roaming e-mail is to use SSH tunneling. I can > prepare a key pair for roaming users. They can automatically login to a > special smtp account, providing access to localhost:stmp. Their mail client > would be configured to send via localhost. If they are already using > localhost, they can configure a different port for the tunnel. > > --- Noel > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
