Am 17.02.2015 um 20:38 schrieb ricky gutierrez:
this solution looks cool , I was thinking of putting another server
with a specific account and through transport map from the gw send
e-mail server to another server with a specific account.

I was looking for how to handle this with postfix

where the ccount lives don't matter

the only resticiton is that "header_checks" BCC in Postfix 3.0 only works for "header_checks" and *not* "smtp_header_checks", hence it need to be defined on the downstream server instead on the MX

where the target address itself is located don't matter, postfix just generates a BCC and sends it to that local or remote address

but be sure you consider the legal implications!

2015-02-17 13:14 GMT-06:00 Reindl Harald <h.rei...@thelounge.net>:


Am 17.02.2015 um 20:03 schrieb ricky gutierrez:

Hi , I have mounted one gateway filtering me all spam in the business,
I have to postfix + centos6.6 + amavisd-new 2.8 + clamav +
spamassassin, currently captures 65% of spam the other 35 gets
through, I want to improve the effectiveness making a Bayesian db.

I am not an expert in postfix and spamassassin, I was thinking to
leave a copy of all messages for the domain and classify emails as
spam and ham, and then build the db, the problem is that postfix is
only a gateway and leaves no emails locally! ,

someone has faced this type of situation?


update to Postfix 3.0 and use the new BCC feature for header_checks on the
*downstream servers* to use that as training data *but* be sure you place a
sieve rule there to discard all the BCC's to users without a explicit opt-in
for *legal* reasons!

and protect that BCC account from receive mails on the MX!
_________________________________________________

the sieve rule just lists the subscribed Users in the To/Cc-Header with
'keep' and the elseif 'discard'

if you want to optimize that add your own enevlope-headers on the MX which
covers also BCC and can be used by the sieve-rules instead From/Cc
http://comments.gmane.org/gmane.mail.postfix.user/193456
_________________________________________________

main.cf:
header_checks = pcre:/etc/postfix/header_checks_smtpd.cf
nested_header_checks =
mime_header_checks =

/etc/postfix/header_checks_smtpd.cf:
/^X\-Spam\-Flag: Yes/ BCC spamfil...@thelounge.net
/^X\-Spam\-Report: Flag: No.*(BAYES_80|BAYES_95|BAYES_99)/ BCC
spamfil...@thelounge.net
/^X\-Spam\-Report: Flag: No.*(BAYES_50)/ BCC
spamfilter+inbox...@thelounge.net

Spamassassin local.cf:
clear_headers
fold_headers 1
add_header spam Flag _YESNO_
add_header all Status _YESNO_, score=_SCORE_, tag-level=_REQD_,
block-level=8.0
report_safe 0
add_header all Report Flag: _YESNO_, _REPORT_
rewrite_header Subject [SPAM]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to