Los mensajes llegan en spam :(

Hola,

Creo que desde hace semanas o siempre estoy teniendo un problema, usamos Google Apps para HospedRed, los mensajes que envió desde Google a veces llegan en spam y a veces no. Los mensajes que envió desde el phpmail (los que envia el whmcs) llegan todos en spam hasta marcarlo como no spam.

Me canse de agregar registros como estos:

También tengo el domainkey el RSA y como quiera continua esto!

Se revisaron todas las listas contra el spam y no esta en ningunas ninguno de los dos servers s1.hospedred.net ni s2.hospedred.net, que se puede hacer?

Un saludo.

 

Malformed greeting or no A records found matching banner text for following servers, and banner is not an address literal. RFC5321 requires one or the other (should not be a CNAME). If this is not set correctly, some mail platforms will reject or delay mail from you, and can cause hard to diagnose issues with deliverability. Mailserver details:

74.125.136.26 | WARNING: The hostname in the SMTP greeting does not match the reverse DNS (PTR) record for your mail server. This probably won't cause any harm, but may be a technical violation of RFC5321
173.194.70.26 | WARNING: The hostname in the SMTP greeting does not match the reverse DNS (PTR) record for your mail server. This probably won't cause any harm, but may be a technical violation of RFC5321
74.125.136.26 | WARNING: The hostname in the SMTP greeting does not match the reverse DNS (PTR) record for your mail server. This probably won't cause any harm, but may be a technical violation of RFC5321
173.194.70.27 | WARNING: The hostname in the SMTP greeting does not match the reverse DNS (PTR) record for your mail server. This probably won't cause any harm, but may be a technical violation of RFC5321
74.125.131.27 | WARNING: The hostname in the SMTP greeting does not match the reverse DNS (PTR) record for your mail server. This probably won't cause any harm, but may be a technical violation of RFC5321


Mailserver rejected mail to address literals. Mailservers are technically required by RFC1123 section 5.2.17 to accept mail to domain literals (i.e. IP addresses instead of domains). This ensures backwards compatibility and can help with delivery in certain non-optimal situations, like a DNS server being down/unresponsive.

74.125.136.26 | unexpected response to [RCPT TO: ] | 550-5.1.1 The email account that you tried to reach does not exist. Please try550-5.1.1 double-checking the recipient's email address for typos or550-5.1.1 unnecessary spaces. Learn more at550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 n49si378597eeo.109
173.194.70.26 | unexpected response to [RCPT TO: ] | 550-5.1.1 The email account that you tried to reach does not exist. Please try550-5.1.1 double-checking the recipient's email address for typos or550-5.1.1 unnecessary spaces. Learn more at550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 dq5si4051991wib.27
74.125.136.26 | unexpected response to [RCPT TO: ] | 550-5.1.1 The email account that you tried to reach does not exist. Please try550-5.1.1 double-checking the recipient's email address for typos or550-5.1.1 unnecessary spaces. Learn more at550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 w8si376990eeo.116
173.194.70.27 | unexpected response to [RCPT TO: ] | 550-5.1.1 The email account that you tried to reach does not exist. Please try550-5.1.1 double-checking the recipient's email address for typos or550-5.1.1 unnecessary spaces. Learn more at550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 o10si1204287wiy.30
74.125.131.27 | unexpected response to [RCPT TO: ] | 550-5.1.1 The email account that you tried to reach does not exist. Please try550-5.1.1 double-checking the recipient's email address for typos or550-5.1.1 unnecessary spaces. Learn more at550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 pe15si569487vcb.21

We were unable to connect to any of your WWW addresses listed. Users will be unable to access your site until this is resolved.

184.154.192.118 : server timeout

This domain has an SPF record, or an SPF formatted TXT record. SPF usage may have a negligible impact on spam prevention and if implemented incorrectly cause serious mail delivery problems for remote users. This software does not check the content of your SPF record to test if it is well designed only that it exists. Your SPF record(s) for each nameserver is/are:

"v=spf1 +a +mx +ip4:184.154.192.118 ?all"
"v=spf1 mx ptr ~all"
"v=spf1 includerivatednsorg.com ~all"
"v=spf1 include:_spf.google.com ~all"
"v=spf1 +a +mx +ip4:184.154.68.242 ?all"
"v=spf1 include:hotmail.com ~all"
"v=spf1 include:gmail.com ~all"
"v=spf1 include:yahoo.com ~all"
"v=spf1 +a +mx +ip4:184.154.68.243 ?all"

SPF value covers incoming mailservers The SPF value does not allow mail delivery from all mailservers in the domain. This may cause problems if you use the same servers for incoming and outgoing mail. The failing mailservers are:

74.125.136.26 is neither permitted nor denied by domain of hospedred.net | neutral | 74.125.136.26
173.194.70.26 is neither permitted nor denied by domain of hospedred.net | neutral | 173.194.70.26
74.125.136.26 is neither permitted nor denied by domain of hospedred.net | neutral | 74.125.136.26
173.194.70.27 is neither permitted nor denied by domain of hospedred.net | neutral | 173.194.70.27

 

@copernico.es, puedes compartir la herramienta con la que has realizado ese test?

 

Deseo saber lo mismo y también un atajo de lo que tengo que hacer por que solo me estoy confundiendo, entiendo que hay como un timeout pero no veo la posibilidad de evitar que eso siga pasando :S

También no me funciona el smtp de gmail con el whmcs y esta todo configurado, parece que gmail actualizo algo o tiene que ver con autorización de algo pero no logro encontrar ese algo.

 

Creo que el problema fue solucionado, ya no llegan en spam en ninguno de los emails!

Pero igual si alguien tiene experiencias sobre esto, estoy abierto a recibirlas!