Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Major European payment processor can't send email to Google Workspace users

atha.io

Post reply on HN
Print view View original

441–443 of 443 posts

Re: Major European payment processor can't send email to Google Workspace users

#441

Post by tracker1 »

eli wrote: post #231
tracker1 wrote: post #222

Earlier quoted context omitted.

You have to have a working mail server attached to a domain to be able to send mail... that's the big part. Right now, email can more or less come to anywhere from anywhere as anyone. There are extensions for signing connections, tls, etc... but in general SMTP at it's core is pretty open and there have been efforts to close this. It would simply close the loop and push the burden of the messages onto the sender's sy…

Like it proves you have the ability to receive mail at the domain you're sending from? I feel like SPF/DKIM already does this

SPF doesn't prove that... I can send through SendGrid with an SPF record, doesn't mean I've got a server configured to receive mail... for that matter, it actually makes it so you HAVE to be responsible for the mail system and cannot outsource sending separately from receiving. Again, shifting the burden enough to where other measures of dealing with bad actors are more effective.

Re: Major European payment processor can't send email to Google Workspace users

#442

Post by vel0city »

stdbrouw wrote: post #381
vel0city wrote: post #319

Earlier quoted context omitted.

You should wear sunscreen to the beach. Its recommended as a good way to prevent sunburn. However, the beach police aren't going to come get you for not wearing it. You just might get a sunburn if you don't plan accordingly with other sun countermeasures.

So if I send an email that lacks a feature that MUST be there, will the email police come get me? At a certain point, looking for an analogy stops making sense I think.

I mean, kind of, yeah? If you're sending traffic that fails to meet the MUST requirements, you're probably going to be marked as malicious traffic and eventually wind up on spam/bot lists. If you fail to do the SHOULD things, you might find yourself in some odd edge cases of your peers and experience behavior you didn't expect.

Re: Major European payment processor can't send email to Google Workspace users

#443

Post by gessha »

josephg wrote: post #240
stackskipton wrote: post #155

Earlier quoted context omitted.

As someone else who does System Engineering, when dealing with ancient protocols, "shall" is extremely difficult barrier to get over since there is always ancient stuff out there and there might be cases not to do it, esp if it's internal communication. "SHOULD" is basically, if you control both sides of conversation, you can decide if it's required looking at your requirements. If you are talking between systems whe…

> … when dealing with ancient protocols I’m doing some work with an email company at the moment. The company has been in the email space for decades. Holy moly email is just full of stuff like this. There is an insane amount of institutional knowledge about how email actually works - not what the specs say but what email servers need to actually do to process real emails and deal with real email clients and servers.…

The Computer History Museum [1] has a YouTube channel where they post interesting interviews. You can pitch it to them.

[1] https://computerhistory.org/

Post reply on HN