Subj : NET 1 tidy-up
To   : Avon
From : Oli
Date : Thu Sep 22 2022 09:24 am

Avon wrote (2022-09-22):

 A> On 20 Sep 2022 at 09:19a, Oli pondered and said...

 A>>> If we do end up pruning some echomail areas and merging things
 A>>> down to few new ones I will ensure the old messages are copied
 A>>> across to the n echomail areas.

 Ol>> How would that work, technically?

 A> read/write permissions I expect.

My question was more about the copying and distribution of the old mails. Do you want to copy the messages as they are to the new echo and then export the old mail from the new echo to every downlink? Will MSGIDs and dates stay the same? I would expect some tossers / nodes would sort the mails to the DUPES or BAD area. Or do you want to forward the messages with a new header to the new echo, which would break threading. Or is there some magic tool or other way of merging echos that would avoid the problems? I'm curious if merging of old messages into a new echo is possible without creating a mess.

Anyway, I don't grant permissions to copy/merge _my_ mails from old to new echos. Quoting and cross-quoting is fine, but I expect that my original mail is distributed unmodified, which includes the AREA: line and the context they are appearing in.

My proposal: create new echos (if you really have to) and retire the old ones slowly. First read/write with weekly reminders, then read-only. When everyone had a chance to pickup the new echos, then the old ones can be purged from the Hubs / Areafix. BBSing is slow.

⁂

---
 * Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (21:3/102)

.