Hi Noel, by handling it this way, you have to ask all clients for authentication when it is turned on. Later on, in the transport queue, you check if authentication would have been necessary. But my approach was to let local clients send mails without specifying authentication data while remote hosts would have to authenticate in order to even deliver the mail. This is the same than with local recipients. In the moment (at least with my installation), if a host connects, it is asked to authenticate when authentication is switched on. But normally you'd want to be able to deliver mail to local accounts without the need to authenticate (which isn't possible since other mail servers delivering mail have no local accounts to authenticate with). Authentication is only needed when mail is going to be relayed outwards. Or do I miss something?
Regards, Thomas > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 31, 2002 3:50 PM > To: James Developers List > Subject: RE: Open relay with SMTP-AUTH > > > Thomas, > > I don't believe that it is necessary to configure the SMTPHandler > that way. > What you want to do would be configured through appropriate > matchers/mailets. To require AUTH regardless of circumstance, you would > turn on authRequired. To require AUTH for relaying by non-local IP, you > would use a matcher that checked for authorized mail if it failed the IP > check. This is the JAMES philosophy: building blocks with appropriate > infrastructure. > > --- 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]>
