I wrote a small post about how the mail header is to be understood for spam-mails, when the additional lines are written to the header and how the mails with Dovecot / ISPConfig end up not in the inbox, but in the junk folder. The article can be found here: […]
We regularly publish new rules for SpamAssassin. Most of the rules have a score from 5. You can use our Ruleset for free. Just add our update-Channel to your SpamAssassin-Config our use our Script to get new / updated Rules. Don’t forget to restart amavis after installing / updating rules. […]
With the Antispam plugin from Dovecot, new spam mails can be pushed by hand into their own IMAP folder. Mails that are moved to this folder, spamassassin learns as spam mails. If a mail is moved from this folder (for example to the INBOX because it is not spam), spamassassin […]
The script wp-spamreport.php (as a download here in my git) reports at any time the spam comments of the last 48 hours to blocklist.de. It does not matter when a comment was marked as spam (manually or automatically by example Antispam Bee), but only that the comments are posted in […]
DMARC extends SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) and is stored as a TXT record in the DNS. DMARC is officially still a draft, but is already supported by many vendors – and it can not hurt. A very simple DNS entry looks in bind like this: […]
I use SPF records for many years. My implementation of SPF records in ISPConfig occurred to me to point out the advantages again. SPF is an authentication method that is stored in the DNS. This entry specifies which server can send mail for a particular domain. And why do I […]
I use postscreen postscreen to prevent spam mails. Potential spam messages are rejected directly before they reach the server and the content must be scanned. You shouldn´t use postscreen if a Mail-User-Agents (MUAs) should be able to connect. Usually the TCP-Port 25 is only used for Mail-Transfer-Agents (MTAa) since MUAs […]