SMTP auth will indeed block certain kinds of spam, basically it will reject mail from external, unauthenticated, users which is not destined for delivery to the local domain(s). It doesn't, AFAIK, check the local user, as this would deny James the ability to handle mail not destined for a local user, such as mailing lists or forwarding.
d. > -----Original Message----- > From: Kenny Smith [mailto:[EMAIL PROTECTED]] > Sent: 28 November 2002 18:12 > To: James Users List > Subject: RE: My first contact with James > > > Hi Danny, > > Yeah, I've read through that (it was very important to me), but I think > Nebril is looking for a way to stop James from accepting the mail at all, > instead of accepting the mail and then dropping it to /dev/null. > That's why > I suggested SMTP-AUTH, because I believe that cuts the connection > short and > doesn't even accept the mail without authentication. > > Sorry if there was a misunderstanding. > > Kenny Smith > JournalScape.com > > > -----Original Message----- > > From: Danny Angus [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, November 28, 2002 9:57 AM > > To: James Users List > > Subject: RE: My first contact with James > > > > > > James is not an open relay for Spam. > > James is not an open relay without using SMTP AUTH. > > > > This topic has been coverd over and over. > > Read This: http://jakarta.apache.org/james/FAQ.html#2 > > > > d. > > > > > > > > > > -- > > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
