Some notes on spam filters:
Originally Posted by
Winged Mermaid
This is because people decide they don't want the MerNetwork emails anymore (like thread subscription notifications and such), so they report it as spam instead of unsubscribing.
Depends on the spam filter (can also be per user then).
Originally Posted by
Winged Mermaid
Between that and the volume of emails that we pump out, some email servers have decided that the email is spam.
The count of mails is a valid metric to detect spam but it only increases the probability - there must be other issues as well.
Originally Posted by
Winged Mermaid
So they block the automated emails from going through, even to the spam folder. It's very hit and miss. I would fix it if I could, but so far I've had no luck.
This comes from european law: if the mail server accepts the email, in the meaning of law, the email is delivered to the recipient. For that reason, many mail servers rejects spam instead of moving to junk.
---
Another reason is might be a DMARC issue (incorrect SPF entry) in combination with the sender address. For example I have got this headers in a mernetwork mail:
Code:
Received: from << original domain >> (<< original domain >>. [<<sender ip>>])
by mx.google.com with ESMTPS id 33si...
for <<<my email>>>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Mon, 01 Jan 2018 00:00:30 -0800 (PST)
Received-SPF: softfail (google.com: domain of transitioning << mernetwork mail>> does not designate <<sender ip>> as permitted sender) client-ip=<<sender ip>>;
Authentication-Results: mx.google.com;
spf=softfail (google.com: domain of transitioning << mernetwork mail>> does not designate <<sender ip>> as permitted sender) smtp.mailfrom=<< mernetwork mail>>;
dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=gmail.com
Received: from mernetwo by << original domain >> with local (Exim 4.89_1) (envelope-from << mernetwork mail >>) id 1eVv1G-0034HW-5T for <<my email>>; Mon, 01 Jan 2018 00:00:26 -0800This means that forum emails have a spoofed sender as << mernetwork mail >> is not permitted to send mails as gmail.com. Instead the mail does come from << sender ip >>.
There are two ways to fix this:
1. Use a permitted mail server as a sender - in that case it would be sent via a gmail server and DMARC would be valid (IP of gmail + @gmail.com -> OK)
2. Use the own domain as a sender (example@mernetwork.com) which allows the original sender.
Bookmarks