On 08/05/2018 09:10 AM, Bernie Cosell wrote:
>> I discovered, after much mucking around, that the problem
>> is that Mailman requires all of the form fields to be
>> submitted.
>
> Just a footnote to this: If you have a big list and you're trying to, say,
> change the 'nomail' setting via the
On 08/05/2018 04:09 AM, Bernie Cosell wrote:
> I discovered, after much mucking around, that the problem is that
> Mailman requires all of the form fields to be submitted. So unsubscribing
> with just
>
> @fields = ( unsubscribees => "$email",
> setmemberopts_btn =>
On 08/05/2018 01:54 AM, Jason Wandel wrote:
>
> Yes, it's on cPanel... But I would've thought it would still be a standard
> mm install in the back end???
cPanel modifies Mailman, mostly to support their appending of '_domain'
to list names to avoid name collisions between different domains. The
> I discovered, after much mucking around, that the problem
> is that Mailman requires all of the form fields to be
> submitted.
Just a footnote to this: If you have a big list and you're trying to, say,
change the 'nomail' setting via the membership page, you're going to have
a *lot* of POST
I discovered, after much mucking around, that the problem is that
Mailman requires all of the form fields to be submitted. So unsubscribing
with just
@fields = ( unsubscribees => "$email",
setmemberopts_btn => "Submit Your Changes",
) ;
Doesn't w
Hi Mark,
Thanks for the response.
Yes, it's on cPanel... But I would've thought it would still be a standard
mm install in the back end???
Anyway, url encoding the quotes made no difference I'm afraid... But it did
point me in the right direction. Replacing the < and > chars around the
address w
