usr/bin/razor-check & echo -n "spam" || echo -n "ham" # chained, so only a single X-Sieve-Mark is possibleĮlsif address :localpart Įlsif address :domain :regex ["^twitter\.",Īddheader "X-Sieve-Mark" "SocialNetwork" Įlsif address :domain :regex ["debian\.",Įach time scripts are modified in this folder, sievec must be run by root (because otherwise sieve script are compiled by current user, which cannot write in /etc for obvious reasons): # simple flagging for easy per-user sorting These two will take to send through rspamd and accept/reject/discard mails.Ī dovecot_lmtp transport is also necessary: Log_message = reject mail from $sender_host_address as high-probability spam # find out if a (positive) spam level is already setĬondition = $ # because some might be forwarded by smarthost client, requiring scanning with no defer/reject # - and scan all the messages no matter the source: # - using CHECK_DATA_LOCAL_ACL_FILE included in the acl_check_data instead a creating a new acl What matters most is acl_check_rcpt definition (already used in previous version) and new acl_check_data definition.: My new setup is contained in my rien-mx package: the initial greylist system is still there. It blocks rejects/discard spam earlier and makes filtering easier in a multiuser environment (sieve is not dangerous, unlike procmail, and can be managed by clients, if desirable) The idea is to have: Exim SMTP accept with greylist and rspamd -> dovecot with sieve filtering Instead of having: Exim SMTP accept with greylist -> bogofilter -> spamassassin -> procmail -> dovecot Rspamd seems activitely developed and easy to integrate not only with Exim, the SMTP, but also with Dovecot, which is use as IMAPS server. Rspamd?įull, UTF-8 conversion/normalisation, lemmatization You filter but do not discourage or block spam sources. It means that filtering is done after SMTP-time, when the mail has been already accepted. Second, my whole setup was based on using specific transports and routers in exim to send mails first to bogofilter, then to spamassassin. For instance, the bayesian filter training cronjob had configured SPAMDIR, etc. Why changing anything then?įirst, I have more users and the system was not really multiuser-aware. I must say that almost no spam reached me unflagged for years. For more than ten years, I used SpamAssassin and Bogofilter along with Exim to filter spams, along with SFP and Greylisting directly within Exim.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |