* Mark Sapiro :
> First of all, if the list is gone, i.e. there is no lists/LISTNAME/
> directory in Mailman's hierarchy, no currently queued messages will be
> processed. Outgoing runner or some other runner may pick up queue
> entries for this list, but the list won't be there, so the queued
> me
Thanks for your reply Mark.
I took a look in the .mbox file and unfortunately the dates in the From and
Date headers are 2000, so it seems a manual fix is in order. There's 230
messages so I'll put that on hold for now.
On Sun, Nov 4, 2012 at 11:07 PM, Mark Sapiro wrote:
> Anthony Wilson (Jaf)
Sahil Tandon wrote:
>On Tue, 2012-11-06 at 11:26:40 -0800, Mark Sapiro wrote:
>
>> In your case, the input to the hash on which runners are sliced
>> includes all the message headers and the listname so it is likely that
>> the "equivalent but different" listname messages will be in different
>> s
Eric Smith wrote:
>I want to receive all mail relating to lists that I create and
>manage into my inbox. Because there are arbitrary list names and
>also numerous domains, I think that the best way is for all list
>mail to carry an identifying mail header.
>
>Having searched the archives, I unders
On Tue, 2012-11-06 at 11:26:40 -0800, Mark Sapiro wrote:
> Actually, AvoidDuplicates.py ccould serve as a good example, but it is
> currently not actually used. It is experimental and is bot included in
> the default GLOBAL_PIPELINE.
As you noted in your follow-up, the docstring does not at all d
I want to receive all mail relating to lists that I create and
manage into my inbox. Because there are arbitrary list names and
also numerous domains, I think that the best way is for all list
mail to carry an identifying mail header.
Having searched the archives, I understand I should
edit the s
Mark Sapiro wrote:
>Actually, AvoidDuplicates.py ccould serve as a good example, but it is
>currently not actually used. It is experimental and is bot included in
>the default GLOBAL_PIPELINE.
I seem to be having more than my usual problems with
typing/proofreading this morning. The above paragr
Sahil Tandon wrote:
>
>Thanks Mark, this seems like the ideal approach. I'll try to hack
>something together borrowing from the various handlers (namely
>AvoidDuplicates.py) that are already in use.
Actually, AvoidDuplicates.py ccould serve as a good example, but it is
currently not actually use