-------- Original Message -------- Subject: Re: Re-2: Fw: table lookup problems warnings and not critical? (22-Oct-2014 22:16) From: wie...@porcupine.org To: postfix-us...@spectrumcs.net > steve: > > > > > > Hi, > > > > Thankyou for taking the time to reply. > > > > All maps on my setup are MySQL backed. I have no local mail as such. All > > domains are virtual (I think that's the correct postfix terminology?) > > > > # postconf | grep mysql > > > [lotsa maps] > > > > That depends on the purpose of the table lookup. For example, if > > > the error could result in a delivery error, then the error is > > > critical and Postfix defers delivery. > > > > That makes sense. The problem is in my case it did't result in a > > delivery error, it resulted in a taking of delivery error. The > > servers failed to receive any email for a couple of hours as a > > result of the MySQL outage. Here's an example of the kind of > > messages I have on my logs... > > You mean, Postfix deferred the mail transaction, instead of making > the wrong decision what mail to reject or accept, and instead of > making the wrong decision where to deliver mail. Sorry, just to clarify the servers I'm talking about at internet facing, accepting emails from "the internet" for domains I've configured my postfix(s) as being virtual. > > > 2014-10-18T00:02:43.000+01:00 maroon postfix/smtpd[75860]: warning: proxy: > > mysql:/usr/local/etc/postfix/mysql/mynetworks.cf: table lookup problem > [lots more table lookup errors] > > 2014-10-18T00:05:16.000+01:00 maroon postfix/smtpd[75860]: lost connection > > after EHLO from unknown[213.199.154.78] > > > > A 'table lookup problem' resulting is not being able to take receipt > > of email is a critical situation in my setup. > > Yes. Postfix defers delivery when database lookup fails that could > result in accepting or rejecting the wrong mail or delivering mail > to the wrong place. >From looking at my logs I don't see postfix is defering anything with a 5XX >status, it's instead letting the connection from the inbound SMTP server >timeout. Hence why I felt it should be a critical alert in the logs. > It is your responsibility to take action when Postfix logs database > lookup errors. I suggest that you run a logfile watcher that raises > an alarm. I'll look into that. My concern would be that I can setup a logfile watcher to look for "database lookup errors" but what if my next problem is something else I'm not currently looking for. Is it possible to get a list of all the possible postfix warnings it could log? Perhaps I asked the wrong question at the begining of this thread. Perhaps the question should be... should "Illegal address syntax from unknown[A.B.C.D]" or "hostname W.X.Y.Z does not resolve to address 111.222.333.444" be classed as warnings? I feel a "table lookup problem" is more severe than a "Illegal address syntax from" or "hostname does not resolve to address" problem. Perhaps "Illegal address syntax from" or "hostname does not resolve to address" should be logged as info or debug? Kind regards Steve DISCLAIMER This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the authors prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in future then please respond to the sender to this effect.
