Domain Outage when attempting email to vzwpix.com from an AWS Server through SES

[jcheek1234]

Good Morning, We are having an issue with SES sending to vzwpix.com & vtext.com from within AWS.
The message is never received, but there is no error returned from SES. We initially contacted AWS as we could still message the vzwpix.com & vtext.com from our personal Gmail accounts so there must be a disconnect there between them and the services but nothing useful is being returned. Hoping the details from that case will help here in resolving the issue.

Feedback from AWS Support:

Hello,

Thank you for contacting AWS Support. My name is Spencer and I will assist you with your case today.

I understand your email sent to vzwpix.com was never received

The following is a snippet from the event logs for message ID: 01000196885d9523-3c85be26-2eaa-421c-b5b0-65b842d2c278-000000

deliveryAttempts: 1
eventTime: 1746044556865 (Wed, 30 Apr 2025 20:22:36 GMT)
eventType: DELIVERY_ATTEMPT_FAILURE
responseCode: -1
fastDeferralClassification: DOMAIN_OUTAGE

......

deliveryAttempts: 1
eventTime: 1746044558001 (Wed, 30 Apr 2025 20:22:38 GMT)
eventType: DELIVERY_SUCCESS
responseCode: 250
responseMessage: 250 2.6.0 <[email address removed per the Verizon Terms of Service]> [InternalId=94038308952504, Hostname=SN7PR04MB8464.namprd04.prod.outlook.com] 14651 bytes in 0.152, 93.959 KB/sec Queued mail for delivery

......

deliveryAttempts: 2
eventTime: 1746044985908 (Wed, 30 Apr 2025 20:29:45 GMT)
eventType: DELIVERY_ATTEMPT_FAILURE
responseCode: 452
responseMessage: 452 4.1.0 <[email address removed per the Verizon Terms of Service]> server temporarily unavailable AUP#MXRT

......
Multiple attempts
......

deliveryAttempts: 8
eventTime: 1746054117992 (Wed, 30 Apr 2025 23:01:57 GMT)
eventType: DELIVERY_ATTEMPT_FAILURE
fastDeferralClassification: DOMAIN_OUTAGE
responseCode: -1
responseMessage:

It looks like SES tried to send the email at first at 30 Apr 2025 20:22:36 GMT, and it throws an error that the Domain is Outrage. 2 seconds later, recipient server returned a message saying the email is successfully received and queued. They returned a 250 success code. Then SES tried multiples times to delivery the email and at 23:01:57, the 8th attempt failed also because of DOMAIN_OUTAGE.

Since the server once returned a 250 and queued response, SES consider it as a delivered email. From the overall logs, looks like there are some issue at the recipient server side when the email was sent.

I used the 3rd-party tool to check the domain vawpix.com, it's showing "The remote name could not be resolved: 'vzwpix.com' (http://vzwpix.com)"
>> https://mxtoolbox.com/emailhealth/vzwpix.com/

Same result when I run the following command to nslookup the domain:
nslookup -type=mx vzwpix.com
;; connection timed out; no servers could be reached

I would suggest you talk to the ISP vzwpix.com, to see if they email servers work fine at the time.

I hope the information above is helpful. Please let me know if you have any other question and I will assist you further. Thanks.

We value your feedback. Please share your experience by rating this and other correspondences in the AWS Support Center. You can rate a correspondence by selecting the stars in the top right corner of the correspondence.

Best regards,
Spencer L.
Amazon Web Services

[SynthpopAddict]

Vtext and VzwPix are no longer supported.  Business customers have something new called EMAG to use, so I'd contact whomever your Verizon representative is and have them transition you to the new app.