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

[MM3-users] Re: Disable Sign-up per domain

by Mark

On 2025-08-01 19:40, Mark Sapiro wrote: > Please confirm that the issue only occurs with the modified > /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py > and does not occur with the original .../user_adapter.py. > Hi Mark, In working through this I reverted the test server (which had the working "Disable") back to original, then re-applied the changes, and now I'm getting the same errors as on the Production server. I think it might be me screwing up somewhere. It's doing my head in today so I'll sleep on it and have another crack at it tomorrow. STEPS TAKEN =========== 1. Reset the "Test" server back to original. (a) I put the original "user_adapter.py" back in place. It contains: ... def is_open_for_signup(self, req): return False ... (b) Ensured that "settings.py" had the following completely removed: ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ... (c) systemctl restart mailman3 systemctl restart mailmanweb (d) Reloaded browser with "lists" page for each domain and clicked "SignUp" on each. Result: As expected, both domains correctly displayed their SignUp pages. ----------- 2. Made the following changes to the "Test" server. (a) Edited /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py It now contains: ... # def is_open_for_signup(self, req): # return False def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.MYDOMAIN.COM': return False else: return True ... (b) Appended to - /etc/mailman3/settings.py - the following: ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' (c) systemctl restart mailman3 systemctl restart mailmanweb Result: 502 Bad Gateway page and log shows ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. ===========

7 months, 2 weeks

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 15/2/21 16:57, Mark Sapiro wrote: > Finally, although I said previously that the translated templates should > be submitted as a merge request, that can still be done, but is not > necessary. They can be translated in weblate. See > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > and<https://gitlab.com/mailman/mailman/-/issues/825>. I had the templates translated now in UTF-8 coding map. I copied all of them en a new directory (es) under mailman package templates (as I can see are other languages): /usr/local/lib/python3.7/site-packages/mailman # ls templates __init__.py de es it __pycache__ en fr sk /usr/local/lib/python3.7/site-packages/mailman # ls templates/es domain:admin:notice:new-list.txt list:member:regular:header.txt help.txt list:user:action:invite.txt list:admin:action:post.txt list:user:action:subscribe.txt list:admin:action:subscribe.txt list:user:action:unsubscribe.txt list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt list:admin:notice:disable.txt list:user:notice:hold.txt list:admin:notice:removal.txt list:user:notice:no-more-today.txt list:admin:notice:subscribe.txt list:user:notice:post.txt list:admin:notice:unrecognized.txt list:user:notice:probe.txt list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt list:member:digest:header.txt list:user:notice:rejected.txt list:member:digest:masthead.txt list:user:notice:warning.txt list:member:generic:footer.txt list:user:notice:welcome.txt But mailman isn't aware of them (I restarted the server). May I have to execute some process as "compilemessages" to mailman be capable to use them? Now mailman is using the "en" templates for sure. After testing them I'll do both of the suggestionsyou made: a merge request AND the revision and translation via Weblate.

5 years, 1 month

[MM3-users] Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Allan Hansen

