Hi Marek, Happy Easter to you, Marek, and to all on this list. May all of us each seek a spiritual awakening in our own hearts, so that we can participate in the resurrection of joy and peace in humankind. This, to me, is not a "Catholic" or "Protestant" or even "Christian" experience and goal. It is a universal human potential which some of these spiritual luminaries in history have discovered and tried to tell us about. It cuts across all religious boundaries and erases all distinctions that seem to separate one person or people from another.
Sunday, April 12, 2009, 1:23:26 AM, you wrote: > Hello all, > Sunday, April 12, 2009, Bob Riley wrote: >> I just just going to use a backup utility to back up My Documents (the >> Windows folder), and I realized that, with my TB mail filed under My >> Documents\The Bat, there is a GIANT file called IMAP.log_1 which is >> around 264 MB!! I was shocked at its size. It accounts for about >> 25% of the size of my total "My Documents" folder, which has many >> subfolders, going back into the early 1990's. > these logs are created because You have turned on Protocol logging in > Account properties | Transport | Protocol logging. > And You have more logs because You have more connections enabled in IMAP > Fine-tune. Hmmm... I never consciously turned on Protocol logging. I suppose it is used for troubleshooting in case of connection problems. But due to the "Law of Unintended Consequences," it became a monster (in the size of the log file developed). I have now turned off that protocol logging. I wonder how many IMAP users even know of such a feature or such a practice. I have no idea. Thank you for your informative reply, Marek! I did a Google search on IMAP Protocol Logging just now, and I found this article (from among others): ******************************** I had a question come across my desk the other day about how to enable protocol logging in Exchange 2007 for IMAP and POP. Protocol logging for these protocols generates comma delimited logs similar to HTTP logs (except for IMAP). In Exchange 2003 you enabled these with a couple of registry tweaks. These don't however work in Exchange 2007. Exchange 2007 instead uses a couple of config files on the file system. To enable the logging for IMAP, you would do this: Browse to C:\Program Files\Microsoft\Exchange Server\ClientAccess\PopImap Open Microsoft.Exchange.Imap4.exe.config with text editor (e.g. Notepad) and scroll to the bottom Modify ProtocolLog from false to true. Modify LogPath as necessary Restart the MsExchangeImap4 service For POP, simply edit Microsoft.Exchange.Pop3.exe.config instead and restart the MsExcahngePop3 service. You can use a number of tools to parse the logs, although one tool I would recommend is LogParser from Microsoft. ******************** Here is the link to the above article: http://briandesmond.com/blog/exchange-2007-protocol-logging-imap-pop/ Apparently that feature can be turned on (if desired) in Mozilla mail-news applications, such as Thunderbird: https://wiki.mozilla.org/MailNews:Logging -- Take Care, Bob -- Using The Bat! 4.1.11.13 Windows XP 5.1 build 2600 Service Pack 3 ________________________________________________________ Current beta is 4.1.11.13 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
