+34 911 599 883

+34 911 895 172

Email Reputation Poor en sendbase.org Cisco database

Recibimos una incidencia de un cliente que al enviar correo desde uno de nuestros servidores al correo del dominio icam.es o repsol.com recibia el siguiente error:

Error de icam.es:

said: 550 (in reply to     RCPT TO command)

Final-Recipient: rfc822;
Action: failed
Status: 5.0.0
Remote-MTA: dns;
Diagnostic-Code: smtp; 550

Error de repsol.com:
Diagnostic-Code: smtp; 554-smtptc2.repsol.com 554 Your access to this mail
system has been rejected due to the sending MTA’s poor reputation. If you
believe that this failure is in error, please contact the intended
recipient via alternate means.

Este problema a que uno de nuestros servidores estaba en senderbase.org con una reputación de email pobre: Email reputation poor
Debido a que se había detectado envio de mails con virus desde una de las cuentas de correo de los alojamientos.


Creamos un ticket de soporte a support@senderbase.org y esto nos contestaron:

“Dear Sergio,

The most recent complaint we have on file for IP is dated 6/8/2016. If the spam problem is fixed as you believe it to be, then there should  be no further complaints received.

In general, once all issues have been addressed (fixed), reputation recovery can take anywhere from a few hours to just over one week to improve, depending on the specifics of the situation, and how much email volume the IP sends. Complaint ratios determine the amount of risk for receiving mail from an IP, so logically, reputation improves as the ratio of legitimate mails increases with respect to the number of complaints. Speeding up the process is not really possible.SenderBase Reputation is an automated system over which we have very little manual influence.

In the meantime, if there are recipients whom you cannot contact, we would recommend contacting the ISP involved to request temporary whitelisting or you can always arrange to contact the recipient via alternative means.

SenderBase Support”

Sólo podíamos esperar. Mienrtas Para solucionarlo cambiamos la IP de salida del servicio de correo saliente de nuestro servidor afectado.

A los 5 días el servidor ya aparecía con Email Reputation neutral.