Login
You're viewing the functional.cafe public feed.
  • Nov 13, 2026, 2:07 PM

    @neil I'd then say if the email was delivered, i.e. a 2xx response from one of the recipient's domain's MX record, then it has in fact been delivered.

    Getting it reliably from that point to the attention of an actual person or process is the recipients responsibility.

    There is always a technical grey area catch on such things but that is a massive edge case. Far more likely email logs shows delivery attempt (and non delivery response) or delivery response.

    But the border is the recipient MX.

    💬 3🔄 1⭐ 5

Replies

  • Nov 13, 2026, 2:09 PM

    @revk @neil To me it's like when people say that they didn't receive my email because it went in their spam. Well that's their problem, not mine. It was sent to them and received

    💬 1🔄 1⭐ 1
  • Nov 13, 2026, 2:16 PM

    @mikecox @neil Indeed, I have likened it to an office that throws out any post that comes in pink envelopes. Clearly if I sent it and it arrived even in a pink envelope, I have done my bit.

    I'd also be replying "thank you for confirming you did in fact RECEIVE my email within the required time frame (even if you chose to file it as spam), I have saved your confirmation for future reference".

    💬 0🔄 1⭐ 3
  • Nov 13, 2026, 2:29 PM

    @revk @neil Interestingly that puts people who use intermediary services like Mimecast at a disadvantage compared to those who just publish the M365 MX records. The company I work for is in this situation, with the mail then backing up at Mimecast. The tests I sent this morning seem to indicate that MS are responding with 4XX temp failure codes on the SMTP level.

    💬 1🔄 0⭐ 2
  • Nov 13, 2026, 2:33 PM

    @andrew @revk @neil It's not that unusual to how some big financial companies handle mail - many use a physical mail processing company to receive the mail and I guess scan and forward it electronically. It's fairly easy to spot when you notice the postcode for big companies is all neighbouring ones in the same town where the company isn't.

    💬 1🔄 0⭐ 1
  • Nov 13, 2026, 2:51 PM

    @penguin42 @andrew @neil I would not say a disadvantage but a clear demarkation of responsibility.

    If you contract with someone to handle your email sending (e.g. ISP) the demarkation is when they send it on to the MX of the recipient. You chose to contract out your sending.

    But if someone contracts out their receiving, which, as you say, happens, the recipient is taking responsibility as they are the ones that contacted that out.

    You need a line, and handed to an MX for domain is a good one

    💬 1🔄 0⭐ 2
  • Nov 13, 2026, 2:56 PM

    @penguin42 @andrew @neil My key issue here is that there should be a specific point that sender hands over responsibility to recipient.

    Up to then, any failure is the sender's fault.

    Beyond that is the recipient's fault.

    Contracting someone else for each side does not change that reality.

    As I say, there is always some technical edge cases on that specific SMTP connection, which is unavoidable but really not going to happen in most cases.

    This also fixes the date/time.

    💬 1🔄 0⭐ 2
  • 💬 3🔄 0⭐ 1
  • Nov 13, 2026, 3:03 PM

    @revk @andrew @neil Well you can get 'proof of posting' at a post-office; and often you're told to use tracked/signed-for - so there's some requirement on the sender to do something in the face of a delivery system that's known to be flaky.

    (which in the case of mail handling companies is useless - you get a delivery picture of a huge box sitting on a table without your letter visible)

    💬 1🔄 0⭐ 1
  • Nov 13, 2026, 3:05 PM

    @penguin42 @andrew @neil Ha, yeah, but for some legal things a "proof of posting" is all you need. My suggestion on MX of recipient domain is actually a tad further down the line, but also allows for people sending email themselves not using an ISP.

    I have had such a picture (to amazon) and sued RM (who caved) on basis proof of delivery picture did not show *my* package (distinctive colour even).

    💬 0🔄 0⭐ 1
  • Nov 13, 2026, 3:06 PM

    @revk @penguin42 @andrew @neil iirc with Royal Mail there is (in the context of legal notices) a presumption of delivery - if you can prove postage then it's on the other party to prove that it wasn't delivered. I don't know if there's anything analogous in email

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 13, 2026, 3:18 PM

    @revk @penguin42 @andrew @neil No the postal service is special here

    You have an interest in proving and email was or was not delivered. You can tamper with or lose your server logs. Stuff can get lost. SMTP is not reliable

    The post office is notionally an uninterested third party with a process in place to manage high reliability document delivery and recognized as such.

    The analogy would be not using email but both using an agreed reliable third party provider of electronic document service

    💬 3🔄 0⭐ 3
  • Nov 13, 2026, 3:21 PM

    @etchedpixels @revk @penguin42 @andrew @neil

    While technically true, recent event have seen 1st class mail here be delivered in the 3rd week after it was posted and the new barcodes on the side of stamps mean they are not franked with the posing date (I assume the PO can look up in DB the day/time it was scanned, but it's harder to verify)

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 1
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 13, 2026, 2:30 PM

    @revk @neil

    This is but one reason, why I have my MXs configured in a way, that filtering unwanted mail happens as part of the delivery process, so that in the case it's identified as unwanted, the delivery process itself will abort with a rejecting error.

    It also allows me to tell-off people who suggest "I should look into my spam folder…"

    Sorry mate… doesn't work like that with my mail server.

    💬 1🔄 0⭐ 3
  • Nov 13, 2026, 2:53 PM

    @datenwolf @neil That creates an interesting point.

    I agree, best place for it.

    But it means you have a case of "sender attempted to delivery and you refused delivery", which I imagine in some legal senses means sender did what was required and it was your choice to refuse.

    Where as a spam folder is "sender actually did deliver", which I would assume has even more legal leverage, as sender would not know delivery was ignored.

    💬 0🔄 0⭐ 0