1 (edited by blade 2011-10-24 14:36:08)

Topic: Temporary lookup failure ...what is the problem?[SOLVED]

Im getting a lots of Temporary lookup failure messeges in my maillog. I readed that problem could be  mydestination statement in postfix main.cf file.
My distribution is centos 5.6

mydestination statement in my main.cf file :
mydestination = $myhostname, localhost, localhost.localdomain, localhost.$myhostname

2

Re: Temporary lookup failure ...what is the problem?[SOLVED]

It's hard to understand what you explained. Please post detail Postfix error log instead.

3

Re: Temporary lookup failure ...what is the problem?[SOLVED]

Im getting huge amount of this logs :

Sep 24 16:59:33 mailserver postfix/trivial-rewrite[23831]: warning: transport_maps lookup failure
Sep 24 16:59:33 mailserver postfix/trivial-rewrite[23831]: warning: transport_maps lookup failure

Sep 24 17:03:55 mailserver postfix/scache[3305]: statistics: domain lookup hits=0 miss=1 success=0%
Sep 24 17:03:55 mailserver postfix/scache[3305]: statistics: address lookup hits=0 miss=1 success=0%

Sep 24 17:09:16 mailserver postfix/smtpd[2534]: NOQUEUE: reject: RCPT from unknown[X.X.8.22]: 451 4.3.0 <newsletter@example.com>: Temporary lookup failure; from=<newsletter@example.com> to=<biuro@example2.pl> proto=ESMTP helo=<smtp.xxx.xxx.pl>

ps. sorry for my bad language ,my English is poor

4

Re: Temporary lookup failure ...what is the problem?[SOLVED]

Check your settings in Postfix transport_maps lookup files, i guess the username or password is incorrect.

5 (edited by blade 2011-09-27 01:54:09)

Re: Temporary lookup failure ...what is the problem?[SOLVED]

ZhangHuangbin wrote:

Check your settings in Postfix transport_maps lookup files, i guess the username or password is incorrect.

If you mean access data from files /etc/postfix/mysql/transport_maps_user.cf and /etc/postfix/mysql/transport_maps_domain.cf I can log in to mysql with user and password from this files without any problems.

And I think that problem occurs only periodically, or in certain cases (do not yet found a pattern).  this is output from pflogsumm -d today --problems_first -e /var/log/maillog


Postfix log summaries for Sep 26

Grand Totals
------------
messages

  22618   received
  26262   delivered
    258   forwarded
    343   deferred  (537  deferrals)
     94   bounced
  18023   rejected (40%)
      0   reject warnings
      0   held
      0   discarded (0%)

   7436m  bytes received
   8733m  bytes delivered
   3943   senders
   2194   sending hosts/domains
   3123   recipients
   1355   recipient hosts/domains


message deferral detail
-----------------------
  error (total: 168)
       168   address resolver failure
  local (total: 16)
        16   address resolver failure

And today when I was looking in maillog I noticed that policyd logs time stamp is two hours late to podtfix log.


