Article View: bit.admin
Article #1611Re: Problems with gateways between the mailing lists & Usenet.
From: John Stewart
Date: Thu, 16 Jul 1992 18:17
Date: Thu, 16 Jul 1992 18:17
39 lines
3305 bytes
3305 bytes
In <1992Jul16.165608.17970@utdallas.edu> shane@utdallas.edu (Shane Davis) writes: >In article <1992Jul16.023706.32373@mp.cs.niu.edu>, rickert@mp.cs.niu.edu (Neil Rickert) writes: >|> Complain to the mailing list manager. Complain to people who write >|> broken software which does this. The "Reply-To:" is supposed to be >|> an optional header available to the author of the article. The practice >|> of adding a "Reply-To:" pointing back to the list is abusive. It abuses >|> the intentions of the "Reply-To:" header. It abuses the readers who >|> wish to reply privately to the author. It abuses the readers of the >|> mailing list who see many messages of no interest to anyone but the >|> original author. >|> >Most lists are set such that any Reply-To inserted by the author will be >respected; the list is only inserted if there is no Reply-To. So, this is >under the poster's control (though how a news gateway behaves regarding >Reply-To is not a function of poster or LISTSERV). Perhaps the gateway should >insert the From: address into Reply-To. >If these Reply-To were so abusive, why have people been using these lists for >so many years? Obviously, people do not feel abused. I don't see your name on >RFC 822, so what makes you so certain of the intentions of Reply-To? I certainly feel abused by this practise. I had to write a script to bounce undeliverable mail (account disk space full, no mail folder, etc.) on our mailframe. Messages from a LISTSERV can't be handled in the same way as regular mail because the Reply-To: header line points back to the list -- bouncing the message to that address causes a mail loop. The only solution seemed to be to check the comments in header lines for tokens like "list" or "distribution" that are generally found in messages from a LISTSERV. I'd be a lot happier though if LISTSERV would add an Errors-To: header to provide a proper place to report delivery problems to. I'd guess that LISTSERV also has some klugey logic to try to distinguish a bounce reply from a list submission. -- John Stewart -- Computing and Communications Services, Carleton University Internet: jstewart@ccs.carleton.ca or Mr.Canoehead@algonquin.carleton.ca "Why can't we just forget about our constitutional problems and go canoeing?"
Technical Details
Message-ID:
<jstewart.711310628@cunews>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!sun-barr!cs.utexas.edu!torn!cunews!jstewartReferences:
<1992Jul15.015543.22595@mits.mdata.fi> <1992Jul15.151734.22118@csd.brispoly.ac.uk> <1992Jul16.005647.10015@mits.mdata.fi> <1992Jul16.023706.32373@mp.cs.niu.edu> <1992Jul16.165608.17970@utdallas.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10f432,84cfa015f81b8547 X-Google-Attributes: gid10f432,public X-Google-Thread: fd322,84cfa015f81b8547 X-Google-Attributes: gidfd322,public X-Google-Thread: 109803,84cfa015f81b8547 X-Google-Attributes: gid109803,public X-Google-ArrivalTime: 1992-07-15 21:35:32 PST Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!sun-barr!cs.utexas.edu!torn!cunews!jstewart From: jstewart@alfred.carleton.ca (John Stewart) Newsgroups: bit.admin,comp.mail.headers,news.software.readers Subject: Re: Problems with gateways between the mailing lists & Usenet. Message-ID: <jstewart.711310628@cunews> Date: 16 Jul 92 18:17:08 GMT References: <1992Jul15.015543.22595@mits.mdata.fi> <1992Jul15.151734.22118@csd.brispoly.ac.uk> <1992Jul16.005647.10015@mits.mdata.fi> <1992Jul16.023706.32373@mp.cs.niu.edu> <1992Jul16.165608.17970@utdallas.edu> Sender: news@cunews.carleton.ca (News Administrator) Organization: Carleton University Lines: 39