[OT] broken-reply-to

[OT] broken-reply-to

[Lee Willis]

Can anyone provide me with a pointer to the discussion of why
mailing-lists shouldn't put in Reply-To headers.

Cheers
Lee.
-- 
I was doing object-oriented assembly at 1 year old ...  
For some reason my mom insists on calling it "Playing with blocks"

Re: [OT] broken-reply-to

[Hrvoje Niksic]

Lee Willis <lee@gbdirect.co.uk> writes:

> Can anyone provide me with a pointer to the discussion of why
> mailing-lists shouldn't put in Reply-To headers.

The document at <http://www.unicom.com/pw/reply-to-harmful.html> sums
it up pretty well.

Re: [OT] broken-reply-to

[Toby Speight]

Hrvoje> Hrvoje Niksic <URL:mailto:hniksic@iskon.hr>

0> In article <9t9u2mvvejj.fsf@mraz.iskon.hr>, Hrvoje wrote:

Hrvoje> Lee Willis <lee@gbdirect.co.uk> writes:

>> Can anyone provide me with a pointer to the discussion of why
>> mailing-lists shouldn't put in Reply-To headers.

Hrvoje> The document at <http://www.unicom.com/pw/reply-to-harmful.html>
Hrvoje> sums it up pretty well.

To bring this on-topic for ding-list:

Should the documentation of the broken-reply-to parameter link to that
document (or a mirror of it on gnus.org)?

Re: [OT] broken-reply-to

[Lee Willis]

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

> Hrvoje> Hrvoje Niksic <URL:mailto:hniksic@iskon.hr>
> 
> 0> In article <9t9u2mvvejj.fsf@mraz.iskon.hr>, Hrvoje wrote:
> 
> Hrvoje> Lee Willis <lee@gbdirect.co.uk> writes:
> 
> >> Can anyone provide me with a pointer to the discussion of why
> >> mailing-lists shouldn't put in Reply-To headers.
> 
> Hrvoje> The document at <http://www.unicom.com/pw/reply-to-harmful.html>
> Hrvoje> sums it up pretty well.
> 
> To bring this on-topic for ding-list:
> 
> Should the documentation of the broken-reply-to parameter link to that
> document (or a mirror of it on gnus.org)?

Would make things easier, patch attached :


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: docpatch --]
[-- Type: text/x-patch, Size: 548 bytes --]

--- pgnus-0.98/texi/gnus.texi   Tue Nov  9 13:00:05 1999
+++ pgnus-0.98-lw/texi/gnus.texi        Tue Nov  9 16:34:23 1999
@@ -2075,7 +2075,8 @@
 headers in this group are to be ignored.  This can be useful if you're
 reading a mailing list group where the listserv has inserted
 @code{Reply-To} headers that point back to the listserv itself.  This is
-broken behavior.  So there!
+broken behavior. If you really don't believe us we suggest you go and
+read @file{http://www.unicom.com//pw/reply-to-harmful.html}.
 @item to-group
 @cindex to-group

[-- Attachment #3: Type: text/plain, Size: 133 bytes --]


Lee
-- 
I was doing object-oriented assembly at 1 year old ...  
For some reason my mom insists on calling it "Playing with blocks"

Re: [OT] broken-reply-to

[Toby Speight]

Lee> Lee Willis <URL:mailto:lee@gbdirect.co.uk>

0> In article <lz4sevwrko.fsf@landlord.gbdirect.co.uk>, Lee wrote:

Lee> ... patch attached:
Lee>
Lee> +broken behavior. If you really don't believe us we suggest you go and
Lee> +read @file{http://www.unicom.com//pw/reply-to-harmful.html}.
                                      ^^
A stray '/' slipped in!

Re: [OT] broken-reply-to

[Karl EICHWALDER]

Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

|   Lee> +read @file{http://www.unicom.com//pw/reply-to-harmful.html}.
|                                         ^^
|   A stray '/' slipped in!

And, please consider to use @uref{...}.

-- 
work    : ke@suse.de                          |
        : http://www.suse.de/~ke/             |       ------    ,__o
personal: ke@gnu.franken.de                   |      ------   _-\_<,
        : http://www.franken.de/users/gnu/ke/ |     ------   (*)/'(*)

Re: [OT] broken-reply-to

[Lars Magne Ingebrigtsen]

Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

> Should the documentation of the broken-reply-to parameter link to that
> document (or a mirror of it on gnus.org)?

I kinda want to not have too many external links in the manual.  Sites 
come and go, but the paper remains.

Keeping a mirror on gnus.org would be nice, but that would mean
setting up mirroring software for a bunch of pages, which is, like,
ehh.

But I've put a link to this page from the Notes on News page on
Quimby. 

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: [OT] broken-reply-to

[Toby Speight]

Lars> Lars Magne Ingebrigtsen <URL:mailto:larsi@gnus.org>

0> In <URL:news:m37ljp17f0.fsf@quimbies.gnus.org>, Lars wrote:

Lars> Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

>> Should the documentation of the broken-reply-to parameter link to that
>> document (or a mirror of it on gnus.org)?

Lars> Keeping a mirror on gnus.org would be nice, but that would mean
Lars> setting up mirroring software for a bunch of pages, which is,
Lars> like, ehh.

A static copy would probably be sufficient for this one - there's no
need to keep it updated or anything.


Lars> But I've put a link to this page from the Notes on News page on
Lars> Quimby.

Great.

Re: [OT] broken-reply-to

[Karl EICHWALDER]

Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

|   Lars> Keeping a mirror on gnus.org would be nice, but that would mean
|   Lars> setting up mirroring software for a bunch of pages, which is,
|   Lars> like, ehh.

I guess you want to say, it would be a challenge ;)

|   A static copy would probably be sufficient for this one - there's no
|   need to keep it updated or anything.

For this article it might work; the article looks like famous last
words.  OTOH, a local copy often is out-of-date; this matter of fact one
reason to invent XPointers and XLinks (-> W3C); of course, software to
check the links is needed nevertheless ("mirroring software")...

Tantalus, Tantalus.

-- 
work    : ke@suse.de                          |
        : http://www.suse.de/~ke/             |       ------    ,__o
personal: ke@gnu.franken.de                   |      ------   _-\_<,
        : http://www.franken.de/users/gnu/ke/ |     ------   (*)/'(*)