fractals wrote:
>
> Sorry to bother you with this. This is not a developer issue but a user one.
> I asked this question already a couple of times to the user mailing-list,
> but I could not get a working answer.
>
> I think what I am trying to do in very simple and basically everyone should
> be able to do it:
>
> To avoid relaying I just want mails whose Sender is not a local user to be
> considered as spam. That's all folks !
which is exactly what the mailet does.
>
> It seems to me that the basic anti-relay mailet is meant just the other way
> around:
>
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
> <processor>spam</processor>
> </mailet>
>
> Doesn't this mean that the *recipient* is not allowed to be on a remote
> server ? How do local users send mail to the outside world then ? This
> really doesn't make sense to me... I already tried to put ",urbanium.tv.*"
> after the "127.0.0.1" and ",194.183.224.*" which are the 3 first numbers of
> the IP address of my server, all this without much confidence. But anyway
> none worked.
>
> PLEASE help me on this, I'll be a much more enthusiast James users for the
> advanced capabilities it offers (which is why I *do* want to use it as my
> mail server) when I know my users can use them to send e-mail !!!
>
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.
As for naming, the remote address here is the ip address from which the
mail came. You set it to your own network(s). So you can read the
mailet/matcher combo as: "if the sender's ip address is not in my
network, its spam".
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
