New answers tagged

1

Postfix Header Checks Blocking double extensions can be done with regex. Here is an example of how to block any extension. Create /etc/postfix/header_checks and maybe block some of these extensions Modify as required: Here are 2 ways to do the same thing you asked for. # do something with JS files # # method 1, much like what you asked for ...


0

As pointed out by the accepted answer, there are a couple of conmponents to get this to work. I have had both spamassassin and spamass-milter installed. However, during the setup, i misunderstood how to setup the sockets so here are the relevant files/lines First /etc/default/spamassassin : OPTIONS="-x --max-children 5 --nouser-config --helper-home-dir ...


2

If I understand things correctly then spamassassin (or spamd, as you are using here) can not directly be used as a milter. You need spamass-milter in addition to spamassassin. See here: http://www.stefan-seelmann.de/wiki/mailserver-postfix-dovecot or here: https://www.nesono.com/node/220 for reference.


0

As far as the internet is concerned, host.example.eu and example.eu are two completely different domains. Therefore if you want to block sub domains then you will need to have something like @ * .*.eu (if the tool that you are using can support the double wildcard).


0

My solution to this was to configure Dovecot's built-in antispam/mailtrain feature to pass messages to a script as spam/ham when they are transferred to/from my junk mailboxes respectively, so that they can be learned using a cron-job. While it's possible to pass the messages to sa-learn directly this could mean learning accidental mis-filings, plus it's ...


0

Put the following line in your local.cf: report_safe 0 The spam information will still be available in the header, but it will not change the body of the email.


3

You could give this package a try instead: libmail-dkim-perl One of the walk-throughs linked in the Spamassassin documentation points out a hint that I would recommend to follow: "You should NEVER need to use CPAN on a RPM or DEB based Linux distribution."


0

This happend because of the missing perl module Mail::DKIM. Without that, every mail with dkim signature will fail the verification. Even those with correct signature. You can find futher information about it here. A simple fix is to install the missing module via cpan.


1

If you combine the smtpd_sender_restrictions = check_client_access cidr:/etc/postfix/internal_clients_filter from the answer you found with these instructions for clamsmtp incoming filtering (excluding the content_filter paramater and replace: 192.168.0.0/24 FILTER smtp:[127.0.0.1]:12501 with 192.168.0.0/24 FILTER scan:[127.0.0.1]:10025 ...


-1

I think the main problem might be the following commit in spamassassin's sources made on December 16th 2015 which could be a good guess as this is the time about when the problem started: https://github.com/apache/spamassassin/commit/aa98a1573458f8df5ebe4338eaa99eeba69d4876#diff-c34e50f996b2140fbdc2454bfbfb6267



Top 50 recent answers are included