Article View: comp.mail.headers
Article #200Re: Return-Receipt-To & forwarding...
From: Warner Losh
Date: Mon, 28 Dec 1992 23:27
Date: Mon, 28 Dec 1992 23:27
16 lines
1245 bytes
1245 bytes
The biggest question about Return-Receipt-To: is what to do when a nieve user sends mail to a mailing list with this header in it. It would generate TONES of automatic messages w/o much usefulness to the user that set Return-Receipt-To: on by default. It would be critical that mailing lists and such filter out Return-Receipt-To:. Also, it should be expressly forbidden to have a Return-Receipt-To: on a return receipt, for obvious reasons. Return-Receipt-To is a dangerous header as it stands now. If its use is to be standardized, its meaning much change :-) Warner -- Warner Losh imp@boulder.parcplace.COM ParcPlace Boulder I've almost finished my brute force solution to subtlety.
Technical Details
Message-ID:
<Bzzt68.G8z@boulder.parcplace.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!gatech!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!csn!boulder.parcplace.com!impReferences:
<1992Dec20.022054@avsht.sph.spb.su> <19921225.001@erik.naggum.no> <sdorner-271292095054@0.0.0.0>Show Full Headers
Complete Article Headers
Newsgroups: comp.mail.headers,comp.mail.misc Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!csn!boulder.parcplace.com!imp From: imp@boulder.parcplace.com (Warner Losh) Subject: Re: Return-Receipt-To & forwarding... Message-ID: <Bzzt68.G8z@boulder.parcplace.com> Sender: news@boulder.parcplace.com Organization: ParcPlace Boulder References: <1992Dec20.022054@avsht.sph.spb.su> <19921225.001@erik.naggum.no> <sdorner-271292095054@0.0.0.0> Date: Mon, 28 Dec 1992 23:27:43 GMT Lines: 16