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

[MM3-users] Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > Hello. > > I tried to remove random email address signing ups (which I signed up > while testing) via admin panel. After removing I tried to sign up again, > but I am getting, > > 'A user is already registered with this e-mail address' You removed the user's subscription from the list, but you didn't remove the user from the system. Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. User's have addresses and a user or one of the user's addresses can belong to a list with one or more roles (non-member, member, moderator or owner) > Combing through the database, I found auth_user table in mailman3web db > still contain those mail address. How to wipe email address entirely > from the db so I can signup again without the 'forget password' method There are a couple of things. If you log in to the web UI as a django superuser, you can go to the django admin UI -> Users section and delete the User, but I think that will only delete the web user and not delete the user from Mailman core. You can also log in to the web UI as the user and go to <https://lists.mailman3.org/user-profile/delete>, but that again only deletes the web user, and if you could do that, you could just subscribe once you're logged in, so I assume that's what you want to avoid. I don't think there is a way for a user as opposed to a site admin to delete her user record from Mailman core and even for a site admin, there's no way in Postorius to delete a user from core. It has to be done via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Docker or virtualenv?

by J.Schulz

For Docker: just use the README on https://github.com/maxking/docker-mailman ; this should be enough for a basic setup. Eventually, you'll need to add some things to core/mailman-extra.cfg : ___ [mailman] site_owner: help(a)elternserver.de SMTP_MAX_RCPTS = 1 VERP_CONFIRMATIONS = Yes VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = 1 # [devmode] # enabled: yes # recipient: you(a)somewhere.com # # extra local settings for mailmen [mta] # NullMTA is just implementing the interface and thus satisfying Mailman # without doing anything fancy # outgoing: mailman.mta.null.NullMTA smtp_user: your_auth@your_MTA smtp_pass: supersecretpassword smtp_verify_hostname: yesorno smtp_secure_mode: starttls # or whatever # [logging.debug] [logging.smtp] level: warn ___ also, web/settings_local.py needs tweaking in some cases; the DJANGO_ALLOWED_HOSTS come from my docker-compose.yml ---- import os # see https://github.com/maxking/docker-mailman/issues/548 django_allowed_hosts = os.environ.get('DJANGO_ALLOWED_HOSTS') if django_allowed_hosts: ALLOWED_HOSTS = django_allowed_hosts.split(':') MAILMAN_WEB_SOCIAL_AUTH = [] SOCIALACCOUNT_PROVIDERS = { } DEBUG = False # see https://gitlab.com/mailman/mailman/-/issues/957 DEFAULT_AUTO_FIELD='django.db.models.AutoField' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'xapian_backend.XapianEngine', 'PATH': "/opt/mailman-web-data/fulltext_index", }, } ----- Am 10.01.23 um 09:11 schrieb Odhiambo Washington: > Hi Jörg, > > Kindly share the link to the HOWTO, which you use to setup everything. > I just need to test. Perhaps I can use docker on Windows, no? > > On Mon, Jan 9, 2023 at 8:58 PM Jörg Schulz <info(a)joergschulz.de> wrote: > > I have a successful installation using docker, just updated to the > most > recent version - it runs along quite some other docker containers, so > there is a benefit when I want to switch machines. > > Am 07.01.23 um 12:02 schrieb Odhiambo Washington: > > On Sat, Jan 7, 2023 at 1:54 PM Johannes Rohr <johannes(a)rohr.org> > wrote: > > > >> I wanted to say "I have now chosen virtualenv". Sorry for the > confusion. > >> > > I have never tried docker, but soon I will. Just for the kicks. > > > > > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.netmailto<mailto:mark@msapiro.netmailto>:mark@msapiro.net<mailto:mark@msapiro.net>> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…> > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. _______________________________________________ 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> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

3 years, 7 months

[MM3-users] Re: import21: ModuleNotFoundError: No module named 'Mailman'

by Mark Sapiro

On 7/28/19 4:18 PM, Christian Schwarz wrote: > > Most mailing lists can be imported successfully using the `import21` subcommand, as described in the docs. Good. > Some mailing lists fail with the following error: > > sudo -u list mailman import21 REDACTEDLIST(a)example.org /var/lib/mailman/lists/REDACTEDLIST/config.pck > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailman/commands/cli_import.py", line 64, in import21 > pickle_file, encoding='utf-8', errors='ignore') > ModuleNotFoundError: No module named 'Mailman' I know what's happening, but I need more detail to do more than guess at how to fix it. The issue is there is a Mailman 2.1 Mailman.xxx.yyy object in the config.pck file. My best guess is that the list's bounce_info is the culprit. The list's bounce_info is a dictionary with keys equal to member addresses and values equal to the Mailman.Bouncer._BounceInfo object representing that member's bounce info. So when import21 calls pickle.load to load the config.pck, there is a reference to one or more Mailman.Bouncer._BounceInfo objects, but pickle.load can't find the definition of that object and that raises the exception. As to how to proceed, there are a couple of ways. One is to fix import21 so it ignores this issue. I just reported <https://gitlab.com/mailman/mailman/issues/618> on this, but I'm not sure how to fix it. I don't think it will work to try the pickle.load and pass the ModuleNotFoundError exception because I think the rest of the pickled data won't be returned. It looks like you still have the MM 2.1 installation, so you could use either MM 2.1's bin/withlist or bin/config_list to set the list's bounce_info to an empty dictionary. and then use the updated config.pck for the import. This assumes that bounce_info is the issue. You can verify that there is a non-empty bounce_info dictionary with either bin/withlist or bin/dumpdb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] UnicodeEncodeError: 'ascii' codec can't encode character

by Stephen J. Turnbull

Marvin Gülker writes: > I've accidentally sent from an unregisted address to one of my lists. > Mailman correctly held the message back for moderation, but when I go to > the page for held messages in postorios, I receive a 500 error. I've > included an except from the log below. To me, it looks as if it errors > on processing my last name (which has a non-ascii character in > it). You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right? If you're right about the umlaut being the trigger, the first thing I'd look at is a feature-negotiation problem in the MTA delivering to Mailman. I'm pretty sure our LMTP does not offer the SMTP UTF8 feature. > Ideas? And how do I discard the message without access to the held > messages page? I would guess this is in the shunt queue. If there's only one file there, you can just delete it. To get more information about the content of posts, use "mailman qfiles". > UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' > in position 269: ordinal not in range(128) Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name. So the non-ASCII character was replaced *on the way in*, and on the way out Mailman assumes ASCII in the header because Mailman doesn't know how to negotiate SMTP UTF8, and SMTP UTF8 specifies UTF8 in a context where there is no MIME way to indicate it to Mailman. So Mailman has no way of knowing it needs to encode to anything but ASCII (as specified by the Ancient Wisdom of RFC 5322). I'll put SMTP UTF8 support as a feature request in the tracker. I'm not sure how difficult this will be; it presumably involves RFC something (6532 or so?) internationalization support etc. and may not be trivial. So no short term promises, just medium term aspirations (next year's GSoC task list, for example). Steve

5 years, 5 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… How could I check, that the setting is used!? But maybe some additional information: - I use the Debian installation on a stable buster, so mailman is version 3.2.1 - I use apache2 as my web-server and use the given alias-conf-file - Python is version 3.7.3 - Postorius is Version 1.2.4 - HyperKitty is version 1.2.2 -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains What do I miss? Or where to investigate? Thank you in advance, best regards. By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Am 18.03.21 um 21:52 schrieb Mark Sapiro: > On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? > > Set FILTER_VHOST = True in your settings_local.py or where ever you put > your site Django settings. > >

4 years, 2 months

[MM3-users] Re: Pb with archive display

by Mark Sapiro

On 5/5/22 08:02, Pierre Malard via Mailman-users wrote: > > Unfortunately we still don't have any archives... > > Here are the logs retrieved from the mailman.log logs: > May 05 15:59:42 2022 (579075) Exception in the HyperKitty archiver: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} > raise ValueError(result.text) > ValueError: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} > > And in mailman-web.log: > WARNING 2022-05-05 13:58:52,996 579167 hyperkitty.views.mailman Could not archive the email with message-id '<C7E61653-D399-466A-BEC3-CE61D567E870(a)teledetection.fr>': character with byte sequence 0xe2 0x80 0x99 in encoding "UTF8" has no equivalent in encoding "LATIN1" > > Is it a way? > > I don't understand the message about LATIN1. > It seems to me that UTF-8 was the encoding retained in Mailman. I too don't understand what's trying to encode as LATIN1. The particular byte sequence is a utf-8 encoding of right single quote (’) which has no LATIN1 equivalent, but there's not enough info in the logs for me to determine exactly what's going on. There is an issue with MySQL and derivatives if that's the database you are using. You need the MySQL encoding to be UTF8MB4. in the DATABASES definition in your django settings you want ``` 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings. ``` but that doesn't seem to be the issue here. I suspect this issue has to do with the particular message. When mailman-hyperkitty processes the queue and a queued message throws an exception, it just dies. You might try moving aside the first (in alphanumeric sequence) message in /var/lib/mailman3/archives/hyperkitty/spool and see if the remaining messages can be processed. If that works I would like to see that message's .pck file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

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

by Mark Sapiro

On 6/24/16 8:18 AM, John Griessen wrote: > On 06/18/2016 02:10 PM, Mark Sapiro wrote: >> I think in the >> long run, you'd be better off with Mailman 3. > > > Is it time to install version 3? > > Is that going to work with different rewrite rules behind nginx? > > Will it cure my problem with moderation and nginx and https? If you are going to post to mailman-users(a)mailman3.org, please join the list. That way you will see replies to your posts such as the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. You can join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. The reply addresses your first question. With respect to your other questions, I think you have resolved your http/https issues in MM 2.1. MM 3 works similarly, but perhaps more obviously. When you create a domain in MM3 you specify a web URL for the domain's web UI. If this is an https URL, you won't have the issues you saw. There is another way to address this, and that's in the web server (nginx in your case) when you configure the web server to redirect http to https with a 301 Moved Permanently status (or maybe a 302), this tells the browser to issue a GET for the new URI, even if the original request was a POST. Thus the POST data is lost. That is the underlying issue. If instead, you configure the web server to issue a 308 Permanent Redirect instead, this tells the browser to issue a request for the new URI using the original GET/POST/whatever method, so the browser SHOULD reissue the original POST to the new URI. This will work provided the browser recognizes 308 and acts appropriately. Thus, fixing the scheme in Mailman is the more reliable solution as it doesn't depend on the browser knowing what to do. See, e.g., <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] parallel processing of out queue messages

by Stephen J. Turnbull

Dan Caballero writes: > I have tried increasing the number of runners to alleviate a > backlog of messages in the "out" queue. I increased the out runners > to from 32 to 64. How many messages per day are you processing?! How many CPUs do you have? How much memory? I know a site with 2 in runners and 8 out runners on something basically the same as a 8CPU 16GB premium Linode. It processes over 100,000 messages/day. The out queue occasionally gets in double digits but 99% of the time it's back at 0/1 in 3 seconds. Load average is usually around 5, CPU utilization 50-80%. I'm not sure it needs 2 in runners or 8 out runners, but it definitely needs at least 4 out runners. (We haven't tested a 4-runner configuration since resolving the "runner stall" issue described below. Virtual CPUs are not at a premium at that client.) > Is there another configuration needed beyond the number of runner > instances to get more messages processed at once? No, the slicing algorithm is trivial, the only upper bound (if you have enough memory ;-) is 2^160. One thing we ran into on the system above was some (still unidentified) issue between Mailman and its SMTP out gateway that caused an out runner to stall for extended periods (sometimes it would restart, often not, nothing interesting in the log). Unfortunately I don't have the monitoring tool we used, but it's easy to create one. The slicing algorithm is based on the file name, and divides the space of SHA1 hash values into N contiguous regions of each length.[1] Get a directory listing of the out queue, count each slice's length. If you see one (rarely more) that just keeps increasing, that's it. You can also use utilities like lsof to keep tabs on the connections to the outgoing SMTP gateway (connections are identified by the source port). If one lasts more than 5 seconds, that's it. Footnotes: [1] The slicing algorithm is in the __init__ function in mailman/src/mailman/core/switchboard.py.

1 year, 8 months

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

by Mark Sapiro

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. > Okay, so it looks like this is because the mail hosts are all tied > to the one web host. Yes. > We can create additional "sites" in the Django > admin UI and then switch the association of the mail hosts to those > distinct web hosts. But after doing so, the first vhost still seems > to show an unfiltered list of all lists in Postorius (Hyperkitty > continues to be fine), while Postorius on the other vhosts correctly > shows their filtered sets of lists instead. > > I also noticed when mailman-web is starting up, its log claims the > first site is being set as the "default domain," so have to wonder > if that's related to this behavior. Should we create an extra web > host to serve as the "default" so that all our typical vhosts get > the expected list filtering behavior, or am I completely off-base > and there's a much better approach I've missed? I'm not really sure what's going on here. You could try creating a dummy default host to see if that fixes the issue for you. There are subtle differences in the implementation between HyperKitty and Postorius that allow HyperKitty to work better, but it too will exhibit some anomalous behaviors. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 4:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 16:03, Odhiambo Washington wrote: > > > > There is just one more thing - I have this in settings.py: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > And what are LOGGING['handlers']['file']['level'], > LOGGING['handlers']['file']['class'] and > LOGGING['handlers']['file']['formatter'] > Those are left as defaults in my setup.py. > > However, the referenced file is ever empty. At what point is it supposed > to > > record anything? > > What is logged depends on `level` but even with `DEBUG` not much routine > stuff is logged. See https://docs.djangoproject.com/en/3.2/topics/logging/ I will read that and see if I get to pick up something. And now I am having a problem with mod_wsgi. First, the URL displayed when I load the page looks bogus to me. While I expect the URL to be https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an extra /mailman3! So I have; 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, or appears to. 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, or appears to. 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or appears to 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or appears to 5. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… - This throws an exception error when I click "Manage Subscription". -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ And while I do not quite understand the error itself, there is also one particular line that I also saw that has left me baffled: [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client 197.232.81.246:13865] AH00128: File does not exist: /usr/local/www/apache24/data/archives/list/ kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, refe rer: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Jered Floyd

This is due to a change in the dependencies. You can either demand an older version of django-allauth when doing your install, or I fixed it with this line added to the very end of my settings.py: # Fix for updated django-allauth MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) --Jered ----- On Oct 19, 2023, at 7:27 AM, Wikinaut mail(a)tgries.de wrote: > I followed all single steps until this: > https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… > (I will improve the documentation with the missing parts later today), > > Now I got this and got stucked and need your help: > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > > full stack: > (venv) mailman@mail:/run$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> > sys.exit(main()) > ^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/manage.py", > line 37, in main > execute_from_command_line(sys.argv) > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", > line 420, in execute > django.setup() > File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", line > 24, in setup > apps.populate(settings.INSTALLED_APPS) > File "/opt/mailman/venv/lib/python3.11/site-packages/django/apps/registry.py", > line 124, in populate > app_config.ready() > File "/opt/mailman/venv/lib/python3.11/site-packages/allauth/account/apps.py", > line 15, in ready > raise ImproperlyConfigured( > > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

1 year, 7 months

[MM3-users] Incoming command emails (i.e. listname-leave) routed to list itself

by Mark Lindsay

Hi mailman-users, I'm new to Mailman 3 and Mailman in general, but I've got it up and running, and my external app is communicating quite well with the administrative REST API. Here's the only problem I haven't been able to figure out: Say I have a list called "potato." List members can post to the list by emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to the list too. The command email gets sent out to all members, as if the user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. This is also the case with the potato-request(a)lists.mydomain.org address. I am using exim4 on Ubuntu. I followed the instructions here: http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The only change I had to make to the exim4 config files in the readthedocs instructions was in this line: MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} I had to change it to: MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} That is how the subdirectories are named in my lists directory. e.g. potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from readthedocs, I get 550 Unrouteable bounces. Here are some baffling lines from /var/log/exim4/mainlog from the incoming potato-leave(a)lists.mydomain.org email: 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification succeeded] 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport H=localhost [127.0.0.1] C="250 Ok" 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >`? I think this is actually an exim4 problem, so if the solution is to just switch to postfix, then I will definitely do that. But I'm just asking in case someone had a similar issue with exim4 and was able to work through it. Thanks a lot, Mark

8 years, 1 month

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 3/22/19 6:10 AM, Malcolm Austen wrote: > On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj > <maxking(a)asynchronous.in> wrote: >> >> "Default Processing" means the default pipeline defined in > > Thanks, I will do some (more!) reading. > >> List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This >> pipeline is >> system wide and is defined in source code, so it can't be customized by >> site administrator. > > Unfortunately, that is not available to list-owners on the system > concerned. Ancestry must have removed it. It wouldn't help you anyway. All it shows are the choices 'default posting pipeline', 'default owner pipeline' and 'virgin', not the contents. See <https://mailman.readthedocs.io/en/latest/build/lib/mailman/app/docs/pipelin…> for info on pipelines. Also, when we're talking about Default Processing in the context of moderation, we're not really talking about pipelines; we're talking about rule chains. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html> and <https://mailman.readthedocs.io/en/latest/src/mailman/chains/docs/moderation…>. This latter doc mentions 'defer' which is another name for 'Default Processing'. Also in the latter doc in the example under "Anne’s post to the mailing list runs through the incoming runner’s default built-in chain. No rules hit and so the message is accepted." you'll see Hits: Misses: dmarc-mitigation no-senders approved emergency loop banned-address member-moderation nonmember-moderation administrivia implicit-dest max-recipients max-size news-moderation no-subject suspicious-header The misses are the rules processed in the normal chain in order. When you set a (non-)member's moderation to Accept, at the appropriate (non)member-moderation rule, the rest of the chain is skipped and the message is accepted. If the(non-)member's moderation is Default Processing, that rule passes, but the remaining administrivia implicit-dest max-recipients max-size news-moderation no-subject suspicious-header rules are checked before the message is accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Controlling Mailman3 from the Linux commandline

by Eggert Ehmke

Why do you not use the mailman addmembers command? Agree, I also had to search for that. Am Samstag, 18. September 2021, 17:54:01 CEST schrieb Allan Hansen: > All, > > Not versed in Python, I found using the Python gateway to Mailman3 commands > rather cumbersome for the few and very simple interactions I have with the > shell. So I implemented a set of .bash scripts that I use instead. They all > have this from, where the last part is the Mailman shell command (in this > case the command for adding members in file $1 to the list $2). > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" > members --addmembers $1 $2 > > To invoke it: > > . addMembers.bash <FILE_OF_EMAIL> <listname> > > I have other scripts for commands such as: > > List all lists > List all members on all lists (with a sort -u) > Send an email with a given list's members to a given address > Delete members from a list > Delete members from all lists > Help > Count members on a list > > Note the one that sends the member list to a given email address. It does > this: > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" > members $2 |grep -v -e "has no members"|sed -e 's/.*/\L&/'|mailx > --subject=$2 $1 > > This one I use a lot because the system has a bug that does not allow > moderators to see the list of members on the list they are supposed to > moderate. My lists are set up to allow this, but it does not work. The > moderators send me an email with the request, I log on and run this script. > > I hope this is helpful. > > Yours, > > Allan > > > _______________________________________________ > 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/

3 years, 8 months

[MM3-users] Re: under which uid should uwsgi/manage.py run?

by Guillermo Hernandez (Oldno7)

On 14/1/22 18:16, Axel Rau wrote: > Hi Guillermo, > > thanks for your reply. > >> Am 14.01.2022 um 12:51 schrieb Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>: >> > . . . >> drwxr-xr-x 21 mailman mailman 1024 Jul 8 2021 lists > How are new lists created by the web frontend with uid www? That's because is not "www" who is doing that work (I suspect). In my apache24 httpd.conf file I have these lines ##### LoadModule wsgi_module "/usr/local/lib/python3.7/site-packages/mod_wsgi/server/mod_wsgi-py37.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty #### In the httpd-vhosts.conf I have all the Alias directives and, related to this, this lines: WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ##### I believe that you can be suffering of a mixup of configuration files (al least the ownership that has to be mailman). > I like your approach, but must resolve my pgsql cert access issue. > >> I've read your mail about your installation and I did it different. I followed the steps that I detailed in https://forums.freebsd.org/threads/mailman-3.61050/#post-488128 <https://forums.freebsd.org/threads/mailman-3.61050/#post-488128> > I followed the same, but had trouble with the recent cryptography python package. > I’m now at Python3.9 > >> Thus I don't know if it can help, but I know for sure that I don't like that your ../var/etc dir is owned by root. > I have changed that to mailman. > > Axel > --- > PGP-Key: CDE74120 ☀ computing @ chaos claudius > > _______________________________________________ > 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/ >

3 years, 4 months

[MM3-users] Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by skenny＠scss.tcd.ie

Our in-production Mailman 3 service is running under Docker (maxking's mailman-web, mailman-core and Postgres database containers). I want to move Mailman to a different server, where I have a clean install of Mailman 3 up and running. When I take a database dump of the in-production database, and import it on the new server, a ton of errors are produced, and the core and web containers die after 15 seconds or so. I have noticed that if I first delete the mailmandb database on the new server, then create it anew, and _then_ do the import, everything is fine. I see all my lists in the web interface on the new server, it's all good. But deleting and then creating a new blank mailmandb database just prior to importing ... it can't be the right thing to do. Below is a sample of the errors that are reported on the stdout from my docker-compose command. I'd be very grateful for any pointers as to where to go next with this. Many thanks in advance, Stephen Kenny database_1 | ERROR: relation "auth_permission_id_seq" already exists database_1 | STATEMENT: CREATE SEQUENCE public.auth_permission_id_seq database_1 | START WITH 1 database_1 | INCREMENT BY 1 database_1 | NO MINVALUE database_1 | NO MAXVALUE database_1 | CACHE 1; database_1 | ERROR: insert or update on table "_request"well violates foreign key constraint "_request_mailing_list_id_fkey" database_1 | DETAIL: Key (mailing_list_id)=(774) is not present in table "mailinglist". database_1 | STATEMENT: COPY public._request (id, key, request_type, data_hash, mailing_list_id) FROM stdin; database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_group_id_permission_id_0cd325b0_uniq UNIQUE (group_id, permission_id); database_1 | ERROR: multiple primary keys for table "auth_group_permissions" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_pkey PRIMARY KEY (id); database_1 | ERROR: multiple primary keys for table "auth_group" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group database_1 | ADD CONSTRAINT auth_group_pkey PRIMARY KEY (id); database_1 | ERROR: relation "auth_permission_content_type_id_codename_01ab375a_uniq" already exists database_1 | ERROR: relation "account_emailaddress_user_id_2c513194" already exists database_1 | STATEMENT: CREATE INDEX account_emailaddress_user_id_2c513194 ON public.account_emailaddress USING btree (user_id); database_1 | ERROR: relation "account_emailconfirmation_email_address_id_5b7f8c58" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_email_address_id_5b7f8c58 ON public.account_emailconfirmation USING btree (email_address_id); database_1 | ERROR: relation "account_emailconfirmation_key_f43612bd_like" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_key_f43612bd_like ON public.account_emailconfirmation USING btree (key varchar_pattern_ops); database_1 | ERROR: constraint "hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id FOREIGN KEY (thread_id) REFERENCES public.hyperkitty_thread(id) DEFERRABLE INITIALLY DEFERRED; database_1 | ERROR: constraint "hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id FOREIGN KEY (user_id) REFERENCES public.auth_user(id) DEFERRABLE INITIALLY DEFERRED; and finally .... mailman-core | Traceback (most recent call last): mailman-core | File "/usr/bin/mailman", line 8, in <module> mailman-core | sys.exit(main()) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1130, in __call__ mailman-core | return self.main(*args, **kwargs) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1054, in main mailman-core | with self.make_context(prog_name, args, **extra) as ctx: mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 920, in make_context mailman-core | self.parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1613, in parse_args mailman-core | rest = super().parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1378, in parse_args mailman-core | value, args = param.handle_parse_result(ctx, opts, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2360, in handle_parse_result mailman-core | value = self.process_value(ctx, value) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2322, in process_value mailman-core | value = self.callback(ctx, self, value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/bin/mailman.py", line 95, in initialize_config mailman-core | initialize(value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 218, in initialize mailman-core | initialize_2(propagate_logs=propagate_logs) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 177, in initialize_2 mailman-core | config.db = getUtility(IDatabaseFactory, utility_name).create() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 55, in create mailman-core | SchemaManager(database).setup_database() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 84, in setup_database mailman-core | current_rev = context.get_current_revision() mailman-core | File "/usr/lib/python3.8/site-packages/alembic/runtime/migration.py", line 435, in get_current_revision mailman-core | raise util.CommandError( mailman-core | alembic.util.exc.CommandError: Version table 'alembic_version' has more than one head present; please use get_current_heads() mailman-core exited with code 1 mailman-web | Compiling locale files in /usr/lib/python3.8/site-packages mailman-web | Traceback (most recent call last): mailman-web | File "/opt/mailman-web/manage.py", line 10, in <module> mailman-web | execute_from_command_line(sys.argv) mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line mailman-web | utility.execute() mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 363, in execute mailman-web | settings.INSTALLED_APPS mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 82, in __getattr__ mailman-web | self._setup(name) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 69, in _setup mailman-web | self._wrapped = Settings(settings_module) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 170, in __init__ mailman-web | mod = importlib.import_module(self.SETTINGS_MODULE) mailman-web | File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module mailman-web | return _bootstrap._gcd_import(name[level:], package, level) mailman-web | File "<frozen importlib._bootstrap>", line 1014, in _gcd_import mailman-web | File "<frozen importlib._bootstrap>", line 991, in _find_and_load mailman-web | File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked mailman-web | File "<frozen importlib._bootstrap>", line 671, in _load_unlocked mailman-web | File "<frozen importlib._bootstrap_external>", line 848, in exec_module mailman-web | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed mailman-web | File "/opt/mailman-web/settings.py", line 65, in <module> mailman-web | MAILMAN_ARCHIVER_FROM = (os.environ.get('MAILMAN_HOST_IP', gethostbyname(os.environ.get('MAILMAN_HOSTNAME', 'mailman-core'))),) mailman-web | socket.gaierror: [Errno -2] Name does not resolve mailman-web | python3: can't open file 'manage.py': [Errno 2] No such file or directory mailman-web exited with code 2

2 years, 10 months

[MM3-users] Re: Twitter OAuth2

by Mark Sapiro

On 12/28/22 11:37, Odhiambo Washington wrote: > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/27/22 21:46, Odhiambo Washington wrote: >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: >>>> >>>> I see from another post that you've decided against using Twitter, but >>>> to answer the question, Twitter does not require adding anything to >>>> SOCIALACCOUNT_PROVIDERS. >>>> >>> >>> I tried it and ended up with: >>> >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: >>> /accounts/twitter/login/ >>> Traceback (most recent call last): >> ... >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching >>> query does not exist. >> >> >> Do you have >> >> 'allauth.socialaccount.providers.twitter', >> >> in INSTALLED_APPS? >> > > Here is what I have in settings_local.py: > > INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > 'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > 'allauth.socialaccount.providers.google', > 'allauth.socialaccount.providers.facebook', > 'allauth.socialaccount.providers.twitter', > #'allauth.socialaccount.providers.stackexchange', > ) Did you add an app at https://site.name/admin/socialaccount/socialapp/ with twitter as a provider? See https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/26/21 9:49 AM, David Newman wrote: > On 11/25/21 1:16 PM, Mark Sapiro wrote: >> >> What django admin command are you running? > > As the mailman user, with venv activated: > > (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com > /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox hyperkitty_import is not a command. it is a subcommand to the django administration command. You need to run ``` mailman-web hyperkitty_import -l testlist(a)lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox ``` ... >> If you don't set DJANGO_SETTINGS_MODULE in the environment and you >> have activated your virtualenv and run `mailman-web` as the django >> admin command it will set /etc/mailman3/settings.py as the settings. > > I'd run these two environment commands as the mailman user with > virtualenv activated: > > export DJANGO_SETTINGS_MODULE=settings > export PYTHONPATH=/etc/mailman3/settings.py That should be ``` export PYTHONPATH=/etc/mailman3/ ``` but you don't need these. > Am I being overly literal here with 'settings' in that first command? > Asking because 'mailman-web check' runs clean before running these > commands and returns this error afterward: > > ModuleNotFoundError: No module named 'settings' Yes, the mailman-web command sets these up correctly if they aren't set, but if they are, it believes what you set which was wrong for PYTHONPATH. Don't set those environment variables and let mailman-web do it for you. > Either way, the hyperkitty_import command still isn't found. Again because it's not a command but a `mailman-web` subcommand. >> By default, only lists that you are owner, moderator or subscriber for >> are shown. What if you click Filter by Role and select All? > > Same result. In this case, the ID of the admin and list owner are the same. Have you set FILTER_VHOST = True in your settings.py. If so, that could possibly explain it. Can you access these lists at something like https://example.com/mailman3/lists/listname@example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Dist. List forwarding and DMARC Reject circumvention. Will this pattern work?

by titan160＠hotmail.com

I would be grateful if someone could vet and verify (or guide otherwise) the following pattern please. With the major mail vendors move to DMARC - Full Reject, I have a small challenge. - We have a number of 365 Distribution List addresses. - These lists accept email from anyone and, currently, then forward those emails onto list members. - List members, however, are NOT necessarily email addresses within the list's mail domain. They might be outlook.com, Gmail, yahoo, Hotmail, username(a)local.ISP. Consequently, DMARC Reject policies are causing these emails to be marked spam as the 365 Dist. List forwarding is not doing any header manipulation. My thinking is: - I could set up a Mailman list (elists.mydomain.com) alongside the 365 Exchange mail domain (mydomain.com) - I leave inbound mail deliver to the 365 Dist. lists. - I reconfigure the (mylist(a)mydomain.com) Dist. Lists to fwd to a similarly-named Mailman address at the email sub-domain (mylist(a)elists.mydomain.com) - The Mailman list, by virtue of having to use the 365 MTA, should be able to accept all inbound from the list (mylist(a)mydomain.com) - Mailman would then need to re-write the mail headers such that the inbound email to-be-forwarded from the Mailman list, both appears to come from the (mylist(a)mydomain.com) address, and also has the 365 'mydomain.com' SPF and DKIM records. And given Mailman has to use the 365 MTA, it would actually be coming from that main mail domain. - Somewhere in there, the original sender's email address would need to be included, such that a Reply-to-All from a receiving List member would not only go back to the List, but also the original sender. My thinking is that with this pattern, I don't need to worry about inbound emails to the list address as that would simply continue to function as normal, and fwdd mails from the List to recipient list members would not be marked spam as the headers would all be good. Is my thinking good? Or am I out of my cotton-pickin' mind?

9 months, 2 weeks

[MM3-users] Re: Hyperkitty performance problem

by monochromec

Following the root cause analysis which Tobias started all those weeks ago we (the admin team behind the installation) are still struggling with the following phenomenon: messages on average take more than 24 hours to be processed, more precisely, the average lifetime of a pickled message object in `/var/lib/mailman3/queue/pipeline` clocks in at around 26 hours). Couple of stats of the installation: standard installation from Bookworm OS repos, Hyperkitty as archiver and Postorius as web frontend as explained above, running Python 3.11.2 from the standard systemd service as packaged with the Bookworm deb file. All backends (Core + Hyperkitty) are supported by Postgres version 15+248. The MTA is a standard Postfix installation, again from OS packages. The underlying VM has 7 cores with just under 24 GB of main memory. This production instance is handling less than 130 mailing list (MLs) with an average of less than 10 postings per day per ML. CPU core utilisation hovers around 50% with the lion share allocated to the four pipeline runners as part of the MM configuration. OS resource utilisation is well below bounds (approx. 8 GB of main memory allocated to running processes), plenty of available sockets space (I noticed some transient `Connection lost during _handle_client()` warnings in the logs so I checked that the SMTP runner can connect to Postfix for delivering the messages after processing by checked the socket allocation of the running processes). Cursory review of the corresponding Core classes (runner + pipeline implementation in addition to `posting_pipeline`) didn't reveal any further pointers. What I did notice though that increasing the logging levels of the components (namely `smtp`, `pipeline` and `lmtp` to `debug`) in `/etc/mailman3/mailman.cfg` didn't add any useful information to the logs as configured after restarting the Core. As outlined above, Hyperkitty doesn't seem to do a check based on ML and message ID before archiving a message in the database. But this only add a REST roundtrip and Postgres communication through Hyperkitty's underlying Django framework to the overall system load and the driving UWSGI instance is well within CPU cycle bounds. Any pointers are appreciated - more than happy to provide more info if required.

5 months, 1 week

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 3/31/23 14:17, Andrew Hodgson wrote: > Hi. > > Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in ``` --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 @@ -2,13 +2,13 @@ import os import sys -sys.path.insert(0, '/opt/mailman/mm') +sys.path.insert(0, '/etc/mailman3') # The above line is required. The next line doesn't hurt, but it doesn't work # because the PYTHONPATH environment setting is processed by Python's setup # and must be in the environment when Python starts to be effective. -os.environ['PYTHONPATH'] = '/opt/mailman/mm' +os.environ['PYTHONPATH'] = '/etc/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' import django django.setup() ``` Also, look at this ``` # If we delete the Django user and there is a Mailman user with no memberships # shall we delete the Mailman user too. DELETE_MAILMAN_USER = False # Shall we delete the Django user if there is a Mailman user with no # memberships or only if there is no Mailman user. DELETE_DJANGO_IF_MAILMAN = True ``` and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Mailman 3 installation documentation

by Abhilash Raj

Hi All, I have been trying to work on revamping the documentation site we have at https://docs.mailman3.org. It is on https:// but I am not sure why the http->https redirect doesn't work in Readthedocs. I have set it to "serve always from https". Anyway, it might not look too different right now, but there are some small re-organizations. I have been learning some new ReST and Sphinx tricks and been trying to cross-reference and link various sections and settings. The docs site shows up Mailman's logo now (I didn't even know we could do that ;-). There is a place[1] for all supported Django settings that Postorius and Hyperkitty have. I am also planning to add some common Django settings that often people have to lookup and is not fun for people from non-python backgrounds. Hopefully, it will make lives easier for administrators. I have reverted my own stupid decision to use "sudo pip3 install" in the docs to instead use virtualenv. The installation docs are going to grow to be more comprehensive. I am also working on mailman-web project[3], which should simply installation process for all the web components using a single project and provide better guidance on Django's settings file management and howto run manage.py commands. I have added a `mailman-web` command, which, for those of you familiar with internal details of Django, is going to be our custom manage.py script. It sets up settings correctly and would hopefully reduce the pain of using `django-admin` and/or finding out the right path for `manage.py` script. It is still not ready for prime time, but it is usable. Early adopters can play with it if they like! I would really appreciate if people who have tried to manually install Mailman 3 in the past would share their experiences about what they think could be documented better. You can reply here or open an issue[2]. The user documentation are going to follow, hopefully soon :) [1]: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… [2]: https://gitlab.com/mailman/mailman-suite-doc/issues [3]: https://gitlab.com/mailman/mailman-web -- thanks, Abhilash Raj (maxking)

5 years, 8 months

[MM3-users] Re: New release candidates for Postorius and Hyperkitty

by Abhilash Raj

Hello Again, Turned out, there was an issue with a vendored JS library in Hyperkitty 1.3.4rc1. Also, someone requested another release of Core for a couple of bugfixes that have landed in master since the last release in November. I have just released Hyperkitty 1.3.4rc2 and Maiman Core 3.3.3rc1. Complete change logs are available here: Hyperkitty: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Core: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… New stable version of Core will be out alongside the other releases previously announced. Abhilash On behalf of GNU Mailman Team On Sat, Jan 16, 2021, at 12:38 PM, Abhilash Raj wrote: > Hey Everyone, > > Happy new year to everyone! > > I am pleased to announce new release candidates for Postorius and > Hyperkitty along with new releases for Mailmanclient and > Django-mailman3! > > These include both new features and bug fixes. Complete change log for > each components: > > Postorius 1.3.4rc1: > https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4rc1 : > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > Mailmanclient 3.3.2.: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > Django-mailman3 1.3.5: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > Since these are pre-releases, you can install them using: > > $ pip install --pre --upgrade postorius hyperkitty > > Or you can also specify the exact versions: > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > Unless there is a release-blocker bug, stable versions for Postorius > and Hyperkitty will be released in 2 weeks time. If you can test these > releases, we encourage you to report any bugs to us on Gitlab. > > If you'd like to help out with translations for some of the new strings > in your native language, the documentation is available here[1] on how > to do that. > > [1]: https://docs.mailman3.org/en/latest/translation.html > > -- > thanks, > Abhilash Raj (maxking) > On behalf of GNU Mailman Team -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: More Mailman releases!

by Eggert Ehmke

