At 1:55 AM -0600 3/26/99, Jason L Tibbitts III wrote:
> SA> * node aliasing different names can exist for a single list, but the
> SA> permissions are managed through the node hierarchy.
> Dunno. Sounds kind of weird. You want a tree, not a directed graph or
> else you have lots of problems (loops being one of them).
Think symbolic links in unix filesystems. It's doable. About all
you'd need to do is track crossing symlinks in the namespace, and if
you've crossed it once, you don't cross again
> Ug, that is horrible, but I suppose there is no other alternative given
> that clients don't support adding headers. The problem is that you will
> end up with subject strings so long that they get truncated by some loser
> client software (40 characters). And since you base everything on the
and the first time someone replaces the subject line with their own
subject, all of the threading and reply information disappears. The
Subject Line is for Subjects. if you really need to encode this data,
create an X-foo line in the header to hold it, since that's what the
RFCs allow. And then, all you have to worry about are clients that
strip non-standard headers....
Chuq Von Rospach (Hockey fan? <http://www.plaidworks.com/hockey/>)
Apple Mail List Gnome (mailto:firstname.lastname@example.org)
Plaidworks Consulting (mailto:email@example.com)
<http://www.plaidworks.com/> + <http://www.lists.apple.com/>
Featuring Winslow Leach at the Piano!