KyleS
Tue Jul 26 15:33:19 CDT 2005
Okay, this'll be the second respond to my own post. I can now send and
receive. I had 128 bit encryption enabled on my virtual SMTP server. Once I
disabled that all was well. Thanks for the input!
"Kyle S" wrote:
> I wasn't thinking about the port 23 part. TELNET's port! It's too early for
> me!
>
> "Kyle S" wrote:
>
> > I tried to telnet and had no luck. I typed in telnet X.X.X.X:25 and comes
> > "could not open connection to the host, on port 23: Connect failed. I don't
> > understand why it would say port 23 though when i put in port 25.
> >
> > I ran the test on my domain from dnsreport.com. It failed on two things in
> > the MAIL section of the test. 1. "Acceptance of NULL <> sender" and the
> > second FAIL was "Acceptance of postmaster address"
> >
> > 1)
> >
> > ERROR: One or more of your mailservers does not accept mail from "<>".
> > Mailservers are required by RFC1123 5.2.9 to accept mail from "<>". By
> > refusing this mail, you will never get reject/bounce messages, or return
> > receipts, and you may get other mail server admins upset at you if they have
> > to deal with your bounce messages.
> > ERROR: mail.mydomain.com's MAILFROM <> response: 530 5.7.0 Must issue a
> > STARTTLS command first .
> > ERROR: mail.mydomain.com's MAILFROM <> response: 530 5.7.0 Must issue a
> > STARTTLS command first .
> >
> > 2)
> >
> > ERROR: One or more of your mailservers does not accept mail to
> > postmaster@mydomain.com. Mailservers are required (RFC822 6.3, RFC1123 5.2.7,
> > and RFC2821 4.5.1) to accept mail to postmaster.
> > mail.mydomain.com's postmaster response: >>> RCPT
> > TO:<postmaster@mydomain.com> <<< 530 5.7.0 Must issue a STARTTLS command
> > first
> >
> >
> >
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> > >
> > > "Kyle S" <KyleS@discussions.microsoft.com> wrote in message
> > > news:803ABE0E-C49B-40A9-B395-22F69149F57D@microsoft.com...
> > > >- It appears now that I'm able to send, just not receive.
> > > >
> > > > - Internal DNS config - 'A' records for both my exchange server and DC.
> > > > 'MX' record for the exchange server.
> > >
> > > Not necessary. The MX records belong in your public DNS, not your internal
> > > DNS. Did you check out your domain at the link I gave you?
> > >
> > > >
> > > > - I'm unable to ping my mail server from outside my network.
> > >
> > > Nor should you be able to, unless you've enabled the option to allow ICMP in
> > > your firewall config, which I don't recommend. The test ought to be, can you
> > > telnet on port 25 to your public IP from the internet?
> > >
> > > > - All clients are pointed at one DNS server.
> > > > - when trying to send from a pop3 account I have I receive an error that
> > > > states "must issue a STARTTLS command first"
> > >
> > > That isn't relevant, necessarily - IIRC that means you would need to
> > > authenticate to your SMTP server first. But I don't recommend accessing your
> > > server via POP/IMAP anyway.
> > >
> > >
> > > >
> > > >
> > > >
> > > > "Lanwench [MVP - Exchange]" wrote:
> > > >
> > > >>
> > > >>
> > > >> In news:8DD9110F-3BFA-4EBE-82A8-282E0F594F9C@microsoft.com,
> > > >> Kyle S <KyleS@discussions.microsoft.com> typed:
> > > >> > I'm unable to send and receive external email through Exchange using
> > > >> > SMTP. I am able to access OWA remotely. I can also send and receive
> > > >> > emails within my domain. Both with outlook and OWA. The only thing
> > > >> > I can't do is send to external addresses nor receive from them
> > > >> > either. My first guess is a DNS problem, but I'm out of ideas. Any
> > > >> > suggestions??
> > > >>
> > > >> For your outbound mail - what's your internal DNS config? Can you resolve
> > > >> the domain names from the server via ping? Using forwarders in DNS and
> > > >> all
> > > >> clients pointing only at the internal DNS server IP?
> > > >>
> > > >> For your inbound: www.dnsreport.com may help you - enter your domain
> > > >> name.
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >