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

[MM3-users] Help with installing Postorius and Hyperkitty on Ubuntu 19

by andrew.bernard＠gmail.com

I'm new to Mailman. I have a Ubuntu 19 production server. I attempted to get Mailman 3 and the web components going with the system packages, but I encountered a few showstopper errors (such as indexing not working at all) which I know have been fixed in the codebase. To that end I erased my installation, and installed mailman from the gitlab source. That all works much more nicely now and I feel I have a lot more control of the layout of all the files (the various Ubuntu packages smear the parts all over the place, confusingly). Now I want to get Postorius and Hyperkitty going again, independently of Ubuntu packages. I would like to run Postorius and Hyperkitty under one Django project. So I downloaded the git source for mailman_web. I do not know if this is the right way to install. I am partially familiar with Django, but to come to the point, I have no idea once having obtained the source from git how to setup and install the project, where it lives in the filesystem, and so on. Are there any pointers to help in this area? The very nice readthedocs format files for Postorius and Hyperkitty are very silent on basic matters like this, which is not of much help! The git README files also define a new level of brevity. I need some initial hand holding here. If any help is forthcoming, such as links to more full documentation for newbies to Mailman, I would be most grateful.

6 years, 1 month

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

by Stephen J. Turnbull

David Newman writes: > As for FQDN, is there some reason we shouldn't use the definition from > RFC 1594, section 5.2? For the definition, yes, that's fine. But there's more to it if somebody needs to figure out how Mailman uses the term. One issue is that we don't necessarily follow those definitions exactly, especially when validating. ISTR somebody got in trouble because they had a very unusual (but technically legal) character in an email address. It's a little risky to put implementation details like that in separate documentation rather than chanting "Use the Source, Luke", but on the other hand even if somebody knows where to find the source they may have difficulty reading a regular expression. And in this particular case, the regular expression used to parse the URL accepts almost anything (possibly including Chinese characters and emoji :-) in the FQDN. Another thing we might want to put in such a glossary item would be under what circumstances we query DNS to check it's valid. Doing that for *everything* would be a massive undertaking, of course, but it might be worth trying to add such items when we (core devs) get a question, rather than requiring people to search the archives to research it on their own. And for other contributors like you, if you remember having in issue with a term, eg, not recognizing its significance in an error message, you might add it to the glossary. I'm not sure this is a great idea at all, just throwing things at the wall. Steve

3 years, 8 months

[MM3-users] Re: Messages not going to held queue

by Mail Person

I have it set so that members automatically go to the moderation queue from the Postorius settings. To make sure that wasn't the issue, I also added a test subscriber account to the list and set them manually to have their messages held for moderation. I then set them to "accept immediately" to make sure Postorius settings were taking effect. When "accept immediately" was set, the messages were sent through. When they were set to be held for moderation, the user did not get a moderation email, myself as the moderator did not get a notification, and Postorius did not show them in the held messages queue. As far as logs, in var/log/mailman3 I do not see any logs other than mailman.log, plugins.log and smtp.log. In the SMTP log I can see that the message is getting to mailman: Sep 07 20:10:08 2022 (2837) ('127.0.0.1', 45958) Data: b'MAIL FROM:<test email>' Sep 07 20:10:08 2022 (2837) ('127.0.0.1', 45958) sender: test email Sep 07 20:10:08 2022 (2837) ('127.0.0.1', 45958) Data: b'RCPT TO:<test@domain>' however no action is taken after that. In the cases where the message is sent I there are two actions showing the message going out: Sep 07 20:10:09 2022 (2839) <stuff(a)mail.gmail.com> smtp to test@domain for 2 recips, completed in 0.14289569854736328 seconds Sep 07 20:10:09 2022 (2839) <stuff(a)mail.gmail.com> post to test@domain from testemail, 2969 bytes This leads me to believe the message is being discarded or for some reason not getting to the moderation queue.

2 years, 10 months

[MM3-users] Re: Finding a mailman3 installation description that works

by Abhilash Raj

On Tue, Mar 31, 2020, at 11:28 AM, Andrew Hodgson wrote: > ralf.wiegand(a)tena-sda.org wrote: > > >WE are currently using mailman2. I have the task to setup and install a maiman3 server. Postfix is installed and working. Can anybody point me to a link where the actual installation is described using RHEL 7 or RHEL 8. This will be a >hardened DISA compliant server, so I am trying to avoid installing compilers and tools that are not part of the standard RHEL 7 repos. > > Have you looked at creating a development environment using a Python3 > venv somewhere else (eg another server or container) then copying the > venv out to the production server? Python virtualenvs are really not movable because of the paths that are in there. It is tricky to get that working right, I would caution against doing that. There is a Virtualenv based installation guide at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > I found the following very useful: > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > > Granted you will need RedHat packages for Python, Postfix and the web > server, but everything else can be installed in the Python virtual > environment and ran from there using the scripts on that site with > minor tweaking. > > Hope this helps. > 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, 4 months

[MM3-users] Re: The future is here?

by Jonathan M

On 8 Jan 2021, at 04:18, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Discourse is a different kettle of fish. They concentrate on the much > more straightforward (from a network and interapp communication > configuration standpoint) web service because that's what their users > expect. Mail is a lot more baroque from that standpoint. > > We shouldn't hope to successfully "encourage" hosts to do things our > way. Maybe Mail-in-a-Box is a useful comparator in terms of complexity (though it appears to be less configurable than Discourse, and the software itself is not comparable). Maybe my experience hasn’t been typical. I’ve mainly used a shared server which didn’t have Mailman installed, but of course had email set up. It was relatively easy to install Mailman 2 but impossible to install Mailman 3. I could probably install Mailman 3 on Digital Ocean or similar, but get the feeling that the mail server is the hardest part. If I ever can set aside enough time to get it working I should write the idiot’s guide that I needed. It would be great if there were a “Mailman-in-a-Box” including everything necessary to get Mailman working from scratch on a VPS (in addition to the primary, flexible way that allows experts to use Mailman 3 according to their personal preference). I will look into Abhilash’s Docker container setup. I think the first time I saw that I didn’t know he was “maxking” and assumed it was a third-party thing that would likely be abandoned. Best wishes Jonathan

4 years, 6 months

[MM3-users] Re: Can login at /admin, but cannot login at the account/login page.

by Stephen J. Turnbull

Gonzalo Cardenas writes: > Actually it doesn't let me in to the login page / sign up page (the > HTTP requests hangs until it times out). The URL I'm trying to > access is http://localhost/accounts/login/?next=/mailman3/lists/ or > http://localhost:8002/accounts/signup/?next=/mailman3/lists/ > eventually Nginx returns a "502 Gateway timeout error" The second URL appears to presume Postorius is actually running on port 8002, but this > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; tells nginx to proxy to port 8000. I don't use nginx or uwsgi myself (I use Apache and mod_wsgi) so I am not very confident. But you need to make sure that all of the configuration files use the same port. I don't remember if any of the webservers suffered from this, but some programs don't map 127.0.0.1 to localhost. If any of the configs specify localhost for the Postorius URI, you could try using 127.0.0.1 instead. If making all these port configurations consistent doesn't do the trick, please post your mailman-web settings.py, uswgi config, and nginx config. You can substitute fake domain names and IP addresses if you're worried about privacy of your configs, but make sure that (1) if the configs specify several IPs or several domain names, you distinguish them in your fake versions, and (2) always substitute the same fake IP/name for a given real IP/name. Steve

3 years, 2 months

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

by Mark Sapiro

On 1/3/23 00:31, Onyeibo Oku wrote: > > (1) Mailman refuses to resolve to a preferred subdomain. If the > server's domain is "website.tld", I'd like mailman's homepage to be > at "list.website.tld". Mailman insists that I add "website.tld" to > the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an > ALLOWED HOST (same VPS/IP address nonetheless). The result is that > the homepage ends up at "https://website.tld/mailman3/lists" when the > desired url is "https://lists.website.tld/mailman3/lists". This is a > conflict because the main domain is intended for another service. How > do I approach this? This is all configured in your web server. It needs to proxy requests for lists.website.tld to gunicorn and depending on the web server, may need more. E.g. see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for nginx. > (2) See the traceback below: > ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server > Error: /mailman3/lists/ Traceback (most recent call last): ... > "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", > line 650, in get raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. > > It seems a migration is missing. How should I approach this? Set SITE_ID = 0 in your Django settings. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Process on migrating mailman

by Odhiambo Washington

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. Is there somewhere in the data where the DOMAIN1 is hardcoded in a way that it cannot be replaced by a text editor? @Mark Sapiro <mark(a)msapiro.net> ? -- 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: Dealing with email bounces from web signups

by Hans-Martin Mosner

Am 17.03.22 um 03:40 schrieb Mark Sapiro: > > > The issue of more concern to me is when the subscription uses a deliverable address. The owner of that address > receives this unwanted confirmation email which is bad enough, but then sometimes reports it as spam to her ISP which > affects my server's reputation. But, so far, I don't do anything about that either. > As I'm a mail admin for a server whose users get lots of those misguided mails I'd say that the vast majority of them are not from mailing list signups but from web contact forms which automatically respond to entered contact requests with "Dear Polly liked your profile https://bit.ly/crap". I regularly report these as spam and expect website owners to disable automatic mails from such forms (I also advise our users who have their own websites to disable that, and strictly filter it on outgoing mail). I would probably also report these as spam when coming from mailing lists subscription requests, and I would likewise advise you to send subscription responses only after a moderator checks and releases the subscription request. It can still happen that you send out somethin to someone who didn't subscribe, but you should be able to reduce the numbers significantly. I know this causes extra moderator work because you don't get the automated pre-filtering for deliverable addresses, so this is something where you need to weigh pros and cons for your particular situation. Cheers, Hans-Martin

3 years, 4 months

[MM3-users] Mailman web interface / uwsgi

by Jan Eden

Hi, I followed the installation instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, which thankfully shielded me from configuring the Django applications for the web interface manually. All Django applications (postorius, hyperkitty, haystack etc) are loaded via mailman_web/settings/base.py, which is in turn referenced by the top-level settings file in /etc/mailman3. uwsgi is linked to mailman_web via /etc/mailman3/uwsgi.ini. So far, so good. I do not want to dive into the interaction between the various components and just want to switch from a http socket (http-socket = 0.0.0.0:8000) to a file socket (socket = /opt/mailman/mm/var/mailman.sock). After making this change in /etc/mailman3/uwsgi.ini, I applied it in the nginx proxy configuration proxy_pass http://127.0.0.1:8000; → proxy_pass http://unix:/opt/mailman/mm/var/mailman.sock; and received an error message (as expected): 2022/11/25 18:39:12 [error] 2978606#2978606: *3 upstream prematurely closed connection while reading response header from upstream, client: 37.201.155.65, server: lists.eden.one, request: "GET /mailman3/lists/ HTTP/2.0", upstream: "http://unix:/opt/mailman/mm/var/mailman.sock:/mailman3/lists/", host: "lists.eden.one" There are obviously a couple of places where the http-socket on port 8000 is referenced (e.g. mailman_web/settings/mailman.py, /opt/mailman/mm/hyperkitty.cfg). Is there an overview of the required changes when using a different (file) socket? Related question: My own (much simpler) Django applications use the following (e.g. in mysite_nginx.conf): upstream django { server unix:///private/tmp/mysite.sock; } location / { uwsgi_pass django; } instead of the "http://unix:/..." notation I tried for Mailman above. Is there any difference between the upstream/uwsgi_pass combination and the proxy_pass variant? Thanks, Jan

2 years, 8 months

[MM3-users] Re: Welcome message issue

by Mark Sapiro

On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Ann: Mailman Core 3.3.5b1 is out

by Abhilash Raj

Hello Everyone, I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a pre-release for 3.3.5, which is slated to come out in 3 weeks from now. I am planning for a 2 week beta period, after which I'll release the first RC and then stable a week after. Right now I am not planning to release a second beta version, but if there are several changes in Core in the next week or so, then I might. This release includes a lot of bug fixes and some new features. It also includes a security enhancement that improves the authentication of REST API by adding resistance to some timing channel attacks. A full list of changes in this version can be found here[1]. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… We have also made improvements in the i18n workflow and now the email templates are updated from the translated messages in the .po files that we get from Weblate. Documentation for translators is available here[2] if you want to help translate Mailman into your native language. [2]: https://docs.mailman3.org/en/latest/translation.html This is a pre-release version, if you want to test it with your setup, you can install it using: $ pip install --pre mailman==3.3.5b1 If you want to download a release tarball, you can do so from here: https://pypi.org/project/mailman/3.3.5b1/#files This release received a lot of contributions from community, which I am really happy about! I'd like to thank everyone who made this release possible! -- thanks, Abhilash Raj (maxking)

3 years, 10 months

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 9:22 PM, David Newman wrote: > > On my system that file lives here: > > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py It appears that you have installed following https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… and in that case, this is the file. > But the error persists after this addition and restarting MM3 and > mailmanweb and nginx: > > url(r'^mailman/', include('postorius.urls')), > > There is this 404 error in uwsgi.log: > > [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed > Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 > bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on > core 0) However, that's not the issue. You originally reported and I didn't look closely enough: > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. That URL is from a Mailman 2.1 installation. Are you still running Mailman 2.1? If so, you need to support Mailman 2.1's CGIs. In Apache, this would be something like ScriptAlias /mailman/ /parh/to/mailman/cgi-bin/ but nginx doesn't do that. You would need something like location /mailman/ { proxy_pass <something that can serve Mailman 2.1's CGIs.> } The something could be apache or ?? -- 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: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/22/23 09:32, Stephen J. Turnbull wrote: > > To diagnose, we really need to see that in context of the raw message > as received by the user. It was posted. The issue is the message declares Content-Transfer-Encoding: base64 but the body is not base64 encoded so the MUA tries to base64 decode it and even though that's invalid, produces the garbled output. > The only other thing I can think of is it might have something to do > with your internationalization settings. What is the default language > of the list? (This is available in Postorius.) Have you changed the > default encoding for English on your site? (I think you need to look > in mailman.cfg for this.) What is the default language of the site? I note that the message also declares Content-Type: text/plain; charset="utf-8" and Python's email package will base64 encode utf-8 message bodies. I also note that the messages Subject: is RFC 2047 encoded as utf-8. These tell me that the user's preferred_language if set or the list's preferred_language is not English or the charset for English is changed to utf-8. I tried to duplicate this in a test installation with the charset for English set to utf-8, but I get a similar response but with Subject: =?utf-8?q?The_results_of_your_email_commands?= and Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: [Mailman-Users] Mailman 3 on Ubuntu 18.04

by Odhiambo Washington

On Sun, 9 Dec 2018 at 22:37, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/9/18 10:14 AM, Odhiambo Washington wrote: > > > > In my quest to run Mailman3, I obtained a VM running Ubuntu 18.04 and > > started on getting to run Mailman3. > > I found this link -> https://github.com/iomarmochtar/mailman3_ei > > It has instructions which looked fairly simple to get Mailman3 installed. > > However, I did encounter some hitches since the script is not meant for > > Ubuntu. > > > First, a more appropriate list for Mailman 3 is > mailman-users(a)mailman3.org > <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. > I am shifting to that list, after this. > > Also, we find it very difficult to address issues arising from third > party packages and how-tos. See <https://wiki.list.org/x/12812344>. > > And, there is a Mailman 3 package for Debian/Ubuntu > > apt install mailman3-full > In all my searching, I never found this in any documentation. I must have been searching in the wild, or my FreeBSD-mindedness got me stuck to containers and VENVs. > > With a few runs and observing the logs and modifying the script at every > > step it encountered and error, I finally managed to install Mailman3. It > > seems this is what you guys call a virtual environment in the Linux > world? > > :-) > > > I think the virtual environment in this case is a Python thing, not a > Linux thing. > I agree with you on that. > <snip> > > > Much of what I snipped is specific to > <https://github.com/iomarmochtar/mailman3_ei>, the details of which I'm > not interested in learning. > That is fine. I have put it aside for now. > > > >>From this point now is where I need help - serious help in smoothening > > things up and getting to understand these venv stuff! > > > > So I did run 'service mailman3 start' but this seems to be waiting for > too > > long to drop me back into the CLI. > > I also run 'systemctl start supervisord' and that seems to work. What I > am > > not sure is whether 'systemctl stop supervisord' actually does what it is > > expected to do because after I execute it, I still see processes running > > that I think are related. > > > > So far, I have been able to access the webUI on my VM using > > https://N.N.N.N:9090 > > I created a domain. > > But when I create a test list, I get an error - and I do not have a clue > > which logfile would have the error details - nginx or mailman... (I am > 100% > > new to nginx). > > > The nginx logs generally aren't too useful. Both Mailman core and Django > write logs. Core's log is probably in var/log/mailman.log where is > defined in mailman.cfg as var_dir. Django's log is defined in Django's > settings in the LOGGING setting. > Which file contains Django's settings? > > So now, I am stuck at: > > 1. Creating the mailing list > > 2. Getting to know whether the archiver is installed and running > > 3. Knowing is there are cron jobs to be running (Mailman2 type of > thinking!) > > > See > <http://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs > > > and > < > http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > > > Great to see that. I'll read and see if I make heads or tails of the writeup. > > Ultimately I need to figure out: > > 1. How the mailman queue runners are started and stopped > > mailman start > Why not systemctl mailman start?? Just wondering, as that is what I am seeing is common in Ubuntu. Does this make the components start after a reboot? > > 2. Migrate s few lists from Mailman2 to this Mailman3 > > mailman import21 > <django management> hyperkitty_import > Please show me where that is documented. I have to pull my lists from an old machine to this new one. > > 3. Mailman3 should use MySQL storage and Exim4 as the MTA (I have > > configured these bits in mailman.cfg) > > > You also need to configure MySQL in Django. See the DATABASES setting in > the Django settings. > So, when you talk about Django settings, you are referring to mailman.cfg file??? :-) I have spent all my weekend till now, trying to figure all this out. Life seems a little easier with mm2.x .... Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

6 years, 7 months

[MM3-users] mailman 2.1 or 3.0 (or another MLM)

by Stephen J. Turnbull

nate writes: > It's "just worked" over the years, no issues. I have been using > Linux since 1996, not a newbie here. If so, and you're familiar with Docker (obviously not the same thing, but maybe? ;-), you might find the containerized version provided by Abhilash (which is usually quite up to date) closer to a turnkey installation. I use the venv approach myself (more because developer than out of principle), so I'm not really familiar with the container distribution, but from traffic on the list I get the impression that most of the troubles have to do with networking in containers, rather than configuring Django and WSGI hosts. I appreciate the detailed description of what you did and didn't find in the docs. The docs are weak on administration, we admit, and we we get some of those round tuits .... > Or is there a better MLM for simple use cases? I used Majordomo > back in the 90s and was happy to get onto Mailman from > that. Something similar to Mailman 2.1 in features/functionality. It's been years since we had an answer to that question. Mark might have more to say, but the last time we were challenged on this, the rival was Sympa, and the conclusion I came to was that the use cases are different. Depending on your Linux distro, and your attitude to risk, Python 2 plus Mailman 2 in a container, VM, or even a dedicated host in the DMZ or outside the firewall might be a reasonable solution. Steve

3 years, 6 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/11/22 13:32, gordon(a)dickens.com wrote: > Hi Mark, > > I think that I found a hint as to the cause of my problems. > > I changed the apache2 LogLevel to debug and the following was then generated in /var/log/apache2/ssl_error_log: > > [Fri Feb 11 15:40:18.325675 2022] [core:debug] [pid 3982011] core.c(5280): (95)Operation not supported: [remote /var/lib/mailman3/web/static/uwsgi.sock:12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY) > > Apparently, there appears to be a problem with uwsgi.sock. > > My uwsgi.ini file has the following: > > uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock > > Also, my apache.conf for mailman3 has the followig: > > ProxyPass /mailman3 unix:/var/lib/mailman3/web/static/uwsgi.sock|uwsgi://localhost > > So do you see a problem in my configuration files that would cause the Operation Not Supported error with the uwsgi.sock file. I don't use uWSGI and have no experience with it at all, however here are some things to consider: For Apache to support uwsgi protocol you may need ``` a2enmod mod_proxy_uwsgi ``` However, I would suggest you use http rather than a unix socket. In your uwsgi.ini file instead of ``` uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock ``` which requires Apache support for uwsgi protocol, put ``` http-socket = 0.0.0.0:8000 ``` which will tell uwsgi to listen on TCP port 8000 and in Apache, use ``` ProxyPass /mailman3 http://127.0.0.1:8000 ``` -- 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: Message is received but is not sent out. Another, similar message, is processed fine.

by Allan Hansen

Thank you, Mark. I see this in mailman.log. I had looked there for her email address, but it does not appear, so I moved on to the smtp.log. In Jun 26 17:18:11 2023 (1243315) ACCEPT: ^M <CH3PR12MB82593801A1DF2E329E977046BE27A(a)CH3PR12MB8259.namprd12.prod.outlook.com> Jun 26 17:18:11 2023 (1243319) Uncaught runner exception: unknown encoding: iso-8859-8-i Jun 26 17:18:11 2023 (1243319) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/handlers/mime_delete.py", line 382, in process process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/handlers/mime_delete.py", line 151, in process reset_payload(msg, firstalt) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/handlers/mime_delete.py", line 202, in reset_payload msg.set_payload(subpart.get_payload(decode=True).decode( LookupError: unknown encoding: iso-8859-8-i Jun 26 17:18:11 2023 (1243319) SHUNTING: 1687825091.8457294+478565324778f2eb6f0fecaeccbd29596edaef53 I also see this in queue/shunt: mailman@list:~/var/queue/shunt$ ls -ltr total 88 -rw-rw---- 1 mailman mailman 7168 Feb 17 23:03 1676703781.903885+fdcba88c680f50a0799c672cd0abe82e4bfe19b3.pck -rw-rw---- 1 mailman mailman 19821 Apr 2 07:08 1680444501.0831451+e110b8c5c20ba3f87c1cea1c5f38e74a6cf8f1c5.pck -rw-rw---- 1 mailman mailman 19489 Jun 18 11:52 1687114364.41209+1684717da96ff76d1ce773a0cf39c5f8b63e9078.pck -rw-rw---- 1 mailman mailman 20274 Jun 18 19:01 1687140067.64057+7f77c1ebca490831f58ef9cfde06109081a4e7d6.pck -rw-rw---- 1 mailman mailman 20085 Jun 26 17:18 1687825091.8457294+478565324778f2eb6f0fecaeccbd29596edaef53.pck The three last entries coincide with the captured messages. Finally, in the captured message source (the last which was Cc'd to me) I do see this: Content-Type: text/plain; charset="iso-8859-8-i" Which matches the complaint in the mailman log. In the message that did get accepted, I see this: Content-Type: text/plain; charset="utf-8" Another difference: The posted message shows Content-Transfer-Encoding: base64 The shunted message shows Content-Transfer-Encoding: quoted-printable It appears that the two messages are, indeed, different, despite the similar looks when rendered. My question thus changes to: a. Should she be doing something special when sending to the lists? b. If not, is my setup in need of change? Yours, Allan On 6/26/23, 20:44, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 6/26/23 8:09 PM, Allan Hansen wrote: > Hi all, > > One of my subscribers is trying to send a message to a list, but it is not being posted. > The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not: > > mailman@list:~/logs$ grep herName smtp.log > Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName(a)hotmail.com <mailto:herName@hotmail.com>> SIZE=40109' > Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName(a)hotmail.com <mailto:herName@hotmail.com> > Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA(a)CH3PR12MB8259.namprd12.prod.outlook.com <mailto:CH3PR12MB82593510B90D8F05177C606BBE5EA@CH3PR12MB8259.namprd12.prod.outlook.com>> post to theList(a)domain.tlc <mailto:theList@domain.tlc> from herName(a)hotmail.com <mailto:herName@hotmail.com>, 40061 bytes > Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName(a)hotmail.com <mailto:herName@hotmail.com>> SIZE=18343' > Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName(a)hotmail.com <mailto:herName@hotmail.com> > Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName(a)hotmail.com <mailto:herName@hotmail.com>> SIZE=19123' > Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName(a)hotmail.com <mailto:herName@hotmail.com> > Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName(a)hotmail.com <mailto:herName@hotmail.com>> SIZE=18930' > Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName(a)hotmail.com <mailto:herName@hotmail.com> > > At the second retry she copied me and I saw nothing untowards in her message. > She's not getting any error return messages and her subscription is OK. > Both messages were multipart/alternative and both contained Hebrew text. > > I told her I'd look at this, but I'm at a loss. smtp.log is not very useful for diagnosing things like this. It only says a message was received, not why it didn't result in a post from the list as in the first case. What's in mailman.log with those timestamps? -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/F4K7HYUYSWEKF6LT35UCT3KBJX6GHY4I/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 1 month

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

Yes, I have django_mailman3/templatetags/d_gravatar.py in my installation. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:11 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org > <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- 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/

3 years, 9 months

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Tue, Dec 24, 2024 at 8:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> I saw that too. Reported > >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > > > > It isn't clear to me what I should do to mitigate the error. > > > Apply this patch: > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - dn = address.display_name or member.user.display_name > + # Non-members may have empty address.display_name and > member.user can > + # be None resulting in AttributeError on member.user.display_name. > + try: > + dn = address.display_name or member.user.display_name > + except AttributeError: > + dn = '' > if email_only or not dn: > print(address.original_email, file=outfp) > else: > ``` > Thank you. Now only if you can help me reconcile the fact that Postorius tells me that I have ``` List Nonmembers (872) ``` ..while the CLI command gives me only 13 addresses. -- 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]

7 months, 1 week

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

Got it. Is there a command that one can manually run to test/expedite the process? ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, July 28, 2025 12:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/28/25 7:07 AM, willie.castillo(a)caemilusa.com wrote: > Looks like "hyperkitty" stopped archiving right after the CERT for the mailman3 website expired, How can I make the missing archives visible on the website? I see there "*pck" files in the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The list archive does not show that last posting [of 25 July 2025. > > ~$ ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 98215 Jul 25 12:01 1753459289.7901242+f3fd7ee77272862f8c1023394bf88d0d4bbe9053.pck > -rw-rw---- 1 mailman mailman 98109 Jul 25 12:01 1753459289.7726512+ee1264c36a194eb0ec1a52089f053e6963f24369.pck > -rw-rw---- 1 mailman mailman 88479 Jul 25 12:01 1753459289.7564857+2e27f35a57f757f058dc95e34c56722a76307900.pck > > The CERT on the website is now up-to-date Those queued messages will be reprocessed on the next post. -- 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://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

5 days, 7 hours

[MM3-users] Re: From address of subscription notifications

by Abhilash Raj

On Wed, Feb 27, 2019, at 5:46 PM, worik wrote: > On 27/02/19 11:54 AM, Mark Sapiro wrote: > > On 2/26/19 2:11 PM, worik wrote: > >> When I subscribe some body to to a list I on I get a notification that > >> says it comes from changeme(a)example.com > >> > >> As far as I can tell no subscribers are getting mail with that, so this > >> is not a crises. But it is untidy and I cannot find where to change it. > >> > >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of > >> docker-compose.yaml (I am using the docker distribution...) > > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > > > > There is no `mailman/config/schema.cfg` on my system. Should I raise a > issue over at the docker-mailman github? > > I have: > > /opt/mailman/core/mailman-extra.cfg > /opt/mailman/core/var/etc/mailman.cfg > > Should I change it in the second one? /opt/mailman/core/mailman-extra.cfg Change it in this one. > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > 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, 5 months

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Andreas Schamanek

On Fri, 7 Apr 2023, at 12:43, Dave Hall via Mailman-users wrote: > On Fri, Apr 7, 2023 at 12:29 PM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: >> On Fri, Apr 7, 2023 at 7:14 PM Dave Hall via Mailman-users < >> mailman-users(a)mailman3.org> wrote: >> It's actually not that difficult to migrate from the Debian >> packages to the virtualenv setup. > It's not an option for me today. I feel you. I am running MM2 und 3 in parallel without problems, I do have a special MTA setup though (Sendmail). Can't speak for Postfix etc.. Ownerships for Mailman 3: # ls -l /etc/mailman3/ total 36 -rw-r--r-- 1 root root 399 2019-06-07 20:03 apache.conf -rw-r----- 1 root list 756 2022-02-24 23:17 mailman-hyperkitty.cfg -rw-r----- 1 list www-data 7672 2023-04-06 13:52 mailman-web.py -rw-r----- 1 root list 11489 2022-02-24 23:16 mailman.cfg -rw-r--r-- 1 root root 2893 2019-06-07 20:03 nginx.conf -rw-r--r-- 1 root root 1511 2019-06-07 20:03 uwsgi.ini /var/log/mailman3/ is list:list 755 /var/log/mailman3/web/ is www-data:www-data 755 /var/lib/mailman3/ is list:list 755 Contents in /var/lib/mailman3/ are list:list 755 except for /var/lib/mailman3/web/ which is all www-data:www-data 755 Make sure to always run any `mailman` as user list. `mailman-web` has the `su` to www-data built-in, it's just: su -s /bin/sh -c "python3 /usr/share/mailman3-web/manage.py $*" www-data So, use mailman-web whereever the docu says manage.py or django_admin --pythonpath /usr/share/mailman3-web -- -- Andreas :-)

2 years, 3 months

[MM3-users] Re: How to fix lists with characters errors?

by Mark Sapiro

On 3/23/24 11:56, Helio Loureiro wrote: > Hi, > it is python 3.10. Problem is... some mailing lists were created long ago, > with python2 something. Most probably 2.5. And the tables on mysql were > set to latin1. This has nothing to do with the data or the charsets/collation in the database. The issue is the locale setting in your python is causing stdout output from the `mailman members` command to be encoded as `latin1` and at least some user's display name contains a `\u0142` (i.e. `ł` character. > That I know. Question now is how to fix this. Any suggestion? What is > the table? I probably can run some script for these specific lists that > have the failure, import data as latim-1, and update back to the table as > utf-8. That's not the issue. The issue is the Python in your venv has sys.stdout.encoding set to latin1, probably for locale reasons. You ca apply this patch ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -17,6 +17,7 @@ """The 'members' subcommand.""" +import sys import click from mailman.core.i18n import _ @@ -30,6 +31,9 @@ from zope.component import getUtility from zope.interface import implementer +sys.stdout.reconfigure(encoding='utf-8') + + def display_members(ctx, mlist, role, regular, digest, nomail, outfp, email_only, count_only): # Which type of digest recipients should we display? ``` to mailman/commands/cli_members.py to fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: old usernames appearing in mailman.log

by Ken Alker

--On Monday, June 26, 2023 5:03 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 10:57 PM, Ken Alker wrote: >> >> I have studied the output, looked at the code lines referenced in the >> Traceback, and I can't figure out the problem (I feel like the sad guy >> on the side of the street with his hood up staring into the engine bay >> with stream pouring out and not knowing what to do next). I did some >> analyses on the log file and determined that there are 71 messages it is >> having problems processing and there are 71 messages "stuck" in >> /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to >> process each message about 20 times). > > > Each time there is a new post, it retries all the messages in the spool/ > directory. > > >> Since upgrading to V3.3.8 I've >> not seen new messages get stuck like this (although it's only been >> running smoothly for 24 hours now and there hasn't been much activity). >> But I'm suspecting there was something awry between the conversion from >> V2 to V3 in February and me installing V3.3.8 that caused this (based on >> message time stamps). It is HIGHLY likely these messages are in the >> archiving spool as a result of me unshunting the shunt queue and that >> they are copies of the messages that got delivered to the subscribers >> when I did that... but are now hung up in the archiving process. > > > Are new messages being archived OK. If so, that is a real mystery. It > says mailman-hyperkitty can talk to hyperkitty and archive new messages, > but it can't talk to hyperkitty when attempting to process a queued > message. Ahhh! I had convinced myself that new messages were being archived, but now that you ask, they ARE NOT. I may have said they were at some point, and I apologize if I did. Now I feel less confused. It appears that archiving stopped when I did the migration from "Debian package layout" to "source layout" and upgraded to V3.3.8. I'll bet I munged a config file or two. I was struggling with what to keep from Debian layout and what to bring over from the source install instructions and I haven't gone back through to clean them up. I had previously figured it could not be a configuration issue since some messages were making it into the archive and some were not, but now that I see NONE are making it, this makes the problem less daunting. >> Following is an excerpt from mailman.log. Note that the "first >> section" (from DOCTYPE at top to 404 at bottom) is repeated four times >> (maybe not identical; but similar) (so I did not include it to save >> room) before the Traceback appears. >> >> Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list >> found >> Jun 25 00:13:04 2023 (386086) ACCEPT: >> <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> >> Jun 25 00:13:04 2023 (386090) HyperKitty failure on >> https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > I just went to that URL and got a 404. This is a serious problem. > https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should > return some documentation of the API. > > https://lists.netlojix.com/archives/api/ does work and returns the > expected information. > > Your urls.py file probably contains in its urlpatterns list > ``` > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ``` > The simplest fix is to add > ``` > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > ``` > to that list. I see many ursl.py files all over the system, but none that appear to be where I'd expect them to be for processing by any executables. Is this a file I should have copied over and edited, or created from scratch and somehow missed? I don't see anything about it in the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html> (although I do see a post from last July from someone stating it got missed in the instructions back then). > Another way to fix this is in your mailman-hyperkitty.cfg, you have > ``` > base_url: https://lists.netlojix.com/hyperkitty > ``` > Change that to > ``` > base_url: https://lists.netlojix.com/archives > ``` Done, and restarted both services, but I'm not seeing a difference when I go to <https://lists.netlojix.com/hyperkitty/api/> (I was getting a "Page not found", and still get that). > but it wouldn't hurt to add the `^postorius/` and `^hyperkitty/` patterns > to urls.py anyway.

2 years, 1 month

[MM3-users] Re: problem configuring mailman3 on debian bullseye

by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia

Hi, Thank you. I discovered tha I removed all templates but in the db table the template was not removed. It was pointing to localhost and this was the problem. Thanks to all for help! Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it Il 16/03/23 04:20, Mark Sapiro ha scritto: > On 3/15/23 09:55, Odhiambo Washington wrote: >> On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione >> territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: >> >>> Hi, >>> >>> I created a template but after some tests I deleted it. >>> >>> Now I created only a standard list without modifying any templates. >>> >>> So they are the standard templates coming with the distribution. I >>> did not >>> change also the language >>> >> Maybe you can start by deleting any templates in postorius_emailtemplate >> table in the DB? > > There shouldn't be any, but if the issue is with accessing postorius > templates, that might make it worse. > > If you want only the system default templates, you could do this > database query to remove any non-defaults: > > DELETE FROM templates; > > That will ensure that you aren't accessing Postorius for any templates. >

2 years, 4 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 9., Sze, 4:49): > ``` > $ 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. > > >>> um = getUtility(IUserManager) > >>> usr = um.get_user('user(a)example.com') # any of the three addresses > >>> usr.addresses > prints a list of the 3 addresses. These are indexed as 0, 1, 2 > >>> usr.preferred_address > prints the preferred address. If this is the one you want to delete, do > >>> usr.preferred_address = usr.addresses[n] # n is the index of one > you want > >>> del usr.addresses[n] # n is the index of the address you don't want > >>> usr.addresses.remove(n) # n is the index of the address you don't > want > >>> commit() > ``` Thanks, I successfully removed my unwanted address, so it now doesn't appear anywhere. (Looks like .remove(n) wasn't needed, it only gave an exception, and the settings were saved even without commit() – which is concerning because I would have assumed that I can cancel transactions by omitting it.) However, the problem still persists: I can't post to the list from HyperKitty. In this regard, nothing has changed since my original report. I'm subscribed to the list with my primary, preferred address, which is the GMail address right now.

3 months, 3 weeks

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

by Mark Sapiro

On 3/22/23 03:42, thomas--- via Mailman-users wrote: > Hello, > very new to mailman3, I used to manage mailman2 on a Debian 10 server. > The server has been upgraded to Debian 11 and mailman2 disappear… > > I try fresh install of mailman3, prerequisite to data migration, but without success. > If some can help, I would be really greatful. > > <VirtualHost *:80> > ServerName newsletter.mydomain.tld > > Alias /static /var/lib/mailman3/web/static > Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > > DocumentRoot /var/lib/mailman3/web/static > <Directory "/var/lib/mailman3/web/static"> > Require all granted You can probably fix the below error by adding options +Indexes here, but see below. > And now I have a 404 answer when consulting my http page. > > When trying to access `/static` sub-path, I get `Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found`. It is unclear to me what is doing a GET of /static/admin/ and why. GETs should by of actual files, e.g., things like /static/admin/css/base.css > I am a bit lost with that. So are we. Questions about the Debian package are better asked of Debian. See https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… We can provide much better help and support if you install via the resources mentioned in the reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Rejecting held emails

by Mark Sapiro

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

7 years, 3 months

[MM3-users] New vulnerability in Hyperkitty master branch

by Abhilash Raj

Hey Everyone, A new vulnerability was reported against Hyperkitty’s git master branch branch which can expose the archives of a private Mailing List through the new Feeds API that was added to Hyperkitty recently to someone who isn't a member or logged-in. Thanks to Ngo Wei Lin for reporting this vulnerability. This bug does not affect any stable released version of Hyperkitty and only affects installations from source (1.3.5b1 version). To differentiate from the vulnerable version, I have bumped the version in master branch to 1.3.5b2, so if you have 1.3.5b1 installed, you should upgrade! The fix for this bug has been committed to master branch[1][2] less than an hour ago as of this writing. If you are using git branches to install Hyperkitty, you can upgrade using the following command: $ pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master I have also triggered a build for Mailman container images[3] with this changes, so if you are using the rolling container images (which are the only affected ones), then you should upgrade to the latest one when the build[1] finishes (approximately in next 30mins). Do note that this version of rolling release of mailman-web image also includes the fix for the vulnerability announced against Postoruis earlier today. You can verify that you have the fixed version of Hyperkitty in the image by running: $ docker run -it --entrypoint bash maxking/mailman-web:rolling bash-5.0# pip list | grep HyperKitty HyperKitty 1.3.5b2 Ensure that you get 1.3.5b2 version. [1]: https://gitlab.com/mailman/hyperkitty/-/merge_requests/362 [2]: https://gitlab.com/mailman/hyperkitty/-/commit/ed086015acbf66ba377e2af7f6e7… [3]: https://github.com/maxking/docker-mailman/runs/3519658592 -- thanks, Abhilash Raj (maxking)

3 years, 10 months

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 2/24/22 18:21, chucka(a)blackforest-co.com wrote: > I have this working: > > #!/bin/bash > H="http://lists.mysite.org/admin.cgi/newsletter-mysite.org/members" > case $1 in > 'add') curl "$H/add?subscribees=$2&adminpw=verysecret" ;; > 'del') curl "$H/del?subscribees=$2&adminpw=verysecret" ;; > esac > > and scan the return for "Successfully [Un]subscribed" Since the above is MM 2.1 I'm assuming you are asking how to do the above in MM 3 via REST. Here are some examples: To add a single user curl -urestadmin:restpass \ --request POST \ -H 'Content-Type: application/json' \ --data-binary '{"list_id": "list.example.com", "subscriber": "user(a)example.net", "display_name": "Joe User", "pre_verified": true, "pre_confirmed": true, "pre_approved": true}' \ http://localhost:8001/3.1/members Response is empty or a JSON object describing the error. To delete a single user: curl -urestadmin:restpass \ --request DELETE \ http://localhost:8001/3.1/lists/list.example.com/member/user@example.net Response as above To delete a list of users: curl -urestadmin:restpass \ --request DELETE \ -H 'Content-Type: application/json' \ --data-binary '{"emails": ["user(a)example.net","other(a)example.org"]}' \ http://localhost:8001/3.1/lists/list.example.com/roster/member Response is a JSON object similar to {"user(a)example.net": true, "other(a)example.org": false, "http_etag": "\"...\""} where success or failure is indicated by a true or false value for each address or a JSON object describing the error if any. -- 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: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Wed, Feb 1, 2023 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/31/23 23:33, Odhiambo Washington wrote: > > Is this a race condition? > > > > <CUT> > > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > > Traceback (most recent call last): > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django_extensions/management/commands/runjobs.py", > > line 40, in runjobs > > job().execute() > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/jobs/update_and_clean_index.py", > > line 37, in execute > > run_with_lock(update_index, remove=True) > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", > > line 181, in run_with_lock > > log.exception("Failed to update the fulltext index: %s", e) > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > > line 470, in __exit__ > > self.unlock() > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > > line 420, in unlock > > raise NotLockedError('Already unlocked') > > flufl.lock._lockfile.NotLockedError: Already unlocked > > <CUT> > > > Yes, it is a race between the monthly hyperkitty update_and_clean_index > job and the hourly hyperkitty update_index job > Okay. This is a bit off from my understanding. What is the cause and how do I mitigate it? -- 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: Sudden increase in "***UNCHECKED***" in email subjects

by Dave Clements

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

5 years

[MM3-users] Re: Hyperkitty performance problem

by monochromec

Thanks for your input and happy new year to you! The logs set debug level prove to be inconclusive: the runner is handing the message over to the archive runner which in turn forwards to the message to HyperKitty. HyperKitty, not checking if a message with the same ML name and msgid is already present in the DB forwards this to Postgres for storage. The following questions remain to further the RCA: - How to obtain additional logging information beyond the settings outlined below [1]? - Why does the archive runner forward a message to HyperKitty if it's already done this in the past (or is this another try if the message hasn't been archived successfully - how do I check this from the archive runner's perspective if the archiver only logs the entry "HyperKitty archived message <msgid> to the HyperKitty REST URL"? - Any additional insights you might be able to share (additional logging configuration, etc.) is greatly appreciated! [1] mailman.cfg excerpt: [runner.pipeline] instances: 4 [runner.out] instances: 1 [logging.smtp] #level: debug [loggging.database] #level: debug [logging.runner] #level: debug [logging.pipeline] level: debug qualname: pipeline propagate: 0 [logging.lmtp] level: debug path: lmtp.log # [logging.archiver] level: debug [logging.mischief] #level: debug [logging.plugins] #level: debug mailman-web.py excerpt: LOGGING = { 'version': 1, 'loggers': { 'hyperkitty': { 'level': 'DEBUG', 'propagate': True } } } The GitLab issue you mentioned I raised due to my incorrect configuration of the # of runner instances was due to the assumption that I suspected a single pipeline runner might not be sufficient with the load and hence my attempt at increasing this.

7 months

[MM3-users] Re: MM3.1 templates

by Abhilash Raj

Hi Matt, On Tue, Jul 18, 2017, at 07:25 AM, Matt Richards wrote: > I've managed, to setup MM3.1 using the docker images from > http://github.com/maxking/docker-mailman. I would like to start > customizing > the templates MM3.1 uses for the footer and confirmation emails. Is there > any mailman site admin or list admin documentation on how to customize > email templates in MM3.1? Not yet, we are still working on perfecting the Installation Guide and other configuration related documentation for Mailman 3. For now, you might have to use command line to do these changes. Templates should exist inside the `$var/templates/<language_code>/` where $var is the var directory for Mailman Core. If you are using the container images, it should be at `/opt/mailman/core/var/`. The templates are named as the naming scheme mentioned in the documentation[1] and ending with a `.txt`. If you place those files there, it should be able to override the default templates that exist in the mailman. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht… > I've found this template doc at > https://gitlab.com/mailman/mailman/tree/master/src/mailman/rest/docs, but > I'm not clear how this works.. and it appears postorius doesn't have > template support yet? I am new to python and django.. That is correct, you can set the URI in the Postorius interface, but there is no way to actually write the templates in Postorius right now. > -- > --Matt > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Hope that helps! -- thanks, Abhilash Raj

8 years

[MM3-users] Re: mailman.log file owned by 'list' user

by Odhiambo Washington

On Sun, Jan 8, 2023 at 1:29 AM Mike Wertheim <mike.wertheim(a)gmail.com> wrote: > I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 > that was done by someone else. > > Mailman is running as a non-privileged (non-root) user called 'xyz'. On the > day that Mailman was installed, that non-privileged 'xyz' user was able to > execute mailman commands successfully to create, view and modify lists. > > A couple of days later, when the 'xyz' user tried running those same > mailman commands, they failed with this error: PermissionError: [Errno 13] > Permission denied: '/var/log/mailman3/mailman.log' > > Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: > -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log > > When I did a 'ps' command, I saw that all of the mailman processes are > running as user 'xyz'. No processes were running as the user 'list'. > > It seems that some process is rotating the mailman.log file at midnight, > and the newly-created mailman.log is being owned by user 'list'. > > Can anyone explain why this is happening, and how to fix it? > The easiest way to NOT FACE such problems is to run Mailman3 in a virtualenv. You will have peace after you migrate to a virtualenv. -- 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: 404 on fresh install (Debian11)

by Jeremy Stanley

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

2 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

my mailman.cfg file is: # AUTOMATICALLY GENERATED BY MAILMAN ON 2017-07-16 20:44:24 UTC # # This is your GNU Mailman 3 configuration file. You can edit this file to # configure Mailman to your needs, and Mailman will never overwrite it. # Additional configuration information is available here: # # http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html # # For example, uncomment the following lines to run Mailman in developer mode. # # [devmode] # enabled: yes # recipient: your.address(a)your.domain #[mailman] #layout: fhs [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix my mailman.config.postfix file is: [postfix] transport_file_type: regex are they ok? El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 12:52 PM, Rafael Mora wrote: > > I made a change for test purpose on the mailman.cfg file and I got this: > > > > > > (env) [mailman@localhost etc]$ mailman restart > > Restarting the Mailman runners > > PID unreadable in: /var/lib/mailman/var/etc/var/master.pid > > [Errno 2] No such file or directory: > > '/var/lib/mailman/var/etc/var/master.pid' > > Is the master even running? > > > > How do I solve this? > > > Try > > mailman stop > mailman start > > -- > 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

8 years

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

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

4 years, 9 months

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

by Bryan Fields

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

1 year

[MM3-users] Re: disabling social login

by Abhilash Raj

On Mon, Nov 6, 2017, at 10:26 AM, Simon Hanna wrote: > On 11/06/2017 07:22 PM, Dmitry Makovey wrote: > > Hi, I'm trying to disable social login and running into troubles > > stepping on it's remnants all over the place. What's the proper sequence > > for disabling social login in MM3 install? > comment out 'allauth.socialaccount' and all social providers in the > INSTALLED_APPS in your settings.py This apparently doesn't work, Hyperkitty apparently depends on this to do some stuff. I haven't dug up in there, but the migrations would break if we remove this from INSTALLED_APPS. Instead, please let the 'allauth.socialaccount' be there, along with 'allauth.account' and 'allauth' and everything else related to allauth should be removed. It looks something like this: ```` 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', ) ``` I tested this works, see [1]. [1]: https://lists.araj.me/postorius/lists/ > They shouldn't be enabled by default in the first place I guess, since > pretty much all of them require further setup in order to work > properly... > > How are you running MM3? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 8 months

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

by Roland Giesler

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?

1 year

[MM3-users] Re: Disable Sign-up per domain

by Mark

On 2025-08-01 19:40, Mark Sapiro wrote: > Please confirm that the issue only occurs with the modified > /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py > and does not occur with the original .../user_adapter.py. > Hi Mark, In working through this I reverted the test server (which had the working "Disable") back to original, then re-applied the changes, and now I'm getting the same errors as on the Production server. I think it might be me screwing up somewhere. It's doing my head in today so I'll sleep on it and have another crack at it tomorrow. STEPS TAKEN =========== 1. Reset the "Test" server back to original. (a) I put the original "user_adapter.py" back in place. It contains: ... def is_open_for_signup(self, req): return False ... (b) Ensured that "settings.py" had the following completely removed: ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ... (c) systemctl restart mailman3 systemctl restart mailmanweb (d) Reloaded browser with "lists" page for each domain and clicked "SignUp" on each. Result: As expected, both domains correctly displayed their SignUp pages. ----------- 2. Made the following changes to the "Test" server. (a) Edited /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py It now contains: ... # def is_open_for_signup(self, req): # return False def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.MYDOMAIN.COM': return False else: return True ... (b) Appended to - /etc/mailman3/settings.py - the following: ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' (c) systemctl restart mailman3 systemctl restart mailmanweb Result: 502 Bad Gateway page and log shows ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. ===========

23 hours, 13 minutes

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

by kelly.close＠lrewater.com

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. 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. There is a manual step with this install (mailman3-full on Ubuntu 18.04) that involves added 4 lines to the end of your postfix config file (/etc/postfix/main.cf). Those 4 lines are tricky because 2 of them are long and wrap in my documentation. I had a typo probably introduced by copy and paste, whereby 2 of the lines were on the same line and yes, those are the lines that specify where the hash tables go. So - lesson learned, follow your own instructions :-) I'm pretty sure that had i set those lines up properly the hash files would have been set up properly when mailman first tried to initialize. Maybe I'll try this again one day and see... ~Kelly

5 years, 1 month

[MM3-users] Mailman recovery test did not go as planned

by bob B

I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. I need to perform a DR recovery test. I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). While Mailman was stopped, I had our database team take a backup dump of the database. I then restarted Mailman in docker. I threw some more messages at a test list. I validated that the new messages were delivered, and showed up in the archive. I shut down Mailman again. I had the database team restore the Mailman database from the backup. I started Mailman I logged into Mailman I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. When went into the list archive, I get a spinning icon and no messages showed up. I quit, restarted my browser, and logged in again, and the same thing. I then sent a test message to the list and the message was delivered to the list. Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Is this normal? After a restore did the new message cause a refresh of archived messages etc? Is there a way to do this without sending a message to a list after a restoration of the database? Are there better steps I should take when restoring the database? Thanks

2 years, 11 months

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

by Abhijith PA

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 ? --a

6 years, 6 months

[MM3-users] Re: Username being set to givenname for socialaccount login

by Abhilash Raj

On 9/22/21 11:22 AM, cfarley(a)iastate.edu wrote: > I have a new mailman3 install setup with Okta as a social application. This is working well for logins and data comes through as expected, but for some reason the username is being set at to a lowercase version of the given_name. The Extra data on the social users in the admin interface looks good, so I don’t think it’s a problem with the attributes coming from Okta. > > We have tried a number of variations on the below setting, but that all of them other than the default of “username” end up with the username being empty. > ACCOUNT_USER_MODEL_USERNAME_FIELD = “email” This setting actually specifies which field in your custom user model should be treated as username. From what I am seeing, you don't have a custom user model, so I don't think you want to override this field. AFAIK, the username is picked by the Okta provider in django-allauth and it is a part of that integration betweek Okta and Django. If you look at the implementation of that integration, it doesn't set the username[1], which (only some I am guessing) other providers do, Github for example[2]. You can open an issue on django-allauth's Github page[3] to ask them to update the Okta provider such that it also sets the username correctly like other providers. [1]: https://github.com/pennersr/django-allauth/blob/master/allauth/socialaccoun… [2]: https://github.com/pennersr/django-allauth/blob/master/allauth/socialaccoun… [3]: https://github.com/pennersr/django-allauth/issues -- thanks, Abhilash Raj (maxking)

3 years, 10 months

[MM3-users] Missing Base64 encoding from control message reply

by Stephen J. Turnbull

lists-mailman3(a)janaberger.de writes: > I have a setup with GNU Mailman 3.3.8 where a user tried to > subscribe. When replying to the "confirm" message, the user > received a completely garbled response, like so: > > N?z?????zf???&???j?????u?[zZ0:???v???,j?z???k?e?0 > 4D???r?^b??r?????*'???y????{ax?L?X????0:???v???,j?z???k?d?m?-???zz?rn??l]y+???-E?( > ?^N??'??M???t???Mz?????^i?????}?o?\????6sN?zf??????r??z?????????b?{h?????f?r?ne== To diagnose, we really need to see that in context of the raw message as received by the user. > The user then forwarded the .eml file to me, which clearly shows > the contents of the mail as plain text while being announced as > base64 (Content-Transfer-Encoding: base64): It also clearly doesn't show anything like the mojibake above. What is the relation between the two? While the problems could be related to Mailman, it could also be any MTA along the way or the user's mail client. I suspect that the .eml file has been significantly altered by intervening software. As far as I know, the Python email package does not MIME-encode plain ASCII text as you see in the email's subject. The only other thing I can think of is it might have something to do with your internationalization settings. What is the default language of the list? (This is available in Postorius.) Have you changed the default encoding for English on your site? (I think you need to look in mailman.cfg for this.) What is the default language of the site? Steve

1 year, 10 months

[MM3-users] Re: Display the last post time for a list or all lists.

by bryant＠sandiego.edu

> since #453 was fixed, mlist.last_post_at is None and time.ctime(None) is > the current date and time. > That too could easily be fixed like: > > import time > def last_post(mlist): > if mlist.last_post_at: > print('{}: Last post at {}'.format( > mlist.display_name, > time.ctime(mlist.last_post_at) > )) > else: > print('{}: No posts'.format(mlist.display_name)) > The trickier part is the Mailman 3 mailman withlist command has no > option to run for all lists, so you'd need to run it something like > #!/bin/sh > for list in mailman lists -q; do > mailman withlist -r last_post -l $list > done Thanks for the leg up on converting that from mailman2 to mailman3 much appreciated. I found 1 issue. When I had a list that was imported, but had not done another post after being imported, the script would fail with the following error: print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: 'datetime.datetime' object cannot be interpreted as an integer Made a final change to set the mlist.last_post_at to mlist.last_post_at.timestamp() and that cleared the problem. The final form of last_post.py is: ------------------------- import time def last_post(mlist): if mlist.last_post_at: print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at.timestamp()) )) else: print('{}: No posts'.format(mlist.display_name)) ------------------------------- Don't know if this will help others, but the place I put the last_post.py file was in: /opt/mailman/venv/bin (same location as the mailman script executable). Bryan

11 months, 3 weeks

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 15/2/21 16:57, Mark Sapiro wrote: > Finally, although I said previously that the translated templates should > be submitted as a merge request, that can still be done, but is not > necessary. They can be translated in weblate. See > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > and<https://gitlab.com/mailman/mailman/-/issues/825>. I had the templates translated now in UTF-8 coding map. I copied all of them en a new directory (es) under mailman package templates (as I can see are other languages): /usr/local/lib/python3.7/site-packages/mailman # ls templates __init__.py de es it __pycache__ en fr sk /usr/local/lib/python3.7/site-packages/mailman # ls templates/es domain:admin:notice:new-list.txt list:member:regular:header.txt help.txt list:user:action:invite.txt list:admin:action:post.txt list:user:action:subscribe.txt list:admin:action:subscribe.txt list:user:action:unsubscribe.txt list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt list:admin:notice:disable.txt list:user:notice:hold.txt list:admin:notice:removal.txt list:user:notice:no-more-today.txt list:admin:notice:subscribe.txt list:user:notice:post.txt list:admin:notice:unrecognized.txt list:user:notice:probe.txt list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt list:member:digest:header.txt list:user:notice:rejected.txt list:member:digest:masthead.txt list:user:notice:warning.txt list:member:generic:footer.txt list:user:notice:welcome.txt But mailman isn't aware of them (I restarted the server). May I have to execute some process as "compilemessages" to mailman be capable to use them? Now mailman is using the "en" templates for sure. After testing them I'll do both of the suggestionsyou made: a merge request AND the revision and translation via Weblate.

4 years, 5 months

[MM3-users] Re: External Mail-Server?

by Florian Schulze

Hi! But LMTP is the "Local" Mail Transfer Protocol. I only have access to IMAP, POP3 and SMTP. Outgoing seems to be simple, but what about incoming? Regards, Florian Schulze On 11 Sep 2021, at 21:21, Jörg Michael Schulz via Mailman-users wrote: > Hi, > > yes, this should be possible. > > See the parameters in your mailman.cfg: > > [mta] > # The class defining the interface to the incoming mail transport > agent. > incoming: mailman.mta.exim4.LMTP > #incoming: mailman.mta.postfix.LMTP > > # The callable implementing delivery to the outgoing mail transport > agent. > # This must accept three arguments, the mailing list, the message, and > the > # message metadata dictionary. > outgoing: mailman.mta.deliver.deliver > > smtp_host: mail.yourfavoritedomain.de > smtp_port: 25 > smtp_user: > smtp_pass: > > Am 11.09.21 um 19:53 schrieb Florian Schulze: >> Hi! >> >> Is it possible to use an external Mail-Server? Does mailman3 support >> that directly, or would I have to setup a local MTA which somehow >> fetches incoming mails from the external inbox and uses the external >> Mail-Server for delivery? >> >> Does anyone do that and have example configurations? >> >> Regards, >> Florian Schulze >> _______________________________________________ >> 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/

3 years, 10 months

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/24/21 12:57 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/22/21 2:16 AM, Henrik Rasmussen wrote: > > > > After sending a mail to the list as the moderated list user, the > > > resulting notification returned to the users email address is > > > mostly in German, but the reason indicated is in Spanish "El > > > mensaje proviene de un miembro moderado". > > > > > > I am unable to duplicate this in Mailman 3.3.5rc1. > > Is it possible that one of the message catalogs is incomplete, and > something in the environment (LANGUAGE seems like a likely candidate) > is set to a value that uses German when Spanish is unavailable or > vice-versa? Thanks for the hint Steve. There is a Spanish message catalog as evidenced by the fact that the reason was translated to Spanish, but the issue is almost certainly that there is no mailman/templates/es/list:user:notice:post.txt template so we fall back to the one for the list's language. Note that prior to Mailman 3.3.5rc1 there are lots of missing templates and in particular, the 3.3.4 Spanish templates were incorrectly named with `_` rather than `:` in the names. Templates are actually translated in the message catalogs via weblate, but these translations weren't installed in the appropriate templates/ directory. There is now a script at https://gitlab.com/mailman/mailman/-/blob/master/update_lang_templates.py to do this. -- 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] Mailman3 on virtual domains (was: Re: Re: Alias for a list name)

by Lars Bjørndal

[Mark] > On 10/6/23 09:49, Lars Bjørndal wrote: > > > > To run mm 3 through Postfix, I use local_recipient_maps and > > transport_maps. > > > > What I want to achieve, is alias medlem(a)list.saf-org.no to > > saf-medlem(a)list.saf-org.no > > > > I tried to put > > > > medlem(a)list.saf-org.no: saf-medlem(a)list.saf-org.no > > > > and get the following error when running newaliases: > > > > postalias: warning: /etc/aliases, line 231: name must be local > > > > Is it possible to do this aliasing in a simple way? > > > If list.saf-org.no is a local domain, i.e. in mydestination, the alias would > be > > medlem: saf-medlem(a)list.saf-org.no > > or more simply > > medlem: saf-medlem > > If list.saf-org.no is not a local domain it needs to be a Postfix virtual > (alias or mailbox) domain and you need a virtual_alias_maps with an entry > like > > medlem(a)list.saf-org.no saf-medlem(a)list.saf-org.no Thank you. One of my other domains is a virtual domain. According to https://wiki.list.org/DEV/LMTP%20process I tried to add hash:/opt/mailman3/mm//var/data/postfix_lmtp to virtual_alias_maps in Postfix's main.cf. When sending to testliste(a)rokaden.no, I get back an Undelivered Mail Returned to Sender message with <"lmtp:[127.0.0.1]:8024"@dalen.lamasti.net> (expanded from <testliste(a)rokaden.no>): unknown user: "lmtp:[127.0.0.1]:8024" What's my problem here? Thanks, Lars

1 year, 9 months

[MM3-users] ARC

by Stephen J. Turnbull

David Krantz writes: > Is the documentation correct that ARC should be as simple to configure > in mailman 3 as to add the private DKIM key and restarting mailman? > (https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign…) You need to enable ARC by adding the ARC section to mailman.cfg and setting "enabled = yes" in it. I've submitted a pull request to update the documents. > I've tried that without finding any effect in my so far limited tests. What do you mean by "effect"? Is the "effect" that you're not seeing the presence of ARC header fields in outgoing mail? If so, you probably haven't set the enabled flag. If the effect you're looking for is that Google and several other participants in the ARC protocol accept your mail when they didn't before, you'll have to ask them about it. > I have not found anything in logs although I might have missed looking > in one. I don't recall that anything is logged by the module under normal circumstances, there may be some error logging. What would you expect to be logged? > Are there any known limitations? Of what kind? It's a simple protocol: if there is authentication information (DKIM or ARC) in the incoming message, validate it. Then package up the validation in the ARC-AR, ARC-Signature, and ARC-Seal fields. Those are the operations the module performs. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

5 years, 11 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 11/6/19 9:18 AM, josh(a)caluette.com wrote: > I just setup a new Mailman 3 server using maxking/docker-mailman from GitHub. I got everything working just right including changing the footer template for messages. However, when trying to set anything in a Welcome template, I am encountering these same errors. > > I have confirmed that the mailman-core container is able to download the template via curl using the http://mailman-web:8000/ api URL and gets the correct text, but anytime I try to mass subscribe, it fails with the errors that Brian had provided and I get an HTTP 500 error. > > If I remove the Welcome template, then I can do mass subscribe just fine. > > Here are the logs: > > Nov 06 17:10:13 2019 (29) deque: > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 384, in _make_request > six.raise_from(e, None) > File "<string>", line 2, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 380, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1331, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 297, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 258, in _read_status > line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") > File "/usr/lib/python3.6/socket.py", line 586, in readinto > return self._sock.recv_into(b) > socket.timeout: timed out Have you set POSTORIUS_TEMPLATE_BASE_URL appropriately in your settings_local.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/27/21 3:48 PM, Ruth Ivimey-Cook wrote: > > It is also possible to Alter existing databases and tables, but with one > catch: the maximum table row length is reduced, so some tables will need > to be adjusted (e.g. converting varchar(255) to varchar(230)). This is misleading. The maximum row length depends on the actual data stored in the row. The sum of the various column size limits for VARCHAR and other columns can well exceed the maximum row size as long as the sum of the lengths of the actual data stored in the row does not. The significant issue is all these limits are bytes, not characters, so in the worst case, a VARCHAR(255) column can only store 85 3-byte utf8 encoded unicodes or 63 4-byte utf8mb4 encoded unicodes, but this too is misleading an most strings contain single byte encodings with some 2 or 3 byte encodings and maybe at most one or two 4-byte encodings. Furthermore, the problem issues are essentially limited to emojis and possibly other 4-byte encoded symbols in email subject headers and bodies. Bodies are a TEXT field and the data are stored separately and do not affect the row size and subjects are defined with a maximum length of 512 bytes which should be sufficient. None of the data stored in rows is at all likely to exceed the maximum row length, even with a lot of 4-byte encodings. -- 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: Database deadlock when trying to delete a member.

by Simon Coggins

> On 18 Mar 2021, at 5:05 pm, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hi Simon, > > > On Mar 17, 2021, at 10:16 PM, Simon Coggins <s.coggins(a)cqu.edu.au> wrote: > > > > Hi, > > > > I’ve got a strange error. I migrated from mailman 2.1 to 3 using the migration guide on the website and things have been working fine. But I’m in the process of testing the new syncmembers command to replace some inhouse mailman API code we wrote. I’ve tracked my problem down to what appears to be a deadlock in the postgresql database. When trying to delete certain users the SQL query hangs and never returns. > > > > After doing some tracing and tracking it down to the database, I enabled DB logging of all queries and saw that the following query was never returning: > > > > DELETE FROM member WHERE member.id = 166814 > > > > If I try to run it manually I get the same issue, in psql it never returns. > > mailman=# explain analyze DELETE FROM member WHERE member.id = 166814; > > [… 60 seconds passes…] > > ^CCancel request sent > > ERROR: canceling statement due to user request > > CONTEXT: while deleting tuple (2998,72) in relation "member" > > I’m just wondering if there are any commands or scripts I can run to verify the database and it’s constraints to see if there is some error in the database data? Or where you’d recommend I go from here? It only impacts the user on this specific list. If I add this user to another list and remove them, everything works fine. > > Are you able to retrieve that Member object using API? > > This[1] the Python code which would try to delete a Member object and I > am assuming is being called from syncmembers command. I am not entire > sure about what would cause the database to hang, if there was some database > constraint that failed, I would imagine some error to be returned. > > [1]: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… > Ok I think I’m getting closer. It appears to be an open transaction that is locking the database record. While mailman is running, if I try to execute "DELETE FROM member WHERE member.id = 166507;” on the mailman table in psql the query hangs and never returned. But if I shutdown mailman and try to run the query again, it executed immediately. So I’m pretty sure there is an open transaction that is causing the entry to be locked. > One thing you can try is see if you can unsubscribe the user using the API or > `mailman shell` command. > > You can unsubscribe from API by calling a `DELETE` method at > > http://localhost:9001/3.1/members/<member_id> > > This would give us some indication about whether there is some bug > in the implementation of syncmembers command or if there is something > else going on. > Trying via shell or via API to delete the user all fail and hang. I’m able to receive the user/membership/list data without any issue both via mailman command and via the API. > > > > This is on a test system so I can do various testing. I’m trying to find the root cause so that I can verify my production system isn’t impacted by the same thing. > > > > > > Setup Details: > > OS: Oracle Linux 7 (Redhat) > > Installed using pip via virtualenv talking to a local pgsql database on the same box. > > Data was migrated from a mailman 2.1 install into mailman3 using migration instructions on the website. > > > > PIP Modules versions: > > django-mailman3 1.3.5 > > mailman 3.3.3 > > mailman-hyperkitty 1.1.0 > > mailmanclient 3.3.2 > > postorius 1.3.4 > > psycopg2-binary 2.8.5 > > What is the version of sqlalchemy package? There is a new 1.4.0 version that came out recently > and is incompatible with Core right now. There are backwards incompatible changes which might > need some changes in Core to add support. > SQLAlchemy 1.3.19 > > > > RPM packages: > > postgresql12-12.6-1PGDG.rhel7.x86_64 > > postgresql12-server-12.6-1PGDG.rhel7.x86_64 > > postgresql12-libs-12.6-1PGDG.rhel7.x86_64 > > postgresql12-devel-12.6-1PGDG.rhel7.x86_64 > > > > > > -Simon > > > > > > _______________________________________________ > > 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/ --- Simon Coggins, Principal Systems Engineer Digital Services Directorate CQUniversity, Lvl 6.14, 160 Ann Street Brisbane, QLD, 4000 Email: s.coggins(a)cqu.edu.au Web: http://www.cqu.edu.au/

4 years, 4 months

[MM3-users] Re: auto-away notices as bounces

by Mark Sapiro

On 8/29/21 10:19 PM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > >> That said, bounce processing should treat even a VERPed message as >> unrecognized if it doesn't look like some kind of DSN. This may not >> be the case in MM 3. > > Thanks, that's what I also think. Looking at the returned mail, they > definitly don't look like DSNs / bounces to me. > > > Anything I should be doing re this topic? I've created https://gitlab.com/mailman/mailman/-/issues/939 for this. I think this patch will fix it. --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -51,13 +51,18 @@ class BounceRunner(Runner): addresses = StandardVERP().get_verp(mlist, msg) if len(addresses) > 0: # Scan the message to see if it contained permanent or temporary - # failures. We'll ignore temporary failures, but even if there - # are no permanent failures, we'll assume VERP bounces are - # permanent. + # failures. We'll ignore temporary failures, and if there + # are no permanent failures, we'll assume this is a vacation + # response or similar. temporary, permanent = all_failures(msg) if len(temporary) > 0: # This was a temporary failure, so just ignore it. return False + if len(permanent) == 0: + log.info('VERPed bounce message but not a recognized DSN: %s', + msg.get('message-id', 'n/a')) + maybe_forward(mlist, msg) + return False else: # See if this was a probe message. addresses = ProbeVERP().get_verp(mlist, msg) (Watch for wrapped lines) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Allan Hansen

Thank you both. Since the first message she sent was UTF-8 and the second iso-8859-8-I, I have asked her what she did diffently between the two messages. No response yet... But now being aware that this can happen when non-ASCII messages are sent, and how to find the issue when it does, is good. Yours, Allan On 6/27/23, 07:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 6/27/23 12:30 AM, Stephen J. Turnbull wrote: > > That said, if the users are unable or unwilling to use UTF-8, it would > be possible to create a codec for "iso-8859-8-i", I don't know how to > do that, and I doubt Mark does. You could ask on > python-list(a)python.org <mailto:python-list@python.org>, or file an RFE on Python's GitHub tracker. See https://github.com/python/cpython/issues/90079 <https://github.com/python/cpython/issues/90079> filed by me in Nov 2021. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/4WPWU3SKGWM2BTG5AK3LWNG7FDIBVSTP/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 1 month

[MM3-users] Re: Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails

by Mark Sapiro

On 10/12/24 1:44 AM, francesd919--- via Mailman-users wrote: > Hi everyone, > > I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. > These emails mentioned that the subscription was disabled due to bounce score. > Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > I have some questions: > > 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? > 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. > 3. What could have cuased functioning emails to bounce and therefore being disabled? The answer to all those is you upgraded from a Mailman core version prior to 3.3.1. Prior to that, bounces were recorded in the database but not processed. when you upgraded, they all got processed at once. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… which includes a `mailman shell` interaction to re-enable all the subscriptions disabled by bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: Mailman 3 bounce handling and DKIM mitigation

by Mark Sapiro

On 09/05/2017 01:14 PM, David Krantz wrote: > > I have a question on bounce handling. I get the impression that > bounces are just lost and neither handled nor forwarded to the list > admin. Is this a known problem? I am running mailman from git, but > about version 3.1 and use postfix. Bounce processing in Mailman 3 is currently not done. See <https://gitlab.com/mailman/mailman/issues/343>. > I find lots of things in the > bounceevents table. Is there any way to find out more on these events? > I probably can configure postfix to send listname-bounce@domain to an > admin adress. Or for that matter hack mailman to send it to the > correct admin. Your ideas are possible. Until it's fixed, you could just make postfix forward the listname-bounces address to listname-owner. I think this will then get the LMTP runner to send them to the owner. > Also the DKIM mitigation does not seem to detect DKIM domains. If I > force the mitigation for all mails it works but that of course has > annoying consequences although mostly cosmetic. This has caused quite > a number of bounces for my lists (as well as being temporarily banned > by at least Microsoft). I assume you mean DMARC mitigation. It should work for From: domains that publish DMARC policy 'reject' or 'quarantine' without setting DMARC Mitigate unconditionally. What if anything do you see in mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: How to promote non-members to members?

by Mark Sapiro

On 3/17/22 10:19, Quanah Gibson-Mount wrote: > > So then I ran your code to confirm it, and it blows up with an error: ``` >>>> for token, data in pendings.find(pend_type='subscription'): > ... if data['token_owner'] != 'subscriber': > ... continue > ... if data['email'] != 'xxxxxxxx(a)xxxxx.org': > ... continue > ... sub_mgr.confirm(token) > ... > Traceback (most recent call last): > File "<console>", line 6, in <module> > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 545, in confirm > workflow.restore() > File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line > 149, in restore > setattr(self, attr, data[attr]) > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", > line 119, in address_key > assert self.address is not None > AssertionError ``` This says that there is no Address object with the email xxxxxxxx(a)xxxxx.org What do you get in `mailman shell` for ``` >>> um = getUtility(IUserManager) >>> um.get_address('xxxxxxxx(a)xxxxx.org') >>> um.get_user('xxxxxxxx(a)xxxxx.org') ``` These should return an Address and a User respectively. If they don't, did you perhaps run some process to delete the user? If the user is gone, you should be able to replace ``` ... sub_mgr.confirm(token) ``` in the above with ``` ... wfm = getUtility(IWorkflowStateManager) ... pendings.confirm(token, expunge=True) ... wfm.discard(token) ``` to clear the pending subscription and workflow and then be able to mass subscribe the 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] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 10:02 AM, brian(a)emwd.com wrote: > I followed Kelly's guide and ran into some issues but were able to resolve most of them. It seems I have one out standing issue: Hyperkitty. When I post to a list, I am getting the following in the /var/log/mailman3/mailman.log: > > Apr 11 14:01:15 2019 (1334) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF/$ > <html><head> > <title>503 Service Unavailable</title> > </head><body> > <h1>Service Unavailable</h1> > <p>The server is temporarily unable to service your > request due to maintenance downtime or capacity > problems. Please try again later.</p> > <hr> > <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> > </body></html> > (503) ... > 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. 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'. Set base_url in mailman-hyperkitty.cfg to use an acceptable host name instead of localhost or adjust your apache config to accept localhost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

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

