Solved

Exchange 2003: only subject arrives at destination. Error: No message collected

Posted on 2006-07-10
5
1,074 Views
Last Modified: 2008-02-01
Working in a small business 2003 evironment. A couple of times a week, we have the problem that recipients only receive the subject of the email that's being send. Sometimes, but not always, the receiver sees the following message in the body of the email:

<<< No Message Collected >>>

I just activated logging on the SMTP protocol. But since it only happens couple of times a week, it could take a while.

Don't know if it could be of influence, but i did notice the following, in the properties of my 'default SMTP virtual server', under 'delivery' and then 'advanced' is the setting to check the DNS of your fully-qualified domain name. If I check that setting, I receive an error 'The domain name is not valid'.

Furthermore, we are running Symantec Mail Security for MS Exchange, but I believe that only checks incoming mail, not outgoing.
Also, we are forwarding our SMTP mail to the mailserver of our ISP.


0
Comment
Question by:Constant IT Support
  • 2
5 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 250 total points
ID: 17077471
The check DNS button usually fails. That will have nothing to do with this problem.

It isn't 100% clear from your message, but this is for outbound email? Email leaving your server to be sent to someone outside?

If so, it is going to be very difficult to prove where the message is being stripped.
My instinct is usually to blame the Symantec product. When I do that I am often not wrong - Symantec's products seem to cause more problems than anything else.

Unfortunately to test whether the Symantec product is at fault, it has to be removed. Disabling it is not enough, as the product still has hooks inside Exchange.
Also make sure that no desktop AV application is not scanning any of the /exchsrvr directory.

Simon.
0
 

Author Comment

by:Constant IT Support
ID: 17079415
Yes, problem is with outbound mail.
Symantec only scans inbound mail voor virusses and spam I believe. Could this still be the problem then?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17080737
The antivirus product is usually on the transport mechanism. So while it isn't acting on anything on the outbound traffic, it will still be interfering. The only way to test that is to remove it.

The point I am trying to get across is that until you have exhausted all possibilities at your end, no ISP is going to listen to you. Remember all ISPs are only interested in one thing - finding something else to blame. You have to rule out everything else so that when they tell you it isn't their problem, you have as much proof as you can to say that it isn't something with your setup.

Simon.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

680 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question