: The following works fine on James 1.2.1:
:
: <mailet match="RemoteAddrNotInNetwork=127.0.0.1,192.168.1.*"
: class="ToProcessor">
: <processor>spam</processor>
: </mailet>
:
:
: Do use ip addresses, don't use domain names.
: As the note in James.config.xml says - order of mailets is important.
: This comes after local delivery and before remote delivery.
This is my exact configuration (transport processor):
<mailet match="RecipientIsLocal" class="LocalDelivery">
</mailet>
<mailet match="HostIsLocal" class="ToProcessor">
<processor>spam</processor>
</mailet>
<mailet match="RemoteAddressNotInNetwork=127.0.0.1,192.168.1.*"
class="ToProcessor">
<processor>spam</processor>
</mailet>
<mailet match="All" class="RemoteDelivery">
I used 192.168.1.* because you just told me to, but as I said I already
tried 194.183.224.* which are the 3 first numbers of the IP address of my
machine, without success. BTW, I already noted that local networks often
have addresses beginning with 192.168.111... Perhaps you know why...
The latter configuration still generates error reports in the form:
We were unable to deliver the attached message because of an error in the
mail server.
Message details:
Subject: fjdskqmfqsdkljfqmsdfj
Sent date: Tue May 15 15:44:28 GMT+02:00 2001
To: fractals <[EMAIL PROTECTED]>
Size (in bytes): 2
BTW2, I *can* send an email from a local user to another local user which
led me to think that the anti-relay mailet was really discarding remote
recipients and not remote senders.
Still very, very confused...
Thanks anyway ! :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