by Jeremy Stanley

On 2022-12-14 17:26:59 -0800 (-0800), Mark Sapiro wrote: > 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. [...] While this does appear to solve the problem on my test deployments, a challenge that I'm left with is how to automate it. Our community takes an "infrastructure as code" approach to all the services we run for our projects, and we make sure that we can automatically bootstrap every system from scratch into a working state. Unfortunately, I'm not having any luck finding an API or CLI which I can use to create sites and domains rather than manually doing it in the Django admin WebUI. Does such a thing exist, or an I going to need to resort to directly performing database inserts (which I'd rather avoid since it could break if the schema changes). It appears there's a foreign key relationship involved, which could make DB manipulation like this even more fragile. -- Jeremy Stanley

2 years, 6 months

[MM3-users] Re: Mass Subscribe caused Delivery Status to become "unset"

by Odhiambo Washington

On Sat, Sep 7, 2024 at 9:45 PM chad.hays86--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > One of the admins on our Mailman site said they recently performed a mass > subscribe operation on list, however they noticed that for each user they > subscribed, their "Delivery status" was unset, so they weren't receiving > email updates whenever there was new activity on the list. They had to go > in after the fact and manually set it to "Enabled" for each user that was > subscribed via the mass subscription operation. Is this behavior expected? > During the mass subscribed, pre-confirm, pre-approved, and pre-verified > checkboxes were all checked. > I do subscribe members using the same method your admin used, and I also check the option to send a welcome message as it defines things that the new user ought to know. I have just checked on the profile of one user I added 3 or so days ago and found that NO option is set on their web profile - just like your admin found out. I then checked my MTA logs for list posts (the list is active today) and found that ML posts are also being sent to their address. So what your admin is reporting is rather strange - to me. -- 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, 3 weeks

[MM3-users] Re: hidden list is hidden even to the owner

by Abhilash Raj

On Wed, Jul 1, 2020, at 1:31 PM, Mohsen Masoudfar wrote: > Hi, > > I am not sure, if it is designed this way, or I am doing something wrong. > > I created a list in MM3 as a hidden list, meaning: > Show list on index page: NO > and assigned the owner. When I login as Postorius web admin, I see the > list on the list page which is listed as: (unadvertised*). This is fine. > But when the owner or moderator login to Postorius they don't see the > list at all. Of course if they add the list name at the end of the URL, > they get to the list and as the owner can manage it too. > My question is: I am just not sure, if I am missing something or this > is how it is supposed to work? Which version of Postorius are you running? Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. > You could expect, that the owner or the moderator should see the list > as (unadvertised*) too. > > Best regards > Mohsen Masoudfar > Lead System Analyst, IT Operation > American Association for the Advancement of Science > 1200 New York Ave, NW, Washington, DC 20005 > 202-326-7087 > > > _______________________________________________ > 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] Personalization issue when no To header?

by Alan So

We have ported a number of lists from mailman 2 to mailman 3 earlier. We cannot find any personalization setting in the mailman 3 web UI or using the mailman client. It is fine as it is not essential. However, recently we notice an issue. As the lists in the mailman 2 probably have personalization turned on, it looks like that the setting are also migrated by using "mailman import21". Recently, some users start sending mail simply with Bcc without any addresses in the To header. We notice the following error: Oct 08 11:26:03 2019 (1832) Uncaught runner exception: 'to' Oct 08 11:26:03 2019 (1832) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 163, in deliver callback(mlist, message_copy, msgdata_copy) File "/usr/local/lib/python3.6/site-packages/mailman/mta/personalized.py", line 58, in personalize_to msg.replace_header('To', formataddr((name, recipient))) File "/usr/lib64/python3.6/email/message.py", line 558, in replace_header raise KeyError(_name) KeyError: 'to' After tracing the source codes above, we suspect that the issue was caused by no To header due to personalization is turned on. Any quick suggestion of workarounds such as how to turn off personalization for all lists? We do not have much experiences with mailman shell. Thanks a lot.

5 years, 9 months

[MM3-users] Re: Finding a user to delete them

by Quanah Gibson-Mount

--On Saturday, March 14, 2020 7:03 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. Thanks Steve, Generally I just found the mailman shell examples in the documentation lacking, as: * it used functions not available without loading additional modules not listed in the documentation * the steps to find accounts is lacking, since they don't work for email addresses that are not yet verified * I could find no documentation on what fields are available in the user object, so I was unable to find the account via other methods, including the actual username created by mailman3 (which seems odd, wouldn't this be a standard way to find users..?) The Django UI is the only thing that let me find the miscreated user and delete it. Hopefully the bug I filed about github user integration being badly broken will receive some priority, given the bug causes new accounts to incorrectly be created for existing users. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 4 months

[MM3-users] Programmatic Creation of Users

by jciesla＠techsupportme.com

I am returning to Mailman after being away for a LONG time and I need to create 40 lists with ~350 subscribers spread across those lists. After a lot of testing I am now able to create users from the Core Shell and set (most of) the necessary values. Having jumped that hurdle I have hit a roadblock and I am hoping that the list can provide some insight and/or solutions. After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? Any information is greatly appreciated! -John

3 years

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

Thanks all! I will use these pronto. On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > > > >> Mistakes were made, and for while every single outbound email bounced. > >> I've fixed the mistakes, but now in my largest and most active email > list, > >> every single user's delivery status is "Disabled by Bounces". > >> > >> Is there a way to bulk fix this? Or do I have to go into each user, > one at > >> a time, and fix them? > > > > Please see this thread: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > The script in that post does all lists. For a single list see > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > but note that the command line > ``` > $ shell -l list(a)example.com > ``` > should be > ``` > $ mailman shell -l list(a)example.com > ``` > > -- > 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 swd(a)pobox.com >

8 months, 3 weeks

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

by Barry Warsaw

On Jun 18, 2016, at 12:10 PM, Mark Sapiro wrote: >because I want to run all the Mailman pieces from >the heads of their branches rather than what's in PyPI, but even without >that, installation is significantly more work than installing a distro's >package. My hope is that the upcoming 3.1 release will be much more solid and usable than 3.0 so that you won't have to run from the git heads. I think of it very much like Python 3.0 and 3.1 - the 3.0 release was really a stake in the ground and a major milestone so that people will start using it in anger and helping us understand the priorities for fixing and improving it. In that we've succeeded I believe (witness in addition to Mark's work on python.org, that the Fedora mailing lists have all been converted to use MM3). There are a number of interesting options for improving the turnkey installation of MM3. There are Debian folks who are waiting for 3.1 to complete the packaging work there, and there are docker/juju/etc. containerization work happening too. >I will say that once you have Mailman 3 installed and running, updating >(which I do frequently, but which doesn't need to be done unless you >want specific updates/fixes) is pretty easy. Yes, we're trying to be very serious about upgrades and backward compatibility, so that even if you bravely install 3.0 today, it should always be easy to upgrade to the next point release. Similarly, I try to keep core's git head always working so you could track that if you want. Cheers, -Barry

9 years, 1 month

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

by Mark Sapiro

On 7/5/22 12:32 PM, Kimmo L wrote: > Hello! > My plan is to install fresh Mailman3 host, which means that i need to migrate/transfer my existing mailman mailing lists + hyperkitty archives to new host. > Unfortunately i didnt find any good documentation about this. > I tried myself to export and import mailmanweb/mailman databases (from old PostgreSQL to new PostgreSQL) and recreate indexes(mailman-web update_index). Now i can see and search hyperkitty archives, but if try to open one of the mailing list, i get error - HTTP Error 500: {"title": "500 Internal Server Error"} > So im pretty sure, that I'm gonna have to transport some more stuff over, which I have no idea. Maybe existing users and user rights. Dumping the databases from the old serverr and loading them on the new server should work. There should be an exception and traceback logged in Mailman core's mailman.log or possibly in the Django (mailmanweb) log. What is logged? > If its not a big trouble, can someone kindly share, what exactly should i need to export/import and what would be the right steps/commands/moves. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Abhilash Raj

On Fri, Jan 4, 2019, at 7:02 AM, Thomas Stein wrote: > On 04.01.19 15:55, Abhijith PA via Mailman-users wrote: > > > > > > On Friday 04 January 2019 08:19 PM, Thomas Stein wrote: > >> On 04.01.19 09:40, Thomas Stein wrote: > >>> > >>> 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. > >> > >> While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should > >> I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation > >> what variables i can put in those templates? > > > > If you are using 3.2.0, you can do that from webapp itself. [ I haven't > > tried though] > > Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik. > > https://launchpad.net/ubuntu/+source/mailman3 This link mentions that 3.2.0-1ubuntu1 is the current stable version. > > thanks and 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/ > > > _______________________________________________ > 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, 6 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Jered Floyd

This was entirely my fault. *facepalm* I replace styles/base.py when I do my container builds, so that I can override list defaults (personalization, subscription_policy, and dmarc_mitigate_action). I failed to notice the added dmarc_attributes attribute added to apply() --Jered ----- On Nov 25, 2023, at 7:49 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 11/25/23 16:25, Jered Floyd wrote: >> Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home >> from another episode of turkey overconsumption. >> >> I confess that I am not a python expert - once I create a new list, what’s the >> easiest way to inspect the object state? > > ``` > $ mailman shell -l list(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 list(a)example.com mailing list > >>> print(m.dmarc_addresses) > [] > >>> > ``` > > -- > 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 jered(a)convivian.com

1 year, 8 months

[MM3-users] Re: How to delete non-users

by Stephen J. Turnbull

Mark Sapiro writes: > My original point is the presence of a nonmember role should not prevent > the user from subscribing. If there is an issue with subscribing it is > probably because of the outstanding subscription request waiting > moderator approval. I don't think it is likely, but is it possible that the moderator is not just refusing the subscription, but banning the address from subscribing? > I understand that you would like the nonmember role to disappear, but > that isn't going to happen in the distribution, and I can't undertake > the extensive effort required to figure out how you can do it for your site. It seems to me that explicitly displaying the nonmember role is an internal and/or administrative need, and most ordinary users are only interested in whether they are subscribed or not. If the list appears in "their" list of list, they're going to assume they're subscribed. (We've even had that confusion about moderators and owners in the past.) I haven't done any deep thinking about this, but perhaps we could provide a more streamlined view tuned to this specific need? That is, the role won't go away, but at least in some contexts you'll have to ask explicitly for that user-list relationship to be displayed. Also, IIRC Allan's community contains a substantial group of folks with visual impairments, presumably including admins and moderators. Especially to serve that circumstance I think it makes sense for us to provide streamlined views that are more easily grasped as a whole where we can.

2 years, 10 months

[MM3-users] Re: Hyperkitty Replies showing up as new posts

by Mark Sapiro

On 3/5/25 8:55 PM, Arte Chambers via Mailman-users wrote: > Hello, my Hyperkitty is creating a new post for each reply in a thread. I > would expect that new posts to a list would show up in the archive and once > you click on that thread you would see all replies. However in my > Hyperkitty each reply to a thread shows up as its own post usually with the > subject line saying RE: Original Message. How can I set up Hyperkitty to > behave more like the lists.mailman3.org archives where replies to topics > are filed under their respective threads? HyperKitty's threading is based solely on In-Reply-To: headers. It does not attempt to thread based on References: or Subject: matching. Usually this works, but it can fail if for example A posts to a list. B replies off list to A and A replies on list to B's off list reply. In this case, the In-Reply-To: of A's reply is the Message-ID: of B's reply which isn't on the archive, so A's reply starts a new thread, but this is unusual, and HyperKitty has a "Reattach this thread" feature that a list owner or superuser can use to attach one thread to another. However, if this non-threading occurs regularly, It may be that the replyer's MUA is not setting In-Reply-To:. I've seen some phone clients do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: installation

by Henry S

Thanks Mark and Brian. I'll try the suggestions. My IP might have got blocked by CBL when testing mailman3 against a Gmail address. I have since removed it from CBL. I don't know how my IP got into the Outlook's block list. Maybe a used one. Will try DKIM signing and Microsoft programs. On 23/11/2020 11:59 am, Brian Carpenter wrote: > > On 11/22/20 6:54 PM, Henry S wrote: >> >> Now I am trying to figure out how to configure mailman+postfix to >> pass the unnecessarily convoluted world of spam-free certification >> and ip blockings by those 'security lawmakers'. >> >> Any suggestions on how to not be blocked by gmail, hotmail, etc? I >> have used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an >> appropriate question to this mailman list. > > Mark Sapiro provided some very good suggestions. > > Is this a new IP address or one that has been used for mail traffic > for a white? The only way Gmail and Hotmail will block an IP address > is if you have some major outgoing spamming problems or in the case of > a new IP address, the IP address has a sordid history which will be > reveal if you do a RBL check on it. > > Gmail likes SPF records and MTA's that utilizes SSL for outbound mail. > > For Hotmail deliveries, you will want to signed up for Microsoft's > Smart Network Data Service (SNDS) program which I find very good. Also > sign up for their JMRP program for your IP address. > >

4 years, 8 months

[MM3-users] Re: EMWD Mailing Lists Down

by Allan Hansen

All, I recently entered a ticket for some work and received this response: ***** Allan, Thank you for your business with EMWD however we are experiencing a severe shortage in labor(just like any other small business at the moment) and we cannot currently support your request. We hope to be at full staff in a few months but as you know this is a niche product and it is difficult to find or train mm3 experts. Thank you for your understanding. Sincerely, Marshall ***** I sincerely hope that they manage to get the company up and running again. I had great help from Brian and enjoyed working with him. Yours, Allan On 1/15/22, 18:18 , "Sherry Xie" <sherrytxie(a)gmail.com> wrote: Hi all, I am an EMWD Mailman 3 customer, and I recently realized my mailing lists are no longer working (the last email that went through was sent on December 25, 2021). Emails I send to the lists do not show up in archives or reach subscribers. It seems like others have had this issue before since ownership of the company was transferred following Brian Carpenter's passing – has anyone been able to get in touch with support or get their issues resolved? I've submitted a support ticket but have no idea if this is being monitored. I also have no way to contact the current management team, as only their names were announced in the November 5, 2021 email from Barbara Carpenter. Any help would be greatly appreciated – thanks in advance! Sherry _______________________________________________ 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, 6 months

[MM3-users] Re: starting gunicorn per mailman.log yet gunicorn not installed

by Mark Sapiro

On 6/26/23 1:15 AM, Odhiambo Washington wrote: > On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Yes, it makes sense. Mailman 3 core is basically an application which >> manages a webserver that provides the REST API, a database of domains, >> users, and lists, an LMTP server for incoming posts and an SMTP client >> for outgoing distribution. Mailman uses gunicorn to provide the >> webserver. >> >> Installation of gunicorn is handled as a package dependency, so you >> probably wouldn't notice unless you were watching the installation >> process very carefully. >> > > It doesn't make sense, IMHO, because as the OP says, > 1. his ExecStart is: > ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and > not* > ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf > mailman_web.wsgi:application. > > 2. He has not knowingly created any gunicorn.conf > > Why would Gunicorn be Exec-ing itself? :-) As Steve says, Mailman core uses Gunicorn to manage it's REST API. This has nothing to do with whatever WSGI server (uWSGI, Gunicorn, Apache mod_wsgi, ...) is used to support the Django applications (django-mailman3, hyperkitty and postorius). I.e., there is always a Gunicorn instance configured and started by Mailman core, regardless of whatever WSGI server supports Django or even if one isn't running Django at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

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

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

1 year, 3 months

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

by tlhackque

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

7 years, 11 months

[MM3-users] Re: Putting mailman3 server behind a netscaler

by Jered Floyd