The upgrade worked flawless, and my system works as expected, but even after restarting apache in the footer line is displayed: Postorius Dokumentation • GNU Mailman • Postorius Version 1.3.9b1 In the venv: $ pip list | grep postorius postorius 1.3.10 Is this a leftover? Am Samstag, 21. Oktober 2023, 20:35:23 CEST schrieb Abhilash Raj: > Hello Everyone, > > I am pleased to announce several new releases for GNU Mailman project. > Thanks to all the contributors for making these releases possible! > > 1. Postorius 1.3.10 [1] > 2. Hyperkitty 1.3.8 [2] > 3. Django-mailman3 1.3.10 [3] > 4. Mailman-web 0.0.7 [4] > > All the releases are published to PyPI and you can find links to all the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 > [2]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 > [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst > Do note that for Postorius, I released 1.3.9, but I forgot to update > dependency metadata to require `django-mailman3>=1.3.10` (which is > required for the new bootstrap 5 upgrade across packages) and so I also > released Postorius 1.3.10 just after. > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > If you find any issues, you can report them at the respective bug > tracker for the projects. The links to issue trackers are available > at https://docs.mailman3.org/en/latest/. > > Finally, similar to Mailman Core, note that PyPI doesn't accept > signatures anymore so each packages' release page now has the tarball > uploaded to them along with the signature: > > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 > Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 > Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 > > -- > thanks, > Abhilash Raj (maxking)

1 year, 7 months

[MM3-users] Re: moving lists to another server

by Odhiambo Washington

On Mon, Nov 20, 2023 at 12:14 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > I use the utf8mb4 character set as default, unless something wants a > > different one. > > MySQL and MariaDB are almost similar. I have encountered very few > > significant differences since I switched to MariaDB. > > OK, then that would not be a problem. > > > On Mon, Nov 20, 2023 at 7:56?AM Stephen J. Turnbull < > > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > > Isn't one installation using 'mailman' and 'mailmanweb' databases, > > > while the other only 'mailman'? You'll need to deal with that at > > > least I suppose. > > > > This is true. However, I was hoping that I could merge the two foreign > DBs > > into one. I am yet to test it though. > > Yes. The point is that when you dump 'mailman' and 'mailmanweb' on > the old host the name of the database will occur in at least the SQL > CREATE DATABASE and CONNECT commands. You will need to edit that for > mailmanweb. > Actually, that was the easier part. [snip] > If there are only a few, it's little more time spent than writing > scripts. And you can be sure you'll have basically working lists that > you can fix any inadvertant configuration changes later. The only > thing I would double and triple check is privacy settings (reply-to > munging, archives, and subscriber rosters) and DMARC settings. In the > MTA of course you want to be very careful about getting SPF and DKIM > right for the new domain. > This is another easy part. How do I dump the archives into an mbox file? Thanks for all the support. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 6 months

[MM3-users] Re: Resetting users' password for them?

by Abhilash Raj

> On Apr 8, 2021, at 8:33 AM, Duane Raymond <duane(a)fairsay.com> wrote: > > Hi. > > I have quite a few users who when they reset their password, don't receive their password reset email. It works fine for many, so they are going out. But for those who they don't go out for, I was hoping to get their password reset key/token from the database tables and send it to them...only thing is I can't find it in there! )it may not be there). > > So what would you suggest for enabling people to reset their password when the system email isn't received: > - Is there a way to get the reset token so I can send it manually - if so, where/how do I find it? You can reset it without a reset token if you have admin access. You can go to `admin/auth/user/` on your installation, search for the user you want to reset the password for and you’ll see right at the top “username” and “password” fields and under password: > but you can change the password using this form. Click on “this form” to change password for the user. Make sure you are already logged in as superuser to be able to access /admin/ console. > - Would enabling social login be a work around for this problem? I don’t think there is a way for you as an admin to enable social login for them. But that wouldn’t reset their password, it is an additional mode of authentication. > - Anything else you can suggest? I am not sure why the emails aren’t going out for some users, it might be worth checking it in your MTA logs if those emails are indeed not being for some users or is it a problem on the users’ end. They should also check their Spam folders for these emails. > > Cheers, > > Duane > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as > > the list admin to send a new mail, but hold it back, to see what type it is. > You have to add the MIME types for the attachments you want kept the the > list's pass_types. You need to do this via mailman shell or REST as it > isn't currently exposed in Postorius. > Here's an example from a list that wants to accept PDFs as well as word > processing and spreadsheet documents. Note that nappdf and x-pdf are > uncommon PDF subtypes that I have seen. > ['multipart', > 'message/rfc822', > 'text/plain', > 'text/html', > 'application/pdf', > 'application/nappdf', > 'application/x-pdf', > 'application/rtf', > 'application/vnd.oasis.opendocument.spreadsheet', > 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', > 'application/vnd.ms-excel', > 'application/vnd.oasis.opendocument.text', > 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', > 'application/msword' > ] Thanks, done! However, PDF's and an image is still filterd out. On May 21st the list admin tested by setting Filter content to 'No'. As expected, the mail was received as sent, with PDF attachment, inline image and HTML intact. Resending this mail to a newly created test list (from Outlook by selecting Resend, which does exactly just that, the mail was again received as sent, even the config of Alter Messages as the same as the list having the problem. The difference was that list(m.pass_types) is [] Now, setting m.pass_types = ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword'] on the new testlist and resending the mail again, the mail still came out intact. So I guess the problem must be something complete different. Also I wonder why a newly created list accepts the PDF in question, when list(m.pass_types) is []. /Henrik Rasmussen

5 years, 11 months

[MM3-users] Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

First of all, best wishes and Happy New Year for everybody. Two days ago I had to reinstall all mailman3 related apps in a mailman 3 server (I tried to upgrade just hipperkitty, but it went bad). At first, all seemed running as before, but I just noted that the messages are not being archived. I did not change any config. Now the log is showing ERROR 2022-01-03 12:22:15,654 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,674 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,791 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:16,208 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-04 11:44:55,644 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:55,664 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,478 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,620 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,647 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header (it's a very low traffic list: just two messages in two days) I do believe I did the upgrade/reinstall procedure as in previous upgrades (using pip: it's a system wide installation, not using dockers or venv), but seems that I did something wrong The messages are being delivered normally, but it fails archiving Before I make a bigger hole for myself, where to look for? Versions installed: HyperKitty 1.3.5 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 uWSGI 2.0.19.1 Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 30 2020, 10:49:53) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a -- ___________________________________________ 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 years, 5 months

[MM3-users] Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Odhiambo Washington

On Wed, Oct 11, 2023 at 11:15 AM Kyriakos Terzopoulos < kyriakos.terzopoulos(a)gmail.com> wrote: > Hi, > > I have set up (I believe successfully) and configured the following in a > Virtualhost environment (with HestiaCP): > > - A record for lists.mydomain.com > - Venv > - Mailman core > - Mailman web (run migrate, collectstatic, compress, compilemessages) > Postorius > - gunicorn, hyperkitty > - Nginx > - SMTP exim4 conf > > I can see Posrorius and I have logged in and created my first mailing list: > > [image: Screenshot 2023-10-11 at 10.57.31 AM.png] > > My issue is that even though I have subscribed to my list as you can see > above, I am not receiving the confirmation email. I get a "recipients > refused" error. The smtp log for mailman is as follows: > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> recipients refused: > {' > kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for > <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > >\nUnrouteable > address\nSender verify failed')} > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> smtp to > testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 > seconds > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> post to > testlist(a)myproject.eu from > testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu, > 1667 bytes, 1 failures > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> delivery to > kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification failed > for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > >\nUnrouteable > address\nSender verify failed' > > I have used the configuration for exim that is here > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > > and > I have also tested with the alternative approach that is documented in > What do you have in the Exim's mainlog? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 7 months

[MM3-users] xapian db corruption - xapian.DatabaseCorruptError: Couldn't read enough (EOF) ??

by Odhiambo Washington

Today, my hourly cron job has generated an error and continues to do so every hour: ``` Subject: Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs hourly ``` Not sure what caused this. Perhaps a reboot when the cronjob hadn't completed? And a possible manual remedy would be to wipe the indexed db and let the cron run again? [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Couldn't read enough (EOF) (pid 85950): Couldn't read enough (EOF) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/haystack/management/commands/update_index.py", line 119, in do_update backend.update(index, current_qs, commit=commit) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 276, in update database = self._database(writable=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 1160, in _database database = xapian.WritableDatabase(self.path, xapian.DB_CREATE_OR_OPEN) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian/__init__.py", line 3743, in __init__ _xapian.WritableDatabase_swiginit(self, _xapian.new_WritableDatabase(*args)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xapian.DatabaseCorruptError: Couldn't read enough (EOF) Failed to update the fulltext index: Couldn't read enough (EOF) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/hyperkitty/lib/utils.py", line 179, in run_with_lock fn(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/hyperkitty/search_indexes.py", line 117, in update_index update_cmd.update_backend("hyperkitty", "default") File "/opt/mailman/mm/venv/lib/python3.11/site-packages/haystack/management/commands/update_index.py", line 342, in update_backend max_pk = do_update( ^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/haystack/management/commands/update_index.py", line 119, in do_update backend.update(index, current_qs, commit=commit) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 276, in update database = self._database(writable=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 1160, in _database database = xapian.WritableDatabase(self.path, xapian.DB_CREATE_OR_OPEN) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian/__init__.py", line 3743, in __init__ _xapian.WritableDatabase_swiginit(self, _xapian.new_WritableDatabase(*args)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xapian.DatabaseCorruptError: Couldn't read enough (EOF) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months, 1 week

[MM3-users] Re: Mailman 3 - Header Filter

by Mark Sapiro

On 9/25/23 06:30, Henrik Rasmussen wrote: > > In my case I would be more interested in holding or discarding mails with subject 'Out of Office' if the mail would otherewise be send the to the list members due to a non-moderated list. > > I would emagine that the order of "check for member moderation" and header_matches would not be significant if holding or discarding the mail due to header_matches, am I right? 🤞🏻 No. It depends on what the check for member moderation rule does. If the post is from a non-member or from a member and the members moderation is Default Processing or if it is List default and the list's Default action to take when a member posts to the list is Default Processing, then the Header Filters will be applied. However, if the post is from a member and the members moderation is directly or via list default any of Hold, Reject, Discard or Accept, that is the action that will be applied. > If so, I would think that Header "subject:" or "subject" with Pattern "^(?i)(.*)autosvar(.*)" - without the double quotes - and Function "Hold for moderation" or "Discard" should either hold or discard any message with "Autosvar" (danish word for "Out of Office reply") somewhere in the subject, but that doesn't happen. What is the correct syntax? Do not include the : in the header name. Other than that, your pattern should be OK but the ^, the (?i) and the parentheses around .* are all unnecessary. > *) In a prevous mail I was told that ^ would tell Mailman that it is a regex. That is true for lots of things where either a string value or a regexp is acceptable such as the * these nonmembers entries, but the Pattern entry for Header Filters is always a regexp and is searched with re.search with re.IGNORECASE, so while your pattern above should work, a much simpler pattern is just "autosvar" (w/o the quotes). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > Hi tried both. > > Same result. > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > Gecko/20100101 Firefox/60.0" And, you have verified that the files exist at `/opt/mailman/static` on your host? > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > Hi, > > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > > > I tried to do the same with Apache, but the statics files are not > > > delivered (404). > > ... > > > <VirtualHost *:80> > > > ServerName mailing.ddd.fr > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > <Location /static/> > > > Alias "/opt/mailman/static/" > > > </Location> > > > > > > <Location /> > > > ProxyPass http://localhost:8000/ > > > ProxyPassReverse http://localhost:8000/ > > > ProxyPreserveHost On > > > </Location> > > > </VirtualHost>/ > > > > > > In Apache, location > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > appropriate for resources in the file system. > > > > Try > > > > Alias /static/ /opt/mailman/static/ > > > > not within a location block. > > > > -- > > Mark Sapiro <mark(a)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 > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 12:32 AM, adam.heathcote(a)utas.edu.au wrote: > Hey there, > > We have a Mailman3 server with quite a few lists all running with no issues. > Recently I imported a list from our old Mailman 2 server which went fine. > > I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. > > The output of /opt/mailman/web/logs/mailmanweb.log is here: > > ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner > response = get_response(request) ... > TypeError: sequence item 1: expected str instance, NoneType found Was there more in the log? I.e., a line like The above exception was the direct cause of the following exception: followed by another traceback. If so, what was that? Is there anything in Mailman core's mailman.log? > I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? What do you get from Mailman's ``` mailman members -R owner your_list(a)your.domain ``` If this doesn't list you, try something like this: ``` $ mailman shell -l your_list(a)your.domain Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the your_list(a)your.domain mailing list >>> from mailman.app.membership import add_member >>> um = getUtility(IUserManager) >>> usr = um.get_user('adam.heathcote(a)utas.edu.au') >>> rr = RequestRecord(usr.preferred_address.email, usr.display_name, None) >>> add_member(m, rr, MemberRole.owner) >>> commit() >>> exit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] mailman3 not working for mailman21 lists

by blup＠fortytwo.ch

