Re: Any RFCs describing mailing list subscription practice?
"Donald E. Eastlake 3rd" <dee3@torque.pothole.com> Mon, 10 July 2000 03:10 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id XAA15305 for ietf-outbound.10@ietf.org; Sun, 9 Jul 2000 23:10:01 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15253 for <ietf@ietf.org>; Sun, 9 Jul 2000 23:02:03 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id XAA22624; Sun, 9 Jul 2000 23:04:19 -0400 (EDT)
Message-Id: <200007100304.XAA22624@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: Ross Finlayson <finlayson@live.com>
cc: ietf@ietf.org
Subject: Re: Any RFCs describing mailing list subscription practice?
In-reply-to: Your message of "Sun, 09 Jul 2000 17:18:32 PDT." <4.3.1.1.20000709170651.00b72650@shell7.ba.best.com>
Date: Sun, 09 Jul 2000 23:04:19 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org
As far as I know, there is no such IETF document. The only even vaguely related RFCs I know of are 2369 and 1211. Standardizing list processor commands has proven to be very controversial. But a BCP supporting use of a mail loop to confirm subscription would be a good thing and should be doable... Thanks, Donald From: Ross Finlayson <finlayson@live.com> Message-Id: <4.3.1.1.20000709170651.00b72650@shell7.ba.best.com> X-Sender: rsf@shell7.ba.best.com Date: Sun, 09 Jul 2000 17:18:32 -0700 To: ietf@ietf.org >Do we have any RFCs (or even I-Ds) that describe the preferred '3-way >handshake' method for validating a request to subscribe to a mailing list - >i.e., to first send back - to the requester's source email address - a >"please confirm your subscription" response message (preferably containing >a random token), and then add the address to the mailing list *only if* the >user responds to this second message? > >I am constantly fighting with clueless (or lazy, or opportunistic) mailing >list operators who insist on adding bogus email addresses - containing my >domain name - to their mailing lists, without first confirming their >validity. It would be nice if there were an IETF document that I could >point them at. > > Ross.
- Any RFCs describing mailing list subscription pra… Ross Finlayson
- Re: Any RFCs describing mailing list subscription… Donald E. Eastlake 3rd