Hi Tom, I'm not familiar with Netscaler, but I run my Mailman 3 behind a reverse proxy (Apache Traffic Server, which somehow I ended up as a package maintainer for also). I assume that Netscaler can operate in a transparent reverse proxy mode (e.g. including Host headers to the origin server), which is what I would recommend for best results. I also did a migration from Mailman 2 about a year ago, and may have notes on managing that migration. But the first step for you is to have a fully functional Mailman 3 install. Since this supports multiple domains *far* better than 2 did, a good place to start may be to do an install under an entirely separate test domain until you are comfortable with the software, and then add your primary domain and migrate lists. This has the least opportunity for disruption. If you have many, many lists, I recommend having your inbound MX be able to select transport between the old and new servers on a per-list basis so you can migrate one at a time. (This is easily done with Postfix and I'm sure other MTAs as well.) The web interface will have to point at one or the other through the process, unfortunately, but at least the SMTP interfaces will continue to operate as normal. Some starting questions I have are what OS you are running, and by what mechanism have you installed Mailman 3? I found the documentation to be generally very helpful, and ended up containerizing things to make tweaking things repeatable. I admit that the whole process took a good 2-3 days to complete. Regards, --Jered ----- On Nov 28, 2023, at 6:27 PM, Lieuallen, Thomas Otis Tom.Lieuallen(a)oregonstate.edu wrote: > I’m obviously new to MM3, so overwhelmed by all the various pieces. > > In rereading some documentation and playing with the admin interface, I see that > one can specify a web host. I made that change, but it didn’t seem to make any > difference. > > I’m very tempted to scrap my installation and start over again. > > I had also removed the example.com site, which I thought I saw in passing one > shouldn’t do. > > If I start over, I should be able to have hostname, email domain, and web site > all be distinct? > > Thank you > > Tom Lieuallen > > From: Lieuallen, Thomas Otis <Tom.Lieuallen(a)oregonstate.edu> > Date: Tuesday, November 28, 2023 at 13:14 > To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> > Subject: [MM3-users] Putting mailman3 server behind a netscaler > (I sent this a week ago, but apparently it got lost, trying to resend.) > > We’ve been using MM2 for eons and are working on a migration to MM3. So, bear > with me as I’m still coming up to speed. I’m running MM 3.3.8 and Postorious > 1.3.8. > > Our mailing lists include members within our organization as well as a number > outside. We don’t want to expose our MM3 server directly to the open internet, > so wish to hide the web portion behind our netscaler and our regular pool of > web servers. Those web servers will proxy MM3 web pages on over to our MM3 > machine to handle. This seems to work. Email will meander in via MX and mail > relay servers. > > I found and followed directions in this email regarding changing URL paths: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > > So, say our MM3 server is: mm3.fqdn > I am trying to publish and use urls like > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…><http://www.fqdn/mailman3-admin>, > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…><http://www.fqdn/mailman3/lists>. > Again, that works for me. > > However, MM3 still has its concept of what URLs should be. I hoped I could fix > that by way of templates, but I’m not sure there’s a template for everything. > I added some templates, but have not replaced all. I was wondering and > hoping that some central change could fix any default templates en-mass. > > Most recently, I changed the mailman admin email yesterday and the confirmation > email directed me to mm3.fqdn/…/confirm-email/…. I looked at the stock > templates and nothing there had that wording. > > I just looked at postorious docs and nothing jumps out at me there. > > > 1. Have I gone down a bad rabbit hole? > 2. Is there a way to change the advertised web server address? > 3. Should I just continue rolling out my own templates and hope and assume that > will take care of this issue? > > 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 lieualth(a)oregonstate.edu > _______________________________________________ > 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, 8 months

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

by Mark Sapiro

On 11/4/21 12:58 PM, Simon Coggins wrote: > > Please file an issue for this at > https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a > better solution. Your approach of munging Message-IDs will create other > issues. Consider a post to a list with direct CC to userx. userx > replies-all to the message received directly. the In-Reply-To of this > reply is the unmunged Message-ID which will affect threading in the > archives and other recipient's MUAs. I realize this is preferable to > losing the message, but I hope we can do better. > > > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Stephen J. Turnbull

Mihai Moldovan writes: > But, all this said, mailman-web is typically already a wrapper > calling su -s /bin/bash -c "python3 .../path/to/manage.py $*" www-data, so why should it be > wrapped in another wrapper with a different user? The list user is typically > used by the mailman-wrapper wrapper. This isn't "typical" nowadays, except for .deb installations as far as I know. IIRC modern .rpm distros use our Python scripts for the 'mailman' and 'mailmanweb' commands, and we recommend using the same user for mailman and mailman-web services (we call it 'mailman' but of course 'list' will do if you already have one), because there's normally no reason www-data should need filesystem access to Mailman data and vice-versa. For best support, you'll find that assuming we are only vaguely aware of what your startup scripts and utility tools look like is helpful. When we ask you to run a simple test, it's probably a good idea to run it even if you're pretty sure what the outcome is. Then you can say, "the outcome was X, which is what I expected because Y". You lose a minute or two, and we learn something about your system (X and Y). Otherwise you lose hours or days of calendar time if you say "no point, because Y" and we reply, "please run it anyway" and something you didn't expect happens. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 2 weeks

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi Mark, thanks for correcting my assumption. Based on your information I have been able to identify the suspect message file in /var/lib/mailman3/messages, replace the suspect file with another file, update the file permissions and successfully load the held messages page. This allowed me to discard the suspect message and other held messages are then available for review again. In case the steps below help someone else who is having this issue here are the steps I followed with my initial search string redacted: Searched all files in messages folder for matching string: cd /var/lib/mailman3/messages grep -ir [REDACTED] * Finds string in one file: Binary file HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV matches Check whether file can be parsed using mailman command: mailman qfile ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Throws a matching error: [----- start pickle -----] <----- start object 1 -----> 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 97, in main args.func(args) File "/usr/lib/python3/dist-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/lib/python3.6/pprint.py", line 161, in _format rep = self._repr(object, context, level) File "/usr/lib/python3.6/pprint.py", line 393, in _repr self._depth, level) File "/usr/lib/python3.6/pprint.py", line 405, in format return _safe_repr(object, context, maxlevels, level) File "/usr/lib/python3.6/pprint.py", line 555, in _safe_repr rep = repr(object) File "/usr/lib/python3/dist-packages/mailman/email/message.py", line 45, in __repr__ return self.__str__() File "/usr/lib/python3.6/email/message.py", line 135, in __str__ return self.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 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) 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 characters in position 8-9: ordinal not in range(128) Move suspicious file out of messages: mv ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV /root/20200914/ held_messages page still throws 500 error. Checking debug log, it is now because the database references a file that is no longer there. Can I just copy a parseable file to the path of the bad file so I can delete it or do I need to remove the reference from the database? Copy some other file: cp ZZ/B2/ZZB24ADTZ2BOKBWTQWI7KG4XACGR6DTJ HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Still throws an error but this time it's a permissions error. mailman can't access the copied file: ls -l HE/D7/ -rw-r----- 1 root root 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chown list:list HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chmod g+w HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV ls -l HE/D7/ -rw-rw---- 1 list list 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV held_messages now loads OK. Cheers, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, 12 September 2020 06:17 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 10 months

[MM3-users] Re: Hyperkitty import from mailman2

by Marvin Gülker

Just a suggestion -- if your list didn't have any e-mails in the last month, the front page will show it as inactive. Dig into the archive links on the left side to actually see your e-mails. I've been bitten by that behavior as well. The front page simply doesn't show e-mails older than a month. Look here: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… No emails on the front page. Now go here: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… Well there. Greetings Marvin Am 23. December 2017 um 01:05 Uhr +0200 schrieb Sten Aus <sten.aus(a)eenet.ee>: > Hi > > Thank you Mark and Simon for your input! > > I can see imported list from Hyperkitty GUI, but it's inactive. > I can confirm that I can see those emails from command line (python shell > shows Email Objects). > > Import shows everything is OK: > > # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v > 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > Only emails after 2010-01-01 00:00:00+02:00 will be imported > Importing from mbox file /tmp/test.mbox to test(a)list.domain.com > /--some 22 emails being imported here --/ > 22 emails read > 22 email added to the database > 22 emails are stored into the database > 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. > > # python2 manage.py update_index --settings settings > Indexing 50 emails > NB! Only 6 of them are archived from new list (which has been created from > Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to > different lists). > > > I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the > same django application. > Also tested with running server directly and then connecting to a port 8000, > but I guess it does not matter, because both of them are using Python > script. > > I have not yet managed to set up cron tasks, as this is relatively new > installation, but I have ran them manually. Also, I have done update_index > (runjob update_index and manage.py update_index, both ways). > > > SQLite database shows emails, for example there's a thread > FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django > error: No Thread matches the given query. > > > As Postorius and Hyperkitty are in the same Django, they share sqlite > database (mailman/web/database.db). Mailman has it's own database in > mailman/var/data/mailman.db. > > > Happy holidays > Sten > > > On 22/12/2017 21:09, Simon Hanna wrote: > > On 12/22/2017 03:39 PM, Sten Aus wrote: > > > Hi > > > > > > I have installed mailman3 - it looks very great! > > > > > > Now I wanted to try import from mailman2 mbox, so i did: > > > > > > python2 manage.py hyperkitty_import --settings settings > > > --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com > > > /tmp/test.mbox > > > > > > It shows that it have sucessfully imported all emails and I can see > > > them from database (sqlite3), but I cannot see them from GUI > > > (hyperkitty). Only thing I can see is this inactive "test" list. > > > > > How did you try to access them using Hyperkitty? Can you try doing that > > while logged in as a django superuser? Could you try using a permalink > > for a message? If you can access the files from the database you should > > be able to construct the urls using the list name and the > > message_id_hash of a message. You should try this using DEBUG=True in > > the settings.py. The URL would be similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… > > > > > > Another option would be to check if you can access the data using a > > python shell. > > > > `python manage.py shell` to open a python shell preconfigured for > > Hyperkitty and then input the following two lines: > > > > from hyperkitty.models.email import Email > > Email.objects.all() > > > > > > This should print out all the messages that are stored in the database. > > (You can limit them by appending "[10:]", or any other python slice) > > > > What do you see in the UI? Is it somewhat similar to > > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 7 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

> Fra: Mark Sapiro [mailto:mark@msapiro.net] > Sendt: 2. oktober 2017 17:26 > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > There is no user or list admin workaround, but the defense is a fairly > simple patch. See the MR at > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > at > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > The commit changes 7 files, but only two are needed. The rests are tests > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't >necessary. > > The only changes you need are those to mailman/email/message.py and > mailman/mta/connection.py. I am using Docker-mailman (not yet very familiar Docker and version control). I would expect I have to wait for a Docker-mailman release including this change, right? I have at least five+ lists which almost haven't been working since my switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am desperate trying to figure out whether it is best to fall back to the Mailman 2 server, for the time being, where the lists came from, or it is better to wait for an update to the Docker-image. Will https://github.com/maxking/docker-mailman/milestone/2 fix my problems regarding failed mail handling and will it become available soon (when?) (https://github.com/maxking/docker-mailman/issues/147)? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

7 years, 9 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

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', ) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface

by Mark Sapiro

On 9/30/23 10:53, Wikinaut wrote: > I use mailman3 since a while, for some of my lists I have been using > > - list:member:digest:footer.txt > - list:member:regular:footer.txt > > When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! Postorius templates are handled differently from file system templates. When you set a template in Postorius, that template becomes available in Postorius' API and an entry for the template in the template table in the database is created with a URI pointing to the template in Postorius' API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for info about template URIs. The fact that Postorius doesn't show the file system template as the initial value when creating a template in Postorius is https://gitlab.com/mailman/postorius/-/issues/366 > When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. They are not created as files - see above. The fact that they aren't working is probably because your Django setting for POSTORIUS_TEMPLATE_BASE_URL is not correct. This should be set to the scheme and host part of the URL you use to access Postorius, e.g., https://lists.mailman3.org for this list's installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: django fake users

by roberto

Hello, yes we talk about django users who are not subscribing to any list only to the django user managment. Automatically removing this users like described above with a cron job is a good idea, but i would more like to avoid this users. Obvious this users are created by a bot, would it not be helpfully to use any kind of captcha? Am 17.01.21 um 12:24 schrieb Andrew Hodgson: > Stephen J. Turnbull wrote: > >> r.woithe(a)callassoftware.com writes: >>> is there a opportunity to avoid django fake users? >>> Because of it is not stopping, further and further fake users are > subscribing. >> Require moderator approval for subscribing. > I don't think this would help the issue. What I am seeing here is users signing up through Postorius using the sign up option which then creates an account in Django (but not Mailman). Yesterday alone I had over 700 of these accounts created. I don't know whether they pass email confirmation or not (I don't see this in Django admin), however they don't get added as users in Mailman and they don't attempt to subscribe to any list. > >> It may be possible to do something automatic, but you need to explain how you know these users are "fake", and it has to be something that can easily be detected with a few lines of Python. If it becomes at all complex, it will almost surely make trouble for "real" subscribers. > I agree, this is why I am taking the route of running a regular Cron job to delete the users as explained earlier. > > Andrew.

4 years, 6 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Andreas Barth

* Lars Schimmer (l.schimmer(a)cgv.tugraz.at) [210301 09:10]: > On 27/02/2021 04:02, Stephen J. Turnbull wrote: > >Lars Schimmer writes: > > > > > Hm, it completely ignores the standard way for Debian: > > > apt-get install mailman3-full > > > also exim4 as standard mailer. > > > And apache2. > > > >Right. The idea is that Debian is a *component* of *Brian's* system, > >not that Brian is installing a Debian system. One problem is that a > >lot of people like to run Debian Stable, which lags our releases by > >many months, sometimes a couple of years. A lot of people run a > >Debian Stable system plus a couple of mission-critical apps from > >source or from upstream repositories. > > Maybe the debian packages are old because people do not care about > and use always upstream because debian packages are old? Eh, sorry, but stable means: only essential (i.e. security) bugfixes get into that version. This is not a problem, it's a feature. If someone wants the latest greatest version of all packages, run testing or unstable. And if you need it for just one package, install the required package by hand. This works usually quite well. The testing/unstable branch contains version 3.3.3 as of writing this which is the currently released version, see https://packages.qa.debian.org/m/mailman3/news/20210205T001903Z.html (and which was uploaded about a day after release - not a bad timing). I would be quite careful speculating that someone may be not careing about something. Andi

4 years, 5 months

[MM3-users] Re: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by summersan＠nclack.k12.or.us

Hi Mark, Thank you for your quick response! When setting up Mailman 3, I went through much of this "how to" guide here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. As far as I can tell, my current setup appears to be proxying from Nginx to Gunicorn, according to the related Nginx and mailman3-project-specific Gunicorn config files. Specifically, I checked the local address:port being used in the Nginx file and compared that to the mailman3-project-specific Gunicorn bind address. It looks like I might have "separated out" the REST API to a different server block in the Nginx config file, so I think I'm looking at the correct server block with this conclusion. For what it's worth, I don't recall this type of "slow first visit startup" issue happening in the past when using web applications with uwsgi, and I've had the opportunity to use uwsgi with a variety of programs. I think Gunicorn is fairly new to me. I do, however, remember that something like this might have happened in the past when using Passenger (https://www.phusionpassenger.com/) a long time ago, but that might have been setting related on my part. Okay, thanks for the encouragement about the potential solution to periodically accessing the related "example.mailman.site/mailman3/lists/" type location (from my earlier email). Wanted to check on that and was also hoping that there might be some setting I'm missing in the overall Mailman 3 project setup related to the "slow first visit startup" issue. Thank you!

4 years, 2 months

[MM3-users] Re: Mailman 3 with AWS auto scaling and potentially load balancing

by Abhilash Raj

On Fri, Mar 30, 2018, at 1:13 PM, Abhilash Raj wrote: > On Fri, Mar 30, 2018, at 12:00 PM, Chris McMacken wrote: > > Thanks for the prompt response. > > > > Why does the application store messages on the local disk? > > It is how our queuing system is built, every queue is stored on disk and > messages in intermediate states like when being processed or decorated > inside Mailman Core as stored on disk. *Most* of these isn't the > problem, since the emails are sent out pretty fast, it's the held > messages waiting for approval or broken messages in the shunt queue that > would be lost and is what I mean by "State" mostly. > > AFAIK API being served by different instances will affect what and how > many held messages are reported. > > > I'm guessing > > it's for performance reasons but wanted to ask. Do you have any plans to > > add database storage for these at some point in the future? And No, currently we don't have any plans to tinker with the queuing system in near future. It works very well right now and is quite fragile, one single bug in queuing/accounting of emails and you can bomb your subscribers with 1000s of emails or important emails being swallowed up. > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > Abhilash Raj > maxking(a)asynchronous.in -- Abhilash Raj maxking(a)asynchronous.in

7 years, 4 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by IEM Network Operation Center (IOhannes m zmölnig)

thanks both Mark and Odhiambo (who replied off-list) for your answers. On 8/6/24 18:40, Mark Sapiro wrote: > On 8/6/24 01:43, noc(a)iem.at wrote: >> >> but how can i export an entire MM3 list (including 20 years of >> archives) to some serialization format, and import it again in another >> instance? > > > With the dump and other utilities from your database manager. Almost > everything is in the database. There are some things in Mailman's var/ > directory, but those can simply be moved. > urgh. while this will (hopefully) work with a fresh installation, i'm somewhat afraid whether this will also work for: - migrating a single list from one instance to another (at least, if you (like me) do not have have an intimate knowledge about the db layout) - importing lists into an instance that is already populated with other lists (things like changed db schemas come to my mind) right now my task is to move both some MM3 lists (from an old MM3 instance) and some MM2 lists onto a single server with a fresh installation, so i guess i will be fine. my worries are mostly about future migrations. is a feature-request warranted, or am i worrying too much? gfasmdr IOhannes PS: thanks for finding and fixing the issue with my PGP signature not allowing me to post! ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

11 months, 3 weeks

[MM3-users] Re: New releases

by Abhilash Raj

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. > > вт, 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)

5 years, 1 month

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/30/20 11:24 AM, Odhiambo Washington wrote: > This works - I mean changes the error message to > > [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] > /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) I'm not sure why you are getting this warning, and it's non-fatal, but you can get rid of it by pip install cmarkgfm in your virtualenv. > [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client > 197.232.81.246:63962] AH01630: client denied by server configuration: > /var/spool/mailman-web, referer: > http://mm3-lists.my.server/mm3/mailman3/lists/ > > There is NO /var/spool/mailman-web anywhere. It has not been created. > You mentioned that it should be created automatically, IIRC. No. I think I told you that the references to /var/spool/mailman-web/static in your Apache config should be changed to /opt/mailman/mm/static and that directory would be created/populated by mailman-post-update. I think you still have Alias /static "/var/spool/mailman-web/static" in your Apache config and it needs to be Alias /static "/opt/mailman/mm/static" That may be my fault as when I recently edited <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>, I missed that line. -- 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: Can't see held messages

by Massimiliano Paragnani

SOLVED! I changed x = random.random() + right_now % 1.0 + time.clock() % 1.0 to x = random.random() + right_now % 1.0 + time.process_time() % 1.0 In mailman/utilities/uid.py and everything started to work Il giorno ven 27 gen 2023 alle ore 18:53 Massimiliano Paragnani < max.paragnani(a)gmail.com> ha scritto: > Hi everybody, > I've a new installation in my own vps. Everything works if I set "Deliver > immediately" but if I turn on the "hold for moderation" I can't see the > mails in web interface and I can't confirm the delivery or discard. > > What information do you need to help me? > _______________________________________________ > 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 max.paragnani(a)gmail.com > -- *Massimiliano Paragnani* *Clausola di Riservatezza* *Le informazioni contenute in questa comunicazione e gli eventuali documenti allegati hanno carattere confidenziale e sono ad uso esclusivo del destinatario. Nel caso in cui questa comunicazione Vi sia pervenuta per errore, Vi informiamo che la sua diffusione e riproduzione è contraria alla legge, pertanto Vi preghiamo di darci prontamente avviso e di cancellare quanto ricevuto. Grazie.* *This e-mail message and any files transmitted with it contain confidential information intended only for the person(s) to whom it is addressed. If you are not the intended recipient, you are hereby notified that any use or distribution of this e-mail is strictly prohibited: please notify the sender and delete the original message. Thank you.*

2 years, 6 months

[MM3-users] Re: REST API notes

by tlhackque

