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

[MM3-users] Re: Sudden increase in "***UNCHECKED***" in email subjects

by Dave Clements

Hi Peter and Mark, Thanks for the insight and fixes. We (we being Nate who is also on this list) think it was a lack of virtual memory on the server. This crashed ClamAV and it could not restart. Thus our mail really was unchecked. Restarting processes and cleaning up some things has fixed this. Cheers, Dave C On Sun, Jul 19, 2020 at 4:07 PM Peter Adebahr via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 7/18/20 7:46 PM, Mark Sapiro wrote: > > On 7/18/20 9:30 AM, Dave Clements wrote: > >> Hi all, > >> > >> I have just noticed a big jump in the number of emails going out with > >> "***UNCHECKED***" added to the subject line. > > > > > > This does not come from Mailman. Some milter or other process in your > > MTA or elsewhere in the delivery chain is adding this to the Subject: > > > > Hi Dave, > > I had experienced the same symptom a while ago. For me, it was amavis > doing this. This behaviour could be corrected by adding this line to > amavisd.conf: > > > # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it > $undecipherable_subject_tag = undef; > # > > Hope it helps :) > > Best regards, > Peter > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- https://bcc2020.github.io/ https://galaxyproject.org/

5 years, 1 month

[MM3-users] Re: 404 on fresh install (Debian11)

by Jeremy Stanley

On 2023-03-23 09:07:02 -0700 (-0700), Mark Sapiro wrote: [...] > bookworm (testing) and sid (unstable) do have current versions of > Mailman core and django-mailman3 and possibly mailman3-web > 0+20200530-2.1 has current Postorius and HyperKitty, but those are > generally not the Debian packages that most users would install. And those will also become out of date over time, because Debian is a stable server distribution so intentionally freezes the versions of software it supplies and backports only critical/security fixes to those increasingly outdated versions when warranted. Basically it's a question of whether users value stability with a bit of security support over newest versions of software and new features. The upstream Mailman packages on PyPI (and container images) cater to users who want the latest versions of the software, packages in stable server distros like Debian cater to users who want to safely go years between behavior changes in software. Both are valid choices, it just comes down to the user's specific situation. That said, when you have trouble with the packaged versions of software in Debian, the expectation is that you ask on Debian mailing lists and possibly report bugs in the Debian bug tracker, rather than burdening upstream software maintainers with details that might be specific to choices or mistakes in Debian's packages. The package maintainers in Debian generally forward bug reports upstream if they determine the issue you've encountered isn't related to how it's been packaged, isn't already fixed upstream (in which case they might backport the fix), et cetera. -- Jeremy Stanley

2 years, 5 months

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

Victoriano Giralt writes: > El vie, 23-10-2020 a las 08:19 -0700, Mark Sapiro escribió: > > > > This would be more difficult for Postorius/Hyperkitty because those > > users are Django users, but that isn't an issue for Affinity. > > > > All of a sudden, an idea has dawned on me ... Wouldn't it be possible for > Postorius/Hyperkitty, both Django applications, to use Mailman core user > model as their User model? It is just a setting for Django > (AUTH_USER_MODEL). I find the "just a setting" claim a bit implausible. I suspect a certain amount of replumbing of Postorius and HyperKitty will be necessary to get it to work. Most important, the "AUTH_" is pretty scary. Mailman core has *no* authentication built in. It is assumed to be firewalled off from the rest of the world with only access from Postorius and HyperKitty permitted. Can you expand on how hard it would be to do this? Remember that some Mailman instances are either big targets (eg, Apple) or require good security for content reasons (lists for doctors' patient support groups, domestic violence support groups). This is not a great authn/authz model in the modern Internet, but as far as I can see changing it is going to be quite a lot of work, and none of us are authentication specialists (although Abhilash did study security, I don't think he specialized in authentication tech) -- providing reasonably reliable and secure authentication services, especially "social auth" (OpenAuth, OpenID etc) is an important reason we went with Django in the first place. Steve

4 years, 9 months

[MM3-users] Re: hyperkitty threads by month question

by Bryan Fields

On 7/25/24 7:04 PM, Mark Sapiro wrote: > On 7/25/24 11:20, Bryan Fields wrote: >> When this happens, I get an email error below. > > > This is really wierd. See below. > >> line 88, in reverse >> return resolver._reverse_with_prefix(view, prefix, *args, **kwargs) >> File >> "/opt/mailman/venv/lib/python3.10/site-packages/django/urls/resolvers.py", line 828, in _reverse_with_prefix >> raise NoReverseMatch(msg) >> >> Exception Type: NoReverseMatch at >> /archives/list/nanog(a)nanog-mm3.keekles.org/ >> Exception Value: Reverse for 'hk_archives_with_month' with keyword >> arguments '{'year': 999, 'mlist_fqdn': 'nanog(a)nanog-mm3.keekles.org', >> 'month': 12}' not found. 2 pattern(s) tried: >> ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$', 'hyperkitty/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$'] >> Raised during: hyperkitty.views.mlist.overview > > > It appears to be trying to get the threads for December, 999. > > What do these queries show? > > SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; > > SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; mailman=> \c mailmanweb You are now connected to database "mailmanweb" as user "mailman". mailmanweb=> SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; id | thread_id | date_active | category_id | mailinglist_id | starting_email_id -------+----------------------------------+------------------------+-------------+----------------+------------------- 35670 | GHLCKUC7TDEBAI27SKRQN5PWX3TGB26Q | 0102-04-15 20:06:12+00 | | 3 | 150555 (1 row) mailmanweb=> SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; id -------- 136872 150555 (2 rows) Does this mean it imported archives with an invalid date somehow? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

HI Mark, On 6/26/25 13:16, Mark Sapiro wrote: >On 6/26/25 11:37, Hirayama, Pat wrote: >> >> When I look at the domains in mailman-core, I see: >> >>>>> show_domains() >> <Domain fhcrc.org> >> <Domain fredhutch.org> >> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> >> <Domain lists.hanc.info, , alias: > >> - owner: cit-sys-engineering(a)fredhutch.org > > >This is part of the problem. The alias domain for a list should not be a >real domain. Apparently, someone set this up so that mail to lists in >the lists.fhcrc.org domain would go to the corresponding list in the >lists.fredhutch.org domain. I think that may actually work, but you need >more. In order to add recipients to the patest-bounces addresses, the >recipient domains need to have an alias domain. In the cases below the >domains lists.fredhutch.org and lists.hanc.info. E.g set an alias domain >for lists.fredhutch.org to x.lists.fredhutch.org and for >lists.hanc.info to x.lists.hanc.info. Ah, I think that makes sense. So, add the alias domains here or through the CLI: [cid:3f6bbb96-1ec3-4bdd-9a59-991fc9d1e31b] Oh, does the alias domain x.lists.hanc.info (etc) need to be resolvable in DNS, or will it be internal just to Mailman? Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Replaced multipart/alternative part with first alternative.

1 month, 4 weeks

[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. ===========

3 weeks, 2 days

[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.

4 years, 6 months

[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, 1 month

[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

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

Search results for query "sapiro"