Thank you Noel for the reply. The clients have nor problem connecting to JAMES and sending mails with Authentication tag is set TRUE.
The real problem is when JAMES will talk to other Servers using SMTP protocol. The other servers (and I don't know where the clients will be sending mail to so that I can use <authorizedAddresses>) have to authenticate themselves to JAMES, and this where the problem is found. This is what I found on the net: "It seems that some (many?) people do not realize the SMTP users use to send emails is the same SMTP used by other mail servers to forward emails to James; so, if you setup James to require SMTP-Auth for all cases (without configuring the mailet as Danny suggests), you assume that every other mail server in the world will configure login information to your James server." So I don know if <authorizedAddresses> will help. Regards -Bahman -----Original Message----- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: 30. desember 2004 19:22 To: James Users List Subject: RE: Proper way to setup SMTP-Auth Please do not use HTML e-mail. Thank you. > The Clients within our internal network use SMTP protocol to talk > to our James Mail server. > If Authentication tag is set FALSE in James, then everything is ok. > If Authentication tag is set TRUE in James, then everything is NOT ok. If you require authentication, then (as you would see if you turned on DEBUG for the SMTP Server, and looked at the protocol exchange in the log) JAMES will require SMTP AUTH to accept e-mail for non-local addresses. You can use the <authorizedAddresses> tag to tell JAMES that clients in your designated sub-nets are implicitly authorized. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