On 28-Jun-17 23:19, Barry Warsaw wrote: > On Jun 28, 2017, at 01:47 AM, tlhackque--- via Mailman-users wrote: > >> As a beginner with the REST API, I found it necessary to read code and >> experiment to figure out how to get things done. > Thanks for the feedback. Other than the work supporting Postorius and > HyperKitty, I think you've done some of the more extensive exploration of the > REST API, so your comments here (and greatly appreciated bug reports) are > quite valuable, and I think will help us make the REST API both more usable > and more discoverable. I didn't plan to become so involved, but that's what happens when one tries to use something new - perhaps for a slightly unexpected purpose. > It's important to point out some history of the REST API. I understand/expected that there was history; there is still art and evolution in software design. I hope the tone doesn't come across as critical; I only mean to report what I found so you see it from outside the development bubble. > based traversal, I was able to port the extensive existing REST implementation > to the new underlying library fairly easily. > > All this to say that some of the problems you describe are due to historical > accident. And that's served us well(-ish) while we only had to support > mailmanclient and P/HK. But as the REST API is used in more places, those > deficiencies are becoming more glaring. I think if we ever make progress on > Lemme (our authenticating REST proxy), we'll likely encounter the same > problems. But at this point, it's infeasible to completely reimplement the > REST machinery. I don't think it needs to be re-implemented. There are some some fairly simple things that could address the challenges I've found. I'll try to add some notes to/add new bug reports as I have a chance. (But I'm really trying to make progress on my project, of which this is a small part...) > > Much of that is because these are doctests, i.e. testable documentation. It's > a tradeoff between making them useful as docs but also testable without too > much clutter. It's very much oriented toward Python because that makes > testability easier. It would be good to have documentation for pure HTTP/JSON > consumers, but it would be imperative for that also to be testable so we're > sure it remains accurate, aside from any requirements to keep the docs in > sync. Suggestions and contributions would be very much welcome here. If the APIs are supposed to be equivalent, I'd try to define a consistent mapping between the http (S!) API and the internal Python API. Since the implementation is pretty consistent, that shouldn't be too painful. If that can be done, then the same tests can verify the Python API and prove that the HTTP functions are equivalent. The other thing to consider is some tests that are higher level and can become documentation examples. E.g. Starting with an empty installation, create a list with an owner and a subscriber. Which would be in order, every API call necessary to implement this, and then verify (with GETs) that all the objects exist with the right properties. Currently that takes me about 220 lines of source (Perl, includes blank and closing '}' lines, but still...) Not counting loops, I think there are 10 places where I call the API for what is expected to be an 'atomic' create of a list. >> The REST API has a hybrid interface: Requests are made with >> application/x-www-form-urlencoded POST, PUT, PATCH and delete http requests. >> Requests are also accepted as parameter strings. >> >> The responses are JSON. (This is rather surprising - one would expect JSON >> requests - and I hope someday they'll be accepted, as the split complicates >> clients. I suspect this evolved to simplify the initial Web GUI client >> (Postorious), but it precludes using standard JSON-in/JSON-out client >> libraries.) > Absolutely. I want to support JSON-in/JSON-out. Again, the current mismatch > is due to historical implementation decisions, but there's nothing in > principle preventing us from accepting JSON in, afaict. We'd have to continue > to accept both, for backward compatibility reasons. I noted somewhere that this should be easy to implement. I expect that you get an associative array ("dict"?) with the webform parameters. Decoding JSON also ususally provides an associative array. The parameters have the same name. So you should be able to address this at your API entry point, e.g. if the inbound request is Content-Type: application/json, decode as JSON; if x-www-forms-urlencode, decode as today. Then you have the same parameters, and they go downstream for decoding in the array - again as today. I haven't looked at the code (not being a Python person), but I'd be surprised if this was not feasible. >> Error responses are often misidentified as content-type: application/json, >> but actually contain a text/plain error message. This isn't universally >> true; for example the 401 response actually IS JSON. A client has to guess >> and handle decoding exceptions. > That's clearly a bug. The Content-Type should always be accurate. It would > be a new feature to also support JSON error responses. Except that for some responses, you already do... > >> The API presents resources hierarchically, rooted at '/'. The top level >> resources include /users, /lists. /addresses, /domains, /system >> >> The next level is a resource id. > Kind of. It all depends on what the top-level resource is returned. This > makes sense when you think about the object based traversal machinery. > > Each path component points internally to an object, and the subsequent path > component is handled by that object. If that returns another object, then the > next remaining path component is consumed by *that* object. And so on until > we reach the end of the path. Then the object at the leaf responds to the > HTTP command, and each object knows how to represent itself as JSON, and it > knows its canonical location within the resource tree (there can be multiple > paths to any particular object, but there's always one canonical location). That's a better description from inside. I was trying to summarize what it looks like to someone trying to use the API.... > >> There is a an id which is stable for the lifetime of an object, and a current >> name (which can be changed). For example, a list has a name like >> mylist(a)example.com, and a list_id of mylist.example.com. But if you change >> the list name, it becomes mynewname(a)example.net, while the list_id remains >> mylist.example.com. > Lists are weird in that they have two identifiers. One is the posting > address, what we internally (and slightly incorrectly) call the "fully > qualified list name". I don't particularly like that nomenclature anymore, > but we live with it. We all have similar artifacts in any non-trivial code... > A posting address can change, e.g. if you rename or rehome a list. > > The (RFC 2919) List-ID is assigned when the mailing list is created and it's > immutable. Section 4 discourages changing the List-ID and Mailman takes that > as a requirement. Rename a list or rehome it to a different domain on the > same server and the List-ID will never change. Yes. > Again for historical reasons, many APIs both internal and external used the > posting address to identify the list, but this is wrong exactly because that > can change. I've slowly been converting APIs to accept both the posting > address and the List-ID when identifying the mailing list. New APIs generally > accept only the List-ID. Bottom line, it's best to use the List-ID. I noticed that, and indeed go to some pains to fetch the list_id for chained operations. >> Lists are associated with "domains", which are the "domain part" of the >> list's address. That is, the part after the @. This is sometimes referred >> to as the "mail host", but there need not be a real host. > Yep, again historical nomenclature. I understand the history. But I was very, very confused by the overlaid uses. Even in the GUI, I couldn't decide what I should enter. (And I'm fairly familiar with e-mail RFCs and history...perhaps that's my problem.) Documentation needs improvement. Feel free to use (or improve) my words. > >> A domain has to be created before you can create a list with an address in >> that domain. > Some APIs (e.g. `mailman create` CLI) will create the domain automatically if > it doesn't already exist, and unless you disable that explicitly. I was writing exclusively about the REST API. I couldn't create a list without the domain, so I create the domain unconditionally (and ignore the 'it exists' error); that's cheaper than query+create. "Create if not exists" would be a useful API extension, since clients would see a success code either way. (200 OK for exists, 201 Created for new). > >> Resources are created with a POST to their top-level resource. To create a >> domain, post to /domains with mail_host => the domain, and (optionally) >> description => a description for the GUI. The response isn't JSON as one >> would expect. In fact, it's an empty application/json response with a 201 >> status. >> >> To create a list, one POSTs to /lists. This post takes a restricted set of >> parameters; in the case of a list, just its fqdn_listname, (and an optional >> style - which isn't well defined). The response isn't JSON as one would >> expect. The Location header of the response contains a URL of the new list. > What else would you expect? From my reading of books like RESTful Web > Services (admittedly a long while ago), that's exactly the proper response to > an appending POST. Return a 201 with a Location header to the new resource > and empty content. I didn't read the book - but I have talked to a number of services that claim to provide a RESTful API. Of course, REST is a style, not a specification, so mileage varies... I would expect the new resource address to be in the JSON body of the response. I don't mind the Location header (if you imagine the response to be a 301, it kind of makes sense). But a client (well, at least mine) wants a consistent place to look for the result of an operation. That would be the HTTP Status + JSON reply. This is inconsistent - and with JSON REST client libraries, it turns out to be more difficult to get at the headers. (I patched the one that I use...) My 3 cents: if an interface is JSON, it should be usable entirely as JSON. JSON in, all JSON out.... This simplifies life for a client: Get a response, decode the JSON - and everything is in the decoded JSON (usually an array or associative array in whatever language). Not some in the JSON, some in the Response headers (and some in the HTTP status - which usually is replicated in the response JSON), and some plaintext in the response body. > >> To configure the list, you have to follow up with a PUT or PATCH to that URL >> + /config This is where you can set the description, posting policy, etc. >> It's unrealistic to do a PUT; even if you're cloning another list, there's no >> programatic way to determine which attributes are writable. PATCH what you >> know... > Mailing list resources are somewhat unique in that they probably have the most > properties of any resource/object in the system. That's not surprising if you > think about it, but it does make PUTing to a mailing list more or less > impractical. That's certainly not true of other, smaller resources though, > and of course, you still want symmetry there (plus, implementation-wise, it's > almost a no brainer to support both PUT and PATCH). The problem is that from a client, there is no way to know which attributes are writable, and which are immutable. So get (template), modify, put (new) doesn't work. There should be a way to find out what attributes are writable. Or the API could ignore writes to immutable attributes, and return "success" (or in a JSON reply, "partial succes") to the client.... >> Members are associated with e-mail addresses - which belong to Users. > Users can have multiple addresses, addresses can be linked to only one user, > but may be unlinked, and members associate "subscribers" to mailing lists, > where a subscriber is either a user-with-preferred-address, or an address. I saw that. I didn't look into the unlinking part, as (oddly enough) I'm only trying to do a restricted subset of the possible operations. All I need to do is create & configure a list (with a couple of members) on-the fly. (Oh, and post an announcement of the fact on a related list.) The tricky part is that it's all done without human intervention. >> You create a user by posting to /users with email => the email address, and >> optionally display_name => the name string. (A user can also be implicitly >> created by subscribing an e-mail address, but that gets confusing.) The >> e-mail address is the primary email address for the user. More later. >> Again, you get a Location header in the response, which you can use to PATCH >> /preferences to set delivery_status, etc. .These preferences are part of a >> hierarchy - many have a system default, a list default, the user default, and >> a subscription to that list value. You can find the User associated with a >> list by a GET of /addresses/address(a)example.net. > Technically, the returned user isn't necessarily associated with a list. It > *may* be subscribed to the list, but that relationship is represented by a > member. I understood that. > >> This GET returns two URLs: user => the user owning this address, and >> self_link => the address object. > *All* resources in the REST API have a self_link, and while that may seem > redundant, it's not. As mentioned above, you can take various paths through > the resource tree to get to a particular resource, but regardless of that, > every resource has exactly one canonical location. That location is > represented by the self_link. Yes. >> Note also that there are both an email and original_email attribute. The >> latter preserves case. The former is used internally by Mailman as a >> resource key, etc. (Though exactly what happens if John(a)example.net and >> john(a)example.net both subscribe is unclear.) > They can't. Mailman is case-preserving case-insensitive for email addresses. > Technically speaking, john(a)example.com and JOHN(a)example.com can be different > mailboxes, but that never happens in practice anymore, and Mailman has always > explicitly treated them as the same address. This goes back to the earliest > days of Mailman. I still run into systems that demand exact case for delivery. I agree that two different humans assigned to such a mailbox would go (or already are) crazy. But I have seen John using john and JOHN as two different identities. I havesuggested using '+' subaddressing instead. Then again, 70% of of the e-mail address validators that people come up with reject clark+kent(a)example.net because of the '+'... I am curious as to whether anything breaks if I subscribe to a mailman list with a plus address, but it's low on my list... >> Once a list is configured, you can add members. This requires the list_id - >> which you don't (officially) have. So you do a GET on the list resource, to >> get the list_id. Then you can subscribe a member with list_id => (the list >> id), subscriber => email address. Optionally you can >> pre_verify/confirm/approve the member and/or add a display_name.. POST to >> /members. Again, you get a Location header back. You can't specify >> everything you might like. as a creation attribute. So you may have to PATCH >> the member to, for example, set the moderation_status. > This is true, but it also kind of makes sense if you grok the way preferences > work, i.e. hierarchically as you describe above. TBH, I don't particularly > like the way preferences are modeled either internally or through the REST > API, but I haven't been able to come up with anything better. > >> You may also need to PATCH the member /preferences if you want to set >> list-level delivery status, etc. > All true. In each of those cases, you may be talking to a different > preference resource. > >> Consider adding at least an owner when creating a list. > I think that would be a useful addition to the REST API for list creation. > >> One challenge is that almost everything requires multiple REST operations to >> set up. But REST (by definition) is stateless. So the best you can do is >> order operations & hope. > I don't understand this. REST is stateless, but not all HTTP operations are > idempotent. POST certainly isn't, by definition, so if you use it to create a > new resource under a collection, you clearly cannot modify that resource > through PUT or PATCH until the resource is created, which only happens when > POST succeeds. I've written up an issue on this with some more detail/thoughts and will post (er, no pun intended) it shortly. The short form is that (as noted below), I want a list to atomically create a list - either it exists (configured the way I need it to be), or it doesn't exist. That's not possible. So I create a domain, create a user, configure the user, create a list, configure the list, add the user - but at any point in the middle, a message could arrive for the non-quite-configured list. This isn't good... > >> The mailman client examples refer to transactions (e.g in users.rst, there is >> 'transaction.commit(); - but REST can't hold state. It does appear that the >> server uses DB transactions to ensure that any given REST operation is ACID, >> but the composite operations (e.g. create a list and set it's config) can not >> be Atomic. This is an architectural flaw in the API. > I think what you're getting at is that some POSTs to create new resources do > not accept the same parameters as the subsequent PUT or PATCH on the newly > created resource. I think that may be true, but it's not universally so. > E.g. POST on /domain creates a new domain, returning the location of the new > resource. You can provide both a description and an owner, and you can also > provide a mail_host. But mail_host is immutable, and PATCH or PUT support > changing all mutable attributes on the domain. > > That should be the general rule; if an attribute on a resource is mutable, you > should be able to PATCH and PUT it, *and* you should be able to specify all > mutable attributes, plus some immutable ones on the POST that creates the > resource. Yes. I can't specify everything about an object on many posts - list creation the the most glaring example. Also, things linked to the object - e.g. if I create a member, I have to: POST (create the member); PATCH (set moderation_action; PATCH(preferences) to set (delivery_status,hid_address,receive_list_copy,receive_own_postings). That's three REST calls for what should be one - ATOMIC transaction. Plus, this is separate from the list creation, so there's a window between creating the list (even if it were atomic - which it isn't) and the time its required members are subscribed. > GET should return all attributes, mutable or immutable. This rule > may not be strictly adhered to for all resources and collections, but I would > consider that a bug, not an architectural flaw. > > AFAIK, this is all working as any well-defined web service should work. >> Symbolic names (which are required) for attributes are in the >> src/mailman/interfaces/(class).py. > Please note that the interfaces under this package are for the *internal* API, > which often, but not always, is exposed in the REST API. These two APIs serve > different purposes so they cannot be a one-to-one mapping, and there are many > resources in the REST API that don't correspond directly to internal objects, > and there are many internal objects that are not exposed to the REST API. There was no other place I could find that defined attribute values for enumerated items. E.g. delivery_status => 'by_user' - interfaces is where I found how to spell 'by_user'. Maybe I missed something more obvious. >> What you can get/set comes from src/mailman/rest/(class).py. > Yes, so clients of the REST API are served by objects in this package. > Plugins and other internal operations are served by the objects that implement > interfaces in the src/mailman/interfaces package. This is a strict separation > of concerns, and it mirrors other 'external facing' interfaces, of which the > command line is another example. I keep struggling with wanting to understand the external model of the API without having to understand the internal implementation. When the API is formally documented, I encourage you to de-emphasize the internal model and concentrate on the external interfaces in client terms... > Hope that helps. Yes, thanks. > -Barry >

8 years, 1 month

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Mark Sapiro

On 3/18/19 2:19 PM, Ralph Seichter wrote: > Hello list. > > I have read [1] and [2], but I am not quite sure what the recommended > method is to completely disable message headers/footers and subject > modifications for *all* lists tied to a specific domain. Being new to > Mailman 3, I was actually surprised that there are no configuration > switches in the Web UI's settings for mailing lists that allow me to get > rid of unwanted message decorations. It's still a work in progress. You can do it via list settings except for one issue [1]. See that issue and also the post referenced in it's description [2]. To not modify the Subject for a list, on the list's Settings -> List Identity tab, set 'Subject prefix' empty. To not add headers and or footers, you need empty templates for them. These could be created via the list's Templates form except until [1] is fixed, you can't make empty templates. You can use the method in [2] to create empty var/templates/domains/DOMAIN.NAME/LC/list:member:generic:footer.txt and var/templates/domains/DOMAIN.NAME/LC/list:member:generic:header.txt files for the domain and language. Then as long as no list specific templates are created for lists in that domain, no headers or footers will be added. [1] <https://gitlab.com/mailman/postorius/issues/331> [2] <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/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, 4 months

[MM3-users] Re: task runjobs minutely uses 100% cpu

by Abhilash Raj

On Tue, Aug 13, 2019, at 2:00 AM, Lars Schimmer wrote: > Hi! > > Since we do run roughly 40 mailinglists on mailman3, the > schedules/cronjob task > python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU > core 100% all the time. > > Any idea howto see why? So, the minutely job updates the fulltext index, which uses a Python based indexing library called Whoosh. Whoosh is good for testing but doesn't work well for prod environments at scale. There is a need to update the docs, but it would be great to move to a better indexing engine like Xapian or ElasticSearch (which we have been using on this list for a while). As a short-term fix, you can move the minutely cron job to run every 15minutes or even 1 hour. The only delay you will see is that it will take new emails upto 1hour to be indexed via search, which I don't think is a big deal. > debian mailma3n-full package 3.2.1-1 > Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC > 8.3.0] > > > > MfG, > Lars Schimmer > -- > ------------------------------------------------------------- > TU Graz, Institut für ComputerGraphik & WissensVisualisierung > Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at > Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 > > > _______________________________________________ > 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/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

5 years, 11 months

[MM3-users] How to approve moderated messages via email?

by Stephen J. Turnbull

Brian Carpenter writes: > What is the protocol to approve moderated messages via email? I > hope I asking the question correctly. Is this capability important to you or your clients? If so, what is the context? I ask because, as you know, email is rather insecure by default. Making it highly secure would require a lot of effort and sophistication for the moderator, eg, PGP signatures, but there might be intermediate levels that would be appropriate for many lists. For example, the Mailman 2 mechanism. I forget exactly what Mailman 2 does, but if the post to be approved were identified by a one-time key, then a spammer would have to have both the moderation password and the key (presumably by intercepting the moderation email) to approve their own spam. That's still a plausible scenario in principle[1] so I don't much like it (and I bet that's why Barry didn't implement it), but it would be straightforward to implement. Footnotes: [1] Ie, a moderator falls for a phish; then Ms. Cantor[2] probably got everything she needs to spoof approvals. It's questionable whether a spammer would go to the trouble of identifying a moderator, phishing them, reading their mail, and using the email approval to spam for profit, of course. But I can easily imagine it if somebody hates you. On the other hand, if they have your Gmail password, and you use your Gmail account to authenticate to Postorius, they can do it by web, so disallowing email approvals is no help. Security is hard .... Maybe we should implement 2FA for privileged roles. [2] Original "Green Card Lawyer".

4 years, 6 months

[MM3-users] Re: hyperkitty_import Unicode Errors - Drop all Archives and Start Over?

by Mark Sapiro

On 5/16/23 08:49, Dave Hall via Mailman-users wrote: > > What I would really like to do is to drop all of the previous archives and > start fresh. Looking at the table list for the database, It would appear > that all of the archive content is stored in the tables with names that > start with 'hyperkitty_' I'm wondering if I could just wipe the content of > these tables, or exclude them from a backup, and then start fresh. It is correct that all the HyperKitty tables start with `hyperkitty_`. I *think* it would be safe to just drop the content of these tables, but I won't guarantee that there aren't `django_mailman3_` tables with foreign keys into the hyperkitty tables. As a superuser logged in to hyperkitty, you should see a Delete Archive button at the top level overview for a list. It would be safer to delete the archives that way. > Alternatively, if I restore the exiting archives to the new database with > the correct unicode settings, could I re-run the hyperkitty-import tool and > get it to pick up all of the messages it skipped due to the unicode problem? This will work too. You will need to specify the --since option to hyperkitty_import because the default for `since` is the date of the newest message in the archive. The import will not reimport a message whose Message-ID: is already in the archive. -- 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: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/14/2016 07:11 AM, Mark Sapiro wrote: > On 5/13/16 5:05 PM, Simon Hanna wrote: >> On 05/12/2016 09:26 PM, Barry Warsaw wrote: >>> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >>> >>>> It is the intent that Postorius will eventually expose all these >>>> settings. We're not there yet. At present you could possibly do this by >>>> interacting with mailmanclient, although I'm not certain the settings are >>>> exposed there. >>> >>> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >>> core's REST API, on the member resource. It's the `delivery_mode` attribute >>> and it takes as legal values one of 'regular', 'plaintext_digests', >>> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >>> DeliveryMode enum). > >> They are exposed in mailmanclient and are used in postorius. They can be >> found in the users personal subscription settings >> https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > > You are correct. When I checked this before my initial reply, I never > pulled down the Delivery Mode list to see all the options. My bad. > > However, please correct me if I'm wrong, but there does not appear to be > a way in Postorius to set a list's mime_is_default_digest attribute. > You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.

9 years, 2 months

[MM3-users] Re: Whitelist non subscriber

by Mark Ziranski

Hi, thanks for your reply. Can I set the moderation_action on this member? I cannot figure out the API command. All posts of other members should be moderated. POST: http://localhost:8001/3.1/members role=nonmember list_id=something.localhost subscriber=someone@localhost moderation_action=accept Reply: Unexpected parameters: moderation_action Thanks. Gesendet: Donnerstag, 10. August 2017 um 22:05 Uhr Von: "Mark Sapiro" <mark(a)msapiro.net> An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Whitelist non subscriber On 08/10/2017 07:12 AM, Mark Ziranski wrote: > > I want to whitelist an email address on all lists to bypass moderation. > The email address is not a subscriber. On google I > found accept_these_nonmembers but I do not know how to use it. > Please show me some examples how to whitelist someone(a)example.org. Since this is a Mailman 3 list, I assume you are asking about MM 3. Mailman 3 defines the list attribute accept_these_nonmembers, but it is not currently implemented to actually have any effect, nor is it exposed in Postorius. At the present, I think you would have to create a user record with the address and add that user to all lists with role nonmember and moderation_action 'defer' to apply subsequent tests or 'accept' to unconditionally accept posts from that address. (In MM 2.1, accept_these_nonmembers is a list of addresses and regexps matching addresses whose posts are to be accepted, subject to subsequent tests, and is exposed in the web admin UI) -- 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 [1]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org / References 1. https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 11 months

[MM3-users] Re: Topics - Tags

by Stephen J. Turnbull

Mark writes: > >> In Mailman 2 there is an Admin web UI for "Topics". Is there > >> such a web UI that can be enabled in Mailman 3 so that the list > >> owners can create topics (tags) in their lists? Do you specifically want topics, that is, a way for users to select subsets of the list posts based on themes set by the administrator? There is (was?) an alternative specification implemented by the Systers, which they call "dynamic sublists". The dynamic sublist feature is controlled by the users (thus "dynamic"), using specially formatted email messages to tag threads as "sublists" and to subscribe to them or suppress them. This was implemented internally by the Systers so it has not been contributed back to the Mailman project, and it was integrated with other Systers-specific features, so it wasn't just a matter of a git merge, If that sounds as good as Mailman-2-style topics to you, I can add/emphasize it on our GSoC task list. (It was on our GSoC task list for several years (maybe still is, I need to check that since contributor applications are now open.) The Systers users are developers themselves, so using email commands isn't much of a burden. I don't think it would be impossible to add sublist control features to Postorius, but it's nontrivial, and might require a second project to implemnt after the initial port. I may add the Mailman-2-style topic feature as well, although in my opinion the dynamic sublist feature is a better match for Mailman's core audience (lists that support open source development organizations). Steve

1 year, 4 months

[MM3-users] Re: Mailman3 on FreeBSD

by Barry Warsaw

On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> wrote: > > The instructions say > > After this, create a configuration file at /etc/mailman.cfg for Mailman > Core. > > On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't > see any indication as to what I should put in this file and if it was in > /usr/local/etc/mailman.cfg then how would mailman find it? It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro? (Side note, you can always use `-C /usr/local/etc/mailman.cfg` or set the MAILMAN_CONFIG_FILE environment variable for alternative locations.) > I'm using a different system to install Mailman so it's difficult to paste > the error msgs, but it seems to be related to being unable to find the > module '_sqlite3' That’s a Python problem. What does the following do for you? % python3 Python 3.6.2 (default, Jul 27 2017, 18:13:18) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import _sqlite3 >>> _sqlite3 <module '_sqlite3' from '/usr/local/Cellar/python3/3.6.2/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload/_sqlite3.cpython-36m-darwin.so’> This is what you get from a Python 3.6 installed via homebrew on macOS. Maybe you need to install another package to provide SQLite on FreeBSD? -Barry

7 years, 11 months

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

by Mark Sapiro

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

6 years, 3 months

[MM3-users] Mailman archive issues (Hyperkitty)

by klillipuu＠gmail.com

Hello All! I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). I also mention, that hyperkitty is a pretty old version - 1.1.4. The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? Extra information: * I have also noticed some memory violation issues which has caused by uwsgi. * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Output from mailman.log: HyperKitty failure on http://localhost/hyperkitty/api/mailman/archive: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (504) Exception in the HyperKitty archiver: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (1808) Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html>

4 years, 2 months

[MM3-users] Re: Postfix-Fehler mit mailman-web

by Jens Günther

Am 28.08.23 um 10:21 schrieb Stephen J. Turnbull: > Jens Günther writes: > > > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: > > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host > > rejected: cannot find your hostname, [192.168.176.6]; > > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> > > There are a bunch of $myxxxx variables in Postfix, I think $myhosts > might be the right one. If you add the IP 192.168.176.6 to that > variable, it will be whitelisted and this problem should go away. > There may be better ways to handle this, but don't mess with > hostnames. Find the "right" way to permit that IP should do the job. Thank you, adding the IP/network under mynetworks, as Abhilash writes, the error is gone. (this is so dumb, somehow docker started with a different IP and I have to figure out why ... and there is another Django-error -> shall I open a new thread? "OSError: [Errno 99] Address not available") > > I mean the hostname for the core-container must be there, since > > mail is accepted :-D > > That's not the way this works. Postfix accepts the mail because it's > arrives at the physical host, then looks up routing for the mailbox > and discovers it should be delivered via LMTP to the core container's > IP. No hostname needed. Ok, probably a misunderstanding. I was saying, that mails from core are relayed correctly to the outside world ... that's because the mailman-network was was relayed, but as I wrote, the web-container somehow got a different IP now. Thanks again.

1 year, 11 months

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

by Odhiambo Washington

On Mon, Nov 20, 2023 at 7:56 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > The idea is to (if possible) not change anything at all. I will be > > serving the list using the original domain. > > Fine. I just didn't want to assume anything. > > > I am hoping that should not be necessary. > > It's not. That's one of the major things that MM3 does that MM2 does > not: handle multiple domains properly. > > > I actually had thought it wouldn't be complex doing this until I > > sat down and said wait - there is a DB involved :) > > > 3. (If the DB engines are different) Dump both databases in text > > > format (ie, scripts of SQL commands). Check to see how they > > > differ. > > > > > > > The DB is MySQL. My running setup uses MariaDB. I am not getting what > you > > mean here by how they differ. > > You didn't say that before. I tend to assume PostgreSQL because > that's what I use. > > I don't know if MySQL and MariaDB have different features that have > different syntax, etc. That's what you're looking for. Any commands > that are *not SQL* used to configure the database engine itself (for > example the utf8mb4 parameter which MySQL has but PostgreSQL does not, > does MariaDB need it?) Also any non-standard SQL stuff (mostly around > varchar/text types I think). > 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. > 4. Adapt the foreign database to its new environment with search and > > > replace. > > > > If going with what I have mentioned above, is this step still > > necessary? > > 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. > > > 5. (Optional if your name is "Daredevil") Create a new Mailman suite > > > install using your current configs, preferably in a new VM or set > > > of containers. > > > > I was thinking about this as one way of testing the situation, much > > as it is quite involving. > > Fred Brooks famously put it this way: "Build one to throw away. You > will anyway. The only question is whether you deliver the first > version to the customer." ;-) > I had to Google who he was :-) > Suppose I just do: > > 1. Create the new list on my server using the inherited domain and > > configure it appropriately, > > 2. Configure Django to handle the different domains (there is something > > that I am yet to understand here around SITE_ID when you have multiple > > sites!) > > You just add them in the Django admin page. Problems come in when you > delete the original example.com placeholder domain. I think you > probably need to add SITE_ID=0 to settings.py so the Django figures > out the site from the HTTP header rather than just assuming it's the > same Postorius site for all lists. > In my case, I did not delete the original example.com. I finally get to use SITE_ID=0. I suppose that it should be accompanied by FILTER_VHOST=True > > 3. Extract the users from the list and subscribe them afresh (I can > > shoot an email to let them know the ML had to be moved so they can > > set their preferences again) > > 4. Import the archives of the list > > I should more or less achieve the migration, no? > > I think that should work. > I am going to try this method. It looks safer for me. > > What about setting up on /opt/mailman2 a complete replica of the > > list? That'd be the real "Daredevil" :) > > This will also work, I'm sure. But we'd be embarrassed after going to > the trouble of making Mailman 3 handle multiple domains. Also you'd > need separate instances of Mailman running, with their own > /etc/mailman3-1 and /etc/mailman3-2, and more important you'd double > the RSS and VM requirements by running two instances. > I also will need to have extra macros, routers, and transports for Exim. This method is untenable as it complicates life. -- 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, 8 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Eggert Ehmke

Hello Mark, thank you. I did change that entries, and now my mailman runs fine on Debian Bookworm. I did a complete reinstall of the venv directory to have a clean start. Maybe this was not needed. What's missing in the documentation: -the directiories web/logs have to be created manually with the ownership mailman. -The debian package pkg-config must be installed. -the package psycopg2-binary can/must be installed without version restriction on Bookworm Maybe this info helps some other people. Cheers, Eggert Am Montag, 26. Juni 2023, 22:22:37 CEST schrieb Mark Sapiro: > On 6/26/23 12:35 PM, Ken Alker wrote: > > I'm brand new to this, so take this with a grain of sale, but, I had a > > similar problem a few days ago, however, mine was "flufl.i18n>=3.2". > > Perhaps the same thing is happening with flufl.lock (but that didn't bite > > me). > > > > I solved my problem by following this: > > <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately > > modifying > > "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires. > > txt" per that thread (see > > <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by > > Thomas Ward section called "The WORKAROUND"). Maybe you need to do the > > same thing, but for flufl.lock. > Yes, the same issue now affects flufl.lock as well as flufl.i18n. You > will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 1 month

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Odhiambo Washington

On Thu, Aug 8, 2024 at 10:34 AM IEM Network Operation Center (IOhannes m zmölnig) <noc(a)iem.at> wrote: > On 8/7/24 12:55, Odhiambo Washington via Mailman-users wrote: > > On Wed, Aug 7, 2024 at 1:05 PM IEM Network Operation Center (IOhannes m > > zmölnig) <noc(a)iem.at> wrote: > >> - ./data: empty > > > > With a Postfic MTA situation, that would have had some files. So you > don't > > use Postfix. > > > >> - ./lists: empty directories named after each list (i think these are > >> used by the MTA to determine whether it should hand over a mail to the > >> mm3-ltmp) > > > > True, at least according to Exim MTA. > > indeed, i'm using exim. > i guess these directories are named like they are for backwards > compatibility. > if the sysadmin is supposed to ever do something with them, it would be > nice if there was some (discoverable) documentation (like a README in > Mailman's var; or the yet-to-be-written mm3-to-mm3 migration guide; even > if those files/directories are mentioned in the Bible for installing > Mailman, i don't think this can be found by a normal administrator (it's > not reasonable to assume that one should look up each file/directory in > Mailman's var to see if it is needed). > If you read that Bible with a toothcomb, you will be led to the READMEs which are online. And I think the Developers wrote this summarized version of the 'Bible' with the focus of getting us up and running with MM3 in the easiest way and shortest time. The complete MM3 'Bible' <https://docs.mailman3.org/projects/mailman/en/latest/README.html>is as large as the real Bible itself and that is left for the curious to go read online: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… >> - ./locks: plenty of lock-files, most of them rather stale (as in: 3 > >> years old) > > > > So MM3 on that host hasn't been running or? > > it *is* running. > i do not know why it didn't cleanup. > > > > - ./messages: a couple of old messages (i think all of them have been > >> held for approval) > >> - ./queue: dirtree without files > >> - ./templates: more templates for the existing mailinglists, though they > >> don't seem to be used (are these the fallbacks when I remove a template > >> via the webinterface?) > >> > > > > Yes. > > so can i just ignore them? > I believe it is safe to ignore them. > > So out here we focus so much on the following as the Bible for installing > > and running MM3: > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > probably. > sorry for being obtuse. > > afaict, the documentation is written for people setting things up from > scratch, where the paths are mostly setup automatically, and you only > need to configure them manually for interoperability with other software > (e.g. when using postfix as the MTA, the docs tell the admin to ensure > that both mm3 and postfix communicate via the same paths). > I am not sure that is entirely correct. People have installed MM3 on paths other than what the docs say. Narrowing down on Postfix, I know that all it needs to be told is how to 'know the lists being created by MM3 in order to handle mail deliveries for MM3'. There are instances where people don't even run a local Postix instance. > i guess i'm confused because it is unclear to me, which of these paths > hold persistent data, and which are just for ephemeral things > (like sockets). > In the summarized Bible, there is a reference to https://docs.mailman3.org/en/latest/config-core.html#config-core, which tells you that! There are also other references to the things you are interested in. Just a little more curiosity and you find them. PS: I saw the point you raised about the "the yet-to-be-written mm3-to-mm3 migration guide". In one of my responses to your posts, I attempted to write part of the process off the top of my head. I think you are going finish writing it for us since you are on that path. You will be able to complete the portions that I left out. Your experience, if documented and discussed here (addressing the pitfalls on the way) will finally bring forth that document. Or a semblance of 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]

11 months, 3 weeks

[MM3-users] Re: Mass subscribe bug - if you delete and re-add users it does not use updated info

by Abhilash Raj

On Thu, Sep 5, 2019, at 3:22 AM, roger(a)reasonal.com wrote: > Hi all -- think this is a bug. I had added some users as a mass > subscribe. Some were Name Surname <name(a)foo.bar> format, some were just > email addresses. I wanted to update the member list with complete name > & email addresses. I unsubscribed the partials, and re-added them as > full versions. However the updated member list keeps showing the > partial address only. > > This bug also works the other way. I added "Bob Smith <bob(a)bob.com>", > checked it was there in list. Unsubscribed the address, and then > re-added as "bob(a)bob.com" -- now in the members list it appears as the > full "Bob Smith <bob(a)bob.com>. This behavior happens because Mailman will remember all the "users" once it has seen it. It usually doesn't update the user's name (add or remove) it once it knows about it. Addition might be something we *could* do, but I don't think it makes sense to remove the user's name. Note that the user you add and subscribe has the ultimate control over their name. "Subscription" or "Unsubscription" process merely links or unlinks them with the MailngList. The link is what is called a "Member". > _______________________________________________ > 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, 10 months

[MM3-users] Re: Problem with database change sqlite -> mysql

by Stephen J. Turnbull

moritz both writes: > > "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/query.py", > > line 435, in get > > raise self.model.DoesNotExist( > > hyperkitty.models.email.DoesNotExist: Problem installing fixture > > '/home/daneben/mailman-suite/datadump.json': Email matching query does > > not exist. I assume you're using "python manage.py dumpdata > datadump.json" to dump and "python manage.py loaddata > datadump.json" to load the data? Are you using the right python binary, ie the one Django uses? I guess it's possible that some data is not in the database, but retrieved from Mailman core's on the fly, in which case you need Mailman core running. That said, this is entirely handled by Django, I think, and you might be better off asking on Django channels. I'll give you a couple of wild guesses, but unless somebody else knows more about Django than I do, it's probably fastest to ask on Django channels. I did a quick search for "datadump.json" and brought up these references, but none seem to refer to Mailman: https://stackoverflow.com/questions/4371375/db-error-when-running-python-ma… https://www.reddit.com/r/learnpython/comments/8jkre9/deserializationerror_w… https://www.rockandnull.com/django-dumpdata/ Here's a tutorial on SQLite to MySQL migration in Django: https://newbedev.com/what-s-the-best-way-to-migrate-a-django-db-from-sqlite… These are tutorials on SQLite to PostgreSQL migration in Django: https://www.solution-hub.com/Blog_description/37/ https://dev.to/thepylot/how-to-migrate-data-from-sqlite-to-postgresql-in-dj… https://gist.github.com/sirodoht/f598d14e9644e2d3909629a41e3522ad https://simpleit.rocks/python/django/migrate-django-sqlite-to-postgresql/ Perhaps one of those references will help. Steve

3 years

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/24/22 10:57, sascha.rissel(a)gmail.com wrote: > Hello, > > I have newly set up Mailman 3 on Ubuntu 20.04. > Sending and receiving mails between list members does work, but I am currently experiencing two issues: > 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. > 2) Archiving is activated within list settings, but there isn't any archive created. > > I found this thread, where the first of these issues is also described: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. > I am running Mailman 3.2.2 on Python 3 .8.10. This is only one of the issues with the Debian/Ubuntu packages. > So I need to either upgrade Mailman Core or downgrade Python. > I already did >> apt-get upgrade >> apt-get update > Unfortunately this didn't upgrade Mailman Core's version. > > Which steps do I have to undertake to upgrade Mailman Core? I suggest first removing the Debian/Ubuntu packages and installing the PyPI packages following docs at https://docs.mailman3.org/en/latest/install/virtualenv.html. There are also other takes on this at https://wiki.list.org/x/17891998; https://wiki.list.org/x/17892066 and https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… This will require some effort, but you will be freed from dependence on out of date packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/24/23 07:20, Stephen J. Turnbull wrote: > > The only thing I can think of at the moment that might move the > discussion forward is if Mark knows how to run his test in your Docker > environment to see if it also produces > Content-Type: text/plain; charset="US-ASCII" > Content-Transfer-Encoding: 7bit Assuming there is not something like ``` [language.en] charset: utf-8 ``` in your mailman.cfg overriding the default us-ascii charset for English, if you send a message From: yourself to list-confirm-xxxxxxx(a)example.com with Subject: Re: Your confirmation is needed to join the list(a)example.com mailing list (replacing list and example.com with the actual list and domain), you should receive a response like (some headers removed) ``` Subject: The results of your email commands From: list-bounces(a)example.com To: mark(a)example.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: <169556563227.2592.7908020161516725770(a)example.com> Date: Sun, 24 Sep 2023 07:27:12 -0700 Precedence: bulk X-Mailman-Version: 3.3.9b1 List-Id: A test list <list.example.com> List-Help: <mailto:list-request@example.com?subject=help> List-Owner: <mailto:list-owner@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> The results of your email command are provided below. - Original message details: From: Mark Sapiro <mark(a)example.com> Subject: Re: Your confirmation is needed to join the list.example.com mailing list. Date: Sun, 24 Sep 2023 07:27:10 -0700 Message-ID: <20230924142710.GA23819(a)example.com> - Results: Confirmation token did not match - Done. ``` What do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Held messages not delivered after approval

by Stephen J. Turnbull

Stephan Krinetzki writes: > And then there is a logrotate: > And yes, this restarts mailman at midnight. Maybe i should optimize > the logrotate. Not sure what you mean by "optimize". Because of the bug I mentioned earlier, in older versions of Mailman 3 the master process would fail to close some of logfiles. After rotation, the master process would continue writing to the still-open file handle, defeating the purpose of logrotate. Unless that bug has been fixed in your version, you should leave the restart stanza in the logrotate for configuring mailman. That the shunt queue is collecting digests seems weird. It's not surprising that the message object in the queue file is empty, that's by design. It seems like the digest process is happening at the same time as the restart. This shouldn't be a problem, but it might clarify things if you make sure the periodic digest delivery is offset from the midnight restart in the /etc/cron.d/mailman3 file. Eg # cron time is UTC, put stuff on desks at start of day JST # core sends mail 22 5 * * * mailman /opt/mailman3/.v/bin/mailman notify 22 6 * * * mailman /opt/mailman3/.v/bin/mailman digests --periodic (note 22:00 UTC is 07:00 JST). My only other comment on your mail is that I see that you do have multiple out slices. So that explains the case of the .pck.bak (in process) file being younger than a .pck file (waiting in queue). It's not unusual in your configuration. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 day, 7 hours

[MM3-users] Re: How to remove a nonmember from a list

by skenny＠scss.tcd.ie

Abhilash Raj wrote: > Could be, I am not sure which operation is it stuck at. Can you check logs to see > where is it breaking? Sure. I'm doing all this under Docker; below is what I see in /opt/mailman-web-data/logs/mailmanweb.log when I try to delete a nonmember via the web interface. Thediagnostics appear 30 seconds after I click on 'delete': ERROR 2020-04-09 20:35:51,482 19 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 421, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 416, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 720, in urlopen method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] File "/usr/lib/python3.6/site-packages/urllib3/util/retry.py", line 400, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/lib/python3.6/site-packages/urllib3/packages/six.py", line 734, in reraise raise value.with_traceback(tb) File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 421, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 416, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 96, in call headers=headers) File "/usr/lib/python3.6/site-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 533, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 646, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", line 38, in wrapper return fn(*args, **kwargs) File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line 943, in remove_role roster = getattr(the_list, '{}s'.format(role)) File "/usr/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 86, in nonmembers response, content = self._connection.call(url, data) File "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 119, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie The file /opt/mailman-web-data/logs/uwsgi.log contains just one line: [pid: 19|app: 0|req: 82/96] 172.19.199.5 () {46 vars in 1233 bytes} [Thu Apr 9 20:35:20 2020] GET /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie => generated 5583 bytes in 31411 msecs (HTTP/1.0 503) 5 headers in 180 bytes (1 switches on core 0) > Can you try doing the same with the REST API, just to verify if it is the Core which > has the issue or it is the web frontend. Using the REST API, I can successfully remove a named nonmember from the list. But I see the same pause-then-fail behaviour when I try to simply list all the nonmembers. My snippet of code can happily produce a listing of the members, but it gets stuck trying to list nonmembers, and then 30 seconds later it crashes out with exactly the same error messages as when I tried to delete a user in the web interface (see above). My piece of code appears below (II invoke it like this: docker exec -it mailman-core bash -c 'python3 /opt/mailman/local/probe.py scss-sysadmins(a)lists.scss.tcd.ie'). from mailmanclient import Client from mailmanclient import MailingList import sys my_list = str(sys.argv[1]) client = Client('http://172.19.199.2:8001/3.0', 'restadmin', 'restpass') this_list = client.get_list(my_list) print("\n\nMembers:\n-------------------------------------------------") for i in this_list.members: print(i) print("\nNonmembers:\n-------------------------------------------------") for i in this_list.nonmembers: print(i) Thanks again Stephen

5 years, 3 months

[MM3-users] Re: mail loops back to myself

by Mark Sapiro

On 6/13/25 01:59, Florian Sukup wrote: > > > On 6/13/25 01:58, Mark Sapiro wrote: > >> but I'm at a loss to understand the issue, unless your >> /etc/postfix/master.cf is missing an uncommented entry for lmtp like >> ``` >> lmtp unix - - y - - lmtp >> ``` >> > > I found it there, here is my master.cf: I realized after the fact that that probably wasn't the issue because it probably would have logged an error. > mailman unix - n n - - pipe > flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Is the last line a problem? It seems to be from mailman2. It's a Debian thing for an unsupported MM 2.1 process to deliver mail to Mailman. It doesn't do any harm if it's not referenced in main.cf. > Is there a possibility to debug in more detail? To find out when and > where it takes the wrong turn? I'm unable to see where this is going wrong. I think it is a Postfix issue, not a Mailman issue per se, and while we make a best effort to help with Postfix-Mailman integration issues we are not the primary support resource for Postfix which is the postfix-users(a)postfix.org mailing list. See https://www.postfix.org/lists.html for info on subscribing and posting. Also, since you are dealing with Debian packages, the primary support resource is Debian. See https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Abhilash Raj

Excerpts from Simon Liebold via Mailman-users's message of May 29, 2017 2:16 pm: > Am 28.05.2017 um 22:24 schrieb Mark Sapiro: >> 'Delete this message' is in the 'message' view. "Delete this thread" is >> in the 'thread' view. > > Now found the message view. Thanks. > >> HyperKitty requires Django<1.11. The comment in the requirements in >> setup.py implies this is only a django-haystack requirement >> >> "Django>=1.8", >> # Don't upgrade to 1.11 until django-haystack supports it: >> # https://github.com/django-haystack/django-haystack/pull/1499 >> "Django<1.11", >> >> but since it works for me with Django 1.10, you might want to try that. > > OK, I was still running an RC version. Silly me. > >> In particular, this looks like Django 1.11 bug >> <https://code.djangoproject.com/ticket/27975>. > > Which was closed in the release version that I initially upgraded to > (1.11.1). > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > You may have to do `python manage.py makemigrations` after adding a new INSTALLED_APPLICATIONS and before running `python manage.py migrate` Hope that helps! -- thanks, Abhilash Raj

8 years, 2 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

Hello Mark and everyone else, I made significant progress in that I got the web interface working. The file permissions were wrong for the /var/log/mailman3/web directory in that the web directory needs to be writable by www-data (the apache user), Also, the aliases in the Apache configuration needed to be changed to the following: Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /static/ /var/lib/mailman3/web/static/ Once I fixed these issues then I was able to successfully access the web interface and login. Now, I am able to access the web interface and I am able to navigate to all of the main links on the top of the main page including: Postorius. Lists, Domains, Bans, System Information, Users and Archives. My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: "Server error An error occurred while processing your request." Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" This email and my logs now complain about: "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ get() returned more than one EmailAddress -- it returned 3!" Also, I get the same errors after I create a new mailing list as well. I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! Thanks, Gordon

3 years, 5 months

[MM3-users] Re: changing the main template for subscriptions and more

by Mark Sapiro

On 2/1/22 12:40, Paul Paulchen wrote: > Hi Mark, > > thanks for your advice. Unfortunately we need some more clues. > First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman I do not know what the file layout is in the Docker container, so I can't verify paths. > Our version: > 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] > > We put an example footer.txt into the templates folder as you mentioned: > mailman3_core => var/templates/sites/de/list:member:regular:footer.txt > Mailman user can read them As I said, I can't give you an absolute path. If you can run `mailman info` in the container, that will show the location of mailman.cfg which may help Installing the template as you have should work if it's the correct path. > Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt The default templates are in the mailman/templates/ directory where the mailman/ directory is where all the Mailman core software is. Hopefully someone familiar with Docker and the Mailman Docker container can provide better information. -- 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] Re: Installing mailman 3

by Abhilash Raj

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

8 years

[MM3-users] Re: Mailman 3 localization

by Alexander Klotz

> I wanted to set it up, but the requirement is to use a free hosted > solution. (So transifex and crowdin are a no-go, they would be great to > get translations, especially crowdin looks very active in that regard) > I tried out zanata.org but it's extremely slow... > The other option at the time was pootle > (http://pootle.translatehouse.org) which doesn't offer hosting but some > folks at gnu had a customized instance set up, but they discontinued the > service. > > I searched for a translation service for a private project and found > weblate.org . They offer hosting (hosted.weblate.org) for open source > projects and it looks like a couple of people are using it. You need to > contact them if you want to set it up for an open-source project though > and I didn't want to invest in it without knowing what the end-result > would be... > > Since I'm also mainly interested in German translations for my own > installation, I opted to just use plain .po files and filed merge > requests against the repositories. Postorius has translations (not > perfect, but a start for the moderators that use my instance) included > by now but my merge request for core is still outstanding > https://gitlab.com/mailman/mailman/merge_requests/400/ > Since I don't use Hyperkitty, I didn't translate that. > Thanks for the reply, Simon! We were thinking of using plain .po-files too, however, we couldn't find the matching "src" folder in our installation, do you have any more details where it or the .po-files may also be located? Regards, Alex

7 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I think you have to open a new issue to modify the website for the mailman-suite git clone, it should be: git clone https://gitlab.com/mailman/mailman-suite.git El vie., 21 jul. 2017 a las 14:07, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Installing mailman-suite for web ui. I did this: > > (env) [mailman@localhost ~]$ git clone > https://gitlab.com/mailman/mailman-suite/ > Cloning into 'mailman-suite'... > error: RPC failed; result=22, HTTP code = 404 > fatal: The remote end hung up unexpectedly > > > but it returned an error, what should I do?? > > Thanks > > > > > > > > El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 10:29 AM, Rafael Mora wrote: >> > Can we modify the docs? >> > >> > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) >> > escribió: >> >> >> >> However, that said, the doc is wrong. The lines should be added to >> >> main.cf, not master.cf. See >> >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. >> >> >> That's what the above issue and associated MR are for. >> >> -- >> 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 > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Apple Mail encoding again

by tlhackque

On 21-Apr-22 13:09, Mark Sapiro wrote: > On 4/21/22 04:53, tlhackque via Mailman-users wrote: >> >> Note that MailMan is encapsulating a multipart/signed message in a >> multipart/mixed in order to append it's footer, and reports that it >> removed the signature part of the multipart/signed. This makes the >> signed message format invalid. So at least, MM3 needs to handle >> signed messages better: either include the signature or remove the >> signature headers (an unwrapping exercise to convert the message to >> unsigned)... Note that this can be recursive where a signed message >> contains a message/rfc822 part that contains a signed message, that.... > > This was an issue with Mailman's content filtering for the > mailmanusers(a)mailman3.org list. Pass types was: > > multipart > message/rfc822 > text > application/pgp-signature > > So the application/x-pkcs7-signature part was removed. I have just > updated Pass types to: > > multipart > message/rfc822 > text > application/pgp-signature > application/x-pkcs7-signature > > to not remove application/x-pkcs7-signature parts going forward. > That's what I expected to be behind the behavior. Thanks for fixing it on this list. But as I noted, it would be better if the application/*signature parts were automagically passed when a multipart/signed is present. Ideally those that correspond to the multipart/signed, but it's probably less work to allow them anywhere. I've seen variations of this misconfiguration on a number of lists, all of whose administrators had to learn by experience. Seems like a good case for Mailman becoming smart enough to do the right thing...

3 years, 3 months

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

by Bryan Loniewski

Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; +---------------+--------------+ | list_name | howManyBytes | +---------------+--------------+ | <snip> | 65535 | | <snip> | 65535 | | <snip> | 65535 | +---------------+--------------+ 3 rows in set (0.01 sec) So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:15 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 7:35 PM, Bryan Loniewski wrote: > $ /opt/mailman/mm/bin/mailman version > GNU Mailman 3.3.2 (Tom Sawyer) > > So, I'm running > 3.2. Any other advice on debugging the truncated data? The traceback indicates sqlalchemy is unpickling data whose type is PickleType. The only mailinglist columns which are PickleType are the legacy *these_nonmembers and topics. You could try invoking mysql on Mailman's database and doing SELECT list_name, accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, discard_these_nonmembers, topics FROM mailinglist; and look for the longest values to possibly identify the problem list and attribute. -- 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

3 years, 11 months

[MM3-users] Re: restricting public lists per virtual domain

by Stephen J. Turnbull

David Newman writes: > Awhile back Stephen Turnbull suggested a terminology guide that > included an MM3-specific definition of FQDNs. I think that Mailman should use the usual definitions, but sometimes we have more restrictive implementations. For example, although we store the case sensitive form of email addresses, some checks for equality of email addresses are case insensitive even though local parts can be case sensitive at some hosts. That can be surprising, although frequently it's what users expect. It's going to be hard to document all of these, but even listing some of them will probably help users diagnose issues for themselves, or suggest improvements. > > Also in an MM3 context, I think it would be useful to distinguish > between mail hosts and web hosts and domains (all in the general > Internet sense) and mail domains and sites (in the > MM3/Django/Postorious/Hyperkitty sense). Yes, this is really complicated. Web hosts aren't too bad, although often www.example.com will be a CNAME for example.com and configurations like that, but Internet mail is quite a mess, what with CNAME, MX, and PTR at least being involved, and if you are doing signatures, all the stuff for SPF, DKIM, DMARC, ARC and more, not to forget that if you're actually sending and receiving mail you need to worry about distinctions among SMTP, LMTP, and SUBMIT, and all of the SSL/TLS versions. *sigh* > Not sure I fully understand these distinctions yet, but I can take a > crack at it. Just list them under "this stuff is really weird, watch out for dragons lest you be toasted from behind". :-) Steve

3 years, 7 months

[MM3-users] Re: Social signup?

by Duane Raymond

Wow - thanks for the redirection on where to patch it and the first-cut code. I'll look into this in 2 weeks when I am able to focus on it. Cheers, Duane On Wed, 15 Mar 2023 at 16:18, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/23 05:08, Duane Raymond wrote: > > > > 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 > > > This is not what you want to do for this. The changes need to be in > django-mailman3, not postorius. I have attached a patch which might work > for you. I think it is good, but some of the wording is stuff that may > not be appropriate. See what you think. > > -- > 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 duane(a)fairsay.com >

2 years, 4 months

[MM3-users] Re: Urgent help needed...

by Simon Hanna

On 05/24/2018 06:21 PM, Darren Smith wrote: > Hello, > > This morning our Mailman 3/Hyperkitty/Postorius installation has become > unresponsive. When looking at the machine, postgres is pegging all 4 CPUs > on the machine. > > We did some digging in postgres, and here is the query that is causing > problems: > > "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE > hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY > hyperkitty_email.date ASC LIMIT 1;" > > We have found that it doesn't matter what mailinglist_id is being used. > > We have also found that this might be an issue with the LIMIT 1 - our > investigation is showing that using LIMIT 1 in postgres makes things > execute very differently than if you use a limit 2 or more, and that this > is probably what is going on. > > Basically, every time this gets called, it pegs an entire CPU for 20-30 > seconds. It appears to be called a LOT. > > So our users are getting 504 gateway timeouts right now. > > What has changed: > > We have been in the process of importing our 40 million archived emails > from our old mailman 2 archives. > > Questions: > > 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, > postorius, django - basically anything that might be calling this code, but > we can't find it. Does anyone know what generates this query? It looks like the query is to get the date from the last email for a mailinglist. AFAIK Hyperkitty checks this when new emails get it (maybe even during import) It could also relate to the "active" state of mailinglists...

7 years, 2 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 08:14, Eggert Ehmke via Mailman-users wrote: > I edited this file: > venv/lib/python3.9/site-packages/mailman/commands/cli_members.py > > The content at line 107ff is: > #patch of Mark Sapiro > # if email_only: > if email_only or not address.display_name: > print(address.original_email, file=outfp) > else: > # print(formataddr((address.display_name, address.original_email)), file=outfp) > print(f'{address.display_name} <{address.original_email}>', file=outfp) > > This file is actually executed when I call mailman members. I verified this by uncommenting the first (old) print line. Now each address is printed twice (as expected), with the utf8 code in both lines in case of umlauts. In that case the address.display_name value is the RFC 2047 encoded name. One way this can happen is if the subscribe was via email prior to Mailman 3.3.3. See https://gitlab.com/mailman/mailman/-/issues/802. You could try something like this to fix these. ``` mailman shell 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. >>> um = getUtility(IUserManager) >>> from email.header import decode_header, make_header >>> for address in um.addresses: ... decoded = str(make_header(decode_header(address.display_name))) ... if decoded != address.display_name: ... address.display_name = decoded ... print(f'Fixed {decoded}') ... >>> # while you're at it do users too. >>> for user in um.users: ... decoded = str(make_header(decode_header(user.display_name))) ... if decoded != user.display_name: ... user.display_name = decoded ... print(f'Fixed {decoded}') ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

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

by Danil Smirnov

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? 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, 4 months

[MM3-users] Re: Server 500 error for just one list, just one page

by Mark Sapiro

On 6/28/20 4:05 PM, kelly.close(a)lrewater.com wrote: > I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). Neither do I, but you want to look in Mailman core's mailman.log and Django's log. mailman.log is in a directory with others including smtp.log and subscribe.log. If you don't know where to find that, look in the output from `mailman conf`. The first thing to look for is [mailman] layout: which will have a value like `fhs`, `dev`, `here` or `local`. then look at [paths.xxx] log_dir: where xxx is the layout value, and if that includes $var_dir, look at [paths.xxx] var_dir: For the Django log look in settings_local.py and settings.py or whatever they're called in your case for LOGGING['handlers']['file']['filename'] > So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… That page should be the same as <https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org…>. Can you go there? Where are you finding that link? What postorius version is this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] mailmanweb/django?: too many postgresql DB connections

