How to get Mailman core to provide more debug info in a running environment
Docker-mailman 0.1.1
I am using Mailman 3.1 in production and I am trying to debug a problem[1] so I tried to setting Mailman to provide more debug info in the smtp.log file[2]. I might have been doing it wrong, but in the mailman-extra.cfg I set
[logging.smtp-failure] path: smtp.log
and restarted Mailman, which stopped incoming mails until removing the added section. What is the correct way to get Mailman to provide more debug info in the smtp.log
- https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/T...
- http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html#...
Henrik Rasmussen
On Sep 28, 2017, at 07:28, Henrik Rasmussen <her@adm.ku.dk> wrote:
[logging.smtp-failure] path: smtp.log
That’s a typo/leftover in the schema.cfg comments. There is no longer an smtp-failure log so [logging.smtp-failure] can’t be used.
However you said that “stopped incoming mails”. Can you provide more information on exactly what happened? Bogus logging sections should effectively be ignored.
Cheers, -Barry
From: Barry Warsaw [mailto:barry@list.org] Sent: 28. september 2017 16:38
On Sep 28, 2017, at 07:28, Henrik Rasmussen <her@adm.ku.dk> wrote:
[logging.smtp-failure] path: smtp.log
That’s a typo/leftover in the schema.cfg comments. There is no longer an smtp-failure log so [logging.smtp-failure] can’t be used.
Oh okay. I suppose that smtp failures will be logged in the smtp.log by default then? Or otherwise, how do I increase logging if needed. For now I found the problem by consulting the mailman.log.
However you said that “stopped incoming mails”. Can you provide more information on exactly what happened? Bogus logging sections should effectively be ignored.
Actually I think my Postfix docker container got confused when restarting the Mailman core container. I just associated it with my change in mailman-extra.cfg.
-- Henrik Rasmussen <her@adm.ku.dk> University of Copenhagen, Danmark
On Sep 29, 2017, at 07:38, Henrik Rasmussen <her@adm.ku.dk> wrote:
Oh okay. I suppose that smtp failures will be logged in the smtp.log by default then? Or otherwise, how do I increase logging if needed. For now I found the problem by consulting the mailman.log.
Yes, that’s correct. Just use smtp.log.
Cheers, -Barry
On 09/29/2017 04:38 AM, Henrik Rasmussen wrote:
how do I increase logging if needed.
You can get more logging by changing the level. The default level for most loggers is 'info', but you can set it to 'debug' with an override like
[logging.template] level: debug
or for a specific logger, e.g.
[logging.smtp] level: debug
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear Henrik.
Have you able to figure out the issue you had[1]. I had similar (in your case certain mailing list, but in my case every lists on some domain). I made smtp log level: debug.
What I find is,
Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f8cac5b55c0>
When lists works it appeared on log. On failing I couldn't find this.
--a
participants (4)
-
Abhijith PA -
Barry Warsaw -
Henrik Rasmussen -
Mark Sapiro