I think that it has to be all receipients.The problem is that if we get
reports about maildelivery it's after the fact, and so far we've not found the
problem here, but rather in 'the other end', and thus it makes it more
difficult to 'prove' if we don't have smtp actions in the log as well. It's
hard to document something that isn't there :-)Could I add debug for all
receipients? Or just turn up the loglevel to verbose so it includes smtp
commands?
Den lørdag den 13. oktober 2018 18.40.20 CEST skrev Matus UHLAR - fantomas
<uh...@fantomas.sk>:
On 12.10.18 17:01, K F wrote:
>I will only activate it for our outgoing send array, not for incoming. I
> know it will take up space, but our customers have expressed some wishes
> about more knowlegde of the smtp transaction, and apparently can't Seattle
> for the postfix error messages.
you can temporarily set debug_peer_list to list of peers you want to debug.
http://www.postfix.org/postconf.5.html#debug_peer_list
would that be enough for you?
>>This is not part of routine logging, because it would allow an
>>adversary to fill your file system with garbage.
>>
>>Postfix debug logging is for debugging and produces even more output.
>>That's a way of saying "do not complain about Postfix performance"
>>if you turn on debug logging.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"Where do you want to go to die?" [Microsoft]
