> 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.
I don't have access to the web-site right now, but I am fairly sure that
this issue is already documented. Also, at the top of SAR-INF/config.xml it
says to check all of the CONFIRM and CHECKME entries. The anti-relay
provision says:
<!-- CHECKME! -->
<!-- This is an anti-relay matcher/mailet combination -->
and then goes into additional detail regarding what you need to do.
> 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> -->
BAD IDEA (as you said later) unless you know that no one else can reach your
server, or are using SMTP authorization. Otherwise, you turn your server
into an Open Relay.
> 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
The correct thing to do is to ADD your subnet(s) to the list of allowed
addresses. In James v2.2, the equivalent code is supported directly in the
SMTP handler, providing an SMTP response in the tranaction rather than
sending the message to the spam processor.
--- Nel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
