Hacker News Reader

Comment by dwd | Hacker News Reader

I would also recommend setting up a dmarc record so you can monitor your deliverability.

Spam however is still a hassle and you're never going to match Gmail or Outlook when you're small. Say it takes a few hundred identical spammy emails to trigger a filter. For Gmail it means the chance of receiving that spam is less than 1 in a million. If you're small and managing say a 1000 users - a large percentage will end up with receiving the spam.

View on HN

You can't actually measure deliverability with dmarc reports. They will only tell you the portion of emails that are bounced, but they don't differentiate between email in inbox and email in spam folder.

Wrong word - delivery rather than deliverability. You just want to know about the SPF and DKIM fails.

Last thing you need someone on a self-hosted email server is running EDM campaigns.

SPF and DKIM are best practices to get delivered to the inbox and DMARC reports are the richest source of aggregate email authentication performance results.

However, you are correct, DMARC reports will not provide the disposition of an email getting delivered to the inbox or spam folder. The report is generated based upon the transaction at the MTA level before the message is handed off for delivery.

>Say it takes a few hundred identical spammy emails to trigger a filter

Wait, is this really the way how spam filters work? All I need to do is to add a random number to all emails to bypass spam filters?

In essence this is one of the principles, the thing is the emails don't need to be perfectly identical, just identical-ish with the identicalish matching implementation being not public (as this would immediately lead to spammers adding just enough randomness to whatever they are sending)

In short, no.

Reply on news.ycombinator.com