I have an exchange 2007 server with all services on one server. I've been sending CDO emails just fine up until the last week and now they are all being sent to the poison queue. The emails being send are just local emails sent to internal exchange users. I'm at a loss at this point. I looked at the email after exporting them and they open in an email client just fine. I think it has to do with maybe a receive connecter but I've tried to install a new one just for local smtp but it fails every time no mater what I call it or IP address I use. Event Viewer:Poison Count is 2 for the message with RecordID 18657. The message has reached or exceeded the configured poison threshold of 2. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue. I ran the troublshooter in the tools and got this error message but makes no sense to me: Agent registered for 'OnRoutedMessage' event failed while processing a message at 2011/05/09 14:14:41 GMT - 240 with the following call stack: System.NullReferenceException: Object reference not set to an instance of an object. at Ninja.Transport.Agent.NinjaRoutingAgent.NinjaRoutingAgent_OnRoutedMessage(RoutedMessageEventSource source, QueuedMessageEventArgs e) at Microsoft.Exchange.Data.Transport.Routing.RoutingAgent.Invoke(String eventTopic, Object source, Object e) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.Dispatcher.Invoke(MExSession session) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.AsyncInvoke(Object state) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.BeginInvoke(String topic, Object source, Object e, AsyncCallback callback, Object callbackState) at Microsoft.Exchange.Transport.Categorizer.MExEvents.RaiseEvent(MExSession mexSession, String eventTopic, AsyncCallback callback, Object state, Object[] contexts) at Microsoft.Exchange.Transport.Categorizer.MExEvents.RaiseOnRoutedMessage(TaskContext context, AsyncCallback callback, MailItem mailItem) at Microsoft.Exchange.Transport.Categorizer.CategorizerComponent.Stage5OnRoutedMessage(TransportMailItem transportMailItem, TaskContext taskContext) at Microsoft.Exchange.Transport.Categorizer.TaskContext.Invoke() at Microsoft.Exchange.Transport.Categorizer.CatScheduler.JobThreadEntry(Object ignored) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

This is the CDO code I'm using. Set objMessage = CreateObject("CDO.Message") objMessage.Subject = "DO NOT SEND INVOICE" objMessage.Sender = "xx@xx.com" objMessage.To = "xxx@xxx.com" objMessage.TextBody = "Cust# - " & CustomerInformation.CodeObject.Customer & vbCRLF & "SO # - " & OrderHeader.CodeObject.SalesOrder & vbCRLF & "SO TL $" & OrderTotals.CodeObject.OrderTotal '==This section provides the configuration information for the remote SMTP server. objMessage.Configuration.Fields.Item _ ("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 ''==Name or IP of Remote SMTP Server objMessage.Configuration.Fields.Item _ ("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "10.10.10.1" ''==Server port (typically 25) objMessage.Configuration.Fields.Item _ ("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 objMessage.Configuration.Fields.Update objMessage.Send

Do you have contacts for the sender or receive or did you recently contacts for them? Can you verify that you're on the latest version of CDO? Did you do any recent Exchange updates? Verify that you're on the latest update Exchange 2007 sp3 ru3. You may also have to enable some pipeline tracing to get some more diagnostic info. Also do a simple CDO test replace your objMessage.TextBody = "Cust# - " & CustomerInformation.CodeObject.Customer & vbCRLF & "SO # - " & OrderHeader.CodeObject.SalesOrder & vbCRLF & "SO TL $" & OrderTotals.CodeObject.OrderTotal to objMessage.TextBody = test Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 6.5.8211.0 http://www.microsoft.com/downloads/en/details.aspx?familyid=e17e7f31-079a-43a9-bff2-0a110307611e&displaylang=en Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 (KB2530488) http://www.microsoft.com/downloads/en/details.aspx?FamilyID=17615f50-8a56-428c-bc1a-629795692da1 How to Enable Pipeline Tracing http://technet.microsoft.com/en-us/library/bb125018(EXCHG.80).aspxJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Thank you! I will work on these and let you know. p

Hi pltfla, I would suggest that you could post the issue on below forum, if it is related development. http://social.technet.microsoft.com/Forums/en-us/exchangesvrdevelopment/threads Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The contacts are exchange users. CDO and exchange are updated to the latest versions. The "test" in the body has the same poison results. What kinds of info should I get with the pipeline tracing? I implemented and all I'm getting is the .eml files I did notice that it shows 2 entries where the others only show 1. Routing.eml and smtpreceive.eml The .eml opens and shows the 'from', 'to', 'subject', date and the body 'test' information as it should. Could it be the 'receive connector' settings? I don't have anti spam turned on, I have a third party software doing that. Thank you for your help P

Well I figured it out. Kind of stupid.. Exchange didn't like the word "sender", changed to "from". Must have been some sort of update.. thanks