Vexing email delivery problem

My best DTC customer is not getting our emails.

Last June he hard bounced twice and got into the Hard Bounce state.

We redid the subscribe process, he did get the confirmation email and we have him in the Double-Opt In state. However emails I try to send through SendGrid/Vin65 are now Soft Bouncing and he isn’t getting them.

I can email him directly with no issues, no bounce.

I am not getting any bounce messages directly so I can’t see what the issue might be.

His email is on aol.com.

Did I mention that he is MY BEST DTC CUSTOMER?

Any ideas?

1 Like

Maybe check your sitch out here:

https://postmaster.aol.com/ip-reputation

https://postmaster.aol.com/sa-ticket

So I looked at the last test email I received for IP addresses. I tried to choose the relevant one. Result:

"198.37.159.135 [o3.email.vin65.com] Reputation is Good

What does a good reputation mean?

The IP address has a good reputation. This means AOL has enough data to determine that the IP address is a known mail sender with a good reputation. You should not be experiencing bounce or reject errors when sending mail from this IP.

Why am I receiving errors when trying to send mail to AOL?

DYN:T1 errors usually occurs if you send high volume of mail. To resolve DYN:T1 errors, please apply for Whitelist."

Now what?

https://postmaster.aol.com/whitelist-request

I’d like to think vin65 and sendgrid did that at the beginning of time…

And in any case it is on vin65 and sendgrid to agree to the whitelist T&Cs…

@Brent

Can we get some love here?

@ElJefe - is this happening consistently across all AOL users or just the one on the support ticket? The specific customer we are discussing had his email address added to the Spam Report in SendGrid and we are getting our IT team to remove it from that list as soon as possible. Email addresses gets added to the Spam Report like so: https://sendgrid.com/docs/Glossary/spam_reports.html

hi @carisenr I did get the note from support. Thanks very much for the help. This customer is not very technical…

Is there a best practice for identifying these and getting them fixed, other than this way?

1 Like