Mark Sapiro wrote:
Mohamed CHAARI wrote:
As I really need to keep possibility to have both MM archiving and
external one, I've made a small patch on Mailman, so that it accepts
both internal archiving (pipermail) and external archiving (if enabled).
In this way, there is no longer need to
Mohamed CHAARI wrote:
what about the Archiver.pyc file ? do you think it is necessary to
re-compile and re-install the whole soft ? or simply apply the patch on
Archiver.py to make it working ?
End original message. -
Python is (usually) smart enough to
Mohamed CHAARI wrote:
As I really need to keep possibility to have both MM archiving and
external one, I've made a small patch on Mailman, so that it accepts
both internal archiving (pipermail) and external archiving (if enabled).
In this way, there is no longer need to call 'arch' in
Mark Sapiro wrote:
Mohamed CHAARI wrote:
Mark Sapiro wrote:
See
http://mail.python.org/pipermail/mailman-users/2005-August/045994.html.
you mentioned, in the thread above (Aug 2005), that it would be better
to have a unique temporary file, to avoid conflict problems ...
I've tried this,
Mohamed CHAARI wrote:
Mark Sapiro wrote:
but the normal way
to do this is to just do normal archiving in Mailman and subscribe an address
to the list to do the external archiving.
I didn't understand well this solution. can you please explain it, how
can a subscriber/address do the
Mark Sapiro wrote:
Mohamed CHAARI wrote:
I'm using Mailman for lists management, in a collaboration
infrastructure site.
I configured Mailman so that an external archiver is used, but I
hesitate to run this archiver in background or foreground.
More concretely, in mm_cfg.py conf file,
Mohamed CHAARI wrote:
Mark Sapiro wrote:
See
http://mail.python.org/pipermail/mailman-users/2005-August/045994.html.
you mentioned, in the thread above (Aug 2005), that it would be better
to have a unique temporary file, to avoid conflict problems ...
I've tried this, in mm_cfg.py, using
Mark Sapiro wrote:
Mohamed CHAARI wrote:
Mark Sapiro wrote:
See
http://mail.python.org/pipermail/mailman-users/2005-August/045994.html.
you mentioned, in the thread above (Aug 2005), that it would be better
to have a unique temporary file, to avoid conflict problems ...
I've tried this,
Mohamed CHAARI wrote:
I'm using Mailman for lists management, in a collaboration
infrastructure site.
I configured Mailman so that an external archiver is used, but I
hesitate to run this archiver in background or foreground.
More concretely, in mm_cfg.py conf file, should I put:
Hi all,
I'm using Mailman for lists management, in a collaboration
infrastructure site.
I configured Mailman so that an external archiver is used, but I
hesitate to run this archiver in background or foreground.
More concretely, in mm_cfg.py conf file, should I put:
PUBLIC_EXTERNAL_ARCHIVER =
10 matches
Mail list logo