I installed mailman3 on a server where mailman21 was installed before. Newly created mailinglists work fine. But if I create mailinglists with a name that was previously used on mailman21 nothing works (same behaviour with and without import of old configs and archives; no logs). I purged all old mailman21 config and data and also old postfix aliases (or at least I do think so). If I send a mail to old list list1(a)a.b and new list list2(a)a.b I get the following logs /var/log/mail.log Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2(a)c.a.b>, orig_to=<list2(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1(a)c.a.b>, orig_to=<list1(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) /var/log/mailman3/smtp.log ug 21 22:17:40 2022 (934) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 21 22:17:40 2022 (934) Peer: ('127.0.0.1', 44746) Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) handling connection Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) sender: .... Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list2(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list2(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list1(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list1(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() Aug 21 22:17:46 2022 (936) <166111306097.933.1775779871266718007@...> smtp to list2(a)a.b for 1 recips, completed in 3.1437485218048096 seconds How can I get more info on why the mail for list1 isn't processed? Where could old mailman21 or postfix info on list1 be stored that causes mailman3 to not handle the list properly? How can I diff the config between list1 and list2 from the command line? Regards Diana

2 years, 9 months

[MM3-users] Newbie question 2: Rewriting issue for bounced emails

by William Oliver

I have installed mailman3 on a debian system with postfix and dovecot. I have gotten to the point that I can open the admin interface, set up domains and a mailinglist, and add users. I have subscribed two test users, one on the server and one on a different machine. Both got the confirmation email requests and the welcome messages. However, when I try to sent an email *to* the list from either account, I get the following error: This is the mail system at host mail.libertyfp.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <"lmtp:[mail.libertyfp.org]:8024"@libertyfp.org> (expanded from <fplist(a)libertyfp.org>): unknown user: "lmtp:[mail.libertyfp.org]:8024@libertyfp.org" Apparently, fplist(a)libertyfp.org is getting rewritten to 8024(a)libertyfp.org. The only place where I have that number (that I know of) as a configuration is in mailman.cfg, where I have: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.libertyfp.org lmtp_port: 8024 smtp_host: mail.libertyfp.org smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no Here's the last little bit of /etc/postfix/main.cf: # add to the end (add virtual users) # if specify multiple domains, specify comma or space separated virtual_mailbox_domains = libertyfp.org virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 # mailman3 changes owner_request_special = no always_add_missing_headers = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp #local_recipient_maps = # hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp header_checks = regexp:/etc/postfix/header_checks Here's the bit in /etc/postfix/ mailman3 unix - - - - - lmtp -o lmtp_send_xforward_command=yes -o disable_dns_lookups=yes I don't think I have any mailman3 changes in /etc/dovecot/dovecot.conf Once again, any help would be appreciated. billo

3 years, 5 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/14/22 08:21, Stephen J. Turnbull wrote: > Yes. The C-T-E on all the multipart parts was quoted-printable, not > allowed under RFC 2045. That's what I expected (we're talking about Apple Mail), but thanks for confirming. > The Python email library says the message is defective. Mailman's lmtp > runner in turn rejects the defective message with a 501 status > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… > > It could accept a defective message or one with specific defects, but > this is problematic for further processing. For example, at least one > MUA, Thunderbird, renders such a message with an empty body. Sure, but that's not our problem. I mean, I have my MUA set to ignore HTML so I get empty bodies all the time! :-) We are perfectly within our rights to just let the Apple Mail and Thunderbird users fight about it. :-) If it causes problems for *our* processing, that's another matter. I don't see why it would, though. Whether we *want* to do that depends on how much trouble that causes for our main constituency (list and site admins), and whether we can provide discoverable documentation of the problem. My take is that this seems to be an extremely rare problem, and at least some MUAs are able to read the message, so we should let it through. If we wanted to be really obnoxious, we could add a header to the message This message does not conform to mail standards. Some clients may omit some or all of the content. Or we could make passing it an option, perhaps as a pseudo-content type in "Pass these content types" or as a separate option. I feel strongly enough that Postel implies "let it through" that I'll write up a PR shortly (a few days). Sleep on it, we bring in Abhilash and I guess Barry?, and if you all still don't like it, veto it -- my time is no big deal, it'll only be an hour to put it together I think. Steve

3 years, 1 month

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS While I'm tracing the problem out, this is the configuration I had working and the error it shows after upgrade: <------- snip of settings.py> # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression #### activo compresion 18/12/20 COMPRESS_OFFLINE = True ###COMPRESS_OFFLINE = False <---------- end snip> And below is the error it shows: /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" Traceback (most recent call last): File "/usr/local/mailman3/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. -- ___________________________________________ 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, 7 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

After making that change and doing some testing. So far I’ve not had any issues and the sync are working as expected now. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 2 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, as the original poster, I have asked the user to send a test mail through our mailman3 system (docker image maxking/mailman-core:0.4.2) and the mail passed. The user is now on Apple Mail 16, maybe that does the trick. Please find enclosed the anonymizied mail source. Best regards and thanks for caring even if the problems seems to affect only a small number of users! Rainer On Fr, 15 Apr 2022 09:03:41 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/14/22 21:33, Stephen J. Turnbull wrote: >> >> Whether we *want* to do that depends on how much trouble that causes >> for our main constituency (list and site admins), and whether we can >> provide discoverable documentation of the problem. My take is that >> this seems to be an extremely rare problem, and at least some MUAs >>are >> able to read the message, so we should let it through. > >First, we are not silently dropping this message. We are rejecting it >at LMTP time so the sender should be notified. > > Then the broader question is should we accept all messages with >defects, almost all of which are spam, or only certain defects and >which ones. > > I note that Apple has now released Mail 16 so maybe they've fixed >this. My macs are still on Big Sur, so I can't test this. > > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years, 1 month

[MM3-users] Re: Help with fresh debian install

by Mark Dadgar

Thanks for the al the help - much appreciated! Mailman3 is a HUGE step up from 2.1.x. Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin. I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: www-data@mail:/tmp$ python /usr/share/mailman3-web/manage.py hyperkitty_import -l trackjunkies(a)pdc-racing.net /backups/trackjunkies.mbox Importing from mbox file /backups/trackjunkies.mbox to trackjunkies(a)pdc-racing.net Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. Any thoughts on how I can re-run the full import to make sure that all the archives are present? Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878 > On Oct 3, 2019, at 9:25 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> >> I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. >> >> Importing lists from 2.1 has been a real problem. >> >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> File "/usr/bin/mailman", line 11, in <module> >> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() >> File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main >> initialize(config_path) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize >> initialize_2(propagate_logs=propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 >> mailman.core.logging.initialize(propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize >> _init_logger(propagate, sub_name, log, logger_config) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger >> handler = ReopenableFileHandler(sub_name, path_abs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ >> self._stream = self._open() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open >> return codecs.open(self.filename, 'a', 'utf-8') >> File "/usr/lib/python3.6/codecs.py", line 897, in open >> file = builtins.open(filename, mode, buffering) >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. > > >> Error in atexit._run_exitfuncs: >> Traceback (most recent call last): >> File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown >> h.flush() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush >> if self._stream: >> AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' > > > This is due to the prior permissions error. > >> If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: > > > If there are a lot of members to add, that can take a long time. The > current version of import21 has a progress thermometer for this. > >> — >> Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 >> Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' >> Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration >> msg, msgdata = self.switchboard.dequeue(filebase) >> File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue >> with open(filename, 'rb') as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > > First, I don't know what these messages are. Normally import21 doesn't > send any mail. I'm guessing it's trying to send 'you are subscribed' > notices to the users, but it shouldn't be doing this. > > All these files should wind up in Mailman's var/queue/bad/ directory > with a .psv extension. You should be able to examine them with the > 'mailman qfile' command. > > Whatever they are, the error comes from virgin runner so import21 should > have actually succeeded. Did it import the list? > > >> It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? > > > It makes a weak effort at converting the list's msg_footer and > digest_footer into MM 3 templates in > templates/list/<list-id>/<list-lang>/. These are owned by root in your > case because you ran import21 as root. > > >> Any thoughts on what’s going wrong here? > > > It looks like this may be an issue with the Debian package, at least the > sending of messages part. > > As for the rest, the Debian package should install stuff as a Mailman > user, perhaps 'mailman' or 'list', and you should be running all > commands as that user. > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 8 months

[MM3-users] Bounce of HCL Notes invitations - CloseBoundaryNotFoundDefect() - 501 Message has defects (in reply to end of DATA command)

by Stephen J. Turnbull

Ulf R. writes: > >>> msg.defects > [CloseBoundaryNotFoundDefect()] This means that the message declares a MIME multipart Content-Type, and some part had a "start" boundary line but no "end" boundary line. > Is there a quick fix for this available? No. If the sending software isn't quite broken, this defect means that a chunk of the message was lost somewhere. Ignoring this kind of defect is obviously a bad idea, and any other fix (on the Mailman side) requires knowing precisely what's causing the defect to be detected. > Is it a problem of the python code or the format of the HCL Notes > Server? Nothing's impossible, but I would bet that the problem is in the HCL Notes format. The MIME multipart spec goes back to the early 1980s, and I'm sure the Python Email package implements it exactly by default. I can't say more without the exact MIME structure of a message that causes this error, preferably the whole message (header and body). That said, it might be something that (a) can be worked around with a slightly more lenient existing email policy, or (b) that we could create a new policy that ignores the problem. > In the .eml file I see 25 header fields calles "X-Notes-Item". May > be it is an overflow? Extremely unlikely. All header fields have been successfully processed by the time a CloseBoundaryNotFoundDefect can be detected, and the copy of the field you provide in your followup email is well-formed and contains no interesting content (such as non-ASCII characters, even after decoding the MIME-words). I cannot say why removing the first instance of the field would resolve the error without seeing the whole message. > Any ideas? Not without the full message. If you're not comfortable sending the message to the list, but do trust us enough, you can send a message that causes the error to me and/or Mark Sapiro <mark(a)msapiro.net>. Regards, Steve

2 months, 2 weeks

[MM3-users] Re: User management page [was: Changing subscription address]

by Stephen J. Turnbull

Abhilash Raj writes: > Typo :( Page in Postorius is what I meant to say. :D No problemo, mon, I just did it too -> > Is that necessarily required? Every user in Django has a corresponding > user in Core, but the converse isn’t true and I am not sure if that is even > required. I meant "accessed from Postorius or HyperKitty." :-) > You will be able to see: > - Does the user have a Django account? > - All Subscriptions for the User > - All addresses of the User > > You will be able to perform following actions: > - Add or remove a user’s address > - Verify or un-verify an address > - Set any address as primary for the user > - Update display name of the user > - Update address on any of the subscriptions I don't think we *need* a Django account for what I'm thinking of. I do think that creating the account on User access from Postorius might make the implementation logic simpler. > What I am on fence about: > - Provide a full blown preferences menu to the admin for that user. This > will also make the UI extremely complex to see and implement. Wait to decide on that until I have a mockup or maybe a full MR. > But, when you have an account in Django with a different email > (email2) and a different Mailman user (user2) and you add a second > email (email1) to your account and are able to prove ownership by > verifying the address, Django will ask Core to add that second address > (email1) to your Mailman user (user2) and absorb “user1”. This > process is already implemented. Good. > However, if two Django accounts are created for “user1” and “user2” > then situation becomes more tricky and currently we don’t have a > way to resolve that short of delete one of the accounts and add the > addresses to other account. Delete "that" and add its attributes to "this" is what I had in mind. Again, thanks for explaining the existing logic. Steve

4 years, 2 months

[MM3-users] Re: mailman_web/urls.py changes in Postorius 1.3.10

by Mark Sapiro

On 12/5/23 09:52, Lieuallen, Thomas Otis wrote: > The latest release of Postorius includes these lines in mailman_web/urls.py: > > > # Include alternate Postorius and HyperKitty URLs. > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > > It appears that these paths override the originals (/mailman3 & /archive). They were intended as optional additions, but it appears they do function as overrides for some purposes. > I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. This is apparently a side effect of this change that wasn't considered in making the change. The change was made because some docs and/or example projects used the /postorius and /hyperkitty URLs and some used the /mailman3 and /archives URLs. This was an attempt to make either set work. > If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). > > Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. > > One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? It was intended to just add the /postorius and /hyperkitty URLs as alternates. I had assumed the links on various pages would reflect the URL used to access the page, but this is apparently wrong. I could change the order of the path lines in the distributed urls.py, but at this point it just may cause more confusion. However, since the sample config at https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… shows only the /mailman3 and /archives URLs, I will change the order. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Rejecting held emails

by Darren Smith

Mark, You're quite right, I meant Discard. Thanks for the clarification. I hope to be able to pull a fix in for this in the near future. :) -Darren On Thu, Apr 26, 2018 at 10:14 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/26/2018 08:43 AM, Darren Smith wrote: > > > > We recently had a phishing message make it through our spam filters and > > arrive at a mailing list. The good news is that since it was not from a > > list member it was in the held message queue. > > > > I was able to find the message in the var/messages directory by searching > > for a keyword in the subject. However, after rejecting the message from > > Postorius, the message doesn't seem to be removed from the var/messages > > directory. > > > Do you mean Reject and not Discard? Phishing/Spam should never be > "rejected" for backscatter reasons. Reject should only be used for > somehow inappropriate posts from known people. > > > > Is this expected behavior? I know that infosec people won't be too happy > > about a phishing email sitting around on our disk. (Infosec guys are > > notoriously paranoid. :) ) > > > > Is there some sort of cleanup process that would remove these messages? > If > > not, does this pose an issue where over time disk usage will creep up? > This > > could be a pretty significant problem if that is the case. > > > It's not the behavior I would "expect", but it is the way it currently > works, and yes, all your concerns are valid. This is > <https://gitlab.com/mailman/mailman/issues/257> which I just edited to > note that in addition to not removing the pending db entry, the message > isn't removed either. > > -- > Mark Sapiro <mark(a)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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 1 month

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Kelly Close

Thanks for those clarifications Mark. -- K. Kelly Close, P. E. Senior Project Manager | Water Rights Engineer | Technology Team Lead Office: 303-455-9589 Direct: 303-867-7665 Kelly.Close(a)LREwater.com LREWATER.COM 1221 Auraria Parkway Denver, CO 80204 **CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you. On Tue, Jun 16, 2020, 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > > I resolved this myself with a search that turned up a 2018 post from > Mark that suggested typing "mailman aliases" to create the > hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where > they are on Ubuntu 18.04). I looked in that folder and sure enough it was > empty so I typed "sudo mailman aliases" which did indeed create the 4 > things that needed to be there: > > postfix_domans > > postfix_domains.db > > postfix_lmtp > > postfix_lmtp.db > > > > But, they were owned by root:root and everything else under that > /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the > ownership on the 4 files to list:list. > > Because that's how you ran it. Run > > sudo -u list mailman aliases. > > > > Seems to have worked! I was perplexed about why I had to do this though > because these were created automatically last time I did this, but I > figured that out too. > > > Current `mailman start` should create the aliases. > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 11 months

[MM3-users] Re: Handling of (un)subscribe mails for already (un)subscribed users

by Mark Sapiro

On 12/10/20 11:51 AM, Andreas Barth wrote: > Hi, > > I noticed that a mail to -subscribe for an already subscribed user > doesn't get any response (about line 225 in > mailman/src/mailman/app/subscriptions.py). Same but different for > unsubscribe for users not on the list. I tested and I see this, so there is a bug, but I don't know what the issue is. The code you point to should raise AlreadySubscribedError and <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> should catch it and report, but this doesn't seem to be happening.. Also, <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m…> should report an attempt to unsubscribe a non-member, but the issue here is <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/comman…> which supresses sending the response because it is redundant if the user gets a 'you have been removed' email, but in this case there isn't one. > I'd need these kind of mails however in hope that users complain less. > > Would that be generally interessting, and if so, any special > requirements for submitting patches, or should I just do that locally? These things should be fixed, but it's more involved than just a patch to fix the error. For all but trivial fixes, the workflow should be something along the lines of the following. There should be an issue on GitLab for the appropriate project; in this case at <https://gitlab.com/mailman/mailman/-/issues>. Then to develop a fix, there needs to be a fix, a test for the fixed code and a note in the NEWS.rst file about the fix. I generally prefer to start with a local clone of the GitLab branch and first create a test for the desired behavior. This test should fail. Then I create the fix, and now the test should pass. Finally, I create the NEWS item and commit those changes and create a merge request. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Mark Dadgar

On Nov 4, 2021, at 3:05 PM, Andreas Barth <aba(a)ayous.org> wrote: > * Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: >> >> >> --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro >> <mark(a)msapiro.net> wrote: >> >>> On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >>>> >>>> My conclusion: >>>> I ask you to consider these experiences in an update for the mailman3 >>>> packages in debian bullseye. It would save time, questions and nerves. >>> >>> >>> Issues with Debian packaging should be directed to Debian. >> >> Or as previously discussed, the debian packages should be avoided entirely. > > I strongly disagree with that statement. > > Distribution packages have their own up- and downsides. Of course, how > they are done is to be discussed with the distribution, so: if > something is wrong with a debian package, please follow the > instructions on bugs.debian.org on reporting bugs. > > However, they have the advantage that they're integrated with the > distribution. They have the disadvantage that they're stable for some > time - that is why it's called a stable release. If they have all the > features someone wants, they usually work fine (and my first > mm3-installation was the default debian package). If one looks for > bleeding edge, of course that's not what one can expect from a > distribution package - but that's also a feature. You left out the fact that the distro edition of mailman3 has very poor support because Debian doesn’t know how to do it and the setup is different enough from vanilla that this community has a hard time supporting it as well. You can certainly try to run it, but I’m willing to bet that you’ll regret it. Having tried it myself, I can’t in good conscience recommend it to anyone. The bottom line is that, IMHO, distro works great for fairly mature projects. MM3 isn’t that yet. YMMV, my $0.02, you get what you pay for, etc. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 7 months

[MM3-users] Re: Sending to mangled 'From' addresses.

by Mark Sapiro

On 5/31/24 22:23, hansen via Mailman-users wrote: > > Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. DMARC mitigation action ‘Replace From: with list address’ will also place the poster's address in Reply-To: (or Cc: depending on list configuration), so a simple `reply` from a reasonable MUA should go just to the poster. > For example, say the mail client captures my address as > > “Allan Hansen via <listname>” <listaddress> > > then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: > > “Allan Hansen via <listname>” > > and, to make it worse, the actual email address, <listaddress>, is often hidden. If this is the result of a `reply` and not `reply-all` the client is not behaving reasonably. > The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. That is a problem with the client, but I suppose such clients are not uncommon. > Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., > > "Allan Hansen via <listname>" You could add a header filter on the To header with a regexp like `^.*via <listname>` and the desired action. > Should I get onto the other list to request this as an enhancement? I don't think that's necessary in this case, as Header filters should do it. In general, the best way to request an enhancement is to file an issue with the appropriate GitLab project at `https://gitlab.com/mailman` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Hyperkitty configuration

by Odhiambo Washington

On Fri, Nov 22, 2024 at 12:16 AM Alain D D Williams <addw(a)phcomp.co.uk> wrote: > Well, I have finally got it to archive something. > > One simple thing that tripped me up was the ARCHIVER_KEY > > • mailman-hyperkitty.cfg says: > > # The shared api_key, must be identical except for quoting to the value of > # MAILMAN_ARCHIVER_KEY in HyperKitty's settings. > api_key: SecretArchiverAPIKey > > Which is confusing as it is referring to "# Mailman API credentials" in the > file mailman-web.py > > • mailman-web.py says: > > MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' > > It would be good if the lines in mailman-web.py were: > > # The value below is the same as api_key in mailman-hyperkitty.cfg except > that the value here has quotes round it > MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' > > And the lines in mailman-hyperkitty.cfg were: > > # The shared api_key, must be identical except for quoting to the value of > # MAILMAN_ARCHIVER_KEY in HyperKitty's settings (mailman-web.py) > # The value here does not have quotes > api_key: SecretArchiverAPIKey > > > And if you want to be really nice check if the api_key value is enclosed in > quotes and generate a message if so. > The official and supported documentation for installing MM3 doesn't speak anything about mailman-web.py. It is here: https://docs.mailman3.org/en/latest/install/virtualenv.html On this platform, the rule is - IF you don't use the documentation above, then your primary support is your distro's packagers. The official documentation speaks of only 3 files: settings.py, mailman.cf and mailman-hyperkitty.cf (IIRC) and the "quoted here", not quoted there, is something that I remember as referring to mailman-hyperkitty.cfg and settings.py. Those who prefer not to lose hair scratching their heads do follow https://docs.mailman3.org/en/latest/install/virtualenv.html. It doesn't address everything, but it's quite close. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

6 months, 2 weeks

[MM3-users] How to store additional information about lists?

by Stephen J. Turnbull

Andreas Barth writes: > I need to add custom attributes to the mailing lists: It's a rather different use case, but Systers Mailman contains extensive modifications including Systers-specific attributes. Might be a useful example (although I don't know how recently they've merged from mainline. ISTR the last time this came up the Systers repo had moved and it wasn't clear where. Try a quick Google and if no joy, I can probably put you in touch with somebody who has a clone. > Enhance the boolean public to a tri-state: public, restricted audience > and private (restricted audience means: some people could subscribe > themself I'm not sure tri-state is a good idea. The boolean public controls visibility of the list in listinfo pages. I'm not sure if combining that with who-can-subscribe logic is safe, and there are pending RFEs to change the visibility logic, which might cause you annoyance at upgrade. I also am not sure it's a *bad* idea :-), although I suspect if we were to add the feature to our distribution, we'd probably implement as a per-list check for permission (this could be a list of Users, a list of Addresses, or a function to be called with one or the other). > - of course this could also be implemented as a second boolean that > e.g. splits "not public" into "restricted audience" and "private" > (means: nothing goes wrong for code that doesn't know this > difference). Exactly my concern. > Any hints how to do that best? Is it possible to store custom > attributes, or should that be stored elsewhere? No, I don't think there's provision for custom attributes in core. Of course you could change the database schema, but you'd have to provide a migration for that. Migrations for somebody else's custom attributes being a hard thing to automate on our side, we don't provide for them. Does this need to be implemented in core (eg, because restricted audience users would subscribe by mail), or could you get away with a modification to Postorius only?

4 years

[MM3-users] Re: Mailman Core 3.2.2 is now out

by Abhilash Raj

Danil Smirnov wrote: > Hi Abhilash, > > Docker builds are failing for the last few days so we don't have this > update in the images: > https://circleci.com/gh/maxking/docker-mailman/tree/master > > Could you look at the issue please? I fixed the daily builds and am currently pushing a new release with updated versions of Core, Postorius and Hyperkitty's releases. > > Best regards, > Danil Smirnov > > вс, 24 мар. 2019 г. в 07:59, Abhilash Raj <maxking(a)asynchronous.in>: > > > Hello Everyone, > > > > Mailman Core 3.2.2 is released and available on PyPI[1]. > > > > This is a regular bugfix release and I had to do that to fix a version > > constraint > > which pulled in a pre-release of a dependency (falcon) when installed via > > pip > > and caused the default install to break. > > > > There are few other changes included in this release, including a big > > refactor > > of error reporting in Core's REST API. All the error responses are now > > correctly > > formatted as JSON with more information about the error. For example, > > invalid > > inputs for Enum data types return the valid options. Other error message > > are > > now generated from the input validtor and will be more informative. > > > > REST API also accepts input as JSON formatted body, alongside the > > x-www-form-urlencoded. > > > > A full list of changes are available here: > > > > > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 > > > > This release supports Python 3.5-3.7. > > > > Thanks very much to all the contributors involved in this release. > > > > > > [1]: https://pypi.org/project/mailman/ > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > 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/ > >

6 years, 1 month

[MM3-users] How to increase maximum size of the message in mailman

by Stephen J. Turnbull

Shashikanth Komandoor writes: > But the /var/log/maillog says the below error during the above > hand shake. > > *status=bounced (host 0.0.0.0[0.0.0.0] said: 552 Error: Too much mail data* > > I have browsed google for understanding and fixing the issue. > During which I encountered the information given by Mr. Mark Sapio at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…. > But I could not fix the issue as it is mentioned the default size > limit is 33554432. There's no way to configure the LMTP server's message_size_limit in Mailman; this is a bug but I can't say when it will be fixed. In mailman/src/mailman/runners/lmtp.py, class LMTPController, if you edit the line server = LMTP(self.handler) to server = LMTP(self.handler, data_size_limit=100_000_000) it should have the desired effect. (I think that if as suggested by your post you're using Python 3.6, you'll have to remove the underscores from "100_000_000"; that feature was added in 3.7.) Unfortunately, any time you upgrade Mailman you'll have to edit it again (that's why I say this is a bug). I do not understand why the approach you used of editing DATA_SIZE_DEFAULT in aiosmtpd/smtp.py didn't work. The only thing I can imagine is that you have multiple Python installations and the one you edited is not the one that Mailman is currently using, or the same issue for multiple Mailman installations each with their own venvs or whatever. You also will have to configure Mailman. If you haven't done so already, the procedure is 1. Sign into Postorius as owner of the list, 2. click on the tab "Settings" in the middle of the header under the name of the list, 3. click on "Message Acceptance" in the sidebar at the left, and 4. set "Maximum message size" to 100000 (kb; no commas or periods). Unlike the LMTP size setting above, this configuration will persist across Mailman upgrades. > Also, please also let me know if there is any limitation specific > for the attachments so that I can customize that too respectively. No. Steve

3 years, 9 months

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by Mark Sapiro

On 11/8/23 14:47, gordon(a)dickens.com wrote: > > Basically, it does not appear that mailman nor the runners are active and rebooting does not help. "/opt/mailman/venv/bin/mailman start" generates errors as follows: > >> Traceback (most recent call last): >> File "/opt/mailman/venv/bin/mailman", line 6, in <module> >> from pkg_resources import load_entry_point >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3248, in <module> >> @_call_aside >> ^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3223, in _call_aside >> f(*args, **kwargs) >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 3261, in _initialize_master_working_set >> working_set = WorkingSet._build_master() >> ^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 617, in _build_master >> ws.require(__requires__) >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 956, in require >> needed = self.resolve(parse_requirements(requirements)) >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 815, in resolve >> dist = self._resolve_dist( >> ^^^^^^^^^^^^^^^^^^^ >> File "/opt/mailman/venv/lib/python3.11/site-packages/pkg_resources/__init__.py", line 856, in _resolve_dist >> raise DistributionNotFound(req, requirers) >> pkg_resources.DistributionNotFound: The 'mailman==3.3.5' distribution was not found and is required by the application First of all, when running /opt/mailman/venv/bin/mailman you need to specify the -C option with the path to mailman.cfg, i.e. ``` /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg start ``` Can you run the mailman command without a subcommand. I.e. ``` /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg ``` should just produce a list of subcommands. Does it do that or produce the same error as above? I don't understand the above error. I think the content of /opt/mailman/venv/bin/mailman should be ``` #!/opt/mailman/venv/bin/python # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) ``` Which doesn't correlate with the above traceback. What is yours? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Migrating Mailman 3 lists

by Abhilash Raj

On Mon, Apr 27, 2020, at 9:05 AM, Andrew Hodgson wrote: > Brian Carpenter wrote: > > >I know how to migrate mailman 2 lists to a new mailman 3 server. However I do not know how to migrate a mailman 3 list from one mailman 3 server to another one. Are there any instructions or protocol on how to accomplish this? >The Mailman 3 server I want to migrate *from* was setup using Docker. The Mailman 3 server I want to migrate these lists *to* was setup using a python virtual environment via pip. > > I did this the other week, the difference I think we've got here is > that I migrated the whole instance (Mailman Core's var files plus > complete Postgresql database) over to the new server rather than trying > to add the lists to an existing setup, which I couldn't work out either > which is what prompted me to complete the server migration before > adding more lists. > > The only issue I ran into was not copying the Mailman Core var files to > the new server, this actually gave me a bit of trouble later on as > firstly Mailman doesn't create the lists directory which is what I was > checking with Exim for list existence, and also I had an issue where I > was missing a moderated message from the messages directory which > stopped the admin interface from displaying for that list. var/ directory does store some state for Mailman, specifically queued messages. Optionally, also templates. Directory structure is something that could be fixed with this issue[1], but given that the messages are still stored on the filesystem instead of database, you'd need to move var/ directory too. It might help to document the process somewhere. I'll create a bug report. [1]: https://gitlab.com/mailman/mailman/-/issues/699 > > However if anything would help on my experience would be happy to share > more info. > > Andrew. > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Monthly Password Reminders

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:05 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > On Thu, Feb 2, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 2/2/23 06:29, Odhiambo Washington wrote: > > > > Does MM3 send these monthly subscription reminders the way MM2 used > to > > > do? > > > > I am looking for the setting, but can't find that in the list > settings. > > > > > > No, it does not. > > > > The rationale behind the decision to toss away that feature? Security?? > > For the passwords, yes. It was frequently reported as a bug, in fact. > Mostly the reminders generate requests to know how to shut them off. > You're the first in probably a decade who's asked how to turn them on! > It's because I only recently migrated to MM3 after watching from the periphery for years :) I have been on MM2, and even there I disabled it. I was just curious. While in theory we could protect in transit with SMTP over TLS, we > can't guarantee end-to-end encryption (eg, if there's a .forward at > the subscribed address), and while TLS is widely implemented, it's > still not universal. And there's no way to protect unencrypted email > from admins at the receiving host. Receiving encrypted email is > pretty much not implemented at all, except in some specialized > communities. Also, now that passwords (if they're used) are > attributes of Users who may have several Addresses and worse, they may > have admin privileges. So Mailman 3 passwords are generally higher > value than in Mailman 2. > > I can imagine a use for the list of subscriptions part that a few > users might like, but most folks would prefer not to get another > regular mailing. > > Steve > That makes complete sense, and I am satisfied with the decision. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: MM3 installation recommendation: Docker or individual components?

by Abhilash Raj

On Sat, Jul 28, 2018, at 7:47 AM, Tom Browder wrote: > I want to install MM3 on a virgin host running Debian 9. I want to minimize > problems as bugs are fixed and necessary upgrades are published. > > I will use PostgreSQL, nginx, and Postfix, and am reasonably competent > runnng my own remote server (full control, hard iron server, not virtual). > The host will only serve mail to the public and nothing else (no websites, > no other users). I did run a successful MM2 site (thanks to Mark’s copious > and gracious help!) for a couple of years from 2011 to 2013, so I’m no > stranger to some of the MM3 jargon. > > I have been running Apache 2.4+ with 10+ virtual https websites since 2010. > I use Letsencrypt certificates for all of them. > > I have no experience with Docker, Django, or nginx. > > Should I choose the Docker method or individual compnent installation? > > I realize this is an open ended and very subjective request, but I would > appreciate any advice. I'd recommend using the system packages for Debian/Ubuntu. I am not sure if Debian already has 3.2 release, but it should be available soon. Docker based deployments are easy if you are comfortable using Docker or similar technologies for deployments. For past few releases, I find them to be quite stable and administration is very similar except a few networking related setup. Finally, if you want to be running at the bleeding-edge, getting the bug fixes the day they are done, you can install from source using a virtual environment. We (mailman developers) do it for a few of the lists that we run (like this one), but if your service is going to be critical, I'd recommend against it. Although, rolling back after a bad update shouldn't be harder than `git co HEAD~` :) Not sure I can give more advice than this, but there is documentation for Docker images[1] and setting up using virtual environment[2] is available. [1]: https://github.com/maxking/docker-mailman/blob/master/README.md [2]: http://docs.mailman3.org/en/latest/prodsetup.html -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 12, 2020, at 3:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/12/20 3:02 PM, Mark Dadgar wrote: >> >> The second patch did not work either. Ahh, well. > > > I think you need to do something like this: > > $ mm/bin/django-admin shell > Python 3.7.1 (default, Dec 14 2018, 13:17:01) > [GCC 5.4.0 20160609] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email >>>> emails = Email.objects.all() >>>> for email in emails: > ... if email.content.find('\u200b'*5) >= 0: > ... print('Found in ml {}, hash {}'.format( > ... email.mailinglist.name, > ... email.message_id_hash)) > ... >>>> _NAME/message/HASH/ Finally getting around to looking into this now that I’ve migrated from sqlite3 to postgres (writeup on that coming soon for the archives). Here’s what I get when I attempt the above commands: root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email Traceback (most recent call last): File "/usr/lib/python3.8/code.py", line 90, in runcode exec(code, self.locals) File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/hyperkitty/models/__init__.py", line 25, in <module> from .category import ThreadCategory File "/usr/lib/python3/dist-packages/hyperkitty/models/category.py", line 61, in <module> class ThreadCategory(models.Model): File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 103, in __new__ app_config = apps.get_containing_app_config(module) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 252, in get_containing_app_config self.check_apps_ready() File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 134, in check_apps_ready settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. >>> I am in no way a django expert. Thoughts? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

[MM3-users] Re: spf/dkim/dmarc

by Odhiambo Washington

On Fri, May 19, 2023 at 7:09 PM Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > Using https://www.spf-record.com/ I have checked my SPF records which are > reported as 'SPF check passed'. My DKIM also passes various test suites. > Yet, Google is still rejecting mailman messages to any and all gmail users. > I have even filled out their short form for delisting at > https://support.google.com/mail/contact/bulk_send_new all to no avail. > Example of block logfile message: > > May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: > to=<billb6951(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, > delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host > gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM > domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard > fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: > [192.46.218.224]. To best protect our users from spam and 550-5.7.26 > phishing, the message has been blocked. Please visit 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for more 550 > 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - > gsmtp (in reply to end of DATA command)) > > Could the hard fail policy be implicated in the gmail rejection? > > Other than readdressing my server, is there anything else I can do? > Kindly use some sane MUA and try and learn how to hit the reply button. Having said that, here is a test for SPF records for my MM3 domain, versus a test for yours: ``` [19:26 ~ ]$ dig +short lists.kictanet.or.ke txt "v=spf1 a mx ip4:41.212.32.14 -all" [19:26 ~ ]$ dig +short lists.ccalternatives.org txt "v=spf1 -all" ``` I have never seen an empty SPF record before. Yours is the first one I am seeing. I suppose there is something amiss with your SPF record, but I am not even sure. Can you please head to: http://www.appmaildev.com/ Run the SPF and DKIM tests and share the results here so that we can also see. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years

[MM3-users] Run a mailman program outside of mailman shell

by Greg Newby

Hi again folks. I have hundreds of lists to convert from MM2.1 to MM3, and intend to write a Python program do this this rather than running commands in mailman shell (and rather than running 'command()' functions in mailman shell, if possible). However, when I write a simple Python program to run the types of commands found in the Mailman docs, such as these <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>, I get errors. This is a venv installation, following these instructions <https://docs.mailman3.org/en/latest/install/virtualenv.html>. The Mailman3 installation is working fine and I have a handful of lists in production that I set up manually. Here's a very simple program, import-try1.py, just to create a list: #!/opt/mailman/venv/bin/python3 from mailman.app.lifecycle import create_list l = create_list('testlist2(a)lists.aaabbb.org') Here's the output I get (yes, the domain exists and already has lists - I'm putting aaabbb instead of the actual domain name): ./import-try1.py Traceback (most recent call last): File "/opt/mailman/./import-try1.py", line 4, in <module> l = create_list('testlist2(a)lists.aaabbb.org') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 74, in create_list getUtility(IEmailValidator).validate(fqdn_listname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 180, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.address.IEmailValidator>, '') I get different errors with other sets of commands. The same commands work fine from `mailman shell`, i.e., (venv) mailman@mail:~$ mailman shell Welcome to the GNU Mailman3 shell on aaabbb.org >>> from mailman.app.lifecycle import create_list >>> l = create_list('testlist2(a)lists.aaabbb.org') >>> Output from mailman info, with the passwords omitted: GNU Mailman 3.3.9 (Tom Sawyer) Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:secretaaabbb@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:reallysecretaaabbb I suspect I just need to either change the interpreter (1st line of my program), or find the correct 'import' lines (I've tried numerous variations; the above is the simplest example). Help will be appreciated! Greg

10 months, 2 weeks

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:11 PM, David Newman wrote: > On 1/14/22 4:54 PM, Mark Sapiro wrote: >> >> It should work. I suspect you need to go to the list's Settings -> >> Automatic Responses and set `Admin immed notify` to Yes. > > > It's enabled. I think this triggers notifications only for new > subscription requests, not pending ones. Yes. That will send a single notification at the time of the request using the `list:admin:action:subscribe.txt` template. Notices of pending requests are sent by the `mailman notify` command using the `list:admin:notice:pending.txt` template. ... >> You can test `mailman notify` at any time by running it by hand. > > > Thanks. This still isn't working as intended. I took these steps: > > 1. Created the file > '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' The template name is `list:admin:notice:pending.txt`, not `list:admin:action:pending.txt`. Thats why it didn't work. ... > 2. Restarted the mailman3 and mailmanweb services You only needed to restart Mailman core. ... > What I'm trying to do here is replicate a feature from MM2.1, where > pending notifications had URLs embedded in the message. That's not > available out of the box in MM3, and if there's a place for feature > requests I'd be glad to ask that this be made the default. The place for feature requests for Mailman core (which this is) is https://gitlab.com/mailman/mailman/-/issues, however, this is not straightforward as Mailman core doesn't know if you even have Postorius or some other web management UI installed or what the URL to access it might be. Thus it's not just a simple matter of editing templates. It would also require a configuration setting for the base URL for the web admin UI and changes in logic to provide an appropriate replacement depending on whether or not the base URL was configured. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, Not a very good response. (venv) mailman@new-server ~ (v3.3.9) [0|1]> mailman-web check postorius Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 158, in get_app_config return self.app_configs[app_label] KeyError: 'postorius' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in handle app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in <listcomp> app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 165, in get_app_config raise LookupError(message) LookupError: No installed app with label 'postorius'. (venv) mailman@new-server ~ (v3.3.9) [0|1]> mailman-web check hyperkitty Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 158, in get_app_config return self.app_configs[app_label] KeyError: 'hyperkitty' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in handle app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in <listcomp> app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 165, in get_app_config raise LookupError(message) LookupError: No installed app with label 'hyperkitty'. (venv) mailman@new-server ~ (v3.3.9) [0|1]> mailman-web migrate -h usage: mailman-web migrate [-h] [--noinput] [--database DATABASE] [--fake] [--fake-initial] [--plan] [--run-syncdb] [--check] [--prune] [--version] [-v {0,1,2,3}] [--settings SETTINGS] [--pythonpath PYTHONPATH] [--traceback] [--no-color] [--force-color] [--skip-checks] [app_label] [migration_name] Updates database schema. Manages both apps with migrations and those without. positional arguments: app_label App label of an application to synchronize the state. migration_name Database state will be brought to the state after that migration. Use the name "zero" to unapply all migrations. options: -h, --help show this help message and exit --noinput, --no-input Tells Django to NOT prompt the user for input of any kind. --database DATABASE Nominates a database to synchronize. Defaults to the "default" database. --fake Mark migrations as run without actually running them. --fake-initial Detect if tables already exist and fake-apply initial migrations if so. Make sure that the current database schema matches your initial migration before using this flag. Django will only check for an existing table name. --plan Shows a list of the migration actions that will be performed. --run-syncdb Creates tables for apps without migrations. --check Exits with a non-zero status if unapplied migrations exist. --prune Delete nonexistent migrations from the django_migrations table. --version Show program's version number and exit. -v {0,1,2,3}, --verbosity {0,1,2,3} Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output --settings SETTINGS The Python path to a settings module, e.g. "myproject.settings.main". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used. --pythonpath PYTHONPATH A directory to add to the Python path, e.g. "/home/djangoprojects/myproject". --traceback Raise on CommandError exceptions. --no-color Don't colorize the command output. --force-color Force colorization of the command output. --skip-checks Skip system checks. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 17 Dec 2023 at 04:15, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Helio Loureiro writes: > > > Well... not that good. Now it is mailman3-web that doesn't work. > > > > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > > System check identified no issues (0 silenced). > > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate > > Traceback (most recent call last): > [omitted] > > LookupError: No installed app with label 'migrate'. > > > > Any idea why migrate isn't working and saying it is installed? > > Management commands aren't applications, so they wouldn't be valid > arguments to "mailman-web check" in any case. > Try "mailman-web check postorius" or "mailman-web check hyperkitty" to > see how the application argument works. You should get the report > "System check identified no issues (0 silenced)." as above. > > Then try "mailman-web migrate -h". > If that returns help output, the migrate command is installed and can > be run (the help string is part of the migrate module, not part of > mailman-web itself). > > Why do you think "mailman-web migrate" isn't working? Most likely > "migrate" is working as designed, but it is doing nothing because > something about the way you transported the database originally caused > mailman-web to think its database schema is up-to-date even though it > is not (as happened with the mailman database). > > Unfortunately this database is managed by Django, not by Alembic, and > I don't know offhand how to discover and tell Django the actual schema > version and then ask it to run any new migrations. > > Steve > > >

1 year, 5 months

[MM3-users] Re: Hyperkitty is not archiving due to 405 error - GET instead of POST

by Mark Sapiro

On 2/12/24 8:46 AM, Matthias via Mailman-users wrote: > Hi there, > > I am running mailman3 on Debian 12 - latest package (GNU Mailman 3.3.8 (Tom Sawyer)). > Message handling in general is working fine, but as soon as a message is released, archiving with Hyperkitty is not working, due to a 405 error: > --- > Feb 11 16:18:48 2024 (3479662) HyperKitty failure on http://lists.domain.tld/mailman3/hyperkitty/api/mailman/archive: (405) > Feb 11 16:18:48 2024 (3479662) Could not archive the message with id <170766472771.3479669.4791049109141956450(a)otherdomain.tld> > Feb 11 16:18:48 2024 (3479662) archiving failed, re-queuing (mailing-list jahrgang.domain.tld, message <170766472771.3479669.4791049109141956450(a)otherdomain.tld>) > Feb 11 16:18:48 2024 (3479662) Exception in the HyperKitty archiver: > Feb 11 16:18:48 2024 (3479662) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message > url = self._send_message(mlist, msg) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message > raise ValueError(result.text) > ValueError > --- I would expect to see the text from the requests.post result here. > > When tracing this back, even the frontend Nginx server receives a get in his logs, hence I assume that hyperkitty is really creating a GET instead of a POST request? > --- > 217.72.204.162 - - [11/Feb/2024:16:18:48 +0100] "GET /mailman3/hyperkitty/api/mailman/archive HTTP/1.1" 405 0 "-" "python-requests/2.28.1" I don't know what's going on here. The code is doing a POST <https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperki…>. If in fact HyperKitty is seeing a GET and therefore returning a 405, that explains the above traceback, but I don't know why that would be. You could always try adding additional logging to mailman_hyperkitty/__init__.py to log the entire result, but I suspect the issue is that there is a redirect somewhere in the path from the configured HyperKitty base_url (see mailman_hyperkitty.cfg) and the actual HyperKitty API that is redirecting the POST to a GET and also dropping the POST data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Mails for 1 specific mailinglist not being send and looping in out queue

by Eric Broens

In my mailclient it looks like the LF's have been removed. I'll attach the log extracts to make them better readable. Best Regards, Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote: ----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail. The mailman3 error log show that there is a connection failure to port 25. A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail. Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail. Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either. For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue? Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric _______________________________________________ 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/

4 years, 5 months

[MM3-users] Mailman lifecycle

by Stephen J. Turnbull

eugenio.jordan(a)esa.int writes: > Perhaps this is a sort of dummy questions for software supported by > the Community, my apologies in advance. Aside from the proverbial statement about "unasked questions", your question is particularly appropriate for community-supported software. Many projects do, others don't. > I have been asked on information related to the end of life of > support for 3.1 version, That depends on what you mean by "support". If you mean, will we officially release patches to that version, the answer is "no". We make releases directly off the main branch. If you need features or bugfixes that are not in 3.1, the official upgrade path is to the current release. If you mean, will we answer questions about it, of course the answer is yes. If for some reason you're uncomfortably upgrading to the current version, we'll certainly discuss generating a patch that you'll have to maintain, but our resources are very limited in that area, although there may be other users with interest who can help. And if we judge it to be a bug and confirm that it still exists in the main branch, we are very likely to generate such a patch based on the older version, since that's the best test of whether it works, and of course it's the most urgent need. > and I was wondering whether you could please provide some insights > on how the Mailman life cycle is conceived. For instance, are there > periodically planned releases, say 1 per year? No. We try to release more frequently than that, and until 2019 we almost always had a big release after the sprints at PyCon, but we couldn't sprint effectively in 2020 or 2021. I hope that tradition will continue from next year, though. We have occasionally had a release after the conclusion of Summer of Code, as well, but that's much less consistent. > If so, will you please confirm how long we are to expect the > previous versions to be maintained? There is no maintenance planned on past releases, except future releases. Patches to the current release, whether bugfixes or new capabilities, go directly into the next release. Regards, Steve

3 years, 10 months

[MM3-users] Re: migration from 2.1 - owners and moderators

by Brian Carpenter

On 10/23/20 8:31 PM, Alex Schuilenburg via Mailman-users wrote: > We're migrating from 2.1 to 3.2.1 and an odd issue has popped up. It > may be something different in the way mailman3 works, or a > misconfiguration on my part. > > Most of the lists migrated so far don't have moderators, just owners. > However, when these lists have messages requiring moderation, the > owners dont get notified of held messages - unlike 2.1 where they > did. Is this a change or is there something I am missing in the > configuration? > > I have the minute/quarterly/hourly etc cron jobs running, although I > have had to tune down the frequency of minute to hourly as it takes > 6.5 minutes to run* - but I doubt this is the cause. > > While for the moment I have found the held messages in files in > /var/lib/mailman3/messages and figured out which lists are in need of > attention (and notified the owners), it seems I may have to do a bit > of coding myself to walk through the lists and notify owners when > their list is in need of attention. There must surely be something > that does this already - or is this moderators only in mailman3? > > Guidance appreciated. > > Thanks > > -- Alex > > * From the list I realise this is because I am still using the default > whoosh backend to haystack and need urgently to switch to xapian or > solr, but the info on how to get this working for a noob like me is > unfortunately lacking Hi Alex, List owners should be receiving moderation notifications and are able to moderate messages when they log into Postorius. Have you checked your MTA logs to see if they are or are not being sent out? If you don't mind having some paid assistance, I may be able to assist you with getting Xapian up and running. We use Xapian on our vanilla MM3 servers and Elasticsearch on our MM3 Affinity/Empathy servers. You can contact me off list if you are interested. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: moving individual list to different domain

by Mark Sapiro

On 3/21/23 06:21, Johannes Rohr wrote: > Dear all, > > on mailman2 it was possible to move a list to a different domain within > the same mailman instance. > > I have found no information on how the same can be accomplished on > mailman3. > > Is this possible at all? In mailman 2.1, a list was identified by its name only without the domain and those names had to be globally unique. A site could be configured to support multiple virtual hosts and a list had a host_name attribute which could be changed if desired to assign the list to a different virtual host, but there couldn't be two lists with the same name even if they had different host names. Mailman 3 is different. In order to remove the restriction that list names (without the domain) had to be globally unique, in MM 3 the domain is part of the list name. I.e., we can now have list(a)example.com and list(a)example.net as two distinct lists in the same installation. Suppose we want to rename list(a)example.com to list(a)example.net. This becomes involved in Mailman 3 because it affects not only Mailman core, but also mail delivery and archiving. Furthermore, the list with fqdn_listname list(a)example.com has the list_id list.example.com. If we change the fqdn_listname to list(a)example.net, the list_id should remain list.example.com per RFC 2919 Sec. 4. <https://www.rfc-editor.org/rfc/rfc2919>. We can just change the list's mail_host attribute via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or via a database query, but this leads to confusion. I.e., a URL like https://example.com/mailman3/lists/list.example.com/ will still work but https://example.com/mailman3/lists/list@example.com/. To avoid this, we could also change the list_id, but we can't do that via REST as it's a read-only property, and changing the list_id says this is really a new list, not the same list with a new name. Also, none of this addresses archiving. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Easiest way to install a new mailman3 deployment?

by Andrew Hodgson

ieso(a)johnwillson.com wrote: >@AndrewH. >Yes, I saw your notes, but the impression I got during this effort is that package-based/non-docker implementations change too much between versions, so anything written based on Ubuntu 16.04 or earlier just didn't feel worth spending significant time on... that impression came from the "this is new to version >18.04" warnings in the Ubuntu 18.04 walkthrough ( https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) >See my comment below for more. Upgrading for me is just a case of running the relevant Pip commands and running the post-update script. I have done it a number of times. As I have done the installation from scratch I am fairly confident I can move to a newer OS without much hassle and identify where problems may occur. The biggest issue for me is getting modules via Pip and having issues therein. For example when I first did this in March I ran into an issue with a Python module having been upgraded and thus the latest version of a package caused an error which took a while to troubleshoot until I wrote to this list and eventually installed an older version. >@JonathanM >My attempt at doing a DigitalOcean package/non-docker based implementation was frustrating. I found a really detailed walkthrough ( https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) >and after the usual hyperkitty authorization problem solving, it got me to a point where everything looked perfect, based on a glance at the web interface. However, a bizarre collection of errors showed up during QA testing, such as the following: I think the best point is to give us errors if you encounter them and we can try and troubleshoot specifics rather than giving up altogether, however, see below on the Docker part. >So here's my latest (failed) attempt, to see if anyone can spot where I went wrong. Again, I'm just trying to get a dedicated mailman3 server up from scratch. Oh, I should add that I tried the mailman4 AWS Mailman3-as-SaaS <https://aws.amazon.com/marketplace/pp/New-IT-Mailman-4/B089M2PCVV>, and that >worked just fine. However we can't host our data on a SaaS platform, so that's unfortunately not an option for us. I just want to mention it for anyone looking for a "give me mailman services in five minutes for $30/month" solution. Regarding this marketplace image this would actually run on your VM but its running as an appliance/turnkey solution so may still not qualify for you. I wouldn't go there anyway because troubleshooting it may be hard and I am a bit suspicious of smaller companies posting to Amazon Marketplace like this as to their long-term support. >Phase 1 - Prepare the AWS instance and MTA Most of the documentation on the Mailman side talks about running these containers on a dedicated VM with an MTA and front-end web server installed on the VM. If you are using a VM to run the containers then the network 172.19.199.0/24 is assumed to be a backend Docker network which is used to allow the different containers to talk to each other and to allow the front-end web server/MTA to communicate. If it were me doing this with this setup I wouldn't create the VPC with the same subnet as it may cause issues and we don't really care of the VPC subnet details. If you look at the Docker Compose file in the Docker-Mailman repo you can see its creating this 172.19.199.0/24 network as a bridge network and in most cases you wouldn't connect to these containers from anything other than the VM. A typical traffic flow may look something like the following: - Inbound SMTP to Exim/Postfix running on the VM (inbound access to port 25 and MX delivery arranged). - Exim/Postfix knows to relay messages for the Mailman domains to 172.19.199.2 on port 8024 (LMTP). - Mailman services connects to Postgresql DB on 172.19.199.4. - Mailman Hyperkitty plugin connects to the Hyperkitty web service on 172.19.199.3:8000 to archive the message. - Mailman core sends email out to Exim/Postfix server running on 172.19.199.1. What Postfix does with the email (i.e sends out via SES) is not Mailman's concern. - A user wishing to access the web interface connects to the VM directly on port 80 or preferably 443 with necessary inbound NSG rules defined. - The front-end web server knows to proxy these requests to 172.19.199.3:8000 (or if the front-end server supports Uwsgi then its 172.19.199.3:8080 - The front-end web server knows that the /static path should be served up locally from the local filesystem /opt/mailman/web/static which the Mailman-web container writes files to when it starts up. I think its best to continue running these containers from the VM in the above setup, you mention ECS later on in this email but that is going to confuse the issue unless you really want to run the containers under ECS. [...] > 1. Tried to follow the standard directions... .I put most of the > relevant files below. Did you create the necessary /opt/mailman/core and /opt/mailman/web directories on the VM and set perms as detailed in the repo README? >docker-compose.yaml [...] >services: > mailman-core: [...] > volumes: > - /opt/mailman/core:/opt/mailman/ /opt/mailman/core (or at least /opt/mailman) on the host VM needs to exist. The container will write files to /opt/mailman which then get persistently written to /opt/mailman/core on the host. One of the files that get written in this way is /opt/mailman/core/var/data/postfix_lmtp and /opt/mailman/core/var/data/postfix_domains which is referred to in your Postfix configuration (see later on). [...] >maillog has some interesting stuff I'm seeing for the first time. Let me know if this suggests any obvious suspects. [...] >postfix/qmgr[4351]: error: open >/opt/mailman/core/var/data/postfix_domains: No such file or directory Check this file on the VM and see if it exists (or if parent path exists). If parent /opt/mailman/core doesn't exist create it. If it exists but there is no var directory inside it, check the container stdout logs for errors. If other directories inside /opt/mailman/core/var (especially logs) look at them for more info. Thanks. Andrew.

4 years, 5 months

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

by Rafael Mora

El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > You've said you're working with labbrands.com. > > labbrands.com has address 192.185.51.89 > mail.labbrands.com has address 192.185.51.89 > www.labbrands.com is an alias for labbrands.com. > > telnet proves that Exim is running on that IP address. Either you're > running it, or hostgator is redirecting the SMTP ports. > > You added: > lists.labbrands.com has address 190.145.27.66 > > Presumably that's a different machine. > > So that now needs an MX record, and a firewall routing. I added the MX record on our hostgator hosting like this: [image: image.png] Is it correct??? > And the SPF > records ... and spam and virus filters, and all the other stuff you need > to setup an independent, public-facing smtp server. > > But at least you won't have to relay. > > Good luck. > > On 03-Aug-17 16:55, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org>) escribió: > > > >> I think you're confused. > >> > >> You already have mail.labbrands.com set up as the MX record for > >> labbrands.com. And it has an A record with the same address as your > >> webserver. > >> > > I'm working with the hostgator mailserver, we are not running a local > > mailserver. > > > > As suggested I added an A record like this: > > [image: image.png] > > > > Is it correct? is it redirecting to my Ip so I can redirect it to my > > postfix/mm3 server? > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > >> server running on that IP address. You can't have 2 servers on port > >> 25. In that case, as has been noted before, you'll need to setup a > >> relay in that server, not a firewall redirect. Depending on your MTA, > >> you would need to relay to your internal server. And make sure your > >> firewall setup allows your MTA to do this. > >> > >> We can see it's EXIM: > >> > >> telnet mail.labbrands.com 25 > >> Trying 192.185.51.89... > >> Connected to mail.labbrands.com (192.185.51.89). > >> Escape character is '^]'. > >> help > >> 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 > 15:47:48 > >> -0500 > >> 220-We do not authorize the use of this system to transport unsolicited, > >> 220 and/or bulk e-mail. > >> 214-Commands supported: > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > >> quit > >> 221 gator4137.hostgator.com closing connection > >> Connection closed by foreign host. > >> > >> Or, consolidate all your e-mail to one server - which is a lot easier to > >> manage unless you have a really big operation. Postfix is probably the > >> right choice, but requires more setup. > >> > >> Although Mailman3 configuration is not well documented (as you've > >> discovered), you may want to get help from someone with more general > >> network and mail experience. You're now into territory that is, as > >> Simon indicated, not Mailman-specific. > >> > >> On 03-Aug-17 16:28, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) > >> escribió: > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > >>>> escribió: > >>>>>> You need to forward port 25 for SMTP mail delivery and if you want > the > >>>>>> web UI (Postorius and HyperKitty) accessible from the outside, port > 80 > >>>>>> for http and/or port 443 for https > >>>>>> < > >>>>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>>>> . > >>>>> I mean for incoming mail redirected from my hostgator hosting, > because > >>>> when > >>>>> I suscribe an email address MM3 sends a confirmation email, so I have > >> to > >>>>> reply to be suscribed to the list. > >>>> As I said, for mail delivery you need to forward port 25 to the > Mailman > >>>> server. > >>>> > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local > >> centos7 > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > >>> > >>> > >>>> -- > >>>> Mark Sapiro <mark(a)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 > >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >>>> > >> -- > >> This communication may not represent my employer's views, > >> if any, on the matters discussed. > >> > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by Jason Glazer

Mark Thanks for the link to the test archive. That and your information has clarified things a lot. Jason On 7/12/2017 11:39 AM, Mark Sapiro wrote: > On 07/12/2017 04:47 AM, Jason Glazer wrote: >> Does anyone know if Hyperkitty can be configured to allow for inline >> images to be maintained so that an HTML file looks like a normal HTML >> message? >> >> Also, can attachments to a message under Hyperkitty preserve their name >> rather than being "scrubbed" into "attachment-*.*" files? > > The answer to some of this is at > <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DC…>. > > One question unanswered by that post is what happens with an inline > image in an HTML message body. In the original message, the image is > referenced by an IMG tag with "src=" pointing to the image MIME part. > Since this structure is not maintained in HyperKitty, inline images > probably don't work. > > Also, with respect to Mailman 2.1, if you want the scrubber to preserve > file names and extensions, set the following in mm_cfg.py > > SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False > SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True > > and if you want scrubbed HTML to not be HTML escaped so it renders > rather than looking like raw html, set > > ARCHIVE_HTML_SANITIZER = 3 > > but note this comment from Defaults.py > >> # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this >> # is very dangerous because it essentially means anybody can send an HTML >> # email to your site containing evil JavaScript or web bugs, or other >> # nasty things, and folks viewing your archives will be susceptible. You >> # should only consider this option if you do heavy moderation of your list >> # postings. > > This is an issue with HyperKitty as it appears this is what HyperKitty > does and there's no way to turn it off. > -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

7 years, 10 months

[MM3-users] Re: Welcome Message

by Abhilash Raj

On Wed, Apr 17, 2019, at 1:41 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > If the URL for template is wrong, or Postorius is down for whatever reason, > > the subscription will fail with the error that you saw before. > > Explain URL for template. You mean "POSTORIUS_TEMPLATE_BASE_URL"? That > is not wrong. I am confident of that. It is back to > "http://mailman-web:8000". I can successfully ping mailman-web:8000 > from bash. POSTORIUS_TEMPLATE_BASE_URL is used to create the template urls, yes. > > > > I logged out of Postorious and subscribed using the > > > subscribe form on > > > the info page and the change to the welcome template showed up. So it > > > looks like being logged in as admin while trying to subscribe someone > > > was what was causing the problem. Is that a bug I discovered? > > I suspect stopping-restarting and re-creating the template (idk, if you > > really did that) might have something to do with it. I am not sure if this > > is a bug unless you can reliably reproduce this. > > This error is absolutely reproducible. It even impacts other list > admins who are trying to use a custom welcome message and subscribing a > member while logged into Postorious. Everything else is working fine on > this server and I followed your directions precisely when I set this > server up. Please help. Can you reply here with the output of this query on your server: $ curl --user restadmin:restpass -L http://172.19.199.2:8001/3.1/lists/mailman-users.mailman3.org/uris Please replace "restadmin:restpass" with the username password of the rest api, if you have customized it. It not leave it as it because that it the default. Also, replace "mailman-users.mailman3.org" with the the List-ID of your mailing list. (replace @ with .) in your posting address. If you don't have curl, choose whatever http client you have. > > Thanks, > Brian > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: toward improving correctness when running on single core system ...

by Stephen J. Turnbull

Nelson Strother writes: > > Presumably there's also a chance for the runner to detect and > > log the expired lock before it dies. > > This may require some cleverness, as the delays introduced by > recording a log message e.g. "I'm the nntp runner holding the lock, > and it has not expired yet." are likely to change the results of > the lock competition, maybe even allowing all runner processes to > continue as intended. Unless the runner is killed with an uncatchable signal, there likely is a point before exit to do this, and no, *all* runner processes won't continue, because this one is already dying in my suggestion. I understand there may be cases where you can't find a place to put the log, but I don't think it's worth treating this as a recoverable error if it happens that after the message is logged the initialization somehow completes successfully -- once you detect an expired lock, give up. > It is unclear to me whether a process would ever have an > opportunity to record a log message e.g. "I'm the nntp runner > holding the lock which has expired, but I am not dead yet." before > it dies. Agreed. Until it's clear that the opportunity doesn't exist, this idea may provide a faster simpler way to diagnose this kind of problem. > If such an opportunity exists, it should extend the lock's lifetime > via e.g Lock.refresh(timedelta(seconds=10)). I disagree. The point of setting an expiration is that you know the process is misbehaving if it holds the lock that long. Setting a longer expiration is a reasonable workaround until we understand and fix the misbehavior. But allowing the misbehaving process to extend possession of the lock is a bad idea. > As I attempted to summarize at the end of [3] above, each time I > tried shorter sleep intervals (1, 10, 15 seconds) within > .../flufl/lock/_lockfile.py It wasn't clear to me which experiment that referred to. Thank you for clarifying.

1 year, 11 months

[MM3-users] Re: Hyperkitty on Debian 12

by Michael Oberrauch

On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key > used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a > subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > Hi Markus, we are also running MM3 on Debian 12 from Package Repositories. First of all, you should not try to directly switch user (su) to the lists user, it's generally intended to executes commands as that user, if necessary; either using `runuser`, `sudo`, or `su -c`. However, the prepackaged scripts `mailman-wrapper` and `mailman-web` already do this and therefore you ca run those as root without permission problems. On Debian there are two relevant users for MM3: the list user runs mailman core, whereas the www-data user runs Postorius and Hyperkitty. So you have to make shure, that the www-data user can access the .mbox files while importing. Hope that helps. Cheers, Michael -- Michael Oberrauch (er/ihm) Computerreferent Fachschaft Mathematik/Physik/Informatik/Chemie Studentische Vertretung Technische Universität München Boltzmannstraße 3 85748 Garching eMail: oberrauch(a)fs.tum.de Tel: (+49) 089 289 18545 Fax: (+49) 089 289 18546 https://mpic.fs.tum.de

1 year, 2 months

[MM3-users] Re: AH01102: error reading status line from remote server 172.19.199.3:8000

by Abhilash Raj

Hi Henrik, On Mon, Jul 17, 2017, at 02:31 AM, Henrik Rasmussen wrote: > I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the > right CSS layout I installed Apache on the Mailman server outside Docker, > as advised by Abhilash Raj and Alexander Klotz. > > My Mailman server is on a secured network and the https connection from > Internet will be handled by proxy servers, so I will be using http (port > 80) between proxy-servers and Mailman server. > > But when I sign in (currently via an SSH tunnel to the Mailman server > from my workstation) I get "Internal error: [client ::1:41912] AH01102: > error reading status line from remote server 172.19.199.3:8000, referer: > http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F" Output from logs might be more helpful to debug what is wrong. They are present at `/opt/mailman/web/logs/mailmanweb.log` for Django. You may also find some other log files there which are related to uwsgi, the WSGI server that is used to interface Django with Web Servers like Apache. > If I type a wrong password, I am just warned about that, so the problem > appears when log in is accepted. > > I expect that it is because I connect to localhost:80 through SSH tunnel. > What do I miss in my Apache configuration on the Mailman server to avoid > this problem? > > <VirtualHost *:80> > ErrorLog /var/log/httpd/error_log > LogLevel warn > CustomLog /var/log/httpd/access_log combined > > ServerAdmin root(a)example.foo > ServerName list.foo.bar > Alias /static /opt/mailman/web/static > Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico > > ProxyPassMatch ^/static/.* ! > ProxyPass / http://172.19.199.3:8000/ > ProxyPassReverse / http://172.19.199.3:8000/ > > <Directory /> > Allow from all > Require all granted > </Directory> > > <Directory /opt/mailman/web/static/hyperkitty/img/> > Allow from all > Require all granted > </Directory> > > # ssl config here ... > </VirtualHost> > > > Thanks, > Henrik Rasmussen > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 10 months

[MM3-users] Re: Unsubscribe Notifications to List Owners and Members

by Brian Carpenter

What list are you trying to unsubscribe from and how are you doing it? On 10/22/20 4:58 PM, Jerry Koutavas wrote: > > No offense but been trying to unsubscribe for months, nothing happens > > *From:*Brian Carpenter [mailto:brian_carpenter@emwd.com] > *Sent:* Thursday, October 22, 2020 4:56 PM > *To:* Mailman users <mailman-users(a)mailman3.org> > *Subject:* [MM3-users] Unsubscribe Notifications to List Owners and > Members > > It seems that the only time an unsubscribe notification is sent to a > list owner and/or list member is when a list member sends an email to > lisname-unsubscribe@listdomain <mailto:lisname-unsubscribe@listdomain> > and that list member is not registered > with Affinity/Postorius. Can anyone confirm this and if confirmed, is > this considered a bug? > > > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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/ > > ------------------------------------------------------------------------ > > *Total Control Panel* > > > > Login <https://asp.reflexion.net/login?domain=ascii.com> > > To: jk(a)ascii.com > <https://asp.reflexion.net/address-properties?aID=10188568&domain=ascii.com> > > From: mailman-users-bounces+jk=ascii.com(a)mailman3.org > <mailto:mailman-users-bounces+jk=ascii.com@mailman3.org> > > > > Message Score: 70 > > > > High (60): Fail > > My Spam Blocking Level: Medium > > > > Medium (75): Pass > > > > > Low (90): Pass > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-address=1&hID=458079…> > this sender / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-address=1&hID=…> > this sender enterprise-wide > > > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-domain=1&hID=4580794…> > mailman3.org / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-domain=1&hID=4…> > mailman3.org enterprise-wide > > > > /This message was delivered because the content filter score did not > exceed your filter level./ > -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: Timeout error on anonymous subscribe

by vogt＠spamcop.net

Mark Sapiro wrote: > On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > > localhost tcp port. Any local user can do that. > I am trying to duplicate what Mailman does in an attempt to find the issue. > > I can access the template content with > > curl > > http://localhost:8000/mailman3/api/templates/list/community.lists.example.co... > > as well as > > curl > > http://lists.example.org/mailman3/api/templates/list/community.lists.example... > > as any user on the mailman server. > > How about > curl -A 'python-requests/2.32.3' > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as the Mailman user? I have tried anything I could think of but I cannot reproduce the issue using curl as user mailman (or any other for that matter) Going directly for localhost:8000, using some or all of the headers I can capture with tcpdump: ``` $ curl -v -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… ``` as well as going through the local httpd: ``` $ curl -v --http1.1 -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' https://lists.example.org/mailman3/api/templates/list/community.lists.examp… ``` Running tcpdump during those runs shows me it's sending the same headers as mailman does. Thus on http protocol level it's the same, but still the server returns immediately. What I have just noticed is that the Date header in the delayed response is the "late" time. I have even compared tcp headers from either capture. They look identical down to the frame sizes. The only difference the last times is that with curl, the server side sends the ACK for the request and milliseconds later a PSH,ACK with the response headers. When it comes internally from mailman it sends the ACK for the request and then 5 seconds later it sends the PSH,ACK with the response headers. Thanks, Gerald

7 months, 2 weeks

[MM3-users] Re: Advice on migrating to Mailman 3

by Allan Hansen

Ditto. I very much like the MM3 archives. The archives in MM2 were very hard to use. MM3 has better DMARC support as well, and members have better control of their subscriptions on a multi-list server (I maintain some 50 lists and many of the members are on multiple lists). MM3 is in need of more work and it appears to be happening, but it’s a very good package already, well worth it. Yours, Allan Hansen hansen(a)rc.org > On Feb 20, 2020, at 10:17 , Mark Dadgar <mark(a)pdc-racing.net> wrote: > > On Feb 20, 2020, at 8:47 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >>>> The only problem is that our list runs on Mailman 2. We would like to >>>> move to Mailman 3 >> >>> Why? >> >> I'll echo this. We don't need to know (unless there's a specific >> technical challenge to Mailman 2 that you hope Mailman 3 can resolve, >> and then we can tell you whether Mailman 3 has it, will have it soon, >> or won't have it soon if ever), and don't really care (happy to help >> and all that). But you need to ask yourself that question because >> it's rarely a good idea to fix what ain't broke. And Mailman 3 is >> sure to become more robust, easier to install, and easier to migrate >> Mailman 2 lists over time. Don't do it until you forsee a near- >> future *need* to migrate, is my advice. > > > I’ll weigh in here. In my case, I moved an almost 20 year old MM2 installation to MM3 primarily to get archiving that actually worked well. The poor searching of the list archives was easily the #1 complaint I got about my mailing list. > > MM3 is awesome. Finicky to get running, but awesome. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > _______________________________________________ > 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/

5 years, 3 months

[MM3-users] Re: /hyperkitty/list/ shows "example.com" / mailman3 archives not updated

by Mark Sapiro

On 5/17/20 6:05 AM, patrick-mailinglists(a)whonix.org wrote: > /hyperkitty/list/ shows "example.com". Not the actual domain name that I configured. How can I fix this? Ensure that your actual domain is listed in the Django admin interface under Sites. Then ensure that your SITE_ID setting in your Django settings is correct. This is tricky because the site id might not be what you expect. You have to look in your database at the django_site table[1]. This table contains one row per site with columns id, domain and name, and the id values don't necessarily match what you'd think from looking at Sites in the Django admin interface. > I would not mind too much about hyperkitty showing "example.com". But the more important issue is that mailman3 archives are not updated. Therefore I guess it's a symptom of a more important issue. I doubt that these things are related. > E-mails to the list are delivered to e-mail subscribers, though. Seems only the web part is broken. What's in Mailman's log (var/logs/mailman.log) and are the messages all queued in var/archivers/hyperkitty/spool? If so, mailman-hyperkitty can't communicate with hyperkitty. Ensure that the settings in mailman-hyperkitty.cfg are correct. base_url: needs to be a URL that can access hyperkitty and api_key needs to match the MAILMAN_ARCHIVER_KEY setting in your Django settings except that it's quoted in the Django settings and not in mailman-hyperkitty.cfg. > Using Debian buster mailman3 packages. In configuration folder /etc/mailman3 I cannot find any textual string saying "example.com". > (`grep -r -i example /etc/mailman3`) > Therefore I don't know where mailman3 gets "example.com" from. Please see <https://wiki.list.org/x/12812344> [1] other ways to get this are a) increment the SITE_ID setting until you find the one that works or b) in a django admin shell do from django.contrib.sites.models import Site for site in Site.objects.all(): print('id: {}, name: {}, domain: {}'.format( site.id, site.name, site.domain)) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: "The content of this message was lost."

by Jens Günther

You have to incorporate these 2 changes: https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs and https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs We made it persistent in the Dockerfile of mm-core, so that it will be rewritten every time when building the container: COPY ./moderator.py /usr/lib/python3.8/site-packages/mailman/app/moderator.py COPY ./test_moderation.py /usr/lib/python3.8/site-packages/mailman/app/tests/test_moderation.py It is already fixed in Postorius 3.3.6, but it's not clear, when maxxking's containers will be bumped to that version. Am 09.09.22 um 16:33 schrieb skenny(a)scss.tcd.ie: > I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). > > This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. > > In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read > > The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list. > > I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? > > Thanks for any advice. > Stephen > > PS: > The Mailman web interface "System Information" link reports: > Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > _______________________________________________ > 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/

2 years, 9 months

[MM3-users] Re: Moderator e-mails only going out once a day

by Odhiambo Washington

On Mon, Apr 21, 2025 at 10:16 PM dgoldsmith--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > I am having a similar issue as Joe. > > Our Mailman 3 server is running on Rocky Linux 9.5. It is deployed using > a Python virtual environment. > > (venv) [mailman@<server> shunt]$ mailman info > GNU Mailman 3.3.9 (Tom Sawyer) > Python 3.9.21 (main, Dec 5 2024, 00:00:00) > [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] > config file: /etc/mailman3/mailman.cfg > <output trimmed> > > Mailman 3.3.9 > Postorius Version 1.3.10 > HyperKitty version 1.3.9 > Postfix = 3.5.25-1.el9 (may have some newer bits backported into it - RHEL > way) > Django version = 4.2.13 > > Output of the for loop Mark provided above shows that all the lists on the > server have admin_immed_notify set to True. > > Here is the activity from the mailman.log file when I send a message to > the list and it gets held: > > Apr 21 19:11:37 2025 (2564) sans-faculty: DMARC lookup for > dgoldsmith(a)sans.org (_dmarc.sans.org) found p=reject in _dmarc.sans.org. > = v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email > Apr 21 19:11:37 2025 (2564) HOLD: sans-faculty(a)mlm.sans.org post from > dgoldsmith(a)sans.org held, message-id= > < > SJ0PR18MB5112D63A7D9F3851A4A6B0C0AEB82(a)SJ0PR18MB5112.namprd18.prod.outlook.com>: > The message comes from a moderated member > > No further activity indicating it sends (or attempts to) a notice to the > list admins/mods about a held message. > Assuming you did run the mailman shell command and the output was: ```List sans-faculty(a)mlm.sans.org Immed notify True``` What do you have in your MTA logs around the same time? Nothing? That would imply that for this list, you have set "Default action to take when a non-member posts to the list" to "Discard" If you change that setting to "Hold for moderation", then you will receive a notification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 month, 2 weeks

[MM3-users] Re: WEB UI fail to reply and create new thread

by Abhilash Raj

On Sat, Dec 19, 2020, at 6:29 AM, Abhilash Raj wrote: > > > On Sat, Dec 19, 2020, at 4:32 PM, Carlo Landmeter wrote: > > We are not running in debug mode, we simply set the loggers to log > > DEBUG or else we don't see much info. > > I also doubt the shown error is the problem as I see more template > > errors. > > I have also tried to run the official docker images mailman-docker but > > im having the same issue. > > > > When I post via the online form, i can see uwsgi requests with http > > status 200 from the ajax call, so i would expect it to work, but it > > does not leave a message in hyperkitty nor sends an email. > > > > PS emails are send just fine via smtp posting. > > Unless I am missing something basic, I don't really know why it doesn't > fail on our servers. May have something to do with Django versions or > something. I need to work a bit more on verifying it. > > This is the line in template[1], rendered using this context[2] which > seems to be causing the issue. I've made the change to remove the `'display_fixed'` attribute for email [1]. [1]: https://gitlab.com/mailman/hyperkitty/-/merge_requests/299 You can update the `pip install commands` to `git+https://gitlab.com/mailman/mailman@master` after the MR gets merged to create a test image and see if it fixes the issue for you. You can see the sample .dev Dockerfiles i have in my docker-mailman repo for reference[2]. [2]: https://github.com/maxking/docker-mailman/blob/master/web/Dockerfile.dev Abhilash > > [1]: > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/templates/hy… > [2]: > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/messag… > > > > _______________________________________________ > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

4 years, 5 months

[MM3-users] Re: mail host choices when creating a new list

by Andrew Hodder

Ah, so obvious I can't believe I hadn't noticed it before, thanks! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Tue, Oct 24, 2017 at 3:50 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Tue, Oct 24, 2017, at 12:24 PM, Andrew Hodder wrote: > > Abhilash, > I'm not sure what you're referring to, there's no "web hosts" in the admin > panel and I already added the "mail hosts" there (of the four added, only > the first one shows up in the postorius drop down). > > > Ah! I mis-read your email. You need to add new domains in Postorius before > you can create new lists using them. > > You are looking for '/postorius/domains/', add a new domain there, and > then it will show up in the 'mail hosts' in create-new-list form. > > > Sincerely, > > Andrew Hodder > Systems Administrator > Support Operations, Afilias > E-mail: drew(a)afilias.info > Phone: +1 416.673.4164 > Fax: +1 416.646.1541 > > On Tue, Oct 24, 2017 at 3:08 PM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > Hi Andrew, > > On Tue, Oct 24, 2017, at 11:58 AM, Andrew Hodder wrote: > > Hi! > > > > So, I'm trying to create a new list and pick one of the other mail > > domains > > we have configured (from the django admin panel), yet in the "Create New > > List" page in postorius, I see only a single option (the first domain > > we'd > > added/set as the default) in the drop-down under "Mail Host". Am I > > missing > > somewhere else I need to add alternative mail domains to? Thanks in > > advance! > > Yes, you can add new 'Web Hosts' from the Django's Admin console > (admin/django_mailman3/maildomain/). Note that you need to be a > superuser to do this. > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > >

7 years, 7 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 02:35 PM, Abhilash Raj wrote: > > Hi, > > > > On Wed, 9 Aug 2017 13:42:20 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > [...] > > > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > > well? > > > It's only that one and whether it's needed or not depends on list > configuration. The list has attributes digest_send_periodic and > digest_size_threshold. When a post is received it is added to the list's > digest mbox, and if that causes the size of the mbox to reach > digest_size_threshold K bytes, a digest is sent. Additionally, if > digest_send_periodic is true, a digest is sent periodically whether or > not it has reached digest_size_threshold. > > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks? I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there. > > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Also, it seems that Postorius doesn't have any way to set `digest_send_periodic` and only has a setting to set the max_threshold for the digest. I opened another issue (https://gitlab.com/mailman/postorius/issues/211) to add this feature. -- thanks, Abhilash Raj

7 years, 9 months

[MM3-users] Re: Lost posting in archives

by Axel Rau

> Am 22.01.2022 um 02:39 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: > > On 1/21/22 3:06 PM, Axel Rau wrote: >> I created a list, did migration from 2.1 and run update_index_one_list. >> Then I posted a test mail to the list and it got distributed and was seen in the archive. >> Now 2 days later it does no longer show up in the archive. >> What is going on here? >> May this have to do with >> HYPERKITTY_RENDER_INLINE_IMAGE >> which I have turned on meanwhile. > > It may. Is there anything in Django's log about this? Yes: - - - Jan 19 16:46:59 2022 (1997) HyperKitty failure on https://lists.framail.de/hyperkitty/api/mailman/urls: <https://lists.framail.de/hyperkitty/api/mailman/urls:> <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) - - - I have: - - - MAILMAN_ARCHIVER_FROM = ('{{ fqdn }}') - - - Should I put localhost here? > If you have the original message from the list, can you go to the URL in the Archived-At: header? Is empty: - - - Archived-At: <> - - - > is the message in the hyperkitty_email table in the database? E.g., > > SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx'; > > (xxx is the value of the Message-ID-Hash: header from the message) No. > > If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com <mailto:var/archives/prototype/list@example.com>/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. No. How can it be enabled? That’s all I have: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# ls -lR var/archives total 1 drwxrwx--- 3 mailman mailman 3 18 Jan. 18:05 hyperkitty var/archives/hyperkitty: total 25 drwxrwx--- 2 mailman mailman 6 19 Jan. 16:46 spool var/archives/hyperkitty/spool: total 1310 -rw-rw---- 1 mailman mailman 838274 19 Jan. 16:46 1642610819.7180374+05663686ecac2e85272bac93299d8469aa299a6d.pck -rw-rw---- 1 mailman mailman 8888 19 Jan. 16:46 1642610819.7836225+51d3aa9170bfb408821d5d05bd50acb687f23c19.pck -rw-rw---- 1 mailman mailman 13215 19 Jan. 16:46 1642610819.846788+bdfe7825a5a718d081683cf9cfa53cc1f36e64f2.pck -rw-rw---- 1 mailman mailman 469150 19 Jan. 16:46 1642610819.9367082+6c8adeae7d43ec9f721959a57bc1d1415c0b4857.pck - - - Thanks for your time, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 years, 4 months

[MM3-users] Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210523 02:41]: > Andreas Barth writes: > > > Currently it is "list public" vs "subscribers only". I need something > > inbetween, so that some (i.e. most) people have access to the > > restricted audience lists but not just everybody. > > That much is clear. The problem is that "access to list" can mean a > lot of things: can subscribe, can post, can admin, can view archives, > can view list in listinfo, can view subscriber list, and there are > probably others. What permissions are needed for what general classes > of users? public: anyone can subscribe and read the archive. Think about an announcement mailing list of an organisation. restricted: for employees (or members - or whatever) only. So they could subscribe themself. The archive and posting may be restricted to subscribers or to anyone in that group - both would be working for me. (How to know who is allowed to subscribe is another question - having an internal mailing list which contains all the members just for this purpose would be ok for me.) private: hand-selected people, think about e.g. board or steering committees internal discussions. Of course, the archive (if there is any) should be restricted to the actual members. Posting to these lists is currently not restricted, so no derivation needed from the current set in postorius. > > Just as an idea, how about always one "custom attributes" field. So > > that from a database pov this field is always there. > > We could do that, but then we'd have to support it. I'm thinking of > situations like admin A populates the field, then leaves the > organization, and we add (some of) the supported features, and admin B > wants to migrate that. I don't see any good coming of that for us. > As Mark says, a separate table seems like the way to go for custom > attributes. Well, that problem will always exist. I don't think you would make it harder by having one "custom attributes" field. I'm going to try the plugin route Mark suggested. Andi

4 years

[MM3-users] Hyperkitty list overview error: thread matching query does not exist

by Darren Hart

When attempting to visit the hyperkitty archives list overview for one of my two lists: Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). The following appears in /var/log/mailman3/web/mailman-web.log: ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 135, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 251, in overview_posted_to for thread in mlist.recent_threads: File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 142, in recent_threads return self.cached_values["recent_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py", line 59, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 281, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 281, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. The hyper kitty archives for a second list on this Mailman3 instance is working correctly. How can I fix this view of the archives? Or how can I get more information on what might be failing? Thanks, Darren

3 years

[MM3-users] Ubuntu 24.04 upgrade notes

by Andrew Hodgson

Hi. Just thought I would write up my installation experiences on Ubuntu 24.04 following this guide as much as possible: Virtualenv Installation - Mailman Suite 3.3 documentation (mailman3.org)<https://docs.mailman3.org/en/latest/install/virtualenv.html> Ubuntu packages: I'm trying not to install dev packages on the server if possible and managed to get away with the following packages: python3-psycopg2 sassc lynx python3-venv python3-certbot-nginx postgresql exim4-daemon-light Creating the venv: python3 -m venv --system-site-packages --symlinks venv This creates the venv referencing the system packages as well which is useful as some of the dependencies for Mailman are met by the Certbot and python3-psycopg2 packages. Using Pip I installed the following packages: pip install mailman mailman-hyperkitty mailman-web Postgres: I ran into an issue with the database after running `mailman-web migrate`. This was because a newer version of Django pulled in from the above command needed some tables creating in the public schema, and from Postgres 15 (Ubuntu ships with Postgres 16) that isn't allowed by default. I solved this by making the Mailman role owner of the mailman database. I am aware of discussions around whether its best to do this or give explicit perms on the databases to allow all on the public schema, but I decided to go with this option. My Postgres commands are now: sudo -u postgres psql create database mailman; create user mailman with encrypted password '[...]'; ALTER DATABASE mailman OWNER TO mailman; Django: I ran into an issue with a newer Django installation not allowing any form submission, was getting a 403 returned due to CSRF protection failure. I resolved this by adding this line to my local Settings.py: CSRF_TRUSTED_ORIGINS=['https://lists.domain.com'] I moved back to using Gunicorn for the backend server, the instructions on this were spot on. I've had this error before but the mailman-web compilemessages command failed because of missing msgfmt. I think I can pull this in from Ubuntu packages but may need to update installation docs with this extra package requirement. Search: I continued to use Woosh as I'm running a very low traffic site and that is what comes with Mailman-Web as part of package requirements. Thanks for the good support as always guys. Andrew.

11 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 10. Dezember 2019 um 10:25 Uhr -0800 schrieb Mark Sapiro: >The underlying issue here is probably ><https://bugs.python.org/issue32330>, but that knowledge doesn't help >us. We need to get rid of the offending message in the message store. >The first step is in mailman shell. Note the paths /opt/mailman/mm/bin/ >and /opt/mailman/mm/var/ will need to be adjusted. Thanks for this information. Ubuntu's mailman stores the messages below /var/lib/mailman3/messages. The "mailman" command is in the $PATH. >This should print the file name and Message-ID-Hash (two lines the same) >for each message in the messages directory until it prints only one line >followed by the UnicodeEncodeError exception. That list line is the file >name/Message-ID-Hash of the offending message. I've execucted that code, but it does not cause an exception at all. It quietly runs through. I've attached the transcript of the shell session to this mail. With a little crude use of grep(1), however I found my held message in WQ/ZS/WQZSFFJLVMWQHMG4VYKGXJEKQVQXVK67. Does the messages directory contain only held messages? I've looked at some messages and all of these I looked at were spam. The directory structure contains 40 messages in total, accumulating to 480 KiB disk space. If required, I can zip that directory up and e-mail it to you for inspection. >DELETE FROM message WHERE message_id_hash = xxx; As the exception you expected did not occur, I didn't do this yet. I can make a database and directory backup and then run it, though. Should I try? I assume after this I should also delete the respective files from the messages/ directory? >As of Mailman core 3.3.0 there is a 'mailman notify' command designed to >be run periodically by cron to notify owners/moderators of prnding requests. I did receive an e-mail to the list owner address that told me that the e-mail from my incorrect e-mail address "requires approval". That was the first time I received such an e-mail. In parallel, on the incorrect e-mail address, I received the notification for moderator approval. Marvin -- Blog: https://mg.guelker.eu

5 years, 5 months

[MM3-users] Re: Shorted Subjects in Mailman

by Stephan Krinetzki

Stephen J. Turnbull wrote: > Stephan Krinetzki writes: > > We have been experiencing the following problem lately: When a user > > sends a mail with an unusually long subject to a mailing list, this > > subject is shortened. > > Is this being observed by all subscribers? Especially subscribers > with various different mail clients? Do you observe this when you > look at the "original message"? (Different clients describe this > function in different ways, but most mail clients allow you to look at > all of the header and body text exactly as sent, with no formatting). Yes, it doesn't matter which cleint they are using. The cutted subject was reported multiple times. > > Here are the two examples: > > Original subject: "[SAV-LINUX] Notice from Sophos Anti-Virus on > > lx1bcms-storage.physik.rwth-aachen.de" (82 characters long) > > Subject in Mailman: "[edv-support][SAV-LINUX] Notice from Sophos > > Anti-Virus on" (57 characters long) > > By design, Mailman does not truncate the subject, it folds it to > multiple lines to conform to Internet mail standards which state that > lines should be no longer than 78 characters. So, including adding the > "edv-support" tag, a stock Mailman installation should be changing: > Subject: [SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" > (all one line) to (two lines, split after "on" with the space starting > the second line[1]: > Subject: [edv-support] [SAV-LINUX] Notice from Sophos Anti-Virus on > lx1bcms-storage.physik.rwth-aachen.de" > A mail client that conforms to Internet mail standards might either > display it exactly that way, or it might unfold it to a single line, > or it might unfold it, then refold it to match the user's display > width. > Of course if you look at the original text and there is no second > line, that's a Mailman bug. And here we are: There is no second line! The subject header only contains the displayed value, no new line or other things. But the mailman subject line is intact. Only the regular Subject: is truncated. So, i have to file a bug report, right?

2 years, 10 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Odhiambo, Yes, trying to. Mark, I'll review your suggestions. Thanks. On Wed, Jul 3, 2024, 12:52 Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to keith1christian(a)gmail.com >

11 months

[MM3-users] MM3 shunting mails

by Anders Nilsson

I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using RPMs from https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/ I do have problems with some lists occasionally going into some kind of shunt mode, where alla mails sent to them gets shunted. In the Mailman log I get entries for each shunted email: Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.4/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 121, in process process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist) File "/usr/lib/python3.4/site-packages/zope/component/hookable.py", line 33, in __call__ return self.__implementation(*args, **kw) File "/usr/lib/python3.4/site-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib64/python3.4/site-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.4/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 And so far my Google-fu hasn't been good enough to give me any useful answers to why this happens. If I dump one of the pickles using qfile I cannot see any complaints. Most of the times, if I remove and recreate a failing list and run unshunt the shunted emails get processed and sent. Anyone seen something similar? Regards, Anders Nilsson -- Anders Nilsson, Ph.D. <andersn(a)control.lth.se> Dep. of Automatic Control, Lund University Phone: +46 (0)46 222 87 94, Fax: +46 (0)46 13 81 18 Mob: +46 (0)703 22 57 67

8 years, 2 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, I can't find any log entry which indicate a problem with this subscription request. The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. The token is found in the pended table: +-----+------------------------------------------+---------------------+ | id | token | expiration_date | +-----+------------------------------------------+---------------------+ | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | +-----+------------------------------------------+---------------------+ These are the relevant entries in the pendedkeyvalue table: +------+--------------+-------------------------------------+-----------+ | id | key | value | pended_id | +------+--------------+-------------------------------------+-----------+ | 1130 | type | subscription | 115 | | 1131 | list_id | "********************" | 115 | | 1132 | email | "***********************@*********" | 115 | | 1133 | display_name | "" | 115 | | 1134 | when | "2021-01-06T16:17:38" | 115 | | 1135 | token_owner | "moderator" | 115 | +------+--------------+-------------------------------------+-----------+ Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Thanks in advance, Eric On Friday, January 15, 2021, 11:42:47 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

Thank you, Mark. By "However, all of the above can be avoided without any DMARC changes by enabling bounce probes." Do you mean that I can get rid of the 'From' mangling, which has been a frequent source of embarrassment because the list address is captured and reused by type-ahead when sending non-list messages and those messages instead going to 1000 subscribers. __ Allan On 2/1/23, 09:59, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/31/23 22:32, Allan Hansen wrote: > Hi all, > > Apparently Google just started to get very aggressive about DKIM settings. Some hundreds of my subscribers have had their subscriptions disabled because of Google's bounces. > > I tried to 'Enable' some of them, expecting that their bounce scores would be reset, but when I list the users, the bounce scores are still 5. > > Please advise. Will enabling them without the bounce score being reset just cause the server to disable them again. Yes, Google has started enforcing a policy which is effectively DMARC p=reject even for senders whose domains don't publish DMARC p=reject or quarantine. To avoid this issue, you may need to set DMARC Mitigate unconditionally to Yes as well as DMARC mitigation action to Replace From: with list address if it isn't already. As far as enabling without resetting the bounce score is concerned, I think you are correct that they will just be disabled again on the next bounce. This is a bug and should be fixed. However, all of the above can be avoided without any DMARC changes by enabling bounce probes. in the [mta] section of mailman.cfg, set ``` verp_probes: yes ``` Since the probe is sent From: the list's domain, it should pass googles SPF and DKIM checks and not bounce. -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/56WVO6NIOGOBAOOS2B4YCIDJN7VCIXTF/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 4 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Mark Sapiro wrote: > On 1/26/22 00:11, Stephan Krinetzki wrote: > > After we enabled the "slow query log", we got in the postgresql database the following output: > > 2022-01-25 12:49:41.538 CET [16126] LOG: unexpected EOF on client connection with an open transaction > > 2022-01-25 15:34:36.047 CET [16864] LOG: duration: 30760.028 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > 2022-01-25 15:34:36.047 CET [3900] LOG: duration: 9372.471 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > 2022-01-25 16:42:07.243 CET [3900] LOG: unexpected EOF on client connection with an open transaction > > > > > > Pretty sounds like a database problem? > > The unexpected EOF is because the gunicorn worker timed out and was killed. > There are two DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > transactions because the first one timed out. These came from > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.p... > The accept action is processed and ultimately we get to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.p... > and that in turn is doing the DELETE at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.p... > There must be some kind of database locking causing this, but I have no > clue as to what it might be. If you haven't done so, I would stop all > the mailman services and the database server and then start them again. > I don't know if that would help, but it might. We did this and nothing changed. I even tried to lookup up potential DB locks, but they are no locks in the database. Side note: Wie have a 37GB big Database with ~4.000 Mailinglists and ~70.000 addresses > > sometimes the log (mailmansuite.log) show us this error > > That too is from the gunicorn worker timing out and being killed. Okay. We already set the timout of the gunicorn process of the mailmancore higher (6 Min) I think there is a communication problem in the chain: apache -> uwsgi -> mailmancore/API ->database but i can't dig deeper there. Let me know if i should provide more details or logs

3 years, 4 months

[MM3-users] Mailman Ubuntu 24.04 install notes

by Andrew Hodgson

Hi. Just thought I would write up my installation experiences on Ubuntu 24.04 following this guide as much as possible: Virtualenv Installation - Mailman Suite 3.3 documentation (mailman3.org)<https://docs.mailman3.org/en/latest/install/virtualenv.html> Ubuntu packages: I'm trying not to install dev packages on the server if possible and managed to get away with the following packages: python3-psycopg2 sassc lynx python3-venv python3-certbot-nginx postgresql exim4-daemon-light Creating the venv: python3 -m venv --system-site-packages --symlinks venv This creates the venv referencing the system packages as well which is useful as some of the dependencies for Mailman are met by the Certbot and python3-psycopg2 packages. Using Pip I installed the following packages: pip install mailman mailman-hyperkitty mailman-web Postgres: I ran into an issue with the database after running `mailman-web migrate`. This was because a newer version of Django pulled in from the above command needed some tables creating in the public schema, and from Postgres 15 (Ubuntu ships with Postgres 16) that isn't allowed by default. I solved this by making the Mailman role owner of the mailman database. I am aware of discussions around whether its best to do this or give explicit perms on the databases to allow all on the public schema, but I decided to go with this option. My Postgres commands are now: sudo -u postgres psql create database mailman; create user mailman with encrypted password '[...]'; ALTER DATABASE mailman OWNER TO mailman; Django: I ran into an issue with a newer Django installation not allowing any form submission, was getting a 403 returned due to CSRF protection failure. I resolved this by adding this line to my local Settings.py: CSRF_TRUSTED_ORIGINS=['https://lists.domain.com'] I moved back to using Gunicorn for the backend server, the instructions on this were spot on. I've had this error before but the mailman-web compilemessages command failed because of missing msgfmt. I think I can pull this in from Ubuntu packages but may need to update installation docs with this extra package requirement. Search: I continued to use Woosh as I'm running a very low traffic site and that is what comes with Mailman-Web as part of package requirements. Thanks for the good support as always guys. Andrew.

11 months, 1 week

[MM3-users] Re: Mailman 3 Status Update Please?

by Barry Warsaw

Hi David, On Jan 31, 2017, at 06:24 PM, ddw David Wilson wrote: >I have been eagerly looking forward to a comprehensive install script for >Mailman3 since the originally stated target date of Aug Sept and wondered if >any new dates have been proposed? We're very close I think. Core is essentially done. I've made a pass through the Postorius, HyperKitty, and mailmanclient milestones and there's not a lot left, but both of the former two could probably use some help getting to the finish line. I'm going to spend some time on mailmanclient. gitlab.com is down right now so I can't provide any links. >Furthermore, I wonder if either of the two following projects have been >proposed for Google Summer of Code applications: > >1) the afore mentioned comprehensive install script for Mailman3 on various >targeted hardware; and/or; We've been debating about the best way to do this, and right now the only thing we can agree on is that mailman-bundler needs to go away. ;) We know we want distro packages, but that's a longer term prospect. I suspect we want some container-based deployment options too, and I know that there are several dockerfiles floating around, but none are currently blessed officially. It's possible we won't have one single official deploy method, but instead we'll encourage experimentation and help to promote the best options in the short term, perhaps with adoption in the longer term. I don't have a more solid answer than that, but I highly encourage anybody who has an interest in this to come to mailman-developers@ and help us get there. >2) updated for Python 3 and the latest P3 compatible Django utilities for >archiving and email list collection, along with any new appropriate features? That's a great question for the Postorius and HyperKitty folks. Core is Python 3 already (and only), while P and HK should support both on Django. mailmanclient is and will remain bilingual. >Many thanks in advance for all your efforts in this extremely worthwhile OSS >project. Thank! We have a small team of core developers, but they are really awesome. And of course, we welcome new contributors! Cheers, -Barry

8 years, 4 months

[MM3-users] Re: Unable to get Postfix to bounce messages to non-existent lists

by skenny＠scss.tcd.ie

Thanks Mark Sapiro and Stephen J. Turnbull for your responses. Re the output of mailq - this was initially confusing (to me anyway). The diagnostic for the message stuck in the queue was "connection timed out", but the IP listed was the Postfix mail server's not Mailman's. At a guess, Postfix was trying to send the message to Postfix's local domain after it failed to LMTP it over to the Mailman server, and was unable to do that too. Since I posted yesterday, I hit upon a solution that seems to work ... I set relay_recipient_maps to the same value as transport_maps, so that the relevant config lines now look like this: transport_maps = regexp:/var/mailman-data/postfix_lmtp local_recipient_maps = $alias_maps relay_domains = regexp:/var/mailman-data/postfix_domains relay_recipient_maps = regexp:/var/mailman-data/postfix_lmtp This seems to have the desired effect (and, I hope, no unintended consequences). If I fire a message at a non-existent list now, I get an immediate bounce message in my mail client - "Recipient address rejected: User [nonexistent-list(a)lists.scss.tcd.ie] unknown in relay recipient table". No longer is the message loitering in the Postfix queue. The Postfix documentation for relay_recipient_maps says "Optional lookup tables with all valid addresses in the domains that match $relay_domains. [...] Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from the table lookup." For transport_maps, it says "Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination). " Postfix does what we want now: bounce the message is the list name isn't found in relay_recipient_maps, forward it on to the Mailman server via LMTP (transport_maps setting) if it is. Re Stephen J. Turnbull's comment about the patch allowing Postfix to query Mailman's database and more, I think I'll hold off for the moment, but good to know. We will reconfigure when it makes it into an official release (we're using Maxking's Docker images). As ever I'm really grateful for your taking the time to respond, many thanks. Kind regards.

1 year, 3 months

[MM3-users] Re: clarifying configuration

by Mark Sapiro

On 6/30/20 11:29 AM, trewtus+200629maitr(a)gmail.com wrote: > Hey Team, > I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg > > [logging.template] > level: debug > > But that doesn't work for me. For example, after using that `mailman conf` doesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add > > [logging.smtp] > level: debug > > Invoking `mailman conf` will reflect that new loglevel. The settings in the logging.template section set defaults for the other logging.* sections. In particular, the logging.debug section sets `level: info` so setting [logging.template] level: debug will not affect the setting for logging.debug. See mailman/config/schema.cfg which is augmented by mailman/config/mailman.cfg and by your own mailman.cfg. > This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing. > > For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the `mailman conf` output. Why would that be? Because you have installed the Debian/Ubuntu package and that setting is specific to that package and probably only defined in their local mailman.cfg. The reason you don't see it in `mailman conf`, is it's broken. Without a `-s/--section` argument, it only lists sections defined in schema.cfg. See <https://gitlab.com/mailman/mailman/-/issues/736>, <https://gitlab.com/mailman/mailman/-/merge_requests/666> and <https://pythonhosted.org/lazr.config/lazr/config/docs/usage.html>. If you do `mailman conf -s logging.debian` you'll see it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Social signup?

by Duane Raymond

Thanks Stephen, With support to dip in on how to do this, I would hope it is the start of a series of contributions to the platform :-) My starting point these days is asking chatGPT how to add the functionality. The response looks convincing but often has some glaring errors in it...but at least it helps me narrow down where I start and give me an idea of the steps/complexity of the task. I'll jump over to the developers list when I start this (I'm about to travel for a week to run an annual event in Oxford - so the far removed from programming)...but which chatGPT suggested so far was 1. Extending postorius/signups.html with a loop to get the configured social login providers PLUS adding a csrf_token field to the form 2. Modifying postorius/views.py (which doesn't seem to exist but there is a postorius/views folder) - so perhaps this is views/urls.py So with dev community support and chatGPT support I should be able to muddle through it! Probably as practice I'll convert a recent simple Flask app I built into django to get familiar with Django as a framework before I dip into postorius & hyperkitty Cheers, Duane On Wed, 15 Mar 2023 at 08:26, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Duane Raymond writes: > > > I'll dip into the code in the next weeks and see if I can figure > > out how to add it (using the example of the login page) > > Welcome to the team! :-D > > I doubt you need any Python code; I think you just need to add buttons > in HTML in the page template, and an explanation of where the user > will end up (probably not where they expect ;-). I forget how this > works, but you might even be able to ensure a redirect to where they > expect to go in pure Django templating language. If not, it will > likely need a straightforward one-line change to the view. > > If all that makes sense to you, great! If not, feel free to ask > questions, here, or perhaps more appropriately on > mailman-developers(a)python.org. > > Steve >

2 years, 2 months

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by gordon＠dickens.com

Hi Mark, The command "pip install --force-reinstall mailman" ran successfully. Then, the command "/opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg" generated the following errors: >Traceback (most recent call last): > File "/opt/mailman/venv/bin/mailman", line 33, in <module> > sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ > return self.main(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1077, in main > with self.make_context(prog_name, args, **extra) as ctx: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 943, in make_context > self.parse_args(ctx, args) > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1644, in parse_args > rest = super().parse_args(ctx, args) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1408, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 2400, in handle_parse_result > value = self.process_value(ctx, value) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 2362, in process_value > value = self.callback(ctx, self, value) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 95, in initialize_config > initialize(value) > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/core/initialize.py", line 229, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/core/initialize.py", line 187, in initialize_2 > config.db = getUtility(IDatabaseFactory, utility_name).create() > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/database/factory.py", line 57, in create > database.initialize() > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/database/base.py", line 117, in initialize > self.engine = create_engine( > ^^^^^^^^^^^^^^ > File "<string>", line 2, in create_engine > File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned > return fn(*args, **kwargs) # type: ignore[no-any-return] > ^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/engine/create.py", line 601, in create_engine > dbapi = dbapi_meth(**dbapi_args) > ^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/mysql/pymysql.py", line 75, in import_dbapi > return __import__("pymysql") > ^^^^^^^^^^^^^^^^^^^^^ >ModuleNotFoundError: No module named 'pymysql' What to do now? Thanks, Gordon

1 year, 6 months

[MM3-users] Implementing threading [was: hyperkitty failed to create a thread]

by Stephen J. Turnbull

tlhackque writes: > I believe that for threading to work more or less reliably, the > thing to do is to look at the 'References' header. > > That should give you the thread in order, and allow any message > received out of sequence to be put in the proper location in your > display. This is more difficult than it seems, since References is not defined for mail as far as I know (it's a netnews concept originally, and RFC 5337 is a netnews-specific RFC). Although it is adopted by most mail clients, there's no guarantee of strict conformance. In mail, In-Reply-To is more reliably present, but of course asynchronicity means you have no guarantee of a complete set of all links. Even if all clients conform to the netnews RFC, you still need to create the full tree (full conformance to RFC 5537 means it will be a tree), and break ties between branches in some arbitrary way to create a total order. It's worse if you *don't* have conformance from all clients: you can get a DAG or even something that isn't even a DAG. So, even today, you can't assume a well-behaved ancestry graph. > 'References' should be a superset of Reply-To (which is at most 1 > Message-ID), so you only need Reply-To if there is no References - or to > handle a client that doesn't obey the RFCs. I suppose HyperKitty uses References (it works for messages that have proper Message-IDs ;-), but I don't know what algorithm it uses. Might be worth looking into, as well as considering a more Postelian parsing of Message-IDs. Specifically, take the field body, unfold it, strip leading and trailing whitespace and leading "<" and trailing ">", and whatever's left is the message ID. Alternatively, strip everything that's not atext or "@" (including inside the purported Message-ID). This won't break any RFC 5537-valid Message-IDs, but might identify two different, nonconforming Message-IDs as the same (too bad if they can't take a joke!), or identify a nonconforming message with a conforming one (<sad_emoji />. Thoughts? Steve

6 years, 3 months

[MM3-users] Re: [SOLVED] Re: how to unhold a hold message from a nonmmeber in hold list.

by Odhiambo Washington

On Fri, Apr 21, 2023 at 1:27 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 21/4/23 a las 11:03, Guillermo Hernandez (Oldno7) via Mailman-users > escribió: > > > > El 21/4/23 a las 10:37, Odhiambo Washington escribió: > >> > >> > >> On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via > >> Mailman-users <mailman-users(a)mailman3.org> wrote: > >> > >> I'm having troubles with Django and cannot access to web admin. > >> > >> I need to unhold a message while figures out what is happening. > >> > >> Searching the mailman cli help commands didn't help me. > >> > >> Anyone who knows how to unhold a message, please? > >> > >> > >> TBH, I find it a lot easier to fix the web UI than mess with the > >> python shell :-) > > > Well... I found you where right. Messing with the CLI seems a nightmare > to me. > > The problem with the UI seems solved. What I finally have done: > > Detected that the module "asgiref" was in a different version that the > server (with all the same config) that is working. pip upgraded it. This > didn't work, but it raised new error messages (about hyperkitty parsing > messages) > > Installed pip-review and upgraded ALL python modules with pip-review > --local --interactive > > (Re)upgraded all mailman3 packages with > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty uwsgi mod-wsgi > > Restarted apache24 > > And then all begun to work. > > Thanks a lot for your advising and help. > Do you now see why a virtualenv style of setup will save you lots of grief? :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 1 month

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by kelly.close＠lrewater.com

Holy Schmoly Robert - this was it for me, thank you for this post! This is very unfamiliar territory for me (the virtual host stuff) and I had to do some self-teaching before I could follow where to put the lines of code you referenced. But the internets are replete with examples and I'm a quick learner so for others who might be complete virtual host newbs like myself, here's a little more detail on how I applied this fix to resolve the 403 Forbidden error I was getting: (after making sure the archiver keys matched and the base url was set to my actual domain and my ip was added to the MAIL_FROM variable) The mailman3-full install for Debian provides you with an apache.conf file (in the deployment folder) and creates a symbolic link to it in the apache virtual hosts configuration folders (etc/apache2/conf-available). So that is nice - that is already taken care of. What I wasn't sure about was where to add the new <VirtualHost 127.0.0.1:80 [::1]:80></VirtualHost> section provided by Robert. In the /etc/apache2/sites-available folder just two of the conf files are linked into the /sites-enabled folder so I figured it was one of those. One of them is clearly the ssl conf settings and the other, well I guess it's the default one you have before you install ssl on your server. I opted to add the new section to that one (000-default.conf). I created the section at the top and just added the 2 lines to it for ServerName and Include, and a note to explain why it was there. After saving the file and exiting, I reloaded apache2. <VirtualHost 127.0.0.1:80 [::1]:80> # non-https port 80 listener for localhost so hyperkitty can archive ServerName localhost Include conf-available/mailman3.conf </VirtualHost> What a nice surprise too that all 6 billion test messages I sent trying to get this to work showed up in the archive! :-) And actually that WAS a nice surprise because this is a live and active server and several messages had already come in since I deployed it this morning so those are now in the archives as well. Time to go play outside. Happy first day of summer to all! ~Kelly

4 years, 11 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Stephen J Turnbull

From: "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> To: ceo(a)sartrack.nz Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Mailman3 / Exim4: Router fails In-Reply-To: <168469116281.118014.2976538609194809676(a)mail.mailman3.org> References: <168469116281.118014.2976538609194809676(a)mail.mailman3.org> X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta34) "kale" 5b7378119a27 XEmacs Lucid (x86_64-apple-darwin21.6.0) --text follows this line-- ceo(a)sartrack.nz writes: > But it fails with this: > MM3_LISTCHK=/var/lib/mailman3/lists/${local_part}@${domain} For reasons I do not understand, although Mailman 3 keeps list configurations in the RDBMS, when it creates a list it *also* "touches" a directory for that list in the directory $var_dir/lists. (If I remember correctly, these are empty. It's a real directory, not "virtual".) Since I already knew how to search for the lists/$LIST/config,pck file used by Mailman 2, I used the same method for Mailman 3. $var_dir is set somewhere near the top of mailman.cfg. I don't know where to find that file in your installation, it's often in /etc/mailman3. Compare $var_dir with MM3_LISTCHK. If the prefix /var/lib/mailman3 is not the same as $var_dir, check that the lists directory exists in $var_dir and is populated with the list posting addresses you expect. Then fix up MM3_LISTCHK to match. If anything looks suspicious, feel free to ask, even if it works. Later you wrote: > mailman3 create templist(a)sartrack.nz templist.lists.sartrack.nz (?) > I tried to create it as: > create templist(a)sartrack.nz templist(a)sartrack.nz > but it would not accept that. I believe that's because "mailman create" wants the posting address and the list ID. The posting address is a mailbox@domain address as usual, but the list ID is defined to be "dots only" so you can tell the difference. Normally the list ID just swaps "." for "@" in the posting address, but if you ever need to change domains, it saves your users hassle if their mail client understands the list ID. That can stay mailbox.domain even though you have to change the posting address to mailbox@newdomain. So create templist(a)sartrack.nz templist.sartrack.nz should work. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

2 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Thank you Abhilash, I will read the instructions again and come back to you if something comes up! Have a great day. El jue., 20 jul. 2017 a las 14:09, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi Rafael, > > On Wed, Jul 19, 2017, at 01:49 PM, Rafael Mora wrote: > > Hello, > > > > What are the suggested steps in order to install the web UI ?? > > I haven't read through this entire thread but I understand that you are > having problems with multiple configuration files for Core and setting > up the Web UI. > > The installation guide at docs.mailman3.org should now have a > "Pre-Installation Guide" and another new section called "Configuring > Mailman 3". Please make sure than you read both of them along with the > "Installation Guide" They have more information about how to setup > Mailman 3 after you have installed them so that it becomes function. > > Also, your original question's answer can be found there. It has > instructions about how to setup your Django project, which is the what > the Web frontend for Mailman 3 is based on. > > > > > Thanks > > > > El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< > > kylerichardson2(a)gmail.com>) escribió: > > > > > There must be another config file being picked up. Have a look at the > > > mailman.cfg search order explained here [1]. > > > > > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name > mailman.cfg' > > > to be sure. You'll want to delete any in the search path and then rerun > > > 'mailman info'. > > > > > > [1] > > > > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > > > > > -Kyle > > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/19 8:47 AM, Odhiambo Washington wrote: > > > > If you could include the missing steps that you left out then I could > > possibly be able to follow the steps :-) > > > Please help me understand what steps are missing and I will try to > provide the information. Okay. At the installation stage, you say the following: "I already had some things set up in /opt/mailman including a git subdirectory containing clones of the GitLab mailman, mailmanclient, mailman-hyperkitty, hyperkitty, django-mailman3 and postorius projects. On the third server I have added mailman-suite because I use the settings.py from that project as the basis for mine." Please assume that the reader is a newbie to python3 virtualenv and give the details of the commands they need to execute to (a) clone all the projects needed and (b) create the virtualenv. The next steps are: mkdir /opt/mailman/mm Then you say "I then created a /opt/mailman/mm directory and within that a Python 3.6 virtualenv" What happens here is something that needs clarification, because you are specific about "python3.6". I have googled and realized that one has to be specific about the python version they want to use in their virtualenv as shown here -> https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… exact command to execute to create the /opt/mailman/mm/venv exact command to execute to activate virtualenv From there, I think the newbie can follow and fumble till they come up with a working MM3 site. Come to think of it, your steps kind of look clearer than most that I have encountered. I do understand that there are only a few people working on the MM3 development, which I think is the reason there still isn't a document similar to the ones included with MM2.1x source under doc/ However, if your steps here are polished a little, they can possibly become one such doc. I think MM3 docs would come with three options - virtualenv option, docker option and package option. Installing from source seems like something not easily doable. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 5 months

[MM3-users] Re: Message IDs

by Philip Colmer

On Fri, 15 Oct 2021 at 11:05, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Philip Colmer writes: > > > The situation we're seeing is that if person A sends an email from a Google > > account to Mailman 3 and receives the (modified) post back from Mailman 3, > > the message ID is not being changed. Google's behaviour then is not to show > > that message to the user because it thinks it is the same message that the > > user sent out. > > Google is broken, but they're not going to change. No argument here. > > > > Since Mailman 3 is modifying the message, it ought to have a different > > message ID. > > I don't think your posters would agree that Mailman is the author of > their posts. I'm not sure that the message ID identifies the author, does it? I've just done a quick test of sending myself an email and then replying to it. The original email has a message ID of CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com In the reply, the following headers are present: References: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> In-Reply-To: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> Message-ID: <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> Would it be reasonable for Mailman 3 to use "References:" to keep the original Message ID and then add a new Message ID? I think that what Mailman 3 is doing is similar to forwarding the email. If I forward an email, again the headers change: References: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> In-Reply-To: <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> Message-ID: <CAKTSSTjwP1_J_f5mL03dhebVWNPQwL5tXORxuEXK4_8XpHvtpA(a)mail.gmail.com> > The IETF has addressed the issue of non-identical but equivalent > messages with the Resent-Message-ID field (and in general the whole > suite of Resent-* fields. Mailman doesn't appear to be adding that header. Would that be an acceptable solution instead of the one I suggested above? I appreciate your view that Google is broken. I'm just trying to find an acceptable solution to the end-user perception of "I've sent an email to the list but I haven't received a copy back". That is going to be a big issue/headache for us. Thanks. Philip

3 years, 7 months

[MM3-users] Re: More Mailman releases!

by Abhilash Raj

Hello, I missed one important merge request in django-mailman3, so here are a couple more versions. I've released Django-mailman3 1.3.11 and Mailman-web 0.0.8 (which requires django-mailman >= 1.3.11). Gitlab releases are available here: Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.8 Django-mailman3: https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.11 I have also yanked mailman-web 0.0.7 since that'll cause spurious errors due to change in session serializer. Abhilash On 10/22/23 00:05, Abhilash Raj wrote: > Hello Everyone, > > I am pleased to announce several new releases for GNU Mailman project. > Thanks to all the contributors for making these releases possible! > > 1. Postorius 1.3.10 [1] > 2. Hyperkitty 1.3.8 [2] > 3. Django-mailman3 1.3.10 [3] > 4. Mailman-web 0.0.7 [4] > > All the releases are published to PyPI and you can find links to all the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 > [2]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 > [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst > > Do note that for Postorius, I released 1.3.9, but I forgot to update > dependency metadata to require `django-mailman3>=1.3.10` (which is > required for the new bootstrap 5 upgrade across packages) and so I also > released Postorius 1.3.10 just after. > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > If you find any issues, you can report them at the respective bug > tracker for the projects. The links to issue trackers are available > at https://docs.mailman3.org/en/latest/. > > Finally, similar to Mailman Core, note that PyPI doesn't accept > signatures anymore so each packages' release page now has the tarball > uploaded to them along with the signature: > > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 > Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 > Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 > -- thanks, Abhilash Raj (maxking)

1 year, 7 months

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Brian Carpenter

On 7/14/20 1:06 PM, Mark Sapiro wrote: > It's confusing, but after adjusting that setting, you need to restart > Mailman core, not gunicorn. > > If you are running a gunicorn service, that is what is providing WSGI > support for Django (Postorius and/or HyperKitty). You may be using > gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is > not the gunicorn we are considering here. > > Regardless of what you use to provide WSGI support for Django, Mailman > core uses gunicorn to support the REST API, and that is the gunicorn > affected by the settings in the gunicorn.cfg pointed to by > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > If, with the above configuration, you do `ps -fwwA|grep runner=rest` you > will see something like: > > mailman 20582 20561 0 01:21 ? 00:00:16 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20722 20582 0 01:21 ? 00:01:19 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20725 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20726 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20727 20582 0 01:21 ? 00:01:50 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > > The first of these, pid 20582, is Mailman's actual REST runner. The > other 4 with parent pid 20582 are the 4 gunicorn worker processes forked > from the REST runner. > > It's the REST runner or Mailman core that needs to be restarted to pick > up that change. Thanks Mark. I knew that once but forgot it. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

4 years, 10 months

[MM3-users] docker mailman-core mailman3 image not responding on port 8024

by bob B

Ok, I took a step back and started fresh... So the issue appears to be that mailman-core docker image is not replying on port 8024. I did a packet capture and it shows (172.23.01 is the gateway for the docker network on the host, 172.23.03 is the IP of mailman-core when I did the capture) *************************************** 1 2021-08-16 14:15:14.865053 172.23.0.1 172.23.0.3 TCP 74 34066 → 8024 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=985607751 TSecr=0 WS=128 2 2021-08-16 14:15:14.865084 172.23.0.3 172.23.0.1 TCP 54 8024 → 34066 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0 *************************************** The above show the docker host sending/relaying mail to mailman-core, but mailman-core does not acknowledge on port 8024. The images are up i.e *************************************** 58923db6fb9f maxking/mailman-core:0.3 "docker-entrypoint.s…" 26 minutes ago Up 25 minutes 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core *************************************** Docker yamel has the port setup (8024) *************************************** services: mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core . . ports: - "127.0.0.1:8001:8001" # API - "127.0.0.1:8024:8024" # LMTP - incoming emails networks: mailman: *************************************** I can nc to the ports for docker web & 8001 on core and they are listening But 8024 is not responding *************************************** #>docker-mailman-host]# nc -v 172.23.0.4 8000 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.4:8000. ^C #>docker-mailman-host]# nc -v 172.23.0.4 8080 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.4:8080. ^C #>docker-mailman-host]# nc -v 172.23.0.3 8001 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.3:8001. ^C #>docker-mailman-host]# nc -v 172.23.0.3 8024 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connection refused *************************************** Docker logs show postfix is up on mailman-core *************************************** sudo docker logs mailman-core List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------+---------+----------+------------+------------+--------------------- mailmandb | mailman | UTF8 | en_US.utf8 | en_US.utf8 | postgres | mailman | UTF8 | en_US.utf8 | en_US.utf8 | template0 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + | | | | | mailman=CTc/mailman template1 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + | | | | | mailman=CTc/mailman (4 rows) Postgres is up - continuing Using Postfix configuration Found configuration file at /opt/mailman/mailman-extra.cfg HYPERKITTY_URL not set, using the default value of http://mailman-web:8000/hyperkitty *************************************** Any ideas is there anything else I can do to troubleshoot? Is the issue with the mailman-core image?

3 years, 9 months

[MM3-users] Docker mailman3 delete social logins, did something change?

by bob B

I want to remove the social logins from mailman3 in docker. I found this info https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… but the link to the default shows *************** INSTALLED_APPS = [] DEFAULT_APPS = [ 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ] ***************** However when I go to the bug https://github.com/maxking/docker-mailman/issues/283 it shows ********* INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ******** The two examples are different so what should it be? I tried to add it in both ways and when I do I get bad gateway and he mailman website is broke. I have not setup any domains yet, just setup the admin password,. For example this breaks my website cat /opt/mailman/web/settings_local.py ALLOWED_HOSTS = ['127.0.0.1','localhost','REDACTED','REDACTED','REDACTED','REDACTED','REDACTED'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'REDACTED' EMAIL_PORT = 25 INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ************************************************************************* And I have even removed anything? What should my /opt/mailman/web/settings_local.py look like?

3 years, 8 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

I was able to instantiate the class AND get the expected three objects from it - pre_hook, post_hook, and resource. >>> from mailman_customizations.hooks import MailmanCustomizations >>> instance = MailmanCustomizations() >>> dir(instance) ['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__implemented__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__providedBy__', '__provides__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'post_hook', 'pre_hook', 'resource'] I know Abhilash Raj is probably well versed in this from statements made elsewhere, so I've added them in the CC field. Abhilash Raj, any ideas? Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 10:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler? On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't > necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

1 year, 7 months

[MM3-users] Re: Mailman 3 Status Update Please?

by Barry Warsaw

I have maybe just a little bit to add to what Abhilash has said. On Jul 20, 2017, at 14:47, ddw David Wilson <ddw.256(a)gmail.com> wrote: > 3. A design/plan from an inside expert perspective stating costs, time > and resources to implement the plan, incorporating crowdfunding to > pay for project. > 4. As a backup incentive to the crowdfunding plan might be the offer of > an expert to set up a system for each significant amount donated, > say US$1,000, such as might be accomplished by an SSL session on the > target computer/server after the user has specified all necessary > detail as required in a template. We do actually have a Mailman donation fund, set up through the Free Software Foundation. After an initial seed, and some occasional funds from GSoC, we have a little bit of money that we’ve used to help GSoC students attend Pycon, where most of the in-person hacking happens. https://my.fsf.org/civicrm/contribute/transact?reset=1&id=22 I encourage everyone who loves Mailman (of any version) to donate! You help us and the FSF. > In summary, I guess what I am requesting is an overview forecast by half year period and out for the next two years? > > Please share the big picture? I would encourage everyone who wants a turnkey Mailman 3 system to help Abhilash and others to test and contribute to his docker image project. That’s really the officially sanctioned best way to deploy Mailman for those who don’t want to “roll their own”. There are also folks in Debian working on getting all the packaging set up for Mailman 3. Right now there are some dependencies that are working their way through the process first. Hopefully, we’ll also start to see Mailman 3 become available on other Linux distros too. Each of the subprojects has their own rough set of plans, and the best way to help is through the various Gitlab projects under this umbrella: https://gitlab.com/mailman For Core, I’ve started to milestone some issues and merge proposals to 3.2. One big project that I’d love to see gain more traction is Lemme, our authenticating REST proxy. We just haven’t had much collective resources to spend working on it. https://gitlab.com/mailman/lemme Cheers, -Barry

7 years, 10 months

[MM3-users] Re: Problems after update to mailman 3.3.7

by Danil Smirnov

Hi Guillermo, We've faced the same issue and already reported it: https://gitlab.com/mailman/mailman/-/issues/1044 I would not recommend anyone using MySQL/MariaDB database engine upgrade to the latest version yet. With my best regards, Danil Smirnov Mailman3.com On Tue, Dec 6, 2022 at 4:32 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > I've getting the most strange behaviour after update to last releases. > In one of my mailman3 servers, the messages doesnt reach for some lists > (the five last ones) > > the update have not showed any error but in the var/data for the lmtp > and vmap postfix files mailman does not create aliases for that last 5 > lists. Any message addressed to them is returned with a "no such user" > error. > > If I create a new list the system or restart mailman runners it shows > this error: > > Generating MTA alias maps > /usr/local/lib/python3.9/site-packages/pymysql/connections.py:799: > UserWarning: Previous unbuffered result was left incomplete > warnings.warn("Previous unbuffered result was left incomplete") > > I did a CHECK TABLE on mailinglists table but all seems ok. > > I tried reinstalling PyMySQL, but has no effect. (well, I tried > reinstalling all) > > It seems to me that something is preventing creation of that aliases, an > then the that last five lists are unreachable. > > I have no clue of what to do now and I'm driving crazy. > > Some direction to look for will be much apreciated. > > Thanks in advance. > > P.S.: I can access via postorius/hyperkitty to the archives of the lists > that are unreacheable. > > > -- > > ___________________________________________ > 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. > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to danil(a)smirnov.la >

2 years, 6 months

[MM3-users] how to migrate mailing lists to a new domain using mailman 3

by C. Souza

In a few days my current domain will be disabled (it is out of my control) and I would like to know how to migrate the mailing lists to the new domain name. As a solution I added a new domain in mailman 3 and created a script that replicates the lists in this new domain. To forward the emails received by the old lists, the script removes the members and adds the email of the new list. Is there a fashionable way to do that? Also, one problem that I don't have a solution is the archive of the old lists. How to bring them to the new ones? Thanks for your help. My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: Package Version ------------------- ---------- 1 aiosmtpd 1.2.4 2 alembic 1.5.3 3 arrow 0.17.0 4 asgiref 3.3.1 5 atpublic 2.1.2 6 authheaders 0.13.0 7 authres 1.2.0 8 bleach 3.3.0 9 blessed 1.17.12 10 certifi 2020.12.5 11 cffi 1.14.4 12 chardet 4.0.0 13 click 7.1.2 14 cmarkgfm 0.5.2 15 cryptography 3.3.1 16 decorator 4.4.2 17 defusedxml 0.6.0 18 Django 3.0.12 19 django-allauth 0.44.0 20 django-appconf 1.0.4 21 django-compressor 2.4 22 django-extensions 3.1.0 23 django-gravatar2 1.4.4 24 django-haystack 3.0 25 django-mailman3 1.3.5 26 django-picklefield 3.0.1 27 django-q 1.3.4 28 djangorestframework 3.12.2 29 dkimpy 1.0.5 30 dnspython 2.1.0 31 docutils 0.16 32 falcon 2.0.0 33 flufl.bounce 3.0.1 34 flufl.i18n 2.0.2 35 flufl.lock 3.2 36 gunicorn 20.0.4 37 HyperKitty 1.3.3 38 idna 2.10 39 importlib-resources 5.1.0 40 lazr.config 2.2.3 41 lazr.delegates 2.0.4 42 mailman 3.3.2 43 mailman-hyperkitty 1.1.0 44 mailman-web 0.0.3 45 mailmanclient 3.3.2 46 Mako 1.1.4 47 MarkupSafe 1.1.1 48 networkx 2.5 49 nose 1.3.7 50 oauthlib 3.1.0 51 packaging 20.9 52 passlib 1.7.4 53 pip 21.0.1 54 postorius 1.3.3 55 psycopg2-binary 2.8.6 56 publicsuffix2 2.20191221 57 pycparser 2.20 58 Pygments 2.7.4 59 PyJWT 2.0.1 60 pyparsing 2.4.7 61 python-dateutil 2.8.1 62 python-editor 1.0.4 63 python3-openid 3.2.0 64 pytz 2021.1 65 rcssmin 1.0.6 66 readme-renderer 28.0 67 requests 2.25.1 68 requests-oauthlib 1.3.0 69 rjsmin 1.1.0 70 robot-detection 0.4 71 setuptools 39.2.0 72 six 1.15.0 73 SQLAlchemy 1.3.23 74 sqlparse 0.4.1 75 typing-extensions 3.7.4.3 76 urllib3 1.26.3 77 uWSGI 2.0.19.1 78 wcwidth 0.2.5 79 webencodings 0.5.1 80 wheel 0.36.2 81 Whoosh 2.7.4 82 zipp 3.4.0 83 zope.component 4.6.2 84 zope.configuration 4.4.0 85 zope.deferredimport 4.3.1 86 zope.deprecation 4.4.0 87 zope.event 4.5.0 88 zope.hookable 5.0.1 89 zope.i18nmessageid 5.0.1 90 zope.interface 5.2.0 91 zope.proxy 4.3.5 92 zope.schema 6.0.1 -- Carlos Souza

2 years, 10 months

[MM3-users] Re: Problem with docker and css

by tlhackque

On 05-Jul-17 06:14, Alexander Klotz wrote: > Hi Abhilash & everybody, > > thanks for your help! We got the configuration working now, see below > - proxy modules have to be loaded here to make it work. > > Regards, > Alex > > <VirtualHost *:443> > ServerAdmin webmaster@localhost > ServerName mailman.example.org > Alias /static /opt/mailman/web/static > Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico > ProxyPassMatch ^/static/* ! > ProxyPass / http://172.19.199.3:8000/ > ProxyPassReverse / http://172.19.199.3:8000/ > <Directory /> > Allow from all > Require all granted > </Directory> > <Directory /opt/mailman/web/static/hyperkitty/img/> > Allow from all > Require all granted > </Directory> > ErrorLog ${APACHE_LOG_DIR}/error.log > LogLevel warn > CustomLog ${APACHE_LOG_DIR}/access.log combined > # ssl config here ... > </VirtualHost> > I'm glad you got your server working. Thank you for posting your configuration. I see one problem with what you posted: You probably don't mean "ProxyPassMatch ^/static/* !", but rather "ProxyPassMatch ^/static/.* !", although "ProxyPassMatch ^/static/ ! " would also be correct. (You are missing a period before the asterisk.) The first argument to ProxyPassMatch is a regular expression: "/*" means "zero or more '/'", but you want '/' followed by anything. ".*" means "zero or more <any character>". (Including the '/' prevents something like '/staticlibrary' from matching.) But since you don't try to match anything after the '/', the '.*' is unnecessary. (You'd need it for something like "^/static/.*\.(?:css|png|js)$", where you want to match some arbitrary text followed by something definite.) Apache doesn't do a good job of documenting its regular expression syntax, so here are a couple of notes: Apache uses the Perl Compatible Regular Expression library (with a couple of extensions). See http://www.pcre.org for full documentation; the regexps are almost exactly Perl, which is documented here: http://perldoc.perl.org/5.10.1/perlre.html. The differences are documented here: http://www.pcre.org/current/doc/html/pcre2compat.html - but unless you are an advanced regex user, you're unlikely to encounter them. The differences are with respect to Perl V5.10 (the current version of Perl is 5.26). One of the extensions is !, which inverts the match criteria. Apache does document that. The configuration posted is for Apache 2.4 +.

7 years, 11 months

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Darren Hart

On Wed, May 25, 2022 at 08:10:39AM -0700, Mark Sapiro wrote: > On 5/23/22 11:11, Darren Hart via Mailman-users wrote: > > When attempting to visit the hyperkitty archives list overview for one of my two lists: > > > > Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ > > > > The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). > > > > The following appears in /var/log/mailman3/web/mailman-web.log: > > > > > > ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to > > Traceback (most recent call last): > ... > > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get > > raise self.model.DoesNotExist( > > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > > > Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. > > > > The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. > > > > The hyper kitty archives for a second list on this Mailman3 instance is working correctly. > > > > How can I fix this view of the archives? Or how can I get more information on what might be failing? > > > I'm not sure if this will help, but try running your django management > command with arguments `runjob recent_threads_cache`. Note that this will be > run daily if you are running the Cron Jobs for Mailman Web. See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=perio… Thank you Mark. These are in cron, but I ran this (and all the runjobs hourly,daily, etc. options), checking after each. The failure persisted until I restarted mailman3-web, and then it started working again. I'm not sure what combination of cron jobs and restarting resolved the issue, but it's running again. Thanks again. -- Darren Hart Ampere Computing / OS and Kernel

3 years

[MM3-users] Mailman upgrade results in page not found error

by Andrew Hodgson

Hi. Just doing the Mailman suite upgrade on my small installation I use for test purposes. Steps include: Run backup script Stop services Mv venv venv-old python3 -m venv --system-site-packages --symlinks venv source venv/bin/activate pip install -U pip pip install mailman mailman-hyperkitty hyperkitty postorius whoosh deactivate ./bin/Django-admin collectstatic ./bin/Django-admin migrate At this step I got an error regarding the import of URLs, a quick Google suggested this was because the new venv has upgraded to Django 4.0. I downloaded the urls.py from the mailman-web Git repo (I should migrate to this at some point I know) and replaced my version with this one. This allowed the migrate to run correctly. Once services were up everything worked as expected except for the web page. If you go to https://lists.hodgsonfamily.org you get a Postorius page not found error, however if you click on the Mailman logo you get to the correct place. I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? Urls.py: # -*- coding: utf-8 -*- # Copyright (C) 1998-2016 by the Free Software Foundation, Inc. # # This file is part of Postorius. # # Postorius is free software: you can redistribute it and/or modify it under # the terms of the GNU General Public License as published by the Free # Software Foundation, either version 3 of the License, or (at your option) # any later version. # # Postorius is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for # more details. # # You should have received a copy of the GNU General Public License along with # Postorius. If not, see http://www.gnu.org/licenses/. from django.conf.urls import include from django.contrib import admin from django.urls import path, reverse_lazy from django.views.generic import RedirectView urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), ] Thanks. Andrew.

2 years, 7 months

[MM3-users] Re: Migration from old server to new server failed

by Helio Loureiro

Hi, Thanks for the tip. Now I can see hypperkitty available. But I'm still seeing some errors. Feb 22 14:16:56 2024 (2062795) HyperKitty failure on http://127.0.0.1/archives/api/mailman/archive: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> (500) Feb 22 14:16:56 2024 (2062795) Could not archive the message with id < AM6PR07MB592539392144457915580AF992752(a)ABCD.externaldomain.com> Feb 22 14:16:56 2024 (2062795) archiving failed, re-queuing (mailing-list cn-lratci-op.mailman3.domain.com, message < AM6PR07MB592539392144457915580AF992752(a)ABCD.externaldomain.com>) Feb 22 14:16:56 2024 (2062795) Exception in the HyperKitty archiver: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Feb 22 14:16:56 2024 (2062795) Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Which might be a minor issue since now I can access the web page and login is working again. Thanks a lot! Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 22 Feb 2024 at 11:31, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Thu, Feb 22, 2024 at 12:49 PM Helio Loureiro <helio(a)loureiro.eng.br> > wrote: > >> Hi, >> >> Any suggestions here? >> > > [snip] > > >> > I'm using uwsgi via apache: >> > > Okay. > > >> > (venv) mailman@new-mailman3 ~ (v3.1.1)> more >> > /etc/apache2/conf-enabled/mailman3.conf >> > Alias /mailman3/favicon.ico /local/mailman/web/static/favicon.ico >> > Alias /mailman/favicon.ico /local/mailman/web/static/favicon.ico >> > Alias /favicon.ico /local/mailman/web/static/favicon.ico >> > Alias /mailman3/static /local/mailman/web/static >> > Alias /mailman/static /local/mailman/web/static >> > Alias /static /local/mailman/web/static >> > >> > <Directory "/local/mailman/web/static"> >> > Require all granted >> > </Directory> >> > >> > <IfModule mod_proxy_uwsgi.c> >> > ProxyPass /mailman3/favicon.ico ! >> > ProxyPass /mailman/favicon.ico ! >> > ProxyPass /favicon.ico ! >> > ProxyPass /mailman3/static ! >> > ProxyPass /mailman/static ! >> > ProxyPass /static ! >> > ProxyPass /mailman3 >> > unix:/local/mailman/var/uwsgi.sock|uwsgi://localhost/ >> > ProxyPass /mailman >> > unix:/local/mailman/var/uwsgi.sock|uwsgi://localhost/ >> > #ProxyPass /mailman3 http://localhost:8000/ timeout=180 >> > #ProxyPass /mailman http://localhost:8000/ timeout=180 >> > #ProxyPass / http://localhost:8000/ timeout=180 >> > </IfModule> >> > > Mostly I can only see the "Page not found" error. So let's try just the > standard config (using TCP socket) as documented and see. > In the documented configuration, I can see that you do not have > "ProxyPreserveHost On" in your configuration, but to be honest, I am not > sure of that is the problem. > Let's try doing this the standard way, according to the documentation at > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… > : > Let's also log and analyze what Apache says. Use the config below, please. > > ``` > Alias /static "/local/mailman/web/static" > <Directory "/local/mailman/web/static"> > Require all granted > </Directory> > > ErrorLog ${APACHE_LOG_DIR}/mm3-error.log > CustomLog ${APACHE_LOG_DIR}/mm3-access.log combined > LogLevel info > > <IfModule mod_headers.c> > RequestHeader unset X-Forwarded-Proto > <If "%{HTTPS} =~ /on/"> > RequestHeader set X-Forwarded-Proto "https" > </If> > </IfModule> > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > ``` > > Did you say you're logging both Mailman Core and Mailman Web to > /var/log/mailman.log? Can you please separate them for clarity? > Is your settings.py the same as the one at > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > with the exception that you're using MySQL? > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] >

1 year, 3 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/4/21 2:15 PM, Bryan Loniewski wrote: > Based on your import21 comments, I'm realizing the issue may be caused by multiple runs of import21. I have been (although I've stopped it for some time now) running import21 nightly to sync up my Mailman3 list data with Mailman2. I've been doing the same for archiving as well. import21 was never intended to be run more than once for a particular list. > I've noticed now that some lists have duplicate acceptable alias entries (looks to be like <number of aliases> x <number of import21 runs>) and the same goes for *_these_nonmembers entries. That's not surprising. There may be other attributes that are duplicated or otherwise corrupted from running import21 multiple times. > Is this a symptom of running the old(er) import21 command pre-3.3.2? Will the 3.3.2 import21 work as expected w/out the duplications if I was to clear out the appropriate lists col data (i.e., is it okay to run import21 multiple times)? I tried to figure out if there were any other duplicative data, but did not come across any. Is there more that I'm missing? I don't think the 3.3.2 changes to import21 will avoid the duplications. I think there will be other issues as well. For example, if there are changes in membership or ownership on the 2.1 list import21 will probably pick up the additions but not the deletions. The intended use of import21 is for a one time migration of a MM 2.1 list to MM 3. It is not intended to somehow sync parallel MM 2.1 and MM 3 lists. If the idea is to run import21 to create a test MM 3 list while still running the MM 2.1 list in production, I would suggest to run import21 once and then when ready for the final migration, delete the MM 3 list, create a new, 'empty' list and run import21 on that. As far as hyperkitty_import is concerned, it can be run multiple times. If --since is not specified, it will only consider messages newer than the newest in the existing archive, and in any case will skip duplicate Message-IDs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Upgrade-path from Ubuntu18LTS to recent mailman release

by Ruth Ivimey-Cook

Just for the record, I did exactly this change a while ago (because I was having issues with locking of the file, IIRC). I thought I could dump the database using sqlite's export to sql tool and then import with minimal fuss into mysql, but it didn't work straight away -- too many differences in sql types and styles. I thought to edit the dump file into mysql's style, but this resulted in other errors. In the end I found it necessary to create a blank database using the mysql backend, then dump only the data (no table or index ops) into that. I can't quite remember if any fixup was needed but if so it was very minor. It would be nice to have a migrate DB function within mailman (i.e. a utility that created the tables in a new db from current, then copied the data using the ORM tools, so as to avoid low-level sql issues). Ruth On 13/05/2022 09:25, Stephen J. Turnbull wrote: > Stefan Bauer writes: > > > As i only use sqlite, i will give it a try to just copy the database files. > > OK, if sqlite works for you, I think there's no hurry (I don't know of > any severe performance issues for small sites, nor security issues). > > However, I still recommend considering a migration to one of the more > powerful RDMBSes like PostgreSQL or MySQL for the long run, because > Mailman installations can easily scale to sizes where sqlite becomes a > performance bottleneck. It's not that hard to do, because Mailman > (mostly via the Django and SQLAlchemy ORMs, but I think there's some > "raw" SQL in Mailman) sticks to the common core for SQL, so you can > dump the database as SQL commands and then restore it in another SQL > database without too much fiddling. You may need some fiddling, such > as the database-specific initializations such as setting the encoding > for text items and ensuring that sized columns are wide enough, but > mostly that will be taken care of by the ORMs. -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 2 Jul 2020, at 8:38, Florian Schulze wrote: > On 30 Jun 2020, at 8:22, Florian Schulze wrote: > >> On 29 Jun 2020, at 23:40, Mark Sapiro wrote: >> >>> On 6/29/20 1:38 AM, Florian Schulze wrote: >>>> Hi! >>>> >>>> After upgrading to HyperKitty 1.3.x I get the following error for >>>> qcluster: >>>> >>>> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >>>> 300, >>>> in pusher >>>> task = SignedPackage.loads(task[1]) >>>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>>> 31, >>>> in loads >>>> serializer=PickleSerializer) >>>> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >>>> line >>>> 38, in loads >>>> return serializer().loads(data) >>>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>>> 44, >>>> in loads >>>> return pickle.loads(data) >>>> AttributeError: Can't get attribute 'process_task_result' on >>>> <module >>>> 'hyperkitty.tasks' from >>>> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >>>> >>>> How do I recover from that? It seems like there are still persisted >>>> tasks in the qcluster queue using the old code from 1.2.x with the >>>> old >>>> locking implementation. >>> >>> Have you stopped ans started qcluster since upgrading? >> >> Yes >> >>> Are you running the Django periodic jobs? >> >> They were disabled because of the errors (someone else did the >> upgrade). I have enabled them again and will watch it and report >> back. > > The cronjobs seem to work fine, no errors so far. > > The queue doesn't seem to change at all. In "qmonitor" there is > nothing listed and the statusline remains the same at > ORM default Queued 303(118) > Success 100 Failures > 0 I managed to figure out how to inspect the queue in the admin interface. I just deleted all the repeatedly failing tasks and ran all cron jobs. I hope it is fine now. Regards, Florian Schulze

4 years, 11 months

[MM3-users] Re: Message-Footer after migrating to Mailman3

by christopher.claus＠tgcamberg1848.de

Hi Abhilash, excuse my delay, i was out-of-order in the last weeks. > You want the URL at which Postorius (postorius) is available from Core (mailman-core container). The default for that in the container images is set to http://mailman-web:8000. Does that not work for you? I changed the container-names (but not the hostnames) an probably i set the POSTORIUS_TEMPLATE_BASE_URL to the container-name and not to the hostname. > If you want to verify, you want to exec into the Core’s container (docker exec -it mailman-core bash) and see if you can curl the URL from inside there. If you are using the default docker-compose-postorius.yaml then there is a /etc/hosts entry created by docker for the mailman-web container, hence http://mailman-web:8000 works there (but it won’t work on the host, since docker doesn’t modify the host’s /etc/hosts). I modified the compose-file since i have a separate container for a database and i use a seperate network for all my other container. The consequence was, that i do not have a fix subnet. I tried to change all occurences of ip-adresses to hostnames. Therefore i stripped these parts in the compose-file. Currently, there is not entry for mailman-web in the hosts file of mailman-core. I did not find any place in your config and scripts, were this file is written. At which place, this should be done? An interesting point: mailman_core has an entry to itself (with own ip) in /etc/hosts and mailman_web also. I think, this is not correct, isnt it? But nevertheless a curl of the URL from core to web works without error message. > There might also be a bug in play here which would cause such connection refused errors when subscribing/unsubscribing when there was a template configured for the list. Is that the case for you or are you seeing always when trying to send the email (which would imply that the Web container simply isn’t reachable from Core). I thought about the situation, that all my lists where migrated from mailman 2. Many of the have footer- and header-messages, automatic replies which are not shown in the template section of the list. Is a recreation in mailman3 a good option in this situation? Best regards, chrclaus

3 years, 8 months

[MM3-users] Re: Docker or virtualenv?

by Tim Cutts

I’ve used docker on my setup. I have been wondering about this though, it causes me to need to run an AWS VM continuously to run my mailing lists, and that probably isn’t really necessary. I do sometimes wonder whether docker might be a better approach and run it under ECS, so I no longer have to look after a VM. Even better, MM3 is just a bunch of python functions at the end of the day, and it doesn’t *need* to be running continuously. Mailing lists are, more or less by definition, event driven. Has anyone considered whether it’s feasible to turn it into a bunch of Lambda functions with a serverless database behind it? Tim Sent from my iPhone > On 31 Dec 2022, at 08:35, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > On Sat, Dec 31, 2022 at 11:15 AM Johannes Rohr <johannes(a)rohr.org> wrote: > >> Dear all, >> >> I have noticed that Ubuntu's current LTS no longer contains packages for >> mailman2 and its mailman3 packages are incomplete. So, prior to >> upgrading the server, I will have to migrate from mailman2 / distro >> packages to mailman3 installed either in virtualenv or docker. I have >> got zero experience with virtualenv and some experience with Docker. >> Overall, the docker method looks easier. >> >> Is docker the default method by now? <mailman-users-leave(a)mailman3.org> > > > The default method is virtualenv, IMHO. > I rarely see talk about Docker, but it also doesn't matter which option you > choose to go with as long > as you are able to run the core and any other bits that you require. I > think at the end of the day you > still end up using the settings.py and config files, albeit in a convoluted > way :) > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to tim(a)thecutts.org

2 years, 5 months

[MM3-users] Mailman-web stop responding.

by Paul Rubin

I was trying to administrate a list and discovered that mailman-web was unresponsive. I have tried stopping and restarting it. The error logs update for the startup, but not when anything connects to localhost:8000. The last entry in uwsgi.log was two hours ago and nothing has been added since. I tried both lynx http://localhost:8000 and telnet to http://localhost 8000 and GET request instantly closes the port and logs nothing. As far as I can tell both mailman and postgres are working fine. This is what logs on startup. ==> uwsgi-error.log <== *** Starting uWSGI 2.0.22 (64bit) on [Sun Apr 14 10:45:51 2024] *** compiled with version: 13.2.1 20230912 [revision b96e66fd4ef3e36983969fb8cdd1956f551a074b] on 05 October 2023 13:37:28 os: Linux-6.5.4-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e) nodename: mail.rubinsoftware.com machine: x86_64 clock source: unix detected number of CPU cores: 4 current working directory: / detected binary path: /opt/mailman/venv/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! your processes number limit is 15246 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8000 fd 8 Python version: 3.11.5 (main, Aug 31 2023, 07:57:41) [GCC] PEP 405 virtualenv detected: /opt/mailman/venv/ Set PythonHome to /opt/mailman/venv/ Python main interpreter initialized at 0x7f2c3d709d58 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 250128 bytes (244 KB) for 4 cores *** Operational MODE: preforking+threaded *** added /etc/mailman3/ to pythonpath. WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x7f2c3d709d58 pid: 16064 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 16064) spawned uWSGI worker 1 (pid: 16065, cores: 2) spawned uWSGI worker 2 (pid: 16067, cores: 2) [uwsgi-daemons] spawning "/opt/mailman/venv/bin/mailman-web qcluster" (uid: 72 gid: 67) 14:45:52 [Q] INFO Q Cluster white-green-ten-mobile starting. 14:45:52 [Q] INFO Process-1:1 ready for work at 16072 14:45:52 [Q] INFO Process-1:2 ready for work at 16073 14:45:52 [Q] INFO Process-1:3 monitoring at 16074 14:45:52 [Q] INFO Process-1 guarding cluster white-green-ten-mobile 14:45:52 [Q] INFO Process-1:4 pushing tasks at 16075 14:45:52 [Q] INFO Q Cluster white-green-ten-mobile running. What should I do to diagnose further?

1 year, 1 month

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 7:44 PM, Alan So wrote: > I just notice that if I send an email to a list with a Cc header broken into multiple lines and the pair of double quotes are put in different lines, the email addresses afterwards will be wrongly rewritten. > > For example, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> tl;dr It is not valid to fold a header inside of a quotes string. First of all, the above is invalid. Presumably the address is intended to be "ABC DEF (XYZ)" <name(a)example.com> RFC 5322, sec 2.2.3 says in part: "The general rule is that wherever this specification allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP." and the definitions in sec 3.4 say in part: address = mailbox / group mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr angle-addr = [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr display-name = phrase In this case, the quoted-string "ABC DEF (XYZ)" is a phrase which is the display-name and the only places where comments or folding white space are allowed is immediately preceding the "<" or following the ">" surrounding the addr-spec. Folding in the middle of the quoted string is not allowed. Were there no quotes, e.g. ABC DEF (XYZ) <name(a)example.com> Then ABC DEF is a phrase and (XYZ) is a comment and folding between DEF and (XYZ) would be allowed > It will become the following after going through the mailing list: > > CC: XYZ <"ABC DEF"@mail.server.name> Which is clearly wrong, but GIGO. > It seems that Outlook often split the To/Cc header into multiple lines and they often add double quotes to the full name of the users. Is the rewriting of Cc header handled by Mailman's code or another Python class? I haven't looked at the code to see exactly what's responsible here. I do note that adding double quotes around a display name is not only allowed, but is required if the display name contains "specials". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Thu, Dec 15, 2022 at 5:00 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > (sorry: I sent this yesterday afternoon, but from a unsuscribed mail > account) > > El 14/12/22 a las 19:04, Odhiambo Washington escribió: > > > On Wed, Dec 14, 2022 at 8:33 PM Guillermo Hernandez (Oldno7) via > > Mailman-users <mailman-users(a)mailman3.org> wrote: > > > >> 1. The post-update script runs everything required. For the avoidance of > >>> doubt, here it is: > >>> <CUT> > >>> #!/bin/bash > >>> > >>> set -e > >>> > >>> BINDIR="/opt/mailman/mm/bin" > >>> CONFDIR="/opt/mailman/mm" > >>> SETTINGS="settings" > >>> DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" > >>> STATIC_DIR="$CONFDIR/static" > >>> DEBUG="False" > >>> > >>> set -x > >>> > >>> if [ "$DEBUG" == "False" ]; then > >>> mkdir -p "$STATIC_DIR" || : > >>> "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput > >> --verbosity 0 > >>> "$DJANGO_CONTROL_SCRIPT" compress > >> Odhiambo, I had problems in the compress process in the last updates. I > >> would make sure the process is running ok. I had to disable the off line > >> compression for this matter. > >> > > @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> that sounds a bit > > non-standard, but care to explain what additional arguments you passed to > > django-admin compress? > > I had to set compression off in the update to 3.3.7 because I was > reproducing the same error as when I updated to 3.3.6. My guess is the > problem you have now is about the same problem and you cannot see > because you ran it in a script. > > I reported that in > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… In my case I do not get any errors so I think this is unrelated. I just seem to have a problem with the CSS files when accessing the archives. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Digest Formatting

by Mark Sapiro

On 11/7/20 9:08 AM, Stephen J. Turnbull wrote: > > I thought there was a way to trigger immediate distribution of a > digest immediately, but I guess I'm remembering that from Mailman 2. > Neither the Postorius management interface nor the core documentation > suggests there's such a trigger in Mailman 3. There is nothing in the web UI or REST, but the `mailman digests` command can send accumulated digests for one or more named lists or all lists unconditionally or only if the list's digest_send_periodic is set to True. see `mailkman digests --help` for details. > > 2) I have customized list:member:digest:header, but am not seeing > > the custom text where I thought it should be. The documentation > > seems to imply that both list:member:digest:header and > > list:member:digest:footer surround each message in the digest > > Which documentation do you mean? As far as I know (Mark will have > authoritative information if I'm wrong), the digest header and footer > appear at the top and bottom of the *whole* digest message (ie, once > each per digest), not surrounding or in the bodies of the component > messages. Steve is correct. The layout is as follows The masthead from the list:member:digest:masthead template. The digest header if any from the list:member:digest:header template. The table of contents. The individual messages. The digest footer from the list:member:digest:footer template. For the MIME digest, these are all separate MIME parts and the individual messages are message/rfc822 parts within a multipart/digest part. For the plain text digest, the digest is one text/plain part containing the above formatted par RFC 1153 And in another post, mailman(a)manygoodideas.com wrote: > I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks. This already exists, it is list:member:digest:footer. Your confusion seems to be because you think the list:member:digest:header template and list:member:digest:footer template are prepended/appended to each individual message in the digest which would not make sense and is not the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Templates

by David Krantz

On Sat, Sep 23, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Have you tried restarting/reloading whatever dbm (MySQL, PostgreSQL, ?) > you are using? No, that would have been strange to me; the table in the database was up to date. But now I tried that, I got no effect this time but I probably could set up a better test. I also had another problem [solved]: I get the error message "Multiple rows were found for one_or_none" when I try TemplateManager.get(name, context) for the list. There is only one matching row in the templates table so something is fishy with the ORM. This occured when I changed to the previous uri value. As the database does not have any duplicates in the templates table I suspect either a broken join or that the cache retains the old value. The traceback looks like this in the mailman shell: >>> tm.get('list:member:regular:footer', 'test.example.com') Traceback (most recent call last): File "<console>", line 1, in <module> File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/template.py", line 98, in get contents = cache_mgr.get(actual_uri) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/cache.py", line 125, in get CacheEntry.key == key).one_or_none() File ".../venv-3.5/lib/python3.5/site-packages/SQLAlchemy-1.2.0b2-py3.5-linux-x86_64.egg/sqlalchemy/orm/query.py", line 2814, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Workaround: Delete cached files in .../var/cache and run delete from file_cache in postgresql. Then that works again. The culprit was that the file got cached twice so there is a bug in the cache function. I used the ITemplateManager-util in the shell to cause the problem. >> 2. the $user_delivered_to and $user_email do not expand for some >> reason. Known problem? > > > These require that the list delivery be personalized. See > <http://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/outgoing.h…>. > That explains things. Thank you! Now I got two footers, first one without personalisation and one personalised. Interesting. best regards // David

7 years, 8 months

[MM3-users] Re: Mailman3 in dockers on EC2 - running out of memory and puking ev.ry.where.

by Abhilash Raj

On Tue, Apr 9, 2019, at 2:34 PM, roger.hislop(a)is.co.za wrote: > Hi all -- really need some help. I'm tech literate, but definitely not > a sysadmin or dev. > > I'm following the tutorial at "Olay's Farmland" at > https://www.olay.xyz/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > which seems to be a clone of the same content here > https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ The right place to get help regarding these guides would be the author of the posts, which AFAIK, have no affiliation with Mailman Core Team. On a (very) quick glance, it seems fine. > Easy enough to get most of the way ... set up EC2 instance, configure > SES and add DNS settings with DKIM etc. Set up Postfix, test it. All > working groovy. > > I run through the how to all the way through setting up the containers > and firing it up. This is where things start to get funky. > > Once the docker-compose is run, I run "curl > http://172.19.199.3:8000/postorius/lists/" to test. First time it said > it couldn't connect to database. So I nuked and restarted from scratch. > Second time it said the same thing... was reading around the place and > tried again, and then reran that curl and it worked -- gave me html > from a page. But the VM started running slowly --taking forever to > follow keypresses. > > Eventually became unresponsive. So I rebooted the machine via AWS > console, and docker ps showed only the postgres db running. > docker-compose ps shows > Name Command State > Ports > ------------------------------------------------------------------------------------------ > docker-mailman_database_1 docker-entrypoint.sh postgres Up > 5432/tcp > mailman-core docker-entrypoint.sh maste ... Exit 255 > 8001/tcp, 8024/tcp > mailman-web docker-entrypoint.sh uwsgi ... Exit 255 > 8000/tcp, 8080/tcp > > So rebuilt the container -- same thing. It looks and feels like its > running out of memory. > > I used the compose file from > https://gist.githubusercontent.com/Yexiaoxing/833bfcc5d3e4e0c06a8b7f0bac7c4… (with appropriate edits). How much memory do yo have in your VM? Have you tried using a bigger VM? thanks Abhilash

6 years, 1 month

[MM3-users] Shorted Subjects in Mailman

by Stephen J. Turnbull

Stephan Krinetzki writes: > We have been experiencing the following problem lately: When a user > sends a mail with an unusually long subject to a mailing list, this > subject is shortened. Is this being observed by all subscribers? Especially subscribers with various different mail clients? Do you observe this when you look at the "original message"? (Different clients describe this function in different ways, but most mail clients allow you to look at all of the header and body text exactly as sent, with no formatting). > Here are the two examples: > > Original subject: "[SAV-LINUX] Notice from Sophos Anti-Virus on > lx1bcms-storage.physik.rwth-aachen.de" (82 characters long) > > Subject in Mailman: "[edv-support][SAV-LINUX] Notice from Sophos > Anti-Virus on" (57 characters long) By design, Mailman does not truncate the subject, it folds it to multiple lines to conform to Internet mail standards which state that lines should be no longer than 78 characters. So, including adding the "edv-support" tag, a stock Mailman installation should be changing: Subject: [SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" (all one line) to (two lines, split after "on" with the space starting the second line[1]: Subject: [edv-support] [SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" A mail client that conforms to Internet mail standards might either display it exactly that way, or it might unfold it to a single line, or it might unfold it, then refold it to match the user's display width. Of course if you look at the original text and there is no second line, that's a Mailman bug. > Is there any way to work around this? If Mailman is folding the subject as described above, you'd have to patch the code, and maintain the patch across upgrades. I think the patch might be a little tricky because the code that does this is in the Python distribution, not in Mailman itself, if I remember correctly. Alteratively, get people to use clients that properly handle Internet mail. Asking people to change their mail clients rarely goes over well though. Regards, Steve Footnotes: [1] The mail standards permit splitting header lines only on whitespace under certain conditions, not at hyphens and other punctuation as normal in English text.

2 years, 10 months

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

by Onyeibo Oku

On Sat, 29 Oct 2022 18:21:06 +0900 "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: > > After series of SELinux file context labeling, setting the nis > > boolean, and a few custom policies, it resolved. Thank you for the > > responses (and your patience). > > Perhaps you could post these to our wiki (https://wiki.list.org) if > you don't consider them sensitive? > No problem. Although I suspect some of the Custom SELinux policies may be unnecessary, assuming I missed certain files/folders that require specific labels. I tried my best using the following pages: 1. https://www.systutorials.com/docs/linux/man/8-mailman_queue_selinux/ 2. https://linux.die.net/man/8/mailman_selinux > > 1. Will there be a conflict of resource (ports, threads, etc) > > running another instance [of uwsgi]? > > There can be. That's your problem, you need to configure each > application to use non-conflicting ports and locations (URL paths, if > the applications share externally-visible domains and ports). They > can also conflict over internal resources such as file locks and I/O > channels, but that depends on the specific applications. There are no > conflicts among Mailman suite applications if configured as we > recommend, but to know what conflicts might arise you need to explain > what other apps will be running, and how you plan to configure them. > I am not sure I understand what you mean by apps. Is that Django apps (./manage.py startapp app)? Do you mean a Django Project instead (./manage.py startproject app)? What I have here is an active website project (live) done on Django framework. It runs from a different virtual environment (venv). hence: mailman --> /opt/mailman/venv website --> /srv/website/venv (has a running uwsgi instance) > > In whichcase, it doesn't hurt to follow the doc to its logical > > conclusion? > > I don't understand what you mean by logical conclusion. > That is to follow the guide to the end of the page (disregarding the possibility of conflicts). This guide here: https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… --Onyeibo > _______________________________________________ > 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/

2 years, 7 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 11:33 AM, Mark Sapiro wrote: > On 10/29/20 5:23 AM, Brian Carpenter wrote: >> I have a list owner who had his subscription policy set to confirm. >> Apparently that was too hard for his list members to handle so he >> changed it to moderate only. If someone sent a subscription request that >> needed to be confirm, did not respond to it, and then tried subscribing >> again after the member policy changed to moderate, their 2nd >> subscription attempt still shows up in the confirmation queue. Is that >> normal behavior. My understanding is it is. Please let me know if I am >> wrong here. > > Are you certain that the request waiting confirmation is the second one > and not the first? Good point and I am not sure. I will try to note that if this pops up again. > > >> The real mystery here is when someone tried subscribing again >> (listname-subscribe@listdomain) hours after the subscription policy was >> changed to moderate and they still showed up in the confirm queue. How >> is that possible? I tested the list with two of my addresses and both >> showed up in the moderation queue as expected. As far as I can tell from >> the mailman logs, this was the person's first attempt at subscribing. > > I suspect it was not the first attempt and that the subscription waiting > confirmation was requested when the policy was confirm. The confirmation moderation notice had the date-time stamp that came a few hours AFTER the subscription policy was changed. Also I only saw one confirmation request sent out via Postfix' mail.log. I saw no other for this subscriber. Same thing with the smtp.log. I cannot duplicate this behavior when I try to subscribe. My subscription attempts went straight to moderation. > > The real question is if a user has a subscription waiting confirmation > and the policy is changed to moderate, is a second request rejected > because of the request waiting confirmation. If so, I think this is a > bug which should be fixed. > Do you think this is a bug with Mailman core or my system? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 19:36, Jan Eden wrote: > On 2022-11-27 08:01, Mark Sapiro wrote: > > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > > contents) are readable and writeable by mailman:mailman: > > > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > > > I fail to see where haystack tries (and fails) to create the directory. > > > FWIW, deleting threads is not a problem. > > > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > > add that user to the `mailman` group. > > That's what baffles me – uwsgi is run as the mailman user: > > mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini I tried setting permissions on /opt/mailman/fulltext_index to 777 temporarily, but the issue remained (as expected). It occurs in the Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > if self.use_file_storage and not os.path.exists(self.path): os.makedirs(self.path) where self.path is referenced, which is defined in line 110 (as part of the __init__ function): > def __init__(self, connection_alias, **connection_options): > super().__init__(connection_alias, **connection_options) > self.setup_complete = False > self.use_file_storage = True > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > self.path = connection_options.get("PATH") Unfortunately, I cannot see where the PATH key for connection_options is defined. - Jan

2 years, 6 months

[MM3-users] Re: Advice on migrating to Mailman 3

by Stephen J. Turnbull

Daniel Armengod writes: > Hello Christoph, > > > If we setup such a system, can we assume that it will silently operate > > without causing much administration work most of the time (like my > > nginx server)? Or is maintaining a Mailman 3 server a significant burden? > As with all things, it is easy once you've mastered it, and easy for > someone who /has/ mastered it to say it's easy :P A Mailman 3 server isn't hard to manage. It's the rest of the system that provides most of the challenges ;-) (including the challenges in configuring Mailman!) You can get pretty close to a turnkey system by using one of the Mailman containers Abhilash provides, but then you need to run Docker, and that's probably going to increase the spec of the hardware you need. Mailman 2 is much more self-contained than Mailman 3. You still need an MTA and a webserver that provides CGI, but that's all. > > The only problem is that our list runs on Mailman 2. We would like to > > move to Mailman 3 > Why? I'll echo this. We don't need to know (unless there's a specific technical challenge to Mailman 2 that you hope Mailman 3 can resolve, and then we can tell you whether Mailman 3 has it, will have it soon, or won't have it soon if ever), and don't really care (happy to help and all that). But you need to ask yourself that question because it's rarely a good idea to fix what ain't broke. And Mailman 3 is sure to become more robust, easier to install, and easier to migrate Mailman 2 lists over time. Don't do it until you forsee a near- future *need* to migrate, is my advice. If you're worried about Python 2's "end of life," especially about lack of security maintenance going forward, I wouldn't worry about that. Python 2.7 is a very robust, resilient, and secure in its internal operation. It's very unlikely that a Python-2-specific bug in a Mailman installation is how an attacker gets in. It's not going to need much maintenance. As a whole, Daniel's advice is excellent and worth studying. Steve

5 years, 3 months

[MM3-users] Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'

by Mark Sapiro

Putting this back on the list. On 5/19/21 9:46 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> ... >> Have you set >> ``` >> [mailman] >> sender_headers: ... >> ``` >> in mailman.cfg?, and if so, to what? > > We have not changed it: > > [mailman] sender_headers: from from_ reply-to sender > > According to the smtp.log, there was an envelope sender ("MAIL FROM:.."), which matched the From header. In the example I'm looking at right now, the sender was not a member of the list, but the Accept these non-members box in the list settings has a regexp that matches the sender's domain. In another example from this morning, to a different list, the envelope sender and From header match, and is a member of the list. > > I don't see any obvious reason or configuration setting that would make either address invalid. First of all, the discard has nothing to do with whether the sender has any connection to the list. It only says the message had no sender at all. Assuming the message had a From: with a syntactically valid email address, this discard should not occur. Also, if the envelope (MAIL FROM:) was a syntactically valid email address, this discard should not occur. The address is validated by mailman/email/validate.py by first splitting it into `local_part`, `@`, `[domain_parts]` where domain_parts are the `between dots` parts of the domain and then validating the local_part and domain with regexps defined per > # What other characters should be allowed? > _valid_local = re.compile("[-0-9a-z!#$%&'*+./=?@_`{}~]", re.IGNORECASE) > # Strictly speaking, both ^ and | are allowed and others are allowed in quoted > # local parts, but this can open the door to certain web exploits so we don't > # allow them. > _valid_domain = re.compile('[-a-z0-9]', re.IGNORECASE) > # These are the only characters allowed in domain parts. Does the From: local part or the MAIL FROM: contain any characters not in the [-0-9a-z!#$%&'*+./=?@_`{}~] class? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] MM3 Postfix FROM header issue

by eboltz＠lhtservices.com

Installed MM3 on Debian 11, followed the steps from the MM3 website. I'm running into issues with Postfix headers. I can only get postfix to send emails to/from the list if I set the sender_canonical_maps in the main.cf file. I don't want to have to use that as I'd like the recipient to receive the following in their email header: <Subscriber> via <List Name> <FROM:LIST@DOMAIN>. But if I do the sender_canonical_maps, then the <FROM:LIST@DOMAIN> and all email headers are overwritten by the maps email address. When I check the /var/log/mail.log without the sender_canonical_maps setting enabled, then the initial email sender is either rejected because 'Recipient address rejected: User unknown in virtual alias table' or '550-From header sender domain not verified (example.com) 550-On your sending > Verified senders page 550 verify the sender domain or email to be allowed to send' I have smtp_sasl_passwd_maps disabled, since I'm trying a different SMTP relay Here is my main.cf setup # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 2 on # fresh installs. compatibility_level = 2 # Mailman related settings #owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains #relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} hash:/var/lib/mailman3/data/postfix_domains # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level=may #smtp_tls_CApath=/etc/postfix/o365_smtp_cert.pem smtp_tls_security_level=may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = localhost alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain relayhost = [mail.smtp2go.com]:587 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 sender_canonical_maps = regexp:/etc/postfix/sender_canonical smtp_use_tls = yes smtp_always_send_ehlo = yes unknown_local_recipient_reject_code = 550 always_add_missing_headers = yes #smtp_sasl_auth_enable = yes #smtp_sasl_password_maps = hash:/etc/postfix/sasl/sasl_passwd smtp_sasl_security_options = noanonymous header_size_limit = 409600 default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 header_checks = regexp:/etc/postfix/header_checks mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128

1 year, 5 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Thu, 2021-02-25 at 13:24 -0800, Mark Sapiro wrote: On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. Hi Mark, Thanks for being patient with me. I'm still baffled but might have found the problem. I've done the above, to no avail. If I look at the queries being sent to mysql, I see stuff like this: 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP 174 Query SET sql_mode='STRICT_TRANS_TABLES' 174 Query COMMIT 174 Query SET AUTOCOMMIT = 0 174 Query SET AUTOCOMMIT = 1 174 Query SET AUTOCOMMIT = 0 I note that there is nothing about the charset, so something's clearly wonky. As previously stated, /etc/mailman3/mailman-web.py has the right thing: 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, but that latter is having no effect. I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset (but does have init_command), but I _think_ that's only about the package management system. So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py (which obviously has the right thing), but what about the .pyc file? # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc Binary file /usr/share/mailman3-web/settings_local.pyc matches # grep -i charset /usr/share/mailman3-web/settings_local.pyc # It ain't in the .pyc file. Am I overly optimistic that that might the be problem? If so, I'd be grateful if someone'd tell the newbie how to recreate that file without trashing something. Cheers, David

4 years, 3 months

[MM3-users] Re: New releases

by Abhilash Raj

On Thu, Jun 25, 2020, at 10:35 PM, Abhilash Raj wrote: > > > On Thu, Jun 25, 2020, at 8:59 AM, Danil Smirnov wrote: > > The issue has confirmed by other users: > > > > https://github.com/maxking/docker-mailman/issues/382 > > The issue seems to happen because the static files that are present at > the default staticfile locations aren't valid anymore and aren't > removed automatically on upgrades. > > You can run: > > sudo rm -rf /opt/mailman/web/static > > To remove them manually and then it should be re-created properly on > the next start. I'll try to work on a fix for this in some automated > fashion. Seems like I wasn't using the right options like Mark pointed out above. --clear flag will automatically remove the old files. I have created a PR[1] to fix it and will try to get it out with a new release soon. [1]: https://github.com/maxking/docker-mailman/pull/384 > > > > > вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > > > > > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > >>> COMPRESS_OFFLINE = True > > > >>> COMPRESS_ENABLED = True > > > >> > > > > > > > > These two are commented out. > > > > > > > > > Then compress shouldn't be trying to do anything. I can't explain what's > > > going on. > > > > > > -- > > > Mark Sapiro <mark(a)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 > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > _______________________________________________ > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

4 years, 11 months

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

by Onyeibo Oku

On Wed, 12 Oct 2022 17:52:47 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: Thanks Eggert and Sapiro. > > As Eggert suggests, see > https://docs.mailman3.org/en/latest/install/virtualenv.html and > follow that. I already started out on the above route. Its an adaptation because I am running Fedora. I had no problem with system-wide installations via dnf package management. However, some parts of the documentation does not add up. > You don't need to download the source from GitLab. > Following that doc will get the latest releases from PyPI via pip. > Those are still somewhat out of date - we really should make new > releases - so if you want the latest from GitLab, there are a couple > of ways to do it. Perhaps the easiest is to just run the various `pip > install` commands as documented and then upgrade Mailman core in your > venv with ``` > pip install --upgrade git+https://gitlab.com/mailman/mailman@master > ``` > and update the various mailman web packages with > ``` > pip install --upgrade git+https://gitlab.com/mailman/xxx@master > ``` > where xxx is mailman-web, mailman-hyperkitty, django-mailman3, > postorius, hyperkitty. I.e., run it 5 times, once for each value of > xxx. > I will come to this eventually (assuming that does not break things later). I aim to get it all working with regular pip packages first. I have installed mailman core already. Fedora expects mailman files to reside at /usr/lib/mailman. It appears to ship with a mailman unix user. I adapted to those system defaults. Now I observe that "su - mailman" gives me the proper prompt but .bashrc doesn't kick in. I still have to manually change to the virtual environment despite setting the automatic change in .bashrc. However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". Is this normal? Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which should correspond to "/usr/lib/mailman/mm/var/*" on my instance. However, I don't see any instructions on how to get the "/mm" folder and the associated sub-folders. I just have "/usr/lib/mailman" I am lost "pip list" within the venv environment confirms that I have "mailman 3.3.5". What am I missing? Regards Onyeibo

2 years, 7 months

[MM3-users] Re: Reply w/Email Clients - From: vs. Reply-To:

by Mark Sapiro

On 11/17/20 2:34 PM, j(a)manygoodideas.com wrote: > I'm setting up a new list, and a number of new list members are reporting a problem with replying to the thread. Their email clients seem to ignore the Reply-To: field and instead use from From: field. Are you saying that a 'reply' , not 'reply-all' will reply to the From: only and ignore Reply-To:? If so, the email clients that are doing that are badly behaved. I can't say they are non-compliant as RFC 5322 <https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.2> only says: The originator fields also provide the information required when replying to a message. When the "Reply-To:" field is present, it indicates the address(es) to which the author of the message suggests that replies be sent. I.e., Reply-To: is only a 'suggestion', but well behaved clients will follow it. > When they use Reply All, the email is addressed to both the From: and Reply-To:. Reply All should reply to the Reply-To:, To: and Cc: addresses and to From: if there is no Reply-To:. Whether Reply All should include From: if there is a Reply-To is not well defined. > Reading through previous threads here, I've tried a number of things: > > 1) DMARC mitigation action is "Replace From: with list address" > 2) For Alter Messages - Set "Reply goes to list" > > The goal is that we want a reply to go to the list, not the person posting. Since Reply-To seems to be ignored by some clients, I'm hoping there's a way to force the "From" field to become the list address. Thanks in advance for your suggestions! If Alter Messages -> Reply goes to list is set to Reply goes to list, Reply-To: will include the list posting address. What are the clients that ignore this? Complaints should go to the providers of those. Tf DMARC mitigation action is "Replace From: with list address", that will happen to messages to which DMARC mitigation action applies. If you want it to apply to all messages, set DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

--------------------------------------------------------------------------- First issue:Postfix v3.5.8 on RHEL 8. The below is from journalctl -xe: --------------------------------------------------------------------------- Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or directory I manually created the var_dir: /opt/mailman3/mm/var directory specified in the mailman.cfg file. How do I find out how to populate the postfix_domains.db files, and the postfix_lmtp.db file? --------------------------------------------------------------------------- Second issue: Postgresql authentication. PostgreSQL v10.23. --------------------------------------------------------------------------- I have this in the active mailman3.cfg file, where xxxxxxxxxx is the same complex password in the mailman3 config file: url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 Same password when I created the mailman3 and mailman3web users: create role mailman3 with encrypted password 'xxxxxxxxxx '; create role mailman3web with encrypted password 'xxxxxxxxxx '; psycopg2.OperationalError: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: Ident authentication failed for user "mailman3" --------------------------------------------------------------------------- Contents of the "live" mailman.cfg file, from "mailman info" --------------------------------------------------------------------------- (venv) [mailman3@someserver ~]$ cat -n /opt/mailman3/var/etc/mailman.cfg 1 # /opt/mailman3/mailman.cfg 2 [paths.here] 3 var_dir: /opt/mailman3/mm/var 4 5 [mailman] 6 layout: here 7 # This address is the "site owner" address. Certain messages which must be 8 # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # bounce from a list owner), will be sent to this address. It should point to 10 # a human. 11 site_owner: user(a)example.com 12 13 [database] 14 class: mailman.database.postgresql.PostgreSQLDatabase 15 ##### url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # ---------------------------------------------------------------------------------- 17 # Changed: Fri Jun 28 11:56:02 EDT 2024 18 url: postgresql://mailman3:xxxxxxxx@localhost/mailman3/mailman3 19 # Changed: Fri Jun 28 11:56:02 EDT 2024 20 # ---------------------------------------------------------------------------------- 21 22 [archiver.prototype] 23 enable: yes 24 25 # For the HyperKitty archiver. 26 [archiver.hyperkitty] 27 class: mailman_hyperkitty.Archiver 28 enable: yes 29 configuration: /opt/mailman3/mailman-hyperkitty.cfg 30 31 [shell] 32 history_file: $var_dir/history.py 33 34 [mta] 35 incoming: mailman.mta.postfix.LMTP 36 outgoing: mailman.mta.deliver.deliver 37 lmtp_host: 127.0.0.1 38 lmtp_port: 8024 39 smtp_host: localhost 40 smtp_port: 25 41 configuration: python:mailman.config.postfix 42 verp_confirmations: yes 43 verp_personalized_deliveries: yes 44 verp_delivery_interval: 1 Suggestions appreciated for how to fix the postfix_domains files, and the postgres authentication isssue. ------------- Keith

11 months

[MM3-users] Re: anomalous behavior

by Mark Sapiro

On 10/5/24 04:14, donato(a)molino.it wrote: > Hi, > I installed mailman-full on debian 12. How? Did you follow https://docs.mailman3.org/en/latest/install/virtualenv.html or did you install the Debian packages. If the latter, please see https://wiki.list.org/x/12812344 > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > I have three MLs: > 1) example(a)example.com > 2) test(a)example.com > 3) hello(a)example.com > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > The configurations are identical for all 3: > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > I also enabled all debugging in mailman.cfg. > But everything is fine What's in the MTA log? Does list 1 have any non-digest members with delivery enabled `mailman members --regular --nomail enabled example(a)example.com` In addition to the above in smtp.log, I would expect to see entries similar to the following for your post to this list. ``` Oct 05 11:15:02 2024 (3390806) <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 seconds Oct 05 11:15:02 2024 (3390806) <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes Oct 05 15:22:57 2024 (3390806) <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 seconds Oct 05 15:22:57 2024 (3390806) <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes ``` (the delay between 11:15:02 and 15:22:57 above is the time between arrival and held message approval) Do you see things like that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

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

by Stephen J. Turnbull

Onyeibo Oku writes: > I already started out on the above route. Its an adaptation because I > am running Fedora. I had no problem with system-wide installations via > dnf package management. However, some parts of the documentation does > not add up. As Mark already wrote, "adapting" to Fedora is a bad idea. It makes it harder to read our documentation, which as you note is imperfect. Also, it interferes with Fedora's own package management. You should not be installing anything but Fedora packages into /usr and /var (among others). > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? Yes. Exec summary: Different startup files are read depending on whether the "login" and "interactive" flags are set, and the bin/activate script is not a normal script, invoking it is very finicky. I don't know exactly what's going on with the automatic invocation of the venv, but I suspect it's related to that. A quick workaround for the difference between "su mailman" and "su - mailman" would be to link .bash_profile -> .bashrc, or source one from the other. See bash docs for details. > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" That's undoubtedly related to "adapting" to Fedora practice. Where pip packaged files ended up depends on where you put your venv. My recommendation is to delete everything you've done to this point and start over from the beginning, following our instructions to the letter. This has two benefits: (1) you don't need to continuously translate from Mailman instructions to Fedora practice, and (2) in case our instructions are inaccurate or poorly adapted to the Fedora environment, it's *much* easier for us to advise you on what to do. Steve

2 years, 7 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by tlhackque

On 17-Oct-20 14:31, Mark Sapiro wrote: > On 10/17/20 10:39 AM, Torge Riedel wrote: >> The message is being held because: >> >> Header "Yes" matched a header rule >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> I think this is wrong, it should read 'Header "x-spam" matched a header >> rule'. Cause the header rule is configured for header "x-spam" and >> pattern "Yes". > > The message is defined as > > 'Header "{}" matched a header rule' > > where {} is replaced with the value of the matching header. I agree it > would be better if it were something like > > 'Header value "{}" matched a header rule for {}:' > > with {}s replaced with the header value and name. That would make it in > your case > > 'Header value "Yes" matched a header rule for x-spam:' > >> I haven't found a bug report for this yet on gitlab. If someone of the >> developers confirm this is wrong, I will file a bug on gitlab for it. > > Please do file a bug. It won't be fixed until after the upcoming 3.3.2 > final release because we not making i18n changes between the candidate > and final releases. Also, if you don't like my suggestion, feel free to > suggest something else. > FWIW, I suggest: Header "{name}": rule matched value "{value}" Name tends to be short and must be simple ASCII. Value can be very long and encoded, so it may wrap. Name will be short and recognizable. Plus the name provides the context for the value - and name:value is the way the header appears in the e-mail. So I think name before value obeys the UI principle of least surprise. I might also add the rule number or config filename:line, as in Header "{name}": rule in {file}:{n} matched value "{value}" This would be helpful when backtracking from a rejected message to the cause. A sample expansion might be: Header "X-Spam": rule in foo.conf:83 matched value "yes"

4 years, 7 months

[MM3-users] Dump/restore users (with passwords) via API Update

by Conrad Holmberg

Hello: Just an update and review on a previous thread and some progress. I'm trying to write a Python script to do the following: - Dump all the members from a email list within mailman instance A. This includes the display name, email, password hash, and all the preferences. The output is a json file. - Then we read this json file and create the user, membership to the email list, and the preferences into mailman instance B. The problem is that we are trying to insert the members with the password hash and NOT a new plain text password. A simple json dump example: { "password":"$6$rounds=656000$QhEAT7XCQ9tyUmJV$cj2xv3GKd8UXdSSasMZdqe0NjUL4T751nBEkdubog55jzIY1iZ5AQ4aRVeJIi1jnS1CKHHJn6nVnW.Hz91Xvk.", "list_fqdn": "helpme(a)confused.com", "display_name": "Bob Nobody", "email": "nobody(a)nowhere.com", "preferences": { "receive_list_copy": false, "hide_address": false, "preferred_language": "en", "delivery_mode": "regular", "receive_own_postings": true, "acknowledge_posts": false, "delivery_status": "enabled" } } The code for this within the mailman client API is pretty straight forward. However, the method for create_member will not work for our situation because the argument requires the password to be in plain text to be encrypted later. The rest of the tasks (subscribing, preferences) can be done with the mailman client with this single exception. Now my question is irf someone can send a single piece of code example or where to look to accomplish this. I see two options: Using the mainman core. I believe the modified code would be something like this: user_manager = getUtility(IUserManager) #with transaction(): new_user = user_manager.create_user( 'nobody(a)where.com', 'Bob Nobody') new_user.password = config.password_context.encrypt('abc123') #replace with hash new_user.password = '$6$rounds=656000$tS8sTX' So the password is set with the hash instead of the encryption method. Original code: new_user.password = config.password_context.encrypt('abc123') The other possible method is through django. However, I'm not really sure where to being on this on as I've been looking over the django-mailman3 and this is the only example I can find in test_delete_account.py: def setUp(self): self.mm_user = Mock() self.mm_user.user_id = "dummy" self.mailman_client.get_user.side_effect = lambda e: self.mm_user self.user = User.objects.create_user( 'testuser', 'test(a)example.com', 'testPass', first_name="firstname", last_name="lastname", ) self.client.login(username='testuser', password='testPass') Again, it appears that the password is encrypted somewhere else before encrypted. Any help on this is greatly appreciated. Thanks Conrad

6 years, 8 months

[MM3-users] Re: Disable user registration

by Abhilash Raj

> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > jens.guenther(a)posteo.de writes: > >> Same question here :-) > > This is not a simple question. Mailman is built from the ground up on > the assumption that users sign up. Making sign-up easy and powerful > is the raison d'etre of Mailman. > > One obvious approach is to add "^.$" to each list's ban list > (eventually that should be configurable as a list style, so "easy" to > make domainwide or sitewide), but that doesn't stop people from > creating users via Postorius. One way to address that would be to > clean out users with no subscriptions once a week or so. > > I guess you could go into the templates and remove the > accounts/signup/ links everywhere if "denial by obscurity" is enough, > or into urls.py and send that URL to a "Get out of here you hacker!" > view. Since these interventions are global, though, so the > desideratum of "no site admin intervention" is right out. Users are > site-global. Modifying urls.py to match `/accounts/signup` and redirect to a static page that says “Signups are disabled” or just event a 404 page is probably easiest to do. diff --git a/example_project/urls.py b/example_project/urls.py index 9c854989..3187756e 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -23,16 +23,22 @@ This file is the main URL config for a Django website including HyperKitty. from django.conf import settings from django.conf.urls import include, url from django.contrib import admin +from django.http import Http404 from django.urls import path, reverse_lazy from django.views.generic import RedirectView +def not_found(request): + raise Http404("Signups are disabled on this site.") + + urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('hk_root'))), url(r'^hyperkitty/', include('hyperkitty.urls')), # url(r'^postorius/', include('postorius.urls')), url(r'', include('django_mailman3.urls')), + url(r'^accounts/signup', not_found), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), This did the job for me locally and will present the user with a 404 page saying the “Signups are disabled on this site”. Note it is important to put the new pattern before the “^accounts/“ pattern since the URLs are matched in the order they are defined. -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Archive import fails: "IndexError: list index out of range"

by Johannes Rohr

I am now importing the archives of my old mailman2 installation. Unfortunately, with some of the larger and older lists, import fails halfway through, with an exception, the last message of which is IndexError: list index out of range Below is an example. This means that the last few years are missing from the archive in several lists. Are there any suggestions what I could do to still get them importet? Thanks! Johannes File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '@localhost>' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 387, in handle importer.from_mbox(mbfile, report_name) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 212, in from_mbox progress_marker.tick(unquote(message.get("message-id", 'n/a'))) File "/usr/lib/python3.8/email/message.py", line 471, in get return self.policy.header_fetch_parse(k, v) File "/usr/lib/python3.8/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 607, in __call__ return self[name](name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 202, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.8/email/headerregistry.py", line 535, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or IndexError: list index out of range

2 years, 5 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull: > You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right? No, I'm not that guy. I've not said anything like that, nor have I knowingly configured Postfix to use that. I've looked up how to do it now that you mention it, and found the smtputf8_enable parameter[1]. I have not used it, but it turns out that it is enabled by default. I can turn it off and see if that makes any difference in the future. Testing with telnet, Postfix indeed announced "250 SMTPUTF8" on EHLO. > If you're right about the umlaut being the trigger, the first thing I'd look at is a feature-negotiation problem in the MTA delivering to Mailman. I'm pretty sure our LMTP does not offer the SMTP UTF8 feature. In that case the problem should go away with disabling SMTPUTF8, I suppose? > I would guess this is in the shunt queue. If there's only one file there, you can just delete it. There was a whole bunch of files in that directory. I've taken a look several of them, and as they were all spam, I've taken the liberty to delete them all (this list is so low volume that I know all the senders personally anyway). However, even after restarting mailman, the 500 error persists when visiting the held messages page in postorius. I've also looked into all the other queue directories, they were all empty. > Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name. I confess that I haven't visited the held messages page for a very long time (because I didn't have a reason to; I received no notifications of held messages). Only after I received the notification that my errorneous message was being held, I visited it, and I was faced with the 500 error. If Mailman failed to notify me of held messages previously, they might have been in hold status already and one of them might be the cause. Marvin [1]: http://www.postfix.org/postconf.5.html#smtputf8_enable PS: Sorry for the missing link [1] from the last mail. Here it is: https://gitlab.com/mailman/hyperkitty/issues/201 -- Blog: https://mg.guelker.eu

5 years, 5 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by brian＠emwd.com

> > Everything else works fine. Postfix is receiving and > > delivery mail to Mailman3. List members are receiving the posts. I can access the list on > > Hyperkitty just no archived messages. > What URL do you use to access HyperKitty. I use http://mailman3-lists.com/mailman3/hyperkitty/. However I changed the base-url from localhost to mailman3-lists.com and saw the same error except the URL reflected mailman3-lists.com instead of localhost. > The problem URL above, > http://localhost/mailman3/hyperkitty/api/mailman/archive is based on the > base_url setting in mailman-hyperkitty.cfg which in your case is > http://localhost/mailman3/hyperkitty/, byt the web server listening on > localhost:80 is returning the Service Unavailable. It probably doesn't > like the IP or name 'localhost'. I have this in the apache2.conf file: ServerName localhost I can access the apache default page when using the following: curl http://localhost.com > Set base_url in mailman-hyperkitty.cfg to use an acceptable host name > instead of localhost or adjust your apache config to accept localhost. Isn't ServerName enough? This error also appears in the apache log file when new posts are sent to the list: [Thu Apr 11 19:55:38.755750 2019] [:error] [pid 21370:tid 139988922513152] (32)Broken pipe: [client ::1:49574] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.769245 2019] [:error] [pid 21370:tid 139989049186048] (32)Broken pipe: [client ::1:49576] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.777583 2019] [:error] [pid 21370:tid 139988914120448] (32)Broken pipe: [client ::1:49578] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.787681 2019] [:error] [pid 21370:tid 139988905727744] (32)Broken pipe: [client ::1:49580] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.798273 2019] [:error] [pid 21369:tid 139989082756864] (32)Broken pipe: [client ::1:49582] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.807790 2019] [:error] [pid 21370:tid 139988897335040] (32)Broken pipe: [client ::1:49584] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.818123 2019] [:error] [pid 21369:tid 139989074364160] (32)Broken pipe: [client ::1:49586] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.827737 2019] [:error] [pid 21370:tid 139988888942336] (32)Broken pipe: [client ::1:49588] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.837612 2019] [:error] [pid 21370:tid 139988880549632] (32)Broken pipe: [client ::1:49590] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.848250 2019] [:error] [pid 21370:tid 139988872156928] (32)Broken pipe: [client ::1:49592] sending data to httpd-UDS:0 failed Brian

6 years, 1 month

[MM3-users] Re: Another interesting error...

by Darren Smith

OK chalk another one up to a python newbie... commit() was the magic sauce that we needed. The error 500 is no longer happening on that mailing list. We have three different lists so far that have gotten into this state, and we are going to work on the other two to make sure that this all works. FYI if this is fixed somehow in a later release (later than 3.1.0) we are working on migrating to the latest mailman code. -Darren On Mon, Apr 23, 2018 at 4:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 02:59 PM, Darren Smith wrote: > > Well, using the mailman shell we were able to find the request that was > > causing the problem - it was apparently a spam message that had some > > chinese characters in it. > > > I am trying to duplicate this issue in a test environment. I can create > a message with an invalid RFC 2047 encoded subject, i.e., > > Subject: =?gb2312?Q?=ff=fe=de=21=a2?= > > and send it to a list where it gets held, but I don't get a 500 in > postorius and I see the held message with a raw (not decoded) header. > > I think there were some recent changes that affect this. I'll look some > more. > > > > We used the shell to delete the held request... > > > > And postorius is still giving me an error 500. > > > > If I'm not mistaken the held messages are kept in .pck files - do you > know > > if when postorius asks for held messages through the API, does mailman go > > to the database or to the .pck? I would actually suspect the latter, or > > removing the request should have fixed the problem. > > > They were held in .pck files in Mailman 2.1, but not in Mailman 3. They > should just be in the database and deleting them via mailman shell > should delete them as long as you quit the shell or commit(). > > -- > Mark Sapiro <mark(a)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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 1 month

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Abhilash Raj

On Wed, Apr 17, 2019, at 8:18 AM, Mark Sapiro wrote: > On 4/17/19 8:10 AM, Abhilash Raj wrote: > > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: > >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: > >>> > >>> Which version of Hyperkitty are you using? > >>> > >>> Did you upgrade the version of Hyperkitty when you migrated to the > >>> new host? > >> > >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple > >> releases), so it's hyperkitty 1.1.4. > >> > >> I didn't upgrade anything with the move. > > > > I am not sure where does Debian packaged version store it's fulltext index, but > > I am assuming the move somehow makes Hyperkitty not be able to read the > > index. > > > I think this is a known incompatibility between the Python 2.7 and > Python 3 versions of Whoosh. I *think* 1.1.x releases were based on Python 2.7, so that part looks right to me. > > From the tracebacks, the current HyperKitty is running under Python 2.7. > If the prior server was running HyperKitty with Python 3, that would > explain this. Given that 1.1.x supports only 2.7 and Ubuntu doesn't have 1.2 release, it is unlikely Python 3 was used. > > > Can you try removing and re-building the entire index? I don't know again > > the right command for Django there, but the hyperkitty command you want > > to run is called `rebuild_index`. For source package, something like: > > > > $ python manage.py rebuild_index > > > > Do note that this will take a lot of time if you have a big archive. > > > If this is the incompatibility, rebuilding the index will fix it. > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: Google auth issue redirect_uri_mismatch

by Ugnius S

Thank You for the showing good road. Resolved! For Apache2 setup should look: ProxyPassMatch ^/static/ ! ProxyPass / http://127.0.0.1:8002/ ProxyPassReverse / http://127.0.0.1:8002/ ProxyPreserveHost On Kind regards Ugnius 2019-09-09, pr, 03:29 Abhilash Raj <maxking(a)asynchronous.in> rašė: > > > On Sun, Sep 8, 2019, at 2:12 PM, Ugnius S wrote: > > Hi. > > New question about configuration, maybe somebody has experience and know > > what I should change it. I have tried to implement Google authorisation. > > I have created Google credentials keys and successfully added using > Django > > admin page. > > I use UWSGI proxy for apache setup like "ProxyPass / > http://127.0.0.1:8002", > > UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects > to > > internal) What happens when I try Google auth... > > If I set Authorised redirect URIs: > > http://lists.example.com/accounts/google/login/callback/ , Google gives > me > > error 400 Error: redirect_uri_mismatch and requests for: > > http://127.0.0.1:8002/accounts/google/login/callback/ > > If I set that requested address to Google, then Google authorises > me, > > but and after authorisation redirects to > > http://127.0.0.1:8002/accounts/google....../.... (very long line) Of > > course this internal address does not open, but... > > If I just manually replace part of address just: > http://127.0.0.1:8002 > > replace to https://lists.example.com/.../...(long line) this makes me > get > > in as authorised user to the page. > > How to make django to send external request to Google? Because > > Google should not point back to internal address... This seems simple, > but > > I do not find what I should change in the configuration: Apache or Django > > or uwsgi.ini I hope anybody of You have experience and made it to run. > > You need to set this in nginx under your location directive, where you > setup your proxy_pass or uwsgi_pass > > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > Something similar should exist for Apache. > > > > > Kind regards > > Ugnius > > _______________________________________________ > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) >

5 years, 9 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Correction. Not 22.04. I'm trying 24.04. Am 2024-04-25 13:35, schrieb Thomas Stein: > Howdy! > > I'm trying to migrate an aged mailman3 installation from ubuntu 20.04 > to ubuntu 22.04. Fresh install of mailman3-web gives me: > > Creating config file /etc/dbconfig-common/mailman3-web.conf with new > version > creating database mailman3web.db: success. > verifying database mailman3web.db exists: success. > > Creating config file /etc/mailman3/mailman-web.py with new version > /usr/lib/python3/dist-packages/django_q/conf.py:174: UserWarning: Retry > and timeout are misconfigured. Set retry larger than t > imeout,failure to do so will cause the tasks to be retriggered before > completion.See https://django-q2.readthedocs.io/en/maste > r/configure.html#retry for details. > warn( > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > mailman3-web > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > > I've already seen this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > ...but that does not get me anywhere. > > Could someone please push me in the right direction? > > cheers! t. > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to himbeere(a)meine-oma.de

1 year, 1 month

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 10:29 AM, Dmitry Makovey wrote: > On 09/27/2017 10:20 AM, Abhilash Raj wrote: > > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >>>> I've come across mailman-cli docs: > >>>> > >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >>>> > > > > This is basically one of our GSoC projects which hasn't yet been merged > > with MailmanClient. It uses the REST API to to provide a command line > > client for Mailman, while there hasn't been any in-compatible changes in > > API since this project was finished, I am not sure about the current > > status of it. > > > >>>> yet I cannot figure out what's the official source for the installation. > > > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > > and it doesn't have a CLI, the Github project you linked to says right > > on the top that it is not official project (Thanks for that Rajeev!). > > I did see that, thus I was asking the question here. > > > Also, I would say not to use this client to remotely access Mailman, the > > REST API is not meant to be exposed over internet (unless you have a VPN > > or other sort of setup to securely access the box remotely). > > > > in my case - I need to use REST API since we're deploying with docker > and pieces that need to integrate with mailman commands now live in a > different container (and very likely on a different machine). I do need > to be able to execute commands remotely - I can handle securing of that > connection, but it is not an option for me to run "fat" docker > containers thus the only interconnect is via sockets (either UNIX or > TCP). The CLI project is basically a Shell+CLI based on MailmanClient (python library for Mailman API) and Mailman Core's REST API. So, if I understand correctly, this would run commands over REST API like you want. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 8 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 11/2/21 20:15, Mark Sapiro wrote: > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I contributed in january to translate to spanish all the items left in >> Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I >> thought they will be used in the next upgrade, but I cannot see any >> improvement and there are many words untranslated. > > The Spanish translations for Mailman core and HyperKitty are currently > completely up to date with weblate. django-mailman3 differs in one > string that was translated on Feb 10 and hasn't yet been merged. > Postorius also differs in a few places from the Feb 10 version that > hasn't yet been merged. Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone. > Other than that, the translations should be good. > > >> Is there any way to upgrade the .po files in order to get the last >> translation? > > For the web UI you need to run the django management `compilemessages` > command. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error: su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. if I try with --settings param (for I missunderstood the error message) it shows the same: su -m mailman3 -c "python3 manage.py compilemessages --settings settings" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. I tried to find any doc regarding the use of the "compilemessages" command but I couldn't As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job. I'm lost. Can you, please, point me in the right direction? > For Mailman core you need to run > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > ``` > to compile the mailman.po file for gettext. >

4 years, 3 months

[MM3-users] Re: Separating Lists by Domain

by Mark Sapiro

On 1/3/19 2:34 PM, Abhilash Raj wrote: > > > On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: >> So who manages Postorius? Is that a whole separate application from >> Mailman 3? Is there a way we can get whoever the developer is to update >> it where we can separate lists by domain the way Hyperkitty does? Mark >> Sapiro refers to this in the following post: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at https://gitlab.com/mailman/postorius/issues Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome. As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project. Not long ago I write in another context > MM3 is much more complex than MM2.1 and there's a lot that I don't fully > understand myself. > > There is a basic core engine which does all the work of > creating/managing lists and users and receiving and sending mail. It has > no web UI per se. It exposes a RESTful API on the host server. > > The web management UI is Postorius and it is based on the Django web > framework and communicates with core via the REST API. The Archiver is > HyperKitty and it is fairly independent. It is also based on the Django > web framework. Account creation and web login is via django-allauth. > > Postorius, HyperKitty and the core were all developed separately by > different people and no one understands all of it. That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time. And as I said, merge/pull requests for GitLab issues are always welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: no mails to list members

by Thomas Stein

On 04.01.19 10:44, Abhijith PA via Mailman-users wrote: > Hi. Thomas > > On Friday 04 January 2019 02:10 PM, Thomas Stein wrote: >> On 04.01.19 05:15, Stephen J. Turnbull wrote: >>> Thomas Stein writes: >>> >>> > Thanks for your answer. So the the file in queue/shunt contains >>> > information too? I will have a look. >>> >>> The file in queue/shunt is the message plus some Mailman metadata, as >>> a Python pickle. You can find out what is in it using "bin/mailman.py >>> qfile", but probably the log and traceback will tell you (or us) >>> everything needed to fix the problem. >>> >>> If it's a Mailman bug (somewhat unlikely), we send you a patch and you >>> use "bin/mailman.py unshunt" to reinject the message into the mail >>> system via Mailman. If it's a nonconforming mail message (somewhat >>> more likely -- typically this happens when you have raw UTF-8 or other >>> 8-bit characters in the message header), then the easiest thing to do >>> is to edit a saved copy of the message and resend from your mail >>> client. (It's theoretically possible to edit the pickle and use >>> "unshunt", but Mailman currently does not provide that feature.) >> >> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >> i missed something else but after adjusting the permissions of that template everything worked as expected. > > > Can you explain little bit more about this template, path and its > permission ? Sure. I should start with mentioning the mailing list in question was imported with "mailman import21". After that i had: root@shinymail:~# ls -l /var/lib/mailman3/templates/lists/hoppla.domain.de/en/ total 8 -rw-rw---- 1 list list 106 Dec 26 18:48 list_member_digest_footer.txt -rw-rw---- 1 list list 110 Dec 26 18:48 list_member_regular_footer.txt root@shinymail:~# These txt files where owned by root:root. After changing it to list:list the problem disappeared. cheers t. > --a > _______________________________________________ > 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/ >

6 years, 5 months

[MM3-users] Re: username

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > It seems Microsoft Azure uses SAML2 authentication. When you say > "(what software, what requirements, what ID-related attributes are > available)" -- they just Nobody ever stops at "just". ;-) > want them to authenticate to the mailman listserve using > AZURE. What attributes besides username would have to be passed to > Mailman? The only attribute *needed for authentication* is username. But users are unlikely to be satisfied, and the straightforward implementation that I'm using has a number of implications that happen to work for my client, but I'm pretty sure would not be satisfactory in some other environments. 1. Users in my environment expect their profiles (display name, time zone) to be populated. (I haven't figured out how to do the latter, but it's a company with overseas offices, "that's the server's time zone" is acceptable.) Lack of first name, last name was considered a showstopper, though. In your environment there may be other attributes you'd like to add, but I think in stock Mailman 3 those (plus email, see point #2) those are all the attributes you would like to populate from the ID provider. 2. Owners and moderaters *need* their emails in the profile to be linked to their existing lists migrated from an existing Mailman 2 site (and maybe to future lists they admin, I haven't checked in detail). But confirming an email address is an annoyance you'd probably like to avoid. 3. The REMOTE_USER approach we use authenticates on every request, before the login screen is invoked. This means that superusers known to the network can't have a separate account; you need to give their personal users superuser privilege. This doesn't matter in my environment; the lists are used mostly for customer service, the admins with superuser normally don't interact with lists, so this actually increases accountability. (I don't think there's a "sudo" or "drop privileges" feature in Django.) This wouldn't be desirable in my university environment, as many of the superusers are faculty members who teach classes and supervise lists for their classes. So, yeah, all you *need* is the username, but I'm willing to bet you will be askeed to deal with some of those other issues. And again, the only SAML Service Provider I know how to configure is Shibboleth. Steve

1 year, 11 months

[MM3-users] Re: update_index

by Darren Smith

OK - next issue...here's the warning that I'm receiving when I run that: /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date received a naive datetime (2018-04-03 07:51:25) while time zone support is active. RuntimeWarning) I'm not sure that anything else occurred. The indexing took 2 seconds, and there have been tens of thousands of emails imported since the last index. Thoughts? -Darren On Tue, Apr 3, 2018 at 10:55 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Holy cow I think that's exactly what the problem is. I will give that a > try and let you know what happens! > > On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/03/2018 09:02 AM, Darren Smith wrote: >> > Hello, >> > >> > If I'm reading the docs correctly, when we run manage.py update_index, >> it >> > should be an incremental index of new emails that have been added since >> the >> > last time update_index was run - can anyone confirm that this is the >> > expected behavior? Or is there another command line option that I am >> > missing? >> >> >> There are two ways to run update_index. >> >> Hyperkitty's update_index is incremental and is run by >> >> manage.py runjob update_index >> >> Running >> >> manage.py update_index >> >> runs haystack's update_index which with no options does a full update. Run >> >> manage.py update_index --help >> >> to see the options. The incremental 'manage.py runjob update_index' >> should be run every minute by 'manage.py runjobs minutely' assuming cron >> is running the periodic Django jobs, so running either update_index job >> manually shouldn't be necessary >> >> >> ... >> > So...can anyone help with how to get the update_index to do only emails >> > added since the last time the update_index was run? >> >> >> manage.py runjob update_index >> >> -- >> Mark Sapiro <mark(a)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 >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 2 months

[MM3-users] Re: Emergency Moderation

by Allan Hansen

> On May 24, 2020, at 11:34 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/24/20 10:59 AM, Allan Hansen wrote: >> In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. >> I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. > > >> My own current top-of-the-list issues: >> >> A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? I can only speak for my own application of MM3: Desiring consistency between the lists, I don’t want to turn all the moderators into owners who can change list settings. Many of my moderators keep asking me to see the list of members and to subscribe and remove members. I end up servicing those requests. So... a. Moderators should be able to unsubscribe and subscribe members. b. Moderators should be able to set the member’s moderation status. c. Moderators should not be able to see/modify any other member settings. > > >> A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Awesome!!!! Thank you, Allan > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

[MM3-users] Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 21:19, Abhilash Raj wrote: > > > On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >> >> I restarted de server and the error changed. Now the log >> shows "KeyError: 'subscription_mode'": >> >> Did you also restart Mailman Core after the upgrade? >> >> Yes, indeed: I stopped mailman core and all the processes related. >> Did the upgrades. Started all again. Find the errors in the web user >> interface. Stopped all again. Looked for errors in the log. Restarted >> the complete server. Found the second error that this second mail is >> about to. It happens when, in the main page that shows all the lists >> you click to see one of them. It seems to me that it has been >> database structure changes in django that the upgrade is not aware... >> but it's a very long shot from my side. > `subscription_mode` was added in Mailman Core 3.3.2 and it is actually > a derived atrribute and not stored in Database. Mailman's API should be > returning this attribute for each Member, but for some reason it seems > to me like it isn't doing that even though do have Mailman 3.3.3 running > like you said. > If you have Curl installed, can you send me the output of: > $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 This is the output you asked for (it's the same you can see when you try to interact with one list): /usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> No log entry has been produced... TIA. > It should ideally return an output that looks something like shown > here[1]. You > can put the username/password of Core's API server in the above command. > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Abhilash >> I'm using sqlite as django database and mysql for mailman. >> >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >> Server Error: >> /mailman3/mailman3/lists/name_and_domain.of.the.list >> Traceback (most recent call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'subscription_mode' During handling of the above exception, >> another exception occurred: Traceback (most recent call >> last): File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >> line 34, in inner response = get_response(request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 115, in _get_response response = >> self.process_exception_by_middleware(e, request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 113, in _get_response response = >> wrapped_callback(request, *callback_args, **callback_kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 71, in view return self.dispatch(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >> line 74, in dispatch return super(MailingListView, >> self).dispatch(request, *args, **kwargs) File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 97, in dispatch return handler(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >> line 295, in get member.subscription_mode == File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 124, in __getattr__ self.__class__.__name__, name)) >> AttributeError: 'Member' object has no attribute >> 'subscription_mode' *********************** some info about >> the installed versions via pip list: pip list | grep django >> django-allauth 0.44.0 >> django-appconf 1.0.4 >> django-compressor 2.4 >> django-extensions 3.1.0 >> django-gravatar2 1.4.4 >> django-haystack 3.0 >> django-mailman3 1.3.5 >> django-picklefield 3.0.1 >> django-q 1.3.4 >> djangorestframework 3.12.2 pip list | grep mailman >> django-mailman3 1.3.5 >> mailman 3.3.3 >> mailman-hyperkitty 1.1.0 >> mailmanclient 3.3.2 pip list | grep postorius >> postorius 1.3.4 On 6/2/21 11:12, >> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I've just upgrade mailman 3 installation following Mr. >> Sapiro advice: did a pip install --upgrade >> django-mailman3 hyperkitty mailman mailmanclient >> mailman-hyperkitty postorius I did a "python3 manage.py >> migrate" after, too. And all seemed to run well. All the >> lists showed in postorius via web, but when I try to >> accesss into one of them the browser shows an error. In >> the log you can see: *-*-*-*-*-*-* Traceback (most recent >> call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'get_requests_count' .. (And after all the traceback >> lines) AttributeError: 'MailingList' object has no >> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >> seem to be distributing messeages well.. but I cannot >> acces via web administration (django/postorius) Can >> anyone point me in the right direction to solve this, >> please? _______________________________________________ >> 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.mailman3org/> >> >> >> _______________________________________________ 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.mailman3org/> >> >> >> _______________________________________________ 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.mailman3org/>

4 years, 4 months

[MM3-users] Re: Removing a mail addresses and users

by Abhijith PA

Hi Mark, On 11/06/20 1:16 am, Mark Sapiro wrote: > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) In my case these user signups were just to test postorious. These mail accounts didn't subscribed to anything. >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > Thanks for the link, let me try that out. --abhijith

4 years, 11 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by kelly.close＠lrewater.com

I'm adding to this thread because I'm running into the 403 HyperKitty failure (Access is forbidden) and adding my public ip address to the MAILMAN_ARCHIVER_FROM variable did not do the trick. I'm at a loss as to what might be going on so I'm hoping someone is willing to put fresh eyes on this. All other aspects of this new are site working. It's worth noting that I set up this new install and then restored database backups of mailman3 and mailman3web from my previous install, and also copied over the /var/lib/mailman3 folders (but I left behind the contents of the cache folder). I can see in the apache access log that the attempts are coming from the public IP, and it shows the archive key I'm using also: 54.71.5.180 - - [20/Jun/2020:09:51:01 -0600] "POST /mailman3/hyperkitty/api/mailman/archive?key=<mykey> HTTP/1.1" 403 4151 "-" "python-requests/2.18.4" Here's my ARCHIVER_FROM variable setting: MAILMAN_ARCHIVER_FROM = ('127.0.0.1','::1','54.71.5.180') The apache error log has "broken pipe" messages which Mark said in are just the normal outcome of the failure and not a clue. The mailman.log had both 403 (Access is forbidden) and 503 (Service Unavailable) errors, but the 403 errors come first and I think the 503 is just the result of not having access = here's what the 403 error looks like, right after the successful message posting: Jun 20 09:50:59 2020 (29587) ACCEPT: <20200620155058.1324.27893@mailman3> Jun 20 09:51:00 2020 (29591) HyperKitty failure on https://udfcd-lists.org/mailman3/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> (403) I verified (like a thousand times) that: MAILMAN_ARCHIVER_KEY (with quotes, in mailman-web.py) = api_key (without quotes, in mailman-hyperkitty.cfg) And for fun, here's my base_url. base_url: https://udfcd-lists.org/mailman3/hyperkitty/ I've tried it with http instead of https, and also and with the original //localhost/. With it set to localhost I get an ssl.CertificateError stating that localhost does not match any of the certified domains, which I think is because certbot sets you up with Virtual Hosts when you install the certificates so I need to have the base_url set to my actual domain and use the ARCHIVER_FROM variable to allow the IP address - I think I have all that set up right but still...forbidden. I've run out of things to check - any thoughts out there? Thanks! ~Kelly

4 years, 11 months

[MM3-users] UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, I've accidentally sent from an unregisted address to one of my lists. Mailman correctly held the message back for moderation, but when I go to the page for held messages in postorios, I receive a 500 error. I've included an except from the log below. To me, it looks as if it errors on processing my last name (which has a non-ascii character in it). This is Postorius 1.1.2 on Ubuntu 18.04 LTS from the repos. I've searched on the tracker for the problem and found one ticket[1], but it has something with logging so I suppose this is a different problem. Ideas? And how do I discard the message without access to the held messages page? Python version is 3.6.8. Log excerpt: Dec 09 13:21:04 2019 (3090) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' in position 269: ordinal not in range(128) Dec 09 13:21:04 2019 (3090) 127.0.0.1 - - "GET /3.0/lists/tsc-devel(a)lists.secretchronicles.org/held?count=10&page=1 HTTP/1.1" 500 59 -- Blog: https://mg.guelker.eu

5 years, 6 months

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Ludwig Grandpré

Dear Mr. Turnbull, dear blackout69, thank you very much for your answers. Below this text you will find a brief documentation how I finally managed to install mailman3 and mailman3web packages under Debian 11 with a remote PostGreSQL server v10.22. Maybe there is a more elegant way to install both packages correctly, but AFAIK any solution will be only a workaround for the main problem, that the DBA's password is usually unknown during the whole installation process if you use a remote database server that is run by another staff team. Best regards, Markus ------------ 8< ------------ Mailman3 installation ===================== 1. Installation mailman3 2. Installation mailman3web 3. Integration in boot sequence 1. Installation mailman3 ------------------------ Once the remote database server has been set up with databases mailman3 and mailman3web and with a database user mailman3 that has access to both databases, create database mailman3; create database mailman3web; create user mailman3 with encrypted password 'streng_geheim'; grant all privileges on database mailman3 to mailman3; grant all privileges on database mailman3web to mailman3; the package mailman3 can be installed: # apt install mailman3 To avoid the DBA password prompt that ususally cannot be answered if the database server is run by another team, the installation tool dbconfig-common should be omitted: * Configure database for mailman3 with dbconfig-common? No The mailman3 package will be installed without errors. The configuration of the database connection can be done in file /etc/mailman3/mailman.cfg: ... class: mailman.database.postgresql.PostgreSQLDatabase ... url: postgres://mailman3:<secret>@<host>:<port>/mailman3 At this point the required tables have not yet been created in the database. Therefore, the mailman3 package should be configured again: # dpkg-reconfigure mailman3 Because the database mailman3 already exists on the database server, it does not need to be recreated using dbconfig-common: * Reinstall database for mailman3? No * Add the HyperKitty configuration to mailman.cfg? No Also moving the HyperKitty configuration to /etc/mailman3/mailman.cfg is not necessary at this time. After dpkg-reconfigure has finished, all necessary tables do now exist in the database mailman3: mailman3=> \dt List of relations Schema | Name | Type | Owner --------+--------------------+-------+---------- public | _request | table | mailman3 public | acceptablealias | table | mailman3 public | address | table | mailman3 public | alembic_version | table | mailman3 ... An initial start of the service mailman3 shows no errors: # systemctl start mailman3 # systemctl status mailman3 ● mailman3.service - mailman3 server. Loaded: loaded (/lib/system/system/mailman3.service; enabled; vendor default: enabled) Active: active (running) since Thu 2022-11-03 10:10:29 CET; 11min ago. ... 2. Installing mailman3-web -------------------------- Once the mailman3 package is installed, package mailman3-web can be installed: # apt install mailman3-web This time you should not do the installation process without the help of the installation tool dbconfig-common: * Configure database for mailman3 with dbconfig-common? Yes * Database type to be used by mailman3-web: pgsql * Host name of the PostgreSQL database server for mailman3-web: new host * Host running the PostgreSQL server for mailman3-web: <remote host> * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> Even if the DBA password prompt cannot be answered: Create configuration file /etc/dbconfig-common/mailman3-web.conf with new version Password for user postgres: ?????? the dbconfig-common tool should be used again: * Next step for database installation: retry * Configure database for mailman3-web with dbconfig-common? Yes * Connection method for PostgreSQL database of mailman3-web: TCP/IP * Host name of the PostgreSQL database server for mailman3-web: <remote host> * Port number for the PostgreSQL service: 5432 * Method for authenticating the PostgreSQL administrator: password * Method for authenticating PostgreSQL user: password * PostgreSQL database name for mailman3-web: mailman3web * PostgreSQL username for mailman3-web: mailman3 * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> * Name of the database's administrative user: postgres * Password of your database's administrative user: sldjkfhskldfjhyxlökcjy The prompt for the DBA password cannot be answered correctly again, therefore "ignore" should now be the best choice for the further course of the installation process: * Next step for database installation: ignore * Password of your database's administrative user: sldjkfhskldfjhyxlkcylö An error does occur now because the database user mailman3 can not be created: ... Password for user postgres: unable to connect to postgresql server. error encountered creating user: psql: error: fe_sendauth: no password supplied ... But this error doesn't matter, because the database user mailman3 does already exist and the installation process of the package mailman3web will nevertheless be finished completely. A look into file /etc/mailman3/mailman-web.py shows that dbconfig-common has entered the database connection to the database server correctly, too: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman3web', 'USER': 'mailman3', 'PASSWORD': '<secret>', 'HOST': '<remote host>', 'PORT': '', <--- missing? 'OPTIONS': { }, } } Also all required tables have been created in the database mailman3web during the installation process: mailman3web=> \dt List of relations Schema | Name | Type | Owner --------+-----------------------------------+-------+---------- public | account_emailaddress | table | mailman3 public | account_emailconfirmation | table | mailman3 public | auth_group | table | mailman3 public | auth_group_permissions | table | mailman3 public | auth_permission | table | mailman3 ... The initial start of the service mailman3-web shows no errors: # systemctl start mailman3-web # systemctl status mailman3-web ● mailman3-web.service - Mailman3-web uWSGI service. Loaded: loaded (/lib/system/system/mailman3-web.service; enabled; vendor default: enabled). Active: active (running) since Thu 2022-11-03 10:42:30 CET; 11min ago ... 3. Intergration in boot sequence -------------------------------- Finally, the two services mailman3 and mailman3-web can be included in the boot sequence: # systemctl enable mailman3 Synchronize the state of mailman3.service with the SysV service script with /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3 # systemctl enable mailman3-web Synchronize the status of mailman3-web.service with the SysV service script using /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3-web ------------ >8 ------------ On 01.11.22 08:10, Stephen J. Turnbull wrote: > blackout69 writes: > > > For mailman3 > > sudo dpkg-reconfigure mailman3 > > > > For mailman3-web > > sudo dpkg-reconfigure mailman3-web > > I guess those will work too as long as the users and databases have > been created. But they'll still fail at the first step without that > (and they might fail anyway if checking for the existence of those > users and databases involves logging in to the database as the admin > user). > > _______________________________________________ > 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/ -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

2 years, 7 months

[MM3-users] Re: Rejection based on total message size including attachments

by Mark Sapiro

On 09/19/2018 03:34 PM, leith(a)khimaira.com wrote: > As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro. > > Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers. Is this a Mailman 3 question or a Mailman 2.1 question? If Mailman 3, the architecture is quite different. This would be done with a rule, not a handler, but based on details in your question, I think you are asking about Mailman 2.1. In that case, the appropriate list is really mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>, but since you're here, the basic info on custom handlers for MM 2.1 is at <https://wiki.list.org/x/4030615>. There is an example called MyHandler.py linked from that page. It won't do what you want but can be used as a starting point. Also, look at Mailman/Handlers/Hold.py, in particular the code following the "# Is the message too big?" for how to determine the message size. That handler will compare the size to the list's max_message_size and hold the post if it's too big. You probably want to compare the size to a fixed value or a size defined in mm_cfg.py and either reject or discard the message. If you put your handler between Moderate and Hold, it's probably safe to reject the message because it is from a member or an address in accept_these_nonmembers. Rejecting post from arbitrary non-members is a bad idea because of spam backscatter. If you need more help, please join mailman-users(a)python.org and post to that list. In any case, this could be generally useful enough that I will probably add it to the stuff at <https://www.msapiro.net/scripts/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

Yeah I'll set up some advanced debugging in Postfix on the relays to see whats' coming in and out. Will take time though 'cause we have a TON of messaging going through that smtpproxy out to the 'net so it'll take a bit for me to dissect the message logs. Give me a bit since it's EOD for me now. Thomas On 12/6/23 15:44, Mark Sapiro wrote: > On 12/6/23 11:11, Thomas Ward via Mailman-users wrote: >> See, that's the oddness. There appears to be SOME weird mail loop >> here where $ORIGIN (MS365/Exchange) hands it once, then there's >> back-and-forth between SMTPPROXY and Mailman. IT's really odd how it >> behaves, and I have no explanation for it. >> >> Right now I'm away from the office where this happens, but when I'm >> back there I'll grab logs from both sides. >> >> >> Thomas >> >> On 12/5/23 17:54, Mark Sapiro wrote: >>> On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >>>> We use a multi-hop SMTP system to go from the inside of our network >>>> out to the Internet at the domain test.lists.example.com. >>>> >>>> The setup is this way for ingress: >>>> >>>> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >>>> Connector) -> Mailman for delivery to listserv > > > Presumably the EXTERNAL to MS365 SMTP transaction includes > > MAIL FROM: <user(a)example.com> > RCPT TO: <invalid(a)test.lists.example.com> > > It seems that somewhere in the path to Mailman this is getting changed to > > MAIL FROM: <invalid(a)test.lists.example.com> > > so the outbound DSN is sent to invalid(a)test.lists.example.com instead > of user(a)example.com. The question is which one of the MTAs in the path > is doing this and why. > > But even more mysterious is the fact that the DSN from Mailman should > be sent with > > MAIL FROM: <> > > so when it's undeliverable, no further DSN is sent. >

1 year, 6 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Abhilash Raj

On 9/8/21 3:39 PM, Patrick Brückner wrote: > Hi everyone, > > one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back. > > What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list. > > The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain. > > Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again. > > According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API. > > Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)? You are probably on an old version of Mailman which didn't expose the values in API and also Postorius didn't expose it in UI. You can install a new version manually by downloading new debs from Debian unstable repos (I don't know if Ubuntu just copies the ones from Debian or has their own packaging, I think it is former) that have newer built debs. On your version, you probably would be able to set the accept_these_nonmembers using the command line using ``` mailman withlist -l test(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the test(a)example.com mailing list >>> m.accept_these_nonmembers ['*.example.com'] >>> m.accept_these_nonmembers = [r'*.example.com'] >>> commit() >>> quit() ``` -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello guys, This is what I've got on ../var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 76 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db What should I do in order to let mailman install the DB files? Thanks El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 08:16 AM, Rafael Mora wrote: > > This is the content of my /var/log: > > > > > > [root@localhost log]# pwd > > /var/log > > [root@localhost log]# ls > > anaconda grubby messages-20170716 spooler-20170710 > > audit grubby_prune_debug messages-20170723 spooler-20170716 > > boot.log httpd mysqld.log spooler-20170723 > > btmp lastlog php-fpm tallylog > > btmp-20170701 letsencrypt ppp tuned > > chrony maillog rhsm wtmp > > cron maillog-20170702 samba xferlog > > cron-20170702 maillog-20170710 secure xferlog-20170702 > > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > > cron-20170723 mailman secure-20170716 xferlog-20170723 > > dmesg messages secure-20170723 yum.log > > dmesg.old messages-20170702 spooler > > firewalld messages-20170710 spooler-20170702 > > > Your current postfix log is /var/log/maillog. The files like > /var/log/maillog-20170702, etc are older versions rotated by logrotate. > > On 07/23/2017 08:14 AM, Rafael Mora wrote: > > content of the file maillog-20170723 (I didn't find mail.log in > /var/log): > > > > [root@localhost log]# cat maillog-20170723 > > You want to be looking at /var/log/maillog for current messages. > > > ... > > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory > > > Is this where these files are? You should have at least postfix_domains, > postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the > /var/lib/mailman/var/data/ directory. It this the case? > > > output command 'postconf -n': > > > ... > > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp > > > This is missing a / > > > transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp > > > -- > Mark Sapiro <mark(a)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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: logrotate

by Christian

Thank you! Would I run your script weekly in cron or ? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, May 2, 2023 4:37 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: logrotate Please don't hijack threads. Post a new topic as an original post, not as a reply to an old thread. On 5/2/23 15:45, Christian via Mailman-users wrote: > I noticed that my mailman logfiles are not being rotated. I followed > the instructions in > https://mail.python.org/archives/list/mailman-developers@python.org/me > ssage/ > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Those instructions are for Mailman 2.1. > Now when I try and run logrotate I get the following error > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file > or directory > error: stat of /opt/mailman/mm/error.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file > or directory > error: stat of /opt/mailman/mm/smtp.log failed: No such file or > directory > root@zarathustra: > > What am I doing wrong please? Here's a logrotate script I use: ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` A couple of caveats. The first line of the postrotate script may be wrapped. `sudo ... true` is all one line. That line could also be ``` /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true ``` I.e., it either has to run as the mailman user or specify the --run-as-root option. Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't in /opt/mailman/mm/var/ those paths need adjusting. Finally, there may be an issue with `mailman reopen` in the postrotate scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ JTUKYJDD5Y5JIAVK3OOFNVCK4CVDGK6O/ This message sent to csa(a)web-analysts.net

2 years, 1 month

[MM3-users] Re: getting all registered users and their lists

by Mark Sapiro

On 1/27/22 00:06, IOhannes m zmoelnig wrote: > On 1/26/22 17:19, Mark Sapiro wrote: >> On 1/26/22 00:16, IOhannes m zmoelnig wrote: > >>> is there a scriptable way to get all users that have registered in my >>> mailman3 (3.2.1) instance and which lists they are subscribed to (if >>> any)? >> >> It's in Postorius >= 1.3.6 > > i'm not entirely sure how this relates to the above (working) snippet. > > is it, that with postorious>=1.3.6 i would be able to perform that task > from the webinterface, rather than having to resort to 'mailman shell'? Not really. In Postorius 1.3.6 there is a `Users` view that will display users and their create date and it is ordered by create date. Then each user's entry has a `Manage` button which goes to a page which among other things, lists their subsubscriptions. So, you could find the users of interest via this interface, but unless you developed a screen scraping script, it would be a multi-step manual process. > in any case, this might be related: > before i received your email with the 'mailman shell' snippet, i scraped > some bits of my django knowledge and visited > <https://lists.example.com/admin> (the django admin interface), and > noticed the list of users there. > so i scraped that page for users (assuming that this was the list of > registered users). > then i get myself a list of all subscribers in my instance, using a > crude `mailman lists | grep "@" | while read l; do mailman members > "${l}"; done | sort -u`. > finally i calculated the difference between the two sets. > > interestingly the results are quite different from the ones i got from > your script: both sets contain users that are not in the other set. > how come? My script deals with Mailman users who may or may not be Django users. They won't be if they never signed up on the web UI. On the other hand, anyone can go to the web UI and sign up and become a Django user even if they never join any list and become a Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Fwd: Incoming command emails (i.e. listname-leave) routed to list itself

by Stephen J. Turnbull

This was my bad. For about 20 years now, I myself never used mail commands except subscribe and my Mailman 3 users have *always* used the web interface. And as you might guess, the exim4 config was developed by tweaking a Mailman 2 config until it worked for me. Thank you for diagnosing and documenting a more configuration, Abhilash! Steve Abhilash Raj writes: > Hi Mark, > > Excerpts from Mark Lindsay's message of April 20, 2017 5:37 pm: > > <snip> > > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > > potato-leave(a)lists.mydomain.org email: > > > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > > succeeded] > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > > H=localhost [127.0.0.1] C="250 Ok" > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.o > > rg > > > >> `? > >> > > > > I think this is actually an exim4 problem, so if the solution is to just > > switch to postfix, then I will definitely do that. But I'm just asking in > > case someone had a similar issue with exim4 and was able to work through > > it. > > > > > Yes, I had the exact same problem very recently and was able to fix it. The > updated documentation[1] should fix your problem. The basic gist of the > problem > is that the exim configuration on the older documentation is missing a > critical > part. > > Exim4 by default strips off any prefixes/suffixes when delivering mail to > the > mailman, which causes mailman to post all the messages to mailing list > instead > of processing them as commands. > > `rcpt_include_affixes = true` > > Adding the above line to the transport fixes that problem. > > [1]: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mt > a.html#exim4-configuration > > thanks, > Abhilash >

8 years, 1 month

[MM3-users] Memory usage

by Adi Kriegisch

Dear all, I've been using mailman2 for quite some time and I am considering upgrading to mailman3. In a test setup I noticed that mailman3 with just a basic setup (Debian with mailman3 package and sqlite as backend using exim4) uses over 700MB RAM (RSS): | USER VSZ RSS COMMAND | list 73072 54568 /usr/bin/python3 /usr/lib/mailman3/bin/master | list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1 | list 73100 54572 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=bounces:0:1 | list 73100 54560 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=command:0:1 | list 73100 54600 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=in:0:1 | list 146832 54700 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=lmtp:0:1 | list 73100 54808 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=nntp:0:1 | list 73100 54652 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=out:0:1 | list 73100 54504 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=pipeline:0:1 | list 150516 58228 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=rest:0:1 | list 73100 54508 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=retry:0:1 | list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=virgin:0:1 | list 73100 54608 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=digest:0:1 This is with only one test list configured that just has one member. Compared to a mailman2 setup with many lists with up to 300 members that only uses around 70MB RAM: | USER VSZ RSS COMMAND | list 63724 1396 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -q start | list 62896 10660 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s | list 61156 1792 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s | list 58148 1808 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s | list 73116 23316 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s | list 55464 1672 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s | list 65840 11868 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s | list 62036 10840 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s | list 58716 5712 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s This is without hyperkitty or a management interface, just mailman3 core that uses 10 times as much ram as mailman2. Did I do something wrong here? Is there probably a bug in my python environment? Are there any config options that I should set to avoid this huge memory footprint? I found one thread[1] on this mailing list where a user asked a question similar to mine with comparable numbers. best regards, Adi Kriegisch [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…

6 years, 8 months

[MM3-users] Re: The doubled entries issue

by Lars Bjørndal

[Abhilash] > On Sat, 11 Nov 2023, at 10:15 PM, Stephen J. Turnbull wrote: > > Lars Bjørndal writes: > > > > > > raise ComponentLookupError(interface, name) > > > zope.interface.interfaces.ComponentLookupError: > > > (<InterfaceClass mailman.interfaces.listmanager.IListManager>, '') > > > > That says that "python scriptname.py" need the IListManager interface > > but can't find it. You didn't provide enough information to explain > > why that might be, so I'm not going to guess. > > This is mostly because of trying to run script with `python scriptname.py` > but since it doesn’t initialize the mailman’s zope system. > > What you probably want to do is run the script using `mailman shell —run` > command, which will ensure that it runs the script after initializing the > zope components (and other mailman config and things are initialized too). Thank you. The script I try to run, is found here: https://gitlab.com/mailman/mailman/-/issues/657 I named the script fix-doubled-entries.py. When I try `mailman shell --run ./fix-doubled-entries.py` I get: Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/commands/cli_withlist.py", line 282, in shell r = call_name(dotted_name, *run_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) ^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/importlib/__init__.py", line 121, in import_module raise TypeError(msg.format(name)) TypeError: the 'package' argument is required to perform a relative import for './fix-doubled-entries' How should I invoke the script? Thanks, Lars

1 year, 6 months

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Mark Sapiro

On 09/30/2018 11:42 PM, Thomas G wrote: > Hi, > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > install in Mailman3.2. > > I didn't found how migrate the archives. >>From : HyperKitty - Version: 1.1.1 - Python2.7 > To : HyperKitty - Version: 1.2.1 - Python3.5 As Abhilash said, you shouldn't need to migrate anything but the search index. > I exported a mbox from hyperkitty (web interface) and tried to re-import > it, without result. > """""""""""""""""""""""""""""""""""""""" > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > listedetests(a)hatlab.fr You can't import a gzipped mbox. You have to gunzip it. > Computing thread structure > Synchronizing properties with Mailman > Warming up cache > The full-text search index is not updated for this list. It will not be > updated by the 'minutely' incremental update job. To update the index > for this list, run the 'manage.py update_index_one_list > listedetests(a)hatlab.fr' command. > """""""""""""""""""""""""""""""""""""" > The database stay empty (and web interface): > """""""""""""""""""""""""""""""""""""" > mailmandbnameprod=# select * from hyperkitty_email; > id | message_id | message_id_hash | subject | content | date | timezone > | in_reply_to | archived_date | thread_depth | thread_order | > mailinglist_id | parent_id | sender_id | thread_id | sender_name > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > (0 rows) > """""""""""""""""""""""""""""""""""""" > > Any idea to do this importation ? Why is the database empty? It should be as it was with the prior HyperKitty. Also, it doesn't seem to be the issue here, but if you don't specify a --since option to hyperkitty_import, it won't import any messages older than the most recent message in the existing archive. i.e., if there are any messages in the existing archive, the default for --since is the date of the most recent such message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 4/30/19 1:04 AM, Henrik Rasmussen wrote: > @Mark: I am really sorry for the delayed responses, but this is a very low frequency list. I have subscribed to the list using a non-Microsoft address to see the outcome. > > The mails does indeed contain 'X-Mailman' headers. > > X-Mailman-Rule-Hits:nonmember-moderation > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation It looks like the message hit the nonmember-moderation rule and was accepted. This can happen in a few ways: First we determine the senders. Assuming the config is default, these are the addresses in From:, the envelope sender, and addresses in Reply-To: and Sender: if any. The only address I can see in the message headers that hasn't been altered by Mailman is the From: and maybe Reply-To: which you have munged to [LISTNAME](a)senderdep.example.com. Anyway that unmunged address and possibly others from the original incoming message will be users of the list with role nonmember. Now each of those (possibly only the one) nonmember(s) is checked for a moderation action. Since the message does not appear to have been held or processed through rules beyond nonmember-moderation, we presumably found a moderation action of accept. This can happen in a few ways., If this list was originally imported from Mailman 2.1 by the 'mailman import21' command, there may be a legacy accept_these_nonmembers attribute for the list. If so, and if a nonmember sender address matches an address or pattern in the list's accept_these_nonmembers, the message will be accepted. Otherwise if the moderation_action for a nonmember sender address is accept the message will be accepted. You need to check the list's accept_these_nonmembers attribute and the non-member address's moderation action. If you have recent Postorius, you can see nonmembers and their options from the 'users' -> Non-members view. In any case, you can do something like mailman shell -l list.example.com Welcome to the GNU Mailman shell The variable 'm' is the list.example.com mailing list >>> m.accept_these_nonmembers returns a possibly empty list Then for the sender addresses >>> memb = m.nonmembers.get_member('sender address') >>> memb.moderation_action This may return <Action.accept: 3> in which case you may want >>> memb.moderation_action = m.default_nonmember_action -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Abhilash Raj

On Wed, Nov 25, 2020, at 9:24 AM, Mark Sapiro wrote: > On 11/24/20 7:22 PM, Abhilash Raj wrote: > > > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). > > > It's more complicated than that. Sometimes the fragment name is the > heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor > #3.3.3 work at all as these are #id2 and #id1 respectively. Currently > the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is > #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs > under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but > when a Command line section is added under 3.3.3, that will probably get > the command-line id. > > Thus, the note "Permalink to this headline" es misleading at best > because it isn't very permanent fo an evolving document. Yeah, I was thinking about internal references, `:ref:` which accepts heading names, but anchors aren't added you are right. > > > > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. > > > I too think this is correct. I suppose it might be worth doing for > NEWS.rst in particular since Sphinx doesn't seem to like fragments like > n.n.n. Another way to deal with this would be to always use code names. > It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. > `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` Yep, I created news-3.3.3 for 3.3.3 and we can keep the convention going. I tested it out and it worked for me. https://gitlab.com/mailman/mailman/-/merge_requests/736 > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Re: Message IDs

by Mark Sapiro

On 10/15/21 3:19 AM, Philip Colmer wrote: > > I'm not sure that the message ID identifies the author, does it? No, but it identifies the message, and while Mailman has made some cosmetic modifications to the headers, it is still the same message. > I've just done a quick test of sending myself an email and then replying to it. > > The original email has a message ID of > CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com > > In the reply, the following headers are present: > > References: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > In-Reply-To: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > Message-ID: <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> > > Would it be reasonable for Mailman 3 to use "References:" to keep the > original Message ID and then add a new Message ID? No, because the message from the list is not a reply to the incoming message. It is the incoming message. > I think that what Mailman 3 is doing is similar to forwarding the > email. If I forward an email, again the headers change: If you want Mailman to 'forward' the message, set DMARC mitigation action to wrap the message. >> The IETF has addressed the issue of non-identical but equivalent >> messages with the Resent-Message-ID field (and in general the whole >> suite of Resent-* fields. > > Mailman doesn't appear to be adding that header. Would that be an > acceptable solution instead of the one I suggested above? Mailman doesn't add the header, but even if it did, I doubt it would solve the problem with Gmail. > I appreciate your view that Google is broken. I'm just trying to find > an acceptable solution to the end-user perception of "I've sent an > email to the list but I haven't received a copy back". That is going > to be a big issue/headache for us. It's a long standing PITA with Google. See <https://wiki.list.org/x/4030680>. Your Gmail users can partially mitigate this by setting their Acknowledge posts option to Yes. Note also that Mailman core communicates with archivers to determine what goes in the Archived-At: header and this value is usually based on the Message-ID:. Changing the Message-ID: could possibly render that value incorrect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: hyperkitty failed to create a thread

by tlhackque

On 11-Feb-19 13:01, Abhilash Raj wrote: > On Mon, Feb 11, 2019, at 9:55 AM, Marvin Gülker wrote: >> Hi, >> >> Am 11. Februar 2019 um 19:47 Uhr +0200 schrieb Danil Smirnov: >>> What could be a reason of HyperKitty failing to create a thread from >>> chained emails? >>> >>> For example, see "RECENTLY ACTIVE DISCUSSIONS" on page >>> https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ >>> >>> "Openvpn and Network mapping" discussion displayed as five threads instead >>> of only one... >> This looks exactly like the problem I have been experiencing, see >> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> >> >>> Any ideas how to improve HyperKitty ability to detect threaded >>> messages? >> Sadly, no. Let's hope the problem gets resolved. > Please create a bug report at https://gitlab.com/mailman/hyperkitty/issues with the affected messages. > > It would help us recreate the problem if you could attach a raw messages in the issue. I am > assuming the messages aren't sensitive since the archive are open. Otherwise, feel free to omit > any sensitive information. > > I haven't looked at the threading code in HK since a long time, but my impression is that it > looks at the 'In-Reply-To' header to figure out if the current email is a response to a previous > email that it received. > > In some cases, the order of the incoming messages can cause this to break, like when the > reply comes in first and the original messages comes in later. I am not sure exactly what is > happening here, but looking at the raw messages should help us reproduce and possibly > fix the issue. > I believe that for threading to work more or less reliably, the thing to do is to look at the 'References' header. That should give you the thread in order, and allow any message received out of sequence to be put in the proper location in your display. 'References' should be a superset of Reply-To (which is at most 1 Message-ID), so you only need Reply-To if there is no References - or to handle a client that doesn't obey the RFCs. See https://tools.ietf.org/html/rfc5537#page-15 & https://tools.ietf.org/html/rfc5322#section-3.6.4

6 years, 3 months

[MM3-users] Re: Mails for 1 specific mailinglist not being send and looping in out queue

by Eric Broens

These mails keep looping for days in the out queue and are never shunted. Looks to me as a serious bug. Is there anything that can be done for this? Note that the 29 other mailinglists are working fine. Best Regards, Eric On Saturday, January 9, 2021, 03:52:40 PM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote: In my mailclient it looks like the LF's have been removed. I'll attach the log extracts to make them better readable. Best Regards, Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote: ----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail. The mailman3 error log show that there is a connection failure to port 25. A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail. Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail. Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either. For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue? Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric _______________________________________________ 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/ _______________________________________________ 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/

4 years, 4 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 11:00 AM, Seth Seeger wrote: > > I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: > > Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose > process(mlist, msg, msgdata, start_chain) > File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process > link.function(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), > File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ > self.set_payload(_text, _charset) > File "/usr/lib/python3.8/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 > > There are two owners listed, one of them is also listed as the moderator. This is redundant. Having the same user as both owner and moderator only results in possible duplicate notifications. There is no reason to have an owner also be a moderator. > "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Please do send me the shunted .pck. what is going on is this is an English language list which has character set `ascii` and the notice for some reason has non-ascii, possbbly the Subject: or the user's display name has non-ascii. But possibly the message itself is defective. In any case, I'd like to get the shunted message to see if there's something we should fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: DMARC Mitigation Wrap

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > > MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text. > > The From address of this message has been replaced with the list > address, while the From name has 'via list' appended. Please be > careful when using 'via list' addresses later for new emails, as they > will be sent to the whole list.\r\n -------------------------- > ----------------------------------------------------------------------\r\n > From: Allan Hansen <allan_hansen(a)icloud.com <mailto:allan_hansen@icloud.com>> > Subject: [Testlist] wrap with divider and BLANKLINE > > Which coding option am I missing? I have searched for one online. I assume you are entering your text in Postorius in the DMARC wrapped message text box. There are a number of things going on here. Postorius is wrapping and filling the text and stripping trailing whitespace. If you want more whitespace, I suggest following your text with one or more empty lines and a single dot as in The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list. ------------------------------------------------------------------- . In the above, the blank lines before and after the line of dashes will be preserved as will the final dot which should be unobtrusive enough. More importantly, the rendering of the received message is up to your mail client. Your's apparently begins the wrapped message immediately after the wrapper's text, but many will not do that. Unless you actually view the received message in every mail client used by your user's, you won't know what they actually see. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 09:04 +0100, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 11/2/21 20:15, Mark Sapiro wrote: > > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > I contributed in january to translate to spanish all the items > > > left in > > > Mailman Core, Django-mailman, HyperKitty and Postorius via > > > Weblate. I > > > thought they will be used in the next upgrade, but I cannot see > > > any > > > improvement and there are many words untranslated. > > > > The Spanish translations for Mailman core and HyperKitty are > > currently > > completely up to date with weblate. django-mailman3 differs in one > > string that was translated on Feb 10 and hasn't yet been merged. > > Postorius also differs in a few places from the Feb 10 version that > > hasn't yet been merged. > > Ok. Thanks for checking it. I put my little contribution in Weblate > and I like that it could be used by anyone. Actually, I was going to ask these same questions, because I dedicated some hours to get the Spanish translation nearly finished, it was kind of a "spiritual" need for me, being the person that seeded the efforts for Mailman i18n support back in the late '90s :-) :-) > I tried to run this using the same command as I did for the > "collectstatic" (that solved all my previous problems for the > upgrade) > and "migrate" runs but it shows me an error: > > su -m mailman3 -c "python3 manage.py compilemessages" > CommandError: This script should be run from the Django Git checkout > or your project or app tree, or with the settings module specified. I got this very same error, and was also confused, as manage.py runs at the project level, not application level. > I'm lost. Do not feel bad, Guillermo, an old time pythonist with message translations experience, that uses i18n for some of his applications, is also dazzled and confused :-) Confused-with-translations-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 3 months

[MM3-users] Re: Process on migrating mailman

by Odhiambo Washington

On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > About 500 list. Not sure how to check size of the archives. > > On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > >> >> >> On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> >> wrote: >> >>> Any suggestion on how to migrate mailing list and archirve with >>> diffirent server and domain. For the mailing list from >>> sample.domain1.example.com to sample.domain2.example.com >>> >>> Old Mailing list >>> Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) >>> [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] >>> Domain Domain1.example.com >>> >>> New Mailing list >>> Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) >>> [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] >>> Domain domain2.example.com >> >> >> >> How many lists? How big are the archives? >> >> Looking at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, >> it seems like it's not a trivial exercise. >> >> However, I am wondering about the consequences of: >> 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then >> re-importing >> 2. editing settings.py and webserver config to reflect the DOMAIN2 >> 3. reconfiguring your MTA to handle list mails using the DOMAIN2 >> >> I am imagining a virtualenv type of installation. >> > The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… . -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Re: Can you use @list to include members in accept these non-members in v3?

by Lieuallen, Thomas Otis

Danil, That looks awesome, as do several other features and fixes. It doesn’t look like 3.3.10 is released yet, though. Any ideas on when that might happen? Thank you for directing me there. Tom Lieuallen From: Danil Smirnov via Mailman-users <mailman-users(a)mailman3.org> Date: Thursday, September 5, 2024 at 3:45 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Can you use @list to include members in accept these non-members in v3? [This email originated from outside of OSU. Use caution with links and attachments.] Hi Tom, This feature has been added recently in version 3.3.10, see "New Features" in the changelog: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…<https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/docs/NEWS.rst> Sincerely, Danil Smirnov Mailman3.com On Thu, Sep 5, 2024 at 12:22 AM Lieuallen, Thomas Otis < Tom.Lieuallen(a)oregonstate.edu> wrote: > No answers yet on this, so I’m not hopeful that MM3 supports this > feature. I guess I’ll start on a script to update the list of allowed > senders. > > Thank you > > Tom Lieuallen > > From: Lieuallen, Thomas Otis <Tom.Lieuallen(a)oregonstate.edu> > Date: Thursday, August 29, 2024 at 2:35 PM > To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> > Subject: Can you use @list to include members in accept these non-members > in v3? > In Mailman v2, one could use @listname in ‘accept_these_nonmembers’: > > A line consisting of the @ character followed by a list name specifies > another Mailman list in this installation, all of whose member addresses > will be accepted for this list. > > I don’t see this option listed in version 3. Is it no longer > supported/allowed? Is there another option? > > We often send email to lists of lists and have loved that @listname option > to help us deliver email to 20+ lists without needing to approve the emails > each time or reconfigure all the lists when another sender needs to be > added. > > Thank you > > Tom Lieuallen > Oregon State University > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> > Archived at: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to danil(a)smirnov.la > _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

9 months

[MM3-users] Re: New year releases!

by Jeff

I finally got around to doing this upgrade. I followed the instructions at: https://docs.mailman3.org/en/latest/upgrade-3.2.html Everything seemed to go fine but, mailman3 failed to start because “_BindParamClause” could not be found in sqlalchemy.sql.expression. It looks like alembic-1.6.2 is not completely compatible with SQLAlchemy-2.0.6. I fixed the problem by hacking sqla_compat.py in alembic-1.6.2, but should Mailman start requiring a newer version of alembic? > On Jan 4, 2023, at 4:59 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hello Everyone, > > Happy new year! > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.8 [1] > 2. Postorius 1.3.8 [2] > 3. Hyperkitty 1.3.7 [3] > 4. Mailmanclient 3.3.5 [4] > 5. Django-mailman3 1.3.9 [5] > 6. Mailman-hyperkitty 1.2.1 [6] > > All the releases are published to PyPI and you can find links to all the PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. > > Thanks to all the contributors for making this release possible! > > If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available > here: https://docs.mailman3.org/en/latest/ > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to mm3(a)steele.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/vnd.microsoft.icon Name: favicon.ico Replaced multipart/alternative part with first alternative.

2 years, 2 months

[MM3-users] Re: Weird behavior with Outlook and any MM3 List

by Thomas Ward

Ye it gets a little tricky when we have custom thread IDs being added. I could do some postprocessing on a reply and see what the "In-Reply-To" header says if I can figure out how to fetch the previous message subject line for the custom need for my workplace with a thread/post ID in the subject line. I'm going to experiment with alternative brackets and see if it still does it. While also opening a support ticket with Microsoft to give me a chance to rage at them. I'll report back if I find a solution/alternative. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, November 1, 2023 2:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Weird behavior with Outlook and any MM3 List On 11/1/23 09:42, Thomas Ward via Mailman-users wrote: > I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). > > When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. > > While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. > > Has anyone observed this behavior before? If so, have you found any workarounds? This is a Microsoft/Outlook issue. As you note at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… this is just the way Outlook displays the message subject. I know of now way around this, but I don't use Microsoft MUAs. Does Outlook also strip the prefix from replies? This probably wouldn't matter for replies to the list as the list will add it back, but might be an issue for other direct recipients. Presumably, Outlook is looking at the [] around the prefix. You might try either dropping the brackets or using something else such as _My-List_ instead of [MyList]. -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

1 year, 7 months

[MM3-users] Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

Hello everyone, I am starting a new thread on this so that the issues I encountered do not get mixed up with the other discussions. Over the weekend I upgraded an MM3 installation to the latest versions of the components. I started off by creating a new venv, installing and then migrating the configurations and the scripts. In the end, I ended up with MM3 Core ==3.3.7, postorius==1.3.7, HyperKitty==1.3.6, django==4.1.3. 1. SQLAlchemy - At the stage where one runs 'mailman info', I encountered the first error: : sqlalchemy.exc.NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:postgres This is solved by a change in mailman.cfg so that the URI starts with postgresql:// instead of postgres://. SQLAlchemy used to accept both but has removed support for the postgres name. <https://github.com/sqlalchemy/sqlalchemy/issues/6083#issuecomment-801478013> 2. Django==4.x At the point of running the post-update processes, particularly the "migrate" bit, I got the following error: : ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/urls/__init__.py) I understand this is a consequence of the django.conf.urls.url() having been deprecated starting version 3 and has been removed in version 4 of Django. https://docs.djangoproject.com/en/4.1/releases/4.0/#features-removed-in-4-0 The upgrade process seems to have brought in the newer version of Django because now I have 4.1.3 up from 3.x If anyone wants, I found an elaborate explanation at https://bobbyhadz.com/blog/python-importerror-cannot-import-name-url-from-d… . My Google-fu found suggestions that in urls.py, I should import re_path and use it, or alias it for url for the migrate to work. The solution I used was to alias url to re_path, but I am considering just doing away with url altogether. Not sure which is the better option between using re_path or path. So here is the patch I have used: (venv) mailman@lists:~/mm$ diff -u urls.py.bak urls.py --- urls.py.bak 2022-12-03 12:20:28.028090659 +0300 +++ urls.py 2022-12-03 12:36:20.298875624 +0300 @@ -17,7 +17,8 @@ # Postorius. If not, see <http://www.gnu.org/licenses/>. -from django.conf.urls import include, url +from django.conf.urls import include +from django.urls import re_path as url from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView 3. The last issue that I encountered is one I kind of solved, but completely don't understand the consequences of the solution I applied: /opt/mailman/mm/bin/django-admin migrate <CUT> System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount </CUT> Here again, Google-fu came to the rescue. I added the following line to settings_local.py and the warnings were suppressed. DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' I need to understand how this affects everything and how this is likely to impact the functionality of MM3. What is the proper solution for this? And should it be django.db.models.BigAutoField or django.db.models.AutoField? Which is which? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

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

by Stephen J. Turnbull

Onyeibo Oku writes: > I am not sure I understand what you mean by apps. Is that Django apps > (./manage.py startapp app)? Do you mean a Django Project instead > (./manage.py startproject app)? An app for my purpose is everything configured via the settings.py used by the Django application created in a wsgi.py file. I guess you would think of them as projects. > What I have here is an active website project (live) done on Django > framework. It runs from a different virtual environment (venv). > > hence: > mailman --> /opt/mailman/venv > website --> /srv/website/venv (has a running uwsgi instance) The venvs isolate the Python code used by each app from the other. But the apps can still have conflicts over ports (this is mentioned in the Django docs), filesystem objects, and other resources. For example, a lot of applications use the /static/ location as a place to keep content that is supplied by your project and doesn't change. This is problematic if two different apps each wants to install a default.css, but they're different. One of the apps is going to look funny. Only the person who configures the apps can guess whether this kind of conflict will arise. Neither Mailman nor Django itself tries to protect you from such conflicts (I don't see how they could, in fact). > > > In whichcase, it doesn't hurt to follow the doc to its logical > > > conclusion? > > > > I don't understand what you mean by logical conclusion. > > > > That is to follow the guide to the end of the page (disregarding > the possibility of conflicts). No, you can't disregard the possibility of conflicts. My understanding from what you've posted so far is that you have an app "website" that is already implemented and running. Most likely that app has configured resources (specifically ports and website locations in particular /static/) that are likely to conflict. You need to manage those conflicts, most likely by changing the ports used by Mailman, Postorius, and Hyperkitty and by mapping a different location such as /mailman/static/ to the /var directory that actually contains the static files managed by "manage.py collectstatic". There may be other possible conflicts, but I can't help you with those because they depend on your website code. Steve

2 years, 7 months

[MM3-users] Re: Email verification

by Abhilash Raj

On Sun, Feb 9, 2020, at 9:38 AM, Allan Hansen wrote: > Thank you, Abhilash. > Yes. People are getting these messages. I just got a message from one who had the issue. I asked her to try to sign in again and then she got the verification message. > > It’s just that some have issues, and I’d like to be able to help. Can you check your MTA logs to see if those confirmation emails were indeed sent out? It would help figure out of the email was never sent out or whether they didn't receive it. > Yours, > > Allan Hansen > hansen(a)rc.org > > > >> On Feb 9, 2020, at 9:12 , Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> >> >> On Sun, Feb 9, 2020, at 8:05 AM, Allan Hansen wrote: >>> Some members cannot get past the email verification when they create >>> their accounts. >>> They insist that they have looked in their spam folders. Their email >>> addresses they entered are correct - the are able to log into their >>> accounts with the right email address. But they get the message saying >>> that a confirmation message was sent and if they don’s see it to >>> contact us. >> >> Is your Django configured to send out emails? >> >> https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir… >> >> >>> >>> 1. Who is ‘us’? My members are asking... >>> 2. How do I help them? >>> >>> I tried subscribing them to a bogus list with pre-verified email, but >>> that did not work, so both they and I are stuck. >>> Tried finding help in archive, but did not see anything. >>> >>> Yours, >>> >>> Allan Hansen >>> hansen(a)rc.org >>> >>> >>> >>> >>> _______________________________________________ >>> 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/ >> >> -- >> thanks, >> Abhilash Raj (maxking) >> _______________________________________________ >> 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/ -- thanks, Abhilash Raj (maxking)

5 years, 4 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark for your response. But I am having a final query over this issue. Out of the two hyperkitty records I observed in the database, I am confused which record do I need to remove directly from the database? Because I doubt still there is one more list with the same style i.e. with two hyperkitty records. Please advise. On Mon, Jul 27, 2020 at 4:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > > Thank you Mark. > > > > What you have said is right.. > > > > I found a list with two "hyperkitty" records in the listarchiver in the > > database. I had removed the list and recreated it and now I found it is > > working fine. The recreated list is having only one record. > > > OK, but that's not a reasonable way to fix this in general. You can just > remove the `extra` record using a direct database query which is > probably the least disruptive way to fix this. > > > > After searching the links you provided I found there is just a work > around > > but not the precaution to be taken for not getting the duplicate record. > > > > Can you say what might be the reason for this duplication? If I need to > > provide any details, please let me know. > > > As noted in the threads I referenced, we don't know the cause. Yours is > the first report of this issue with the `hyperkitty` archiver. In all > the other reports, the duplicate archiver has been `mhonarc`. > > If it happens again and you know the exact sequence of events that led > to it, i.e. what was done with the list between the last time it worked > and when it stopped working, that might give us clues, but currently we > are at a total loss to understand how this happens. > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 10 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by alexs＠ecoscentric.com

Mark Sapiro wrote: ... > I thing just dumping and loading the databases and copying mailman.cfg > and the Django settings should do it. Are the domains the same on the > new server? If not there may be issues with that. I'd need to see the > exception and traceback to say more. I am migrating from mailman 3.2.1 & mailman3-web 0+20180916-8 on Debian Buster to mailman 3.3.8 & mailman3-web 0+20200530-2.1 on Debian bookworm, have mailman3 and mailman3-web configured (and running on bookworm) from the initial install. But when I use the mailman3-web 0+20180916-8 database (after stopping mailman3 and mailman3-web) on bookworm, unfortunately migrate fails: # mailman-web showmigrations account [X] 0001_initial [X] 0002_email_max_length admin [X] 0001_initial [X] 0002_logentry_remove_auto_add [X] 0003_logentry_add_action_flag_choices auth [X] 0001_initial [X] 0002_alter_permission_name_max_length [X] 0003_alter_user_email_max_length [X] 0004_alter_user_username_opts [X] 0005_alter_user_last_login_null [X] 0006_require_contenttypes_0002 [X] 0007_alter_validators_add_error_messages [X] 0008_alter_user_username_max_length [X] 0009_alter_user_last_name_max_length [X] 0010_alter_group_name_max_length [X] 0011_update_proxy_permissions [X] 0012_alter_user_first_name_max_length contenttypes [X] 0001_initial [X] 0002_remove_content_type_name ... # mailman-web migrate --plan Planned operations: contenttypes.0001_initial Create model ContentType Alter unique_together for contenttype (1 constraint(s)) auth.0001_initial Create model Permission Create model Group Create model User account.0001_initial Create model EmailAddress Create model EmailConfirmation account.0002_email_max_length Alter field email on emailaddress admin.0001_initial Create model LogEntry admin.0002_logentry_remove_auto_add Alter field action_time on logentry admin.0003_logentry_add_action_flag_choices Alter field action_flag on logentry contenttypes.0002_remove_content_type_name Change Meta options on contenttype Alter field name on contenttype Raw Python operation Remove field name from contenttype ... But the migrate fails at the first operation: # mailman-web migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying contenttypes.0001_initial...Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 239, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (1050, "Table 'django_content_type' already exists") ... Indeed the table django_content_type already exists on 0+20180916-8 . Apart from fields changes, there are an additional 4 tables in mailman3-web 0+20200530-2.1 I managed to import the mailman 3.2.1 database to the mailman 3.3.8 database, and all lists, subscriptions and settings looks fine. So how can I upgrade my existing mailman3-web database?

1 year, 8 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Fri, Aug 2, 2024 at 5:51 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/08/01 10:09, Roland Giesler via Mailman-users wrote: > > > > I needed to put these files at these locations: > > > > transport_maps = > > hash:/etc/mailman3/data/postfix_lmtp > > local_recipient_maps = > > hash:/etc/mailman3/data/postfix_lmtp > > relay_domains = > > hash:/etc/mailman3/data/postfix_domains > > > > However, since I'm using power-mailinabox, Postfix is configured to > > use sqlite already and has these lines by default: > > > > virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf > > virtual_mailbox_maps=sqlite:/etc/postfix/virtual-mailbox-maps.cf > > virtual_alias_maps=sqlite:/etc/postfix/virtual-alias-maps.cf > > local_recipient_maps=$virtual_mailbox_maps > > > > So I have only added this line to postfix's main.cf: > > > > # Add postfix_domains path so mailman can add domains to it for lists > > relay_domains=hash://etc/mailman3/data/postfix_domains > > > > The local_recipient_maps are set by power-mailinabox already, so I'm > > ignoring what mailman creates. > > > It seems that this is a mistake. If I don't let postfix read the > local_recipient_maps that mailman3 created, the incoming emails are not > sent to the other host. So I have a conflict with the > local_recipient_maps that postfix has (created by Power-mailinabox) and > those created by mailman3. > > I'm hoping that if I specify local_recipient_maps more than once and > then both sources will be considered. Would that work? > > If not, then I'm pretty much stumped, unless I go for the database > option that has not been merged yet. Even if I do that, I would need to > make sure that mailman3 doesn't remove the other entries in the database > which, judging by what I've seen, seems to be the case. > > Any ideas? > Quoting the official documentation: https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta ``` If your current main.cf contains settings for these items, including the default setting for local_recipient_maps, you should add the Mailman setting to the existing setting rather than replacing it. ``` Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months, 1 week

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: > >Hi Mark, > > > >Actually all this stuff happens inside the container after it's started > >and > >initialized without errors. I didn't amend the image anyhow. > > > >Also I have the configuration based on docker-compose.yaml provided in > >the > >repository which works just fine for mailman-web image. > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > >fails > >with 500 error... > > > >Now answering your questions: > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > >what > >> is set for Q_CLUSTER? > >> > > > >I've checked settings.py inside the container and I haven't found any > >of > >the mentioned configurations there. > > > >Does the manage.py that's being run here point to the right > >settings.py? > >> > > > >No clue. > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > >configured image? > > > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > Because I am a dum dum ;-) > > Will work on removing those crons and stuff. Would be nice if you > opened an issue on Github so that I don't forget. Should now be fixed in the latest image. > > >Danil > > > > > > > >> -- > >> Mark Sapiro <mark(a)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 > >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > >_______________________________________________ > >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/ > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- thanks, Abhilash Raj (maxking)

6 years, 3 months

[MM3-users] Re: Sendgrid experiences

by Andrew Hodgson

Hi. Thanks for the recommendation on the Google Workspace. How did you set this up in terms of the domain, since I don’t want to use Google Workspace as the main email provider for this domain. Also did you have to set anything special in Mailman? Thanks. Andrew. From: Stephen Daniel <swd(a)pobox.com> Sent: Thursday, May 11, 2023 2:57 PM To: Andrew Hodgson <andrew(a)hodgson.io> Cc: Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp>; mailman-users(a)mailman3.org Subject: Re: [MM3-users] Re: Sendgrid experiences I would definitely look for alternatives to SendGrid. I tried using them and had a very poor rate of people actually getting my emails, even when I temporarily upgraded to an expensive plan with a dedicated IP address. I'm currently hosting mailman in Google Cloud and relaying outbound mail through a Google Workspace account. It's working OK. The workspace account costs me $6/month for basically unlimited mail relay. On Thu, May 11, 2023 at 9:50 AM Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> wrote: Stephen J Turnbull wrote: >2023-05-10 03:49 に Andrew Hodgson wrote: >> Sendgrid is maintaining the Message-Id header which is good for >> archiving. It is re-writing the Return-Path header though which means >> that bounce handling in Mailman won't work, but I think all the >> services do this in some way so I am happy to live with that for the >> moment. >How does it rewrite the Return-Path? Returned mail is not something that such a service would be able to handle properly (although they can help with apparently returned spam). If mail is legitmately sent and returned as undeliverable, only the author or their agent will know how to handle it. So such >services should provide some way to find out about returned mail. An example: Return-Path: bounces+[Sendgrid GUID]-andrew=hodgson.io(a)em6096.lists.hodgsonfamily.org<mailto:hodgson.io@em6096.lists.hodgsonfamily.org> Sendgrid provide information about bounces but crucially that bounce isn't forwarded back to the original return-path sender (i.e, Mailman). A few people have pointed out they can provide list hosting at a cheaper cost than Sendgrid so I'm looking for alternatives again. Andrew. _______________________________________________ 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to swd(a)pobox.com<mailto:swd@pobox.com>

2 years

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Guillermo Hernandez (Oldno7)

El 21/4/23 a las 10:37, Odhiambo Washington escribió: > > > On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: > > I'm having troubles with Django and cannot access to web admin. > > I need to unhold a message while figures out what is happening. > > Searching the mailman cli help commands didn't help me. > > Anyone who knows how to unhold a message, please? > > > TBH, I find it a lot easier to fix the web UI than mess with the > python shell :-) > > While you wait for @Mark Sapiro <mailto:mark@msapiro.net> to save you, > you can be reading the following: > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Thanks: it seems the place to do it (I didn't find it) I'm fighting the web UI problem. It seems that something in wsgi has changed and is no more compatible with my version of things. Error log from apache shows: mod_wsgi (pid=30632): Failed to exec Python script file '/usr/local/mailman3/wsgi.py'. mod_wsgi (pid=30632): Exception occurred processing WSGI script '/usr/local/mailman3/wsgi.py'. Traceback (most recent call last): File "/usr/local/mailman3/wsgi.py", line 34, in <module> from django.core.wsgi import get_wsgi_application File "/usr/local/lib/python3.9/site-packages/django/core/wsgi.py", line 2, in <module> from django.core.handlers.wsgi import WSGIHandler File "/usr/local/lib/python3.9/site-packages/django/core/handlers/wsgi.py", line 3, in <module> from django.conf import settings File "/usr/local/lib/python3.9/site-packages/django/conf/__init__.py", line 19, in <module> from django.utils.deprecation import RemovedInDjango50Warning, RemovedInDjango51Warning File "/usr/local/lib/python3.9/site-packages/django/utils/deprecation.py", line 4, in <module> from asgiref.sync import iscoroutinefunction, markcoroutinefunction, sync_to_async ImportError: cannot import name 'iscoroutinefunction' from 'asgiref.sync' (/usr/local/lib/python3.9/site-packages/asgiref/sync.py) Yesterday all were running without problems, today is another day X) > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] -- ___________________________________________ 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, 1 month

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 12:15 AM, Peter Münster wrote: > > It seems, that mailman bounces the bounces, so that the list-owner never > sees them: > > --8<---------------cut here---------------start------------->8--- > postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] > postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] > postfix/cleanup[11841]: 879D6F12E8: message-id=<> > postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) > postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) > postfix/qmgr[10092]: 879D6F12E8: removed > --8<---------------cut here---------------end--------------->8--- There are a few things going on here. It appears that out04.smtpout.orange.fr has bounced a list post from the <test(a)my-domain.org> list and and sent a DSN back to Mailman at <test-bounces(a)my-domain.org>. It is this DSN that has no Message-ID:. Mailman's LMTP runner rejects such messages. The underlying issue is the orange.fr domain is sending DSNs without a Message-ID: header. > What could I do please, to get the bounces? I would like to use VERP to > identify wrong addresses... If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] section of your config), this log message > postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) would contain to=<test-bounces+user=example.com(a)my-domain.org> and you could identify the bouncing address (user(a)example.com in this case) that way. Beyond that, there are still other issues, the biggest of which is currently, Mailman is not processing bounces other than storing them in the database. See <https://gitlab.com/mailman/mailman/issues/343>. Also, the LMTP runner requires a Message-ID: at least in part because that is part of the algorithm for creating a unique ID for archiving. Given that messages to a -bounces address are handled differently and not archived, it would be possible to not require a Message-ID: for those messages, but arguing against that, if a recipient MTA can't create a DSN that has a Message-ID:, would you trust what else it does? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: moving individual list to different domain

by Johannes Rohr

Dear Mark, thanks as always for your very thorough explanation. I guess, it is simply not practical then... Cheers, Johannes Am 21.03.23 um 19:11 schrieb Mark Sapiro: > On 3/21/23 06:21, Johannes Rohr wrote: >> Dear all, >> >> on mailman2 it was possible to move a list to a different domain >> within the same mailman instance. >> >> I have found no information on how the same can be accomplished on >> mailman3. >> >> Is this possible at all? > > > In mailman 2.1, a list was identified by its name only without the > domain and those names had to be globally unique. A site could be > configured to support multiple virtual hosts and a list had a > host_name attribute which could be changed if desired to assign the > list to a different virtual host, but there couldn't be two lists with > the same name even if they had different host names. > > Mailman 3 is different. In order to remove the restriction that list > names (without the domain) had to be globally unique, in MM 3 the > domain is part of the list name. I.e., we can now have > list(a)example.com and list(a)example.net as two distinct lists in the > same installation. > > Suppose we want to rename list(a)example.com to list(a)example.net. This > becomes involved in Mailman 3 because it affects not only Mailman > core, but also mail delivery and archiving. Furthermore, the list with > fqdn_listname list(a)example.com has the list_id list.example.com. If we > change the fqdn_listname to list(a)example.net, the list_id should > remain list.example.com per RFC 2919 Sec. 4. > <https://www.rfc-editor.org/rfc/rfc2919>. We can just change the > list's mail_host attribute via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or via a database query, but this leads to confusion. I.e., a URL like > https://example.com/mailman3/lists/list.example.com/ will still work > but https://example.com/mailman3/lists/list@example.com/. > > To avoid this, we could also change the list_id, but we can't do that > via REST as it's a read-only property, and changing the list_id says > this is really a new list, not the same list with a new name. > > Also, none of this addresses archiving. >

2 years, 2 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mohsen Masoudfar

Thank you Mark! [EXTERNAL EMAIL] On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? >> Sorry, It was my misunderstanding. DMARC mitigation is functioning well for newly created lists, even with Gmail addresses. >> I am suspicious that Gmail might be rejecting or bouncing emails from the list due to the reputation of those lists. >> It's worth noting that I am not the owner of the lists, but admin the Mailman3 infrastructure. My objective is to determine if our suspicious is accurate, whether Gmail is rejecting emails because of the bad reputation. We have asked Google, but no response so far. >> I am interested to know more about the reasons behind these bounces, they are all handled by Postfix and deleted. > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. >> Is there a way to send them to a mailbox? Or prevent them from being deleted, so that I can look into the message body? -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

1 year, 8 months

Search results for query "dO"