The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Problema con correos rebotados

Discussion in 'Discusión en Español' started by juanpe0890, Mar 1, 2012.

  1. juanpe0890

    juanpe0890 Registered

    Joined:
    Mar 1, 2012
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Cuando envio un mail a ciertos clientes, me regresa un mail con este mensaje, ya investigue un poco y pareciera ser que los clientes nos tuvieran como en la blacklist, pero uno de ellos me asegura que ya no estoy en esa, sino en su whitelist y aun asi no puedo, en verdad apreciaria que me ayudaran con eso.

    Code:
    -------- Mensaje original --------
    Subject: Mail delivery failed: returning message to sender
    De: Mail Delivery System <Mailer-Daemon@web.e-webside.com>
    A: gmassist@erimxl.com
    CC:
    
    
    
    This message was created automatically by mail delivery software.
    
    A message that you sent could not be delivered to one or more of its
    recipients. This is a permanent error. The following address(es) failed:
    
    Victor.Gomez@arrisi.com
    SMTP error from remote mail server after end of data:
    host ironmail2.arrisi.com [216.234.147.87]: 554 Transaction Failed Spam Message not queued.
    
    ------ This is a copy of the message, including all the headers. ------
    
    Return-path: <gmassist@erimxl.com>
    Received: from 189.222.12.181.dsl.dyn.telnor.net ([189.222.12.181]:50009 helo=EriNewPC)
    by web.e-webside.com with esmtpa (Exim 4.69)
    (envelope-from <gmassist@erimxl.com>)
    id 1S3DHT-0000Ah-AF
    for Victor.Gomez@arrisi.com; Thu, 01 Mar 2012 13:11:20 -0800
    From: "" <gmassist@erimxl.com>
    To: "'Gomez, Victor'" <Victor.Gomez@arrisi.com>
    References: <C8E26E5086DF8C4DA358C4E629718AAB03EBF4@ATLEXMBX3.ARRS.ARRISI.com> <002f01ccf73b$6d2b7f00$47827d00$@erimxl.com> <CAHDE-VzWOdJD3+mrq9axDsbD8Yks75F1PibvCqGYbG+2pDCOtA@mail.gmail.com> <C8E26E5086DF8C4DA358C4E629718AAB03EF20@ATLEXMBX3.ARRS.ARRISI.com>
    In-Reply-To: <C8E26E5086DF8C4DA358C4E629718AAB03EF20@ATLEXMBX3.ARRS.ARRISI.com>
    Subject: RE: Test
    Date: Fri, 2 Mar 2012 13:10:52 -0800
    Message-ID: <000f01ccf8b8$f7eeb930$e7cc2b90$@erimxl.com>
    MIME-Version: 1.0
    Content-Type: multipart/related;
    boundary="----=_NextPart_000_0010_01CCF875.E9CDC320"
    X-Mailer: Microsoft Outlook 14.0
    Thread-Index: AQIrN0sZUU7Kkrl7umDWeYD3Nk0HKAI6MLfRAovGMMkCNbtkj5VjJZBw
    Content-Language: en-us
    
    This is a multipart message in MIME format.
    
    ------=_NextPart_000_0010_01CCF875.E9CDC320
    Content-Type: multipart/alternative;
    boundary="----=_NextPart_001_0011_01CCF875.E9CDC320"
    
    
    ------=_NextPart_001_0011_01CCF875.E9CDC320
    Content-Type: text/plain;
    charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable
    
    
    
    Ya revise tambien en varios listados de spam servers, y el mio no esta en ninguno, la verdad no se que mas hacer:
    
    Corri esta prueba en dnssy:
    
    
    Test
    
    Results
    
    Status
    
    
    
    Checking domain format:
    
    Hostname looks good.
    
    Pass
    
    
    
    Checking for parent nameservers:
    
    Found 13 parent nameservers.
    
    Pass
    
    
    
    Checking for parent glue:
    
    Glue from root nameservers to parent nameservers is missing. This means that an extra lookup is required to find your parent nameservers. There is nothing you can do about this.
    
    Info
    
    
    
    NS records at parent nameserver:
    
    Your NS records at your parent nameserver are:
    
    ns2.e-webside.com [50.116.69.248] TTL 172800
    ns1.e-webside.com [184.173.9.140] TTL 172800
    
    Provided by a.gtld-servers.net
    
    Info
    
    
    
    Nameservers listed at parent:
    
    Your nameservers are listed at the parent nameserver.
    
    Pass
    
    
    
    Glue at parent nameserver:
    
    Glue is provided from parent nameserver to your nameservers. This means they provided the IP address of your nameservers, so one less step is required in resolving your domain. This gives better performance.
    
    Pass
    
    
    
    Nameserver name validity:
    
    The parent nameserver responded with NS records that appear valid.
    
    Pass
    
    
    
    Nameserver A records:
    
    All of your nameservers have A records.
    
    Pass
    
    
    
    Nameserver A records match parent glue:
    
    All of the glue provided by the parent nameserver matches the A records for your nameservers.
    
    Pass
    
    
    
    NS records at your nameservers:
    
    Your NS records at your nameservers are:
    
    ns2.e-webside.com reported:
    ns1.e-webside.com [184.173.9.140] TTL 86400
    ns2.e-webside.com [50.116.69.248] TTL 86400
    
    
    ns1.e-webside.com reported:
    ns2.e-webside.com [50.116.69.248] TTL 86400
    ns1.e-webside.com [184.173.9.140] TTL 86400
    
    
    Info
    
    
    
    Nameservers listed at your namservers:
    
    Your nameservers are listed at your nameservers.
    
    Pass
    
    
    
    Glue at your nameservers:
    
    Glue is provided by your nameservers. This means they provided the IP address of your nameservers.
    
    Pass
    
    
    
    Nameserver A records match nameserver glue:
    
    All of the glue provided by your nameserver matches the A records for your nameservers.
    
    Pass
    
    
    
    Parent glue matches your glue:
    
    The glue provided by the parent nameserver and your nameserver matches.
    
    Pass
    
    
    
    Nameservers match (parent):
    
    All nameservers returned by the parent nameserver are also returned by your nameserver.
    
    Pass
    
    
    
    Nameservers match (yours):
    
    All nameservers returned by the your nameservers are also returned by the parent nameserver.
    
    Pass
    
    
    
    All nameservers responded:
    
    All of your nameservers responded.
    
    Pass
    
    
    
    Only root nameservers returned:
    
    Your nameservers returned at least 1 non-root nameserver referernce.
    
    Pass
    
    
    
    Any root nameservers returned:
    
    Your nameservers did not return any root nameserver referernces.
    
    Pass
    
    
    
    All of your nameservers match:
    
    All of your nameservers return the same nameserver records.
    
    Pass
    
    
    
    All of your nameservers return an A record:
    
    All of your nameservers returned an A record for your domain.
    
    Pass
    
    
    
    Recursive lookups:
    
    None of your nameservers support recursive lookups.
    
    Pass
    
    
    
    Nameservers respond authoritatively:
    
    All of your nameservers responded authoritatively for your domain.
    
    Pass
    
    
    
    Nameserver name validity:
    
    All of your nameservers responded with NS records that appear valid.
    
    Pass
    
    
    
    Number of nameservers:
    
    You have only 2 nameservers, which is the minimum allowed. There is a chance that they could both fail simultaneously. Although not necessary, you should consider increasing the number of nameservers to 3.
    
    Warning
    
    
    
    CNAME returned:
    
    No CNAMES found when looking up your domain at your nameservers.
    
    Pass
    
    
    
    Nameservers on different class C:
    
    Your nameservers are of different class C IP addresses. This is an indication (but not proof) that they may not be co-located.
    
    Pass
    
    
    
    Nameservers on private IPs:
    
    Your nameservers appear to be on public IP addresses.
    
    Pass
    
    
    
    SOA record:
    
    Your SOA record at ns2.e-webside.com:
    
    Serial: 2012022800
    Master Nameserver: ns1.e-webside.com.
    Hostmaster eMail: adalidk.yahoo.com.
    Refresh: 86400 (24 hours)
    Retry: 7200 (2 hours)
    Expire: 3600000 (41 days 16 hours)
    Minimum TTL: 86400 (24 hours)
    
    
    Info
    
    
    
    Number of SOA records:
    
    Each of your nameservers returned exactly 1 SOA record.
    
    Pass
    
    
    
    SOA Serial Match:
    
    Each of your nameservers returned the same SOA serial number.
    
    Pass
    
    
    
    SOA Master Nameserver Match:
    
    Each of your nameservers returned the same SOA master nameserver.
    
    Pass
    
    
    
    SOA Admin Email Match:
    
    Each of your nameservers returned the same SOA admin email address.
    
    Pass
    
    
    
    SOA Refresh Match:
    
    Each of your nameservers returned the same SOA refresh value.
    
    Pass
    
    
    
    SOA Retry Match:
    
    Each of your nameservers returned the same SOA retry value.
    
    Pass
    
    
    
    SOA Expire Match:
    
    Each of your nameservers returned the same SOA expire value.
    
    Pass
    
    
    
    SOA Minimum TTL Match:
    
    Each of your nameservers returned the same SOA minimum TTL value.
    
    Pass
    
    
    
    SOA Serial Number:
    
    Your SOA serial number matches the recommended format YYYYMMDDnn [RIPE-203].
    
    Pass
    
    
    
    SOA Master Nameserver:
    
    Your SOA master nameserver is ns1.e-webside.com. It is also listed at the parent nameservers. This is correct.
    
    Pass
    
    
    
    SOA Admin Email:
    
    Your SOA admin email address is adalidk@yahoo.com. This seems to be a valid email address.
    
    Pass
    
    
    
    SOA Refresh:
    
    Your SOA refresh value is 24 hours. This specifies how often a slave nameserver checks for DNS updates at the master. This seems high. If you are using DNS notify to pass changes from master to slave nameservers, then it may be OK. If not, your slave nameservers may be checking for DNS updates too infrequently.
    
    Warning
    
    
    
    SOA Retry:
    
    Your SOA retry value is 2 hours. This is the time a slave nameserver will wait if an attempt to contact a primary nameserver failed before it tries again. This seems to be OK.
    
    Pass
    
    
    
    SOA Expire:
    
    Your SOA expire value is 41 days 16 hours. This is how long a slave nameserver will cache data if it cannot reach the master nameserver. If your master nameserver is unreachable for longer than this your slave nameservers will no longer cache your DNS. This seems to be OK.
    
    Pass
    
    
    
    SOA Minimum TTL:
    
    Your SOA minimum TTL value is 24 hours. This is interpreted by servers as the default TTL. It can be overridden on individual DNS entries. This seems high. This means that if you make DNS changes those changes may not propagate throughout the internet for a long time.
    
    Warning
    
    
    
    MX records:
    
    I found the following MX records:
    
    erimxl.com 0 [50.116.69.251]
    
    This is all of the MX servers I found.
    
    Info
    
    
    
    All nameservers return same MX:
    
    All of your nameservers returned the same MX records.
    
    Pass
    
    
    
    MX records have A records:
    
    All of your MX servers have A records.
    
    Pass
    
    
    
    MX records have CNAMEs:
    
    None of your MX servers have CNAME records. This is good.
    
    Pass
    
    
    
    MX records are IPs:
    
    None of your MX records are IP addresses. This is good.
    
    Pass
    
    
    
    MX records are valid:
    
    All of your MX records appear to be valid hostnames.
    
    Pass
    
    
    
    MX use public IP:
    
    All of your MX servers have public IP addresses.
    
    Pass
    
    
    
    MX IPs have reverse DNS:
    
    Some of your MX servers do not have reverse DNS (PTR) entries. Some mailers will refuse to send email to your domain. I found problems with the following:
    
    50.116.69.251
    
    
    Fail
    
    
    
    Connecting to MX 50.116.69.251:
    
    Connected to SMTP port on 50.116.69.251 OK.
    
    Pass
    
    
    
    Testing Connection:
    
    HELO OK.
    
    220-web.e-webside.com ESMTP Exim 4.69 #1 Thu, 01 Mar 2012 13:47:17 -0800 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
    
    Pass
    
    
    
    Testing HELO:
    
    HELO OK.
    
    250 web.e-webside.com Hello golum.z-host.com [109.200.21.194]
    
    Pass
    
    
    
    Testing null reverse path:
    
    This mail server accepts mail from a null reverse path.
    
    Pass
    
    
    
    Mail to local postmaster:
    
    This mail server accepts mail addressed to "postmaster".
    
    Pass
    
    
    
    Mail to domain postmaster:
    
    I got an error response to my "RCPT TO:<postmaster@erimxl.com>" message. Your mail server does not accept mail addressed to "postmaster@erimxl.com". I expected a response beginning with 250, but got the response:
    
    550 No Such User Here"
    
    [RFC2821 Section 3.6]
    
    Fail
    
    
    
    WWW record:
    
    You have a WWW record setup for your domain.
    
    American-recycle-day -> 50.116.69.251
    
    Pass
    
    
    
    WWW is public:
    
    Your WWW record is a public IP address.
    
    Pass
    
    
    
    Connecting to WWW server:
    
    Connected to WWW port on American-recycle-day OK.
    
    Pass
    
    
    
    Checking HTTP version:
    
    HTTP version 1.1 supported.
    
    Pass
    
    
    
    WWW server type:
    
    Your web server says it is:
    
    Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8m DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
    
    Info
    
    
    
    WWW server version:
    
    Your web server appears to reveal version information. This can pose a security risk if vulnerabilities are identified in this version. You should consider disabling version information in your server configuration.
    
    Security
    
    
    
    WWW home page:
    
    Your web server returned the home page of your web site.
    
    Pass 
     
  2. nibb

    nibb Well-Known Member

    Joined:
    Mar 22, 2008
    Messages:
    301
    Likes Received:
    1
    Trophy Points:
    18
    La IP de tu servidor o mensaje fue clasificada como emisora de spam. Probablemente este en una lista negra como SpamHaus u otra.

    Fíjate exactamente en el error de entrega "554 Transaction Failed Spam Message not queued"

    El error proviene del servidor que recibe el mensaje, no el tuyo, probablemente tiene Iron Port u otro filtro antispam que esta detectando tu email como correo basura. Esto puede ser por la IP u por otros factores.

    Tu servidor estuvo o esta haciendo Spam que es lo mas probable.
     
Loading...

Share This Page