[Mailman-Developers] Functional design issue - optional passwords
Sat, 17 Oct 1998 22:58:34 -0700
Honestly, yes, I'd like to have confirmation in place for *everything*
and not just subscribes, for people who don't want to deal w/
passwords. It should be such that the list admin can completely
disable one or the other if he so chooses, but both should be an
option. Does everyone agree here?
On Sun, Oct 18, 1998 at 03:44:49PM +1000, John Evershed wrote:
> Why not simplify the unsubscription process so that it can not only
> be easily be done by forgetful users but also by dumb agents?
> Most mailing lists allow a simple UNSUBSCRIBE in either subject or
> body to trigger an unsubscription confirmation message being sent
> to the apparent user, with a random token which must be returned in
> the reply. This could be the default mailman behaviour when a password
> is omitted.
> A lot of people in the mailing list community obviously think that the
> mail unsubscription process should be both simple and standard -
> eg the RFC authors who proposed the new mailing list headers such as
> "List-Unsubscribe: <mailto:list-request@domain?subject=unsubscribe>".
> Mailman-Developers maillist - Mailman-Developers@python.org