by api＠egartech.com

Hello, I'm migrating from mailman 2.1 to the latest version (3.3.9) on Almalinux 9 (python 3.19, postgresql 13.16). Have followed the instructions here https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install to perform a clean install on a new VM. Everything seems to be working (well, I just created one list and doing some basic tests). What I have noticed is hundreds of PGsql connections from mailmanweb. Once mailmanweb service is started there are new non-stop DB connections requests (from Django I guess), here is just 1 second from PGsql log: 2024-10-10 12:15:37.112 EDT [3217] DEBUG: forked new backend, pid=3747 socket=10 2024-10-10 12:15:37.113 EDT [3217] DEBUG: server process (PID 3746) exited with exit code 0 2024-10-10 12:15:37.318 EDT [3217] DEBUG: forked new backend, pid=3748 socket=10 2024-10-10 12:15:37.318 EDT [3217] DEBUG: server process (PID 3747) exited with exit code 0 2024-10-10 12:15:37.523 EDT [3217] DEBUG: forked new backend, pid=3749 socket=10 2024-10-10 12:15:37.524 EDT [3217] DEBUG: server process (PID 3748) exited with exit code 0 2024-10-10 12:15:37.728 EDT [3217] DEBUG: forked new backend, pid=3750 socket=10 2024-10-10 12:15:37.729 EDT [3217] DEBUG: server process (PID 3749) exited with exit code 0 2024-10-10 12:15:37.934 EDT [3217] DEBUG: forked new backend, pid=3751 socket=10 2024-10-10 12:15:37.935 EDT [3217] DEBUG: server process (PID 3750) exited with exit code 0 Few minutes later there are around 300 dead (TIME_WAIT) connections to port 5432 like these: tcp 0 0 127.0.0.1:33728 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40392 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:50860 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40254 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40218 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40110 127.0.0.1:5432 TIME_WAIT I'm totally unfamiliar with Django so not sure where even to look, but that doesn't looks right to me. Thanks

9 months, 3 weeks

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

by David Newman

On 1/14/22 4:54 PM, Mark Sapiro wrote: > On 1/14/22 11:56 AM, David Newman wrote: >> >> I created a pending subscription request on a test list. Here is the >> text I'm using in a file called 'list:admin:action:subscribe.txt' >> (minus the rows of hypens): >> >> ---------- >> >> >> As list administrator, your authorization is required for a mailing >> list subscription request approval: >> >> For: $member >> List: $listname >> >> At your convenience, visit: >> >> https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ > > This looks like a Mailman 2.1 URL. Are you sure you don't want something > like > > https://${domain}/mailman3/lists/${short_listname}.${domain}/ Yes. The server redirects MM3-style requests to MM2.1 URLs. I need to determine why, but that may be a different issue than the templates one. There's nothing obvious in this vhost's nginx config that would generate the redirect. Will check, if I can't resolve this I'll open a different thread. > >> >> to approve or deny the request. >> >> ---------- >> >> Instead the message that goes out at midnight daily reads like this: > > > That's a different message. It is sent from the `mailman notify` command > run by cron. It's built from the list:admin:notice:pending template. OK, wrong template then. > >> >> On successive nights I have placed copies of the >> 'list:admin:action:subscribe.txt' file above in these locations: >> >> mm/var/templates/lists/test.lists.domain.tld/en > > I hope you mean > > /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en Yes > >> /opt/mailman/mm/var/templates/site/en > > > Either of those should work. The lists one will take priority over the > site one for that list. > > >> and then in Postorius, with the same contents as above. > > If you set a template in Postorius, it takes priority. If you later > decide you want to use one in /opt/mailman/mm/var/templates/ you have to > delete the postorius one. > > >> The file versions are owned by the mailman user, and have 0644 >> permissions. Not sure this is necessary but I've restarted the >> mailman3 and mailmanweb services each time after a change. >> >> There is no sign of trouble in the MM3 or web logs. The only thing I >> see is in the Postfix log, where the shorter and less helpful message >> goes out each night. I don't see anything in the template docs about >> this. >> >> Questions: >> >> 1. What to do to get the custom message working? > > > 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. > > >> 2. Is there a way to trigger a subscribe reminder for one list only? > > > If by subscribe reminder you mean the `list:admin:action:subscribe.txt` > message, yes that's the above list setting. If you mean the one sent > from the `mailman notify` command, see `mailman notify --help` for the > options. You can specify one or more lists (default is all lists) via > options and put them in your cron. > > >> Asking because there are other lists on this server with other >> requests pending, and I don't want to bother other moderators with >> multiple reminders per day. Not a big deal, but it would be nice to >> test this with one list rather than waiting up to 24 hours after each >> change. > > > 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' with these contents (minus the hyphens top and bottom): ---------- The $listname list has $count moderation requests waiting. $data At your convenience, visit: https://${domain}/mailman3/lists/${short_listname}.${domain}/ to approve or deny the request. ---------- 2. Restarted the mailman3 and mailmanweb services 3. As the mailman user, ran the command 'mailman notify -l test.lists.domain.tld -v' This generated an email message but its contents were the same as in my previous post: ---------- The test(a)lists.domain.tld list has 1 moderation requests waiting. Held Subscriptions: User: letmein(a)domain.tld Please attend to this at your earliest convenience. ---------- 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. For now, though, I'm looking to get this customization working. Thanks. dn

3 years, 6 months

[MM3-users] Re: Authenticating against Hyperkitty's DB

by Abhilash Raj

On Thu, Jul 25, 2019, at 12:36 PM, Marvin Gülker wrote: > Hi, > > inspired by the question about LDAP, I want to ask a related > question. We're currently thinking about adding a wiki to our small OSS > project, and requiring users to have multiple accounts for the same > project is nonsense. We don't have LDAP set up yet, but we do have a > running Mailman 3 installation, including Hyperkitty. Thus I thought > about whether it's possible to just write some glue script that > authenticates against the user information in Hyperkitty's database. > Creating an account for Hyperkitty would then be sufficient to get > access to the wiki. > > Could someone give me a hint where and in what format Hyperkitty stores > the user information into its database? So, Hyperkitty itself doesn't concern with authentication and it is handled by django-allauth, which itself hooks into the higher level authentication API provided by Django. Django allows for pluggable Authentication backends, that it can use to authenticate requests. You can read more about it here[1]. We use Django-allauth as an authentication backend. You can use the higher level `django.contrib.auth.authenticate()` [2] function with right values in a Python script running in the same virtualenv to authenticate the user to your wiki. [1]: https://docs.djangoproject.com/en/2.2/topics/auth/default/ [2]: https://docs.djangoproject.com/en/2.2/topics/auth/default/#django.contrib.a… > > Marvin > > -- > Blog: https://mg.guelker.eu > _______________________________________________ > 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

[MM3-users] Re: Migrate from mysql to postgresql

by Bjoern Franke

Hi, >> >> I tried to convert it with pgloader, but some identifiers had to be cut off: >> _address_id); >> 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner >> idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e >> wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac >> gekrzt > > > > I suspect the issue is due to the way Mailman supports different > databases via SQLAlchemy. The bottom line is the table and column > specifications are based on the Mailman database models, but are > database specific. Now with the via pgloader converted db I get: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context context) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 450, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) FEHLER: Operator existiert nicht: character = uuid LINE 4: WHERE "user"._user_id = 'd254e5dc-188a-48de-8b99-3cbe81155c1... ^ HINT: Kein Operator stimmt mit dem angegebenen Namen und den Argumenttypen überein. Sie müssen möglicherweise ausdrückliche Typumwandlungen hinzufügen. [SQL: 'SELECT count(*) AS count_1 \nFROM (SELECT "user".password AS user_password, "user".id AS user_id, "user".display_name AS user_display_name, "user"._user_id AS user__user_id, "user"._created_on AS user__created_on, "user".is_server_owner AS user_is_server_owner, "user"._preferred_address_id AS user__preferred_address_id, "user".preferences_id AS user_preferences_id \nFROM "user" \nWHERE "user"._user_id = %(_user_id_1)s) AS anon_1'] [parameters: {'_user_id_1': UUID('d254e5dc-188a-48de-8b99-3cbe81155c11')}] Jun 14 12:30:43 2018 (22147) 127.0.0.1 - - "GET /3.0/users/279578694160539064315719588335836290065/addresses HTTP/1.1" 500 59 root@srv20 /etc/mailman3 # > If I were doing this, I would dump the data from MySQL, but rather than > using the CREATE TABLE queries from the dump, I would let Mailman create > a new PostgreSQL database and then just load the existing tables from > the MySQL dump. Unfortunately that did not work due to some missing indexes. Regards Bjoern

7 years, 1 month

[MM3-users] Re: update_index

by Darren Smith

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, 3 months

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

by Stephen Turnbull

Christian writes: > 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record This says it's parsing your mail session and using the MAIL FROM. > 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]. At least Google is seeing the mail arrive from the expected IP address. > To best protect our users from spam and > 550-5.7.26 phishing, the message has been blocked. > Could the hard fail policy be implicated in the gmail rejection? It certainly could. However I would expect the DSN to say "because of the hard fail specification we are rejecting your email" in that case. This looks like a Gmail policy to me. > Other than readdressing my server, is there anything else I can do? I don't think readdressing is going to help unless you're referring to the PTR issue mentioned below. I see the same SPF record you have described before: lists.ccalternatives.org descriptive text "v=spf1 a mx ip4=192.46.218.224 -all" so I'm not sure what is going on with Odhiambo's lookup. However, there is an error (the '=' after ipv4 should be ':'), and it has some other problems: 1. the 'mx' mechanism is a no-op because lists.ccalternatives.org has no MX record. 2. the PTR for 192.46.218.224 points to mail.ccalternatives.org, not to lists.ccalternatives.org. Neither should cause an SPF check to fail but they make the check more expensive. I would simplify your TXT record to "v=spf1 ip4:192.46.218.224 -all" because the 'a' mechanism isn't working and the 'mx' mechanism is a no-op. That's really all you need. Steve

2 years, 2 months

[MM3-users] Re: Ready to try installation: use "normal" install or docker.

by Abhilash Raj

On Tue, Aug 1, 2017, at 09:50 AM, Tom Browder wrote: > On Tue, Aug 1, 2017 at 12:28 Abhilash Raj <raj.abhilash1(a)gmail.com> wrote:>> Hi Tom, > .... >> On Tue, Aug 1, 2017, at 07:54 AM, Tom Browder wrote: >> > I'm leaning toward installing using the docker method but I would>> > appreciate any recent thoughts about which method to choose. >> >> It really depends on what way you want to go, container images will be>> much less hassle to use right now, mostly because all the dependencies>> are bundled in and the moving parts are already configured to work with>> each other. > > Abhilash, thanks for the response. > > My goal is to use the installation in production immediately (production meaning using some interested friends as testers before opening lists to "real" subscribers).> > If I understand properly, the docker way will be a good path to do that and it should make my volunteer maintenance life easier in the future, too.> > Does that sound reasonable? While other non-developers would be able to tell you more about how easy it is to administer these container images, I think I have made them easy easy as possible to deploy without having to worry about inner workings. Unless ofcourse you want something more customized, it should work Ok for you. I am planning to release some new bugfixes and enhancements very soon, maybe today or tomorrow depending on when can I get some time. That release should be a significant improvement over the current one with ease-to-use factor. -- thanks, Abhilash Raj

8 years

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Abhilash Raj

On Thu, Oct 26, 2017, at 11:23 AM, Andrew Hodder wrote: > I have an odd one, my Hyperkitty is functionally working fine (archived > several lists without issue, can login/out), however I must have done > something wrong during it's setup as it's layout is completely broken > (and > it keeps throwing Example.com up in the top-left corner). You need to change SITE_ID in your Django's configuration to point to your domain name you want to be show there. Default is set to `example.com` which corresponds to SITE_ID=1 in the Django's configuraiton. How to find the SITE_ID of your domain? This is rather no-so-nice right now, you will basically have to go to the admin console (/admin/) and login as admin. Then you visit `/admin/django_mailman3/maildomain/` and you should see your domain there. Clicking on it will how your it's id in URL bar, like /admin/django_mailman3/maildomain/2 or something. I understand this is rather difficult thing to do, there is an issue open to make this information visible in the UI. Ideally, SITE_ID is sequential, so if you have only one domain, it is most probably 2. > > See attached. > > I'd run into a similar issue with Postorious when I first set it up, but > I > can't recall what fixed it. Any ideas to what needs correcting? 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 9 months

[MM3-users] Re: Moderation Action Changed After Import

by Mark Sapiro

