Greetings, Jake. On 20 ??????? 2006 ?., 0:24:54 you wrote: > I have to agree. The logging in QMail plain sucks. It's almost made me > switch to Postfix a few times. Unfortunately, I don't see any way of > correlating the messages without modifying the patches, since there is > no common discrimination between the logs. What a message is called > (handle) in one log is something completely different in another log. If > someone modified the various patches (a new patch, I think) to keep > something common between the messages (even just a number that starts at > 1 and increments) and found some way for the next daemon to keep track > of this number and splice it into the logs I think we'd have something > really good here. Otherwise you're at what I sent to Quinn a while back: > cat * | grep [EMAIL PROTECTED] | tai64nlocal > between the logs to find messages that come in at roughly the same > times. I know this has given me problems in the past when multiple > messages come in for the same recipient at the same time (high volume > machine, LWQ based, not even Toaster). Not a solution, but my 2 cents. This trouble in qmail came from its main advantage: DJBs style of coding is strictly attached to The Unix Way (TM) of doing jobs. All tasks in qMail are done using small-and-bulletproof utilities, doing only a small part of greater job, but doing it very well. That's is the cause of trouble.
Any message qMail receives through qmail-smtpd has no any unique ID until it gets queued by qmail-queue handler. After a message gets queued, and until it disappears from queue - it has an unique ID, that is taken from the basis on unix virtual file system - the file's inode number for a file containing the message in queue. It is possible (and would surely happen) for a different messages to got a same ID (inode) number, if they are not being in the queue at the same time. If we would like to change this behavior - we will have to totally rewrite all the qmail, resulting in less robust and stable MTA, with tonns of inherited code from qMail that won't fit good. In such case it's easier to switch to another MTA, instead of hacking up the stable system that do its job well. My approach is to aggregate all the logs from different services to a SQL-based database, and then to do several queries allowing me to quickly and relatively easily find all the info about any message in question. -- Best regards, Alexey Loukianov mailto:[EMAIL PROTECTED] System Engineer, IT Department, Lavtech Corp --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
