In my experience to get a whitelist to work you have to be careful with how your local user account, servernames and smtp are configured. In my setup the user in James and the user in the sending email address are the same (although the domains differ). The domain of the sending address is included in the servernames block along with the name of the James machine (in my case localhost).
Example: James is located on localhost, configured with user bob.smith You send email as [EMAIL PROTECTED] from a machine with address 192.168.20.50 and use James for SMTP. Your whitelist is setup with the manager account [EMAIL PROTECTED] In config.xml: <servernames> .... <servername>localhost</servername> <servername>smithsemporium.com</servername> .... </servernames> <smtpserver> .... <authorizedAddresses>127.0.0.0/8, 192.168.20.0/255.255.255.0</authorizedAddresses> .... </smtpserver> Sending messages as [EMAIL PROTECTED] from 192.168.20.50 will be seen as local, and although SMTP authorization is enabled it won't be necessary (sending from an authorized address) so you might not need the SMTPAuthSuccessful match - mine is set to All. My James server is not exposed directly exposed to the outside. -- View this message in context: http://www.nabble.com/Whitelist-feature-configuration-tp15065351p15113964.html Sent from the James - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
