On Fri, Jun 12, 2015 at 06:54:21PM +0300, Liutauras Adomaitis wrote:
> I need to debug delivery problems from certain IP. For that I add this IP
> to main.cf debug_peer_list and restart postfix. All looks fine, connections
> from that IP produces a verbose logs, however there is a gap of 30s in the
> logs.
If your syslog is lossy, capture traffic from that addresss with
"tcpdump -s0 -w /some/file ...". Alternatively, log locally, rather
than or in addition to a remote syslog server.
> I have quite a large number of ldap lookup tables configured. Logs show
> that postfix enters a stage of >>> CHECKING RECIPIENT MAPS <<<, does a
> several ldap lookup tables checks and then silent for 30s, then I see a
> QUIT command comming from sender IP (a timeout probably). So most
> interesting information is just not shown.
>
> dict_ldap_get_values[1]: search returned 24 value(s) for requested result
> attribute associateddomain
> 2015-06-10T15:29:32.267793+02:00 mx05 postfix/smtpd[28480]:
> dict_ldap_get_values[1]: Leaving dict_ldap_get_values
> 2015-06-10T15:29:32.267798+02:00 mx05 postfix/smtpd[28480]:
> dict_ldap_lookup: Search returned <the list of mydestinations>
What useful query would return a list of 24 domains? You're doing
something wrong perhaps? Your configuration is a mystery, so can't
help there.
> 2015-06-10T15:30:02.978509+02:00 mx05 postfix/smtpd[28480]: < sender[IP]:
> QUIT
> 2015-06-10T15:30:02.978576+02:00 mx05 postfix/smtpd[28480]: > sender[IP]:
> 221 2.0.0 Bye
>
> It looks to me that there is a limit of data which can be logged, therefore
> it is just omited. BTW - logs go to remove rsyslog server. Postfix version
> 2.6.6
No such limits in Postfix.
--
Viktor.
