Trying again, it didn't show up on the list...
-------- Original Message --------
Subject: RELAYCLIENT setting when spamdyke is authenticating
Date: Sun, 21 Nov 2010 14:52:14 +0100
From: Bgs <[email protected]>
To: spamdyke users <[email protected]>
Hi,
I might be the one misinterpreting the docs, but something is strange
for me.
The setup:
spamdyke with auth/access file + qmail-scanner with spamassassin
In my access file I have localhost with RELAYCLIENT and no
qmail-scanner, all other without RELAYCLIENT and qmail-scanner.
I have relay-level set to 'normal' which according to the docs, does the
following:
|normal|: Prevent relaying unless the sender authenticates, the access
file allows relaying or an environment variable allows relaying.
Requires |local-domains-entry| or |local-domains-file| and |access-file|.
So I was expecting the following:
- Normal mail arrives for relay -> denied (does this)
- Normal mail arrives for domain in rcpthost -> do NOT set
relayclient, pass to q-s and further to qmail-smtpd which will handle it
(it doesn't do this)
- Authenticated user sends mail -> spamdyke sets RELAYCLIENT, q-s
skips checks, qmail-smtpd processes mail
The second buffles me:
- access file does not set RELAYCLIENT
- there is no environment variable passed to spamdyke
- the user does not authenticate
Apparently spamdyke also sets RELAYCLIENT when the domain is in
rcpthosts. This means that spamdyke disables spam filtering. If I
override qmail-scanner (with explicit QS_SPAMASSASSIN environment
variable) to check all mail, authenticated users get filtered as well
which leads to loads of complaints.
Am I getting something wrong or is this a bug?
Regards
Bgs
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
