"Send reconfirmation emails to people that have not interacted with your email (no opens or clicks)" How can I check opens? I'm not aware of any reliable way to check this. Mail clients not loading pixels means the software is unaware of opens?
Same way as always, image loading. If image URLs are unique and external then you can track their opening. Not all users will allow it so you also track clicking on in email links.
Show HN: Mailready – meet the new email deliverability standards
11–20 of 39 posts
Re: Show HN: Mailready – meet the new email deliverability standards
#12Re: Show HN: Mailready – meet the new email deliverability standards
#13Our domain checks out because we use O365. However, we have an old Exchange server sending out via SMTP. We're not sure what the best path forward is for us. Do we change our apps to route through O365? Will probably take days for that. We have in house custom apps that use it heavily. Anyone have good resources on what we should do?
Re: Show HN: Mailready – meet the new email deliverability standards
#14My best friend works at a large ISP specifically on their email transport system. They discard 97% of the emails they receive. That's straight into the bit bucket, not to your Junk Mail folder.
Re: Show HN: Mailready – meet the new email deliverability standards
#15> What happens if I dont comply? >You get marked as spam? And that's probably the best case scenario. Your email may not get delivered. My best friend works at a large ISP specifically on their email transport system. They discard 97% of the emails they receive. That's straight into the bit bucket, not to your Junk Mail folder.
Re: Show HN: Mailready – meet the new email deliverability standards
#16i want to send email to my friends at google. yet google blocks delivery.
this is not any kind of business or commercial messages. but from my private account to my friends account.
SPF and DMARC check out and surely private emails should not need unsubscribe headers. so your site says everything is fine. then why does google still reject my emails?
Re: Show HN: Mailready – meet the new email deliverability standards
#17> What happens if I dont comply? >You get marked as spam? And that's probably the best case scenario. Your email may not get delivered. My best friend works at a large ISP specifically on their email transport system. They discard 97% of the emails they receive. That's straight into the bit bucket, not to your Junk Mail folder.
hotmail or comcast? My users complain about email just disappearing, no bounce, no spam folders, just gone.
Re: Show HN: Mailready – meet the new email deliverability standards
#18this doesn't seem to help for private email. i want to send email to my friends at google. yet google blocks delivery. this is not any kind of business or commercial messages. but from my private account to my friends account. SPF and DMARC check out and surely private emails should not need unsubscribe headers. so your site says everything is fine. then why does google still reject my emails?
I really hope that this kind of stuff gets illegal: just taking an email and virtually burning it.
Re: Show HN: Mailready – meet the new email deliverability standards
#19this doesn't seem to help for private email. i want to send email to my friends at google. yet google blocks delivery. this is not any kind of business or commercial messages. but from my private account to my friends account. SPF and DMARC check out and surely private emails should not need unsubscribe headers. so your site says everything is fine. then why does google still reject my emails?
Multiple options. For example, your IP address may not have a good reputation. This can happen when a previous tennant used your IP address to send spam, but it also happens when you send very little email to Google/Microsoft servers, not giving you the opportunity to build a good reputation. I briefly considered sending my mail server logs to Gmail so I could get regular whitelisted email delivered, but I changed my mind when I realised Google would probably mark my domain as a bot.
This seems particularly bad on IPv6 for some reason. I'm not sure why, maybe it's because their spam filters are treating every address as a /128 rather than a /64 network?
The worst server in my experience is Microsoft Exchange. I caught the stupid platform taking my email, _rewriting the email address because it didn't like it (despite being compliant!)_, and _then_ checking the DKIM signature, which obviously failed. It doesn't have IPv6 deliverability issues, though, because like many Microsoft cloud products, it doesn't even support IPv6. Microsoft Outlook also sometimes fails the SPF check... because of DNS issues _on Microsoft's side_.
None of this is standards compliant, of course. The best you can do is DKIM+SPF+reverse PTR+strict DMARC+DNSSEC+DANE+using some expensive data center so there aren't many spammers in the nearby IPv4 blocks. Most of these can be generated automatically through online tools or ready-out-of-the-box email servers such as Mailinabox or Mailcow.
Also, _check your configuration regularly_, set up alerts or something; sometimes something may break and your domain/email address will start losing reputation.
It's infuriating to get email delivered, even if you do everything right. I've given up on that stuff, though, and tell everyone I email to check their spam folder and move it to their inbox to train their spam filter.
Re: Show HN: Mailready – meet the new email deliverability standards
#20Basic XSS - https://mailready.info/authentication?domain=grepular.com
Thanks for this. Will fix.
https://datatracker.ietf.org/doc/html/rfc7208
> Unrecognized modifiers MUST be ignored no matter where, or how often, they appear in a record. This allows implementations conforming to this document to gracefully handle records with modifiers that are defined in other specifications.
A correct SPF validator will ignore the xss modifier, not treat the SPF record as invalid.