> > I can't confirm what was set on the old MM2 list as it is no longer > accessible. I am just going on the word of the List Owner. My opinion is > that the moderation for those list members were set to Reject on the > previous MM2 list. I am mainly interested to see if you know of this > happening to anyone else and/or perhaps there is an existing bug that > could impact the moderation settings of imported MM2 lists. If you have the config.pck and any MM 2.1 installation, you can get all the info from the config.pck. For example > /path/tp/mm2.1/bin/dumpdb /path/to/config.pck|grep member_moderation_action will show the setting with 0 = Hold, 1 = Reject and 2= Discard. Finding which members are moderated is more difficult as there is a dictionary named user_options with keys = to email addresses and integer values and the integer is a bit field defined as follows (from Defaults.py) > # Bitfield for user options. See DEFAULT_NEW_MEMBER_OPTIONS above to set > # defaults for all new lists. > Digests = 0 # handled by other mechanism, doesn't need a flag. > DisableDelivery = 1 # Obsolete; use set/getDeliveryStatus() > DontReceiveOwnPosts = 2 # Non-digesters only > AcknowledgePosts = 4 > DisableMime = 8 # Digesters only > ConcealSubscription = 16 > SuppressPasswordReminder = 32 > ReceiveNonmatchingTopics = 64 > Moderate = 128 > DontReceiveDuplicates = 256 However, to address your concern, As far as I know, import21 is doing the right thing. If you want to send me the config.pck you imported, I can try to verify that. -- 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] How to delete non-users

by Allan Hansen

Hi all, This is a bit of an emergency: I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. For individuals I have been able to delete their non-membership and they then could subscribe properly. I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). Can anyone help me find out how to a. delete all non-members of all my lists b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) Any help with this is appreciated. Yours, Allan I'm still at Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] My system used to be kept up to date by EMWD, but since Brian died have not been able to get it updated, and I'm too scared (from my attempts at installing MM3) to attempt it myself. If the above can only be solved via an update, I'd appreciate a referral.

2 years, 10 months

[MM3-users] Re: Moderated unsub requests are not provided by mailman3 service

by Joachim Schrod

Mark Sapiro writes: > On 11/29/24 4:47 PM, Joachim Schrod wrote: > > > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > > both on Debian 11 (bullseye). > > > > I know that this is out of date; thus a definitive info "this is fixed > > by now" is quite OK for me. (Debian upgrade is planned as the next > > action after getting Mailman3 to work for that use case.) > > Yes, this is fixed. Thanks for the information that it's fixed in Postorius 1.3.6; that information is a great help, it means that I don't need to spend more time on debugging resolved issues. I tried to gather data if an update to Debian 12 (bookworm) would help. But packages.debian.org is not helpful at all, for me. I know that this is beyond the realm of this mailing list, but perhaps someone here has that information and can supply it: Debian 12 (bookworm) package mailman3-web has the version "0+20200530-2.1". This is supposed to be from some source package mailman-suite that is a salsa project that I don't grok at 1st and 2nd sight. Can anybody please provide me with information what versions of mailman3 core and mailman3-web are in this package; i.e., in Debian 12 (bookworm)? Sorry, but I'm not versed enough to understand the information about Debian packages that my search delivers. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

8 months

[MM3-users] Strange behaviour when SSL (https) is activated

by Stephen J. Turnbull

François TOURDE writes: > But if I activate SSL on the web server, I'm unable to login. I go to > the /admin, prompted for the user/pass, and got a Firefox error page > saying "Échec de la connexion sécurisée". According to Google Translate, this means "Secure connection failed", which seems to be a webserver problem, not a Mailman problem. Recent Firefox is very picky: it wants a proper certificate (although free certificates such as CertBot will do), and it won't accept SSL or TLS versions less than 1.2. Make sure that your webserver is properly configured to use TLS >= v1.2, and has a properly configured certificate. > [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) > Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) > OSError: write error > [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 > bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => > generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes > (1 switches on core 1) This suggests that you're seeing a variant on the "redirect from HTTP to HTTPS loses POST data" problem. The description of the problem is different and I have no idea what your configuration is, but if the advice (not the problem description) looks familiar the following post may be of help: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Any hint appreciated ;) More information about your webserver and Django configurations would be useful.

3 years, 6 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Paul Arenson

Well more to report. CPanel says: "Thanks so much for reaching out. I know the mailman upgrade is definitely something many people are looking forward to, but it’s not something we’re able to support at this time. As uncomfortable as it is, the only current option would be to install MM3 and see what breaks. Since we have a minimum requirement for our consideration of their software (being able to migrate people in place), we haven’t done any testing, so it’s not possible for us to say what would or wouldn’t work. Unfortunately you will have to make the best call for your customers, but without our testing I have to advise against trying a manual install of Mailman." There is still the possibility of Discourse (suggested by a member of this forum). But it would require a hosted account somewhere as to host it oneself, you need VPS and something called Docker. I tried a free version of it on Disroot a while ago and it seemed ok, but the Disroot collective was very slow responding, plus you had to see other people's conversations. So while I wait for Mailman 3 on CPanel, this might be another solution. Thanks. PS... I am 66 and have lived outside the US since the age of 27. The language has begun to pass me by. The CPanel rep's use of REACHING OUT is a case in point. When I was in the US, you reached out to someone in trouble, Since I am in trouble, I do to feel I am reaching out to CPanel. I guess that is the nature of language change though.

6 years, 10 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210216 16:24]: > But if the admin should respect the DBS (disabled by subscriber) > setting, DBS|DBA (disabled by admin) is logically equivalent to DBS. > Are there use cases where the admin does not want to repect the > subscriber's choice, and enables it anyway? What are they? To support a user saying "I have disabled myself and can't re-enable it, can you help me please". So basically when acting on-behalf of the user. > > Or while importing from another server, and there are people who > > have receiving mails disabled, this is the state that could be used > > for it. > > Why wouldn't they get the exact state from the original server? Or do > you mean from a non-Mailman server? For example, however there are no more imports from yahoogroups (that's why I started using mm3). > This is possible. If it occurs less than once in a million years, > it's "too unimportant" to even think about.[2] Have you actually done > this, or know anybody who has? I'm happy to have forgotten much of my past experience, and for "my" archives I hope to be soon able to switch from subscriber-only to authorized-user-only, so doesn't matter too much for me anymore. Otherwise, I think the good thing of this discussion is that we have now clearly written up the current state machine. Otherwise, I just wrote up my favourite but if it stays the current way, well, that's ok of course as well. :) Thanks for your answers and time. Andi

4 years, 5 months

[MM3-users] Re: 12/24 hour clock ?

by Per Jessen

Mark Sapiro wrote: > On 11/28/20 7:18 AM, Per Jessen wrote: >> Hi all >> >> at openSUSE we have recently migrated to mailman3, and we seem to be >> having a couple of teething issues: >> >> a) hyperkitty and postorius both seem to insist on using a 12 hour >> clock format, no matter what the user has set. Is there a way of >> changing it system-wide ? > > > This is a Django setting. Try > > TIME_FORMAT = 'H' > > in settings_local.py. See > https://docs.djangoproject.com/en/3.1/ref/settings/#time-format and >https://docs.djangoproject.com/en/3.1/ref/templates/builtins/#std:templatef… Thanks, will have a look. >> b) overriding the default set of footers - despite having set the >> template "list:member:regular:footer" to empty for a specific list, I >> am still getting the default footers attached. > > > How did you set the template to empty? I edited it in list settings under Templates, at first really just leaving it empty, then actually writing "empty" :-) > it works for me in Postorius from the HEAD of the gitlab branch and > should work with any Postorius >= 1.3.0 > > Note that when you set a template in Postorius, it sets the URI in > Mailman core for that template to > https://<HOST>/<PATH>/api/templates/list/<LIST-ID>/<TEMPLATE-NAME> > where the https://<HOST>/<PATH> part is the Django setting for > POSTORIUS_TEMPLATE_BASE_URL. Is that URI accessible from the Mailman > core host machine? I'll have to check, I only do the list admin, I don't maintain the installation. -- Per Jessen, Zürich (2.2°C) Member, openSUSE Heroes

4 years, 8 months

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

by Mark Sapiro

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.… The `accept` action is processed and ultimately we get to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… and that in turn is doing the DELETE at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.… 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. > sometimes the log (mailmansuite.log) show us this error That too is from the gunicorn worker timing out and being killed. -- 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] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 02:30, MegaBrutal via Mailman-users wrote: > On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > >> so it is saying there is only one choice for sender which I think means >> there is only one address associated with your login. That still doesn't >> explain why it thinks you're not a list member. >> > > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries > you recommend to run to get to see what's happening under the hood? Not offhand. What is the exact email address that you are logging on to the web UI with. Does it match exactly with the address of a list member or are there mixed-case differences? You might try an interaction like this: ``` mailman-web shell Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_mailman3.lib.mailman import get_mailman_client >>> client = get_mailman_client() >>> list_id = 'test.example.com' # your actual list_id >>> rest_list = client.get_list(list_id) >>> email = 'user(a)example.com' # your actual email >>> member = rest_list.get_member(email) >>> member This should print something like <Member 'user(a)example.com' on 'test.example.com' with role 'member'> ``` This is exactly what HyperKitty is doing except in your case rest_list.get_member(email) is throwing a ValueError exception instead of returning the member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

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

by Mark Sapiro

