E-mail tracking/log retention

Not so much of a technical issue, but was wondering how long everyone keeps their message tracking and/or e-mail logs around? We use an M-Series, and it looks like you can't specify retention time, rather, you have to manually configure your disk size to limit or increase the amount of data you're keeping.
I'm curios what other folks are doing, how long they're keeping message tracking data available and/or if they have an overall e-mail retention policy. I know some firms are under government guidelines to archive all electronic communication for 7 years or similar.
Thanks.

This is something that we are starting to discuss in our shop. We are just starting to have e-mail retention/archive/discovery conversations and the logs on the IronPort appliances come into that every once in a while. If it is something that is easy to do it may be advantageous to add the ability to set retention of these logs by length of time. From a technical stand point so many MB is great, logic, easy to understand. Unfortunately in the business/legal world they use a different type of thinking and like to speak in terms of days. At least, that's been my expierience.
Long live the Iron Nation
Jason

Similar Messages

Message tracking log of internal users who are all sent the mails to external domain

Hi ,
How can i get the message tracking log from internal users to external users?
We need the report of internal users who are all sent the mails to the external domain
Regards,
Sankar M
Sankar M http://messagingdevelopment.blogspot.in/

Sankar, your outbound send connector has an address space of *. So when you run "Get-SendConnector", you will see something like the following:
Identity                                AddressSpaces
Enabled
Unix System Connection                  {SMTP:*.domfreebusy.contractor.hunti... True
Outgoing SMTP Connector
{SMTP:*;10}                             True
Mailbox Journaling Connector            {SMTP:pdwastap01.huntington.com;1}      True
The middle one with the {SMTP:*;10} in my case (you may have a different number than 10 in yours) is my outbound connector. So yours will show an address space of {SMTP:*;<some number, 10 is the default>}. HTH ...

Message tracking log - time period

Hi,
How long are message tracking logs keeped on appliance?
How can i control message tracking logs.
Lots of HDD space available and I want 3 months of available Message Tracking logs.
When are Message traking logs deleted from the appliance?

Message tracking is based on the drive space available on the ESA appliance.
It is not possible to configure the # of days for retention of message tracking data. The set HDD storage allocation for message tracking data is limited. HDD storage allocation is set based on the hardware:
C1X0: 10G
C3X0: 20G
C6X0: 50G
X10X0: 50G
Your best solution in order to store mail logs/message tracking - would be to also have configured to store the mail_logs off to a syslog server --- that way you can determine the full extent/length of the retention period. (And also allows you to search/manipulate all mail_logs with a little easier access that may be available on the ESA.)
Hope that helps!
-Robert

Message Tracking logs for secondary smtp address

Hi,
There are many people sending mails to secondary smtp address instead of primary smtp address. How can i pull the report of message tracking logs if they sent it to secondary smtp address using get-messagetrackinglog cmdlet?
Sankar M http://messagingdevelopment.blogspot.in/

Hi Sankar,
If I don't understand your description, it seems that you want to get the message tracking log on an mailbox with primary SMTP address and secondary SMTP address.
If it is the case, please add both primary SMTP address and secondary SMTP address to the "Recipients" parameter. More details to see:
http://technet.microsoft.com/en-us/library/aa997573(v=exchg.150).aspx
Thanks
Mavis Huang
TechNet Community Support

Definition of timestamp field in the message tracking log

Hi,
anyone can help me with the exact definition of timestamp field that I retrieve in the messagetracking log?
I think that is the exact time by which the exchange server receive a mail and start to elaborate it
Can you confirm please
Thank you very much
Luca Pozzoli

Hi ,
Please have a look in to the below mentioned points .
Anyone can help me with the exact definition of timestamp field that I retrieve in the messagetracking
log?
Time stamp in exchange will help us identity at when and what time the message has been received and processed
from source server to destination server.
With the help of time stamps we can able to identify the message delay between the hops .
As an additional info you can review the time stamps in message headers as well on the message tracking logs.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

E-Mail Tracking-System

Hi,
I have an idea to create an E-Mail Tracking-System to analyze how many E-Mails are opened which have been send before.
Without APEX I would display a very small image in the e-mail, which would only be displayed when the e-mail is opened. Then I have to look how often this image have been load from the server.
That is not so easy to report and I think it would be easier if I can use APEX.
But I don`t know how to recognize with APEX whether an e-mail is opened or not? Can do this with an image too and would it be displayed in an APEX-View or something like that?
I would be very glad for any help on this topic.
Thanks,
Tim

Guys,
I think the images that the original author is talking about inserting into the sent newsletter is what's called a "webbug", an HTML reference to a tiny image file that resides on his HTTP server. Every time the reader opens the email with the image reference, assuming the email client will automatically display remote images (which Thunderbird doesn't), the HTTP server registers the reader's IP address.
It's been around for years and personally I think it falls somewhere between legitimate marketing and spam, depending on how it's used. I'm not a real fan, frankly.
But his technical problem is he doesn't know how to read the HTTP server's hit log from Oracle. I also think he doesn't understand enough about Apex to distinguish between Oracle and his HTTP server log.
I don't know how to read the log that tracks the "hits" either. I don't think the question is really an Apex one, but more generic.
Just trying to clarify the need,
Stew

RecipientThreadLimitExceeded in message tracking logs, queuing and holding up local email delivery to office365

Please let me know if anyone knows an answer to this one... We're in a Hybrid Exchange environment, with 2 x Exchange 2007 servers, and 1 x Exchange 2013 Hybrid server which is pointing to Office 365 for the purposes of relaying mail to O365 while
we migrate our users out there.
We have just finished migrating, but just a couple of days ago we started experiencing delays in email delivery to O365... Not all mail, but some! Incoming email or locally generated email gets relayed out through the Hybrid server and out to O365,
but not all email is delayed... only some, but it's constant. During the busiest part of the day, about 200 messages are sitting in the Queue in Exch2013... but they all eventually resolve between 5 and 45minutes. The users are not happy.
The last error in the queue viewer for each hung email reads: 451 4.4.0 Temporary server error. Please try again later.
If I look at the message tracking logs, I find an interesting item -- "RecipientThreadLimitExceeded":
2014-05-15T14:15:51.608Z,192.168.3.11,hydra,207.46.163.215,company-mail-onmicrosoft-com.mail.protection.outlook.com,RecipientThreadLimitExceeded,Outbound to Office 365,SMTP,DEFER,10307921510617,<[email protected]>,885ea3ce-a020-41b1-8950-08d13e58d6d3,[email protected],451
4.4.0 Temporary server error. Please try again later,10117,1,,,Read: This is your generic subject line,[email protected],[email protected],2014-05-15T14:16:51.608Z,Undefined,,,,S:Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel=Opportunistic;S:Microsoft.Exchange.Transport.MailRecipient.EffectiveTlsAuthLevel=EncryptionOnly;S:DeliveryPriority=Normal
I have tried to find some documentation on resolution for this RecipientThreadLimitExceeded error, but I can only come up with some Exchange 2011 documentation which recommends adding some entries to the EdgeTransport.exe.config file to bump up the RecipientThreadLimit
value... I have not found anything pertaining to 2013. I cannot even find any powershell commands to see what the current RecipientThreadLimit is on 2013! Aghg!
Has anyone seen this before, or have any recommendations?
Thank you,
Mike

After many days of frustration, Microsoft Support finally resolved this issue. Believe it or not, but the issue was actually on the Office365 side. Here's the fix:
Exchange Admin Center -> Mail Flow -> Connectors -> Inbound Connectors
Open your "Inbound from <guid>" with the "On-premises" connector type
Click on Scope -> scroll down to "Associated accepted domains"
We had an entry in there "<organization>.mail.onmicrosoft.com"... Microsoft support had us remove this entry so that the box was completely empty.
That RESOLVED it... amazing what what little entry could do. We've had this entry in there for about 2 months, and it had been working fine. Support acknowledged that several customers have had this issue, that they are working on getting it
fixed on the back-end.
Hope this helps somebody...
-Mike

Cannot locate client IP Addess in message tracking logs

Hello
Im having trouble with a client who has an Exchange 2010 environment. They wish to identify users (via their client IP addresses of their workstations) who may be sending a large number of emails.
In this environment there are two CAS servers that are hardware load balanced.
My client wishes to interrogate the Message tracking logs (I believe this is the right place) in order to identify the IP address of a client which sent the originating mails. However the message tracking logs returns only the address of the Load Balancer
and not the client IP Address of the sending machine.
Is this anyway this can resolved?
Many thanks in advance

Hi,
Or we can use
IIS Advanced Logging. Add field “X-Forwarded-For” to the Advance Logging configuration to find the real IP address of the client device. Here are steps.
Install “Advanced Logging” on each CAS server: Double click on msi file. Check the accept checkbox and click, next, next and finish for the installation.
Add field “X-Forwarded-For” to the Advance Logging configuration.
From your Windows Server 2008 or Windows Server 2008 R2 device, open the Internet Information Services (IIS) Manager.
From the Connections navigation pane, click the appropriate CAS or CHM server on which you are configuring Advanced Logging. The Home page appears in the main panel.
From the Home page, under IIS, double-click Advanced Logging.
From the Actions pane on the right, click Edit Logging Fields.
From the Edit Logging Fields dialog box, click the Add Field button, and then complete the following:
In the Field ID box, type X-Forwarded-For.
From the Category list, select Default.
From the Source Type list, select Request Header.
In the Source Name box, type X-Forwarded-For.
Click the OK button in the Add Logging Field box, and then click the OK button in the Edit Logging Fields box.
Click a Log Definition to select it. By default, there is only one: %COMPUTERNAME%-Server. The log definition you select must have a status of Enabled.
From the Actions pane on the right, click Edit Log Definition or right click and select Edit Log Definition.
Click the Select Fields button, and then check the box for the X-Forwarded-For logging field.
Click the OK button.
From the Actions pane, click Apply.
Click Return To Advanced Logging.
In the Actions pane, click Enable Advanced Logging.
Now, when you look at Inetpublogs, you will see a new AdvancedLogs folder will be available with new logs and these logs will have the client device IP address.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Is there throttling going on here? Constantly queued emails on Hybrid Exch 2013 server with error RecipientThreadLimitExceeded in message tracking logs...

Please let me know if anyone knows an answer to this one... We're in a Hybrid Exchange environment, with 2 x Exchange 2007 servers, and 1 x Exchange 2013 Hybrid server which is pointing to Office 365 for the purposes of relaying mail to O365 while we
migrate our users out there.
We have just finished migrating, but just a couple of days ago we started experiencing delays in email delivery to O365... Not all mail, but some! Incoming email or locally generated email gets relayed out through the Hybrid server and out to O365, but
not all email is delayed... only some, but it's constant. During the busiest part of the day, about 200 messages are sitting in the Queue in Exch2013... but they all eventually resolve between 5 and 45minutes. The users are not happy.
The last error in the queue viewer for each hung email reads: 451 4.4.0 Temporary server error. Please try again later.
If I look at the message tracking logs, I find an interesting item -- "RecipientThreadLimitExceeded":
2014-05-15T14:15:51.608Z,192.168.3.11,hydra,207.46.163.215,company-mail-onmicrosoft-com.mail.protection.outlook.com,RecipientThreadLimitExceeded,Outbound
to Office 365,SMTP,DEFER,10307921510617,<[email protected]>,885ea3ce-a020-41b1-8950-08d13e58d6d3,[email protected],451
4.4.0 Temporary server error. Please try again later,10117,1,,,Read: This is your generic subject line,[email protected],[email protected],2014-05-15T14:16:51.608Z,Undefined,,,,S:Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel=Opportunistic;S:Microsoft.Exchange.Transport.MailRecipient.EffectiveTlsAuthLevel=EncryptionOnly;S:DeliveryPriority=Normal
I have tried to find some documentation on resolution for this RecipientThreadLimitExceeded error, but I can only come up with some Exchange 2011 documentation which recommends adding some entries to the EdgeTransport.exe.config file to bump up the RecipientThreadLimit
value... I have not found anything pertaining to 2013. I cannot even find any powershell commands to see what the current RecipientThreadLimit is on 2013! Aghg!
Has anyone seen this before, or have any recommendations?
Thank you,
Mike

After many days of frustration, Microsoft Support finally resolved this issue. Believe it or not, but the issue was actually on the Office365 side. Here's the fix:
Exchange Admin Center -> Mail Flow -> Connectors -> Inbound Connectors
Open your "Inbound from <guid>" with the "On-premises" connector type
Click on Scope -> scroll down to "Associated accepted domains"
We had an entry in there "<organization>.mail.onmicrosoft.com"... Microsoft support had us remove this entry so that the box was completely empty.
That RESOLVED it... amazing what what little entry could do. We've had this entry in there for about 2 months, and it had been working fine. Support acknowledged that several customers have had this issue, that they are working on getting it fixed
on the back-end.
Hope this helps somebody...
-Mike

Troubleshooting Mail using the Mail.crash.log file and TN2123 CrashReporter

This morning, for apparently no reason at all, Mail began to consistently crash each time I attempted to send or reply to a message. By observing what occured in mail, opening the crash log [mail.crash.log] located here…
Macintosh HD:Users:<username>:Library:Logs:CrashReporter
…and parsing the information with the help of the Apple Developer Technical Note linked below, I was able to quickly determine that my last action just prior to sending the message—appending a signature to it—resulted in the application crashing. Simply by deleting the existing signature and recreating it, I was able to resolve the problem in only a matter of minutes.
This demonstrates how useful crash logs can be, and why they should likely be the very first place you look for an indication of trouble when an application unexpectely quits.
Here is a very short, relevent section of my Mail crash log which you can examine using the instructions linked below:
Host Name: Michael-Lafferty
Date/Time: 2006-05-15 09:37:57.885 -0700
OS Version: 10.4.6 (Build 8I127)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [64]
Version: 2.0.7 (746.2)
Build Version: 2
Project Name: MailViewer
Source Version: 7460200
PID: 1662
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.apple.WebCore 0x956065d4 khtml::CompositeEditCommand::insertNodeAfter(DOM::No
1 com.apple.WebCore 0x956b0b34 khtml::DeleteSelectionCommand::moveNodesAfterNode()
2 com.apple.WebCore 0x956b1640 khtml::DeleteSelectionCommand::doApply() + 688
3 com.apple.WebCore 0x955ff41c khtml::EditCommand::apply() + 52
4 com.apple.WebCore 0x955ff9c8 khtml::CompositeEditCommand::applyCommandToComposite
5 com.apple.WebCore 0x956a75c4 khtml::CompositeEditCommand::deleteSelection(khtml::…
This is the most significant section of a very long, multi-threaded log, because it shows the detail of the thread which crashed, the actual step at which it crashed, and the particular crash type: in this case, a EXCBADACCESS (0x0001) - KERNPROTECTIONFAILURE, indicating an attempt to write to a read-only memory location.
Here is a link to the Apple Developer documentation you can use to troubleshoot such issues:
http://developer.apple.com/technotes/tn2004/tn2123.html
Technical Note TN2123
CrashReporter

This morning, for apparently no reason at all, Mail began to consistently crash each time I attempted to send or reply to a message. By observing what occured in mail, opening the crash log [mail.crash.log] located here…
Macintosh HD:Users:<username>:Library:Logs:CrashReporter
…and parsing the information with the help of the Apple Developer Technical Note linked below, I was able to quickly determine that my last action just prior to sending the message—appending a signature to it—resulted in the application crashing. Simply by deleting the existing signature and recreating it, I was able to resolve the problem in only a matter of minutes.
This demonstrates how useful crash logs can be, and why they should likely be the very first place you look for an indication of trouble when an application unexpectely quits.
Here is a very short, relevent section of my Mail crash log which you can examine using the instructions linked below:
Host Name: Michael-Lafferty
Date/Time: 2006-05-15 09:37:57.885 -0700
OS Version: 10.4.6 (Build 8I127)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [64]
Version: 2.0.7 (746.2)
Build Version: 2
Project Name: MailViewer
Source Version: 7460200
PID: 1662
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.apple.WebCore 0x956065d4 khtml::CompositeEditCommand::insertNodeAfter(DOM::No
1 com.apple.WebCore 0x956b0b34 khtml::DeleteSelectionCommand::moveNodesAfterNode()
2 com.apple.WebCore 0x956b1640 khtml::DeleteSelectionCommand::doApply() + 688
3 com.apple.WebCore 0x955ff41c khtml::EditCommand::apply() + 52
4 com.apple.WebCore 0x955ff9c8 khtml::CompositeEditCommand::applyCommandToComposite
5 com.apple.WebCore 0x956a75c4 khtml::CompositeEditCommand::deleteSelection(khtml::…
This is the most significant section of a very long, multi-threaded log, because it shows the detail of the thread which crashed, the actual step at which it crashed, and the particular crash type: in this case, a EXCBADACCESS (0x0001) - KERNPROTECTIONFAILURE, indicating an attempt to write to a read-only memory location.
Here is a link to the Apple Developer documentation you can use to troubleshoot such issues:
http://developer.apple.com/technotes/tn2004/tn2123.html
Technical Note TN2123
CrashReporter

Exchange Server 2010 - Message Tracking Logs - Log file creation

Hi,
I would like to find out on the behavior of the exchange server in the way that it logs the message tracking.
Currently the parameter used is
MessageTrackingLogMaxDirectorySize - 10GBMessageTrackingLogMaxAge - 30daysI would like to check when the Max Directory Size has exceeded the value indicated, does Exchange server immediately deletes the oldest log file to make space for the new logs?And in the event that the oldest file is being open or locked, will exchange server delete the next oldest file? or it will reattempt to delete the "locked" file for a period of time?Lastly, when these "oldest" files is not able to be deleted, will exchange server stops logging new tracking events?Thanks!

Hi Zack,
Thank you for your question.
If you have configured the parameter of “MessageTrackingLogMaxDirectorySize” and “MessageTrackingLogMaxAge”, we think you have enable circular logging, it will delete the oldest message tracking log files for new log file when the either of the following
conditions is true:
The message tracking log directory reaches its specified maximum size.
A message tracking log file reaches its specified maximum age.
In addition, it didn’t exceeded the value indicated.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

More Info Needed in Message Tracking Logs in Exchnage 2010 MAILBOX

Hello All
I would like to understand more on message tracking which was little bit confused for me 2 days back.
As far as i can know, HUB SERVER is the main part of the messaging tracking is playing vital role in Exchange 2010.
also, mailbox roles too...
i can see the message tracking logs created in mailbox is only usefull , for web interface for message tracking is part of the Exchange Control Panel and provides very basic search
functionality to search for messages either sent by or received by a mailbox, based on the sender, recipients, and subject line.
so message tracking logs which is available in mailbox is only user for end users who can perform the message tracking by themself vua ECP without installing EMC. -- AM I RIGHT
How will message tracking logs created in mailbox servers .......... will it replicate from HUB servers?
so if i have 4 mailbox servers, will all the mailbox servers having the same message tracking logs? or we may get different
Your information is much valuable to better understand on MT

Hi Rush,
Please checkout this technet blog available at below link which clarify your concern in depth:
http://blogs.technet.com/b/messaging_with_communications/archive/2011/04/22/how-to-track-message-in-exchange-2003-2007-2010.aspx
http://exchangeserverpro.com/exchange-2010-message-tracking/
However, a helpful resource you can checkout at here(http://www.exchangereports.net/) which comes with similar features while need to track mailboxes(sent/received emails), server traffic reports or folder reports in exchange server. It facilitates to produce
the reports in various format which suits better in our environment.

Attachment Name of emails from Message Tracking Logs

Hi,
I have been able to get NDR from message tracking logs in Exchange 2010 using Exchange Management Shell. Is it possible to include the file name of the attactment of the emails from the report generated?
Regards,
Emansky
All the best, Eman Lacuata

Hi,
No that is not possible.
Message tracking will never include names of attachments.
Martina Miskovic - http://www.nic2012.com/
Agree.
Refer to:
Managing Message Tracking
http://technet.microsoft.com/en-us/library/bb124375(EXCHG.80).aspx
Note: Content specific to Exchange 2010 SP1 will be available at a later date.
Best Regards Fiona Liao E: [email protected]

Tracking logs 2010

Is there a default location for message tracking logs on Exch2010?
And what format are they in?
can they be analysed in any other tool than exchange, if for example you had recovered the logs from a backup?

Hi ,
Please have a look in to the below mentioned things.
Is there a default location for message tracking logs on Exch2010?
It depends on the drive on which you have installed exchange.Please use the below command to check the message tracking log file location.
Get-TransportServer | fl name,*messagetrackinglogpath*
And what format are they in?
*.LOG formart
can they be analysed in any other tool than exchange, if for example you had recovered the logs from a backup?
http://www.slipstick.com/addins/exchange-server-usage-reporting-and-analysis-tools/
Note: As per my knowledge for analyzing message tracking logs instead of going for a third party you can use the exchange management console or shell and that would provide you the good result for your query.
Reference blog for message tracking :
http://exchangeserverpro.com/exchange-2010-message-tracking-log-search-powershell/
If you wanted to have the message tracking logs for a long period ,you can simply raise the message tracking log retain age on all the hub transport servers.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Ironport Message Tracking Logs

Hi,
Am unable to post this in the Ironport Security section due to the restricted access on my Cisco support login ID.
I need to export the message tracking logs for a particular user for the last one year (or the period for which logs are available) on Ironport M660.
The GUI only reports 250 search results for every search and I have approx to export logs for approx. 20,000 messages.
Is there a Unix/CLI command which can be executed to export all tracking logs between a time frame in Ironport?
Thanks.

This was a defect covered in the 8.5.6-093 release:
http://www.cisco.com/c/dam/en/us/td/docs/security/esa/esa8-5-6/ESA_8-5-6_HP1_Release_Notes.pdf
So, if running the -074 revision... found defect:
https://tools.cisco.com/bugsearch/bug/CSCuq49620
I wouldn't say that running repengupdate force is not suppose to be done, aside from a formal request... is odd to see or hear that would have been mentioned. With the force updates for any of the processes on the ESA, this is usually always a good troubleshooting step for any customer --- as the process will instantly call out to the updater servers, compare manifests, and then pull regardless of what is running the latest engine and rules sets for the process... and then silently implement in the background. While for the customers who might have bandwidth limiting options running on their network, the only major side effect is the package size that is coming across... since the engine is tagged into the rules...
But, normally with antivirus and antispam - this is the most helpful to run antivirusupdate force or antispamupdate ironport force. Especially in times where the update process itself may have been interrupted with a network related hiccup or staled out download.
-Robert

E-mail tracking/log retention

Similar Messages

Maybe you are looking for