Sep 26 09:16:43 poczta policyd: rcpt=1255028, greylist=new, host=x.x.81.26 (unknown), from=x@x.x, to=y@y.pl, size=0
Sep 26 11:16:43 poczta postfix/smtpd[1134]: NOQUEUE: reject: RCPT from unknown[X.X.81.26]: 450 4.7.1 <biuro@X.pl>: Recipient address rejected: Policy Rejection- Please try later.; from=<x@x.x> to=<biuro@X.pl> proto=ESMTP helo=<user-X.X.118.217.in-addr.arpa>
Sep 26 09:16:43 poczta policyd: connection from: 127.0.0.1 port: 47536 slots: 4 of 2044 used
Sep 26 09:16:43 poczta policyd: rcpt=1255029, whitelist=update, host=XX.XX.80.143 (unknown), from=XX@xXX.pl, to=oxx@xxxda.pl, size=113595
Sep 26 11:16:43 poczta postfix/smtpd[21880]: 21EB02810BC0: client=unknown[x.x.80.143]
Sep 26 11:16:43 poczta postfix/cleanup[6232]: 21EB02810BC0: message-id=<007c01cc7c2b$29aad040$0c00000a@niemiec>
Sep 26 11:16:43 poczta postfix/smtpd[3793]: connect from unknown[X.X.150.28]
Sep 26 11:16:43 poczta postfix/smtpd[1134]: lost connection after DATA (0 bytes) from unknown[X.X.81.26]
Sep 26 11:16:43 poczta postfix/smtpd[1134]: disconnect from unknown[X.X.81.26]
Sep 26 09:16:43 poczta policyd: rcpt=1255030, greylist=update, host=X.X.150.28 (unknown), from=newsletter@xxx.pl, to=XXX@XXX.XXX.pl, size=13384
Sep 26 11:16:43 poczta postfix/smtpd[3793]: 5D2992810D47: client=unknown[X.X.150.28]
Sep 26 11:16:43 poczta postfix/cleanup[25750]: 5D2992810D47: message-id=<01e8631ce44218b1bb1edec91033c315@www.XXXX.pl>
Sep 26 09:16:43 poczta policyd: rcpt=1255031, greylist=new, host=182.183.177.19 (unknown), from=xxxx@xx.ru, to=xxx@xxxx.pl, size=0

Is that normal?? Could that be a reason of temporary lookup failure ???

6

Re: Temporary lookup failure ...what is the problem?[SOLVED]

Sorry, i cannot find the root cause with posted log content.
If MySQL server related settings in /etc/postfix/mysql/transport_maps_user.cf and /etc/postfix/mysql/transport_maps_domain.cf are correct, i'm not sure why it happened. Maybe MySQL server was too busy.

7

Re: Temporary lookup failure ...what is the problem?[SOLVED]

Can this errors be realated to lookup failure problem?

Sep 28 00:31:53 poczta postfix/proxymap23175: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 00:36:19 poczta postfix/proxymap23175: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 01:01:52 poczta postfix/proxymap23175: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 01:41:52 poczta postfix/proxymap5268: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 01:46:19 poczta postfix/proxymap5268: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 02:01:11 poczta postfix/proxymap9010: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 02:51:52 poczta postfix/proxymap12896: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 03:11:11 poczta postfix/proxymap12896: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 03:21:52 poczta postfix/proxymap12896: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 04:01:52 poczta postfix/proxymap20343: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 04:21:10 poczta postfix/proxymap24843: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 05:11:52 poczta postfix/proxymap700: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 05:31:10 poczta postfix/proxymap700: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 05:41:52 poczta postfix/proxymap700: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 06:21:51 poczta postfix/proxymap700: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 06:41:10 poczta postfix/proxymap700: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 06:51:51 poczta postfix/proxymap700: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '='
Sep 28 08:19:24 poczta postfix/proxymap30443: warning: mysql query failed: Illegal mix of collations (ascii_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation '=

8

Re: Temporary lookup failure ...what is the problem?[SOLVED]

Here's solution:
http://www.iredmail.org/forum/post10318.html#p10318

It was a bug in iRedMail early versions, some columns uses character set "ascii", you should convert it to "ascii_general_ci" with phpMyAdmin.

9

Re: Temporary lookup failure ...what is the problem?[SOLVED]

I have everywhere ascii_general_ci and utf8_general_ci... there is no ascii collation in my tables. Maybe changing from ascii_general_ci to utf8_general_ci will help. In this post http://www.iredmail.org/forum/post10318.html#p10318 there is no answer to what type of collation change tables.

10

Re: Temporary lookup failure ...what is the problem?[SOLVED]

changing ascii_general_ci to utf8_general_ci worked for me.

11

Re: Temporary lookup failure ...what is the problem?[SOLVED]

and change all latin1_swedish to utf8_general_ci via phpmysql

12

Re: Temporary lookup failure ...what is the problem?[SOLVED]

changing to utf genral ci helped. Thanks