Hi Noel,
The email from gmail.com in my example log comes in on port 25 - the 1st
line in master.cf. If I leave the "-o
content_filter=lmtp:unix:/tmp/dspam.sock" in instead of removing it,
then authenticating users who choose to use port 25 in their email
clients will also go through dspam as well as non-authenticating users.
That is why I need to have this:
main.cf
---------
smtpd_client_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
.....
check_client_access pcre:/etc/postfix/dspam_filter_access
so that authenticating clients bypass the content filter (regardless if
they use ports 25 or 587) and non-authenticating clients get caught by
the check_client_access line at the end, which puts them through dspam,
but _unfortunately_ before queue.
Cheers,
Chris
On 18/05/2012 17:34, Noel Jones wrote:
On 5/18/2012 7:41 AM, Chris wrote:
Hi everyone,
I am having a problem trying to run dspam as an _after-queue_
content filter on postfix with the
restriction that sasl authenticated users bypass dspam. All my users
and domains are virtual.
When I first installed postfix/dspam/dovecot I did not worry about
excluding my authenticating
users from dspam filtering, with the result that all mail was tagged
by dspam which ran as an
after-queue content filter.
You're making this too hard. Just set in master.cf
submission ...
-o content_filter=
to unset the content_filter setting for mail coming in through the
submission port, and don't bother with access tables and whatnot.
As for your other questions, be assured that dspam is still running
after-queue. You probably have some problem in your access maps, or
in one of the smtpd_*_restrictions that you didn't show.
If you need more help, please see
http://www.postfix.org/DEBUG_README.html#mail
-- Noel Jones
!DSPAM:4fb66c1c193099249720649!
