• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MS Exchange 2003 Problem

I

InlineFour

Banned
i'll start off with a general overview of my current setup.

i have comcast which uses dynamic ip but is static most of the time
port 25 is not blocked
the local network's domain is "something".local
i have an online domain "something".com; i would like to use this domain for exchange

using a test account, i can receive mail on the exchange account, but i have a problem sending mail out. for example, when sending mail to my comcast email address, comcast automatically rejects the email saying it is spam mail. comcast returns an email that says:

test_mail@comcast.net on 3/1/2006 9:46 PM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<srv01.home.local #5.5.0 smtp;550-ip.ip.ip.ip blocked by ldap😱u=rblmx,dc=comcast,dc=net>

srv01.home.local is my exchange server's full dns name. so i try to send a test mail to my gmail account and yahoo. this time they do not reject the test mail but flag the mail as spam. does my server's full dns name (srv01.home.local) have to match my online domain name (something.com)?
 
That's because you have a dynamic IP address that's probably on a dozen blacklists. There's not much you can do, unless you can find a company who will forward your email for you.
 
Originally posted by: InlineFour
how did my ip get on a blacklist?
Click to expand...

In my experience, most dynamic IPs are on blacklists by default, since its typically against your TOS to run servers.
 
InLineFour,

By chance have you setup Comcast's SMTP server as your servers SMTP smarthost? I know that Comcast does not allow direct connections to some of their SMTP servers by their users. Do a search for SMTPDiag on Microsofts site and run that from your Exchange box and post the results. It has a very simple syntax, like smtpdiag someone@something.com someone@somwhere.com /v and it will give you a breakdown of what the servers responses were. It helped me out a ton. Hope that helps some.

 
after running smtpdiag
Searching for Exchange external DNS settings.
Computer name is SRV01.
VSI 1 has the following external DNS servers:
There are no external DNS servers configured.

Checking SOA for comcast.net.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [127.0.0.1].
TCP test succeeded.
UDP test succeeded.
Serial number: 1544
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: "mydomain".com.
MX: mx3.zoneedit.com (100)
MX: mail."mydomain".com (0)
A: mx3.zoneedit.com [216.55.149.18]
Checking MX records using UDP: "mydomain".com.
MX: mail."mydomain".com (0)
MX: mx3.zoneedit.com (100)
A: mx3.zoneedit.com [216.55.149.18]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: comcast.net.
MX: gateway-r.comcast.net (5)
MX: gateway-s.comcast.net (5)
A: gateway-s.comcast.net [63.240.76.26]
A: gateway-s.comcast.net [204.127.202.26]
A: gateway-r.comcast.net [204.127.198.26]
A: gateway-r.comcast.net [216.148.227.126]
Checking MX records using UDP: comcast.net.
MX: gateway-r.comcast.net (5)
MX: gateway-s.comcast.net (5)
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for "user"@comcast.net.
Connecting to gateway-r.comcast.net [216.148.227.126] on port 25.
Received:
450 busy - please try later

Error: Expected "220". Server is not accepting connections.
Failed to submit mail to gateway-r.comcast.net.
Connecting to gateway-s.comcast.net [204.127.202.26] on port 25.
Received:
450 busy - please try later

Error: Expected "220". Server is not accepting connections.
Failed to submit mail to gateway-s.comcast.net.
Connecting to gateway-s.comcast.net [63.240.76.26] on port 25.
Received:
450 busy - please try later

Error: Expected "220". Server is not accepting connections.
Failed to submit mail to gateway-s.comcast.net.
Connecting to gateway-r.comcast.net [204.127.198.26] on port 25.
Received:
450 busy - please try later

Error: Expected "220". Server is not accepting connections.
Failed to submit mail to gateway-r.comcast.net.
Click to expand...
 
InLineFour, are you using Comcast as your SMTP smart host or another one? DNS seems to be working fine from what I see in your post. This is something that just caught my eye from your original post.

<srv01.home.local #5.5.0 smtp;550-ip.ip.ip.ip blocked by ldapu=rblmx,dc=comcast,dc=net>

srv01.home.local does not exist on the internet, if a mail server does a reverse lookup for your domain it will fail.

Make sure you configured smart host for the SMTP server that way if a reverse lookup is done the mail will have come from that host (Comcast) and not a dynamic ip, or unresolvable host. How do you have exchange configured?
 
i don't have smart host configured at the moment. i have setup exchange server before and everything had worked before without a smart host. that was a while ago though.
 
I am pretty sure that using smart host will solve your issues. I just did an SBS2003 install last week and their situation was similar to yours, they had Comcast as well and were running Exchange 2003 SP2. I know that in other cases, I have done as you and configured it without smart host and it worked fine. We have spam to thank for all these hoops we must jump through now 🙂.... Let me know how things work out.

 
i just configured a smart host after reading this very informative tutorialarticle. my emails are sending out and are not being flagged as spam. thanks a lot. i was about to give up trying to set up the exchange server too.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top