On 10/10/24 11:13, Mark Lawrence wrote: > On Thu Oct 10, 2024 at 10:48:24AM +0200, Christian Schulte wrote: >> >> You can enable tracing which will log the information you are looking >> for. For example: >> >> smtpctl trace smtp > > Thanks for the pointer. That is however clearly more of a live trouble- > shooting feature, which I would not want to permanently enable due to > the noise in the logs. The reason why the trace function exists in the > first place :-)
Well. You wanted to trace issues with your configuration. That's what tracing functionality is for. You would not enable it when there are no issues to resolve. There haven't been any issues with your configuration. You could have easily verified that yourself by just enabling tracing. > > My request is about connecting standard log output to the smtpd.conf > configuration in a way that it isn't connected today. > Would not add any value. For troubleshooting, just enable tracing. There have not been any troubles with your configuration and you just got confused. I looked at this and already had a patch around adding what you are requesting. Does not make any sense. It's already way to noisy the way it is in the non exceptional case. In normal operation all you want to "hear" from a daemon is when things are failing for some reason needing manual action, not if some connection could be established successfully and such. Some remote connection failed authentication for you and this got logged already. Tracing this would already have been possible by enabling tracing. -- Christian
