On 8/17/20 4:53 AM, w.schoener@alp.dillingen.de wrote:
One thing I forgot to mention: a week ago, the confirmation-mails still worked.
And now: All attempts to confirm the subscribe message failed. I used the list-request@list.domain and sent text-only message with the "confirm token" in the subject and/or in the body.
This should work. What's in your MTA's logs?
So today I tried and used the Mailman shell to change the pending state to "confirmed", as you described here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/6... After I submitted the command util.confirm('hex_token') and restarted mailman with mailman stop mailman start
It isn't necessary to stop/star/ or restart mailman. How did you exit mailman shell. You must exit with ctrl-D or issue commit() or your transactions won't be committed. In particular, if you exit with exit() without first issuing commit(), nothing will be done.
the pending user wasnt confirmed but cleared, as if he never sent a subscribe-message. The only way to subscribe seems to be by logging in and using there the subscribe-form.
What is the list's subscription_policy? It seems you successfully confirmed that token, but that may not be the last step if the list's subscription_policy is confirm_then_moderate.
Do you have any idea, whats going wrong here? I dont know what to do any more.
Clearly something is broken, but I don't know what unless it is some permissions issue on the template directories/files you created.
Have you looked at Mailman's mailman.log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan