Seth Spitzer wrote:
> Nick,
>
> If you've got cycles to work on this, work on custom header support
> instead of just adding "List-Id:".
That's most likely several orders of magnitude more work. I know why
you'd prefer that people solve the general problem, but I am concerned
that users describe the NS4x custom header as being undocumented and
hard to understand. That does not bode well for getting people to
actually _use_ this feature. I already have procmail :)
Ah well, it was only an idea. I will propose other list automation ideas
at some point in the Mozilla life cycle.
How do I mark a bug which has been determined to be fixed in the bigger
picture by something else, and will not be fixed itself in consequence?
WONTFIX? DUPLICATE?
Nick.
