Chuq Von Rospach proposed,
| How about creating another header:
|
| X-No-Archive-List: (descriptive string).
|
| If that exists, then the string either explains the policy or points to a
| URL that explains the policy. If that exists, you don't archive that list
| without following the policy.
Perhaps
X-No-Archive-List: <listid> (descriptive string)
so that it can be detached from the rest of the message and still identify the
list to which it pertains.
Did list IDs ever make it to the RFC stage, though?
Follow-Ups:
References:
|
|