Thank you both. Since the first message she sent was UTF-8 and the second iso-8859-8-I, I have asked her what she did diffently between the two messages. No response yet... But now being aware that this can happen when non-ASCII messages are sent, and how to find the issue when it does, is good. Yours, Allan On 6/27/23, 07:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 6/27/23 12:30 AM, Stephen J. Turnbull wrote: > > That said, if the users are unable or unwilling to use UTF-8, it would > be possible to create a codec for "iso-8859-8-i", I don't know how to > do that, and I doubt Mark does. You could ask on > python-list(a)python.org <mailto:python-list@python.org>, or file an RFE on Python's GitHub tracker. See https://github.com/python/cpython/issues/90079 <https://github.com/python/cpython/issues/90079> filed by me in Nov 2021. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/4WPWU3SKGWM2BTG5AK3LWNG7FDIBVSTP/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 8 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Fri, 21 Oct 2022 12:23:44 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/21/22 09:56, Onyeibo Oku wrote: > > On Fri, 21 Oct 2022 09:52:03 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Can you successfully start mailman (or run any mailman commands) > >> with, e.g. ``` > >> /opt/mailman/venv/bin/mailman start > >> > >> or > >> > >> /opt/mailman/venv/bin/mailman info > >> ``` > >> without activating the venv? > >> > > > > Yes. All those are working without activating venv. > > > On my test installation with /etc/systemd/system/mailman3.service > installed per > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… > > systemctl start|stop|status mailman3 > > all work. Assuming > ``` > python3 -c 'from pkg_resources import load_entry_point' > ``` > (not in your venv) returns no error, try replacing > /opt/mailman/venv/bin/mailman with > ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: > 'mailman==3.3.5','console_scripts','mailman' __requires__ = > 'mailman==3.3.5' import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', > 'mailman')() ) > ``` > Or in yours posted at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > replace everything from the first `try:` through > `globals().setdefault(...)` with > ``` > from pkg_resources import load_entry_point > ``` > and see if that helps. I did the second alternative and replaced from "try" to the "globals ...". It works when I started it directly. However, I get a detailed traceback when systemd tries to start it. Here is what I got: Oct 22 04:13:55 mail.server.tld mailman[9253]: Traceback (most recent call last): Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/opt/mailman/venv/bin/mailman", line 9, in <module> Oct 22 04:13:55 mail.server.tld mailman[9253]: from pkg_resources import load_entry_point Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3267, in <module> Oct 22 04:13:55 mail.server.tld mailman[9253]: def _initialize_master_working_set(): Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3241, in _call_aside Oct 22 04:13:55 mail.server.tld mailman[9253]: f(*args, **kwargs) Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3279, in _initialize_master_working_set Oct 22 04:13:55 mail.server.tld mailman[9253]: working_set = WorkingSet._build_master() Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 564, in _build_master Oct 22 04:13:55 mail.server.tld mailman[9253]: ws = cls() Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 557, in __init__ Oct 22 04:13:55 mail.server.tld mailman[9253]: self.add_entry(entry) Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 613, in add_entry Oct 22 04:13:55 mail.server.tld mailman[9253]: for dist in find_distributions(entry, True): Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2077, in find_on_path Oct 22 04:13:55 mail.server.tld mailman[9253]: for dist in factory(fullpath): Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2142, in distributions_from_metadata Oct 22 04:13:55 mail.server.tld mailman[9253]: yield Distribution.from_location( Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2606, in from_location Oct 22 04:13:55 mail.server.tld mailman[9253]: )._reload_version() Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3004, in _reload_version Oct 22 04:13:55 mail.server.tld mailman[9253]: md_version = self._get_version() Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2785, in _get_version Oct 22 04:13:55 mail.server.tld mailman[9253]: version = _version_from_file(lines) Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2569, in _version_from_file Oct 22 04:13:55 mail.server.tld mailman[9253]: line = next(iter(version_lines), '') Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2780, in _get_metadata Oct 22 04:13:55 mail.server.tld mailman[9253]: for line in self.get_metadata_lines(name): Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1422, in get_metadata_lines Oct 22 04:13:55 mail.server.tld mailman[9253]: return yield_lines(self.get_metadata(name)) Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1412, in get_metadata Oct 22 04:13:55 mail.server.tld mailman[9253]: value = self._get(path) Oct 22 04:13:55 mail.server.tld mailman[9253]: File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1616, in _get Oct 22 04:13:55 mail.server.tld mailman[9253]: with open(path, 'rb') as stream: Oct 22 04:13:55 mail.server.tld mailman[9253]: PermissionError: [Errno 13] Permission denied: '/opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO' Oct 22 04:13:55 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE It seems one of the dependent packages (zope) requires certain privileges that systemd does not have. This may be what was failing initially. How might one solve this? Regards Onyeibo

3 years, 4 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 22:53, Mark Sapiro escribió: > On 4/1/23 12:44, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I get the same error as before: > > > Did you post this traceback before? If so, I missed it. Yes. I did. when I configured debug in mailman.cfg as Odhiambo sugested > > > ... > The issue is in aiosmtpd which is trying to determine if it can use > IPv6 "::1" for localhost. It does this before it checks if we've > provided a hostname which we have. The issue is in > aiosmtp/controller.py in the get_localhost() function, but it's even > deeper than that in socket which is raising the Protocol not supported > error. > > There is something strange on your server in that IPv6 seems to be > only partially supported. I don't know for sure what the underlying > issue is, but look at > https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/controller.py#L49 > > Find aiosmtpd /controller.py in your venv/lib/python3.?/site-pacakages > directory and change that > > return has_ipv6 > > line to > > return False > that did the trick 14477 - SJ 0:01.12 /usr/local/bin/python3.9 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg --runner=lmtp:0:1 And now the lists are working as should. Thank you very very much. You are a saver. > to work around the issue. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 11 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2022-12-14 17:26:59 -0800 (-0800), Mark Sapiro wrote: > On 12/14/22 13:40, Jeremy Stanley wrote: > > > > Once these entries are automatically added by visiting that page, > > they're all associated with the one "web host" ("site" in Django) we > > have for the server, and now the list filtering functionality in > > Postorius breaks and any of the vhosts all display the full set of > > mailing lists on the server rather than only those associated with a > > particular vhost (note that this seems to only be confusing > > Postorius, Hyperkitty has them correctly filtered still). > > See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > and also below. [...] While this does appear to solve the problem on my test deployments, a challenge that I'm left with is how to automate it. Our community takes an "infrastructure as code" approach to all the services we run for our projects, and we make sure that we can automatically bootstrap every system from scratch into a working state. Unfortunately, I'm not having any luck finding an API or CLI which I can use to create sites and domains rather than manually doing it in the Django admin WebUI. Does such a thing exist, or an I going to need to resort to directly performing database inserts (which I'd rather avoid since it could break if the schema changes). It appears there's a foreign key relationship involved, which could make DB manipulation like this even more fragile. -- Jeremy Stanley

3 years, 1 month

[MM3-users] Re: config incoming email in my domain cpanel

by Simon HANNA

On August 3, 2017 8:50:41 PM GMT+02:00, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: >El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) >escribió: > >> On 08/03/2017 10:42 AM, Rafael Mora wrote: >> > >> > I've found the MX records on my cpanel but how do I redirect the >emails >> > going to my list to my private server? >> >> >> You have to configure the MTA that is the MX for the domain to relay >the >> mail to the Mailman server. >> > >Our domain is: LABBRANDS.COM We have that domain config in a Hosgator >hosting. The emails sent to labbrands.com go to our hosting, so how do >I >tell cpanel in hostgator hosting that the mails sent to the list ( >mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private >server (we have static public IP address) ?? > You can't redirect one email address using DNS! If you don't want to host an entire domain on your own server, I suggest using a subdomain (lists.example.con) instead. You could probably also redirect one email in cpanel to the subdomain, but I'm not sure how mailman and clients like emails with different domains... In theory postfix can send emails using any domain. You just have to make sure spf, dkim and PTR records are properly set. Otherwise you'll most likely get issues with rejected mail... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 7 months

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

