I am a relative new-comer to the James world and I was just able to solve a problem that it appears (from searching the logs) that many newcomers have had related to the default configuration of James.
Now the default configuration is definitely doing the right thing by blocking outgoing mail from hosts other than localhost. That is smart and kudos to whomever came up with that. However it is not clear how you stop James in its default configuration from eating all of your mail.
There is one section of the instructions that is somewhat clear, that you must setup a DNS server (if localhost is not your DNS server) and that you must specify the hostnames of the domains that this email server will service. The one are that is NOT clear is that if you don't setup authentication for your mail server and tell James to not eat mail not routed for localhost your mail will disappear 'silently'. It took me roughly a day to figure out that I need to do:
<!--
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
<processor> spam </processor>
<mailet> -->
(i.e. for the newbies reading this, you need to comment out the maillet that looks at the remote address of all of the mail and turns anything that is not headed to your localhost machine to spam - grep for this in config.xml and comment it out ONLY ONLY ONLY if you've turned authentication on for your email server - else you'll likely end up as a spam source)
in order for James to not route all of the email from the users of this server to the spam processor. This definitely needs to go into the FAQ and any quickstart guide that is out there or might be in the works. Will save many people some frustration.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
