james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: cross posting: Matcher/Mailet Library
Date Wed, 15 May 2002 20:17:34 GMT

At first glance, that sounds like an interesting solution, but the overall
effect might be different from what you expect.  Yes, someone subscribed to
multiple lists would only receive one copy ... but on which list (remember
that when you reply, it typically goes back to the list address, not the
sender)?  Do we have to figure out which list has the majority of
recipients, and consider that the presumptive target?  Let us assume that we
can and do perform this sort of dynamic cross-list filtration; then what
happens when someone on another list replies?  The replies will still be
posting on different lists.

One social alternative would be to start a thread on one list, and announce
on the other(s) that such a subject has been raised.  In this case, rather
than cross-posting, I could have posted the message to the user list, and
then posted an announcement on the developer list inviting anyone not
subscribed to the user list to temporarily join it to participate, if

Even so, I do kind of like your idea of eliminating duplicates on cross-list

	--- Noel

-----Original Message-----
From: Richard O. Hammer [mailto:ROHammer@EarthLink.net]
Sent: Wednesday, May 15, 2002 15:35
To: james-dev@jakarta.apache.org
Subject: cross posting: Matcher/Mailet Library

I'm a newby, but this sounds to me like a problem that might
be solved with a Matcher/Mailet: people sending messages could
address both lists if they thought it appropriate, but any
recipient who was listed in both lists would get only one copy
of the post.

> > PS pls don't cross post, there are two lists for a reason.
> To which list would you restrict this topic?  Users who don't care about
> development subscribe only to the users list.  Developers who don't
> necessarily care to hear from users, and are only interested in
> issues, subscribe to the developers list.  In this case, the topic should
> of interest to both populations.

To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

View raw message