Brian Tillman said:
Since it is the sending mail router that controls the content and
format of the message it is sending to you, there's nothing you can do
about it.
For clarification, wouldn't that status only get returned by the
receiving mail server because the OP opted for delivery notification of
his e-mail? This isn't the same as sending an e-mail that requests a
read receipt because the recipient's mail client would have to handle
that. However, an e-mail requesting delivery notification is a request
that targets the recipient's mail server for a response (i.e., the
sender only knows from the receiving mail server that their e-mail got
there and nothing about whether or not the recipient read the message).
I don't think many mail servers will handle delivery receipt requests.
I forget all the reasons for it but it generally seen as superfluous
overhead. If the message is deliverable, you don't get back an NDR
(non-delivery report). If the message was not deliverable at the
receiving domain, you get an NDR. So the mail server will provide
negative feedback instead of wasting its time confirming every
successful delivery.
When the OP said "get a confirmation back", I had assumed he opting to
request a read receipt from the recipient. It looks instead that Don is
opting for delivery notification. Lots, if not most, mail servers won't
bother handling those. Why would they bother wasting resources to send
back a second e-mail for all the messages they accepted when they can
just send back a few e-mails reporting failure? A delivery receipt in
no way guarantees that the recipient actually got it, only that your
message got to their mail server, and few recipients operated their own
mail server to be in any way responsible for guaranteeing delivery or
being responsible for what the mail server does.