Invalid confirm text
Hi there, I am new to mailman 3, python and django. I try to configure a mailman 3 list. To establish german text, I used the web-admin interface of mm3 in the "templates"-section. I inserted a text for "The message sent to subscribers when a subscription confirmation is required"
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. 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.
Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. Thank you Wolfgang
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
First I now removed the german templates again but alas the newsletter confirmation does not work any more. I only get the message, that the confirmation text is wrong. There was a time, when I received mails from mailman which listed all keywords, found by scanning the mails. I dont get these mails any more. Is it possible to hinder mailman from scanning the emails for confirmation keywords? I am afraid that I screwed this up somewhere in the admin surface.
Thank you
Wolfgang
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.
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 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. Do you have any idea, whats going wrong here? I dont know what to do any more. Thank you :-) Wolfgang
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
Thank you Mark for your help all logs did not help, there is no error thrown. I am afraid, that the problem is caused by an error I made about 6 weeks ago. By accident got into the django admin surface, where I deleted the example.com-Projekt. To fix this, I inserted into the mailman3web.db another row with the id=1, name=example.exe,domain=example.exe. This seemed to helped in the first place.
I now asked our admin that a backup of our mailman server is restored, so that I can start with a clean system again. Luckily I am still testing, not running a live system. Best wishes Wolfgang
participants (2)
-
Mark Sapiro -
w.schoener＠alp.dillingen.de