On 11/22/20 1:22 AM, Torge Riedel wrote: > > I like to ask what to do with other packages when upgrading mailman. I > noted, that after upgrading mailman, all requirements are fulfilled, but > a lot updates are available: > > (venv) mailman@basis2:~/core$ pip3 list --outdated > Package Version Latest Type > ------------------- ------- ------ ----- > aiosmtpd 1.2 1.2.2 sdist > alembic 1.4.2 1.4.3 wheel > atpublic 1.0 2.1.1 sdist > dkimpy 1.0.4 1.0.5 sdist > dnspython 1.16.0 2.0.0 wheel > flufl.i18n 2.0.2 3.1.3 sdist > flufl.lock 3.2 5.0.3 sdist > idna 2.9 2.10 wheel > importlib-metadata 1.6.1 2.0.0 wheel > importlib-resources 2.0.1 3.3.0 wheel > passlib 1.7.2 1.7.4 wheel > PyMySQL 0.9.3 0.10.1 wheel > requests 2.23.0 2.25.0 wheel > SQLAlchemy 1.3.17 1.3.20 wheel > urllib3 1.25.9 1.26.2 wheel > zipp 3.1.0 3.4.0 wheel > zope.component 4.6.1 4.6.2 wheel > zope.event 4.4 4.5.0 wheel > zope.interface 5.1.0 5.2.0 wheel > > Should I update them (regularly) or may I break something in mailman? In some cases and at some times, Mailman itself specifies a version <= something for a dependency. There have been issues where an upgraded dependency is not compatible with current Mailman. You can look at the install_requires section of setup.py to see if there are any specific version requirements, but this is not fool proof. For example, flufl.lock 5.0 broke Mailman core (See https://gitlab.com/mailman/mailman/-/issues/754) This was fixed in core version 3.3.2. Thus, If Mailman is working with the set of installed dependencies that you have and all of them satisfy >= requirements in setup.py, it's probably safest to leave them as is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman 3 localization

by Simon Hanna

> We would like to contribute further german translations, since there > are still some parts missing, e.g. in the postorious interface. Would > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > be the right place to do so, so that everybody could use our > translations? > > If there are other areas in which you could use our help, please let > us know. > > Regards, > Alex I wanted to set it up, but the requirement is to use a free hosted solution. (So transifex and crowdin are a no-go, they would be great to get translations, especially crowdin looks very active in that regard) I tried out zanata.org but it's extremely slow... The other option at the time was pootle (http://pootle.translatehouse.org) which doesn't offer hosting but some folks at gnu had a customized instance set up, but they discontinued the service. I searched for a translation service for a private project and found weblate.org . They offer hosting (hosted.weblate.org) for open source projects and it looks like a couple of people are using it. You need to contact them if you want to set it up for an open-source project though and I didn't want to invest in it without knowing what the end-result would be... Since I'm also mainly interested in German translations for my own installation, I opted to just use plain .po files and filed merge requests against the repositories. Postorius has translations (not perfect, but a start for the moderators that use my instance) included by now but my merge request for core is still outstanding https://gitlab.com/mailman/mailman/merge_requests/400/ Since I don't use Hyperkitty, I didn't translate that. cheers, Simon

7 years, 1 month

[MM3-users] New problem on new installation of Mailman

by Brian Carpenter

I am just about done with installing Mailman 3 on a new Debian 10 server and when I go to run ./mailman-post-update, I am running into the following error: ./mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 10, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 377, in execute django.setup() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/registry.py", line 91, in populate app_config = AppConfig.create(entry) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/config.py", line 90, in create module = import_module(entry) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/__init__.py", line 11, in <module> from haystack.utils import loading File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/utils/__init__.py", line 9, in <module> from django.utils import six ImportError: cannot import name 'six' from 'django.utils' (/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/__init__.py) I assume it has something to do with Haystack. Suggestions for a fix? Thanks, Brian

5 years, 1 month

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

by Abhilash Raj

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, 3 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Mark Sapiro

On 10/15/20 2:07 AM, Onyeibo Oku wrote: > > In the meantime, I moved to option #3 (recommended for production). > I hit a grey area when setting up the virtual environment. At > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, > I see: > > $ cd /opt/mailman > $ python3 -m venv venv > > The documentation imply that a 'user' creates the virtual environment > but is not explicit about that 'user'. The user can be any user you want. I use `mailman` on my production installations and `mark` on my development installation. The key is that user should be set as owner of /opt/mailman and then creating the venv and subsequent steps are all done as that user. > (1) Is it better to have a dedicated user (say 'mailman') then use that > while following the docs? I see a lot of docs referring to a 'mailman' > user. Installing mailman3 from distribution repository introduced a > 'mailman' user to my box (with special UID). There has to be reasons > for that. Yes, a dedicated Mailman user is best. > (2) Should the setup proceed with 'root'? (why do I get the feeling > that this is not the design?) No. setup should proceed as the Mailman user. > (3) How about using an already existing local user? What are the > implications? That's OK, but there are potential security implications due to the fact that the Mailman processes running as that user have access to all that user's non-mailman stuff. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Upgrading packages

by Mark Sapiro

On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > All packages were upgraded fine. I applied the patch to > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py It shouldn't have been necessary to apply any patch. The head of the GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > to change the mistune import line. When I run now > mailman-web migrate > I get: > *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration > graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* > *To fix them run 'python manage.py makemigrations --merge'* > > However, when I run the suggested command as: > $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- > merge > No conflicts detected to merge. There's something strange here. If you look at the migrations at the head of the gitlab branch at https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/migrations, you'll see that migration 17 is named 0017_alter_emailtemplate_language.py, not 0017_auto_20220628_1132. I suggest comparing the content of your postorius/migrations/ directory with the GitLab head and resolving any differences. > Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my > production system. Would be nice to shed some light on this. I'm guessing at some point you installed something which required you to manually make this migration and that produced this conflict. Do you have both 0017_alter_emailtemplate_language.py and 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, probably just removing 0017_auto_20220628_1132 will fix this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

Hi. I have fixed my RO database issue. Thank You for help, Abhilash. It was 100% my stupid fault. I had issues with "django-admin". If I ran manage.py it works correct, if I run django-admin - it not: only basic commands. I did not find way how to give correct environment. Then I found on some notes, that manage.py does exactly the same what django-admin does. So I made work around : I had created /usr/local/bin/django-admin to my project file manage.py and it started to work. Later I installed mailman from 0 under another user, and I forgot about that sym link. So why because database was Read Only. It had simply leaking write privileges to database file. Understandable, because owner was another user... > On 6 Sep 2019, at 00:20, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:49 PM, Ugnius wrote: >> >> Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. >> Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple >> writable. > > I think your problem about locked database might be solved. Like I mentioned, it is possible that those two running server could be stepping over each other toes. > > After removing the "runserver" process, I think you shouldn't fall into anymore of those locking issues. > > FWIW, it is also highly recommended to not use sqlite for any production use cases. Either postgres or mysql is preferred. > >> SQLite version 3.16.2 2017-01-06 16:32:41 >> Enter ".help" for usage hints. >> >> BR >> Ugnius >> >>> On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >>>> >>>> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? >>> >>> No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. >>> >>> The doc mentions that it is "development" server[1][2]. >>> >>> [1]: # Run the Django's "development" server at localhost:8000 >>> [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project >>> >>> Perhaps it should be more descriptive about what does it mean. >>> >>>> >>>>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> >>>>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>>>> >>>>> You only need one of those, since they both do the exact same thing. Please remove >>>>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>>>> >>>>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>>>> May mailman processes are next: >>>>>> >>>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>>>> >>>>>> Looks like there are no double. Nothing more is running. >>>>>> >>>>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> >>>>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>>>> >>>>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>>>> $ sudo pip3 install mailman >>>>>>> $ sudo pip3 install postorius >>>>>>> $ sudo pip3 install hyperkitty >>>>>>> $ sudo pip3 install mailman-hyperkitty >>>>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>>>> >>>>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>>> >>>>>>> >>>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>>> > Hi. All the project installation is under the same user / path and >>>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>>> > I have found work around - it is possible to change list as private in >>>>>>> > "admin" page. >>>>>>> > I started to get issues with runjobs after I have created couple of >>>>>>> > new lists with "no archive" option. >>>>>>> >>>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>>> >>>>>>> > >>>>>>> > If as owner user from project home I run: >>>>>>> > >>>>>>> > django-admin mailman_sync >>>>>>> > >>>>>>> > Traceback (most recent call last): >>>>>>> > File >>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>>> > line 84, in _execute >>>>>>> > return self.cursor.execute(sql, params) >>>>>>> > File >>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>>> > line 383, in execute >>>>>>> > return Database.Cursor.execute(self, query, params) >>>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>>> > >>>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>>> > END TRACEBACK >>>>>>> > >>>>>>> > I did not find information how to fix this. It was worked without errors >>>>>>> > before. >>>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>>> > to work. >>>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>>> > again. >>>>>>> > I did not check other jobs, but I think what is related to database, >>>>>>> > will get errors. >>>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>>> > >>>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>>> > I have returned this database file back, postorius started to work >>>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>>> > only". >>>>>>> > Please help me how to fix this issue. >>>>>>> > _______________________________________________ >>>>>>> > 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) >>>>>> >>>>>> >>>>> >>>>> -- >>>>> thanks, >>>>> Abhilash Raj (maxking) >>>>> >>>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

5 years, 10 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace From: with list address and 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 > _______________________________________________ > 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, 6 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 11:00, Jered Floyd wrote: > > These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! For me, on a test installation with SITE_ID = 0, this only occurs at https://example.com/accounts/social/connections/ Other URLs such as https://example.com/accounts/password/change/ and https://example.com/accounts/email/ do not throw this exception. Here's the code: ``` def get_current(self, request=None): """ Return the current Site based on the SITE_ID in the project's settings. If SITE_ID isn't defined, return the site with domain matching request.get_host(). The ``Site`` object is cached the first time it's retrieved from the database. """ from django.conf import settings if getattr(settings, "SITE_ID", ""): site_id = settings.SITE_ID return self._get_site_by_id(site_id) elif request: return self._get_site_by_request(request) raise ImproperlyConfigured( 'You\'re using the Django "sites framework" without having ' "set the SITE_ID setting. Create a site in your database and " "set the SITE_ID setting or pass a request to " "Site.objects.get_current() to fix this error." ) ``` I tried patching it from ``` if getattr(settings, "SITE_ID", ""): ``` to ``` if getattr(settings, "SITE_ID", None) is not None: ``` but that's even worse. It throws a bunch of "django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist." errors. Somehow, get_current is being called without a request object in the cases where it fails. -- 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: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 15:42, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>>> >>>> The server runs power-mailinabox, which uses Postfix indeed. All my >>>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>>> on port 465. Actually, this message is sent via that server too. >>>> So it's clear to me that MM3 is not authenticating for some reason. >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log The /etc/mailman3/mailman3-web.py file contains inter alia these lines: # Set default domain for email addresses. EMAILNAME = 'fast.za.net' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root@{}'.format(EMAILNAME) fast.za.net was giesler.za.net before, so I changed it.

1 year

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: > > I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. The doc mentions that it is "development" server[1][2]. [1]: # Run the Django's "development" server at localhost:8000 [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project Perhaps it should be more descriptive about what does it mean. > > On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> >> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >> >> You only need one of those, since they both do the exact same thing. Please remove >> whatever is running the "python manage.py runserver" part and only use uwsgi. >> >> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>> May mailman processes are next: >>> >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>> >>> Looks like there are no double. Nothing more is running. >>> >>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> __ >>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> >>>>>> >>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>> > Hi. All the project installation is under the same user / path and >>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>> > I have found work around - it is possible to change list as private in >>>>>> > "admin" page. >>>>>> > I started to get issues with runjobs after I have created couple of >>>>>> > new lists with "no archive" option. >>>>>> >>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>> >>>>>> > >>>>>> > If as owner user from project home I run: >>>>>> > >>>>>> > django-admin mailman_sync >>>>>> > >>>>>> > Traceback (most recent call last): >>>>>> > File >>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>> > line 84, in _execute >>>>>> > return self.cursor.execute(sql, params) >>>>>> > File >>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>> > line 383, in execute >>>>>> > return Database.Cursor.execute(self, query, params) >>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>> > >>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>> > END TRACEBACK >>>>>> > >>>>>> > I did not find information how to fix this. It was worked without errors >>>>>> > before. >>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>> > to work. >>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>> > again. >>>>>> > I did not check other jobs, but I think what is related to database, >>>>>> > will get errors. >>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>> > >>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>> > I have returned this database file back, postorius started to work >>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>> > only". >>>>>> > Please help me how to fix this issue. >>>>>> > _______________________________________________ >>>>>> > 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) >>>> >>>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Mailman 3 install questions: HAYSTACK_CONNECTIONS

by heller＠deepsoft.com

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

1 year

[MM3-users] Time Stand Still

by Barry Warsaw

Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation. I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps. I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken. Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org. It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals. My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced. And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader. If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient. This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate. Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention. -Barry https://www.wefearchange.org/

7 years, 8 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Stephen J. Turnbull

Sebastian Hagedorn writes: > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with Alembic, > as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? No. What is being discussed in the thread is changing the backend RDBMS, behind the SQL schema. Alembic operates in front of the SQL schema, managing the relationship between Python objects and the SQL schema. As the "Migration" section states, Alembic is used to handle changes in the model (ie, the Python objects), so that they are reflected in the SQL used to access the backend. Users don't need to use it unless they customize the Python objects (ie, patch Mailman themselves). If *we* change the model between versions, Alembic will automatically be invoked to update the SQL, but the user doesn't need to do anything about it. The potential issues Mark refers to involve differences in the way the different backend implementations handle SQL (this includes issues like default encodings for strings). These should be few because all the supported backends support standard SQL, but we can't guarantee there will be none. Differences in implementation also mean that you can't use the more efficient and compact dump formats that most implementations provide, because they are implementation- dependent. You need to use the textual format that is actually SQL programs that individually create each table, insert each record, create any needed indices, and so on.

7 years

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

by Mark Sapiro

On 5/24/20 7:20 PM, Alan So wrote: > Really thanks for your hard work Mark! It is a bit strange that parseaddr behave differently with CRLF and LF. Maybe if the server is a Windows, the behavior is consistent. It might be that on Windows, `mailman inject` would create the message with CRLF line endings. > May I know when or whether will this patch be committed to the repository so that it will be effective in future release of Mailman? Thanks. In the absence of an issue at <https://gitlab.com/mailman/mailman/-/issues>, probably never. <hint> The bottom line is the original mail created by Outlook is defective.[1] While Mailman could defend against this defect, starting to do that opens the possibility that there are other areas of the code that need a similar defense. Have you asked Microsoft to fix Outlook to not create these defective messages? That's the real solution. That said, if an issue is filed, someone might consider adding something along the lines of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> to the code base. [1] given an address of the form display-name (comment) <addr-spec> in a header, it can be folded either between the display-name and the (comment) or between the (comment) and the <addr-spec>, but if display-name (comment) is quoted as in "display-name (comment)" <addr-spec> "display-name (comment)" is now a phrase within which folding is not allowed and this can only be folded between the "display-name (comment)" and the <addr-spec>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

by Mark Sapiro

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. > 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` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: what process creates webui tables (mailmanweb db)?

by Mark Sapiro

On 9/26/22 09:14, tflatley(a)gmail.com wrote: > hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate Probably not. First of all, `mailman-web migrate` will only affect the mailmanweb database, not the mailman database, migrations for which are run implicitly when Mailman core is started. Also, migrations will only affect tables for which there are migrations, not all tables. > this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file > > python3 manage.py migrate Yes. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. The above message saying you need to make migrations because of changes to models indicates that your Debian/Ubuntu package is broken as the packager should have created all necessary migrations. > i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? I am confused as to why you are trying to run an out of date and possibly broken Debian/Ubuntu package when it appears you have successfully installed the latest PyPI packages in a venv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Out there plugin idea for tech cost sponsorship

by Steven Clift EDem

After spending 20 years running a non-profit that hosted email lists for local communities as my day job, that's now all volunteer as I run a startup. Figuring out how to raise money to cover server costs without selling out our members with targeted social media advertising, was a continuous challenge. Anyway, today I am still involved in efforts to route around digital ad behemoths, but I a trying to help small businesses and shop for good brands gain new customers. So here is the question - do you think a Mailman add-on/plugin/module/whatever you'd call it that allowed list admins to reward their new subscribers to email lists with custom themed "for good" discounts would be of interest to many??? Normally, we (GoodCarts) reward people post-checkout with discounts in reciprocity powered circles of online stores. Stores essentially grow together by sharing customers instead of bidding against each other. The way I could see working with email list providers is basically adding an affiliate marketing style commission where purchases with post-subscription rewards would go to the partner based on results. When we go from hundreds of brand members to thousands and add in a "buy local" or brands by theme/values/impact, in theory my non-profits local online community forums could mission align by offering discounts to locally owned businesses. Our view is that exclusive discounts as rewards post transaction (purchase, email list subscription, volunteer sign-up, event registration, online petition signature, etc.) is far better than plastering ads everywhere. Anyway, I'd be curious if you think idea might have legs with Mailman list hosts/admins??? Nothing urgent, just a Saturday morning think different idea. Steven Clift

2 years, 6 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. > Is there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell 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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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/

3 years, 8 months

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

by Simon Coggins

On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)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/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs> 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. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [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, 8 months

[MM3-users] Re: Healthchecks and Django

by Philip Colmer

On Tue, 4 Jan 2022 at 09:36, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > Philip Colmer writes: > > > For the MM3 servers, we're probing "/mailman3/lists/". > > You could create a path in urls.py called "250" that does nothing but > respond with a 250 status (and maybe a hello-world page). The issue > with /mailman3/lists/ is that it queries core for the lists (which, if > successful, proves that core is up as a side effect). > > > Is there another URL we could use to check the health of a MM3 server > > What does this mean to you? Our Mailman 3 suite consists of three > applications, core, Postorius, and HyperKitty, which might or might > not be installed, and if installed might or might not be running on > the same host. Core in turn depends on the MTA and starts a bunch of > qrunners. Any of the above might fall over on its own. (I don't > think there's any way to check on the health of a particular qrunner > from the net, though.) > That's a very good point. It would be nice if, at some point, an actual healthcheck endpoint could be included that returned some information about the state of the different applications as a JSON blob. It is increasingly useful to try and spot application problems before users do :) > > > Or, if not, is there a way of stopping Django from sending out the > > emails? > > There probably is, but I don't know it. Mark might, but if not asking > on a Django list would be a better place. > > Thank you. Regards Philip

3 years, 6 months

[MM3-users] Re: Creating users via RestAPI / User-Management - a bunch of questions

by Mark Sapiro

On 6/20/25 06:39, Christian Schneider wrote: > Dear Mark and companions, > > somehow I can not cope with the user management... > (I am running a venv-installation, latest stable versions) > > I read this manual: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > and played with the RestAPI calls... > > I know about the fine grained differences between user and member, admin/owner, superuser... > and about the two user databases in PostgreSQL and Django-Framework. I'm not sure what distinction you are making between PostgreSQL and Django-Framework. There are two separate and distinct users, Django users and Mailman core users. Information about both is in the PostgreSQL database. Django users are in the `auth_user` table and Mailman core users are in the `user` table, both in the public schema, although if you split the data into a `mailman` database and a `mailmanweb` database the `auth_user` table is in `mailmanweb` and the `user` table is in `mailman`. > What I stumble upon is the RestAPI calls to create a "working" user (with the ability to login via WebUI). > When I follow the manual (from the url above) I create a user (including password) that appears in the PostgreSQL database. > (And this user is visible on the User-URL (https://example.com/mailman3/users)) > Even when I (via WebUI) set the user as "approved" this user is not able to log in... > I assume this restriction is in accordance to the fact that there is not equivalent Django user. > (There was a mail in the archive of the MM3 user group...stating that one has to use the Django RestAPI to create the appropriate user) The above is correct. The Mailman REST API only deals with Mailman core. Mailman core knows nothing about Django. > When I create the user using the WebUI (https://example.com/accounts/signup/?next=/mailman3/lists/) > the new user is created in the right (complete) way...appearing in the PostgreSQL database and as a user in Django. > How is this sync between the two databases realized? I'm still looking into that, but it isn't the creation of the Django user per se that creates the Mailman user. The process has multiple steps. 1) Sign-up for an account. This creates the Django user and sends an address confirmation email. 2) Click the link in the confirmation email. This takes you to a page with a `Confirm` button to confirm the email address. 3) Click the confirm button. It is not until step 3) that the Mailman user and address records are created. > (The Django user also has the correct status (no staff status / no superuser status / just active status) how is this realized?) Presumably by the sign-up process not setting staff status and superuser status. > As I am not very familiar with python programming (I know Perl/Java/C++ and have an (maybe outdated) concept of OOP), > is there a quick way to implement this kind of sync by copying the register logic from mailman's python action script for registering? I think it must be django-mailman3 that's doing this, but I haven't been able to see how so far. django-mailman3 does override the template for the /accounts/confirm-email page, but this is only to include styling. > Other questions: > Will there be a create_admin_user-script that is callable via CLI (like createsuperuser or create_list)? > (This script ought create a user in PostgreSQL and as Django user) No plans. There are `mailman addmembers` and `mailman admins` commands to add members or admins to a list. Adding an owner or moderator to a list via `mailman admins` will also create a Mailman user for that person if there isn't one already, but it won't create a Django user. > How will a social account provider (like oidc) linkage (in Django) fit in this concept? > Will oidc-accounts be copied to the Django's user database (or PostgreSQL db) or is it an on-the-fly check against the oidc-provider? (I assume second option) > What are the status-flags (staff status/superuser status/active status) of the linked oidc-accounts? (Can I specify the status flags?) I don't offhand know the answers to that, but I think logging in via a social account provider creates a Django user.. > A conceptual thought: > When "user1" (with email user1(a)example.com) is known to django via oidc linkage > and I create "user1" (also with email user1(a)example.com) via RestAPI calls > (following the url https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > do I have a "complete" user then? > I mean a user who is able to login and who can be assigned to a list as admin (e.g.) > (In this case I would not have to care about the Django user database... ;-)) If the user can log in to the web UI with an associated email address, if that address is an admin of a list, the logged in user can admin the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Dealing with recipients' servers spam filtering

by Gilles Filippini

Brian Carpenter a écrit le 12/02/2021 à 17:33 : > On 2/12/21 10:59 AM, Gilles Filippini wrote: >> It says: host mx1.free.fr[212.27.48.7] said: 550 spam detected >> (in reply to end of DATA command) I don't have any SPF record setup. >> DMARC mitigation is configured to 'Replace From: with list address' >> and 'DMARC mitigate unconditionally' set to 'No'. > > Well make sure you set up SPF records for your list domains. They do > help in mail delivery. I personally set DMARC mitigate unconditionally > to yes for my lists. Unfortunately the 550 spam detected message is too > generalized to be helpful. If you have more informative information from > your logs then please share them. Writing down what I've learned so far, in case it may help others: 1- The lists server DNS record (lists.example.com) should be of 'A' type (no 'ALIAS' or 'CNAME') 2- The SPF record should be set for the very same DNS name; e.g. lists.example.com (not just example.com) 3- This record seems to work for my server: lists.example.com. IN TXT "v=spf1 ip4:123.123.123.123 -all" Where the IP address is the same as the one registered for the 'A' record. How to check the SPF record: 1- Create a dummy mailing list and register your email address and check-auth(a)verifier.port25.com. 2- Send an email to this list. You should receive a report from auth-results(a)verifier.port25.com Here is what I've received for my server: ========================================================== Summary of Results ========================================================== SPF check: pass "iprev" check: pass DKIM check: none Let's see it this is enough to mitigate the problem with Hotmail addresses. Best, _g.

4 years, 5 months

[MM3-users] Re: Current status and issue deleting Archives in Mailman3

by Abhilash Raj

> On Nov 2, 2021, at 12:51 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/2/21 11:50 AM, bob B wrote: >> So I am teaching myself to fish, and see that it is actually django-admin, so that is in >> mailman-web? (in docker) >> But i get this: >> $ docker exec -it mailman-web /bin/bash >> bash-5.0# django-admin shell >> Python 3.8.10 (default, May 6 2021, 06:30:44) >> [GCC 9.3.0] on linux >> Type "help", "copyright", "credits" or "license" for more information. >> (InteractiveConsole) >>>>> from hyperkitty.models import MailingList >> Traceback (most recent call last): > ... >> 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. > > > Do what it says. I.e. run > > DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell DJANGO_SETTINGS_MODULE expects a Python import path, instead of a filesystem path. The docker has documentation on running management commands, which in this case is “shell” [1] $ docker exec -it mailman-web python3 manage.py shell [1]: https://asynchronous.in/docker-mailman/web/#django-management-commands I know there are plethora of ways to run Django management commands, but this is the easiest one for docker. django-admin will work too, but you have to be in the right working directory for the import path to work and it get weird. I’ve always disliked how Django management commands work unfortunately and in trying to “fix” that with “mailman-web” (which isn’t adopted by container images), i feel I might have re-invented a third option. -- thanks, Abhilash Raj (maxking)

3 years, 9 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > Yes, the same problem. > I created the file __init__.py in /opt/mailman/mm > However, when I run using the wsgi.py I ended up (still do!) with the error: > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > application='mm3-lists.server.name|/mm3'): Loading Python script file > '/opt/mailman/mm/wsgi.py'. What is the contend of the file /opt/mailman/mm/wsgi.py? You previously posted the setting of WSGIDaemonProcess in your Apache config as: > WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman3 \ > group=mailman3 python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 \ > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var Is it still that? ... > 197.232.81.246:64709] mod_wsgi (pid=79132): Exception occurred processing > WSGI script '/opt/mailman/mm/wsgi.py'. > [Wed Jul 29 10:08:51.872754 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] Traceback (most recent call last): > [Wed Jul 29 10:08:51.872827 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File "/opt/mailman/mm/wsgi.py", line 38, in <module> > [Wed Jul 29 10:08:51.872835 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] application = get_wsgi_application() > [Wed Jul 29 10:08:51.872847 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/wsgi.py", > line 12, in get_wsgi_application ... > [Wed Jul 29 10:08:51.872984 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] ModuleNotFoundError: No module named 'settings' > > -- 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: changing adverstised status

by Mark Stuart

I can confirm the issue is happening to me as well postorius 1.2.1 / Django 2.0.7. If you're logged in and go to the list setting page, check the radio button for 'Show list on index page' to 'No' and click save at the bottom, it reverts back to 'Yes'. Then it still shows up on the index page. I haven't tried the mmclient method to see if that works. -- Mark (stuieordie) On Wed, Aug 22, 2018 at 1:30 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Aug 22, 2018, at 1:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change "show > > list on index page" via the settings, but the value isn't saved. Is > > there a way to set advertised = False to a specific list via the shell? > > Could be related to > https://gitlab.com/mailman/postorius/merge_requests/352 > > The behavior of some of our boolean fields changed with newer releases of > Django, but it has been fixed in master branch. > > > > > Thanks & Regards, > > Alex > > > > (Kulturserver editorial staff) > > _______________________________________________ > > 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/ >

6 years, 11 months

[MM3-users] Re: Weekend releases

by Abhilash Raj

On Tue, Dec 10, 2019, at 8:27 AM, Mark Sapiro wrote: > On 12/10/19 2:58 AM, Paul Arenson wrote: > > Thank you. The setup I am using now has Hyperkitty 1.3.0 and I just wanted to confirm. Somewhere I thought I read there is a facility in the Hyperkitty archive interface to format text. Probably I misunderstood, but if there is such a facility, I am not seeing it. Maybe I am looking for something like Tiny Ice and thus can't find it. > > > Markdown rendering of message bodies in Hyperkitty is > <https://gitlab.com/mailman/hyperkitty/merge_requests/160>. This is > installed on <https://lists.mailman3.org/mailman3/> and > <https://mail.python.org/mailman3> but is not yet released. > To add more, if you look at the merge request, there are some pieces missing before it can be merged. Especially, a mechanism to opt-out on a per-list basis from this. While markdown is pretty nice to look at when you are dealing with certain mailing lists which communicates in plain text, it can be horrible to look at if the users aren't aware about markdown and/or the special markdown syntax. In practice, there is only so much we can do to render a random email as HTML using markdown syntax. Maybe I can get to it this holiday season and it can go out for interested folks in the next Hyperkitty release :) > -- > 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)

5 years, 7 months

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

On 8/5/22 09:17, summersan(a)nclack.k12.or.us wrote: > > My Questions: > > Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? > > Should there normally be other detectors listed in the logs beyond the `DSN` one? > > If so, is there a setting I can change somewhere to make this happen? Prior to flufl-bounce 4.0, it would run all detectors on every message to the -bounces address. Beginning with 4.0, it runs the detectors in a defined order from most specific/authoritative to least. If you are seeing only or mostly the `DSN` one, you have 4.0 and the `DSN` detector recognizes a RFC 3464 compliant bounce. > For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Probably the upgrade also upgraded flufl.bounce to 4.0. So the real question is why are you seeing large numbers of bounces. Since it appears they are recognized by `DSN`, they probably aren't spam to the -bounces address. Do you have verp probes enabled (verp_probes = yes in the mta section of mailman.cfg)? If so, it's possible that you are getting bounces for spam and the like, but the probes don't bounce so the user's delivery is never disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 03:25:41 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > On 13/3/21 8:53, John Covici wrote: > >> We recommend installing Mailman and the web components in a virtualenv, > >> but it is not a requirement. We also suggest that postgresql is a better > >> choice than MariaDB. > >> > > I sort of am installing from source, gentoo installs from source. No > > one on the gentoo users mailing list seems to be able to help me, > > except to tell me to use a different mailing list mechanism called > > mlmmj. > > > From the perspective of someone who was in the same place (but > installing in a FreeBSD S.O.), I would recommend you to follow > the "virtualenv" guide but without executing the "env" > commands. It will produce a system wide mailman3 installation but > it will work (as it is for me since a few moths ago) > > I writed down a step by step path of my installation and it could > be of your interest (maybe you have to locate and install some > packages by different name, but I think it will be not much > difference). It could provide you a overall view of all the > processes implied. > > I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 Thanks, by the env commands you mean the creation and activation commands? I will certainly look at your thread. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 4 months

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

by Mark Sapiro

On 3/19/21 11:14 AM, Jens Günther wrote: > Just checked again and saw: > > - in the setup it works perfectly in Hyperkitty, that's nice > > - for the first web host I have 2 mail domains registered, so it also > matches (unfortunately) with what you said :-( > > Anyway, I dceleted one of it, still both lists are shown on either web > host, so it's generally not working. I don't know why this didn't work. If there is only one mail host in the domains that has the current web host as its web host, it should work. > If I can do something on this issue, please advise me. Thanks. The issue is that neither Postorius or HyperKitty as a direct way of getting lists by web host as the web host information is not an attribute of the list. We have to see which mail hosts are associated with the current web host and then display only those lists that match one of those mail hosts. The issue with Postorius is if there was more than one mail host associated with the web host, this code https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… could be relatively easily made to work by extending all_lists to include all the mail hosts, but it wasn't clear to me how to fix https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… in the case where there was more than one mail host. If you can suggest a fix, that would help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Trouble Installing Mailman3

by Henry Hartley

I'm having problems installing mailman3 following the instructions on https://docs.mailman3.org/en/latest/install/virtualenv.html Everything goes well until I get to the Installing Mailman Core<https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> step, which has me do the following in my venv environment: (venv)$ pip install wheel mailman psycopg2-binary Ubuntu 24.04.02 LTS Python 3.12.3 pip version 24.0 First, I was getting problems because my company firewall was blocking outbound traffic. I got that taken care of. Next, I was seeing certificate errors, saying there was a self-signed certificate: WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))': /simple/wheel/ Could not fetch URL https://pypi.org/simple/wheel/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/wheel/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))) - skipping When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) ERROR: No matching distribution found for wheel The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I've rerun the apt install of python3-dev and python3-venv to make sure those are present and up to date. Any help you can provide will be greatly appreciated. -- Henry Hartley Westat

1 month, 4 weeks

[MM3-users] Re: Lookup Table Questions

by Mark Sapiro

On 12/7/21 4:09 PM, Peter Williams wrote: > > - The Mailman documentation notes that either hash or regexp tables are > supported. Is it ok to use LMDB or will I run into issues at some point? Mailman only supports hash and regexp tables for automatic maintenance of the tables as lists are created and removed. If you use LMDB tables you will need to maintain them yourself. The `mailman aliases` command won't do it. > - If LMDB tables are not a good idea to use, are there any drawbacks to > switching over to regexp tables? My main concern is that we currently have > 7000+ mailing lists, and I'm worried that switching over to regexp may > result in slower lookups. I am also wondering if there are potential issues > if the 'mailman aliases' command is run simultaneously alongside another > 'mailman aliases' command. In the past it seems like the hash table was > locked (which was good), and I'm not sure if this behavior is kept by > moving over to regexp. This may be more of a Postfix question and I > apologize in advance if I am asking the wrong mailing list for this. The locking is done in mailman/mta/postfix.py regardless of table type. I.e. it's the same for hash and regexp table updates. I wonder why you are manually running `mailman aliases`. This really shouldn't be necessary as the files are regenerated automatically as lists are created and removed. As far as performance of regexp vs hash tables, I have no idea. That's really a Postfix question. -- 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: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. Mailman 3 consists of several pieces. There is a core engine which is Python 3. The core does the basic email list management and exposes many options and settings via a RESTful API. There is also mailman.client which provides Python bindings for the REST API. This is Python 2. We also provide a web management UI, Postorius and an archiver, HyperKitty. These are Django applications and all of this is Python 2. There are other pieces as well. > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler. This is only the core. You can install it with python3 setup.py install either in a python 3 virtualenv or not, but this will only give you the core. I suggest you see the docs at <http://docs.list.org/en/latest/>, and if you don't want to use bundler, see <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the recommended way to set up a working, non-development Mailman suite. In short, the core requires Python 3.4, most of the rest of the suite requires Python 2.7 because of dependencies not yet ported to Python 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 5:43 PM, Ralph Seichter wrote: > With archiving enabled, mail is sent with headers like the following: > > Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> > List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> > List-Post: <mailto:foo-users@lists.example.com> > List-Subscribe: <mailto:foo-users-join@lists.example.com> > > The 'mailto:' entries are fine, but I need all 'https:' links to be > prefixed with https://lists.example.com instead of https://example.com . > > Does Mailman extract CN parts from the SSL certificate to populate the > header values (that would explain 'example.com' in my tests), or is this > something I can influence using configuration parameters? I searched the > docs for Mailman Suite and HyperKitty, but did not find an answer. It has nothing to do with the ssl certificate. It comes from _get_url in hyperkitty/views/mailman.py > def _get_url(mlist_fqdn, msg_id=None): > # We can't use HttpRequest.build_absolute_uri() because the mailman API may > # be accessed via localhost. > # https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.Htt… > # https://docs.djangoproject.com/en/dev/ref/contrib/sites/#getting-the-curren… > # result = urljoin(public_url, urlunquote( > # reverse('hk_list_overview', args=[mlist_fqdn]))) > # We use the MailDomain association from django_mailman3 to find out the > # proper domain. What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/ Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Thu, Oct 26, 2017, at 06:39 PM, Mark Sapiro wrote: > On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > > > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. > > > This usually means that postfic is trying to deliver to an address and > the message already has a Delivered-To: header with that address. > > What are the headers of the "looping" message in the report? What are > the Postfix log messages related to that message? > > > > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > > > https://github.com/maxking/docker-mailman > > > I have essentially no knowledge of the docker container images, so I > can't be much help with issues specific to them. The Postfix integration in container images is basically just using regex instead of hash maps and everything else is same. I do remember atleast one other person facing a similar issue where Postfix wouldn't accept listname+token@domain addresses with our regex. I am thinking this is the same issue. > > -- > 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/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 9 months

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

by Stephen J. Turnbull

Core implementation details, so I beinging this here from Mailman Users @ mailman3.org. Abhilash Raj writes: > I have started working on designing a User management page[2] in > Core which should make it easy for superuser to manage several > things about a User, including the ones that don’t have an account > in Postorius to manage their own. I don't understand this design with a "page in Core". I was thinking about this kind of problem, and tentatively came to the conclusion that any reference to something that can be resolved to a User should generate a Django account for that User in Postorius or HyperKitty. Authorization to use that account would still require authentication via the usual email verification dance, or some level of admin privilege. The thing is that emails that have not been added to a User are unique. They will be the only Address attached to User created to manage them until authenticated, and transitively the only address attached to an automatically-created Django account (since those are 1-1 with core Users if they exist AFAIK). What's missing here is the ability to merge core Users and their corresponding Django accounts. Doing this with nothing more than the usual email verification dance is not *obviously* provably secure to me, so we need to be careful, but I think it probably will turn out to be as secure as you can get. It seems to me that User merging is the most pressing problem of this kind. (At least, it affects me on a couple of list hosts, as well as on GitHub and GitLab.) > [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 I'll take a look tomorrow or early next week. Steve

4 years, 4 months

[MM3-users] Re: Deleting default "example.com" domain breaks everything

by Abhilash Raj

On Fri, Jul 16, 2021, at 12:12 PM, Mark Sapiro wrote: > On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > > Hello. I'm new with v3 of mailman. > > Installed via aptitude on deb10. > > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > > I then deleted example.com, and everything broke. > > The only site I had was still using example.com. > > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? > > > Try setting `SITE = 0` in your Django settings file. If that doesn't > work, try successively 1, 2, etc. One of these should work. Usually, example.com is always 1 and then it increases sequentially. So, if this is the first one you created, I'd try using 2. > > Also going back to your prior thread, you had > > > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser > > Aside from the python/python3 issue, you should run any Mailman and > Django management commands as the Mailman user (probably `list` in your > case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 > and https://gitlab.com/mailman/mailman/-/issues/776. > > > -- > 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

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

by Jacob Sievert

Hello, we seem to have the same problem right now. We are still on python3.6 and postgresql 12.9 I looked at our Table pendedkeyvalue and we have roughly 35k rows in that table, is that normal or shouldn't those get cleaned up after a while? with regards Jacob On 2022-01-28 15:57, Stephan Krinetzki wrote: > Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> > mailmancore/API ->database >> > that seems to have an issue and only with this one >> > DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX >> > query. However, like you, I have no idea as to what you could do further >> > to debug this. >> > I have an idea, but it seems so obvious that presumably it's already >> been tried: log in to the database as mailman with pgsql and try >> deleting something. If that works immediately, try with mailmanclient >> and the mailman command line utility. >> Steve > > Well, we didn't try this. Since we don't know what the query for > deleting a held message in the database needs to look like, we left > that out for now. If someone can help me there, it would be great. > > Over the mailman shell it hangs as long as on the web ui (using > mailman shell -l list@host and iterating over the held messages). So > it is the communication Mailman API <-> Database. > _______________________________________________ > 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, 6 months

[MM3-users] Re: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 7:45 AM, robert.kydd(a)gmail.com wrote: > Hi Mark, thanks for this. I was away and only got back now. > It's great to get rid of the reason text. > Is there any way I can find out what is i18n message catalog. It would be nice to give a more pleasing message to the users I am still not clear on what Mailman version you are using. If it is Mailman 3, i18n translations for Mailman core are still a work in progress, and I can't tell you how to do this. For Mailman 2.1, you will find within Mailman's file system, a messages/ directory with several 'language code' subdirectories, but not 'en'. You need to create messages/en/ and messages/en/LC_MESSAGES/ and then create the file messages/en/LC_MESSAGES/mailman.po with contents like: ---------------------------------------------------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR ORGANIZATION # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: Sun Jun 17 12:22:07 2018\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: ENCODING\n" "Generated-By: pygettext.py 1.4\n" #: Mailman/Handlers/Hold.py:61 msgid "Post by non-member to a members-only list" msgstr "WHAT YOU WANT TO REPLACE IT WITH" ---------------------------------------------------------- with the various UPPERCASE things replaced appropriately and then 'compile' it via > msgfmt -o messages/en/LC_MESSAGES/mailman.mo messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Modify approval email

by Odhiambo Washington

On Fri, Sep 15, 2023 at 5:33 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > pau.baiges(a)csuc.cat writes: > > > Is there a way to modify the email that is sent by default to list > > owners when a non-list member sends email to the list? > > Yes. As list owner (or site admin) in Postorius go to Templates, and > click on "New Template". Select list:admin:action:post from the > drop-down menu to the right of "Name". Copy the current message > (site-packages/mailman/templates/en/list:admin:action:post.txt is the > original, but do not edit this -- it will be overwritten on upgrades) > to the text box and edit to taste. Unfortunately there is no "web > site" variable but typically that is the same for all lists, so adding > > https://your.host.here/mailman3/lists/$list_id/held_messages > > in some appropriate place probably does what you want. > > There is no way to indicate that this is a link because these messages > are plain text. However, most mail clients will turn a URL into a > link. If your moderators are not so lucky, try wrapping it with > > <URL:https://your.host.here/mailman3/lists/$list_id/held_messages> > > or even the usual HTML: > > <a href="https://your.host.here/mailman3/lists/$list_id/held_messages"> > Moderation Page > </a> > > One of those may help. > Also, you can take a look at this documentation: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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, 10 months

[MM3-users] Re: Hyperkitty not receaving messages / empty archive [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/urls

by Mark Sapiro

On 1/21/25 05:44, Helge Baumgart wrote: > Hyperkitty-Api-Key in the docker-compose.yml is set via .env Variabel, > so it should be identical. I don't know how this works in the Docker image, but ... > Traceback (most recent call last): > File > "/usr/lib/python3.11/site-packages/django/core/handlers/exception.py", > line 56, in inner > response = get_response(request) > File > "/usr/lib/python3.11/site-packages/django/core/handlers/base.py", line > 197, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File "/usr/lib/python3.11/site-packages/hyperkitty/views/mailman.py", > line 109, in _decorator > not hmac.compare_digest( > > Exception Type: TypeError at /hyperkitty/api/mailman/urls > Exception Value: unsupported operand types(s) or combination of types: > 'str' and 'NoneType' The above code is doing auth = authorization.split() if (len(auth) != 2 or auth[0] != 'Token' or not hmac.compare_digest( auth[1], settings.MAILMAN_ARCHIVER_KEY)): and the exception says either auth[0] is None or auth[1] or settings.MAILMAN_ARCHIVER_KEY is None. But > META: ... > HTTP_AUTHORIZATION = 'Token (value)' and > Settings: > Using settings module settings ... > MAILMAN_ARCHIVER_KEY = '********************' So The Authorization header is the appropriate `Token value` which should result in auth[0] being 'Token', auth[1] being the value and MAILMAN_ARCHIVER_KEY is set > That is my docker-compose.yml: ... > mailman-web: ... > - HAYPERKITTY_API_KEY=${MM3_HYPERKITTY_API_KEY} #someapikey_longAndTrustworty I don't really understand why the above typo (HAYPERKITTY_API_KEY, not HYPERKITTY_API_KEY) would cause this error, but it needs to be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Mailman List Lost on URL transfer

by Mark Sapiro

On 09/20/2017 10:28 AM, heartsandbones(a)zoho.com wrote: > > Here’s the scoop: > I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. > > I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. As I have told you in other communications, you need a DNS A record for the mail.sbfriends.org pointing to the IP address of the Mailman server that hosts the list. We have no idea what that IP address is. You will have to ask your client what Mailman hosting service they were using for their sbfriends.org domain. That A record will probably suffice to get to the web UI for the list, but you will probably also need an MX record for the sbfriends.org domain pointing to mail.sbfriends.org for mail delivery to the list. > This is my first post to this forum, so I hope I’ve done so correctly. The correct list for Mailman 2.1 issues (http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org is a Mailman 2.1 URL) is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>. This list is for Mailman 3. However, you won't get a different answer from that list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4

by Jered Floyd

The weird client version was, of course, my fault... I had followed the instructions here in my settings.py: https://adamj.eu/tech/2020/02/04/how-to-use-pymysql-with-django/ This fix was incorporated into PyMySQL some time ago and is no longer necessary. The requirement for MariaDB remains real. --Jered ----- On Apr 3, 2024, at 7:36 PM, Jered Floyd jered(a)convivian.com wrote: > A heads-up for anyone else on RHEL 8, because the error is mystifying. > > django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django > 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for > MariaDB 10.3. > > For some reason I haven't yet been able to identify, this causes pyMySQL > integrations to fail with the mysterious error: > django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is > required; you have 1.4.6. > > (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while > Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is > coming from as it appears... nowhere.) > > Bypassing that error check gives the more informative: > django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found > 10.3.39). > > Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past > LTS, so I would recommend that Mailman systems be migrated to RHEL 9. > > --Jered > _______________________________________________ > 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, 3 months

[MM3-users] Re: Mailman3 upgrades

by Caballero, Danny (Dan)

Thank you! Yes, it was my fault. I have some customization in base.html. I'll need to track those changes across updates. Thank you! ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Tuesday, October 19, 2021 8:02 PM To: Caballero, Danny (Dan) <dancab(a)caltech.edu>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Mailman3 upgrades dancab(a)caltech.edu writes: > "Loading failed for the <script> with source > “https://mailman3.caltech.edu/static/hyperkitty/libs/jquery/jquery-1.10.1.min.js” > > Sure enough, I do not have that script. In fairly freshly updated sources, I have references to one or the other of > -rw-r--r-- 1 gunicorn root 117370 Oct 19 14:55 jquery-ui-1.10.3.custom.js > -rw-r--r-- 1 gunicorn root 58173 Oct 19 14:55 jquery-ui-1.10.3.custom.min.js in hyperkitty/hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bunudle.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js hyperkitty/hyperkitty/templates/hyperkitty/base.html The last file also refers to hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css My guess is all the files you listed are from a recent installation or upgrade, but somehow base.html didn't get upgraded. Based on the principle "always blame the user" ;-), I'd start by checking if our version is shadowed by your local version? Anyway, I bet the version number is wrong in base.html and if you fix that everything else will fall in line. If not, check if popper and boostrap are either older versions or perhaps shadowed by older versions somewhere. A word to the wise: grep(1)ing the .min.js.map files is not advised. They're huge and all one line it seems. Better to use an editor's search function.

3 years, 9 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

Hello everybody, I successfully resolved the owner:group issue and I am no longer getting the permission errors. Basically, I had to set the ownership:group to mailman:www-data and make the group permissions rw for everything to work successfully with Apache and Mailman3. As I mentioned earlier, I have mailman (core) now working, however, I cannot seem to get the web interface to work. I believe that I have gotten rid of all of the permissions issues and the mailman3-web service starts and stops without error. However, when I use a browser to go to the web interface, I get File Not Found errors in the browser window and my Apache2 logs say: 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! # ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> By the way, this is the Apache configuration file that the Debian package installed with my initial installation. Does anybody see any problems in my Apache configuration file that could be causing my problems? Do you see or suspect any other issues? Thanks, Gordon

3 years, 5 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/21/22 16:24, Dan Caballero wrote: > Mark, > > I'm seeing this issue pop up this week with several lists. You previously mentioned two conflicting browsers potentially causing the issue. Can you elaborate? That would only cause a transient issue which would not occur on a subsequent get of the held message view. I gather this is not the case here. I.e. once the error occurs on a get of the held message view, it is persistent. > In addition, is there a way for me to run this cleanup using mailman shell -r "somescript" so that I can check all the lists instead of one by one? For a -r script, try ``` # In non-interactive scripts, we need the explicit imports. from mailman.interfaces.listmanager import IListManager from mailman.interfaces.requests import IListRequests, RequestType from zope.component import getUtility def somescript(): for mlist in getUtility(IListManager): requestdb = IListRequests(mlist) for req in requestdb.held_requests: if req.request_type == RequestType.held_message: if not requestdb.get_request(req.id): print(f'List: {mlist.list_id}, Bad request id: {req.id}, deleting') requestdb.delete_request(req.id) ``` The real question here is what are these spurious requests and how are they occurring. If you do a query like ``` SELECT * FROM _request; ``` Are there entries with empty `data_hash` or entries with an `id` that is not the value of any `pended_id` in the `pendedkeyvalue` table. BTW, I understand why you thought an import was needed in the interactive script in my message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… - the `from mailman.interfaces.` line was a mistake on my part and shouldn't have been there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 2 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 2 months

[MM3-users] Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 5/18/22 10:48, dancab(a)caltech.edu wrote: > Mark, > > We have a question related to this thread. We use LDAP for authentication. It seems that the name attributes can only be edited via the LDAP synchronization when a user logs in for the first time and thus creates their user account. > > But what about list members that are not in LDAP? What happens behind the scenes when a member is added to a list? The user's display name is set when the user record is initially created. Assuming someone who is initially unknown, this can happen when the unknown user signs up for a web account, when the unknown user subscribes to a list via the web UI or when the unknown user is mass subscribed to a list. > Manually subscribing members has different results with our configuration. > > I've seen the manually entered name show up as "None" <foobar(a)caltech.edu>. There was a pre-existing user with that address and no display name. > I've seen the entry be accepted as is, eg. "John Doe" <jdoe(a)example.com> > I've seen the name entry be ignored but the email accepted eg. "Foo Bar" <foobar(a)caltech.edu> is subscribed but the member list only shows <foobar(a)caltech.edu> The display name has nothing to do with message acceptance. That is based only on the address. In Postorius >=1.3.6 there is a `Users` selection at the top of most pages if you are logged in as a superuser. This allows management of users including their display name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > we are now getting feedback from people, who say that they are unable to > sign up, with mailman3 telling them: > > Subscription request already pending > > this is somewhat bad as: > > - at least some of the users (who reported the problem) tried to > subscribe 2 months ago (2022-01-04) - if they did not confirm their > email back then, i'm pretty sure that this email has been lost by now > - my /etc/mailman3/mailman.cfg has "pending_request_life: 3d" This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman 3.3.5. > - i (as administrator) do not see any "pending subscriptions" (the list > is setup with a simple "Confirm" subscription policy The count badge only counts subscriptions waiting moderator approval. If you pull down the Subscription requests tab and click Pending Confirmation you should see them and be able to discard them. > i wonder: > - why are the pending subscriptions not expired? (i guess they should > have expired after 3 days) It's a bug fixed in Mailman core 3.3.5 > - why can't people re-subscribe while there's a subscription pending > (e.g. if the confirmation mail got lost)? Because that's the way it was implemented. > - how can i list all pending subscriptions (for a given mailinglist)? Pull down the Subscription requests tab and click Pending Confirmation. > - how can i resolve the situtation (e.g. send out another reminder; > manually expire the pendings; manually confirm the pendings,...) If the above doesn't answer that. provide more detail. -- 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

Search results for query "dO"