4 ms·
It's kind of a pointless question when you haven't provided any details. Are you self hosting? If not, which provider? Are you using an email delivery service?
by Flankk 4y ago
It's kind of a pointless question when you haven't provided any details. Are you self hosting? If not, which provider? Are you using an email delivery service? Have you correctly configured DKIM and SPF?
To answer your question, no you cannot force them to do anything. Either fix it yourself or hire someone who can fix it for you.
- kuboble 4y agoYes, we have all DNS settings configured correctly. We use big email provider to send emails (Gmail & fastmail). We send order emails via smtp client. We already did try to figure out why our emails are marked as spam including external help and available support channels and do follow all known good practices. I'm not looking for advice on how to make my email not look like spam to their systems. Please assume for the sake of the quotation that we did due diligence here. I'm really asking if there is a precedence for someone trying to sue big company for damages caused by their refusal to not mark legit emails as spam.
- maroslah 4y agoSome companies use also plaintext emails to improve deliverability https://useplaintext.email/ https://useplaintext.email/
- g_p 4y agoPlaintext vs HTML email is an interesting one - I found that getting deliverability to MS 365 from a very low volume, self-hosted email server was actually improved by sending in HTML format, as opposed to plaintext. This was the exact opposite of what I expected, but every other reasonable variable was controlled as much as possible.
- iamhamm 4y ago> I'm really asking if there is a precedence for someone trying to sue big company for damages caused by their refusal to not mark legit emails as spam. No. Email is an altruistic delivery system per the RFC. You have no right to have your email delivered at all, let alone a right to have it marked as not spam. You should assume your email is still triggering the undesired spam label because of your configuration, content, or delivery approach and try to resolve that.