On 9/20/12 9:28 PM, "Franck Martin" <[email protected]> wrote:
> Aggregate reports could be complicated to do, it obliges you to have an
> async system. You may want to consider forensic reporting before doing
> the aggregate reportŠ
I considered that, but thought it'd be even more disruptive to send
forensic reports when aggregate was requested by the sender. ("Management
is not responsible for serving you regular when you requested decaf."
Akbar & Jeff's Java Hut)
> Also, if the volume is small to medium, just creating a purpose log
> with a daily rotation, may be enough for doing aggregate reports.
True, but aggregating across multiple geographically-distributed clusters
can get tricky.
J
John Sweet
Principle Software Engineer
Mimecast North America Inc
500 Howard Street, Suite 405 San Francisco, CA 94105
mobile 00 1 415 425 3743
tel: +1 800 660 1194
web www.mimecast.com
The information contained in this communication from [email protected] is
confidential and may be legally privileged. It is intended solely for use by
[email protected] and others authorized to receive it. If you are not
[email protected] you are hereby notified that any disclosure, copying,
distribution or taking action in reliance of the contents of this information
is strictly prohibited and may be unlawful.
Mimecast Services Ltd. is a company registered in England and Wales with the
company number 04901524 VAT No. GB 123 4197 34 Email Address: [email protected]
This email message has been scanned for viruses by Mimecast.
Mimecast delivers a complete managed email solution from a single web based
platform.
For more information please visit http://www.mimecast.com_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
