Correction for the parameter name: debug-peer-list should be debug_peer_list. Wietse Venema: > deoren: > > On 8/24/2018 6:51 AM, Wietse Venema wrote: > > > deoren: > > >>> 'mail=0/1' means that Postfix rejected the MAIL FROM command (the > > >>> client sent 1 MAIL FROM command, and Postfix accepted 0 MAIL FROM > > >>> commands). > > >> > > >> Thank you for the response and for going into detail. > > >> > > >> I suspect I completely overlooked it, but do you recall offhand where > > >> one can read more about the specific fields used in the messages that > > >> Postfix logs? > > > > > > Sorry, the 'adhoc' logging subsystem is a preliminary implementation > > > that I wrote to get Postfix out the door. It is therefore not > > > adequately documented, not even the 'routine' logging. > > > > Acknowledged. > > > > > Here's asuggestion: if all your probes are sent from the same IP > > > address 192.168.2.199, then please do: > > > > > > # postconf debug-peer-list=192.168.2.199
This should be debug_peer_list. > > > # postfix reload > > > > Thank you for the tip, I will do this. I used it once before for an > > extended period of time, but couldn't sufficiently make sense of the > > verbose output to get anywhere. I should have made the time to post here > > with the results to get help deciphering them. I assume that it's > > probably best to upload a larger file of the entries to GitHub and link > > to the log file like I've done wit the config files? > > No, you would have to censor the content and I don't want to look > at censored evidence. Just take the output of > > $ grep 192.168.2.199 the-log-file | grep '[<>] ' > > (note the space before the closing quote) and then directly email > me the output for one failed HaProxy attempt. > > > On a related note, is there any way to easily filter the messages that > > result from using debug-peer-list? We currently send nearly all log > > content via syslog to a central receiver and then into a Graylog > > instance. The instance is minimally tuned, so it would probably not > > handle the load well if all backend relays send their debug messages > > over to the central receiver. > > Definitely DO NOT turn on debug logging proactively. The Postfix > logging is quite sufficient for an expert, and for a non-expert, > the noise just drowns out the useful information. > > In this case, the mail=0/1 is justification to turn on debug logging, > but only for that client, not everyone. > > Wietse >
