The archiver main() code currently adds an 'archived-at' header to mails (unless they have one) before they are processed.
This means that generators which use the header in any way may generate different output for the same input.
Since version 0.10, the archiver no longer stores the parsed message (it uses the original input).
AFAICT there is now no way to see the header added by the archiver.
The header should no longer be added to the parsed input message.
If it is desired to record when a message was archived, that should be done by a recording the timestamp in the ES database in a separate field.
The archiver main() code currently adds an 'archived-at' header to mails (unless they have one) before they are processed.
This means that generators which use the header in any way may generate different output for the same input.
Since version 0.10, the archiver no longer stores the parsed message (it uses the original input). AFAICT there is now no way to see the header added by the archiver.
The header should no longer be added to the parsed input message.
If it is desired to record when a message was archived, that should be done by a recording the timestamp in the ES database in a separate field.