August 2024 - Mailman-users - lists.mailman3.org

Python program to create lists and import settings from Mailman 2 to Mailman 3
by Greg Newby 10 Aug '24

10 Aug '24

Hi friends. A couple of weeks ago I asked for help with calling Mailman functions from within a Python program. This was to avoid using the web interface or shell commands to create a new list from a legacy Mailman 2.x list, and instead do it from within a Python program. Here is the program I ended up using, and I thought it would be worthwhile to get into the Mailman users list archives for future folks. Note that this is for the (recommended) venv installation of Mailman. Some things might be different for other installations. I'll paste the program and also attach it: #!/opt/mailman/venv/bin/python3 # Note: The line above should be the Python3 interpreter for your # installed version of Mailman3. It's the same as the first line in # your 'mailman' command, which might be named manage.py or something # else in your environment. # The venv version of Mailman used to develop this program is: # GNU Mailman 3.3.9 (Tom Sawyer) # Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] # About: # The multiple steps of creating a Mailman 3 list based on a legacy # Mailman 2.1 list. # gbn July 28 2024. This little program is granted to the public domain. ######################################################################## # Adjust these variables for your list, domain, MM2 and MM3 locations: lists_to_import = [ # listname, domainname ('testlist','example.org'), ('testlist2','example.org') # Add more lists as needed ] ######################################################################## # Load prerequisite functionality: from mailman.config import config # Needed for transaction.commit from mailman.core.initialize import initialize # For initialize() from mailman.app.lifecycle import create_list # For create_list import pickle # Pickle file handling from contextlib import ExitStack # Pickle file handling from mailman.commands.cli_import import _Mailman, _Bouncer # "" from mailman.utilities.modules import hacked_sys_modules # "" import subprocess # Subprocess for import21 ######################################################################## # Step 0: Initialize the environment: # Without arguments, initialize() looks in the standard locations for your .cfg def do_init(): initialize() # Alternative: Load an explicit configuration file, such as: # initialize('/etc/mailman3/mailman.cfg') ######################################################################## # Step 1: Create the list # Note: This fails silently if the list already exists or something goes wrong def do_create(new_list): try: # The list might exist or otherwise not be creatable l = create_list(new_list) except: # I did not find useful return values from create_list to diagnose print('create_list('+new_list+') failed. Trying to proceed anyway') # This saves your new list: transaction = config.db transaction.commit() ######################################################################## # Step 2: Rewrite the pickle file from the legacy list. def do_pickle(old_pickle_file, new_pickle_file): # These definitions are so the old pickle file can be parsed: with ExitStack() as resources: resources.enter_context(hacked_sys_modules('Mailman', _Mailman)) resources.enter_context( hacked_sys_modules('Mailman.Bouncer', _Bouncer)) # Input the old pickle file from MM 2.1 with open(old_pickle_file, 'rb') as fp: data = pickle.load(fp) # ban_list was a problematic value from my MM2.1 lists: # print(data['ban_list']) data['ban_list'] = [] # Any other settings you want to change? Add them here. These # variables may be seen with MM2's 'config_list' command data['require_explicit_destination']=1 # yes data['member_moderation_action']=1 # reject data['generic_nonmember_action']=2 # reject data['max_num_recipients']=2 # block cc/bcc to list fp.seek(0) # probably not needed fp.close() # ditto # Output: Rewrite the file in the current MM3 format with open(new_pickle_file,'wb') as ofp: pickle.dump(data, ofp) ofp.close() ######################################################################## # Step 3: Import the legacy settings to the newly created list def do_import(new_list, new_pickle_file): # I did not see how to call import21 directly from Python, so am using # a subprocess which basically uses the CLI syntax. # # CLI syntax: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE def import_list(listname, pickle_file): command = [ 'mailman', 'import21', listname, pickle_file ] subprocess.run(command, check=True) # print(f"List {listname} imported successfully.") # Import the list via a subprocess: import_list(new_list, new_pickle_file) # This saves your changes: transaction = config.db transaction.commit() ######################################################################## # Main process: do_init() # Loop for all lists we want to create & import: for new_listname, new_domainname in lists_to_import: new_list = new_listname+'@'+new_domainname # Adjust for wherever your old MM2 lists are: old_pickle_file = '/var/lib/mailman/lists/'+new_listname+'/config.pck' print('Starting list '+new_list) # The new pickle_file doesn't need to be saved after this program exits new_pickle_file = '/opt/mailman/'+new_listname+'-new.pck' do_create(new_list) do_pickle(old_pickle_file, new_pickle_file) do_import(new_list, new_pickle_file) print('Done with list '+new_list) # Don't forget to import and then index your list for full-text # searching. We're not doing that here because it takes awhile # (depending on the size of the archive). Use a command from the bash # shell such as: # mailman-web hyperkitty_import --since=1971-01-01 -l listname@domainnamed /var/lib/mailman/archives/private/listname.mbox/listname.mbox # followed by: # mailman-web update_index_one_list listname@domainname ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 1

Display the last post time for a list or all lists.
by Henrik Rasmussen 09 Aug '24

09 Aug '24

Does Mailman 3 have something similar to https://www.msapiro.net/scripts/last_post.py displaying the last post time for a list or all lists?

3 4

Mailman/Django-allauth integration with Yahoo
by Дилян Палаузов 09 Aug '24

09 Aug '24

Hello, Has anybody managed to use the Django-Allauth Yahoo provider to authenticate towards Mailman3? I have integrated mailman3/django-allauth/gmail — it works. I want in the same way to integrate mailman3 with yahoo mail. As advised at https://docs.allauth.org/en/latest/socialaccount/providers/yahoo.html , in yahoo I register an application with redirect URL https://l.bapha.be/mm3/accounts/yahoo/login/callback/ , then I add credentials under mm3/admin/socialaccount/socialapp/: client ID and Private Key. I append in settings.py:INSTALLED_APPS = [… 'allauth.socialaccount.providers.yahoo' ]. After I do all of this, I eventually visit /mm3/accounts/login/?next=/mm3/postorius/lists/at.l.bapha.be/, click on Yahoo: “Sign In Via Yahoo . You are about to sign in using a third-party account from Yahoo.” → [Continue]. Now at https://login.yahoo.com I enter user name and password. Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: Messages: Confirmation of email address sent to ...(a)yahoo.com Menu: Entrance \r\n New registration Confirm your email address: We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I have indeed received an email, which states: New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. Any idea what can I improve? In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? Greetings Дилян

2 3

migrate MM3 list from an old server to a new one
by noc＠iem.at 08 Aug '24

08 Aug '24

hi all, i have an old mailman3 instance (3.2.1), and would like to migrate it's lists and archives to a new instance (3.3.8) on a different host. for various reasons, i don't think i am able to upgrade the old instance in-place. unfortunately, i haven't found any documentation on how to proceed. there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? thanks for your help. gamsr4e IOhannes PS: (again) I'm resending this message, as the one i sent yesterday seems to have vanished (i *did* check the archvies). i have no clue why this happens, as i can post via the webinterface just fine (only when using my trusted MUA they just vanish).

4 10

Header settings and Gmail
by erik＠dante.de 07 Aug '24

07 Aug '24

Hi, We operate a mailing list on which many members use their Gmail address. In the default settings, this results in a warning and delayed delivery (and maybe marking as spam): status=deferred (host gmail-smtp-in.l.google.com[74.125.128.27] said: 421-4.7.28 Gmail has detected an unusual rate of unsolicited mail. To protect 421-4.7.28 our users from spam, mail has been temporarily rate limited. For 421-4.7.28 more information, go to 421-4.7.28 https://support.google.com/mail/?p=UnsolicitedRateLimitError to 421 4.7.28 review our Bulk Email Senders Guidelines. As a preventive measure, it helps to use DMARC mitigation action with “Replace From: with list address” and “ DMARC Mitigate unconditionally ”. But now some users are unhappy with the From header " Username via Test-liste <test(a)test-liste.org>". They would rather have their email address in it. Is there a solution with which Google delivers the mailing list messages without complaining, but the sender email address is also in the “From:”? Thanks Erik

3 5

Only Recent archive tab works after mailman upgrade
by zoltan＠circle-interactive.co.uk 06 Aug '24

06 Aug '24

Hi, since I upgraded mailman to 3.3.9 (python 3.11.2) I have an odd issue on lists' archive page. Apparently only the Recent tab works. If I switch to Active or Popular I see the change in the url but page content does not refresh. I can not see any errors in browser console and in logs so I am quite clueless how to debug further :( Thanks for the ideas.

3 4

Where to put static files referred to from list Info page?
by Greg Newby 06 Aug '24

06 Aug '24

Hi friends. Some of my version 2.1 lists had some static files that were referenced from the list's HTML pages. I'd like to do the same for the lists now that they're ported to MM3. My question: Is there a place I can put these files within the Mailman directory hierarchy so they can be linked from the list Info page? I.e., under "Settings / List info / Long description" I'd like to include a <a href=...> to a file that's somewhere in a persistent location in the same directory tree as the Mailman web. I tried putting it under mm/var/lists/listname/ (where 'listname' exists, and is where templates go. This yielded a '404.' I confirmed I can add an href to the Long description, but don't know where in the Mailman3 directory hierarchy I can put the files. Thanks! Greg Newby

2 4

External MTA incoming mail: configuration
by Roland Giesler 06 Aug '24

06 Aug '24

I have mailman set up to send mail via an external MTA, which is supported by mailman and described in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Specifically it says: |lmtp_host|and|lmtp_port|are parameters which are used by Mailman, but also will be passed to the MTA to identify the Mailman host. The “same host” case is special; some MTAs (including Postfix) do not recognize “localhost”, and need the numerical IP address. If they are on different hosts,|lmtp_host|should be set to the domain name or IP address of the Mailman host.|lmtp_port|is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using it. However, there is a practical problem with LMTP (to receive incoming email) which is as follows: The setup in mailman.cfg: lmtp_host: lists.fast.za.net lmtp_port: 8024 Now, lists.fast.za.net is the mailman server. The docs say that mailman passes these on to the MTA. However, the MTA (postfix) on box2.gtahardware.co.za has the following setting in it main.cf: virtual_transport=lmtp:[127.0.0.1]:10025 If I reply to a signup confirmation email for example, the mail is received and processed by box2.gtahardware.co.za, and it is not passed on to the mailman server. So what is meant by "but also will be passed to the MTA to identify the Mailman host" in the docs? If I change the config of the MTA (postfix) to be "virtual_transport=lmtp:[lists.fast.za.net]:8024", I assume the incoming mail will be forwarded, but how does postfix know that only the mailman emails should be forwarded and not all the other mail that the server at box2.gtahardware.co.za receives? This is quite fuzzt to me at this stage. Could someone help me with some clarity please?

3 21