[mlmmj] Exposing the message IDX number better & large archives

[mlmmj] Exposing the message IDX number better & large archives

[Robin H. Johnson]

mlmmj archives mails by an index number, which is a file sequentially
created in the archive directory.

The only places the IDX number gets exposed presently are:
- return-path / MAIL FROM of mail
- bounce probe listing

In some cases, Return-Path can be mangled by later mail servers (and
remailers), so the IDX gets lost.

Can we add a substitution or dynamic header code to inject the number
into a real header for regular list mail?

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

Re: [mlmmj] Exposing the message IDX number better & large archives

[Ben Schmidt]

Yeah. I've had difficulty finding the index in the past, too, e.g. to retrieve 
old/missed messages. A substitution seems the perfect way to deal with this, and 
the list admin can put it in a header if they want (and eventually we'll probably 
get around to shipping it in the best practice headers).

Could you put it on the bug tracker for me? It shouldn't be too much work, but it 
will be forgotten for sure if it's not somewhere organised.

Smiles,

Ben



On 17/08/2016 7:24 am, Robin H. Johnson wrote:
> mlmmj archives mails by an index number, which is a file sequentially
> created in the archive directory.
>
> The only places the IDX number gets exposed presently are:
> - return-path / MAIL FROM of mail
> - bounce probe listing
>
> In some cases, Return-Path can be mangled by later mail servers (and
> remailers), so the IDX gets lost.
>
> Can we add a substitution or dynamic header code to inject the number
> into a real header for regular list mail?
>