> I didn't say it happened to you. And how do you *know*, for a fact, that
> it has not happened to anybody on any of your lists? Did you ask them
> all? Or are you just assuming that this is the case because no one has
> informed you of such a situation? Has it occured to you that the possibility
> exists that it *has* happened to someone on one of your mailing lists
> and that they didn't see fit -- for whatever reason -- to tell you about it?
In which case it obviously didn't worry them enough to complain about it.
Having something in the subject line does not interfere with standard
filtering. I would never suggest to anybody to filter based on the
subject. That would be silly.
> What is at issue are other things like, is it advisable? Is it scalable?
> What problems can it cause? How does it comply with standards? What
> alternatives exist? Are those alternatives better?
Ok, and I tossed in a data point showing that it has worked well for me
and all the people that subscribe to my lists. The PHP mailing lists (see
www.php.net) are relatively busy and the audience is relatively technical.
So far nobody has complained about the list name in the subject line and
when we switched list server software last year and didn't have the
listname in the subject initially we got quite a few complaints.
The one other area where it helps is when you have several lists that
cover variations on the same topic. like x-announce, x-support,
x-development. It's nice to be able to group those in a single x folder
and when you look through it see [X-ANN], [X-SUPP] and [X-DEV] in the
subject lines. This cuts down on the number of filtered folders you need
to manage and groups things based on topics while making it obvious where
each message was posted to.
-Rasmus
