Re: Logging for 'too many hops' issue

2014-09-19 Thread Tom Hendrikx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 18-09-14 17:28, Wietse Venema wrote: > Tom Hendrikx: However, it seems that the error message is only sent in the smtp dialog (554 5.4.0 Error: too many hops), postfix logging does not show anything. All I get in non-verbose logging

Re: Logging for 'too many hops' issue

2014-09-18 Thread Wietse Venema
Tom Hendrikx: > >> However, it seems that the error message is only sent in the smtp dialog > >> (554 5.4.0 Error: too many hops), postfix logging does not show > >> anything. All I get in non-verbose logging is: > >> > >> Sep 18 12:38:58 test postfix-inbound/smtpd[29852]: connect from > >> localho

Re: Logging for 'too many hops' issue

2014-09-18 Thread Viktor Dukhovni
On Thu, Sep 18, 2014 at 04:39:59PM +0200, Tom Hendrikx wrote: > >> Is there a way to detect a 'too many hops' issue from the logging, > >> preferably without changing postfix verbosity? > > > > Does the SMTP client log the rejected command (like Postfix does)? > > If not, which program should be

Re: Logging for 'too many hops' issue

2014-09-18 Thread Tom Hendrikx
On 09/18/2014 03:22 PM, Wietse Venema wrote: > Tom Hendrikx: >> We're currently in the process of parsing postfix logs into something >> that is suitable for end users. After covering lots of basic errors, we >> are working through some edge cases. Since we use customer provided data >> for relayin

Re: Logging for 'too many hops' issue

2014-09-18 Thread Wietse Venema
Tom Hendrikx: > We're currently in the process of parsing postfix logs into something > that is suitable for end users. After covering lots of basic errors, we > are working through some edge cases. Since we use customer provided data > for relaying mail, there is a possibility that something gets

Logging for 'too many hops' issue

2014-09-18 Thread Tom Hendrikx
Hi, We're currently in the process of parsing postfix logs into something that is suitable for end users. After covering lots of basic errors, we are working through some edge cases. Since we use customer provided data for relaying mail, there is a possibility that something gets mis-configured an