About mailing list configuration problem
Hello: I installed mailman3 through docker, and I created a mailing list for testing, which can subscribe, unsubscribe, receive emails, and send emails normally. Now there are two problems that have not been resolved. I would like to ask: 1. When a user subscribes, how to configure it like "lists.mailman3.org" to send a link to confirm the subscription instead of just replying to the confirmation email. 2. I used the mailling list I created to test the sending and receiving of emails, but I didn't see any historical messages in "Archives",Where is the configuration incorrect? And the url of my mailing list is "https://list.example.org/hyperkitty/list/" instead of "https://lists.mailman3.org/archives/list/", is this a problem?
Also ask about the configuration, where to find the relevant documentation.
thank you very much.
liutianhua68@163.com
liutianhua68@163.com writes:
- When a user subscribes, how to configure it like "lists.mailman3.org" to send a link to confirm the subscription instead of just replying to the confirmation email.
Not sure what you mean. mailman3.org lists are just configured with a standard setting, may even be default: in the settings tab, member policy page, set subscriber policy to "confirm". They can reply to the email address or use a link in the email.
- I used the mailling list I created to test the sending and receiving of emails, but I didn't see any historical messages in "Archives",Where is the configuration incorrect?
What do you mean by "historical messages"? Do you mean the test messages?
The information is insufficient for a confident diagnosis, but I would guess that you have not configured the mailman-hyperkitty add on, which is a few lines of Python code that Mailman core needs to send messages to the HyperKitty archiver.
And the url of my mailing list is "https://list.example.org/hyperkitty/list/" instead of "https://lists.mailman3.org/archives/list/", is this a problem?
No. The documentation and the defaults are not entirely consistent on this. Both work, some sites prefer one, some the other. I think that in fact you can make both work with a couple of lines of Python in the Django configuration.
Also ask about the configuration, where to find the relevant documentation.
There's not a lot of separate documentation. The explanations in each settings page are the main documentation. The idea is that list administrators should go through all the settings anyway, to make sure that the defaults are satisfactory for their lists, or change them.
In the summer we plan to work on a feature that makes it easier for a list administrator to copy from one list to another.
On 4/19/22 01:48, liutianhua68@163.com wrote:
1. When a user subscribes, how to configure it like "lists.mailman3.org" to send a link to confirm the subscription instead of just replying to the confirmation email.
You need to make a custom version of the list:user:action:subscribe template that contains a link like
Alternatively, you can confirm by going to the URL
https://lists.example.org/mailman3/lists/$list_id/confirm/?token=$token
You can do something similar for the list:user:action:invite and list:user:action:unsubscribe templates.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
liutianhua68@163.com
-
Mark Sapiro
-
Stephen J. Turnbull