Temporary Lookup Failure

82 views
Skip to first unread message

Kenny Dail

unread,
Dec 13, 2006, 2:46:33 PM12/13/06
to
Got postfix up and running, everthing works as expected 99.9% of the
time.

But occasionally when someone tries to send a message They get a
response of "Temporary Lookup Failure":

Dec 13 11:46:31 mail5 postfix/smtpd[13246]: NOQUEUE: reject: RCPT from mail.patagan.com[69.46.19.60]: 451 <us...@amigo.net>: Temporary lookup failure; from=<sen...@patagan.com> to=<us...@amigo.net> proto=ESMTP helo=<mail.patagan.com>
Dec 13 11:46:35 mail5 postfix/smtpd[14695]: NOQUEUE: reject: RCPT from unknown[66.63.190.235]: 451 <us...@amigo.net>: Temporary lookup failure; from=<sen...@iarekam.com> to=<us...@amigo.net> proto=ESMTP helo=<sys2.iarekam.com>
Dec 13 11:46:46 mail5 postfix/smtpd[14379]: NOQUEUE: reject: RCPT from mx2.blueskyway.net[204.13.171.20]: 451 <us...@amigo.net>: Temporary lookup failure; from=<1-453240-amigo.net?sen...@mx2.blueskyway.net> to=<us...@amigo.net> proto=SMTP helo=<mx2.blueskyway.net>

These are indeed temporary, if the message is tried again even a few
seconds later it usually goes ok. These errors can show up from remote
server connections or MUA connections. What I would like to know is
why these lookup errors occur (what do they mean?), and what can be
done to eliminate them. Right now we get about 10K of these per day
and they can cause some unsightly mail delays.

Postfix version 2.2.10
# postconf -n
alias_database = mysql:/etc/postfix/mysql-aliases.cf
alias_maps = mysql:/etc/postfix/mysql-aliases.cf
biff = no
bounce_queue_lifetime = 12h
bounce_size_limit = 1024
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
debug_peer_level = 2
default_destination_concurrency_limit = 10
empty_address_recipient = MAILER-DAEMON
hash_queue_names = deferred, defer active bounce flush incoming
home_mailbox = Maildir/
inet_interfaces = all
local_destination_concurrency_limit = 2
local_recipient_maps =
local_transport = local
mailbox_command = /usr/bin/maildrop -d ${RECIPIENT} ${RECIPIENT}
maximal_queue_lifetime = 12h
message_size_limit = 20000000
mydestination = $myhostname
mydomain = amigo.net
mynetworks = 5.0.0.0/8, 209.94.64.0/19, 127.0.0.0/8, 172.30.0.0/24
permit_mx_backup_networks = 209.94.64.0/19
queue_minfree = 120000000
recipient_delimiter = -
relay_domains = re-2.org slvdweller.com trappermine.com
relay_recipient_maps =
relocated_maps = mysql:/etc/postfix/mysql-relocated.cf
smtp_helo_name = mx.$mydomain
smtpd_banner = $myhostname ESMTP
smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client list.dsbl.org, reject_rbl_client cn.countries.nerd.dk, reject_rbl_client bl.amigo.net, permit
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_invalid_hostname, reject_non_fqdn_hostname
smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unknown_recipient_domain, reject_unauth_destination, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:10031, permit_mx_backup, permit
smtpd_reject_unlisted_recipient = yes
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain = $mydomain
smtpd_sasl_security_options = noanonymous
transport_maps = mysql:/etc/postfix/mysql-relay.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
virtual_gid_maps = static:465
virtual_mailbox_base = /
virtual_mailbox_domains = mysql:/etc/postfix/mysql-transport.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf
virtual_minimum_uid = 465
virtual_transport = maildrop
virtual_uid_maps = static:465

--
Kenny Dail <ke...@amigo.net>

Wietse Venema

unread,
Dec 13, 2006, 2:57:50 PM12/13/06
to
Kenny Dail:

> Got postfix up and running, everthing works as expected 99.9% of the
> time.
>
> But occasionally when someone tries to send a message They get a
> response of "Temporary Lookup Failure":
>
> Dec 13 11:46:31 mail5 postfix/smtpd[13246]: NOQUEUE: reject: RCPT from mail.patagan.com[69.46.19.60]: 451 <us...@amigo.net>: Temporary lookup failure; from=<sen...@patagan.com> to=<us...@amigo.net> proto=ESMTP helo=<mail.patagan.com>
> Dec 13 11:46:35 mail5 postfix/smtpd[14695]: NOQUEUE: reject: RCPT from unknown[66.63.190.235]: 451 <us...@amigo.net>: Temporary lookup failure; from=<sen...@iarekam.com> to=<us...@amigo.net> proto=ESMTP helo=<sys2.iarekam.com>
> Dec 13 11:46:46 mail5 postfix/smtpd[14379]: NOQUEUE: reject: RCPT from mx2.blueskyway.net[204.13.171.20]: 451 <us...@amigo.net>: Temporary lookup failure; from=<1-453240-amigo.net?sen...@mx2.blueskyway.net> to=<us...@amigo.net> proto=SMTP helo=<mx2.blueskyway.net>
>
> These are indeed temporary, if the message is tried again even a few
> seconds later it usually goes ok. These errors can show up from remote
> server connections or MUA connections. What I would like to know is
> why these lookup errors occur (what do they mean?), and what can be
> done to eliminate them. Right now we get about 10K of these per day
> and they can cause some unsightly mail delays.

The res_search() system library routine returned a TRY_AGAIN
result. Usually this means the request timed out.

You can avoid thousands of errors by running a LOCAL caching DNS
server. The amigo.net DNS records have a TTL of 10000 seconds.

Wietse

Reply all
Reply to author
Forward
0 new messages