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 debug_peer_list = proxy:mysql:/usr/local/etc/postfix/mysql/debug_peer_list.cf mynetworks = proxy:mysql:/usr/local/etc/postfix/mysql/mynetworks.cf relay_domains = proxy:mysql:/usr/local/etc/postfix/mysql/relay_domains-sa-learn.cf, proxy:mysql:/usr/local/etc/postfix/mysql/relay_domains.cf relay_recipient_maps = proxy:mysql:/usr/local/etc/postfix/mysql/relay_recipient_maps.cf, proxy:mysql:/usr/local/etc/postfix/mysql/relay_recipient_maps_catchall.cf, proxy:mysql:/usr/local/etc/postfix/mysql/relay_recipient_maps_postmaster.cf smtpd_client_restrictions = check_client_access proxy:mysql:/usr/local/etc/postfix/mysql/smtpd_client_restrictions-check_client_access.cf, check_client_access hash:/usr/local/etc/postfix/smtpd_client_restrictions-check_client_access-internal-mailservers smtpd_recipient_restrictions = reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_recipient_domain, check_recipient_access proxy:mysql:/usr/local/etc/postfix/mysql/smtpd_recipient_restrictions-check_recipient_access.cf, check_sender_access hash:/usr/local/etc/postfix/smtpd_recipient_restrictions-check_sender_access, permit_mynetworks, permit_sasl_authenticated, reject_unknown_sender_domain, reject_unauth_destination, check_client_access proxy:mysql:/usr/local/etc/postfix/mysql/smtpd_recipient_restrictions-check_client_access.cf check_client_access proxy:mysql:/usr/local/etc/postfix/mysql/smtpd_client_restrictions-check_client_access.cf, check_client_access hash:/usr/local/etc/postfix/smtpd_client_restrictions-check_client_access-internal-mailservers, check_client_access proxy:mysql:/usr/local/etc/postfix/mysql/postfix_whitelisted_servers.cf check_reverse_client_hostname_access pcre:/usr/local/etc/postfix/maps/fqrdns.pcre, reject_rbl_client zen.spamhaus.org=127.0.0.10, reject_rbl_client zen.spamhaus.org=127.0.0.11, reject_rbl_client zen.spamhaus.org, permit # postconf | grep mail_version mail_version = 2.11.1 > 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... 2014-10-18T00:00:13.000+01:00 maroon postfix/smtpd[75860]: connect from unknown[213.199.154.78] 2014-10-18T00:01:28.000+01:00 maroon postfix/smtpd[75860]: warning: proxy:mysql:/usr/local/etc/postfix/mysql/debug_peer_list.cf: table lookup problem 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 2014-10-18T00:03:13.000+01:00 maroon postfix/smtpd[75860]: warning: milter inet:127.0.0.1:8891: can't read SMFIC_CONNECT reply packet header: Operation timed out 2014-10-18T00:05:16.000+01:00 maroon postfix/smtpd[75860]: warning: proxy:mysql:/usr/local/etc/postfix/mysql/mynetworks.cf: table lookup problem 2014-10-18T00:05:16.000+01:00 maroon postfix/smtpd[75860]: Anonymous TLS connection established from unknown[213.199.154.78]: TLSv1 with cipher AES256-SHA (256/256 bits) 2014-10-18T00:05:16.000+01:00 maroon postfix/smtpd[75860]: warning: proxy:mysql:/usr/local/etc/postfix/mysql/mynetworks.cf: table lookup problem 2014-10-18T00:05:16.000+01:00 maroon postfix/smtpd[75860]: warning: proxy:mysql:/usr/local/etc/postfix/mysql/mynetworks.cf: table lookup problem 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. Any help gratefully received! Regards Steve -------- Original Message -------- Subject: Re: Fw: table lookup problems warnings and not critical? (22-Oct-2014 21:18) From: wie...@porcupine.org To: postfix-us...@spectrumcs.net > steve: > > 1) Is it right that a 'table lookup problem' is only a warning and > > not a critical event? In my setup I would feel it was a critical > > event and I would guess it would be in most peoples setups if > > they've gone to the trouble of using a SQL backend. > > 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. > > I see no error context and no configuration information, so I will > not speculate what the purpose of the lookup was. > > > 2) Is there any way to make a 'table lookup problem' syslog as > > critial for my setup ? > > Criticality is determined by the purpose of the lookup. > > Wietse > > To: postfix-users@postfix.org 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.
