On Feb 16, 2015, at 10:11 PM, Andrew Stuart wrote:
>Can there only be one active archiver or multiple?
There are no limits on the number of IArchive implementations that can be
registered with the system. Mailing lists themselves can enable any or all of
the archivers registered with the system.
On Feb 16, 2015, at 06:57 PM, Stephen J. Turnbull wrote:
>It's no harder than that to write a Handler in Mailman 2, and IIRC the
>additional burden (adding the message-id-hash) in Mailman 3 is
>elsewhere in the pipeline. Here's the whole thing for MM 2:
It's a little different in Mailman 3 becau
OK looks pretty easy. Seems like I’ll just write an archiver if I want access
to archived messages.
Can there only be one active archiver or multiple? Say I wanted all messages
to go to a zip archiver as well as going to monharc or pipermail as well as my
custom archive script.
as
On 16 F
Andrew Stuart writes:
> >>Why would you want to access "messages scheduled for archiving”
> >>via REST? I have trouble imagining a use case.
>
> It would make it pretty easy to write an archiver if all I had to
> do is poll via the REST API for new messages waiting to be archived
> wheneve
Steve's explained most of the current thinking on archiving, and as you
observe, archiving is a push interface (from Mailman to the archivers).
At one point I thought about having a sort of built-in archiver that wasn't
any smarter than just an maildir or some other dump on-disk dump. Mailman 2
h
On Feb 16, 2015, at 05:01 AM, Pranjal Yadav wrote:
>So it should be possible to choose one (or more) of them in postorius. In
>/mailman/src/mailman/archiving/docs/common.rst ; It says we have Mail-Archive
>and MHonArc archivers available however there are some issues with the
>non-public lists.
>>Why would you want to access "messages scheduled for archiving” via REST? I
>>have trouble imagining a use case.
It would make it pretty easy to write an archiver if all I had to do is poll
via the REST API for new messages waiting to be archived whenever I feel like
it and put them somewher
Andrew Stuart writes:
> Is there any reason why it should not be possible to be able to
> pull messages scheduled for archiving out through the REST API as
> file attachments?
Oops, my previous message missed the subtlety that you do have the
message at the point in time you're considering. Y
Andrew Stuart writes:
> Can anyone point me in the direction of a good explanation of how
> archiving works?
There isn't one. Mailman core doesn't define an archiving function
and current opinion is that it shouldn't. It just defines an
interface for attaching the archiver or archivers you pr
Hello Andrew
I may not be the best person to answer this but I will try to explain my
views, from the bug https://bugs.launchpad.net/postorius/+bug/987100 I
started looking at archivers and I talked to Florain and Abhilash. The bug
says that the tri-state for archiving is yet not available in post
Can anyone point me in the direction of a good explanation of how archiving
works? I’ve found bits and pieces but the picture isn’t totally clear - it
appears that archiving requires some sort of archive handler function to be
written and installed as part of Mailman?
Is there any reason why it
11 matches
Mail list logo
