RE: Exchange problems mailing @Bellsouth.net & resolution maybe
- From: v-chacez@xxxxxxxxxxxxx (chace zhang)
- Date: Fri, 29 Sep 2006 05:01:11 GMT
Hi,
Thank you for posting here.
From the post, I understand you can not send email to certain domain. Sincethis issue is some domains specific, I have the following suggestions for
your reference:
1. Based on my experience, this problem typically occurs when your outbound
Internet mail server does not have the correct DNS configuration required
to send mail to certain domain. The destination mail server requires that
a valid reverse DNS record (known as PTR) for all of your domain's MX
records. Some specific domain also requires that for every inbound SMTP
connection, the connecting SMTP server must have a valid PTR record even if
an MX record does not exist. So please contact your ISP to make sure your
reverse DNS entry is present and correct. Some messaging systems verify the
existence of the e-mail domain of the sender before they accept a "Mail
from: user@xxxxxxxxxx" Simple Mail Transfer Protocol (SMTP) entry at the
beginning of a new message delivery session. If the domain name cannot be
resolved by means of Domain Name System (DNS), the session is disconnected.
This behavior is mainly used to prevent the messaging systems from
receiving spam (unsolicited e-mail messages).
2. Make sure that your servers are using the static IP address and you do
not use DSL and/or cable modems as the connection.
3. I totally agree with your planning that you are able to create a SMTP
Connector to bypass DNS name resolution to test Simple Mail Transfer
Protocol (SMTP) mail flow to the particular remote domain. For the detailed
information, see the following KB articles:
285863 XCON: How to Bypass DNS Name Resolution to Test SMTP Mail Flow to
Remote
http://support.microsoft.com/?id=285863
HOW TO: Install and Configure SMTP Connectors in Exchange 2000 Server
http://support.microsoft.com/?id=314961
In addition, please contact the administrator of the destination domain for
more info why you can not send mail.
Hope this helps, if you need more help, please do not hesitate to let me
know.
Have a nice weekend!
Best Regards,
Chace Zhang (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Justin - synacs" <jcbrown@xxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: Exchange problems mailing @Bellsouth.net & resolution maybe
| Date: 28 Sep 2006 14:26:06 -0700
| Organization: http://groups.google.com
| Lines: 61
| Message-ID: <1159478766.102257.228350@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 67.188.129.69
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1159478771 6453 127.0.0.1 (28 Sep 2006
21:26:11 GMT)
| X-Complaints-To: groups-abuse@xxxxxxxxxx
| NNTP-Posting-Date: Thu, 28 Sep 2006 21:26:11 +0000 (UTC)
| User-Agent: G2/1.0
| X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7,gzip(gfe),gzip(gfe)
| Complaints-To: groups-abuse@xxxxxxxxxx
| Injection-Info: e3g2000cwe.googlegroups.com; posting-host=67.188.129.69;
| posting-account=d5JnMA0AAABocWkBStjwC4ytx6PLX5d0
| Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed.c
w.net!cw.net!news-FFM2.ecrc.de!news.glorb.com!postnews.google.com!e3g2000cwe
googlegroups.com!not-for-mail
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:301025
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I have an Exchange user who can't send to her @bellsouth.net contact; I
| checked around and found users at theplanet.com talking about this same
| issue as of late. Her SBC smarthost was returning an NDR and after our
| timeout of 48 hours, the user received an NDR.
| ***From: System Administrator
| Sent: Wednesday, September 27, 2006 8:31 PM
| To: stacxxxxxxxx@xxxxxxxxxxxxx
| Subject: Undeliverable: FW: Fashion Show, Sept. 27-Crystal Honn
|
| Your message did not reach some or all of the intended recipients.
|
| Subject: FW: Fashion Show, Sept. 27-Crystal Honn
| Sent: 9/26/2006 8:06 PM
|
| The following recipient(s) could not be reached:
|
| stacxxxxxxxx@xxxxxxxxxxxxx on 9/27/2006 8:31 PM
| Could not deliver the message in the time limit specified.
| Please retry or contact your administrator.
| < flpvm09.prodigy.net #4.4.7>***
|
| The original thread along with my post are at
| http://forums.theplanet.com/viewtopic.php?p=163818#163818
|
| After searching BS's website, I found "Troubleshooting: Non-BellSouth
| Customer Problem Sending E-mail":
|
http://help.bellsouth.net/bellsouth/asp/contentview.asp?sprt_cid=cd1b9607%2D
5b59%2D45bf%2Daca3%2D3154b7ad189a
|
| Pretty helpful in the sense that they encourage a useful
| troubleshooting technique, i.e. telnet'ing to their mail server. I did
| just this, and these are my results.
|
| There are four DNS records for mail.bellsouth.net:
|
| 205.152.59.17 (HOST)
| 205.152.59.16 (HOST)
| 205.152.58.33 (MX)
| 205.152.58.32 (MX)
|
| I tried telnetting to port 25 on each, and in all but one of the HOST
| (A) instances I received exactly the following response:
| "421 Cannot connect to SMTP server 205.152.5x.xx" (205.152.5x.xx:25),
| connect error 10061"
|
| So I observed that of the four records for mail.bellsouth.net, only one
| of them responded to "ehlo test.com" the way one would expect, and it
| was one of their HOST record addresses. As a side note, I thought HOSTs
| were reserved be for messages leaving an organization and not for those
| messages arriving at it. (?)
|
| Possible resolution...
| In Exchange, I created an SMTP connector that uses smarthost for the
| address space bellsouth.net with a cost of 25. The connector is
| configured to forward messages through the "[205.152.59.16]" smarthost
| (minus quotations). x.x.59.16 is the one IP address that didn't 421 me.
| I may add two more smarthost connectors if this doesn't work... one
| will forward to the second HOST IP address, and the other to
| mail.bellsouth.net which would use the MX record lookups. The MX
| connectors will likely have a lower cost so that Exchange will try and
| route messages there first.
|
|
.
- Follow-Ups:
- Re: Exchange problems mailing @Bellsouth.net & resolution maybe
- From: Justin - synacs
- Re: Exchange problems mailing @Bellsouth.net & resolution maybe
- References:
- Exchange problems mailing @Bellsouth.net & resolution maybe
- From: Justin - synacs
- Exchange problems mailing @Bellsouth.net & resolution maybe
- Prev by Date: Re: Adding a 2nd DC to an SBS 2003 network
- Next by Date: Re: Configure Netcomm NB5Plus4 with SBS2003 for VPN
- Previous by thread: Exchange problems mailing @Bellsouth.net & resolution maybe
- Next by thread: Re: Exchange problems mailing @Bellsouth.net & resolution maybe
- Index(es):
Relevant Pages
|
Loading