Quinn Comendant wrote: > I wrote a couple weeks ago about how best to trace the path of an email (an > its errors) through the different multilog files. It clearly isn't an easy > task. Whenever a customer asks me "I lost an email" I usually spend 10-30 > minutes greping, sorting, and cross-referencing log entries before I can find > what is happening. > > So I'm putting the ball out there: what tools can we use to make this easier? > I know there is qmlog in the QT+ but what I'm talking about are tools that go > beyond "show me the log" to actually be able to help answer (real life) > questions like: > > - [EMAIL PROTECTED] tried sending an email. It didn't work. Why? > - Client is waiting to receive an email from a specific sender that has not > yet arrived. Where is it? Was it blocked? > - Client says they do not receive all the mail they should. Are they > smoking crack? > - What portion of mail sent to/from [EMAIL PROTECTED] is successful/failed? > - Which remote servers are deferring (4XX errors)? Blocking (5XX errors)? > - What portion of mail is blocked by rblsmtpd, spamassassin, chkuser, SPF, > DomainKeys? > - Are there any local delivery errors because of misconfigured procmailrc, > mailfilter, broken commands, bad permissions, et cetera? > - Has there been a change in average spam score since I reconfigured SA? > - How many messages are flagged as spam but still delivered. % of total?
These are good questions. While better log analysis tools would certainly help, these seem to be general troubleshooting types of questions. I'd like to see these questions (and how to find answers) in the Troubleshooting section of the wiki. That section of the wiki is woefully lacking. Hey Kyle, weren't you (or was it someone else?) looking for some area of the wiki that needed work? (I knew there was something at the time, but didn't take the time to investigate and it's been bugging me ever since). In the meanwhile (and additionally), we could use more/better tools. > An hour of Googling turned up the following: > > - Qmailanalog has been mentioned on this before as being both very useful > but not successfully installed on the toaster. Anybody out there using it > with the toaster? > http://cr.yp.to/qmailanalog.html > > - Newanalyse seems very useful for tracing emails through the logs. > http://www.fehcom.de/qmail/newanalyse.html > > - Qlogselect has been mentioned around the web and seems to be used by > other tools. > http://www.linux-peine.de/doc/merge/man1/qlogselect.1.html > http://pyropus.ca/software/misc/qlogselect > > - Qlogtools is another oft-referenced log processing tool. > http://untroubled.org/qlogtools/ > > - A script by Charles Cazabon that generates a summary of log files: > http://www.mail-archive.com/[email protected]/msg45587.html > > So... > Anybody have any experience with these? Not me (yet). > Are there any others? sa-stats is another which is already in the QTP package. I don't know how useful it actually is. Maybe could use some enhancements. > Can we include the most useful ones in QT+? Most certainly. Any which are scripts (noarch) would be trivial. If some need compiling, it'd take a little work to package but certainly doable. > What wants to take charge of that? ;P I nominate Quinn :) (or anyone else who'd like to participate). My plate is full for a while. There are some qtp-newmodel enhancements I need to work on (among other things). > Thanks fellers! > > Quinn > -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