by Henrik Rasmussen

Mark Sapiro wrote: > I'm confused. Confirm sends a confirmation request to the subscribed > address which must be acted upon by the user before she is added to the > list. Moderate just means approval by an owner/moderator Oh sorry, you're right, I mixed up those two. > which, it seems > to me is more susceptible to a 3rd party subscribe succeeding - i.e., > subscription requires membership in some organization. A subscribes B > who is a member of the organization but doesn't want to be on the list. > The moderator verifies that B is an organization member and approves the > subscription. 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. > Granted that this can be abused, but not allowing admins to directly add > members will probably create more problems than it solves. I agree, I wouldn't remove it either, but I just have to be concerned about the possibility that someone may have been subscribed against their will. Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Henrik Rasmussen

7 years, 9 months

[MM3-users] Re: hyperkitty web site

by Gelpi Andrea

Il 28/04/20 19:10, Mark Sapiro ha scritto: > On 4/28/20 9:40 AM, Gelpi Andrea wrote: >> >> If in django administration I rename that site it works. >> >> But having more than one domain this is not a solution. >> >> what i need is to separate different domains >> >> https:/website1/mailman3/hyperkitty shows some lists >> https:/website2/mailman3/hyperkitty shows other lists > > > There are issues with FILTER_VHOST. See > <https://gitlab.com/mailman/postorius/-/issues/394> for the Postorius > issue. This will be fixed for Postorius in the next release. > > For HyperKitty, the issue is > <https://gitlab.com/mailman/hyperkitty/-/issues/254>. This is not yet fixed. > > Currently, if FILTER_VHOST is True, HyperKitty only shows lists in the > index for which the list's domain matches the domain in the accessing > url with a leading 'www.' stripped. > > E.g. list(a)example.com will only show on the index if the accessing URL's > host is example.com or www.example.com, but not if it is say > lists.example.com. > Thank You I just discovered it. I put a workaround for now in index.py so also list.example.com works. # Domain filtering if settings.FILTER_VHOST: domain = request.get_host().split(":")[0] if domain.startswith("www."): domain = domain[4:] #gg# Added by Gelpi if domain.startswith("list."): domain = domain[5:] domain = "@%s" % domain mlists = mlists.filter(name__iendswith=domain) Regards -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 10 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Barry Warsaw

On Jun 18, 2016, at 12:10 PM, Mark Sapiro wrote: >because I want to run all the Mailman pieces from >the heads of their branches rather than what's in PyPI, but even without >that, installation is significantly more work than installing a distro's >package. My hope is that the upcoming 3.1 release will be much more solid and usable than 3.0 so that you won't have to run from the git heads. I think of it very much like Python 3.0 and 3.1 - the 3.0 release was really a stake in the ground and a major milestone so that people will start using it in anger and helping us understand the priorities for fixing and improving it. In that we've succeeded I believe (witness in addition to Mark's work on python.org, that the Fedora mailing lists have all been converted to use MM3). There are a number of interesting options for improving the turnkey installation of MM3. There are Debian folks who are waiting for 3.1 to complete the packaging work there, and there are docker/juju/etc. containerization work happening too. >I will say that once you have Mailman 3 installed and running, updating >(which I do frequently, but which doesn't need to be done unless you >want specific updates/fixes) is pretty easy. Yes, we're trying to be very serious about upgrades and backward compatibility, so that even if you bravely install 3.0 today, it should always be easy to upgrade to the next point release. Similarly, I try to keep core's git head always working so you could track that if you want. Cheers, -Barry

9 years, 8 months

Search results for query "sapiro"