I don't have any recent examples of messages sent to http://dummy.us.eu.org/noelleg . I'll open another ticket if/when it happens again with http://dummy.us.eu.org/noelleg . W.r.t. the message you analyzed below: if it got delivered to google (and juno), then that likely means it's a problem at Google's end. That's unfortunate because I made every effort to disable all spam filtering on the Google side. I guess I'd need to follow up with Google. Please close this ticket since clearly Sonic.NET's SMTP server was working fine. Thanks. > From: Sonic Support <http://www.sonic.net/~support> > Date: Sun, 16 Jun 2019 12:16:08 -0700 > > Hello Robert, > > I checked all three of these messages and they all went through Sonic's SMTP > server and were handed off to the MX server on the far end. > > The message to http://www.juno.com/~bhavaniowl was successfully handed off to > mx.vgs.untd.com > > The message to http://www.gmail.com/~bhavaniowl was successfully handed off to > gmail-smtp-in.l.google.com > > The message to http://dummy.us.eu.org/noelleg was successfully handed off to > alt2.aspmx.l.google.com > > We don't have a way to track the messages beyond the point where they were > handed off to the MX server on the far end. > > If you have an example of an email sent to http://dummy.us.eu.org/noelleg that didn't arrive > we should be able to track that message and see what happened to it. This may > give us some insight into why the messages aren't getting through to the other > email addresses as well.