locked
Problemas no recebimento de alguns usuarios externos RRS feed

  • Pergunta

  • Boa tarde Amigo

    Tenho um Exchange 2003, onde alguns usuarios estão reclamando que não estão recebendo algumas menssagens.
    1º Teste, foi verificar se estava em alguma blacklist, tudo normal
    2º Teste, verificar os link e provedor, tudo normal
    3º Teste, relatório do site dnsstuff e me apresentou alguns alertas como segue abaixo:

    WARN

     

    Glue at parent
    nameservers
    WARNING. The parent servers (I checked with d.dns.br.) are not providing glue for all your nameservers. This means
    that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can
    cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is
    perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as
    your domain (for example, a DNS server of "ns1.example.
    org" for the domain "example.com"). In this case, you can
    speed up the connections slightly by having NS records that are in the same TLD as your domain.

    WARN

     

    Nameservers on
    separate class C's
    WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because
    the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to
    make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed
    locations. You should not have all of your nameservers at the same location.
    RFC2182 3.1 goes into more detail
    about secondary nameserver location.

    WARN

     

    Mail server host name
    in greeting
    WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting
    should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail
    using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical
    violation of
    RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A
    record pointing back to the same server. Note that this one test may use a cached DNS record.
    exemplo01.dominio.com.br claims to be host exemplo02.dominio.com.br [but
    that host is at xxx.xx.xxx.xxx (may be cached), not xxx.xx.xxx.xxx]. <br />


     

     

     

    Open relay test
    WARNING: One or more of your mailservers appears to be an open relay. If so, this means that you are allowing
    spammers to freely use the mailserver to send out spam! It is possible that your mailserver accepts all E-mail and
    later bounces it, or accepts the relay attempt and then deletes the E-mail, but this is not
    common.
    WARNING: exemplo.dominio.com.br appears to be an open relay: 250 This is
    hurting you more than it is hurting me. <br />WARNING: exemplo02.dominio.com.br
    appears to be an open relay: 250 This is hurting you more than it is hurting me. <br />
    PASS SPF recordYou have an SPF record. This is very good, as it will help prevent spammers from abusing your domain. Your SPF

    Obrigado.

    sexta-feira, 5 de junho de 2009 15:16

Respostas

Todas as Respostas