[Mailman-Developers] Conf instance in runner different from instance in shell

nicolas nicolas at karageuzian.com
Mon Dec 2 15:42:44 CET 2013


Solved, setting up environment MAILMAN_CONFIG_FILE fixed that point

Le 2013-12-02 15:15, nicolas a écrit :
> Hello,
>
> I'm wondering why the wonderful hyperkitty archiver is not archiving
> some standard messages..
>
> I tested message injection and it work, problem may not come from
> archiver itself...
>
> in a mailman shell, i'm trying :
>
> (py27)mailman at mail:~$ mailman shell
> Welcome to the GNU Mailman shell
>
>>>> from mailman.config import config
>>>> for archiver in config.archivers:
> ...     print archiver.name
> ...
> mail-archive
> prototype
> hyperkitty
> mhonarc
>>>>
>
>
> And that's nice, that reflects my conf, well..
>
> But, adding a constructor to archive runner in order to verify in
> daemon mode (mailman start)
>
> class ArchiveRunner(Runner):
>     """The archive runner."""
>     def __init__(self, slice=None, numslices=1):
>         super(ArchiveRunner, self).__init__(slice, numslices)
>         debug_log.info('start archive trace')
>         for archiver in config.archivers:
>             debug_log.info("loaded archiver : %s" % archiver.name)
>
> debug output gives :
>
> Dec 02 14:21:02 2013 (23189) start archive trace
> Dec 02 14:21:02 2013 (23189) loaded archiver : prototype
> Dec 02 14:21:02 2013 (23189) loaded archiver : mail-archive
> Dec 02 14:21:02 2013 (23189) loaded archiver : mhonarc
>
> and that explains why messages are archived with scripting but not
> while using smtp.
>
> I'm using latest lp:mailman (slightly patched
> lp:~nkarageuzian/mailman/hyperkitty_compliance )
>
> How could we explain this behavior ?
>
> Regards



More information about the Mailman-Developers mailing list