Subscription requires confirmation when list is set as Open
Hi All,
I have a list set with the following ...
List Settings > Member Policy # Subscription Policy = "Open"
When I subscribe with an email address that has been used (subscribed/unsubscribed) on any other list (on that server), the address is subscribed automatically.
However, if I subscribe with an address that has never been used before, I receive an email that requires me to confirm the subscription.
The subscription is also held in the administrator's "Subscription requests: Pending confirmation".
This happens when subscribing by both email and the web UI.
Ideally, as the Policy is set as "Open", the subscription of any new email address should be added automatically.
Have I missed a configuration setting somewhere?
Any advice really appreciated.
Regards, Mark
$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Venv installation on Debian
On 12/17/24 13:35, Mark wrote:
However, if I subscribe with an address that has never been used before, I receive an email that requires me to confirm the subscription.
The subscription is also held in the administrator's "Subscription requests: Pending confirmation".
This happens when subscribing by both email and the web UI.
Ideally, as the Policy is set as "Open", the subscription of any new email address should be added automatically.
Have I missed a configuration setting somewhere?
It is not the subscription that requires confirmation. It is the user's email address. Even though the list's subscribe policy is open, a previously unknown email address has to be confirmed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/17/24 13:35, Mark wrote:
... if I subscribe with an address that has never been used before, I receive an email that requires me to confirm the subscription.
The subscription is also held in the administrator's "Subscription requests: Pending confirmation".
This happens when subscribing by both email and the web UI.
Ideally, as the Policy is set as "Open", the subscription of any new email address should be added automatically.
On 2024-12-18 00:00, Mark Sapiro wrote:
It is not the subscription that requires confirmation. It is the user's email address. Even though the list's subscribe policy is open, a previously unknown email address has to be confirmed.
Thank you Mark. Your explanation is very much appreciated.
Best, Mark
Mark Sapiro writes:
It is not the subscription that requires confirmation. It is the user's email address. Even though the list's subscribe policy is open, a previously unknown email address has to be confirmed.
I assume that's the verification that one can turn off in Postorious `Mass Suscription' with the checkbox "Pre Verified".
I maintain a mailing list for a private holiday where people don't subscribe themselves; I subscribe them. I have vetted their email address beforehand. (The subscribers are mostly not able to handle a verification email, nor any email-based workflow at all.) Is there a configuration option for a mailing list that sets "Pre Verified" to true as a default?
I checked the options of "mailman conf" and "mailman-web help" (the latter seems to be Postorious' manage.py on my Debian system), but to no avail.
Cheers, Joachim
--
Joachim Schrod <joachim@schrod.org>
On 12/18/24 18:22, Joachim Schrod wrote:
Mark Sapiro writes:
It is not the subscription that requires confirmation. It is the user's email address. Even though the list's subscribe policy is open, a previously unknown email address has to be confirmed.
I assume that's the verification that one can turn off in Postorious `Mass Suscription' with the checkbox "Pre Verified".
That is correct.
I maintain a mailing list for a private holiday where people don't subscribe themselves; I subscribe them. I have vetted their email address beforehand. (The subscribers are mostly not able to handle a verification email, nor any email-based workflow at all.) Is there a configuration option for a mailing list that sets "Pre Verified" to true as a default?
This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was later extended by https://gitlab.com/mailman/postorius/-/merge_requests/945 however these are not available until Postorius 1.3.14 which is not yet released.
These add a setting, POSTORIUS_DEFAULTS, which can be used to set these defaults. E.g., setting
POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True}
will set the default for Pre Verified to True. So far, the only defaults that can be set in this manner are mass_subscription_pre_confirm, mass_subscription_pre_approve, mass_subscription_pre_verify and mass_subscription_invite and those not until Postorius 1.3.14, but more may be added.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
I maintain a mailing list for a private holiday where people don't subscribe themselves; I subscribe them. I have vetted their email address beforehand. (The subscribers are mostly not able to handle a verification email, nor any email-based workflow at all.) Is there a configuration option for a mailing list that sets "Pre Verified" to true as a default?
This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was later extended by https://gitlab.com/mailman/postorius/-/merge_requests/945 however these are not available until Postorius 1.3.14 which is not yet released.
These add a setting, POSTORIUS_DEFAULTS, which can be used to set these defaults. E.g., setting
POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True}
will set the default for Pre Verified to True. So far, the only defaults that can be set in this manner are mass_subscription_pre_confirm, mass_subscription_pre_approve, mass_subscription_pre_verify and mass_subscription_invite and those not until Postorius 1.3.14, but more may be added.
Thanks a lot for this info -- I'm looking forward for an upcoming Postorius 1.3.14 release! ;-) :-)
Happy holidays and a good new year to everyone,
JoachimOn 2024-12-19 02:22, Joachim Schrod wrote:
Is there a configuration option for a mailing list that sets "Pre Verified" to true as a default?
Hi,
Editing the list_forms.py file will set the "Pre Verified" checkbox default to "checked" ...
/opt/mailman/venv/lib/python3.11/site-packages/postorius/forms/list_forms.py
... changing initial=False to initial=True - onLine 1267
pre_verified = forms.BooleanField(
label=_('Pre Verified'),
initial=True,...
And then restart of mailman3 and mailmanweb after editing.
See Mark Sapiro's post at ...
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/3...
Regards, Mark
Mark writes:
On 2024-12-19 02:22, Joachim Schrod wrote:
Is there a configuration option for a mailing list that sets "Pre Verified" to true as a default?
Hi,
Editing the list_forms.py file will set the "Pre Verified" checkbox default to "checked" ...
/opt/mailman/venv/lib/python3.11/site-packages/postorius/forms/list_forms.py
... changing initial=False to initial=True - onLine 1267
pre_verified = forms.BooleanField( label=_('Pre Verified'), initial=True,...
And then restart of mailman3 and mailmanweb after editing.
Works like a charm, thanks a lot!
Happy holidays, Joachim
participants (3)
-
Joachim Schrod -
Mark -
Mark Sapiro