- Mailman-users - lists.mailman3.org

Delete Django profiles not signed up to a list
by Andrew Hodgson 02 Apr '23

02 Apr '23

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 02 Apr '23

02 Apr '23

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) 01 Apr '23

01 Apr '23

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 01 Apr '23

01 Apr '23

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 01 Apr '23

01 Apr '23

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

Need some help getting this working...
by Marisa Giancarla 31 Mar '23

31 Mar '23

I'm trying to get mailman set up again (don't ask what happened) and I am having trouble. Anyone interested in working with me to resolve the issues? I'm trying to run itonUbuntu22.04 if that makes a difference. I can provide shell access to the mail server... Thanks for the attention! Marisa -- This email has been checked for viruses by Avast antivirus software. www.avast.com

2 1

Question about whitlisting a domain for specific mailing list
by Zaheer Abbas 30 Mar '23

30 Mar '23

Hi All, I need to whitelist a domain for a specific mailing list on your platform. Only *(a)example.com email addresses should be allowed to post messages to this list. Could you please provide me with documentation or instructions on how to achieve this? I have already searched the knowledge base and user manuals without success. I believe it was previously available in mailman2 via Accept_these_nonmembers attribute. But I cannot find this attribute anywhere on postorius. I am using mailman 3.2.2 Any help would be really appreciated. Best regards, -- *ZA*

3 5

500 error on Held Messages page
by Dan Caballero 30 Mar '23

30 Mar '23

Hello, I searched the list but couldn't find anything specific to the error seeing with held messages for this specific list. See output below from the mailman.log. The problem doesn't seem to be related to the database listarchiver table. Please advise. -- Dan Caballero Caltech Systems Administrator MySQL [mailman3_prod]> select * from listarchiver where mailing_list_id='4899'; +------+-----------------+--------------+-------------+ | id | mailing_list_id | name | _is_enabled | +------+-----------------+--------------+-------------+ | 1872 | 4899 | mhonarc | 0 | | 1873 | 4899 | mail-archive | 0 | | 1874 | 4899 | prototype | 0 | | 1875 | 4899 | hyperkitty | 1 | +------+-----------------+--------------+-------------+ 4 rows in set (0.001 sec) -------------------------------------------------------------------------------------------------- 2022-09-20 14:44:17 [FALCON] [ERROR] GET /3.1/lists/jewishlife(a)caltech.edu/held?count=10&page=1 => Traceback (most recent call last): File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 182, in on_get resource = self._make_collection(request) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in _make_collection entries = [as_dict(resource) for resource in collection] File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> entries = [as_dict(resource) for resource in collection] File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 173, in _resource_as_dict assert resource is not None, resource AssertionError: None

3 13

Re: 404 on fresh install (Debian11)
by Stephen Turnbull 29 Mar '23

29 Mar '23

Sorry about breaking the thread, institution system "upgrade" to O365 broke my world so I'm cutting and pasting into Outlook. comprepair_jimberg--- via Mailman-users writes: > Can you setup Mailman3 for me? I have done apt install > mailman3-full but I have no clue whaat I am doing. You should seriously consider either going for a managed host or hiring somebody. Unfortunately, you're asking a bit much for volunteer help. The problem is that Debian uses the FHS layout with the system Python,while we core devs recommend and use a self-contained "virtual environment" with an /opt-style layout. Debian also applies patches that may or may not be backports from more recent versions. We just don't know what's going to go wrong on a distro install. Mailman also has dependencies on several system components (webserver, mailserver, WSGI implementation, SQL database, text indexer) which each come in multiple flavors, but the range of combinations we're familiar with is limited and may not even include the Debian default list. Once you have a working Mailman installation we'll be happy to help you tune it, though. (And you don't need core devs for that anyway, other Mailman site admins who hang out here can often help as well as well as we can.) We are much more likely to have knowledge and experience to help with a virtual environment install as described in https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Here's an alternative, "from the ground up" step by step description of a specific combination of components: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I think it should work just fine for Debian 11 as well. The author of "Mailman3 On Debian10" was a hosting and mailing list service provider, and used this recipe for all his hosts. Regards, Steve

1 0

Sending a message to a subscription applicant when a subscription request is made
by Allan Hansen 29 Mar '23

29 Mar '23

Dear Mailman 3 wizards, Our subscription process requires that the applicant answers a few questions and sends them to the list moderator. Not having a template that gets sent on all subscribe requests, I'm using the 'list:admin:action:subscribe' template. This gets sent to the list moderator, who then sends it forward to the applicant. This is rather tedious. I would like the template to be sent directly to the applicant. There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. Our Subscription Policy is currently: 'Moderate' for all lists. I figure that three modifications can be used to fix this: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Any suggestions on how to best and most quickly do the above would be appreciated, starting with (a.) or (b.). Clearly, (a.) and (b.), if we do one of those, are hacks that will need to be applied upon Mailman updates. That's fine by me, as I'm in rush to get this done. I'd welcome pointers as to which file to change and how. Of these two options, which would be the least work? (c.) could be entered as a longer-term enhancement request. I can submit that request if you like. Yours, Allan Hansen P.S.: Thank you for the enhancement that lets moderators see the member lists. It has been a big help for us. GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /opt/mailman/mm/mailman.cfg db url: postgresql://mailman:VWy26K4pUfU4jw@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass

2 6