>I just love quoting myself.  Actually, I seem to send my email
>before I finish my thought.  Anyway, I wrote:

 <snip for brevity>

>Let's round out this idea a little.  Both remailers would need to maintain
>all 3 subscriber lists, and would have to forward un/subscription requests
>to each other to keep the lists synchronized.  The protocol would be something
>like this:

 <snip some more for brevity>

>Everything clear?  Anything missing?  It seems to me this is the real
>goal of splitting the list: reduce the needed remailer resources, and
>at the same time, avoid splitting up a very cohesive group of people.

>-Rodney

This would place more demand on the owners of both lists, as they would
constantly be required to monitor subscribe/unsubscribe requests, as well
as remain in constant email content.  Also placing a heavier demand on the
subscriber by forcing him/her to remember where to put which address.
To automate this would require some sort of script on both systems(since
both lists are not at UMN) that polls each list each day/week/hour whatever
for a list of subscribers on each list comparing both lists, eliminating
unique addresses, and determining whether the remaining addresses are in
digest mode or not.  I foresee many CPU cycles being wasted, when the
individuals who choose to be on both lists can use their delete key to
eliminate the duplicate messages.

Cheers,

David
74 Thing
79 Westy