On 09/26/2011 09:03 PM, Barry Warsaw wrote:
Currently, two foreign key constraints are commented out
because those are violated in Mailman 3 (apparently this doesn't bother
SQLite).
Foreign key constraints are available in sqlite 3.6.19 and above. They
are turned off by default. They can be
> Dan MacNeil wrote:
>> [snip]
>> current unsubscribe process take 5 steps:
>>
>> 1) Click
>> 2) enter email
>> 3) click submit
>> 4) read email
>> 5) reply to email
[snip]
>
> I hear what you're saying, a
Stephen J. Turnbull wrote:
[snip]
>>> BTW, a look at the patch suggests it's
>>> incomplete; I couldn't find any
>>> templates for headers and footers, nor
>>> documentation for how to generate the
>>> 1-click unsubscribe button.
Somebody else writes
>> Please, stop looking for reasons why n
> Dan MacNeil writes:
> > For my selfish purposes, "no-dupes" off is a better default setting.
> > Without a copy of the message to their mailbox, many of my users will
> > keep sending the same message because it "didn't go".
Stephen J. Turnbul
Stephen J. Turnbull quoted out of context:
> I see your point, but why won't my suggestion of defaulting the per
> user no-dupes to "on" do fine from that point of view?
For my selfish purposes, "no-dupes" off is a better default setting.
Without a copy of the message to their mailbox, many of my
> Am Mittwoch, den 24.01.2007, 20:13 -0500 schrieb Dan MacNeil:
>> Joachim Breitner wrote:
>>> Alternatively, a message to a members-only mailing list could
>>> automatically trigger a subscribe challenge that, if acted upon, not
>>> only subscribes the sen
Joachim Breitner wrote:
> Alternatively, a message to a members-only mailing list could
> automatically trigger a subscribe challenge that, if acted upon, not
> only subscribes the sender, but also approves the held-back message.
I often miss stuff but near as I can tell this would be a bad thing.
