Advanced Log Searches
Idea shared by Montague WebWorks - 2/1/2024 at 1:55 PM
Under Consideration
Some time ago I asked if we could have improved log searches under Troubleshooting. Frequently customers will ask why they didn't get an email, or an email they sent didn't arrive, and it usually takes a very long time to piece together a life-cycle trail of the email that was sent through the SMTP, IMAP, Delivery, Declude, etc log files, copying and pasting into Textpad, sorting pasted sections into a semblance of order so you can see what the heck happened.

I suggest an inclusive log searching option (keep what you have now, add this as "advanced") that would allow searching From and To addresses on a specific date (not a range), and have the search look through *ALL* the logs, including MailSniffer, Declude and any other anti-virus etc on the server, and sort all the hits in chronological order so you can see when it hit the server first, and follow along the log outputs to see where it got caught up. I understand that each applet may use a different ID schema, but there has to be a way to reign all these logs into something that works.

I'm currently dealing with a customer that tried to email me, we're both on the same email server, and the message doesn't even appear in the SMTP log. It's in his Sent Messages folder, twice, with my correct email address, but... nothing. I'm not sure where to start looking.

Thoughts and up votes would be appreciated.
Mik MullerMontague WebWorks
Zach Sylvester Replied
Employee Post
Hello,

Thank you for your feature request. I have noted it in our product backlog. In regards to why the message did not appear in the SMTP log, if it was sent through webmail, there was no SMTP connection in the first place. However, if it was sent through Outlook using SMTP, you should be able to see it in the log. The delivery log would contain all the necessary information since the message did not leave the server.

I hope this information helps.

Thank you.
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
Its been like that in Mailenable for years.

Absolutely awesome way to search the logs.

You either type in the sender or receiver and all the emails appear that meets the criteria in the logs.

Chose one and then you can see SMTP transactions and if it ends up in spam, you could see why and what rule triggered it.
Looks like it was sent via webmail. I can see it in the Delivery log. However, I use Thunderbird ... ah. I just logged into my webmail and see a ton of email from yesterday and today that do not show up in my Thunderbird, including the emails from the customer. Oh well.
Mik MullerMontague WebWorks
Bump.

I had another customer trying to receive an email from an insurance portal (ie; automated email, likely from a different server/ip than their regular transactional server, and possibly not present in their SPF). I can see the incoming email in the SMTP logs and it looks like it passed without issue, but then it never arrives. I then RDP to my server, go to the Declude logs folder, and look for the same time stamp.

Gotta say, it's pretty frustrating that Declude uses a different log ID than SM. Is it possible to pass a log ID when calling Declude for a particular incoming email?

Anyway, having the above suggestion in place would have saved me a bunch of time.

Please upvote this suggestion, for us all.
Mik MullerMontague WebWorks

Reply to Thread

Enter the verification text