[Mailman-Developers] Logging

Hi Is it possible to log to console? I've changed gunicorn configuration: accesslog='-' errorlog='-' Then logs are not written to log files, but I can't see what's being logged. I'm on a docker environment and having log files it's something that I want to avoid to control disk usage. And I'm

Re: [Mailman-Developers] Logging automatic rejects of incoming posts.

On Oct 19, 2012, at 05:26 PM, Mark Sapiro wrote: >When a handler raises Errors.RejectMessage to reject an incoming post, >nothing is logged. I have filed > in preparation for >addressing this. > >My question is what to log. I'm not sure MM3 is any

[Mailman-Developers] Logging automatic rejects of incoming posts.

When a handler raises Errors.RejectMessage to reject an incoming post, nothing is logged. I have filed in preparation for addressing this. My question is what to log. Currently, IncomingRunner logs automatic discards with the message 'Message disca

Re: [Mailman-Developers] Logging lossage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 13, 2008, at 8:48 AM, A.M. Kuchling wrote: > On Wed, Feb 13, 2008 at 05:35:21AM +0900, Stephen J. Turnbull wrote: >> This is one nice thing about SpamAssassin: it tells you which rules >> were triggered. > > This reminds me of Mailman's most an

Re: [Mailman-Developers] Logging lossage

On Wed, Feb 13, 2008 at 05:35:21AM +0900, Stephen J. Turnbull wrote: > This is one nice thing about SpamAssassin: it tells you which rules > were triggered. This reminds me of Mailman's most annoying reason for holding a message, the 'suspicious header' error/warning. It doesn't say what the head

[Mailman-Developers] Logging lossage

Moved from mailman-users. Mark Sapiro writes: > If this is the case, there will be 'Message discarded' entries in > Mailman's vette log, but they will only tell you the message was > discarded, not why. I've long thought that this is a design bug. This is one nice thing about SpamAssassin: i

Re: [Mailman-Developers] Logging issues on the trunk

On Tue, 2006-04-25 at 14:46 -0700, Mark Sapiro wrote: > There are a few remaining issues regarding logging in the svn trunk. Thanks. I think all these issues should be resolved now, however the scripts/* scripts have only been minimally tested. -Barry signature.asc Description: This is a digi

Re: [Mailman-Developers] Logging issues on the trunk

> Also, if you're interested in working on Mailman 2.2, let us know. I'd > like to get more people involved! I am interested; there are parts of my MySQL plugin patches that are unrelated to MySQL, but permit to make the UI better for big lists. -- Fil __

Re: [Mailman-Developers] Logging issues on the trunk

On Wed, 2006-04-26 at 19:20 -0700, Mark Sapiro wrote: > Barry Warsaw wrote: > >Looks like that's a Python 2.3/2.4 compatibility issue. Dang. Okay, > >I'll figure out a workaround for that. > > > It doesn't seem to me to be 2.3/2.4 compatibility. It doesn't work for > me with 2.4.1 and it didn'

Re: [Mailman-Developers] Logging issues on the trunk

Barry Warsaw wrote: > >On Tue, 2006-04-25 at 14:46 -0700, Mark Sapiro wrote: >> 1) The ReopenableFileHandler.__init__ method in Mailman/loginit.py >>calls >> >> logging.FileHandler.__init__(self, filename, mode, encoding) >> >>This method only allows the instance, filename and mod

Re: [Mailman-Developers] Logging issues on the trunk

On Tue, 2006-04-25 at 14:46 -0700, Mark Sapiro wrote: > There are a few remaining issues regarding logging in the svn trunk. > > 1) The ReopenableFileHandler.__init__ method in Mailman/loginit.py >calls > > logging.FileHandler.__init__(self, filename, mode, encoding) > >This met

[Mailman-Developers] Logging issues on the trunk

There are a few remaining issues regarding logging in the svn trunk. 1) The ReopenableFileHandler.__init__ method in Mailman/loginit.py calls logging.FileHandler.__init__(self, filename, mode, encoding) This method only allows the instance, filename and mode arguments. The enco