I'm know this group isn't for MS SMTP issues, but I'm hoping some of you are
running it either as a gateway, and outbound sender or a backup server and have
run into this issue.
"I'm having some trouble writing a web-based log viewer for Microsoft
SMTP. I have set up SMTP to log to an ODBC database, which is working
fine. It's the content of the data that's throwing me for a loop.
Basically, when I query that table, I start with a from address. I can
pull out the surrounding log entries for that client host (external IP
or name), but I have no way of making sure that all the rows that come
back are from the session I am looking for.
MS MSTP interleaves the log entries. Fine, I have no problem with that.
Why don't they provide some kind of session ID? Most MTAs provide some
kind of hash value that is specific to a particular session. I don't
think any tool could get that information out of MS SMTP.
I see this as cripiling their logging. There are definitely
interleaving instances for high-traffic servers that that result in
ambiguities that are literally unresolvable, leaving the admin unable
to prove a message was handled correctly. Surely MS wasn't that dumb?
Is there some kind of session logging I'm missing? Again,
clienthost/datetime doesn't always cut it, because sessions to the same
host can be interleaved in the logs."
-Chase
Chase Seibert | Network and Systems Engineer | Bullhorn Inc. | 617.464.2440
x119 | www.bullhorn.com
