Live data from Hacker News

Show HN: Mailready – meet the new email deliverability standards

mailready.info

31–39 of 39 posts

Re: Show HN: Mailready – meet the new email deliverability standards

#31

Our 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?

There's an oss dikim signing transport plugin for on prem exchange that has become somewhat a standard in this space.

https://github.com/Pro/dkim-exchange/releases

Re: Show HN: Mailready – meet the new email deliverability standards

#32
post #24
post #16

this 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?

My social group has been shifting away from using the internet-wide email system to using a private one just among us that we run. It works well in my group because most of the emails we send/receive are amongst ourselves anyway. All of these antispam measures are fighting a losing battle -- every one of them reduces the utility of email and are only (barely) acceptable because spammers reduce the utility of email to…

But running an email system that does not connect to the wider internet also ruins the idea of email as a globally reachable address. Everything is a trade-off :-|

Re: Show HN: Mailready – meet the new email deliverability standards

#33

Earlier quoted context omitted.

I have seen something similar at a smaller ISP, but the silently discarded email usually came from domains with bad SPF setups. Really infuriating, because customers would not believe that this wasn't a problem on our end, it was the other side telling us to discard their email!

SPF alone is not a reason for discarding a letter.

It shouldn't be, but the standard is not clear.

The spec is very dodgy in that it acknowledges that every server needs to pick its own policies:

> Disposition of SPF fail messages is a matter of local policy.

On silently dropping email, the following is listed as a "consideration":

> Other dispositions such as "dropping" or deleting email after acceptance are inappropriate because they leave uncertainty and reduce the overall reliability and utility of email across the Internet.

There is no MUST (NOT) in the spec when it comes to silently dropping email.

The intent of the author of the spec is to always provide feedback, but it doesn't actually say that in cleae terms.

Re: Show HN: Mailready – meet the new email deliverability standards

#34
post #16

this 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?

> 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 regula…

Exchange is an abomination. A few hours trying to do something with groups was enough to see that for me. As a QA I would reject it until 100 or so bugs were fixed (that I saw in a few hours of use, so maybe 10k+ bugs total?)

Re: Show HN: Mailready – meet the new email deliverability standards

#35
post #24
post #16

this 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?

My social group has been shifting away from using the internet-wide email system to using a private one just among us that we run. It works well in my group because most of the emails we send/receive are amongst ourselves anyway. All of these antispam measures are fighting a losing battle -- every one of them reduces the utility of email and are only (barely) acceptable because spammers reduce the utility of email to…

Hah... somehow i have this feeling that we are heading right back into the "good old days" of separated BBS networks, some commercial, some private, but none of them interconnected.

Somehow i like the thought of this...

Re: Show HN: Mailready – meet the new email deliverability standards

#36
post #32
post #24

Earlier quoted context omitted.

My social group has been shifting away from using the internet-wide email system to using a private one just among us that we run. It works well in my group because most of the emails we send/receive are amongst ourselves anyway. All of these antispam measures are fighting a losing battle -- every one of them reduces the utility of email and are only (barely) acceptable because spammers reduce the utility of email to…

But running an email system that does not connect to the wider internet also ruins the idea of email as a globally reachable address. Everything is a trade-off :-|

True, but I think the days of email as a globally reachable address are already on their way out. It's not exactly unheard of for some people to be unable to send email to addresses hosted by some common mailservers (including gmail) right now.

However, none of my friends use our mailservers exclusively. They also use the internet mail system. But having our own means that we don't have to worry about deliverability issues, spam, or any of the other problems that exist on the public system.

Re: Show HN: Mailready – meet the new email deliverability standards

#37
post #24

Earlier quoted context omitted.

My social group has been shifting away from using the internet-wide email system to using a private one just among us that we run. It works well in my group because most of the emails we send/receive are amongst ourselves anyway. All of these antispam measures are fighting a losing battle -- every one of them reduces the utility of email and are only (barely) acceptable because spammers reduce the utility of email to…

Hah... somehow i have this feeling that we are heading right back into the "good old days" of separated BBS networks, some commercial, some private, but none of them interconnected. Somehow i like the thought of this...

We've already done this. In effect, we're running a private "internet" that uses the public internet as one of the communications channels, but does not interact with any internet servers beyond that.

It's really beautiful and freeing to have an "internet" that works really well, even if it is a very tiny one.

Re: Show HN: Mailready – meet the new email deliverability standards

#38

Earlier quoted context omitted.

SPF alone is not a reason for discarding a letter.

It shouldn't be, but the standard is not clear. The spec is very dodgy in that it acknowledges that every server needs to pick its own policies: > Disposition of SPF fail messages is a matter of local policy. On silently dropping email, the following is listed as a "consideration": > Other dispositions such as "dropping" or deleting email after acceptance are inappropriate because they leave uncertainty and reduce th…

[deleted]

Re: Show HN: Mailready – meet the new email deliverability standards

#39

> 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.

I have seen something similar at a smaller ISP, but the silently discarded email usually came from domains with bad SPF setups. Really infuriating, because customers would not believe that this wasn't a problem on our end, it was the other side telling us to discard their email!

You wanna know what's worse? There is an SPAM Scoring Monoculture, dominated by BrigthWorks, Symantec and another firm that escapes my mind right now. So if users flag enough of your email as Junk on an ESP using one of these providers, your domain is banned or auto-Junked with all that company's other customers.
Post reply on HN