4 ms·

I use the mail server of my hosting provider. It is a cheap mass hosting provider that offers mails for free or almost for free when you have a domain with them

by TekMol 4y ago

I use the mail server of my hosting provider. It is a cheap mass hosting provider that offers mails for free or almost for free when you have a domain with them. Do you mean their IP? When I send one of my confirmation mails to mail-tester.com, I get 9/10: + SpamAssassin likes you - No DKIM - Your message does not contain a List-Unsubscribe header + You're not blacklisted

Nextgrid 4y ago
I mean the IP of whatever will end up talking to the mail servers of your recipients - it may be, though is not always, the IP of the SMTP server your sending code is talking to. In general when it comes to hosting providers, if they're doing shared hosting you're guaranteed to have some compromised Wordpress/etc crap that will be spamming and will tank the deliverability of everyone using this hosting provider's email server (and their IP ranges in general). In addition, beyond public blacklists that Mail-tester/etc can query, big email providers maintain their own private ones which you can't query and don't know the inner workings of it. Microsoft is a major pain in this regard.
- TekMol 4y ago
  Why would Google need to base their spam detection on IP alone? If they see low "mark as spam" ratios for my mails, why would they care if they come through the same IP as spam from compromised wordpress instances?
  - Nextgrid 4y ago
    In general, even DKIM and a clean domain isn't a safe indicator of non-spamminess. It doesn't take much effort nor cost for a spammer to get a new domain, set up DKIM/etc correctly and then start spamming, and those emails would appear as "clean" as yours do. Therefore they use extra heuristics including the source IP ranges. Plus in your case your current mail tester result suggests you don't even have DKIM set up, so as of right now there's literally no way for a recipient server to tell your email apart from a spammer impersonating you. (to be clear I'm not defending the practice, just explaining my understanding of the current situation)
    - TekMol 4y ago
      you don't even have DKIM set up, so as of right now there's literally no way for a recipient server to tell your email apart from a spammer impersonating you. Coudln't they do that via SPF?
      - Nextgrid 4y ago
        SPF is less of a guarantee - if your SPF policy whitelists a shared email server then anyone using that can still impersonate you. DKIM is a stronger guarantee as it requires having access to a signing key.

by TekMol 4y ago

Nextgrid 4y ago

I mean the IP of whatever will end up talking to the mail servers of your recipients - it may be, though is not always, the IP of the SMTP server your sending code is talking to. In general when it comes to hosting providers, if they're doing shared hosting you're guaranteed to have some compromised Wordpress/etc crap that will be spamming and will tank the deliverability of everyone using this hosting provider's email server (and their IP ranges in general). In addition, beyond public blacklists that Mail-tester/etc can query, big email providers maintain their own private ones which you can't query and don't know the inner workings of it. Microsoft is a major pain in this regard.

TekMol 4y ago
Why would Google need to base their spam detection on IP alone? If they see low "mark as spam" ratios for my mails, why would they care if they come through the same IP as spam from compromised wordpress instances?
- Nextgrid 4y ago
  In general, even DKIM and a clean domain isn't a safe indicator of non-spamminess. It doesn't take much effort nor cost for a spammer to get a new domain, set up DKIM/etc correctly and then start spamming, and those emails would appear as "clean" as yours do. Therefore they use extra heuristics including the source IP ranges. Plus in your case your current mail tester result suggests you don't even have DKIM set up, so as of right now there's literally no way for a recipient server to tell your email apart from a spammer impersonating you. (to be clear I'm not defending the practice, just explaining my understanding of the current situation)
  - TekMol 4y ago
    you don't even have DKIM set up, so as of right now there's literally no way for a recipient server to tell your email apart from a spammer impersonating you. Coudln't they do that via SPF?
    - Nextgrid 4y ago
      SPF is less of a guarantee - if your SPF policy whitelists a shared email server then anyone using that can still impersonate you. DKIM is a stronger guarantee as it requires having access to a signing key.