Limits of View Logs? Debug Log IDs?
Question asked by Rod Strumbel - December 3 at 8:08 AM
When initially setting up the system we were able to search multiple days of logs (most likely due to the record count during testing).   Now when I had to try and track down where an account hack started, the View Logs (SMTP) wouldn't even go back the entire morning.  At 8am I couldn't go back any further than 6:50am.  We don't even have half our customer base up on SM yet.   I looked in the logs with a text file viewer and I can see all the records are there just fine, so it has to be something limiting in the View Logs screen of the admin interface.

Is there a way to expand the record count that will be displayed in the View logs ?

Next, I saw mention in another thread about Debug Log IDs, and I can see where they would be entered into the Troubleshooting screen, but what VALUES are even available for that.  The other thread I mention here specified 22334 or something like that.  Pretty obscure.

Where would I find what other Debug Log ID options are available?

1 Reply

Reply to Thread
Jay Altemoos Replied
The answer I got from support on this was there is a hardcoded limit of MB of data that show on screen. IIRC, they mentioned that it was something like 1MB. I run into this on our installation as well when I want to see detail and depending on what report I am pulling up, some of the data gets chopped off.

You can use the SmarterMail log analyzer and open the logs that way as well, but you will need direct server access for it. Here's a link to the utility:

I can tell you it still is kind of cumbersome to sift through logs with it. I really wish they would raise the limit to some thing like 4 or 5 mb of viewable data. Here's the link to the original question I raised and support mentioned the hardcoded limit:

Reply to Thread