Solved my own problem:
I've moved the 'RemoteAddNotInNetwork' matcher to the transport
pipeline, after local addresses have been dealt with but before James
attempts remote delivery. I think this works correctly, now.
Charles
Charles Benett wrote:
>
> The good news is that almost everything seems to be working, so release
> is near.
>
> However, :-)
> There is a gremlin in the default set-up for anti-spam. Any messages
> from external networks for me get dumped to spam. Obviously its a
> configuration issue.
> What I don't understand, conceptually, is how it is supposed to work
> with only one argument. As I understand it, SenderIsFakeDomain does what
> it says and is OK. RemoteNotInNetwork, though I don't get. What I think
> we want to achieve is to stop relaying, ie:
> (mail from remote network) & (mail to remote network) = relay => spam
> but the effect seems to be
> (mail from remote network) = relay => spam.
>
> Thoughts?
>
> Charles
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
