exchange-2007exchange-2010reporting
I have two Exchange mailbox servers. One running 2007 the other 2010, both Standard edition.
I've looked at 3rd party solutions to get email statistics, and I'm sure they'll work fine. I like MessageStats in particular.
But, I'm curious if there are any free tools or scripts (or even under $500) out there that can give me a weekly report of internal emails (sent/received without going through the SMTP connectors), for both versions/servers.
Make sure that under Organization Configuration>Hub Transport>Accepted domains, you have spelled your domain correctly and that it is Authoritative.
Here are the default settings for the Default Receive Connector on my server:
The defaults for the For the Client Receive Connector are similar, but on the Authentication tab, uncheck "Exchange Server Authentication"; and on the Permission Groups tab, the only one checked is "Exchange Users".
Otherwise, it would be helpful to have the exact bounce message in its entirety.
Finally tracked down the cause. Our Cisco ASA firewall was to blame.
If you happen to be deploying Exchange 2007/Exchange 2010 Server in a multiple sites environment and using a Cisco ASA Firewall as your VPN tunnel, you’ll likely encounter issues below:
Users are only able to send emails within the same Active Directory site
When users attempt to send an email over to the next hop/Active Directory Site, under the Exchange Queue, you’ll see a Retry status: 451 4.4.0 Primary target IP address responded with “451 5.7.3 Cannot achieve Exchange Server authentication” SMTPRelay to remote AD Site
When you attempt to telnet from the Exchange Servers from both site, you’ll get such response from the telnet command: 220*************
The only way to fix this is to use the Commandline Interface (CLI) and type in this command:
telnet YourCiscoManagementIP device password (default is usually cisco) en password (Management password) no fixup protocol smtp 25 write memRemember to run these command all firewalls at each site. Once is done, telnet to the Exchange server with port 25 and you should get a normal response:
220 ExchangeServerHostName.Domain.com Microsoft ESMTP MAIL Service ready at Day, Date Month Year, Hour:Minute:Seconds +TimeZone
As soon as we did this on the ASA, mail started flowing without hassles.
Best Answer
The message tracking logs are ASCII text files and fairly easy to parse. If you're comfortable writing scripts you could probably code something quick-and-dirty that would give you what you want. With the right header definition Microsoft LogParser could probably do what you want, too.