[Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders
[I'm moving this discussion to mailman-developers. -BAW] > "SB" == Stonewall Ballard <[EMAIL PROTECTED]> writes: SB> I've recently discovered that vacation autoresponders will SB> subscribe recipients to Mailman lists when they get "invited". Dang. This is because the From address contains the confirmation cookie encoded in the address. This might kill this idea for ease-of-use confirmations. SB> This is not good. It makes the feature dangerous if you've SB> promised to not subscribe anyone without their assent. Can you submit a bug report on this? We'll have to decide what to do long term. SB> Is there any way to avoid this problem, other than not using SB> the feature? This is yet another reason to move to URLs with SB> unique keys instead of using passwords. Such a URL could be SB> embedded in the invitation message. Take away the From header cookie and that's essentially what you've got in the invitation message. I'm up for any other ideas. -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders
On 1/3/03 5:49 AM, "Fil" <[EMAIL PROTECTED]> wrote: >> SB> I've recently discovered that vacation autoresponders will >> SB> subscribe recipients to Mailman lists when they get "invited". >> >> Dang. This is because the From address contains the confirmation >> cookie encoded in the address. This might kill this idea for >> ease-of-use confirmations. > > I would imagine that, if the autoresponder is set to answer emails coming > with a 'Precedence: list' header, the bug is with them, not with Mailman. > You don't want to kill a good functionality just because most autoresponders > are very poorly written - avoiding loops is enough ;) Blaming the client doesn't work. These people are being subscribed to a list without their knowledge or assent. That's a fatal error to the list manager. - Stoney ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders
At 11:49 +0100 1/3/2003, Fil wrote: >> SB> I've recently discovered that vacation autoresponders will >> SB> subscribe recipients to Mailman lists when they get "invited". >> >> Dang. This is because the From address contains the confirmation >> cookie encoded in the address. This might kill this idea for >> ease-of-use confirmations. > >I would imagine that, if the autoresponder is set to answer emails coming >with a 'Precedence: list' header, the bug is with them, not with Mailman. >You don't want to kill a good functionality just because most autoresponders >are very poorly written - avoiding loops is enough ;) Well, there are different needs for different Mailman sites. If you have to convince your provider that every address in your list truly wanted to be there, it's "unhandy" for there to be such a simple example of involuntary subscription, which the provider can demonstrate at will. Same for sites which choose to block phoney "opt in" schemes, and which contain members of your list. --John -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders
> "JWB" == John W Baxter <[EMAIL PROTECTED]> writes: SB> I've recently discovered that vacation autoresponders will SB> subscribe recipients to Mailman lists when they get SB> "invited". JWB> Well, there are different needs for different Mailman sites. JWB> If you have to convince your provider that every address in JWB> your list truly wanted to be there, it's "unhandy" for there JWB> to be such a simple example of involuntary subscription, JWB> which the provider can demonstrate at will. Exactly what constitutes "proof" from a legal context would be an interesting discussion to have. At the spam conference, Jon Praed gave a great talk about the spammers he's successfully sued, and the fact that they might be going after bulk email software venders. Now, clearly Mailman has legitimate uses, but I still think it would be interesting to know what Mailman can do better to create logs that would meet some legal standard of opt-in. -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
