RE: SMTP error (only from Outlook)
- From: v-chacez@xxxxxxxxxxxxx (chace zhang)
- Date: Wed, 31 May 2006 05:47:00 GMT
Hi Ashley,
Thanks for posting here.
According to your description, I understand this issue is: Most mails are
sent out properly. But some emails stay in the SMTP queue.
Firstly, please answer the following questions to clarify the issue.
What is network topology? Is there a single server?
This issue appeared on specify user or all SMTP clients?
Please create a testing account, and do it again.
In Exchange System Manager\your server\Queues, what queue are the messages
stuck in? Select that queue, what's the additional information displayed in
"Additional queue information"?
Right-click a queue in which the messages are stuck, and click Force
connection, do the message go out then? If yes, in Exchange System
Manager\Connectors, right-click SmallBusiness SMTP connector and click
Properties. Is there any local bridgehead server listed in "Local
bridgeheads"? On the Address Space tab, do you have an address space "SMTP
* 1" listed? On the Delivery Options tab, is "Specify when messages are
sent through this connector" selected and "Connection time" is set to
"Always run"? Are you using a dial-up Internet connection?
What's the anti-spam/anti-virus application running on the SBS server?
Reference:
823166 Overview of Exchange Server 2003 and Antivirus Software
http://support.microsoft.com/?id=823166
Based on my experience, I suggest that we perform the following steps:
If you're using POP3 connector, it will also cause open relaying. Please
check whether KB 835734 solves the problem.
Many unexpected outbound e-mail messages appear in the SMTP queue in Small
Business Server 2003
http://support.microsoft.com/kb/835734
1> Make sure that the Exchange server is not an open mail relay. Please
refer to the following articles to block open relay:
823157 HOW TO: Examine Relay Restrictions for Anonymous SMTP Connections and
http://support.microsoft.com/?id=823157
821881 How to Modify Global Settings in Exchange System Manager
http://support.microsoft.com/?id=821881
2> Even if you block open relay, you may still see these message queues.
Let me show you how this may happen:
a. The spammer with spoofed e-mail address sender@xxxxxxxxxxxxxxx send a
mail to unknown@xxxxxxxxxxxxxxxx
b. The Exchange server find that there's no user named "unknown", thus a
NDR message is generated.
c. The NDR message is sent to sender@xxxxxxxxxxxxxxxx
So it's recommended that you disable NDR message on the Exchange server
2003 to avoid this behavior:
a. On the Exchange 2003 server, start Exchange System Manager.
b. Double-click Global Settings, and then click Internet Message Formats.
c. In the Details pane, right-click a domain name, and then click
Properties. The default SMTP domain is "*".
d. In the Properties dialog box, click the Advanced tab, and then click to
select which types of messages you want to prevent from being sent outside.
e. Stop the Simple Mail Transfer Protocol (SMTP) and Microsoft Exchange
Routing Engine services, and then restart them.
3> Then you need contact destination domain to check whether your Exchange
computer is on an unsolicited commercial e-mail list.
4> Determine whether the Exchange computer is on the Mail-Abuse.org list of
organizations that send unsolicited commercial e-mail. To do this,
follow these steps:
a. Visit the following Web site:
http://mail-abuse.org/cgi-bin/lookup
b. On the "MAPS lookup" page, type the publicly-accessible IP address of
the Exchange computer, and then press ENTER. Note MAPS stands for Mail
Abuse Prevention System.
5> Remove the Exchange computer from the Mail-Abuse.org list. To do this,
follow these steps:
a. Visit the following Web site:
http://work-rss.mail-abuse.org/cgi-bin/nph-rss-remove
b. Type the publicly-accessible IP address of the Exchange computer in the
"You can search this index. Type the keyword(s) you want to search for"
box, and then press ENTER.
c. Follow any additional instructions to complete the removal of the
Exchange computer from the list.
6> Remove the Exchange computer from any open relay block list that is not
covered by Mail-Abuse.org. OpenRBL.org maintains a query engine that links
to over three dozen open relay block lists. Each list maintains a separate
list of open relay e-mail servers, so your server may show up on some, but
not all, lists.
a. Visit the following Web site and query on your server's IP address or
Fully Qualified Domain Name (FQDN):
http://openrbl.org/
b. If your server is on any of the open relay block lists, you will receive
a link to that specific list provider''s Web site.
c. The Web site for that list provider generally provides instructions on
how to remove your server from that.Note Perform the list removal process
for every list that your server appears on. Removing your server from one
list does not guarantee that it will be removed from all lists.
======
Warning: This response contains references to third party World Wide Web
sites. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.
======
For more information, please refer to the following article:
300580:XCON: Cannot Send E-Mail Messages to a Growing List of Domains
http://support.microsoft.com/?id=300580
I know you have perform the following steps to narrow down this issue,
please double check the action step by step.
1> If you are using Smart Host to send Internet mail, please contact your
ISP to trace this issue. If you don't use Smart Host, actually you are
using DNS to send Internet mail. To do so:
a) At the command prompt, type "nslookup" (without the quotation marks) and
press ENTER.
b) If you are using an external DNS server, which is configured in the SMTP
virtual server. Type the following command at the prompt:
server external-dns-ip-address
c) Type the following command to find the MX record of the domain name to
which you cannot send mail. This is the SMTP server you should connect to
when sending mail to that domain.
ls -t MX domain-name.com
d) Type "exit" to quit.
Now you can use the telnet utility to simulate the sending mail process.
e) At the command prompt, type "telnet" (without the quotation marks), and
press ENTER.
f) At the Microsoft Telnet command prompt, type "set LOCAL_ECHO" (without
the quotation marks), and then press ENTER.
g) Type "open <server_name > 25" (without the quotation marks), and then
press ENTER.
NOTE: The server_name is the SMTP server''s server name or IP address you
got in step c.
h) Begin communication by typing the following command:
HELO
i) Type the following command to tell the SMTP server whom the message is
from:
MAIL FROM:<Admin@xxxxxxxxxxxxxxxx>
NOTE: You should replace the sender''s e-mail address with your e-mail
address.
j) Type the following command to tell the SMTP server whom the message is
to.
RCPT TO:<User@xxxxxxxxxxxxxxx>
NOTE: You should replace the recipient''s e-mail address with the one you
fail to send.
k) Type the following command to tell the SMTP server that you are ready
to send data:
DATA
l) Type the message body.
This is just a test mail!
m) Type a period at the next blank line, and then press the ENTER key to
indicate the end of the message.
n) Close the connection by typing the following command:
QUIT
4> Please let me know the results of the steps above for further research.
In addition, please collect the follow info for further analysis.
a. On your Exchange Server, open the exchange system manager
b. Right click your issue server, -> properties
c. Select diagnostics logging page, select MSExchangeTransport in the left
pane
d. Select all the items in the right pane, change the logging level to
maximum
Note: You may first back and clear the Event log before reproduce the
problem.
Hope this helps.
If anything is unclear, please feel free to let me know. I'm looking
forward to your reply.
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.
.
- References:
- SMTP error (only from Outlook)
- From: Ashley Draper
- SMTP error (only from Outlook)
- Prev by Date: RE: sbs.rww error
- Next by Date: RE: Connect virtual directory to doc library in sharepoint site ?
- Previous by thread: SMTP error (only from Outlook)
- Next by thread: Event System Log
- Index(es):
Relevant Pages
|
