We help IT Professionals succeed at work.

Inbound mail vanishes

Bill Herde
Bill Herde asked
High Priority
Last Modified: 2018-10-05
Email sent from Constant Contact cannot be seen.  The system is two exchange 2010 servers across two sites.  DAG is in place.  Inbound mail comes through Symantec Mail Security Service, and servers will receive mail only from there.

On my mailbox I have set up automatic forwarding of received email to my home email address.  In exchange, not Outlook.  When sending test (or live) email from Constant Contact to my work email address, it never shows up in inbox, or any other folder.  This is consistent using either Outlook or webmail (with Outlook turned off). However, it does get forwarded to my home email, which is a pretty good indicator that the exchange server did indeed process the message. I do see the entry in the SmtpReceive log as well.

The built-in anti-spam for exchange was not enabled, so I enabled it and set all the filters to disabled onboth servers. (do I need to restart more than transport service?)
Using the message tracking tool I cannot find the message in my mailbox anywhere.

Edit:  I should mention this is a global problem.  It does not matter who the recipient is, they do not get the email.

I need to find out where it went, and why???
Watch Question


check the header information on your email to check what servers are processing your email. Also check the symantec logs for in and outboud traffic
Bill HerdeOwner


The header on the email received on the personal account shows route from Constant Contact, to Messagelabs,(symantec) to our local server, to Messagelabs, to Google.  This is the expected route.  There would be little value to confirm this on the messagelabs logs.
Using the mail flow troubleshooter (a 'new' thing for me!) I found and tracked the message.  the relay outbound went through without a hitch, but when sending to internal address, it stopped on a transport rule that  failed it.  What I did not notice previously was the messages from constant contact have you enter the desired return address. The return address entered was "inquiries@---.com" which is a mailbox that is set to receive mail only, and is prohibited from sending any mail anywhere.  Designated users have access to this mailbox, but reply from their real mailbox. So it looks like the spoofed return address got through the first part of the transport service and relayed out to outside email OK, but when moving it to mailboxes hit the rule that said no.  So a receive connector can ingest email and apply a discreet mailbox setting that forwards a copy outbound, but the same discreet mailbox applies a transport rule that prevents it from being put in the mailbox.  Sounds like some application of reverse logic where it didn't check to see if the 'sender' is allowed to send until it was about to go into the mail store. I am certain the inquiries mailbox will not send mail to anyone as designed, but did not expect that to impact mail not actually generated there!

Explore More ContentExplore courses, solutions, and other research materials related to this topic.