🚀 go-pugleaf

In article <38rela$voq@unix1.cc.ysu.edu>, doug@cc.ysu.edu (Doug Sewell) says:
>Basically what's being proposed is trashing  "non-rfc-compliant"
>articles.  In theory, it could make much of bit.* go away, and also
>e-mail gateways into other newsgroups as well (the inet groups, for
>example).

I understand the concern about broken threads, but the fact is that
the information is simply unavailable to the gateway. I see three
possible resolutions:

(1) Apply the check at POST time instead of for in-stream posts. This
    would, in effect, leave things as they are now for the gateways.
(2) Apply the check only for hierarchies in the traditional ("Big 7")
    hierarchies. All mailing lists gated to these groups would have to
    be dropped, but hierarchies such as bit.** would be unaffected.
(3) Have the gateway remove the "Re:" on the subject line. These 
    are not replies in the news sense of the word, but rather new posts.

Of these three options, the first would be best.

Jim McIntosh (jim@american.edu)
The American University
Washington DC 20016-8019 USA