Thank you for responding Stefano. > In many years everytime an user reported JAMES being used for spam it > was a configuration issue or it was not true. So let's analyze it before > spreading the word ;-) >
I wasn't trying to say that I can't have misconfigured JAMES. I think JAMES is great and I recommend it to people every chance I get. I'm simply trying to track down how the spam is being sent. > This has nothing to do with being a relay for spammer. You probably > failed to correctly setup the reverse resolution for your IP or to > configure the HELO name for your services according to it. Okay. It simply seemed unusual to me because in the course of using JAMES for several years to send all of my mail I've never encountered a message like this. The server's got a DNS A record pointed at it for mail.mydomain.com. The MX records are pointed at this. The reverse DNS for the server's IP address is mail.mydomain.com. Various web-based testing tools like http://www.mxtoolbox.com/ tell me that the reverse DNS is OK. Is this the correct setup? Are there any other testing tools I should use? In my apps/james/SAR-INF/config.xml file I've got this line: <mail.smtp.localhost>mail.mydomain.com</mail.smtp.localhost> Which the comments in that file say is what sets the HELO name. > > JAMES does not support source routing. This means that > <recipientname%recipientdom...@[my.server's.ip.address]> is a perfectly > valid local mailbox. > > The mailbox is named recipientname%recipientdomain and JAMES will never > try to deliver it to recipientdomain. "%" to James is a simple char like > "a" or "b". > > > So my question is, is this the expected behavior? > > Yes. > In that case, what do you think my next step should be? Should I set up an ethernet capture on the server to try to catch some of the SMTP traffic? Thanks again, Ken _________________________________________________________________ We are your photos. Share us now with Windows Live Photos. http://go.microsoft.com/?linkid=9666047
