Quick Update: On 08/20/2010 I contacted support and requested that my case be escalated. It's now sitting with the Development Team (with no new information and no target date for a fix).
Previously, I believed the problem may have been somehow related to a patch; however, now I believe that this problem has been occurring ever since we implemented this appliance. We had an older appliance that I stepped through the upgrade process from v6.5.3 to v6.7.2 back in May, and the log files functioned properly on that appliance. In June we replaced the old appliance with a new appliance and added the encrypted email feature at that time. In speaking with one of my cohorts who spearheaded the implementation of the new appliance, he does not believe that logging has ever functioned properly on this new appliance. The new appliance was built from CD at v6.7.2 and has been patched up to HF3.
Am I the only person encountering this problem (apparently)? Thanks!
This is the first I have heard of this issue, do you have a case number I could look at?
Case number provided to Ivan Jahnke via PM.
Ivan was a great help to me on this issue! The root cause of my missing binary log file was that I had checked the boxes to delete the logs after FTP (Reporting > Reporting Advanced > Logs). After un-checking these "delete" boxes, Ivan restarted the services and the binary log file regenerated. I am now relying solely upon the log file cleanup schedule to handle log file cleanup (Administration > Cleanup Schedule > LogFiles) and, for the past three or four days, my binary log file has remained intact and functional. I'd highly recommend NOT using the "delete" checkboxes under Reporting Advanced / Logs.
...Thanks again, Ivan!