Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Migration of the e-mail templates

by Mark Sapiro

On 3/6/25 2:24 PM, Markus Grandpré wrote: > > Thank you for your prompt reply. Based on a customer request, it seems > that custom templates need to be copied manually. Could you kindly > indicate which files and locations should be considered when > transferring them from the source to the target system? In MM 2.1, you could have list specific templates in directories like lists/<listname>/<language>/, domain specific templates in directories like templates/<list.host_name>/<language> and sitewide templates in directories like templates/site/<language>. In MM 3 You can create list and domain specific templates in Postorius or you can create them in sub-directories of Mailman's var/templates/ directory. List specific templates in lists/<list-id>/<language>/, domain specific templates in directories like domains/<mail-host>/<language>/ and sitewide templates in directories like site/<language>/. However, you can't just copy MM 2.1 templates because the variable replacement syntax is different and the template file names are different. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documentation of the MM 3 templating system. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Reg Archive Inactive Status and not working in Mailman

by Mark Sapiro

On 9/23/25 04:40, nirmal--- via Mailman-users wrote: > I am having the issue with Mailman Archive not working. Kindly help me to solve the issue. > > > Errors Found in:- > File "/usr/lib/python3/dist-packages/requests/adapters.py", line 489, in send > resp = conn.urlopen( > ^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 789, in urlopen > retries = retries.increment( > ^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 594, in increment > raise MaxRetryError(_pool, url, error or ResponseError(cause)) > urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive?key=n%2FZZnR5bRgNdUEyNK4p731C1%2BgWJLw0%2F (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)'))) Your setting for base_url in mailman-hyperkitty.cfg is an https url, but the addressed server is not configured properly to handle https. If the setting is something like base_url: https://localhost:8000/hyperkitty/ change it to http or change the url to the one used to access hyperkitty from a web browser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 3 weeks

[MM3-users] Re: Setup Mailman3 on shared webhost

by Mark Sapiro

On 11/5/18 5:42 AM, Keyra wrote: > Iam trying to setup mailman3 on a shared webhost (with ssh access). I > could use > > pip3.6 install mailman --user > > and also > > mailman info > > But when I try to start mailman using > > mailman start > > I will first get the error message > > TypeError: expected str, bytes or os.PathLike object, not NoneType > > and when I try it a second (and third etc.) time, it throws > > Starting Mailman's master runner > /usr/bin/python3.6: can't open file '/usr/bin/master': [Errno 2] No > such file or directory > > I didn't get any error messages during installation, so I guess whatever > mailman is looking for in /user/bin/master is available in my > /home/user/ folder, but I have no idea where and how to tell mailman to > look there. For more infos, this is the output of `mailman info` The 'master' command should be in the same directory as the 'mailman' command that you run. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 05/18/2018 03:50 AM, Henrik Rasmussen wrote: > > What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. Setting the policy to Confirm or Confirm, then Moderate will do that as long as admins don't use the mass subscribe feature without a confirmed request from the user. > Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Manually. I.e.post a request to the list with a deadline for response and remove those that don't respond. Or, post to the list that everyone will need to resubscribe and then remove everyone. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Can't remove footer(s)

by Mark Sapiro

On 10/02/2018 01:03 AM, Henrik Rasmussen wrote: > > Copying /dev/null doesn't help. It seems to be the same old content of the footer files before I removed the files and restarted Mailman, as if Mailman keeps the cache. > > I've just (again) ran > # docker exec -it mailman-core mailman shell -l [LISTNAME_FQDN] >>>> getUtility(ITemplateManager).delete('list:member:digest:footer', m.list_id) >>>> getUtility(ITemplateManager).delete('list:member:regular:footer', m.list_id) > > after copying /dev/null to the files in /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/list_member_digest_footer.txt and list_member_regular_footer.txt ,but that doesn't change anything. The templates named list_member_digest_footer.txt and list_member_regular_footer.txt (with underscores) were created by import21 and set as the URIs for those templates. Had you just copied /dev/null (or otherwise made empty) those files and done nothing else, that would have done what you wanted, but since you deleted the template URIs for the list, the template names are now the default list:member:digest:footer.txt and list:member:regular:footer.txt names (with colons) and those are the empty files you need to create. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/27/21 4:04 AM, Henrik Rasmussen wrote: >> Thanks for the hint Steve. There is a Spanish message catalog as >> evidenced by the fact that the reason was translated to Spanish, but the >> issue is almost certainly that there is no >> mailman/templates/es/list:user:notice:post.txt template so we fall back >> to the one for the list's language. > > I should note that my tests on same list with same language setup did not mix languages, for some reason and I can't replicate the problem. I wonder if it could have been a timing issue or the order that I changed languages on list language and user preference. I really think it has to do with two conditions: 1) the user's preferred language is Spanish 2) there was no mailman/templates/es/list:user:notice:post.txt template There were Spanish templates in Mailman core 3.3.4, but they were misnamed, e.g. list_user_notice_post.txt instead of list:user:notice:post.txt. Did you somehow add a mailman/templates/es/list:user:notice:post.txt template after the initial test? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 6:20 PM, David Newman wrote: > > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… although that's with apache and not nginx so it may not be. > Adding a stanza for 'location /mailman/' to the nginx config above > clears the 404 error, but Postorius returns "Page not found" with no > entry in the web or MM3 logs, and a 200 OK in the Nginx logs. > > I think the URL is supposed to go to the list page in Postorius. How to > configure this so that list owners and moderators get a valid URL for > list management? I'm not sure what the solution is in this case, but a workaround would be to add url(r'^mailman/', include('postorius.urls')), to the urlpatterns list in urls.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: deleting a list of spammers from non-member list

by Mark Sapiro

On 10/2/25 11:41, Philip Bondi via Mailman-users wrote: > Hello to all: > > I've studied the following: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > ```bash > mailman shell -l mmlist.domain.ca << EOF | tr , '\012' > nonmember.txt > list(m.nonmembers.members) > EOF > ``` > > I was able to produce a clean list of 50 non-member email addresses that are spammers. > > How would I take this list of non-members and delete them? I was unable to use mailman delmembers Assuming you want to delete all the nonmembers, just do it all in mailman shell. Using the above ```bash mailman shell -l mmlist.domain.ca << EOF for member in m.nonmembers.members: member.unsubscribe() EOF ``` If your 50 addresses are not all the nonmembers and you only want to delete those 50, the bash script could be ```bash mailman shell -l mmlist.domain.ca << EOF for addr in open('nonmember.txt').readlines() member = m.nonmembers.get_member(addr.strip()) member.unsubscribe() EOF ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 2 weeks

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Mark Sapiro

On 8/2/20 12:42 PM, Odhiambo Washington wrote: >> >> It is currently linked from the first paragraph at >> <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. >> > > I followed the steps outlined in the subject document and got mailman3 > running. > However, what is missing in that document is the process of setting up a > webserver for accessing the MM3 UI. > I have spent two days trying to figure out that aspect and discovered a few > things (I could be wrong in what I think): Which document are you talking about? If you mean <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…>, that talks about the Debian/Upuntu package installation and that package is quite behind the current releases. I thought that after mush back and forth with you following <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you got Mailman 3 up and running, so why would you now be trying to install the Debian/Ubuntu package? If you have issues with the <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…> document, you should contact its author. See <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 11:10 AM, dancab(a)caltech.edu wrote: > > We do have mailman(a)caltech.edu configured with valid members/owners. > We're using Postfix for the MTA. Is it possible there's a misconfiguration there? > > We've been testing the system with a handful of lists for months. The bounce you saw From: Mailman mailman(a)example.com To: Mailman Bounces mailman-bounces(a)example.com Subject: SMTP Delivery Failure may have sent because you have VERP probes enabled (verp_probes: yes in the mta section of mailman.cfg) and a user on some list reached the bounce score threshold and a Mailman attempted to send a probe and the MTA refused the message, or it may have been sent because Mailman attempted to send a message to the user and the MTA refused it. In either case, the bounce message (fake DSN) should have contained a message body like Mail to user(a)example.com failed at outgoing SMTP with the actual user's address. These fake DSNs are sent in the case where the outgoing MTA refuses a message from Mailman so there is no actual failure DSN. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Search results for query "sapiro"