Skip to content

Emails sent via SES not delivered to mailboxes libero.it and virgilio.it

1

Hi, for about two years I have activated the Amazon AWS SES service by connecting it to a WordPress site that sends newsletters and communications through the MailPoet plugin using the AWS SES SMTP connection. The service works well, we have never recorded any particular problems. In recent months, however, several users with email addresses @libero.it and @virgilio.it (after the well-known problems affecting these Italian providers https://www.corrierecomunicazioni.it/digital-economy/libero-e-virgilio-continua-il-caos-ripristino-e-mail-ancora-in-corso/) have informed us that they no longer receive our communications (not all users with that type of account only a part). Certainly the problem is attributable to Libero/Virgilio, but the assistance of ItaliaOnline (owners of @libero.it and @virgilio.it) asks for the log of the shipments made to make further checks and clarifications.

So I ask you, how can I download a log of the mailings made, to which recipients, and the result of the mailing?

Thank you so much

  • Same problem here. Did you manage to fix it?

3 Answers
1

Hi

By default, we are unable to get granular data regarding each email delivery. You will need to set up SES event publishing to put the sending events and related information to Cloudwatch.

Another option to improve your deliverability is to try out the Virtual Deliverability Manager which can give you recommendations to improve the overall deliverability of your emails -> https://docs.aws.amazon.com/ses/latest/dg/vdm.html

answered 3 years ago
0

Probably the @libero.it @virgilio.it email addresses are in your account suppression list after the iol server's down. Maybe their down generated hard bounces that are ended in your account suppression list.

answered 3 years ago
0

I have the same problem. Within a mailing list there are hundreds of users belonging to these 2 domains. I did notice that a possible reason for bouncing is due to the configuration of their mail servers: they are configured not to receive more than X (in the case I noticed X was equal to 5) messages from a sender mail address in a given time. I have then separated these users in a second list and setup delivery of max 5 messages per time unit. Slightly improved, but the bouncing problem remains. The solution is on their side

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.