On 8/14/20 3:28 AM, w.schoener@alp.dillingen.de wrote:
Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: return the message unchange.
When I return the message, I get an answer: Invalid confirm text.
With current releases of Mailman, the confirm request you receive should be:
From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token>
with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678>
My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown.
Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line
confirm <hex-token>
as either the Subject or body of the message to <listname>-request@<list.domain>. That should work.
Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval.
Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working.
See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/list:user:action:subscribe.txt>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan