I'd also like to see this presented
as PowerShell script.
I've done so handling of the raw
message tracking logs in PS, and
reliably parsing the logs seems like
it's more complicated than it needs
to be. While the logs are in .csv
format (a huge improvement over
Exchange 2000/2003), the server
only quote-delimits the log entry
fields when necessary due to
imbedded reserved characters.
This makes parsing rather difficult
since most of the fields will never
contain those characters and will
never be quoted. Others may or
may not be.
Subject lines seem to get quoted
more frequently than any other field,
but I've see odd syntax result in
sender address and return path
fields being quoted.
Can we get some insight into the
parsing logic being used for the
"roll-your-own" folks?
Microsoft