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

[MM3-users] Re: Schedule for a resolution of #406, #410 and #437

by Mark Sapiro

On 12/14/2017 02:14 PM, Abhilash Raj wrote: > On Wed, Dec 13, 2017, at 12:11 AM, Henrik Rasmussen wrote: >> I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, >> #410<https://gitlab.com/mailman/mailman/issues/410> and >> #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It >> seems that it would not be far, as >> !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to >> be merged. > > Merged right now! :) And I have updated lists.mailman3.org and mail.python.org. Note however that <https://gitlab.com/mailman/mailman/merge_requests/322> does not fix <https://gitlab.com/mailman/mailman/issues/437> as noted at <https://gitlab.com/mailman/mailman/issues/437#note_46539617>. It also doesn't fix <https://gitlab.com/mailman/mailman/issues/441>. That appears due to a new bug related to <https://bugs.python.org/issue27321>, but which is a different message defect that causes UnicodeEncodeError to be thrown instead of KeyError. I have reported this at <https://bugs.python.org/issue32330>. I have created <https://gitlab.com/mailman/mailman/merge_requests/350> and <https://gitlab.com/mailman/mailman/merge_requests/351> to fix these issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] Re: So near, and yet so far (Configuring Mailman)

by Mark Sapiro

On 1/29/21 3:52 PM, Jack Lenox via Mailman-users wrote: > > Good news everyone! I've got it working. It turns out my issue was with > the mynetwork IP settings in my Postfix config. Things do now appear to > be working. Good. Thanks for the update. > My only remaining issue is that the posts aren't appearing > in the archive. Hmm. If you want our help with that, tell us if you have any non-default [archiver.*] settings in mailman.cfg and what the list's Settings -> Archiving settings are. If you are expecting HyperKitty archiving, are messages remaining queued in Mailman's var/archives/hyperkitty/spool/ directory and if so, what kind of errors do you see in Django's log? Does the value for MAILMAN_ARCHIVER_KEY in your Django settings match the api_key in the [general] section of the mailman-hyperkitty.cfg (or whatever you call it), quoted in MAILMAN_ARCHIVER_KEY but not in api_key, and is the base_url setting in the [general] section of the mailman-hyperkitty.cfg a URL that can actually access hyperkitty? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/21/23 14:50, ceo(a)sartrack.nz wrote: > I copied the wrong debug data in my original post, it should be this: > > --------> mailman3_router router <-------- > 2023-05-22 05:13:59 115223 local_part=templist domain=sartrack.nz > 2023-05-22 05:13:59 115223 checking domains > 2023-05-22 05:13:59 115223 sartrack.nz in "sartrack.nz"? yes (matched "sartrack.nz") > 2023-05-22 05:13:59 115223 data from lookup saved for cache for +mm_domains: key 'sartrack.nz' value 'sartrack.nz' > 2023-05-22 05:13:59 115223 sartrack.nz in "+mm_domains"? yes (matched "+mm_domains") > 2023-05-22 05:13:59 115223 checking require_files > 2023-05-22 05:13:59 115223 file check: /var/lib/mailman3/lists/${local_part}@${domain} > 2023-05-22 05:13:59 115223 expanded file: /var/lib/mailman3/lists/templist(a)sartrack.nz > 2023-05-22 05:13:59 115223 stat() yielded -1 I'm not an Exim expert although I have used it. The above says Exim was unable to stat /var/lib/mailman3/lists/templist(a)sartrack.nz - does that file exist. Does exim have search permission on all the directories in the path and read permission on the file? > 2023-05-22 05:13:59 115223 errno = 2 > 2023-05-22 05:13:59 115223 mailman3_router router skipped: file check -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[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

1 year, 5 months

[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

10 months, 4 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, 9 months

[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

8 years, 3 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, 10 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, 10 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

4 years, 7 months

Search results for query "sapiro"