----- Original Message -----
From: "Charles Benett" <[EMAIL PROTECTED]>
> 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.
Understood. I just saw a patch go through on JAMES.conf.xml, so you may
have already done this, but this is actually pretty easy. It's just a
question of moving that RemoteNotInNetwork check from where it is in the
root processor to just before the remote delivery mailet in the transport
processor.
Things are working pretty well for me with JAMES in production. I've
somewhat given up on the case sensitivity issue for the localpart of email
addresses... I haven't figured out something that really makes sense, so
until that solution emerges, JAMES can just be case sensitive there. I am
going to add the mailet for the Postmaster aliasing (aliasing all the
postmaster@servernames to the postmaster account specified).
I also have to commit some documentation tonight... today is Wednesday... we
about ready to branch and release? :)
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
