From the default config.xml I received with my latest James 2.2:
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
<processor> relay-denied </processor>
<notice>550 - Requested action not taken: relaying denied</notice>
</mailet>
The above will bounce anything that isn't from localhost with a relay denied message. If you change the 127.0.0.1 to the appropriate network, James will bounce anything outside of that network, but happily relay otherwise.
Kenny
Brian C. Dilley wrote:
Hi, i'm working on an anti spam project (You've probably heard this a million or more times) and i'm considering using James as the framework for the SMTP subsystem of the software. I've been looking over the documentation and other things and was able to answer 99% of my questions. The lingering 1% is a fairly important percent, here's the basic question:
Can James be configured to be a mail relay?
Basically i want my software to sit "in front" of the real SMTP server (the one configured by a company with all of their users and other rules in place) and bounce messages that it determines is spam (so they never make it to the "real" SMTP server). The reason I don't want to use James as the email server itself is that i don't want my clients to be required to ditch their current email server which they are married to and love. I'm looking to create a turn-key solution for preventing spam which can work with any existing SMTP server as described above.
----- Linux: Where do you want to GO... Oh, I'm already there! -- Ewout Stam
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
