3 ms·
Another thing to do: if your mailgun email to gmail gets inexplicably marked as spam (as opposed to DKIM failing), try creating a new fresh gmail account and se
by DonHopkins 12y ago
Another thing to do: if your mailgun email to gmail gets inexplicably marked as spam (as opposed to DKIM failing), try creating a new fresh gmail account and see if email to that gets marked as spam. I was using an old gmail account and its filters were full of cat fur, which was causing stuff to randomly get marked as spam. Spent days playing high-low game deleting parts of the message then adding parts back in trying to figure out which words were triggering it, and it was totally non-deterministic. But once I switched to a fresh gmail account, it worked just fine, and nothing went into the spam folder.
- danieltillett 12y agoThis is what drives me crazy about avoiding spam filters. When I email out quotes to customers (initiated by the customer of course) a certain percentage of emails never make it. There is no rhyme or reason to it (all the obvious things like DKIM, spf, etc are OK), it just seems to be random. Microsoft seems to be the worst offender, but it happens on occasion with gmail and yahoo too. Very frustrating.
- jorangreef 12y agoYes, the problem is that many MX servers do not have their spam defences setup in the right order, especially in the case where you reply to someone who has already emailed you: The recipient's server should always check if your email is authenticated (SPF, DKIM). If so, they should check if their user has emailed you in the past, and if so they should let your email through, to prevent it being marked as a false positive. They should try and do this even if your domain happens to land on a single DNS blacklist (or they should use a quorum of DNS blacklists).
- timmipetit 12y agoThanks for the advice, we've had some strange situations where our mails got marked as spam. Currently we only have issues with Outlook. Mails send using Mailgun often get marked as spam, while (the same) mails send using Gmail don't have this problem. Unfortunately, this doesn't seem to happen on all Outlook installations/instances, and Outlook is pretty much a black box to test. Perhaps this could be similar issue (we've had no issues on a clean Outlook installation). Anyone else with similar problems?