Re: Cannot send mail out after default installation

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Not sure what I am doing wrong here. I followed the suggestions in the
articles:

- Disabled fixup protocol on PIX
- Configured correct domain name in the Delivery/Advanced tab
- Asked IP owner (current ISP) to add a PTR record to their DNS server (RDNS)
- RDNS resolved successfully after record was added.

Still have problem with sending email to AOL. NDR replied back as "This
message was rejected due to the current administrative policy by the
destination server. Please retry at a later time. If that fails, contact your
system administrator."

One thing I did noticed when viewing the outgoing header, the log show my
outgoing IP address is not the same as this server. Could this be the
problem? Does this mean I have to tell my PIX firewall to route outgoing
smtp from the internal address to the exact external address as the public IP
of the registered mail server (DNS and RDNS)?
--
Regards,

Andy


"Mike Spike" wrote:

This is then probably because you IP does not reverse DNS to your Domain.

AOL does a Reverse Lookup to see if 212.213.156.155 (random IP address) has
a PTR record for whatever you identify your SMTP server as, and rejects if
it does not match. Your server is probably called called localhost or the
name of your internal domian.

Mike

"gocrm" <gocrm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:02367ACB-15C5-40D0-9BF5-DE4694ECC758@xxxxxxxxxxxxxxxx
Michael,

It turned out that the problem only occurs when sending mail to AOL. I
don't have a problem sending to and receiving from our main company.

I did a DNS report and here's the errors that it found:

1) FAILURE: Reverse DNS entries for MX records ERROR: The IP of one or
more
of your mail server(s) have no reverse DNS (PTR) entries/* (if you see
"Timeout" below, it may mean that your DNS servers did not respond fast
enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your
mail
servers. It is strongly urged that you have them, as many mailservers will
not accept mail from mailservers with no reverse DNS entry. You can
double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if
you
recently changed your reverse DNS entry (it contacts your servers in real
time; the reverse DNS lookups in the DNS report use our local caching DNS
server). The problem MX records are:
XX.XX.XX.XX.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0)
(check
it)]

2) WARNING: 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.

mail.domain.com claims to be invalid hostname
'****************************************************0****0*********************20':
220
****************************************************0****0*********************20
****200**0*********0*00


3) WARNING: Acceptance of abuse address WARNING: One or more of your
mailservers does not accept mail to abuse@xxxxxxxxxxx Mailservers are
expected by RFC2142 to accept mail to abuse.

email.impire.com's abuse response:
RCPT TO:<abuse@xxxxxxxxxx>
<<< 550 5.1.1 User unknown

4) WARNING: SPF record Your domain does not have an SPF record. This means
that spammers can easily send out E-mail that looks like it came from your
domain, which can make your domain look bad (if the recipient thinks you
really sent it), and can cost you money (when people complain to you,
rather
than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004
was
the target date for domains to have SPF records in place (Hotmail, for
example, started checking SPF records on 01 Oct 2004).
--
Regards,

Andy


"Michael Jenkin [SBS-MVP]" wrote:

Hello,

Have you checked DNS is working correctly,

Is your SMTP connector sending email out to DNS or to a smarthost ?

Does your ISP allow you to make outbound port 25 connections ?

Thanks

gocrm wrote:

I have installed SBS 2003 R2 Premium successfully. Incoming email is
working
fine via Exchange 2003. Outgoing email is not. The mail never reach
external receipient. What am I doing wrong?


--
Michael J. Jenkin MVP - SBS, MCP, Small Business Specialist, Senior
Systems Engineer
Visit http://www.mickyj.com




.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)