April 2023 - Mailman-users - lists.mailman3.org

upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner
by Guillermo Hernandez (Oldno7) April 4, 2023

April 4, 2023

As you could have read yesterday, I had problems upgrading to the last versions of mailman3 related apps. The lmtp runner stopped after upgrade and showed and error in aiosmtpd package. the O.S. version running may servers is FreeBSD 13.1-p7 That was in a mailman3 server with few lists and traffic. O did the upgrade today in the server that has many lists and hard traffic. When I restarted mailman it showed this trace: Generating MTA alias maps /usr/local/mailman3 # Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported As Mark pointed it can be circunverted modifying /PATH_TO_YOUR_PYTHON/site-packages/aiosmtpd/controller.py and changing the 49th line as this: # Helper function to assist in mocking^M ## return has_ipv6^M return False After that, restarting mailman 3 works perfectly. It seems that FreeBSD is handling IPv6 in a way that other OSs dont. It surprise me, because FreeBSD was the first OS where IPv6 was deployed, but it is what it is. Thaks to everybody for your patience, specially Odhiambo and Mark. -- ___________________________________________ 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.

4 11

Custom Archiver
by Stephen J. Turnbull April 3, 2023

April 3, 2023

Mark Sapiro writes: > On 4/1/23 16:33, Peter Knowles wrote: > > That all being said, on a slight segway... Aside from using the > > REST API, is it practical or possible to manipulate the database > > directly? That is, in doing so would it just work or are there > > extra moving parts when an API request is issued? > > It probably is possible, but I would definitely discourage it. The > REST API should provide everything you need without your having to > reimplement everything it does. I think it would probably be a really heavy lift, because Mailman internally uses an object-relational manager, SQAlchemy. We occasionally change the schema, and SQAalchemy will automatically upgrade the database schema. You would have to handle that by hand in your code. I would recommend you get the sources for mailmanclient (https://gitlab.com/mailman/mailmanclient, iirc). They're quite repetitive, you wouldn't want to literally port them, but once you're familiar with the scaffolding and a couple of the commands you should be able to write a lot of PHP really fast to cover the REST endpioints you most need in a library with an API to your taste. Steve

1 0

Delete Django profiles not signed up to a list
by Andrew Hodgson April 2, 2023

April 2, 2023

Hi, I have noticed recently I have around 2000 bogus sign-ups that have created accounts in Django. Looking through the logs these have come from the Postorius sign-up pages. I checked and email confirmation is required before the accounts are created and the email addresses that have been used do seem like they could respond to these requests. I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? Thanks. Andrew.

6 13

Custom Archiver
by pknowles＠tpnsolutions.com April 2, 2023

April 2, 2023

I'm playing around with installing Mailman Core, and want to have messages on a "per-list" basis sent to a special "archiver" address which I intend to make archives available at via a custom built "read-only" IMAP client. How would I go about having messages sent to this external address, short of adding the address as a subscriber?

3 3

lmtp runner not starting
by Guillermo Hernandez (Oldno7) April 1, 2023

April 1, 2023

This morning I upgraded the mailman3 installation of the less traffic server I have: a bunch of lists, with very slow traffic. (see pip lists at the end) I sent test mails to a pair of lists, but none were distributed or archived. postorius seemed working well. First I thought it was some I did wrong in the upgrade procedure, but then I realized the lmtp runner was not running. I followed old messages about similar problem (many of them in this same mailman-users list), but I cannot see what is wrong. There is no error logged in mailman.log. the mailman.cfg of the lmtp is the default (and was working at least a pair of weeks ago) *-*-*-*-*-*-*-*-* from mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix *-*-*-*-*-*-*-*-* There is no one listening in port 8024. I tried changing the port (to 9024), with the same results. postfix seems working well. I's just there is nothing listening on port 8024 because lmtp runner is not running :) (from maillog): connect to 127.0.0.1[127.0.0.1]:8024: Connection refused (another simple test) root@www:/usr/local/mailman3 # telnet localhost 8024 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused I'm running out of ideas. Any clue to somewhere to dig in? *-*-*-*-*-*-*-*-*-*-* runners started Apr 01 17:24:40 2023 (4681) out runner started. Apr 01 17:24:40 2023 (4680) virgin runner started. Apr 01 17:24:41 2023 (4679) command runner started. Apr 01 17:24:42 2023 (4688) retry runner started. Apr 01 17:24:43 2023 (4686) in runner started. Apr 01 17:24:44 2023 (4683) digest runner started. Apr 01 17:24:44 2023 (4684) nntp runner started. Apr 01 17:24:45 2023 (4682) archive runner started. Apr 01 17:24:46 2023 (4685) bounces runner started. Apr 01 17:24:47 2023 (4687) task runner started. Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries Apr 01 17:24:48 2023 (4678) pipeline runner started. Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries *-*-*-*-*-*-*-*-*-* pip lists with versions installed root@www:/usr/local/mailman3 # pip list | grep mailman django-mailman3 1.3.9 mailman 3.3.8 mailman-hyperkitty 1.2.1 mailmanclient 3.3.5 root@www:/usr/local/mailman3 # pip list | grep django django-allauth 0.51.0 django-appconf 1.0.5 django-compressor 4.0 django-extensions 3.2.0 django-gravatar2 1.4.4 django-haystack 3.2.1 django-mailman3 1.3.9 django-picklefield 3.1 django-q 1.3.9 djangorestframework 3.13.1 root@www:/usr/local/mailman3 # pip list | grep postorius postorius 1.3.8 -- ___________________________________________ 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.

3 12

Email discard
by qro＠xs4all.nl April 1, 2023

April 1, 2023

Hi I have a good working mailman3 list server with 3 mailing lists. 2 of them work OK, but 1 has a little odd behaiver If a non member send an email it will discard while the setting in /postorius/lists/list.name.nl/settings/message_acceptance shows Hold for moderation A snip from var/mailman3/mailman.log Apr 01 10:48:32 2023 (49342) DISCARD: <4359976d-d4bb-9b30-0901-c842aa1fecb3(a)xs4all.nl>; ['The message is not from a list member'] Changing and saving a other choice makes no difference. Where can I look more to find a solution? (in mysql?) Peter

2 1

Dealing with spam from Web users
by Jeremy Stanley April 1, 2023

April 1, 2023

We recently migrated a bunch of lists from 2.1 to 3.3.7 and have started to get spammers posting via HyperKitty (because I guess that's easier for them than SMTP). It looks like I should be able to set posts from HyperKitty to be automatically moderated by creating a header filter on "User-Agent" matching "HyperKitty" but is there a better/easier way? Also, for things which already went out to the list, obviously I can ban the spammer but what's the cleanest solution for removing their posts from list archives so that we don't further their goals by continuing to publish their handiwork? -- Jeremy Stanley

2 1