<div>
I'm not sure what your messaging environment looks like or your level of access, but generally message tracking logs or SMTP logs would be what you would need in this situation.
</div>


I'm not sure what your messaging environment looks like or your level of access, but generally message tracking logs or SMTP logs would be what you would need in this situation.

<div>
If I understand your question, refer to your MTA logs to follow your message.<br />
<br />
1) You should see it queued, when sent.<br />
<br />
2) Immediately or after some time interval, you'll see a <b>queue run</b>, where your MTA connects to the MX record associated with and address + attempts delivery.<br />
<br />
3) At this point you'll either see the external MX accept the message or reject it.<br />
<br />
4) The MX may later reject the message for delivery + at this point you'll get a bounce.<br />
<br />
If you use a service like MailGun, just lookup the message + you'll see all these steps laid out neatly, for each message sent.
</div>


If I understand your question, refer to your MTA logs to follow your message.

1) You should see it queued, when sent.

2) Immediately or after some time interval, you'll see a queue run, where your MTA connects to the MX record associated with and address + attempts delivery.

3) At this point you'll either see the external MX accept the message or reject it.

4) The MX may later reject the message for delivery + at this point you'll get a bounce.

If you use a service like MailGun, just lookup the message + you'll see all these steps laid out neatly, for each message sent.

<div>
<div class="content wysiwyg-content">
Is there an easy was to set up email (other than standard received notice) to determine if an email sent has been received. We keep having issues with our emails not received.
</div>
</div>


Is there an easy was to set up email (other than standard received notice) to determine if an email sent has been received. We keep having issues with our emails not received.

Email Delivery

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.

Email Servers

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

An email client, email reader or more formally mail user agent (MUA) is a computer program used to access and manage a user's email. A web application that provides message management, composition, and reception functions is sometimes also considered an email client, but more commonly referred to as webmail.