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

[MM3-users] Re: Avoiding non-members to be saved.

by Stephen J. Turnbull

Guillermo Hernandez (Oldno7) via Mailman-users writes: > I find it very convenient too, but it concerns me that spammers, > really "profesional" spammers and senders of phising mail change > the forged address and sender domain too rapidly to track them. As > of it, the non-member database is growing more and more. It could > be a "monster" in two or three years... Well, let's think that out. I think we allocate a 255-byte text field for email addresses, another 255 bytes for display names, and I can't imagine that including the rest of the data fills as much as 1k, even including indicies and other database optimization overhead. So if you get a million spam messages to your lists, each from a unique address, that's only one gigabyte. To get a million spam messages in three years, you'd need to get almost a thousand per day that get through your MTA's filters to Mailman's moderation queue, which is the only place this automatic construction of nonmembers takes place. I think your moderators would let you know about that long before your disk fills up. I'm not making fun of you, I'm explaining why I don't think this is a high priority for us, and why you don't need to worry about monster databases, either: the human resources just for looking at the queue, let alone taking action, will be a constraint long before the disk or CPU consumption for the address database is. If there's something wrong with my analysis, let me know, but as far as I can see, if the spam flood to your lists gets to that scale, the first worries are denial of service and admin exhaustion. As usual, the best answer is to stop the barbarians at the gate (ie, the MTA). I guess if the list is configured to automatically discard all posts from non-members, we could optimize away the non-member creation. But this seems like a relatively rare case, and if there were non-local bans on addresses, it might not be a good idea anyway. In theory, we could even arrange to do the lookup at moderation time, although we currently do it at mail receipt time. That would allow a moderator to ban the addressee on list A and then not even see the post when they go to check on list B. I suspect even professional spammers don't bother to create a unique sender address for each recipient! Obviously, this kind of service would require putting the nonmember addresses in the database, at least temporarily. Steve

5 years, 1 month

[MM3-users] Re: Gmail problems?

by turnbull

2023-04-24 02:12 に Stephen Daniel さんは書きました: > When I check a message that I received from the list I am told: > ARC-Authentication-Results: i=2; mx.google.com; > dkim=neutral (body hash did not verify) header.i=(a)bellsouth.net > header.s=s2048 header.b=nkq1aBRe; This DKIM failure is normal. To get the body hash to verify, you need to set the body header and body footer to empty (beware, you can't see whitespace, but if there's whitespace, it's not *empty*). The header usually is empty, but by default we do set the footer, so you'd have to clean that out. Of course, if you have legal or organizational requirements to set the footer or header, you're stuck. > arc=pass (i=1); ARC is a protocol designed for mailing lists and other intermediaries that may change messages in ways that invalidate cryptographic signatures. It works by having each host that may munge messages (1) check all the previous ARC authentication results and (2) providing its own signature on those results if the most recent one is authentic and validates. (This is like a hash chain such as in git.) > spf=pass (... > > I also see this: > ARC-Authentication-Results: i=1; pb-mx22.pobox.com; > arc=none (no signatures found); This says that at the first ARC host in the path no ARC headers were found. Of course not, there were no previous participating hosts. > bimi=skipped (DMARC did not pass); > dkim=fail (message has been altered, 2048-bit rsa key sha256) Note it has already failed DKIM here. This says that some domain (presumably the one providing the Mailman host) (a) altered the message, invalidating the DKIM signature, and (b) based on arc=none above, does not participate in ARC. > header.d=bellsouth.net header.i=(a)bellsouth.net header.b=nkq1aBRe > header.a=rsa-sha256 header.s=s2048 x-bits=2048; > dmarc=none policy.published-domain-policy=none > > How do I fix this DKIM error? > Has the body changed because I add a footer to emails as they pass > through? Yes. There are two ways to fix it. (1) Don't add a header or footer to the body, and don't munge the subject with [list: serial#] annotations. This is guaranteed to work, in the sense that the DKIM signature will validate, and presumably DMARC "from alignment" will pass. (2) Use the ARC protocol. Mailman 3 provides the basic functionality, but exactly how you you hook that up to your site's crypto credentials depends on your site. Probably you can just reuse the DKIM key-pair. ARC may be less reliable, depending on recipient host policy (including whether it participates in ARC at all). Steve

3 years, 5 months

[MM3-users] Re: list footer questions

by Mark Sapiro

On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://wiki.list.org/x/4030707> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- 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: AH01102: error reading status line from remote server 172.19.199.3:8000

by Abhilash Raj

Hi Henrick, On Tue, Jul 18, 2017, at 04:54 AM, Henrik Rasmussen wrote: <snip> > raise ImproperlyConfigured("No Facebook app configured: please" > ImproperlyConfigured: No Facebook app configured: please add a SocialApp > using the Django admin This is a known issue, it happens because the Facebook is added as a default service provider but it crashes the login page if it is not configured. As a get around, you can either remove the Facebook as a service provider from the Django's INSTALLED_APPS variable, or you can login into the Django's admin console and setup Facebook as a login provider. Documentation should have instructions on both, please ask again if anything isn't clear there. > > When I do sign in, I get the following from uwsgi-error.log <snip> > File > "/usr/local/lib/python2.7/site-packages/django/core/mail/backends/smtp.py", > line 100, in send_messages > new_conn_created = self.open() > File > "/usr/local/lib/python2.7/site-packages/django/core/mail/backends/smtp.py", > line 58, in open > self.connection = connection_class(self.host, self.port, > **connection_params) > File "/usr/local/lib/python2.7/smtplib.py", line 256, in __init__ > (code, msg) = self.connect(host, port) > File "/usr/local/lib/python2.7/smtplib.py", line 316, in connect > self.sock = self._get_socket(host, port, self.timeout) > File "/usr/local/lib/python2.7/smtplib.py", line 291, in _get_socket > return socket.create_connection((host, port), timeout) > File "/usr/local/lib/python2.7/socket.py", line 575, in > create_connection > raise err > socket.error: [Errno 111] Connection refused This is because you haven't setup Django to send emails. When you register an email with Django, it needs to be able to verify that it is a valid email address for which it should be configured to send email. See the documentation on how to do so at docs.mailman3.org asynchronous.in/docker-mailman/ > Henrik > > -----Oprindelig meddelelse----- > Fra: Abhilash Raj [mailto:raj.abhilash1@gmail.com] > Sendt: 17. juli 2017 18:04 > Til: mailman-users(a)mailman3.org > Emne: [MM3-users] Re: AH01102: error reading status line from remote > server 172.19.199.3:8000 > > Hi Henrik, > > On Mon, Jul 17, 2017, at 02:31 AM, Henrik Rasmussen wrote: > > I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the > > right CSS layout I installed Apache on the Mailman server outside Docker, > > as advised by Abhilash Raj and Alexander Klotz. > > > > My Mailman server is on a secured network and the https connection from > > Internet will be handled by proxy servers, so I will be using http (port > > 80) between proxy-servers and Mailman server. > > > > But when I sign in (currently via an SSH tunnel to the Mailman server > > from my workstation) I get "Internal error: [client ::1:41912] AH01102: > > error reading status line from remote server 172.19.199.3:8000, referer: > > http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F" > > > Output from logs might be more helpful to debug what is wrong. They are > present at `/opt/mailman/web/logs/mailmanweb.log` for Django. You may > also find some other log files there which are related to uwsgi, the > WSGI server that is used to interface Django with Web Servers like > Apache. > > > If I type a wrong password, I am just warned about that, so the problem > > appears when log in is accepted. > > > > I expect that it is because I connect to localhost:80 through SSH tunnel. > > What do I miss in my Apache configuration on the Mailman server to avoid > > this problem? > > > > <VirtualHost *:80> > > ErrorLog /var/log/httpd/error_log > > LogLevel warn > > CustomLog /var/log/httpd/access_log combined > > > > ServerAdmin root(a)example.foo > > ServerName list.foo.bar > > Alias /static /opt/mailman/web/static > > Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico > > > > ProxyPassMatch ^/static/.* ! > > ProxyPass / http://172.19.199.3:8000/ > > ProxyPassReverse / http://172.19.199.3:8000/ > > > > <Directory /> > > Allow from all > > Require all granted > > </Directory> > > > > <Directory /opt/mailman/web/static/hyperkitty/img/> > > Allow from all > > Require all granted > > </Directory> > > > > # ssl config here ... > > </VirtualHost> > > > > > > Thanks, > > Henrik Rasmussen > > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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/ -- thanks, Abhilash Raj

9 years, 2 months

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

by Allan Hansen

My 2 cents’ worth: When moving to MM3 from MM2, the latter of which I (relatively) easily installed myself, I read what I could find and went on installing MM3. I soon ran into trouble, namely somewhere around the hooking up of the web server. I ran into a thicket that I could not decipher. Then I asked the person who now hosts the server. He soon ran into trouble at around the same place (as far as I remember). I then asked someone who had been very helpful with MM2 to do the installation. He's a professional. He soon ran into trouble. I don’t know where, but he tried over several weeks to get it going. The trouble? Finding the correct documentation. Understanding the documentation, which is not exactly clear. Doing what the documentation says, if it says it, and things not working as they should. I then asked Brian, who has helped a lot of people (like many of you have). He did the installation very quickly and with no trouble. Don’t tell him this, but it was money well spent! :-) Yours, Allan Hansen hansen(a)rc.org > On Feb 25, 2021, at 18:38 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 2/25/21 8:28 PM, Abhilash Raj wrote: >> Thanks Brian, this looks quite comprehensive in the details. The only >> thing I am a bit concerned about is granting sudo privileges to the >> Mailman user. It really shouldn't have sudo given that Mailman and >> Django are supposed to run as mailman user. Any compromise of >> the Django application will provide the attacker root on the machine. > > Thanks for pointing that out. I have removed that step. It really wasn't needed. > >> Is there a specific reason that you chose to go with an entirely new doc > > Yes. Just from observing the communications on this list, there are multiple ways to install Mailman 3 which produces installation issues, database problems, outdated apps, etc. My document produces a VERY stable installation of Mailman 3 and one that is easy to maintain and update. It is also very comprehensive covering not just Mailman Suite, but the configuration of an entire server environment. Personally I think the choice of Debian, NGINX, Postfix, and PostgreSQL makes for a long and loving relationship with Mailman 3 but I do understand everyone has their own environment that they want to work with. My guide represents a very stable and easily maintained environment for me and hopefully others. > >> rather than helping to improve the existing one? Several parts of it (at >> least the ones that official guide covers) seems similar to me and is >> duplicate information that at least two people are going to spend time >> writing and maintaining in future. > > Is there an official guide? See that is the problem. I did not know there was an official guide. Because every time I tried finding documentation in the past using Google searches, I got fed outdated information. So for me the guide that I came up with, works great for me and if no one else uses it, I certainly will. > > Your guide, by nature has to be minimalistic to accommodate all the various server environments out there. My is meant to be narrow but comprehensive. > > >> Is it something about the contribution process to the official documentation >> that makes it hard for people to contribute? Most of the pages at >> docs.mailman3.org or come from this[1] repo and use Sphinx to build and >> REsT formatting (.rst). >> >> [1]:https://gitlab.com/mailman/mailman-suite-doc > > Well I don't know much about any of the above approach to documentation. So I would say that is a hindrance. > > >> I am just trying to understand how can we lower the barrier for community >> members to help contribute to existing docs instead of them having to create >> new ones. Specifically around installation, since that tends to get stale often >> when depedent packages change or a new dependency is added that >> breaks the installation. > > I had to update my guide twice due to recent changes made to the installation process such as the addition of the Dart Sass section and the problem with the cryptography module when installing Hyperkitty. While my guide covers these new hurdles to a new installation, I don't think yours says anything about them. The Dart Sass section came from Mark's comments on this list. > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 7 months

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

by Stephen J. Turnbull

Andreas Barth writes: > public: anyone can subscribe and read the archive. This is already possible, more or less the default list configuration. "Subscribe and read archive" involves multiple separate list attributes, enforced by three separate applications. Subscription policy is controlled by whether you need approval of an admin or not, and whether you need to verify your email or not, plus the ban lists. Archive access (assuming you have one at all) is contrlled by a different list attribute, archive_policy. Core has final say on subscriptions, but Postorius could do it if email subscriptions are disabled. HyperKitty handles the archive permissions. These various aspects are currently quite loosely coupled. > restricted: for employees (or members - or whatever) only. So they > could subscribe themself. The archive and posting may be restricted > to subscribers or to anyone in that group - both would be working > for me. I think this can be implemented with the controls we already have. The basic idea is to handle the "anyone in that group" case by mass subscribing and setting the subscription to no-mail. Obviously, this is most practical with a fairly static membership (eg, students at a school). A fluid membership (for example, a volunteer organization) would be made easier to manage with a "member adapter" to an external database to handle the "do I know this person" questions. ("Member adapter" is Mailman 2 terminology, I don't know if it's exactly the same in Mailman 3; it does or *should* exist in Mailman 3, though.) It's possible that we could make this easier to configure with some changes to core. However, if this is as close to what you need as I think it is, I would advise against vendoring Mailman, and instead writing some scripts to help manage mass subscription, or create the member adapter. > (How to know who is allowed to subscribe is another question - having > an internal mailing list which contains all the members just for this > purpose would be ok for me.) That's helpful to know. This sounds very similar to the Systers approach, where the Mailman core User database is the authoritative membership database for the organization. > private: hand-selected people, think about e.g. board or steering > committees internal discussions. Of course, the archive (if there is > any) should be restricted to the actual members. Posting to these > lists is currently not restricted, so no derivation needed from the > current set in postorius. This is already possible by requiring admin approval, or by setting the ban list to something that matches everything like "^.".

5 years, 4 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 17:06, Mark Sapiro wrote: > On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >> A mail was sent to root on the localhost with the following content: >> >> Return-Path: <root(a)giesler.za.net> >> X-Original-To: root@localhost >> Delivered-To: root@localhost >> Received: from mailman.fast.za.net (localhost [IPv6:::1]) >> by mailman.localdomain (Postfix) with ESMTP id 2174A120A5B >> for <root@localhost>; Sun, 28 Jul 2024 13:11:03 +0000 (UTC) >> Content-Type: text/plain; charset="utf-8" >> MIME-Version: 1.0 >> Content-Transfer-Encoding: quoted-printable >> Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: >> /accounts/login/ >> From: root(a)giesler.za.net >> To: root@localhost >> Date: Sun, 28 Jul 2024 13:11:03 -0000 >> Message-ID: <172217226313.2150.10895652368679013629(a)mailman.fast.za.net> >> >> Internal Server Error: /accounts/login/ >> >> SMTPRecipientsRefused at /accounts/login/ >> {'roland(a)giesler.za.net': (454, b'4.7.1 <roland(a)giesler.za.net>: >> Relay acce= >> ss denied')} > > This is mail from django-allauth, not from Mailman. Your settings in > mailman.cfg do not affect how this mail is sent. See > https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend for > the Django settings for this. These settings from the Django docs look like the ones in mailman.cfg. Do I have to set them somewhere else too? SMTP backend¶ <https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend> /class/|backends.smtp.||EmailBackend|(/host=None/,/port=None/,/username=None/,/password=None/,/use_tls=None/,/fail_silently=False/,/use_ssl=None/,/timeout=None/,/ssl_keyfile=None/,/ssl_certfile=None/,/**kwargs/)¶ <https://docs.djangoproject.com/en/5.0/topics/email/#django.core.mail.backen…> This is the default backend. Email will be sent through a SMTP server. The value for each argument is retrieved from the matching setting if the argument is|None|: * |host|:|EMAIL_HOST| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST> * |port|:|EMAIL_PORT| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_PORT> * |username|:|EMAIL_HOST_USER| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST_…> * |password|:|EMAIL_HOST_PASSWORD| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST_…> * |use_tls|:|EMAIL_USE_TLS| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T…> * |use_ssl|:|EMAIL_USE_SSL| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S…> * |timeout|:|EMAIL_TIMEOUT| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO…> * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K…> * |ssl_certfile|:|EMAIL_SSL_CERTFILE| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C…> The SMTP backend is the default configuration inherited by Django. If you want to specify it explicitly, put the following in your settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" If unspecified, the default|timeout|will be the one provided by|socket.getdefaulttimeout()| <https://docs.python.org/3/library/socket.html#socket.getdefaulttimeout>, which defaults to|None|(no timeout).

2 years, 2 months

[MM3-users] Re: Postorius permissions granularity

by Liam Reilly

Stephen J. Turnbull wrote: > Liam Reilly writes: > > Is there a way to have more granular permissions in Postorius than > > either User or Superuser? > > Not without additional code. It couldn't be a plugin. It would have > to be a fork of the main Postorius code at first (ie, you would be > responsible for patching it and merging our public releases, there > would not be regular releases). I doubt it would be merged in a near- > future release, at least I wouldn't be confident enough to do that > myself without beta testing on a branch. > I don't think it would be hard to implement a "restricted superuser" > role. The annoying part would be figuring out where to apply it, as > the "authenticated user", "moderator", and "superuser" roles are > implemented via Python "decorators" applied to the functions > implementing the various features. And the changes would likely need > to be pervasive in page templates, forms, and functional code. > > The user permissions that are configurable under /admin/auth/user/ > > do not seem to have any effect. > > As far as I know the only bit that has big effects is "superuser", and > there's a "staff" bit that has some effect on the superuser IIRC. > Everything else is implemented in Postorius. > > We have a helpdesk team that would benefit from being able to > > access all list pages in the same way as a Superuser, but without > > the ability to accidentally delete the mail domain for example. > > I almost started on this two years ago, but that customer wanted it > for individual lists rather than a helpdesk team, and realized that > all the relevant owners would be satisfied with promoting moderators > to owner. So it didn't happen. > Footnotes: > [1] There are several consultants who would be capable of maintenance > in the consultant list on the wiki, and more than one who would be > able to design and implement the code if you're in a we-want-it-enough- > to-pay hurry. > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan Thanks Stephen. It looks like we're going to take the simple route of the helpdesk using existing screen sharing tools to assist list owners, rather than providing elevated access in Postorius. Many of our list owners are not technical and so the transition from Mailman 2 to 3 has been challenging for some.

9 months, 2 weeks

[MM3-users] Re: Change Member's Address

by Dennis Putnam

8 months, 2 weeks

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Stephen J. Turnbull

Nelson Strother writes: > I did not intend to imply that `mailman start` (predictably) > consumes more time than `mailman restart`. Both are lengthy and > variable; You did say something about "30min" I believe. I don't understand why it would take anywhere near that long. For example, I'm working with a site with ~20,000 lists, and it only takes a few seconds. Oh ... wait ... are you using Postfix as the MTA? The supplied Postfix MTA interface rebuilds the list aliases database on every (re)start, and that's an O(#lists^2) process the way Mailman does it. Postfix doesn't actually use the file to route mail, it always goes to lmtp:127.0.01 or something like that. So I configured Postfix to probe for existence of the list in Mailman's database. I think Postfix has plugins for all Mailman-supported databases (PostgreSQL, MySQL/MariaDB, SQLite3). I can provide the changes needed for this for PostgreSQL right away, if you're a MySQL site I can give you the PostgreSQL config to give you the idea, but I may be sslow if you want advice about the MySQL config. It's pretty straightforward, though. > I do not yet understand how to make use of these clues, but at > least one can see an epitaph from each deceased process. I don't understand them either. The only thing I can think of is that a runner may try to access Mailman core, timeout, and crash during the long startup. At least the MTA reconfig would make the restart cycle a lot less painful. Note: this is NOT a Mailman-supported config (or even contrib quality) yet, but I'm pretty confident of the theory and it is working well in QA testing. Regarding the "alpha" status of the config, one Mailman 3 instance can support multiple domains, but the Postfix docs say not to hit the database for the "domain exists" check. If you aren't going to add additional Mailman domains, then this doesn't matter (the domain list file produced by the stock Mailman postfix config will work), but if you do add or remove domains, you either need to configure Postfix to hit the database for the "domain exists" check too contrary to Postfix's advice, or you'd need to manage the domain list file by hand. In any case, you could use this config for debugging, and go back to the tried and true aliases file approach for production. And as I indicated I'm somewhat available on a best-effort basis for trouble-shooting.

3 years, 3 months

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Chihurumnaya Ibiam

On Sat, Feb 7, 2026 at 7:28 AM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Chihurumnaya Ibiam via Mailman-users writes: > > On Fri, Feb 6, 2026 at 7:57?AM Stephen J. Turnbull <steve(a)turnbull.jp> > > wrote: > > > Going by your earlier assumption that perhaps the same thing > > doesn't happen for mailbox_transport, how would I use that as a > > fallback in such cases? > [...] > > mailbox_transport currently doesn't have a value. > > Just use the normal configuration for local recipients: > > local_recipient_maps = > proxy:unix:passwd.byname > $alias_maps > hash:/path/to/postfix_lmtp > > # default, I put aliases in /etc/postfix > alias_maps = hash:/etc/aliases > # you may want to set > virtual_alias_maps = > I'm not sure this would solve the problem because there are no users on the host, just me and root. It'll most likely keep bouncing those confirmation emails, I need to test this again and see if I still get the same error as I've been able to receive bounce messages. > > > No, weblate isn't supposed to receive email. It runs a service that > > sends emails just like MM3. Yes, postfix is also the MTA at > > weblate. > > OK, then what "lists" is trying to send to "weblate" is probably a DSN > (Delivery Status Notice). I would put any addresses that are > authorized to send to mailing lists in a table in virtual_alias_maps > and send them to a local mailbox. The local mailbox can be either a > user's mailbox (such as root or mailman) or it could be aliased to a > file. > Okay. > I can include subdomains, but I don't see a reason for doing so at > > the moment. > > OK > > > One thing I had done to remediate the error - which didn't do > > anything from the logs - is add check_client_access > > hash:/etc/postfix/client_access in smtpd_client_restrictions. > > That is what allows remote MTAs to talk to your local Postfix. The > message in the log was *outgoing*. > > Yes, I wonder why this host is trying to connect to those machines. I know that those machines send their logs to a list, that's about it. > > I don't know why Postorious and Hyperkitty didn't show up at the time, > but > > I just ran lsof and this is the output; > > $ lsof -i TCP(a)127.0.0.1 -i 'TCP@[::1]' | grep 24 > [...] > > Which shows the expected ports being listened on, I'll assume the > > issue with Postorious was probably because the mailmanweb service > > stopped at some point > > OK, the listeners are there as expected and I think you're right, you > just ran lsof the last time when the web UIs were stopped. > > > > I don't have an idea what's going on yet. The mail you see being > > > sent in the logs, is that to a gmail address? Or is it a > > > sugarlabs.org address? (Both of these seem to be problematic at > > > the moment.) > > > It was to a sugarlabs.org address, I've been able to receive mail > > owner messages to my inbox, I configured a gmail address as the > > admin for Mailman suite, which indicates that mail delivery works > > as expected. > > Hm. That doesn't help me figure out what's happening. We'll see if > the changes so far help. > > > Yes, this probably because I haven't properly configured user > > lookup on dovecot. > [...] > > At the moment, I've disabled the service and have no configurations > > for it. I commented out my earlier configs before disabling it. > > Just getting dovecot out of the loop should help a lot. Deleting the > mailman_transport setting and setting Mailman's lmtp_port to 8024 > should clear up most list-traffic problems. > Yes, that did help. I need to test email confirmation again and see what's going on in the logs, will do that later today. > > > All the configurations that are supposed to contain the FQDN does; > > mydestination, mydomain, myhostname. > > > > Am I missing any? > > I don't think so. I think I mentioned earlier that the shortname > might be a mail client setting Message-ID, not Postfix. > Alright. > > Regards, > Steve > > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan > -- Ibiam Chihurumnaya ibiamchihurumnaya(a)gmail.com

7 months, 3 weeks

[MM3-users] running a script for the mailman-shell (to discard held messages) gives errors about a package argument for relative import

by stephan.edel＠gmx.net

Our organization has been been communicating through about a dozen mailing lists, running on mailman, with ~200 subscribers, for 15-odd years. After Debian 10 LTS ran out, I had to upgrade our organisations Debian server, forcing me into mailman3. I haven't managed, yet, to get the web interface running, so I need to do the most urgent tasks in the shell for now. I have found out that, for example, to discard all held messages from the list "motor", I need to > sudo -u list mailman shell -l motor.our-server.de and in the shell, >>> from mailman.app.moderator import handle_message >>> rdb = IListRequest(m) >>> for req in rdb.held_requests: ... if req.request_type == RequestType.held_message: ... handle_message(m, req.id, Action.discard) > commit() Now, obviously, I put these exact lines in a script, so I don't have to type it out every single time, and try to run it using > sudo -u list mailman shell -l testlist.our-server.de -r ./mm_discard_held.py but that invariably gives me ------------------------ Traceback (most recent call last): File "/usr/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'mailman')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/commands/cli_withlist.py", line 294, in shell r = call_name(dotted_name, m, *run_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/__init__.py", line 121, in import_module raise TypeError(msg.format(name)) TypeError: the 'package' argument is required to perform a relative import for './mm_discard_held' ------------- I've tried a PYTHONPATH=/root/bin , where mm_discard_held.py lives, as suggested. I've tried moving it to the path where the mailman binary lives, as suggested. I always get the same result. What else can I do? Thank you.

2 years, 3 months

[MM3-users] Re: Error on timeout vs retry values

by Robert Moody

Thanks I will give that a go a bit later today and see what happens. ⁣Get BlueMail for Android On 19 Jul 2021, 07:34, at 07:34, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > >On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >> Hi everyone, >> >> I have recently setup a new mailman3 service using the venv method. >> Everything is functionally working however I keep getting an error >sent >> to the mailman email every min which I can not seem to figure out >why. >> >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: >> UserWarning: Retry and timeout are misconfigured. Set retry larger >than >> timeout, >> failure to do so will cause the tasks to be retriggered >before >> completion. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry for >details. >> See https://django-q.readthedocs.io/en/latest/configure.html#retry > >> for details.""" >> >> I have edited the timeout and retry values in the >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file >and >> restarted both mailman and mailman-web however this still keeps >repeating. > >You shouldn't edit files in `site-packages` directory as they are part >of the package itself and could cause issues. > >What you want to do is override it in your settings.py (or >settings_local.py) file >for Django. I am not sure which guide you followed to install Mailman, >but it >should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). > > >It should look something like this > >https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web.sett… > >Just the value of retry should be just > than timeout as the error >says, so >not necessarily same values, but so far 300 and 360 has been working >good for us and I haven't seen any report to increase them. > > >> >> Any ideas? >> >> Regards, >> >> Robert >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> _______________________________________________ >> 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/

5 years, 2 months

[MM3-users] Please help - Held message is crashing mailman.

by Alex King

Hi, I've used mailman a lot in the past, and decided to install mailman3 in a recent install. I'm unimpressed so far, it seems buggy. Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. After a few messages, I now can't go to the "Held Messages" in postorius, I get a 500 error. I tried to interact on the command line, but could not work out how. Reading https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html and https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, I tried: # mailman shell Welcome to the GNU Mailman shell >>> command = cli('mailman.commands.cli_withlist.shell') Traceback (most recent call last): File "/usr/lib/python3.6/code.py", line 91, in runcode exec(code, self.locals) File "<console>", line 1, in <module> NameError: name 'cli' is not defined I did a lot of reading of the manual and googled, but I have no idea where the cli object is supposed to come from.....? The documentation is confusing. Anyway, after some trial and error, i found: # mailman shell Welcome to the GNU Mailman shell >>> list_manager = getUtility(IListManager) >>> m=list_manager.get("committee(a)[redacted].org") >>> from mailman.interfaces.requests import IListRequests >>> requests = IListRequests(m) >>> [x for x in requests.held_requests][0].id 8 >>> requests.get_request(8) Traceback (most recent call last): File "/usr/lib/python3.6/code.py", line 91, in runcode exec(code, self.locals) File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line 120, in get_request result.data_hash, expunge=False) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line 138, in confirm value = json.loads(keyvalue.value) File "/usr/lib/python3.6/json/__init__.py", line 354, in loads return _default_decoder.decode(s) File "/usr/lib/python3.6/json/decoder.py", line 339, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode obj, end = self.scan_once(s, idx) json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) It seems something was written out to disk that can't be read in for some reason (assuming a json object on disk?) How do I debug this further? How do I find the json being decoded? Any help would be appreciated. (I found mailman2 just worked, I was happy with that.) (My colleague posted a bug about this I believe but I don't have the link to that.) Thanks, Alex

7 years, 5 months

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

by Allan Hansen

Thank you, Stephen. Yes, I have verified that the users will be subscribed once the moderator accepts their subscription requests. The tricky time is between the non-member record is created and the moderator accepts the application. Many of them will try to post before their subscription is approved (some moderators are good at procrastinating). During this time the user thinks that the subscription has been entered, but is not able to send/receive messages. Then they complain to me... While some of the users and moderators may have visual impairments (well, it's possible that even a majority wears glasses - I do), the bigger issue is that most are not techies, and some are very much not techies. They are brilliant in other ways and Mailman has been a wonderful tool for them all to communicate and organize, but it's also a bit quirky. Yours, Allan On 9/16/22, 23:28 , "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: 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. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

Hi Rafael, On Tue, Jul 11, 2017, at 07:32 AM, Rafael Mora wrote: > Hello, > > I want to install mailman 3 in a centos 7 virtual machine. I'm following > these steps and I cannot make it work: I am wondering if you are interested to setup a development environment or use Mailman 3? These instructions below are for working on Mailman, if you just need to deploy, instructions here[1] would be the best. > 1. `cd ~` > 2. `git clone https://gitlab.com/mailman/mailman.git` > 3. `cd mailman` > 4. `virtualenv -p python3 venv` > 5. `source venv/bin/activate` > 6. `python setup.py develop` > 7. I am pretty sure this setup command will place a configuration file > into > `~/mailman/var/etc/mailman.cfg`. Edit this file. > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > 8. `mailman info` can confirm which configuration file is in use > 9. `mailman start` will start up Mailman 3 Core. This is what the parent > background process command looks like in `ps -ef`: > `/home/ubuntu/mailman/venv/bin/python > /home/ubuntu/mailman/venv/bin/master > -C /home/ubuntu/mailman/var/etc/mailman.cfg` Looks like you are working as the ubuntu user here and the the virtualenv that you created exists at `/home/ubuntu/mailman/venv`. > I also tried the steps on the website > https://wiki.list.org/DEV/SetupDevEnvironment > but it doesn't work either > > What do you suggest? > > This is what I get from console: > > > [root@localhost ~]# cd dev/ > > [root@localhost dev]# cd mailman/ > > [root@localhost mailman]# source venv3/bin/activate Why do you try to user a different venv as a root user here? If you'd just try: $ source /home/ubuntu/mailman/venv/bin/activate and then try $ mailman start things would work! However, this would be a different instance of mailman and would create the new configuration (and the entire var directory) at the directory you run this command from. If you want to inhibit this, you can either use the -C flag, or set MAILMAN_CONFIG_FILE environment variable to point to your one single configuration file. > > (venv3) [root@localhost mailman]# cd mailman/ > > (venv3) [root@localhost mailman]# ls > conf.py COPYING data README.rst src > unittest.cfg > contrib coverage.ini MANIFEST.in setup.cfg template.py > copybump.py cron port_me setup.py tox.ini > > (venv3) [root@localhost mailman]# cd .. > > (venv3) [root@localhost mailman]# mailman start > Starting Mailman's master runner > /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': > [Errno > 2] No such file or directory > > (venv3) [root@localhost mailman]# > > Thank you > -- Hope that helps! [1]: http://docs.mailman3.org/en/latest/prodsetup.html -- thanks, Abhilash Raj

9 years, 2 months

[MM3-users] Re: Mails are stuck in Mailman Pipeline Queue

by Shashikanth Komandoor

Thank you Mark. This solution worked fine for me. On Sun, Mar 27, 2022 at 9:58 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/26/22 21:01, Shashikanth Komandoor wrote: > > > > But the below trace back is observed during mailman service stopping: > > > This doesn't say much ... > > > ...> Mar 27 09:01:22 2022 (5864) Uncaught runner exception: > > Mar 27 09:01:22 2022 (5864) Traceback (most recent call last): > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > > line 173, in _one_iteration > ... > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > > line 114, in signal_handler > > raise RunnerInterrupt > > mailman.interfaces.runner.RunnerInterrupt > > Mar 27 09:01:22 2022 (5864) SHUNTING: 1648351882.6693938+ > > c2e6ed709646a7680c73059b52d2f0451836e591 > > Mar 27 09:01:22 2022 (5864) digest runner exiting. > > Above, digest runner was interrupted in processing and shunted the > message it was working on. > > and below, pipeline runner was interrupted in processing and shunted the > message it was working on. > > > Mar 27 09:01:22 2022 (5860) Uncaught runner exception: > > Mar 27 09:01:22 2022 (5860) Traceback (most recent call last): > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", > > line 37, in _dispose > > process(mlist, msg, msgdata, pipeline) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", > > line 50, in process > > handler.process(mlist, msg, msgdata) > > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > > mailman/handlers/member_recipients.py", line 84, in process > > for member in mlist.regular_members.members > > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > > mailman/handlers/member_recipients.py", line 83, in <genexpr> > > recipients = set(member.address.email > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > > line 239, in members > > yield from self._get_members(DeliveryMode.regular) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > > line 226, in _get_members > > if member.delivery_mode in delivery_modes: > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > > line 205, in delivery_mode > > return self._lookup('delivery_mode') > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > > line 167, in _lookup > > pref = getattr(self.address.preferences, preference) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > > line 287, in __get__ > > return self.impl.get(instance_state(instance), dict_) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > > line 723, in get > > value = self.callable_(state, passive) > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > > line 760, in _load_for_state > > session, state, primary_key_identity, passive > > File "<string>", line 1, in <lambda> > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > > line 850, in _emit_lazyload > > session.query(self.mapper), primary_key_identity > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/ext/baked.py", > > line 603, in _load_on_pk_identity > > setup, tuple(elem is None for elem in primary_key_identity) > > The above says the runner was doing a database lookup. This may be a > coincidence or there may be some database locking issue that underlies > the issue with the pipeline runner. > > > > File > "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > > line 114, in signal_handler > > raise RunnerInterrupt > > mailman.interfaces.runner.RunnerInterrupt > > Mar 27 09:01:22 2022 (5860) SHUNTING: 1648351882.8537986+ > > 9bf59cb23a71a4bae65536bfdbec0abb261adaa0 > > Mar 27 09:01:22 2022 (5860) pipeline runner exiting. > > > I suggest doing the following assuming your Mailman database is not > sqlite3 (if it is, just do step 2): > > 1) Stop mailman core and maybe other mailman services too. > 2) Assuming the two shunted messages are still in Mailman's shunt queue, > run `mailman unshunt` to unshunt them. If there are more shunted > messages, inspect them with `mailman qfile` to see if you want them, > They may be spam. > 3) Restart your database server. > 4) Start Mailman core and any other stopped services. > > Also, look in the database server logs for any issues. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 6 months

[MM3-users] Re: How to debug bounces?

by Stephen Daniel

Thanks. Looking at one of the notifications, I see this is a DKIM failure.: The response from the remote server was: 550 5.7.9 This mail has been blocked because the sender is unauthenticated. Yahoo requires all senders to authenticate with either SPF or DKIM. Authentication results: DKIM = FAILURE - SPF XXX.org with ip X.Y.Z.W = SUCCESS. See https://senders.yahooinc.com/smtp-error-codes/#authentication-failures for more information. This has worked for a long time. What would suddenly cause DKIM failures? On Thu, May 7, 2026 at 11:02 AM Paul Tomblin via Mailman-users < mailman-users(a)mailman3.org> wrote: > The first thing I’d do is look at the outgoing mail logs. If it’s bouncing > 1/3rd of your users, it’s very likely it’s one or two whole domains that > are bouncing, probably because your IP has been black listed or you don’t > have DKIM set up right or something like that. The outgoing mail logs might > tell you that. Also, don’t you get a copy of the “disabling bounce”? I > always get one of that when somebody gets bounced off the list. The bounce > message itself usually gives you a clue as well - I think it’s in an > attachment called email.eml or something like that. > > On Thu, May 7, 2026, at 10:39 AM, Stephen Daniel wrote: > > Colleagues -- > > > > I run a small mailman3 server with perhaps 10 lists. All the lists are > > small. > > > > Over the past two days about a third of the users in my most active list > > have been disabled by bounces. I assume the problem is with my setup, not > > with all of those users. > > > > How do I debug this? Can I see the text of any of the bounce messages to > > understand why the emails bounced? > > > > This issue might stem from my running somewhat old software. Currently > > running mailman 3.3.5. > > > > Thanks! > > > > -- Stephen Daniel > > _______________________________________________ > > 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 ptomblin(a)xcski.com > > -- > Paul Tomblin > _______________________________________________ > 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 >

4 months, 3 weeks

[MM3-users] Intermittent: pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77

by Torge Riedel

|Hi list, sometimes I get the following error in mailman core's log: "pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77". I attached the full log after this mail. I check the provided link in the log (|||http://sqlalche.me/e/2j85|) and also searched for it on the internet and found the following possible reasons: 1. DB user does not have permissions at all -> I doubt that, because in general mailman is working ok 2. DB user is not allowed to connect from remote -> I doubt that too, because everything is on one host and DB user is allowed to connect from localhost 3. Multi-Threading -> pymysql is mentioned to be not thread-safe and each thread needs its own connection May this be caused by multi-threading? What do I have to do (is there anything I can do?) to solve this on my own?||||| Kind regards Torge || |Full log follows: [2021-05-23 07:31:45 +0200] [8244] [ERROR] Error handling request /3.1/lists?advertised=true&count=10&page=1 Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context cursor, statement, parameters, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute cursor.execute(statement, parameters) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute result = self._query(query) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query conn.query(q) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result result.read() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read self._read_result_packet(first_packet) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet self._get_descriptions() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions field = self.connection._read_packet(FieldDescriptorPacket) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet % (packet_number, self._next_seq_id)) pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77 The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 322, in on_get resource = self._make_collection(request) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 172, in _make_collection request, self._get_collection(request)) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 167, in _paginate return list_start, total_size, collection[list_start:list_end] File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/utilities/queries.py", line 42, in __getitem__ return self._query[index] File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3149, in __getitem__ return list(res) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3481, in __iter__ return self._execute_and_instances(context) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3506, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1020, in execute return meth(self, multiparams, params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_clauseelement distilled_params, File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1324, in _execute_context e, statement, parameters, cursor, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1518, in _handle_dbapi_exception sqlalchemy_exception, with_traceback=exc_info[2], from_=e File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ raise exception File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context cursor, statement, parameters, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute cursor.execute(statement, parameters) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute result = self._query(query) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query conn.query(q) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result result.read() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read self._read_result_packet(first_packet) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet self._get_descriptions() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions field = self.connection._read_packet(FieldDescriptorPacket) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet % (packet_number, self._next_seq_id)) sqlalchemy.exc.InternalError: (pymysql.err.InternalError) Packet sequence number wrong - got 102 expected 77 [SQL: SELECT mailinglist.list_id AS mailinglist_list_id, mailinglist.preferred_language AS mailinglist_preferred_language, mailingli$ FROM mailinglist WHERE mailinglist.advertised = true ORDER BY mailinglist.list_id LIMIT %(param_1)s] [parameters: {'param_1': 10}] (Background on this error at: http://sqlalche.me/e/2j85) |

5 years, 4 months

[MM3-users] Re: Long-shot cry for help

by Mark Sapiro

On 6/3/21 6:34 AM, David Partain via Mailman-users wrote: > Hi, > > I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... > > 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. You may need to set the character set and collation for the DB or the server to utf8mb4. See https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html for MySQL (I don't know about MariaDB. > /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. Python3 does not create .pyc files in the same directory as the .py. They are created in a __pycache__ sub-directory. See https://www.python.org/dev/peps/pep-3147/ for details. However, you seem to be still running a Python 2.7 version of Django et al. In this case, if it's not creating a .pyc, it is likely because it doesn't have permission. That is not a problem. If there's no .pyc, it just runs the .py. > The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" Tell your users that smiley faces and other non-base-plane unicode emojis in email subjects add no value ;) > I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. I don't know what that is either. The underlying database access is via Django. See, e.g., https://docs.djangoproject.com/en/3.2/ref/databases/ However, it is not the MySQL queries that are the issue. > Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... > > 2. There's this one curious cron job... > > * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings > > (yes, I know python2.7 is a problem... see the last paragraph below). > > These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: > > www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings > > What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. > > Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? You don't NEED to run this job. In the latest releases there are no minutely jobs anyway. Prior to HyperKitty 1.3.0 the update_index job was run minutely to update the search indexes with new posts, but now it's hourly. You probably have a huge backlog of unindexed posts causing this job to run for a long time (Whoosh is particularly slow at indexing, Xapian is much better). I suggest for now, you quit running the minutely jobs and just try manually running ``` python2.7 /usr/bin/django-admin runjob update_index --pythonpath /usr/share/mailman3-web --settings settings ``` which will probably run for hours if not days. Then after it completes, you can add that to cron to run hourly. > Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Good plan. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: My list has been switched from public to private archives, but they are still visible

by Enrique Terrazas

I am having a very similar issue. Here is what I have found: There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings > Archiving and they are: Public archives Private archives Do not archive this list In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists > Mailing List object(x) > Archive policy: never private public I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged? Enrique > On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: >> Can anyone help with this? >> >> I set my list to private archives today. Up until then, it was pubic. >> And yet, if you go to the list page, you will see that if you click >> archives (top left), you can see them. (Filled with a bunch of tests >> posts for now) > > This change takes a bit of time to sync up Hyperkitty. THere is a daily > cron job which syncs this information from Mailman Core. > > I have made a change which should fix this problem and the process would > become synchronous. > > You can run `python manage.py runjobs --daily` command to force sync > that information. > >> >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… >> >> Am I misunderstanding what a private archive is? > > Not really, your expectation is right. > >> >> Is something wrong with my setup (which is hosted)? >> >> Thank you. >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… >> > > -- > 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

7 years

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

by David Partain

Hi Mark, Thank you for your kind answer. While I've been running a mailman site for many years, I'm just getting going with mailman3 (and migrating my 1400 lists...) and I feel lost occasionally :) I wrote: > I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: > > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.mysql', > 'NAME': 'mailman3web', > 'USER': 'mailman3web', > 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', > 'HOST': 'localhost', > 'PORT': '', > 'OPTIONS': { > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > 'charset': 'utf8mb4', > }, > } > } > > and restarted stuff, but I cannot tell that it has changed anything. You responded: > That should do it. I think the original message should have been saved > as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. That directory has all of the messages sent to that list: # ls /var/lib/mailman3/archives/hyperkitty/spool/ 1611827925.8030825+925c996b9b6020ee18e9a689ce23384855159f77.pck 1611827926.1923075+e728f3c29c1fe6eeeca641314cdba7007cb6e132.pck 1611827925.8917305+d16b7004bdbbef98ce40fb8ee70e492715d1607d.pck 1611827926.2623458+1aac13b50d8e7f32eb14d13e6559656aa8f3bd10.pck 1611827925.9594557+7ad2a910b5ee9142c88f0bf26c60c6df960d4262.pck 1611827926.3488555+04a540651c5f829751518433e1c54168ab63a38b.pck 1611827926.0404096+a5e745f51a9f7d541aeb770a89604be17019f3c5.pck 1611827926.4206145+de861eec6404d0c8f9f8bdb180e29bff2de7c52b.pck 1611827926.1167526+0aa63639a4ec102bf63522827637e75e6a2b092a.pck > If this is the case, it would have been retried and produced the same > error with each new post, and after you made the above change, it would > have been archived and the errors stopped. > Are you saying you are still seeing these errors? If so, it may be a > different error. What is the exact error message? We don't need all the > Django stuff, just the part equivalent to > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\xF0\x9F\xA4\xA3\xF0\x9F...' for > column mailman3web.hyperkitty_email.content at row 1") Yes, I'm still seeing the errors. When I send mail to a list with a cute emoji, I see the following in /var/log/mailman3/web/mailman-web.log: ERROR 2021-01-28 10:58:45,708 16923 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive (bunch of python errors omitted) DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column 'content' at row 1") Also, a bunch of mail is sent to root, presumably one for every message that has previously failed, with the same error information, plus information about the POST method done. (If something there would be helpful, please let me know.) Finally, I'm doing all of this on Ubuntu, with the packages available in the distro, which means: mailman3 3.1.1-9 mailman3-doc 3.1.1-9 mailman3-full 3.1.1-9 mailman3-web 0+20170523-14 python-django-hyperkitty 1.1.4-4 python-django-mailman3 1.1.0-4 python-django-postorius 1.1.2-3 python-mailmanclient 3.1.1-5 python3-mailman-hyperkitty 1.1.0-4 Thanks very much for any help you can offer. Cheers, David

5 years, 8 months

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

by David Newman

On 11/23/21 4:40 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > I am looking for a high-level "do these steps next to get a list > > working" document rather than an API command reference. > > There's no such documentation. "Get a list working" depends on what > you mean by "working". Thanks for getting back to me. IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this. When I say "working": I'm looking to migrate Mailman2 mailing lists to Mailman3, but am struggling with even basic setup tasks before we attempt list migtration. For example, on admin page I've set up two lists, one public and one private (each with unique list IDs), but neither appear in the site's list index. And I don't know where to add list members. And clicking the site archives link throws this error: > The basic answer is > > 1. Install Mailman 3 suite. > 2. Log in to Postorius as an admin user and create the list. > > After that, it's case-specific. > > > - why do the venv docs and admin FAQ give different nginx configs for > > the reverse proxy? > > Because the FAQ is providing a short snippet to solve a specific > problem, the venv docs provide what I guess is somebody's full working > config. Setting up a Mailman server is complex; usually any example > you see in the docs is somebody's "works for me" configuration. > > > - Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides > > /opt/mailman/mm/mailman-hyperkitty.cfg? > > It needs to match MAILMAN_ARCHIVER_KEY in HyperKitty's settings.py. > There are a couple of reasonable ways to organize HyperKitty and > Postorius configs, I'm not sure where the appropriate settings.py > would be on your server. > > > - For Django (presumably in /etc/mailman3/settings.py, but the docs > > don't say), what values to use with Postfix to set up the email back end? > > The answer is "that depends on your mail environment". As far as I > know, normally it just works with the default settings, but if your > Postfix requires secure, you need to set that up: > https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_T… > and possibly the following 3 or 4 variables if authentication is needed. > > There was a thread on this a couple of weeks ago. > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 10 months

[MM3-users] Re: Turn off social logins?

by Jonas Meurer

Hi Stephen, Stephen J. Turnbull: > Jonas Meurer writes: > > > But still, adding so-called "social" authenticators to the mailman3 > > django application will expose users to the risk of clicking on > > those ID provider buttons. > > I can see this point for Debian users. I suspect Ubuntu users are > somewhat less paranoid. :-) Don't know ;) I don't think that Debian users are particularly paranoid. But I consider it a great value of Debian that privacy is considered as something important. > Since that risk holds even for sites that enable explicitly (assuming > we adopt the same policy) I will take a look at making that risk hard > to realize (more distance from anything else clickable, smaller > buttons with visible and accurate boundaries. Mh, I didn't mean that people click on the buttons by accident. But that they will do so, because it is so convenient (which it is, admittedly). But in my eyes, software developers, package maintainers and system administrators all should do their best to protect their users from privacy and/or security threats. Probably we have a different opinion on whether providing usage of authentication providers which earn their money by collecting users' data exposes users to privacy threats. > > > Personally, I consider it a major privacy issue if one central > > instance (e.g. Facebook) is able to track on which platforms and > > services you authenticate. > > Sure, but that ship has pretty well sailed AFAICT. Most users use > unconfigured versions of IE (or Edge) and Safari, which means they're > subject to all manner of webbugs. My employer just asked me to stop > using Firefox because it's too pedantic for their website development > vendors. :-( GDPR enforcement seems to primarily be an arm of the EU > trade offensive against large American services (that's the > Economist's recent opinion, not mine), while Europe-based globals are > undoubtedly doing the same crap. I have a different opinion on this. You're correct that most users know next to nothing about protecting themselves against all kinds of threats on the internet. But to me this shows even more, that we as those who build the tools have a responsibility to protect our users against shooting themselves in their foot. And I don't agree that any ship has sailed here. If you look at the mainstream development, then you're probably right. But this should not serve as the only rule, no? It's well known that the big corporates make their money with users data. That's how they survive in capitalism. But that doesn't mean that we as independent and free software developers have to agree on the dangerous interfaces and standards those corporates develop (for their business!). Don't get me wrong: I like it that Mailman3 actually supports this wide range of authentication providers. There's probably good use cases for it. And if your users like it and you consider it a win for them, then by all means go on with providing the feature. But it's a different question what a good default and the criteria for choosing it are. > > > And to be honstes, I'm a bit irritated that those tracking features > > from big corporates like Facebook and Google, whose main business > > model is to aggregate as as much private data points as possible > > about as much users as possible are enabled by default in Mailman3 > > upstream. > > Your irritation is not our problem, though, since you can use Debian's > version, and as I mentioned earlier, as far as I know most of our > sites are happy to have social auth. I will be paying attention to > the list to see what others think. My irritation was mainly about what I wrote above: that the privacy concerns against authentication providers from big corporates seem to be of low priority when deciding about defaults in Mailman3 upstream. > > I agree with Torge that those social auth providers should be > > disabled per default. IMHO, A sane default would be to list them in > > the settings.py but have them commented out. > > "Those" social auth providers? Are there social auth providers who > provide what you consider acceptable privacy guarantees (a la > Duck-Duck-Go in search engines)? If so, we could make those higher in > the list/easier to use. To be honest, I've never evaluated the privacy implications of OpenID. From a first glance, it looks *way* better. But for sure, Github, Google, Facebook, Stackexchange and Twitter all rely on collecting users data for their business model. So it's probably not a good idea to share with them the information which platforms and services you authenticate against, *if* you care about privacy. Anyway, all that's just *my* opinion. But it's good to have this discussion :) Cheers, jonas

7 years, 7 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Many thanks for your help. I have managed to modify some of the messages after following your instructions. Kind regards, Prasanth On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Thank you for your help. Let me try this. > > Kind regards, > Prasanth > > On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/28/21 6:02 AM, Prasanth Nair wrote: >> > Hello, >> > >> > Does anyone know how to edit an archived email in Mailman3? It is >> possible >> > in Mailman2 ( >> > >> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >> ). >> > Is there any option similar to this in Mailman3? >> >> >> In some sense the process is the same but possibly even simpler in >> Mailman 3. You need to modify the underlying data which requires >> appropriate access to the server. >> >> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >> database. You can get the Message-ID hash from the URL to the archived >> message, e.g. for the message to which I'm replying, the URL is >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >> access, you can do database queries like >> ``` >> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> and >> ``` >> UPDATE hyperkitty_email SET content = '<new content>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> If the message has attachments, they are in the hyperkitty_attachment >> table and can be referenced by `email_id` which is the corresponding >> `id` from the hyperkitty_email entry. >> >> You can also do similar things via `django-admin shell`. E.g. >> ``` >> $ django-admin shell >> Python ... >> (InteractiveConsole) >> >>> from hyperkitty.models.email import Email >> >>> x = >> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >> >>> print(x[0].content) >> ``` >> but this requires some knowledge of HyperKitty's models and Django's ORM. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

5 years

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi, I was wrong. It keeps happening. So the base_url didn't fix the issue. And the keys are the same in all configurations. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Fri, 22 Mar 2024 at 09:37, Helio Loureiro <helio(a)loureiro.eng.br> wrote: > Hi Mark, > > Thanks for your response. I found what the issue was. > > I actually misspelled hyperkitty as hyPperkitty on the url. > > So the error on mailman-hyperkitty.cfg was: > > base_url: http://localhost:8000/hypperkitty/ > > I moved to: > > base_url: http://localhost:8000/hyperkitty/ > > and it was solved. > > Problem was the wrong link was getting a generic page from Django instead > of error. And it was failing to do the parsing probably, which was taking > wrongly as key mistake. > Best Regards, > Helio Loureiro > https://helio.loureiro.eng.br > https://github.com/helioloureiro > https://mastodon.social/@helioloureiro > > > On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/20/24 14:25, Helio Loureiro wrote: >> > Hi, >> > >> > I keep receiving a lot of errors like this: >> > >> > --- Logging error --- >> > Traceback (most recent call last): >> ... >> > >> "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", >> > line 55, in unsign >> > raise BadSignature('Signature "%s" does not match' % sig) >> > django.core.signing.BadSignature: Signature >> "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" >> > does not match >> ... >> > >> > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and >> MAILMAN_ARCHIVE_KEY >> > on setting.py are the same. >> >> >> Of those three, the api_key on mailman-hypperkitty.cfg and >> MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django >> thing and has nothing to do with the others. See >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key >> >> If you changed it, that's the issue. If you know what it was previously, >> you could set the previous value in SECRET_KEY_FALLBACKS, see >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks >> >> -- >> 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 helio(a)loureiro.eng.br >> >

2 years, 6 months

[MM3-users] Mailman 3 questions (purge archives, list metrics, and auto discard held messages)

by Stephen J. Turnbull

bob B via Mailman-users writes: > --Just wanted to check that there is still no way for mailman3 to > automatically purge archived emails after a set amount of time? Pedantically, Mailman itself can't do that, and never will be able to. That's up to the archiver in use. I assume you mean HyperKitty. > it looks like you have to export the database, purge the messages, > then re-import, is this still the only/best way to purge old > archived messages? For HyperKitty, this is still true. This is a pretty hairy operation, and infrequently requested. A bug could be extremely destructive. I expect it will be a while before it is implemented and part of the standard distribution. I guess there may be potential applications where there's something like a max 90 days document retention policy, so there's some room for it. Of course, a volunteer might speed that up. (Money is unlikely to do so, the currently active core developers don't have a lot of time or appetite for consulting.) > --I noticed on the list info page you have metrics, which is > straightforward except for "volume" My volume number is not > increasing? What is that counting exactly? Volume number refers to the digest volume. Each digest mail distributed constitutes a numbered "issue". Every once in a while we increment the volume number and reset the issue to 1 so that the issue numbers don't get huge. The options for reset frequency are Daily, Weekly, Quarterly, Monthly, Yearly. If it's one of the longer ones, you're not going to see increments for a long time. And if you have digests disabled, you won't see it increment at all. > --Is there any way to auto discard held messages after x amount of > time? I assume not but had a user ask if that was an option. There currently is no such option. I'm not sure it's a great idea because if x is large, it's not very useful, and if x is small, moderators will go on vacation or get busy at work, and a bunch of valuable messages will be auto-discarded. If you're not going to be reasonably prompt about moderation, you may as well set the list to discard, not hold. So I'm not inclined to work on this feature myself. I wouldn't oppose another core developer who wanted to add it, and I might even apply a 3rd party patch if it came with a plausible story that I'm at least occasionally wrong about the risk/reward balance I expect.

4 years, 2 months

[MM3-users] Re: default processing

by Stephen J. Turnbull

Sam Darwin via Mailman-users writes: > - "list default". > - "default processing'. and "member default". Three different names, just as "Samuel Darwin" is a different name from "Charles Darwin". > I would just think "Ok, clearly that's the default. Look at the > name there. Default processing. The default." "The" default? There's a cascade of options that are controlled by subscribers, owners, and site admins, with the lower level option values becoming defaults for the upper levels. And there's a side cascade of defaults for subscribers: user-wide defaults, address-wide defaults, and the per-subscription option values. > But if you name both of your sons "Michael" even though you > understand they are separate people, it causes headaches. Sure, but as shown above we didn't. I really don't think this is going to be a common problem. You seem to attach a connotation of uniqueness to the word "default". It simply doesn't apply to the cascade of defaults Mailman uses, while most Mailman administrators and subscribers seem to understand this aspect of how Mailman works. > So ask the question is "default processing" the only compelling > name for that functionality? That's not a useful question to the developers, though. What we ask are, "Are there better names for that functionality?" (arguable) and "Are any sufficiently compelling to warrant a change?" (not to me). > Why use it again? - Because the functionality is a default in a cascade of defaults. - Because at the level the issue presented itself, it's what people *should* use in the absence of a specific reason for using one of the other options. - Because it's already there and at least 35 people are involved in changing it, it's not obvious that the change will be easy for all of them, and it's likely the changes will spill over to several more files, mostly unidentified at this point. Abstract arguments supported by only one person's experience won't overcome the third point for me, so until you do address that point or a few folks chime in to agree that this is confusing[1], I'm out of this thread. Footnotes: [1] I hope those who do agree will speak up. There's an awful lot of individual opinion about language flying around here. "Disagree" is not so useful since it appears that's the developers' bias anyway and we don't need a pile-on, but you all are welcome too. :-) Especially if you report similar but different issues, as we've already seen. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year, 1 month

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

by Thomas Stein

Am 2024-04-26 00:52, schrieb Mark Sapiro: > On 4/25/24 14:01, Thomas Stein wrote: >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >>> >>> I don't know how things are arranged in the Debian/Ubuntu package, >>> but you may have a settings.py which at the end does something like >>> ``` >>> try: >>> from settings_local import * >>> except ImportError: >>> pass >>> ``` >>> If that is the case, adding the above snippet to the end of >>> settings_local.py should work. >> >> Yes, that's the case. I added the snippet in question to >> settings_local.py but this leads to another error: >> >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> >> from settings_local import * >> File "/usr/share/mailman3-web/settings_local.py", line 194, in >> <module> >> x = list(MIDDLEWARE) >> ^^^^^^^^^^ >> NameError: name 'MIDDLEWARE' is not defined >> dpkg: error processing package mailman3-web (--configure): > > Yes. I understand. In your case, MIDDLEWARE is only defined in > settings.py and not in settings_local.py. As I understand it originally > you added > ``` > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to settings.py and you say it didn't help. I don't know why that > wouldn't work as long as there is no setting for MIDDLEWARE in > settings_local.py and you added that after the MIDDLEWARE setting in > settings.py. > When you say it didn't help, do you mean you still get the > > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > > message or something else? I note that the original post in this thread > refers to /etc/mailman3/mailman-web.py which is presumably where the > package ultimately puts the Django settings, and I don't know what > `dpkg --configure` is doing. > > One thing you could try is in settings_local.py, put > ``` > from settings import MIDDLEWARE > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to work around the NameError. After that I get: File "/usr/share/mailman3-web/urls.py", line 20, in <module> from django.conf.urls import include, url ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) 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: I guess I'll wait for the new package for now. thanks again! t.

2 years, 5 months

[MM3-users] Re: Database running VERY hot

by Darren Smith

Well, we haven't tackled the issue if importing old archives yet - we're trying to stabilize things first, trying to get the 504 gateway timeouts to stop happening. Once that happens, we have over 40 million old emails to import. (some of the emails date back to 1987 I think.) We'll see how it goes. :) -Darren On Fri, Mar 9, 2018 at 10:20 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Fri, Mar 9, 2018, at 9:11 AM, Darren Smith wrote: > > Abhilash, > > Thanks for the response. I'm going over to lists.fedoraproject.org to see > if they have done any fine tuning. > > Our installation is at https://lists.rootsweb.ancestry.com, if you're > interested in seeing an installation with over 32,000 mailing lists. As I > mentioned, it was big enough that we have disabled the browse experience in > Postorius and are hosting our own pages for browsing to a new list. > > > Please keep us posted if you have other unique challenges for operating > this high number of lists, other than this particular one. We'd love to be > able to support high number of lists efficiently :) > > If we get time to work on this we will certainly create a pull request. :) > > > On Thu, Mar 8, 2018 at 11:49 AM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > Hi Darren, > > > On 3/8/18 9:43 AM, Darren Smith wrote: > > Hello all, > > We had an old installation of Mailman 2.1 across three servers with over > 32,000 mailing lists on them. Due to circumstances beyond my control, we > had to shut them down and quickly set up Mailman 3 on a new server. > > We have Mailman3 set up on a single server this time, as we were having > problems with a 3-server setup and Hyperkitty and archives. Long story > short, it is up and running, and our users are starting to come back. > > However, we do not have very many users hitting Postorius and Hyperkitty > yet, and we are seeing a distressing number of 504 gateway timeouts. > > We noticed that there is a significant number of queries to the API > whenever hitting Postorius's front page to load the mailing lists, and then > on every load. It looks as if it makes a single call to the API to get > information about a single list, and does this 10 times - once for each > list - to render the page. This gets much worse when users set the view to > 200 per page, as they are inclined to do with 32,000 mailing lists... > > What we've done, actually, is to override the front page and point the > users to a different set of static pages where we have all of our lists > categorized and searchable, and when they find the list they are looking > for, we have a link back to postorius. It has taken a lot of the stress off > of the server. > > However, I still see where the database at times can run VERY hot. > > We have set up this server to run with PostgreSQL. When I do a ps aux | > grep postgres, I find a lot of processes that have been spawned to take > care of mailman - a dozen or so. However, one of the threads is taking up > about 85% of the load, another thread about 14%, and little dribbles here > and there from the rest of the threads. > > Here are the questions: > > 1) Has anyone run into problems like these? I would think that maybe this > is an issue having so many mailing lists, but honestly there aren't that > many people using the system yet. It is going to ramp up as the users > realize that we are live again, but we aren't getting that much traffic. > > > I can say that in general, Postorius doesn't really optimize REST API > queries and so loading a single page can sometimes make things bad. > > Currently, the largest installation of Mailman 3 that we know of runs at > lists.fedoraproejct.org and the administrators of the list would know how > well does our Web UI scale. > > However, I don't think we have anyone actively working on trying to fix > this particular issue. Pull Requests and fixes are welcome :) > > > 2) Is there any configuration that I can set, especially with regards to > the database, so that it can be used more efficiently and not throttle > through one or two threads? > > > There isn't any configuration that would change how databases are used in > Mailman Core. Django *may* have some, but I don't know about any of them of > the top of my head. > > thanks, > Abhilash > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > >

8 years, 6 months

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

by Odhiambo Washington

On Thu, 30 Jul 2020 at 22:02, Mark Sapiro <mark(a)msapiro.net> wrote: > 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. > (venv) [mailman3@gw ~]$ pip install cmarkgfm Requirement already satisfied: cmarkgfm in ./mm/venv/lib/python3.7/site-packages/cmarkgfm-0.4.2-py3.7-freebsd-12.1-RELEASE-p7-amd64.egg (0.4.2) Requirement already satisfied: cffi>=1.0.0 in ./mm/venv/lib/python3.7/site-packages/cffi-1.14.0-py3.7-freebsd-12.1-RELEASE-p7-amd64.egg (from cmarkgfm) (1.14.0) Requirement already satisfied: pycparser in ./mm/venv/lib/python3.7/site-packages/pycparser-2.20-py3.7.egg (from cffi>=1.0.0->cmarkgfm) (2.20) (venv) [mailman3@gw ~]$ > > [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. After changing the Alias line and running the mailman-post-update, all errors are gone and I have a web UI. Yayi!!! I have been able to create a domain, a list for testing. Now I just need to go through the analysis of what I have been doing so that I can clean up my notes. Then I can come back on migration issues. A BIG THANK YOU for all the support up to this point. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 2 months

[MM3-users] mailman procesing small amount of mail, then stop process them like 30 seconds, and then loop back

by Stephen J. Turnbull

mathias.bedu(a)epitech.eu writes: > I am currently trying to optimize my mailman installation, which is > working. The only issue is that i see that mailman seems to process > a few number of messages (around 50 each times), then stopping, and > then processing few next messages. What makes you think that this is Mailman stopping? Mailman's default behavior is to send messages to the MTA as fast as it will accept them, and let the MTA take care of any throttling or optimization. Mailman even tries to parallelize this process. So if you're seeing delays I believe that is more likely to be the MTA delaying acceptance rather than Mailman. The other possibility is lists that have DMARC mitigation on only for p=reject domains. Then there may be delays due to DNS lookups to check for the From domain's DMARC policy. > I precise that the machine itself is largely more powerful than > what mailman is using. This is probably true, but CPU and memory are not usually what limits mail delivery. Aside from MTA and DNS delays, and very underpowered hosts, there's no reason why Mailman would be be stopping for more than a second or two even if some of the "be nice to the MTA" parameters below are given restrictive values. > So my question is : could you give me some leads for potentials > parameters or stuff like this that i could modify to optimize the > installation ? You might look at these parameters in your configuration file, or in the definition file schema.cfg (do not change this file because it is overwritten by upgrades). The defaults are set pretty much as fast as possible. # Ceiling on the number of recipients that can be specified in a single SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. max_recipients: 500 # Ceiling on the number of SMTP sessions to perform on a single socket # connection. Some MTAs have limits. Set this to 0 to do as many as we like # (i.e. your MTA has no limits). Set this to some number great than 0 and # Mailman will close the SMTP connection and re-open it after this number of # consecutive sessions. max_sessions_per_connection: 0 # Maximum number of simultaneous subthreads that will be used for SMTP # delivery. After the recipients list is chunked according to max_recipients, # each chunk is handed off to the SMTP server by a separate such thread. If # your Python interpreter was not built for threads, this feature is disabled. # You can explicitly disable it in all cases by setting max_delivery_threads # to 0. max_delivery_threads: 0

6 years

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

by Helge Baumgart

Hello Mark, THANK You for identifying MY typos.... how embarrassing. :-) Now ist running like a charm. It's always the same... These Variables are setting the internal Values via the docker-compose.yml. If they do not match, the internal variables are not set. Therefor my typo H*A*YPERKITTY_API_KEY =! HYPERKITTY_API_KEY caused, that the mailman-web section of the docker-compose.yml had NO Hyperkitty API- KEY. I suspected something like that, that's why i set the key via the .env variabels to ensure identical values in all sections oft the docker.compose.yml. I didn't check the name of the variables... Thx again! Best wishes Helge Ps.: That docker-compose.yml with the settings_locale.py and mailman_extra.cfg basically setts a complete deployable environment INCLUDING the MTA, which is independent of the host... Am 22.01.2025 um 06:36 schrieb 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. >

1 year, 8 months

[MM3-users] base64 re-encoding and line endings

by Stephen J. Turnbull

Quoted parts are reordered. Executive summary: Mail occasionally arrives at Mailman, Mailman reassembles it with a git patch using CRLF line endings encoded as BASE64, and git can't apply the patch without "fixing" the line endings. I don't think this is a Mailman problem. Analysis below. It would be very helpful to have a copy of such a mail (verbatim as delivered to Mailman's MTA would be best, but at least all Content-Type, Content-Disposition, and Content-Transfer-Encoding header fields). David Bremner writes: > Occasionaly people send it with Content-Transfer-Encoding 8bit. > I guess with 8bit transfer encoding there probably isn't a clear > distinction between the line-endings on the wire, and the intended > line-endings for delivery, It's clear from RFC 2045: line endings on the wire must be CRLF.[1] What they are at either end is ambiguous because it's up to the MTAs, *and will be different on different receiving hosts if the native conventions of the hosts are different.* This means that as far as Mailman is concerned those line endings are *supposed* to be CRLF and nothing else. (Not clear what should happen if 8bit conflicts with the MIME content type or the content of the patch body, see below, but that's the sending system's issue.) I don't think this is a Mailman 3 problem (except possibly in the archive). The canonical [content transfer] encoding model[2] implies that since Mailman receives the message "off the wire" via LMTP (rather than as a system file), if the MIME content type is text/*, (1) the line breaks Mailman sees in the message body are always CRLF after content transfer decoding, (2) the line breaks Mailman emits to its MTA are always CRLF "inside" the BASE64, and (3) the receiving mail system (usually the MTA) is responsible for decoding the BASE64 and then transforming the CRLFs to the local convention. (1) and (2) seem to be consistent with your report, and would indicate that Mailman is conforming to the relevant standards. I wonder if the sending systems are using a binary MIME content type such as application/patch? That would be incompatible with the 8bit content transfer encoding, and might confuse the systems on either end as to what encoding should be done. (I guess it might also confuse Mailman, I'll have to check, but it doesn't point *only* at Mailman.) In that case, the MTA will decode the BASE64 but *not* transform the CRLF to LF, which is consistent with the observed behavior as well. Of course it's *possible* that Mailman is receiving LF and transforming that to CRLF, but that implies sender behavior inconsistent with the 8bit content transfer encoding, there's nothing in the email processing model that suggests Mailman might do that under the reported conditions (in particular, the 8bit content transfer encoding is the identity, implying that even if Mailman "notices" that it is 8bit, it should do nothing about it except maybe complain about NUL, solo CR or LF, and lines longer than 998 bytes), and I think it would show up in other contexts with similarly distressing consequences if Mailman were doing it. > I have a local workaround involving re-formatting the patches, but > I'd really like anyone to be able to apply the patches from the > list archive. If your archive is hosted on an LF system and the content-type applied to the patch is text/*, it "should" just work and the archived patches being impossible to apply "as is" is probably a Mailman issue. > This seems somewhat related to > https://gitlab.com/mailman/mailman/-/issues/269 Not the same. The problem there is that for some reason Mailman is altering the text (removing trailing whitespace). That's unambiguously wrong regardless of MIME content type or content transfer encoding, and damaging in the case of format=flowed. I'm going to have to revisit that issue. > I guess with 8bit transfer encoding there probably isn't a clear > distinction between the line-endings on the wire, and the intended > line-endings for delivery, but it could be inferred from the > "X-Mailer: git-send-email" header. No, *you* as receiver can make that inference, but *we* as a middleman can't. git is used on both LF and CRLF platforms. If we're receiving CRLF, we have to send it back out. This implies that if you want to, you can write a plug-in handler to make this transformation inside Mailman, and insert it into the processing pipeline before the archive handler. Footnotes: [1] RFC 2045, Section 2.8. 8bit Data "8bit data" refers to data that is all represented as relatively short lines with 998 octets or less between CRLF line separation sequences [RFC-821]), but octets with decimal values greater than 127 may be used. As with "7bit data" CR and LF octets only occur as part of CRLF line separation sequences and no NULs are allowed. That is, Content-Transfer-Encoding: 8bit is not binary, does not admit non-text, and requires that line-endings be CRLF. [2] RFC 2049, Section 4. Canonical Encoding Model

6 years, 1 month

[MM3-users] Re: username

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > will do this. The university does use SSO for many applications and > I was asked by upper management of the IT department to try and > implement it here. I'm still trying to understand your reply to my > SSO question from last week (my SSO knowledge is limited and I'll > have to read up on Shibboleth, SAML, as well as Django) so for now > I'm thinking to not use SSO If they want to use it, pass the buck to them. I'm happy to help with the Mailman side (on a time-available basis or as a paid consultant -- time available is probably a much better deal, though!) But I can't know what the system in use is, so maybe you should get them to write an outline of the system (what software, what requirements, what ID-related attributes are available). > then transition to SSO later. I don't think that will be a problem technically, as long as the user ids are the same for the same people. There will be UX issues though in the configuration I use. I think people will accept them quickly, but the UX will be different, which makes folks nervous if you don't warn them and explain why it's OK. > If you have any pointers as to > where to read up on SSO, SAML, Shibboleth and also on Django please > point me in the right direction. For django, search "site:djangoproject.com REMOTE_USER". For shibboleth, the relevant documentation is on the atlassian site. Here's the main documentation for the "service provider" component (this is the part that Postorius would be using indirectly): https://shibboleth.atlassian.net/wiki/spaces/SP3/overview search there for "REMOTE_USER" for the most relevant documentation. The SAML protocol is above our pay grade. :-) There's an introduction to the SAML architecture linked from the service provider documentation. That's way more than you need for this task, I think, so just skim it. Another guy did the Shibboleth config, so I'm a little fuzzy on this, but again I think that's mostly IT/NOC responsibility. (IIRC the main thing was getting the ID provider credentials and our host certs from the NOC, you can't generate those yourself!) The parts that hook into mailman are a list of translations of ID attributes to Apache variables, some email addresses for error reporting, and in Apache some translations of Apache variables to HTTP headers. But you need to make sure it's SAML. I'm no expert on this stuff, but it seems like there are a bunch of these protocols, like OpenID and OAuth2 out there. Django knows how to do those, too, but we need to know which one! Steve

3 years, 3 months

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

by David Newman

+1 to Stephen's comments. I too installed and ran MM2 lists for many years, and found the MM3 setup to be challenging. It took me four or five full installations on test VMs before I was comfortable going into production, and even then I ran into several hiccups, well documented on this list. A few things may help: - don't install from packages on Debian/Devuan. The package version isn't current and has several issues. For now, use Python/pip installation instead. (I'd much prefer to use the distro package any day, and hope the need for this bullet point goes away soon.) - start from the venv and web setup docs: https://docs.mailman3.org/en/latest/install/virtualenv.html https://docs.mailman3.org/en/latest/config-web.html There's some overlap between these but they're the closest thing to an installation manual we have. - Document every step. For example, I documented around six different config changes needed for MariaDB, which my server runs instead of PostgreSQL. You may have similar experiences with Apache instead of Nginx. - For web and email setup, note that the above URLs assume MM3's web components (Django, Postorious, Hyperkitty) are accessible through "/" in Apache's DocumentRoot directive. If you have other web services on the same server (e.g., if you're also running Roundcube), you'll need to tweak your Apache config. - AFAIK there's currently no sysadmin manual for the care and feeding of MM3 and friends once it's up and running. I have some installation and config notes from my setup, and I'd be glad to share them, but they don't cover list management tasks. Hope all this is useful. MM3 is bigger and more complex and has more stuff to break. Once it's running, though, it's been pretty solid. /drn On 1/24/22 4:54 PM, Stephen Daniel wrote: > Nate -- > > A few months ago I, a total novice with Mailman, set out to install > Mailman3 on a Debian server. > I used these instructions: DOC/Howto_Install_Mailman3_On_Debian10 > <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> > > It took me several tries, but with some help from people on the list it is > now up and running. It was also a *much *bigger investment of my time than > I expected. > > I cannot say I completely understood what I was doing every step of the > way, and some of the steps are like: go edit the config file so that it is > right, which can be daunting. However, even for someone who's never > touched mailman before, it can be done. > > Best of luck > > -- Stephen > > On Mon, Jan 24, 2022 at 7:19 PM nate <mailman-list(a)linuxpowered.net> wrote: > >> Hello mailman users out there - >> >> I have been a casual user of mailman for 21 years now I think it is. >> Most of my >> lists were super small (my only current lists have no more than 8 >> members each), >> super low volume. It's "just worked" over the years, no issues. I have >> been >> using Linux since 1996, not a newbie here. 21 years ago I deployed >> mailman as >> part of our corporate email and then there were a lot more users. Since >> that >> time I just use mailman on my personal server. >> >> I did a apt-get dist-upgrade on my system and was surprised to see >> mailman had >> vanished. Wasn't expecting that.. not a big deal, or so I thought. >> >> I am running Devuan 4, which is based on Debian. Investigating further >> it seems >> Debian at some point dropped Mailman 2.1 and started including Mailman >> 3. OK, >> not too bad I thought.. >> >> I was/am prepared to start my mailing lists from scratch again, manually >> copy/paste over settings/users/etc. Don't care about archives etc. I >> setup mailman >> 2.1 on another Devuan 3.x system and copied my mailman configs over to >> it, and >> can view them fine via the mailman cgi scripts through Apache, I was >> planning >> on just copy/pasting list settings between the two systems for each >> list. >> >> Roughly 10-15mins into trying to get mailman3 off the ground I just find >> myself >> overwhelmed. That doesn't happen often. I'm honestly completely shocked >> at >> how it seems the complexity of the system has increased by orders of >> magnitude. >> >> I have been browsing around >> https://docs.mailman3.org/en/latest/pre-installation-guide.html >> (and other links on that documentation site) >> >> But as much information as there is, to me there really isn't any >> information >> there. If that makes sense. I'm sure it doesn't make sense so let me >> give an >> example. >> >> On this page: >> https://docs.mailman3.org/en/latest/config-web.html >> >> I assume that would lead me to how do I configure the web interface so I >> can do stuff with it. >> >> I setup an admin account, then it goes into scheduled tasks(which appear >> to >> be handled by the Debian package already but don't know what these tasks >> would have to do with a web interface). I tried sending a test email but >> that failed, I looked at the setting up email portion but it does not >> give any indication where that config would be stored, a recursive grep >> on /etc for EMAIL_BACKEND turns up nothing (there is a /etc/mailman3 >> directory with some files in there). >> >> Then it goes into other things like task queues, full text searching, >> here I am just looking for info on where this web interface is, where >> is the config, what port does it listen on? Is it a cgi like mailman2? >> It seems like it could be a standalone service. >> >> Then it shows a bunch of other settings, not indicating what file these >> are stored in(or what directory the file is in), etc etc etc. Debian's >> own documentation is severely lacking in this department as well, >> normally >> I am used to going to /usr/share/doc/<package>/ and there is some useful >> stuff. There is stuff for mailman3 but it's minimal at best. >> >> So I'm thinking mailman3 is not the package for me. I've really >> appreciated >> mailman 2.1 (and earlier versions) as I said they always just worked, >> never >> had to think about them. I'm sure a lot of good hard work has been put >> into 3, I just don't recall the last time I looked at a project and just >> honestly didn't even know where to begin which surprised me so much >> given >> my 20+ year history of mailman as a user and as an admin. >> >> Is there some document(s) out there that would be more beneficial to >> me in setting up mailman3? I see that mailman 2 looks like it's still >> being maintained, I assume mailman3 is the result of python3 code and >> mailman2 perhaps uses python 2.7? I am unsure on the ability to run >> mailman2 on a modern Debian-based distro since of course Python 2.7 >> is pretty obsolete at this point (or maybe Mailman 2.1 doesn't use >> python I don't recall). I could try to install the older mailman 2.1 >> package on Devuan 4 and see what happens I don't know if it would >> be that simple or not. >> >> 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. Worst case I could just use >> aliases >> in my postfix config at the end of the day that is all that is really >> needed, though I do like some level of access control on who can email >> the lists(even if nobody outside the list knows the list exists), I've >> had some of these lists for 2 decades, old habits die hard right? >> >> I did some searches for mailing list software on the Debian package >> archives and saw a few options, nothing really stood out at me as >> something super interesting yet though. >> >> I don't mean to come across as harsh or complaining or anything I'm >> just here in shock kind of. Thinking about what the best solution for >> me would be. My mailing lists have been broken for a couple of weeks >> but that's really not a big deal. >> >> thanks >> >> nate >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 8 months

[MM3-users] Re: moving list from mm3 -> mm3

by Mark Sapiro

On 12/8/23 08:01, Jens Günther wrote: > > This is a nice collection of the configuration of a certain list. Does > anybody know how I would get this data back to the newly created list in > the second working mm3-instance? Shouldn't it be possible via POST > command? I thought of something like: > > curl -u restadmin:restpass -d @short.domain -H "Content-Type: > application/json" localhost:8001/3.1/lists/&short.&domain/config > > But it returns {"title": "405 Method Not Allowed"} and I don't know > where to look in the docs, since it shows almost always a way through > mailman shell. You need a PUT command, not POST. Try the above with `-X PUT`. > ## Members, moderators, owners > > To export all members I normally run within mm-core-container as user > mailman the following command: > > mailman members &short.&domain > &short.txt > > To fill them back in, it can be done in Postorius (or is there a way > through API?). You can use Postorius -> Mass operations -> Mass subscribe to add the members, but you can't do that for owners and moderators. Also you lose information about the members such as Delivery status, Delivery mode and other user settings. > What I would love to know is how to get out Owners of the corresponding > lists and reimport them in the new one (which will be the same at the > end :-D but different instance). You can use the --role option with `mailman members` to get owners and moderators, but short of a custom script, you have to add them manually. > ## registered users > > This part is somehow tricky, since I have no clue how to do it. Some of > the mailinglist-admins don't want to bother their list-owners again with > registering newly on the other system. Is there a way to export all > users (I think I found them in the DB in the table auth_users, somehow > in combination with account_emailaddress) and get them over to the new > instance (actually I just need part of them, but that's another question > that I might solve lateron on my own). > > Maybe the answer is already here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > -> but can somebody help to get this working (import/export)? That is not the answer. Those are Mailman core users, not Django (web login) users. You need to get the relevant entries from the auth_users and account_emailaddress tables and add them to the new DB. -- 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-sending confirmation mails (was Re: Re: pending subscriptions lost?)

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

On 3/14/22 18:36, Mark Sapiro wrote: > On 3/14/22 09:18, IEM Network Operation Center (IOhannes m zmölnig) wrote: >> >> this is with "Postorius Version 1.2.4" (as installed by the mailman3 >> Debian package). > > The Debian packages are OK for people who want to install things via a > package manager, but they are quite out of date. i know. the problem is, that right now i have a running (Debian-based, thus outdated) mailman3 installation, and I still haven't found a proper strategy to upgrade and keep staying up-to-date. so for the time being i'm stuck with what i have. > > Something like the following in `mailman shell` can do it. thanks a lot. afaiu, this snippet allows me to purge outdated pending subscriptions. modifying it slightly, also allows me to just list the pending subscriptions along with their tokens and print them out. is it still possible to just use these tokens to confirm the pending subscription (even though it is long overdue)? if so, i could just send out a reminder to those 50 or so people who have not confirmed yet. while investigating this a bit, i also noticed that it seems that with mailman3 the only option to confirm a pending subscription is via email ("leaving the subject intact") - at least that is the only option that is listed in the confirmation mail. now i would like to massage this into what i think is a bit more user-friendly. first of all: most email confirmation systems allow me to either "reply by email" or "click this link". is there a way to do this for mailman3? that is: is there a (hidden) URL that would accept the token in order to confirm a subscription? also: the confirmation mail says that the subject must be kept intact. however, i noticed that the actual "From" address of the confirmation mail already contains the token. would it be enough if people just sent an email to this special email-address (that contains the token), regardless of the subject? i'm thinking of sending a rather personalized email that has a more attractive subject than "confirm flkdsajfsalkjflsajfsoisjdl". finally: what else is required to approve the confirmation? will the sender's email-address be taken into account? (e.g. if they subscribed "foo+mylist(a)example.com" but send the confirmation-reply from "foo(a)example.com", will that still work? sorry for so many questions. i *did* search the documentation, but simply haven't found anything that would help me. i've probably looked in the wrong places, but mailman3 is rather huge so it's easy to miss the imprtant parts. gmdsa IOhannes

4 years, 6 months

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

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

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). > >> - ./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? > 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 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). mgfasdr IOhannes ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

2 years, 1 month

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

by Lars Schimmer

On 02/03/2021 18:31, Quanah Gibson-Mount wrote: > > > --On Tuesday, March 2, 2021 9:09 AM +0100 Lars Schimmer > <l.schimmer(a)cgv.tugraz.at> wrote: > >> On 01/03/2021 13:15, Brian Carpenter wrote: >>> On 3/1/21 3:10 AM, Lars Schimmer wrote: >>>> If it should be a gold standard, it should mention the default setup >>>> of a standard debian system (which is exim4, btw) and not assuming a >>>> special setup debian system. >>> >>> So why don't you write up your own how-to for your so-call ''standard >>> debian system". Remember this is a forum for Mailman 3, not a forum for >>> the users of a "standard debian system". So far your comments are not >>> helpful at all. >> >> Install debian >> >> apt-get install mailman3-full > > As someone who is stuck using the ancient version of mailman3 in debian, > I have to disagree. 99.9999% of the time I hit an issue, it turns out > it was fixed years ago, but because I use the debian maintained version, > I don't have those fixes. It's horrible. Intereting view for a software poackage taking a few years to get a way to migrate from mailman2 to mailman3. Or in other words: if a stable version is not useable/to old, the software is not production ready. Sure, bugs do happen, developement does happen. But for a production server you do not want to update every month just for the latest feature. If a software reaches stable, it gets a package which is able to run the lifetime of debian stable. Bugs will be iron out with debian security packages. All new features will not be production critical, mostly add new features. > Distribution packages tend to be useful for really basic things like > libraries. For constantly evolving projects where you need to be > current, they're more of a detriment. Nope. Vote against this view. You need a stable system to rely on and setup without hassle in a nonce. Not to check every package you installed for latest update and run updates every week with latest bugs, issues while upgrading a package. Debian stable has a reason to exist for admins with less time and a wish to run production ready software. Not latest bleeding edge testing software. > --Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> 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

5 years, 6 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

Unfortunately i need this, as the postfix is listening on all interfaces and we have the policy to enforce TLS only. Nothing special in the logs: Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fbc29b1c4a8> Dec 07 08:14:14 2021 (12303) Connecting to localhost:25 Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients: ['recipient(a)own.domain'], size(msgtext): 5809 Dec 07 08:14:14 2021 (12303) <kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> smtp to v-test@domain for 1 recips, completed in 0.008081912994384766 seconds Dec 07 08:14:14 2021 (12303) <kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> post to v-test@domain from v-test@domain, 5336 bytes Dec 07 08:14:47 2021 (12297) Peer: ('127.0.0.1', 43210) Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) handling connection Dec 07 08:14:47 2021 (12297) b'220 ml01.my.domain GNU Mailman LMTP runner 2.0\r\n' Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) EOF received Dec 07 08:14:47 2021 (12297) Connection lost during _handle_client() Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) connection lost Dec 07 08:15:00 2021 (12297) Peer: ('127.0.0.1', 43516) Dec 07 08:15:00 2021 (12297) ('127.0.0.1', 43516) handling connection Is my mailman version maybe too old for this setting? I'm running GNU Mailman 3.1.1 (Between The Wheels) Thank you. Am Mo., 6. Dez. 2021 um 19:04 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 12/6/21 2:51 AM, Stefan Bauer wrote: > > Need to bring this up again. Django now sends with STARTTLS, but mailman > > itself, does still only drop mails in cleartext. > > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > > > No starttls=1 at all :( > > > > Does the above settings work for anyone? > > > > etc/mailman3/mailman.cfg > > [mta] > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > > > smtp_host: localhost > > smtp_port: 25 > > smtp_user: > > smtp_pass: > > smtp_verify_hostname: false > > smtp_verify_cert: false > > smtp_secure_mode: starttls > > > This should work. What do you see in Mailman's smtp.log if you add > ``` > [logging.smtp] > level: debug > ``` > to mailman.cfg. > > However, do you really need this. It will only affect delivery from > Mailman to Postfix via the loopback interface on the localhost. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 9 months

[MM3-users] Re: Docker Support Sucks

by Allan Hansen

Hi Brian, You have been one of the good and generous people providing support. I hope i can repay a bit with this: These are one-line bash scripts I wrote after moving to MM3, so I could do things not yet in MM3, such as letting my moderators request a list’s members from me. I need one more script that will sync a text file to an existing list, deleting and adding as necessary. The scripts are for public use, reuse, misuse and overuse. I claim no rights and no responsibilities. mm3Members.bash #!/bin/bash # mm3Members # # Obtain a list of members of a given list # # Usage: # mm3Members.bash <listName> # # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members $1 |grep -v -e "has no members"|sed -e 's/.*/\L&/‘ mm3ASddMembers.bash #!/bin/bash # mm3AddMembers # # Add members from a given list. # # Usage: # mm3AddMembers.bash <fileName> <listName> # <fileName>: text file with addresses to add. Same legal formats as in mass subscribe # # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members --add $1 $2 mm3DeleteMembers.bash #!/bin/bash # mm3DeleteMembers # # Deletes members from a given list # <fileName> List of members to delete. Legal format the same a formats used for mass subscribes # # Usage: # mm3DeleteMembers.bash <fileName> <listName> # # Revisions: # # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members --delete $1 $2 mm3MemberCount.bash #!/bin/bash # mm3MemberCount # # Obtain count of the members of a given list # # Usage: # mm3MemberCount.bash <listName> # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # /home/hansen/scripts/mm3Members.bash $1|wc Yours, Allan Hansen hansen(a)rc.org > On Jul 21, 2020, at 18:31 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 7/21/20 8:55 PM, Mark Sapiro wrote: >> On 7/21/20 5:40 PM, Brian Carpenter wrote: >> >> Abhilash (@maxking) is one person and he has a $DayJob. We're all doing >> the best we can. > > Well, I still need support. > >> This is not a Docker issue per se. It is a consequence of upgrading >> Mailman core to 3.3.1+ and processing many old, stale, previously >> unprocessed bounces. See >> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > > I am not worried about the bounce issues at this point. I am just trying to get a membership list exported for a client. > >> >>> So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. >>> >>> I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: >>> >>> ### >>> The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: >>> >>> [webservice] >>> configuration: /path/to/gunicorn.cfg >>> >>> and then in the gunicorn.cfg you can add >>> >>> [gunicorn] >>> timeout = 90 >>> graceful_timeout = 30 >>> ### >>> >>> I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. >>> >>> After restarting docker-mailman, I can't access Postorius due to the following error: >>> >>> ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available >> Is Mailman core running? If not, whats in core's mailman.log as to why not? > > It looks like but no error message in mailman.log. However I noted that the gunicorn process did not start. > > This is with the configuration line enabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log > Jul 22 01:25:17 2020 (22) in runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner exiting. > Jul 22 01:25:17 2020 (21) command runner exiting. > Jul 22 01:25:17 2020 (22) in runner exiting. > Jul 22 01:25:17 2020 (24) nntp runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (24) nntp runner exiting. > [2020-07-22 01:25:19 +0000] [27] [INFO] Shutting down: Master > Jul 22 01:25:21 2020 (1) Master stopped > Jul 22 01:25:26 2020 (1) Master started > Jul 22 01:25:44 2020 (27) rest runner started. > Jul 22 01:25:44 2020 (26) pipeline runner started. > Jul 22 01:25:44 2020 (20) bounces runner started. > Jul 22 01:25:45 2020 (22) in runner started. > Jul 22 01:25:45 2020 (28) retry runner started. > Jul 22 01:25:46 2020 (29) virgin runner started. > Jul 22 01:25:46 2020 (25) out runner started. > Jul 22 01:25:46 2020 (23) lmtp runner started. > Jul 22 01:25:46 2020 (24) nntp runner started. > Jul 22 01:25:47 2020 (30) digest runner started. > Jul 22 01:25:47 2020 (19) archive runner started. > Jul 22 01:25:47 2020 (21) command runner started. > > This is with the configuration line disabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log > Jul 22 01:27:49 2020 (1) Master stopped > Jul 22 01:27:53 2020 (1) Master started > Jul 22 01:28:10 2020 (30) digest runner started. > Jul 22 01:28:10 2020 (29) virgin runner started. > Jul 22 01:28:10 2020 (24) nntp runner started. > Jul 22 01:28:10 2020 (25) out runner started. > Jul 22 01:28:10 2020 (22) in runner started. > Jul 22 01:28:11 2020 (28) retry runner started. > Jul 22 01:28:11 2020 (27) rest runner started. > [2020-07-22 01:28:11 +0000] [27] [INFO] Starting gunicorn 19.9.0 > [2020-07-22 01:28:11 +0000] [27] [INFO] Listening at: http://172.19.199.2:8001 (27) > [2020-07-22 01:28:11 +0000] [27] [INFO] Using worker: sync > [2020-07-22 01:28:11 +0000] [32] [INFO] Booting worker with pid: 32 > [2020-07-22 01:28:11 +0000] [33] [INFO] Booting worker with pid: 33 > [2020-07-22 01:28:11 +0000] [34] [INFO] Booting worker with pid: 34 > [2020-07-22 01:28:11 +0000] [35] [INFO] Booting worker with pid: 35 > Jul 22 01:28:11 2020 (19) archive runner started. > Jul 22 01:28:11 2020 (21) command runner started. > Jul 22 01:28:12 2020 (23) lmtp runner started. > Jul 22 01:28:12 2020 (20) bounces runner started. > Jul 22 01:28:12 2020 (26) pipeline runner started. > > -- > Please let me know if you need further assistance. > > Thank you for your business. We appreciate our clients. > Brian Carpenter > EMWD.com > > -- > EMWD's Knowledgebase: > https://clientarea.emwd.com/index.php/knowledgebase > > EMWD's Community Forums > http://discourse.emwd.com/ > > _______________________________________________ > 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, 2 months

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

by William Oliver

On Sun, 2021-12-26 at 18:23 -0800, Mark Sapiro wrote: > On 12/26/21 6:19 PM, Mark Sapiro wrote: > > > > Otherwise, you can do this in mailman shell, e.g. > > ``` > > $ 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. > > > > >>> dm = getUtility(IDomainManager) > > >>> d = dm.get('example.com') > > >>> d.alias_domain = x.example.com > > >>> commit() > > ``` > > > Ooops. That should be > > d.alias_domain = 'x.example.com' > > I.e., quoted > > Thanks. I am *almost* there. Adding the vmap in mailman fixed *almost* everything. Now I can add users, get receive mails to the list, archive messages correctly, and send emails. Except... The list sends emails to local recipients fine. I have three users on my test list: fp145(a)libertyfp.org (local) billo(a)billoblog.com (not local) oliver(a)billoblog.com (not local) When I send a message to the list from *any* of these three, the mailman3 accepts it and attempts to broadcast it out. It is delivered sucessfully to the local email address, but it looks like there's a relaying problem with external addresses. In the syslog snippet below, note that the fp145(a)libertyfp.org mail is delivered, but the mail to the recipients at billoblog.com get an "Access denied" Dec 27 15:33:25 libertyfp postfix/smtpd[419593]: connect from mail.libertyfp.org[2.56.57.28] Dec 27 15:33:25 libertyfp postfix/smtpd[419593]: DC203421BE: client=mail.libertyfp.org[2.56.57.28] Dec 27 15:33:25 libertyfp postfix/cleanup[420001]: DC203421BE: message- id=<9785b5a56581104fe079221bb947eb3a03813d97.camel(a)billoblog.com> Here it is getting delivered locally: Dec 27 15:33:25 libertyfp postfix/cleanup[420001]: DC203421BE: warning: header Subject: [Testlist] bbbbb from mail.libertyfp.org[2.56.57.28]; from=<testlist-bounces+fp145=libertyfp.org(a)libertyfp.org> to=<fp145(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 27 15:33:25 libertyfp postfix/qmgr[418758]: DC203421BE: from=<testlist-bounces+fp145=libertyfp.org(a)libertyfp.org>, size=2651, nrcpt=1 (queue active) Dec 27 15:33:25 libertyfp postfix/virtual[420016]: DC203421BE: to=<fp145(a)libertyfp.org>, relay=virtual, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (delivered to maildir) Dec 27 15:33:25 libertyfp postfix/qmgr[418758]: DC203421BE: removed Here it is getting bounced for billo(a)billoblog.com and oliver(a)billoblog.com: Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: NOQUEUE: reject: RCPT from mail.libertyfp.org[2.56.57.28]: 554 5.7.1 <billo(a)billoblog.com>: Recipient address rejected: Access denied; from=<testlist-bounces+billo=billoblog.com(a)libertyfp.org> to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: disconnect from mail.libertyfp.org[2.56.57.28] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 quit=1 commands=7/8 Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: connect from mail.libertyfp.org[2.56.57.28] Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: NOQUEUE: reject: RCPT from mail.libertyfp.org[2.56.57.28]: 554 5.7.1 <oliver(a)billoblog.com>: Recipient address rejected: Access denied; from=<testlist-bounces+oliver=billoblog.com(a)libertyfp.org> to=<oliver(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> This error occurs whether the account posting to the list is in the libertyfp.org domain or billoblog.com domain. Note that "regular" mail from libertyfp.org does get delivered to outside addresses just fine, originating from inside the domain or through an email client outside the domain. I tried changing the smtp port in mailman.cfg to 587, but that didn't change anything. In my reading, there seems to be differing discussions about what should be in the mydestinations value, but I don't know what it should be. Here's the current last bit of my main.cf, along with the mydestinations setting: mydestination = localhost.org, localhost # add to the end (add virtual users) # if specify multiple domains, specify comma or space separated virtual_mailbox_domains = libertyfp.org virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 # mailman3 changes owner_request_special = no always_add_missing_headers = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap header_checks = regexp:/etc/postfix/header_checks Here's the current values in /opt/mailman/mm/var/data/postfix_domains: # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-27 21:10:32 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. x.libertyfp.org libertyfp.org here's postfix_lmtp: # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-27 21:10:32 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @x.libertyfp.org domain. testlist(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-join(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-leave(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-owner(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-request(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-subscribe(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-unsubscribe(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 Heres the postfix_vmap that was (finally) successfully created: # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-27 21:10:32 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Virtual mappings for the @libertyfp.org domain. testlist(a)libertyfp.org testlist(a)x.libertyfp.org testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org testlist-join(a)libertyfp.org testlist-join(a)x.libertyfp.org testlist-leave(a)libertyfp.org testlist-leave(a)x.libertyfp.org testlist-owner(a)libertyfp.org testlist-owner(a)x.libertyfp.org testlist-request(a)libertyfp.org testlist-request(a)x.libertyfp.org testlist-subscribe(a)libertyfp.org testlist-subscribe(a)x.libertyfp.org testlist-unsubscribe(a)libertyfp.org testlist-unsubscribe(a)x.libertyfp.org For what it's worth, here's the extended header info for the mail that *was* delivered: Return-Path: <testlist-bounces+fp145=libertyfp.org(a)libertyfp.org> X-Original-To: fp145(a)libertyfp.org Delivered-To: fp145(a)libertyfp.org Received: from mail.libertyfp.org (mail.libertyfp.org [2.56.57.28]) by mail.libertyfp.org (Postfix) with ESMTP id 226F6421BA for <fp145(a)libertyfp.org>; Mon, 27 Dec 2021 16:27:17 -0500 (EST) Received: from [10.112.157.251] (unknown [92.60.40.252]) by mail.libertyfp.org (Postfix) with ESMTPSA id F3608421BA for <testlist(a)libertyfp.org>; Mon, 27 Dec 2021 16:27:11 -0500 (EST) Message-Id: <562c2f8aaeb3c9e2ccf198aff197dbd299fc002a.camel(a)libertyfp.org> From: fp145(a)libertyfp.org <fp145(a)libertyfp.org> To: testlist(a)libertyfp.org Date: Mon, 27 Dec 2021 16:27:07 -0500 In-Reply-To: <eb3380eecc734e240f65ddf974d81ee7dac6ca20.camel(a)libertyfp.org> References: <eb3380eecc734e240f65ddf974d81ee7dac6ca20.camel(a)libertyfp.org> User-Agent: Evolution 3.40.0-1 Mime-Version: 1.0 Message-Id-Hash: FKEDFEFMXBD6YUDWKL235PQRIMUYYPEQ X-Message-Id-Hash: FKEDFEFMXBD6YUDWKL235PQRIMUYYPEQ X-Mailfrom: fp145(a)libertyfp.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember- moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.5 Precedence: list Subject: [Testlist] Re: test from fp145 List-Id: Test list <testlist.libertyfp.org> Archived-At: <https://libertyfp.org/archives/list/testlist@libertyfp.org/message/FKEDFEFM… > List-Archive: <https://libertyfp.org/archives/list/testlist@libertyfp.org/> List-Help: <mailto:testlist-request@libertyfp.org?subject=help> List-Owner: <mailto:testlist-owner@libertyfp.org> List-Post: <mailto:testlist@libertyfp.org> List-Subscribe: <mailto:testlist-join@libertyfp.org> List-Unsubscribe: <mailto:testlist-leave@libertyfp.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Evolution-Source: 14004b3d9af2d67c898fd6d6c16b487f796088f5 I'm beginning to hate postfix. billo

4 years, 9 months

[MM3-users] Re: Trouble Installing Mailman3

by Gerald Vogt

On 03.06.25 17:22, Henry Hartley via Mailman-users wrote: > 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 There is no self-signed certificate in the chain, when I check it. I guess, there is a proxy somewhere which has a different certificate. Run $ openssl s_client -connect pypi.org:443 -showcerts to check what certificate is presented. It should be something like: Connecting to 2a04:4e42::223 CONNECTED(00000003) depth=2 OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign verify return:1 depth=1 C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 verify return:1 depth=0 CN=pypi.org verify return:1 --- Certificate chain 0 s:CN=pypi.org i:C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Feb 24 04:28:22 2025 GMT; NotAfter: Mar 28 04:28:21 2026 GMT ... 1 s:C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 i:OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Oct 16 03:08:04 2024 GMT; NotAfter: Oct 16 00:00:00 2026 GMT ... Server certificate subject=CN=pypi.org issuer=C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 ... > When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: Never ever do that. Find out what is happening. Either something bad is interfering with your network traffic. Or there is a proxy and the chain is different. In the latter case, you will see lots of issue until you have configured your system correctly for the proxy in place... But never ever simply turn off security and try to install something through broken security. It defies the whole purpose of security and certificates if you simply turn it off or try to ignore it. -Gerald

1 year, 3 months

[MM3-users] Re: Debian upgrade Hyperkitty not archiving

by Mark Sapiro

On 2/27/26 13:23, Phil Steel-Wilson via Mailman-users wrote: > > I'm working at a volunteer organization with around a dozen mailing > lists that were previously on mm2 that have been upgraded to mm3 with > the upgrade to debian trixie. Mailman is running and the lists all work > ok but i found 1800 mails in the shunt queue. Hyperkitty also shows all > the old archives pre 2020 the same as in the django console. When i > tried to unshunt the mails they moved to the bad queue. How do i find > whats wrong here? If this is the Debian package, you should be working with Debian. See <https://wiki.list.org/x/12812344>. > Mailman Core Version GNU Mailman 3.3.10 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC > 14.2.0] There is a compatibility issue between Mailman 3.3.10 from PyPI and Python 3.13, but this is apparently fixed in the Debian package. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and near the end of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> Mails are shunted because of some uncaught exception in processing. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for more info on dealing with shunted messages. Messages can end up in the bad queue in multiple ways. One way is content filtering ends up with an empty message and the list's content filtering Filter Action is Preserve. This requires ``` filtered_messages_are_preservable: yes ``` in the [mailman] section of mailman.cfg. The only other way messages end up in the bad queue is in reprocessing messages. When a message is picked up for processing by a queue runner it's extension is changed from .pck to .bak. Then if that runner crashes for some reason without finishing processing of that message, the .bak file remains and when the runner restarts, the entry is reprocessed. If unpickling the .bak throws an exception or if reprocessing the same message is tried 3 times without success, the message is placed in the bad queue. The following errors have nothing to do with messages in the shunt or bad queues. They are the result of trying to log in to the web UI with the fedora oAuth login method which is apparently misconfigured. > Traceback (most recent call last): ... > TypeError: OpenIDProvider.get_server_settings() missing 1 required > positional argument: 'endpoint' > ERROR 2026-02-27 20:50:19,995 1769748 django.request Internal Server > Error: /mailman3/accounts/fedora/login/ > Traceback (most recent call last): ... > TypeError: OpenIDProvider.get_server_settings() missing 1 required > positional argument: 'endpoint' ... > ERROR 2026-02-27 20:51:20,841 1769748 django.request Internal Server > Error: /mailman3/accounts/fedora/login/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users] Re: templates

by Odhiambo Washington

If you don't have any templates in the file system and none in the DB table, then you must go to Jerusalem and pray, because you don't have any and nothing will work the way you want. It's either or! On Thu, May 4, 2023, 21:14 Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. > > > > > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Thursday, May 4, 2023 10:58 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: templates > > On 5/4/23 10:33, Christian via Mailman-users wrote: > > I'm having issues with my lists. For each list I have created a > > template [ list:user:action:subscribe ]which has a prospective > > subscriber have to consent to list rules before they are subscribed. > > This template I created is listed in Postorius for each list. I have > > noticed that there are no other templates listed in Postorius. > Furthermore, there is no 'lists' > > subdirectory under Mailman's var/templates/. > > > When you set a template in Postorius it saves it in the > postorius_emailtemplate table in the database and tells Mailman core to get > the template from Postorius via a URI to a Postorius API. > > -- > 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/ > QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to csa(a)web-analysts.net > > _______________________________________________ > 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 odhiambo(a)gmail.com >

3 years, 4 months

[MM3-users] Re: Database running VERY hot

by Abhilash Raj

On Fri, Mar 9, 2018, at 9:11 AM, Darren Smith wrote: > Abhilash, > > Thanks for the response. I'm going over to lists.fedoraproject.org to > see if they have done any fine tuning.> > Our installation is at https://lists.rootsweb.ancestry.com, if you're > interested in seeing an installation with over 32,000 mailing lists. > As I mentioned, it was big enough that we have disabled the browse > experience in Postorius and are hosting our own pages for browsing to > a new list. Please keep us posted if you have other unique challenges for operating this high number of lists, other than this particular one. We'd love to be able to support high number of lists efficiently :) > If we get time to work on this we will certainly create a pull > request. :)> > > On Thu, Mar 8, 2018 at 11:49 AM, Abhilash Raj > <maxking(a)asynchronous.in> wrote:>> Hi Darren, >> >> >> On 3/8/18 9:43 AM, Darren Smith wrote: >> >>> Hello all, >>> >>> We had an old installation of Mailman 2.1 across three servers >>> with over>>> 32,000 mailing lists on them. Due to circumstances beyond my >>> control, we>>> had to shut them down and quickly set up Mailman 3 on a new server.>>> >>> We have Mailman3 set up on a single server this time, as we were >>> having>>> problems with a 3-server setup and Hyperkitty and archives. Long >>> story>>> short, it is up and running, and our users are starting to come >>> back.>>> >>> However, we do not have very many users hitting Postorius and >>> Hyperkitty>>> yet, and we are seeing a distressing number of 504 gateway >>> timeouts.>>> >>> We noticed that there is a significant number of queries to the API>>> whenever hitting Postorius's front page to load the mailing lists, >>> and then>>> on every load. It looks as if it makes a single call to the API >>> to get>>> information about a single list, and does this 10 times - once >>> for each>>> list - to render the page. This gets much worse when users set the >>> view to>>> 200 per page, as they are inclined to do with 32,000 mailing >>> lists...>>> >>> What we've done, actually, is to override the front page and >>> point the>>> users to a different set of static pages where we have all of our >>> lists>>> categorized and searchable, and when they find the list they are >>> looking>>> for, we have a link back to postorius. It has taken a lot of the >>> stress off>>> of the server. >>> >>> However, I still see where the database at times can run VERY hot.>>> >>> We have set up this server to run with PostgreSQL. When I do a ps >>> aux |>>> grep postgres, I find a lot of processes that have been spawned >>> to take>>> care of mailman - a dozen or so. However, one of the threads is >>> taking up>>> about 85% of the load, another thread about 14%, and little >>> dribbles here>>> and there from the rest of the threads. >>> >>> Here are the questions: >>> >>> 1) Has anyone run into problems like these? I would think that >>> maybe this>>> is an issue having so many mailing lists, but honestly there >>> aren't that>>> many people using the system yet. It is going to ramp up as the >>> users>>> realize that we are live again, but we aren't getting that much >>> traffic.>> >> I can say that in general, Postorius doesn't really optimize REST API >> queries and so loading a single page can sometimes make things bad.>> >> Currently, the largest installation of Mailman 3 that we know of >> runs at lists.fedoraproejct.org and the administrators of the list >> would know how well does our Web UI scale.>> >> However, I don't think we have anyone actively working on trying to >> fix this particular issue. Pull Requests and fixes are welcome :) >> >>> >>> 2) Is there any configuration that I can set, especially with >>> regards to the database, so that it can be used more efficiently >>> and not throttle through one or two threads?>> >> There isn't any configuration that would change how databases are >> used in Mailman Core. Django *may* have some, but I don't know about >> any of them of the top of my head.>> >> thanks, >> Abhilash -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] Managing mailman3 via curl (using bash-scripts or perl-scripts)

by Stephen J. Turnbull

Christian Schneider writes: > My aim is to provide one high-level script for the daily task of > list creation. I'll try to get you started. Mark is likely to have comments or improvements. If you're on-host, list creation can be done with the 'mailman' utility. The point of the REST API is to allow "arms length" operation by arbitrary software, not necessarily on the same host. > The create-list script itself should be a bash- or perl-script (I > am not very familiar with python - SORRY ;-) ) The REST API is script-language-agnostic. It's a bit clumsy compared to using the mailmanclient Python API, but using the REST API, any scripting or programming language would suffer from that. > I would like the scripts to trigger some curl-calls on the mailman > server (from outside the mailman shell and even from outside the > virtual environment) It's your call, but are you sure the commands provided by the 'mailman' utility don't do what you need? > 1) Can I succeed with this plan? (Are curl-calls sufficient? Is it > possible from outside the virtual environment?) Yes, you can do anything using curl that the REST API can do. The virtual environment is only relevant to controlling Mailman from Python. If you are using the REST API, you need a running Mailman, which will already be running in the correct virtual environment. However, calling curl from a script is very clumsy. You will need to trap errors such as "user exists" and so on. You probably need to parse the response as well as check the HTTP status. > 2) Is this a viable curl-call to create a user?: > curl -X POST -u 'admin-user:<password>' -H "Content-Type: application/json" -d '{ > "email": "peter.rabbit(a)example.org", > "display_name": "Peter Rabbit", > "password": "secret" > }' http://localhost:8001/3.1/users The "admin-user" in this command is the "restadmin" user, not the list-owner. I think in the 'create-list' command you meant the --admin-user to be the list owner. Also, the "password" attribute is not very useful in Mailman 3. The only authorized user of the REST API is the restadmin user. There is no provision for access by other users. To authenticate other users, you will need to provide an alternative authentication database, such as .htpasswd validated by a front-end such as Apache. In a full Mailman suite installation, administrative and subscriber authentication is managed by Django, not by Mailman core. > 3) and in a second step can I assign this user to a list as owner > with a curl-call like this?: > curl -X POST -u 'admin-user:<password>' -H "Content-Type: application/json" -d '{ > "list_id": "newsletter.lists.example.org", > "subscriber": "peter.rabbit(a)example.org", > "role": "owner" > }' http://localhost:8001/3.1/members Yes. > 4) What about the commits that are used while operating in mailman > shell? Not relevant. "mailman shell" is intended for experimentation, so an explicit commit function is provided to trigger a backend database commit. This allows you to fix typos before committing, or even to exit without changing the database if you think you made a big mistake. In the REST API, each mutating REST call is a single database transaction and the commit is triggered automatically. If you have a multiple call script and something goes wrong in a later call, you will have to unwind any calls that succeeded by hand. > 5) In the unlikely event that I change from the dark side to the > good side i.e. "python programming" ;-) is there a > "to-the-point" reference for IListManager, IUserManager > etc. giving available functions (with parameters) in a kind of > list way? (the example kind of documentation referenced above is > good, but where can I find a list of all functions?) No. https://docs.mailman3.org/projects/mailman/en/release-3.1/src/mailman/rest/… is fairly complete, but the only truly complete lists are in the source. You can also go into the Mailman shell, import the relevant modules and use the help() function. > 6) I think the starting point for managing lists with python is here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > right? Yes. > 7) Going the python way will require to enter the virtual > environment, right? (otherwise the libraries, environment > variables etc. are not available...I think) For development, yes. It would be very annoying. However, in production, you would most likely use "mailman shell -r script". In that case you can invoke the script with the full path "/path/to/venv/bin/mailman" and place "script" in the venv/bin directory. This will automatically invoke the Python portion of the virtual environment (eg, sys.path will be set appropriately), but not the shell environment. Then you can use a shell script or function to abbreviate the command. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/25/22 01:14, Odhiambo Washington wrote: > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> How about https://mm3-lists.kictanet.or.ke/user_profile/ ? >> > > I have uncommented the line "WSGIScriptAlias /user-profile > /opt/mailman/mm/wsgi.py", > I don't see any definition for it in urls.py as well. Perhaps that's the > issue? It is defined in django_mailman3/urls.py which is referenced by re_path(r'', include('django_mailman3.urls')), > When I uncomment /user-profile, I end up with an ugly URL: > https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ > > So instead of aliasing the /user-profile, I have decided to add another > definition to urls.py: > re_path(r'^user-profile/', include('allauth.urls')), > Which I think gives me a cleaner URL: > https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ It shouldn't include `allauth.urls`. That URL is appropriate if you aren't logged in, but what do you get when you are? Go to https://lists.mailman3.org/user-profile/ and log in if necessary and you'll see what it should look like. > I also had to alias /accounts, which then brings me to: > https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I believe > is fine because one gets the > option to either login or signup. > > And I think that "/account" and "/user-profile" are synonymous. They are in your instance because of re_path(r'^user-profile/', include('allauth.urls')), but they should not be. >> It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time >> (I now use gunicorn on all the sites I manage), but when I did I think I >> had > > >> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py >> >> and all the URLs were like https://example.com/mm3/mailman3/..., >> https://example.com/mm3/archives/..., etc. >> > > I already had gunicorn working too, but I just need to also figure out this > mod_wsgi. Why? Intellectual curiosity or do you have an actual need. The bottom line is with mod_wsgi, whatever you have in your WSGIScriptAlias is going to be prepended to the URL path. If you don't want anything prepended, you need ``` WSGIScriptAlias / /opt/mailman/mm/wsgi.py ``` but then in order for user-profile to work, you need to replace ``` re_path(r'', include('django_mailman3.urls')), ``` in urls.py with the urlpatterns from django_mailman3/urls.py ``` re_path(r'^user-profile/delete$', delete_account, name='mm_user_account_delete'), re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), ``` and also add ``` from django_mailman3.views.profile import delete_account, user_profile ``` to the imports in urls.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Waqas Ahmed Khan

Hi, I have successfully configured Office365 to relay emails from Mailman3. I used the below configuration. change following lines in mailman.cfg: smtp_host: your-domain.com.mail.protection.outlook.com smtp_port: 25 And then configure SMTP Relay Connector in Office365, so it can recognize your server. SMTP relay doesn't use a specific Office 365 mailbox to send email. Option3 of Link: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-s… Could you Please confirm, what should be hardware configuration (ram, processor, disk) to run mailman3 server for medium size organization? This server will have 10-15 lists and some lists having 10k to 20k members. Also what should be DISK SPACE of the server for Archiving emails? Regards, *Waqas Ahmed Khan* p: +923212608044 Skype: waqas-ahmed00 <waqas.ahmed0(a)gmail.com> waqas.ahmed0(a)gmail.com [image: LinkedIn] <http://pk.linkedin.com/pub/waqas-ahmed-khan/15/96a/39a/> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 23, 2020 at 8:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > > Hi, > > > > I have installed mailman3 with postfix. The server is working fine. To > > protect the IPs from blacklisting, I want to relay all emails from > > postfix/mailman to external SMTP servers like O365, Gmail, or our > exchange > > server. > > > I would not recommend using O365 or Gmail as outgoing MTAs. I don't > really know about )365, but I don't think Gmail likes you to send mail > via a gmail server if it is not From: (or maybe envelope from or both) a > gmail or googlemail address. > > > > Could you please confirm is this possible. And how to do its > configuration. > > > It is possible and there are two ways to do it. You can configure this > in Postfix to relay all outgoing mail via some other server. > > > You can configure it in Mailman by setting in the [mta] section of > mailman.cfg > > smtp_host: > smtp_port: > > and presumably for authentication > > smtp_user: > smtp_pass: > > Also see > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > and following for other relevant settings. > > -- > 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/ >

6 years, 3 months

[MM3-users] Re: Installing mailman 3

by Kyle Richardson

It seems odd it would attempt to find the master script in /sbin. Could you please provide the outputs of `mailman info` and `mailman conf` to assist in troubleshooting? -Kyle On Tue, Jul 11, 2017 at 2:00 PM, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: > Hi Abhilash, > > I'm trying to use Mailman 3 on my centos 7 virtual machine. > > Those steps I wrote are from websites, the last console instructions are > mine. > > I don't use ubuntu, I use centos 7. > > When I run the start command I get this: > (venv3) [root@localhost mailman]# mailman start > > Starting Mailman's master runner > > /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': > > [Errno > > 2] No such file or directory > > What can I do? > > Thank you > > El mar., 11 jul. 2017 a las 12:31, Abhilash Raj (<raj.abhilash1(a)gmail.com > >) > escribió: > > > Hi Rafael, > > > > On Tue, Jul 11, 2017, at 07:32 AM, Rafael Mora wrote: > > > Hello, > > > > > > I want to install mailman 3 in a centos 7 virtual machine. I'm > following > > > these steps and I cannot make it work: > > > > I am wondering if you are interested to setup a development environment > > or use Mailman 3? > > These instructions below are for working on Mailman, if you just need to > > deploy, instructions here[1] would be the best. > > > > > 1. `cd ~` > > > 2. `git clone https://gitlab.com/mailman/mailman.git` > > <https://gitlab.com/mailman/mailman.git> > > > 3. `cd mailman` > > > 4. `virtualenv -p python3 venv` > > > 5. `source venv/bin/activate` > > > 6. `python setup.py develop` > > > 7. I am pretty sure this setup command will place a configuration file > > > into > > > `~/mailman/var/etc/mailman.cfg`. Edit this file. > > > > > https://mailman.readthedocs.io/en/latest/src/mailman/ > config/docs/config.html > > > 8. `mailman info` can confirm which configuration file is in use > > > 9. `mailman start` will start up Mailman 3 Core. This is what the > parent > > > background process command looks like in `ps -ef`: > > > `/home/ubuntu/mailman/venv/bin/python > > > /home/ubuntu/mailman/venv/bin/master > > > -C /home/ubuntu/mailman/var/etc/mailman.cfg` > > > > Looks like you are working as the ubuntu user here and the the > > virtualenv that you created exists at `/home/ubuntu/mailman/venv`. > > > > > I also tried the steps on the website > > > https://wiki.list.org/DEV/SetupDevEnvironment > > > but it doesn't work either > > > > > > What do you suggest? > > > > > > This is what I get from console: > > > > > > > > > [root@localhost ~]# cd dev/ > > > > > > [root@localhost dev]# cd mailman/ > > > > > > [root@localhost mailman]# source venv3/bin/activate > > > > Why do you try to user a different venv as a root user here? If you'd > > just try: > > > > $ source /home/ubuntu/mailman/venv/bin/activate > > > > and then try > > > > $ mailman start > > > > things would work! > > > > However, this would be a different instance of mailman and would create > > the new configuration (and the entire var directory) at the directory > > you run this command from. If you want to inhibit this, you can either > > use the -C flag, or set MAILMAN_CONFIG_FILE environment variable to > > point to your one single configuration file. > > > > > > > > (venv3) [root@localhost mailman]# cd mailman/ > > > > > > (venv3) [root@localhost mailman]# ls > > > conf.py COPYING data README.rst src > > > unittest.cfg > > > contrib coverage.ini MANIFEST.in setup.cfg template.py > > > copybump.py cron port_me setup.py tox.ini > > > > > > (venv3) [root@localhost mailman]# cd .. > > > > > > (venv3) [root@localhost mailman]# mailman start > > > Starting Mailman's master runner > > > /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': > > > [Errno > > > 2] No such file or directory > > > > > > (venv3) [root@localhost mailman]# > > > > > > Thank you > > > -- > > > > Hope that helps! > > > > [1]: http://docs.mailman3.org/en/latest/prodsetup.html > > > > -- > > thanks, > > Abhilash Raj > > _______________________________________________ > > 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

9 years, 2 months

[MM3-users] Re: Turn off social logins?

by Torge Riedel

Am 16.02.19 um 13:50 schrieb Stephen J. Turnbull: > Mark Sapiro writes: > > On 2/14/19 11:10 PM, Stephen J. Turnbull wrote: > > > Torge Riedel writes: > > > > > > > - there is a way to do this now via settings_local.py, but feels > > > > a little bit risky if default configuration changes on update of > > > > mailman > > > > > > This should not be true. If it is, we need to fix that. Will check. > > > > > > It is more or less true [...] the only way settings_local.py can > > change something like INSTALLED_APPS is to redefine INSTALLED_APPS > > in it's entirety which leads to the possibility of INSTALLED_APPS > > changing in settings.py and those changes not being picked up in > > settings_local.py. > > That's a different issue from the one I believe Torge is worried > about, which is an update overwriting settings_local.py. But it's not > good. Well, Mark got it what I was meaning. Maybe my explanation was not precise enough. Hopefully an update is not overwriting settings_local.py in any case. Is it part of delivery and then changed afterwards? Haven't checked that yet. I personally like the way other services are importing custom settings by including all config files from a given directory. Maybe it is not worth for mailman cause custom settings will not grow very big - so no need to split it in tiny files. > > > The way around this is to remove the import of settings_local from > > settings.py and then put > > > > from settings import * > > > > at the beginning of settings_local.py and then point Django at > > settings_local rather than settings. > > I don't understand the ramifications of making this change (presumably > Barry or somebody had a reason for the change from Mailman 2's > method), but at first glance it looks like a big step in the right > direction. > > > Then you can do things like > > > > try: > > INSTALLED_APPS.remove('allauth.socialaccount.providers.google') > > except ValueError: > > pass > > > > in settings_local.py except there are still issues because, e.g., > > INSTALLED_APPS is defined as a tuple (immutable) and not a list in > > settings.py. > > Given the concerns of privacy advocates, I would say that it would be > better to have a separate > > AUTH_PROVIDERS = ['allauth.socialaccount.providers.google', ...] > > in settings_local.py, and merge that in to INSTALLED_APPS. Of course > removing specific providers would be OK too, but I think that this is > a place where "deny all / accept what you want" is appropriate. > > Steve >

7 years, 7 months

[MM3-users] Help on removing moderators

by sean_sullivan＠rhoworld.com

Hello Mailman-users. I was hoping someone more experienced than myself would be able to help me with an issue I am currently experiencing. I have created a function to add moderators which works great, but I have also been trying to remove moderators as another function, but I am running into some issues. When I use the mailman shell based upon the documentation, it works great: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… everything works as expected. However, if I try and bring that in as a function that can be used with mailman withlist, I am consistently getting errors, and being that I am not very experienced in python, it has me scratching my head to say the least. from mailmanclient import Client from mailman.interfaces.member import MemberRole, AlreadySubscribedError from mailman.testing.helpers import subscribe addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] client = Client('http://localhost:8001/3.1', 'restadmin', 'restpass') def set_owners(mlist): for email_addr in addresses: try: member = subscribe(mlist, '', email=email_addr, role=MemberRole.owner ) print (member) except AlreadySubscribedError as err: print (err) def remove(mlist): my_list = client.get_list(mlist) # print(my_list.fqdn_listname) # for email_addr in addresses: # my_list.remove_owner(email_addr) The errors I am getting are: ./bin/mailman withlist -r set_owners.remove -l it-test-b(a)lists.rhoworld.com Traceback (most recent call last): File "./bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/opt/mailman3/lib/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/opt/mailman3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/mailman3/lib/python3.6/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/opt/mailman3/lib/python3.6/site-packages/mailman/utilities/modules.py", line 70, in call_name return named_callable(*args, **kws) File "/opt/mailman3/bin/set_owners.py", line 24, in remove my_list = client.get_list(mlist) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/client.py", line 347, in get_list 'lists/{0}'.format(fqdn_listname)) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 404: 404 Not Found So, I am wondering, is it possible to do something like this or am I completely misunderstanding the documentation, and why do I get a 404 here, when in the shell everything works as expected. I know I must be missing something, but cannot for the life of me figure out what that is. Any help would be greatly appreciated. Thanks, Sean

6 years, 6 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

The May 4th digest that went out was _also_ size-triggered, so this may have nothing to do with periodic digests at all, and possibly my periodic digests aren't working. I'm not on any of my own lists in digest mode, I'm slowly extracting diagnostic information out of people who are. Also, since this is a ~2 month cycle, it's really difficult to get data points to work with. I'll need to remember to go in and look when this settles down again (new cycle of activity started last night) to see if there's anything left pending. (venv) root@host2:/home/lists/mailman/venv/bin# pip freeze | grep -i hyper HyperKitty==1.3.7 On 6/4/2023 10:05 PM, Mark Sapiro wrote: > On 6/4/23 18:35, Joel Lord wrote: >> >> The periodic digests do seem to be coming out. I also now have >> confirmation that the one message in this morning's digest that was >> from May 4th was also included in the last digest back on May 4th, so >> it seems that the one message was left behind in the digest queue when >> the periodic digest was sent. > > I don't see how that can happen. The process that sends a digest renames > the var/lists/<list-id>/digest.mmdf mailbox file in which the messages > are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, > where <volume> and <issue> are the volume and issue numbers of that > digest, and then queues a message in the `digest` queue to tell the > digest runner to create the digest from the messages in that mbox and > send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file > behind and that is created anew when the next post arrives. Further, if > there is a non-empty digest.mmdf file, its messages should be sent no > later than the next 11 PM `cron digests`. > > >> There was one earlier message to the list back on May 4th, before the >> one that got duplicated, but I can't tell if that triggered a >> size-based digest to be sent: the logs aren't clear enough on that >> detail for me to tell > > > OK > > >> Just to inform things: >> >> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman >> django-mailman3==1.3.9 >> mailman==3.3.8 >> mailman-hyperkitty==1.2.1 >> mailman-web==0.0.6 >> mailmanclient==3.3.5 >> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper >> mailman-hyperkitty==1.2.1 > > Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up > to date as are the others. > >> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post >> postorius==1.3.8 >> >> > -- Joel Lord

3 years, 3 months

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/25/23 1:31 PM, Ken Alker wrote: > > I moved the .psv file from the bad queue into the shunt queue. I then > ran "mailman unshunt" (as user 'mailman' while in the virtual > environment). I tailed mailman.log during this process and no logs were > spit out. The date stamp on the .psv file never changed (maybe it does > not when being moved between queues?) and, AFAICT, the file never moved > from the shunt queue. I waited maybe five minutes, tops. I forgot that the extension in the `bad` queue is `.psv` (for preserve). You have to rename it to `.pck`. >>> Is there a way to reprocess the bad queue? >> >> You could just move the messages to the 'in' queue. Changing .psv to .pck in the process. this can be done, e.g., by ``` for file in `ls var/queue/bad/*.psv;do mv /var/queue/bad/$file /var/queue/in/${file/psv/pck};done ``` > I just now tried moving the same message into the 'in' queue but, again, > nothing happened. I left it in there for five minutes. Do I have to > run a program to get it to act on the 'in' queue (I presume that there > is a "runner" that is always looking and taking care of this already as > I presume this is the queue where all 'normal' traffic is handled). Again, you need to change the extension to .pck. > Here are the (obfusacted) results of "mailman qfile > /opt/mailman/mm/var/queue/shunt/1675389793.6945386+2aeaf0015558c9d8380c96142c3fa9d03a8142bc.psv" (the message I was experimenting with): > > [----- start pickle -----] > <----- start object 1 -----> > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Subject: THE-list subscription notification > From: email(a)obfuscated.com > To: the-list-owner(a)lists.obfuscated.com > Message-ID: <167538979369.2390432.521344217673230839(a)obfuscated.net> > Date: Thu, 02 Feb 2023 18:03:13 -0800 > Precedence: bulk > > user(a)domain.tld has been successfully subscribed to THE-list. > > <----- start object 2 -----> > { '_parsemsg': False, > 'envsender': 'email(a)obfuscated.com', > 'listid': 'the-list.obfusacted.com', > 'nodecorate': True, > 'recipients': {'person(a)domain.tld'}, > 'reduced_list_headers': True, > 'version': 3} > [----- end pickle -----] I was assuming these were list welcome messages which they aren't. They are owner notifications, so they were sent to the -owner address and processed through the owner-pipeline, but unless the Debian package changed the default-owner-pipeline, it doesn't contain mime-delete so how they ended up in the `bad` queue is still a mystery. However, what would be the point of resending these at this time? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Issue with Docker Postfix and Mailman3 Configuration

by Stephen J. Turnbull

recida8902--- via Mailman-users writes: > When I send an email from my configured email address, What "configured email address"? Do you mean the administrator email address for the Mailman applications? If so, that doesn't matter; the only things Mailman uses it for are (1) as the return address for some automatically generated email and (2) as a place to send certain error messages. It is not specially routed because it is mentioned in the Mailman configuration. It is specially routed because of the host it originates on, and perhaps filtered differently according to some component of the address. > it is successfully delivered to the intended recipients. However, > when someone else sends an email to the same address, it does not > reach the Mailman application, and no error messages are generated. The first thing you need to do is find logs of various messages. For mail transfer agents (MTAs or "mail servers") it's usually in /var/log/postfix/mainlog (I think) or /var/log/mail.log, sometimes in /var/log/syslog or /var/log/messages. Most likely you just need to trace one example each of a message from the "configured address" to Mailman and a message from "outside" to Mailman. Find where the messages that don't get through have a receipt but no transmission. This will most likely be from your border MTA to Mailman, or from your border MTA to your Dockerized Postfix. > 3. Checked the Mailman configuration: I reviewed the configuration > files of Mailman and ensured that all necessary settings are > properly configured. However, I couldn't identify any specific > variables or options related to incoming email handling. There aren't any. Once it gets to Mailman, either it's related to a list or one of the sitewide administrative addresses, or it gets rejected as incorrectly addressed. Incoming mail is handled by the MTA which sorts out Mailman mail vs any other mail. All interesting configuration is in the MTA, Postfix in your case. However, the problem is most likely at the network level, not the mail level. Configuration of Postfix for Mailman is a long-solved problem. First, your Docker host needs to be correctly configured to talk to the Internet side of your network and to the containers' network, and to function as a gateway between the two networks. The issue is that the containers use so-called private IP addresses, which cannnot be reached from the public internet. My guess is that the most likely problem is that your border MTA is misconfigured in trying to talk to the next hop (either the Postfix MTA or Mailman itself). To figure that out, you need to trace messages until they disappear, find out what the actual IP addresses being used by each host are, and what addresses the MTAs are configured to send each mind of mail to.

3 years

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Thu, Feb 16, 2023 at 10:26 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 23:04, Odhiambo Washington wrote: > > > > The last time I referred to the link, I deliberately duplicated the <LC> > > folder in two locations: > > [09:51 ~ ]$ ls -al /opt/mailman/mm/var/templates/site/en/ > > total 48 > > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:53 .. > > -rw------- 1 mailman mailman 615 Jan 17 13:57 > domain:admin:notice:new-list.txt > > -rw------- 1 mailman mailman 341 Jan 17 13:54 > list:admin:action:post.txt > > -rw------- 1 mailman mailman 158 Dec 17 13:32 > list:member:digest:footer.txt > > -rw------- 1 mailman mailman 452 Jan 17 13:54 > list:member:digest:masthead.txt > > -rw------- 1 mailman mailman 137 Jan 17 13:55 > list:member:generic:footer.txt > > -rw------- 1 mailman mailman 1219 Dec 8 15:12 > list:member:regular:footer.txt > > -rw------- 1 mailman mailman 944 Jan 17 15:50 > list:user:action:subscribe.txt > > -rw------- 1 mailman mailman 247 Jan 17 13:56 > list:user:notice:post.txt > > -rw------- 1 mailman mailman 802 Jan 17 13:56 > list:user:notice:probe.txt > > -rw------- 1 mailman mailman 639 Jan 17 13:57 > list:user:notice:welcome.txt > > > > Yet, it is NOT being picked. So definitely something is wrong somewhere. > > > If you have the same list:* file in both > /opt/mailman/mm/var/templates/site/en/ and > /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > the ones in the lists directory will take precedence for that list over > the ones in the site directory. > In my case, I had the exact same files in the two paths and the list:user:action:subscribe.txt was still not used in my tests. Why? I have now created the directory: mkdir -p /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ And I have placed the same files in there. Gearing up for a test to see if the template will be used this time around. > See > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > for a discussion of the search order. > Will do. > >> > >> Are the other templates such as list:member:regular:footer.txt used? > >> > > > > I do see that in posts to the list, but I believe that is perhaps only > > working because the list had that footer when it was imported from MM2. > > A template from import21 of the kictanet(a)lists.kictanet.or.ke list will > be stored in the > /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > directory. > It wasn't a template per se. It was the regular nondigest msg_footer from MM2. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 7 months

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Christian Schneider

Thank you for your instant reply! Mihai Moldovan wrote: > > But I could find no information about the location where hyperkitty stores the archives on an Ubuntu-/Linux-system. > > I assume the archives are stored underneath "/var/..." this is only a guess. > > But is this guess right? > > Not quite. > To the best of my knowledge, by default, a venv installation is fully contained > under /opt/mailman, with archives and stuff stored at /opt/mailman/var/lib/... This information is very helpful! Actually I have about 45GB of archives and these archives only hold messages of the last year... I run a clean-up script every first day of a month which deletes posts older than 365 days... So there is lot of disk space needed... ;-) (and even more if I plan to keep posts around for a longer time) > > Another question is: > > How much space do I have to plan (roughly) for the "/opt"-partition for the mailman install if the archives are stored under "/var/..."? > > Depends on your archives, the way things are archived (you can choose different > database backends, and these might make a difference in how efficiently or > inefficiently data is stored) and whether you want to use the full-text search > index, which adds another big chunk of data. > I can give you a few pointers regarding my setup: my mailman 2.1 data directory > takes up about 8.2 GB of disk space, most of which are archives, naturally (8.1 > GB). I've imported most of the big archives to mailman 3 already, with a > full-text search index, and that uses 5.2 GB disk space currently, but I'm still > missing a few archives, so that'll still grow a bit. It will probably end up at > about the same size, but I can come back to that once my import is fully done > (which sadly will take a few days). > Now, the 8.1 GB of mailman 2.1 archives are stored pretty inefficiently, because > they are essentially duplicated (as a private mbox archive and public text > archives). Mailman 3 doesn't do that - at least not directly - but instead > stores archives once into the database, and queries the database whenever the > archives are accessed via hyperkitty, so I would *assume* the size you need for > the mailman 3 data after a successful migration is just a bit shy of what you > needed for the mailman 2.1 data, maybe even a bit less. Perfect! :-) If I mount an extra partition of 250Gigs at /opt this should carry me for a longer time... And - if I setup a logical volume with LVM - there is an option to stack up the space with ease... ;-) > Mihai Thank you very much for your help! Chris

1 year, 5 months

[MM3-users] Re: Deleting A List

by Mark Sapiro

On 5/3/24 03:59, Odhiambo Washington wrote: > On Thu, May 2, 2024 at 8:11 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/2/24 03:42, Odhiambo Washington wrote: >>> I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. >>> I can see from Django Admin UI that the archives are still intact. >>> I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke >>> Is there a way to move the archives from the old list to the new list? >> >> >> Change the `name` and `list_id` in the list's entry in the >> `hyperkitty_mailinglist` table in the database. If there is already an >> entry there for the new list, delete it >> >> > ``` > mysql> select id, name, list_id from hyperkitty_mailinglist; > +----+----------------------------+----------------------------+ > | id | name | list_id | > +----+----------------------------+----------------------------+ > | 1 | skunkworks(a)lists.my.co.ke | skunkworks.lists.my.co.ke | > | 2 | list(a)nog.ke | list.nog.ke | > | 3 | eanog(a)lists.my.co.ke | eanog.lists.my.co.ke | > | 4 | isoc(a)lists.my.co.ke | isoc.lists.my.co.ke | > | 5 | kazi(a)lists.my.co.ke | kazi.lists.my.co.ke | > | 6 | kenog(a)lists.my.co.ke | kenog.lists.my.co.ke | > | 7 | mechanics(a)lists.my.co.ke | mechanics.lists.my.co.ke | > | 8 | science(a)lists.my.co.ke | science.lists.my.co.ke | > | 9 | security(a)lists.my.co.ke | security.lists.my.co.ke | > | 10 | vmware_tech(a)lists.my.co.ke | vmware_tech.lists.my.co.ke | > | 11 | water(a)lists.my.co.ke | water.lists.my.co.ke | > | 12 | wordpress(a)lists.my.co.ke | wordpress.lists.my.co.ke | > | 13 | list(a)lists.nog.ke | list.lists.nog.ke | > +----+----------------------------+----------------------------+ > 13 rows in set (0.00 sec) > > mysql> delete from hyperkitty_mailinglist where id = 13; > ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key > constraint fails (`mailmansuite`.`hyperkitty_mailinglist_owners`, > CONSTRAINT `hyperkitty_mailingli_mailinglist_id_a47e04ec_fk_hyperkitt` > FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperkitty_mailinglist` (`id`)) > ``` > > Is there an easier way? > I need to delete id=13 then rename id=2 > There are several tables that reference the hyperkitty_mailinglist table by id. These are hyperkitty_email, hyperkitty_mailinglist_owners, hyperkitty_mailinglist_moderators and hyperkitty_thread. Ideally, you wouldn't have created the list(a)lists.nog.ke before updating the hyperkitty_mailinglist entry, but now, do the following: ``` update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_owners set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = 13; delete from hyperkitty_mailinglist where id = 13; update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = 'list.lists.nog.ke' where id = 2; ``` If there have been no posts to the list(a)lists.nog.ke list the updates of hyperkitty_email and hyperkitty_thread won't do anything, and likewise the update of hyperkitty_mailinglist_moderators if the list has no moderators -- 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: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 7/14/20 3:54 AM, Brian Carpenter wrote: > On 7/14/20 6:49 AM, Gilles Filippini wrote: >> Mailman Core logs: >> [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) >> [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) >> [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 > > I am pretty sure that timeout is related to gunicorn. If it is, then > increasing the worker out timeout setting for gunicorn should work. You > tend to get such errors when doing an export of a large membership > roster. This is the first time I have seen it related to a held message. It seems weird that a gunicorn worker would run for more that the default 30 seconds because of a 23MB message, but I think Brian is correct. > I have this in my setup: > > mailman.cfg: > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > gunicorn.cfg: > > [gunicorn] > workers = 4 > timeout = 900 > > You will need to restart gunicorn after adjusting the timeout setting. It's confusing, but after adjusting that setting, you need to restart Mailman core, not gunicorn. If you are running a gunicorn service, that is what is providing WSGI support for Django (Postorius and/or HyperKitty). You may be using gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is not the gunicorn we are considering here. Regardless of what you use to provide WSGI support for Django, Mailman core uses gunicorn to support the REST API, and that is the gunicorn affected by the settings in the gunicorn.cfg pointed to by [webservice] configuration: /opt/mailman/mm/gunicorn.cfg If, with the above configuration, you do `ps -fwwA|grep runner=rest` you will see something like: mailman 20582 20561 0 01:21 ? 00:00:16 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20722 20582 0 01:21 ? 00:01:19 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20725 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20726 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20727 20582 0 01:21 ? 00:01:50 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 The first of these, pid 20582, is Mailman's actual REST runner. The other 4 with parent pid 20582 are the 4 gunicorn worker processes forked from the REST runner. It's the REST runner or Mailman core that needs to be restarted to pick up that change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Settings for prevention of spam obfuscation

by Thomas Ward

I think we forget DMARC can operate with SPF only mode. If you truly want stronger antispam controls then deny all posts from nonmembers, and/or implement SpamAssassin at the postfix level with extended OSINT pattern sets and policies. That will catch MOST stuff but also likely have a higher false positive moderation / reject rate Sent from my Galaxy -------- Original message -------- From: Richard Rosner <rrosner5(a)gmail.com> Date: 2/24/24 10:57 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Settings for prevention of spam obfuscation Well, I don't want to give users additional information, just rectify the manipulated information. And yes, while there may be edge cases where these bad practices do come in handy, but the vast majority of mails (at least from what I can tell from my lists) is either spammers or unnecessary abuse of features. I can't tell if it's because Microsoft sets bad defaults for Outlook or admins hired are incompetent and the competent ones either retire or quit, but there's just too much going on in mails that's just nonsense. E.g. encoding all text - including stuff like the subject - with base64 is just ridiculous, when what was sent is only plain text that uses a small subset of UTF-8 characters. And that's just a very common bad practice and far from the only one. And sure, competent spammers may be able to evade much more, I've seen several emails that must have had manipulated sender data, but that could only be concluded from context, not from analyzing the headers. But thankfully most spammers are far from competent, so spam filters can easily detect far over 50 % of the spam. It's only the slightly more competent spammers that use tactics abused by many non-spammers that give me a headache. I could easily crank up the spam points for various indications, so there would be pretty much no spam left in the false negative category. But sadly, I know from experience that this will lead to a much larger amount of false positives. For the most common senders that won't be sending spammers, I already created whitelisting rules, but that's about it. And until someone can create an ML model that's not gobbling up resources for training and that doesn't need thousands of emails to train with, there's only so much you can do. While DKIM and DMARC are great, they are useless when the vast majority of senders don't have any DKIM signatures. For ARC it's not as uncommon to be present, but the situation isn't that much better. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 7 months

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

by Abhilash Raj

Hey Everyone, I just tagged and uploaded Mailman Core 3.3.5 release. This release includes both bug fixes and some new features. A full list of changes is available here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… You can install this version using pip: $ pip install mailman==3.3.5 The release tarball is available on PyPI as well: https://pypi.org/project/mailman/3.3.5/#files Thanks to everyone who made this release possible! Abhilash > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hey Everyone, > > I just tagged and released Mailman Core 3.3.5rc1 release. > > This is identical to 3.3.5b1 in code, the only changes that have been made are in utility scripts and testing configuration. > > You can install this version using: > > $ pip install --pre mailman==3.3.5rc1 > > If you want to download a release tarball, you can do so from here: > > https://pypi.org/project/mailman/3.3.5rc1/#files > > This is the first (and only) planned release candidate for 3.3.5 release. The stable release is planned for next week. > > thanks, > Abhilash > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: >> 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) -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: Mailman not able to process "big" requests

by Jonas Felber

Thank you for your support, I got informed that we are now able to send out emails again. The problem was that the crashes we got while mass subscribing led to database corruptions. (From what I know, the problem was on our side, as we kubernetes did not properly restore some files after restarting so the database got corrupted (apparently we are running now a cleanup script on each restart)) There are still some problems, but I just wanted to send out a quick update. Thanks for your support, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch > On 24 Apr 2018, at 17:21, Darren Smith <silas.crutherton(a)gmail.com> wrote: > > Our installation at https://lists.rootsweb.ancestry.com has around 33,000 > lists and somewhere around 1.5 million members. We have lists with 5,000+ > members. > > Note that I haven't tried any mass subscriptions. When we upgraded from > mailman 2 to mailman 3, we used the old .pck files and ran the import on > each of the lists. It did take about 6 weeks to do the full import all > 33,000 lists. I'm not joking. > > As for sending messages - there isn't any problem sending that many > messages out, but then we are also not trying to subscribe list members at > the time. We are, though, in the process of importing the old archives from > our old mailman 2 system. This doesn't seem to affect the rest of the > system. > > We have seen some inefficiencies in the new system, such as the front page > of postorius - loading all of the information for 200 lists (if the user > set the "lists per page" to 200) was bringing down the system. We have our > own metadata system to be able to search for lists by state/region/surname > (ours is a genealogy mailing list system), so we had to replace the front > page with our own "find a list" functionality. > > The other main problem was the page where a user can see what lists they > subscribe to. That page was also a denial of service if the user had > several hundred lists they are subscribed to. And for a genealogy mailing > list system, this is common. > > We have actually ended up creating our own API layer (only accessible on > the local machine) and make certain calls to it for the most painful of the > issues. One of these days (when we get a moment to breathe) we are going to > post some of our changes to the project so that we can ditch our own API > and just use the internal REST API. > > To be fair, the inefficiencies are not necessarily with mailman or the rest > API itself - but with Postorius making hundreds of calls to load a single > page. Though if the API supported loading multiple lists at once instead of > having to load them serially, that might help as well. > > So while we have not seen any timeout issues on the call to mass subscribe > users, we HAVE found several other calls that are effectively a denial of > service and have gotten around them ourselves, with plans to contribute to > the project in the near future. > > -Darren > > >> On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 04/24/2018 12:36 AM, Abhilash Raj wrote: >>> On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> >>>> We also have a problem with sending out emails to "large" (>50) groups, >>>> as they seem to not getting sent out at all. Do you have any idea what >>>> the problem here could be? >>> >>> Which MTA are you using? What do you see in mailman's logs and MTA's >> logs? >>> >>> I haven't seen this kind of problem before with Mailman 3. This very >> list is hosted using Mailman 3 and I believe has more than 50 subscribers. >> >> >> Nor have I seen this issue. This list currently has 158 non-digest >> members. There are several @python.org Mailman 3 lists with over 100 >> non-digest members including the active yt-users(a)python.org list with >> 301 members, and I have gotten no reports of an issue like this. >> >> Also, there are over 600 lists at <https://lists.fedoraproject.org/>, >> and I don't think this is an issue there either. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 5 months

[MM3-users] Re: ARC

by Stephen J. Turnbull

Marvin Gülker writes: > However, I thought the entire point in ARC was fixing automatic > rejections caused by DMARC invalidation by mailing lists, which are > vital for so many open-source projects (including Mailman iself). Yes. s/fixing/making it possible to fix/ and s/mailing lists/indirect mail/ (the REALLY big losers in April 2014 were small businesses which had a large percentage of their invoices become undeliverable). That doesn't help you one bit with your "rejection with no reason" problem, though. It helps you with one specific reason (DMARC p=reject). > If ARC falls short of solving that problem, because the large > providers do not automatically trust ARC, then supporting ARC on my > mailing list server is kind of void. Why should almighty Microsoft > trust my small personal mailing list server? The answer to that is "why shouldn't they?" I've never had a problem with any of the big services. There are reasons why some hosts might have problems due to no misbehavior of their own, and they wouldn't necessarily know about them either. But mostly the mail does go through. If the mail itself gets through, I see no reason why they wouldn't trust your ARC fields, so you won't get DMARC rejections, as long as nobody downstream of you breaks your ARC signatures. If you're seeing something different (ARC-authenticated messages getting rejected for DMARC alignment failure), let us know and I'll talk to a guy who knows this gal. My experience is good, the people I talk to are happy. If your experience is different, the ARC developers should know about it, otherwise we can't do anything about it. > ARC can only achieve its goal with black-listing untrusted relays > rather than white-listing known good ones, The goal of ARC is to keep users at p=reject sites happy. A lot of the people involved both at the IETF and at the DMARC Consortium are old-timers who are very sympathetic to mailing lists. But the day-to- day tuning of algorithms is targeted at users with mailboxes, not the lists that fill those mailboxes. Sad to say, users care more about spam (that's their provider's fault) than about mailing lists (which they assess as the mailing list's fault). Last I heard the Google folks and the IETF are very happy with ARC. > because it is simply unfeasable to manually maintain a list of all > open-source project mailing lists in the entire world. I could set > a new one up tomorrow, how should you know? That's not how this works. All of these services use huge databases of spam, ham, hosts, and mailing lists, and apply machine-learning algorithms to that data to create classifiers. It may take them some time to tune them for ARC, but the principle is there's no black or white here, it's all grey. Steve

7 years, 1 month

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

by Jana Berger

On 22.09.2023 18:32, Stephen J. Turnbull wrote: > 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. You can see the same or similar result by opening the EML I quoted. Does the list support attachments? Then I will attach the file directly. > > > 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? Sorry, I should have made that clearer - when opening the EML file with e.g. Thunderbird, the contents (message text) of the mail as displayed is the garbled string. I assume it is the result of Thunderbird trying to process the contents as base64-encoded, which it is not. > > 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. I have multiple control messages, all received from my instance which all contain the "Content-Transfer-Encoding: base64" marker, their contents is plain text (Content-Type: text/plain; charset="utf-8"), but they are still encoded using base64. Of course that is not proof, but an indication that it is either done by the mail server itself or widely across MUAs. > > 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? Global "Preferred language" is "English (USA)", which is not overridden by the list in question. I have not changed the default encoding. Is there a surefire way to detect this? My mailman.cfg has no section pertaining to encoding, and all related files also do not mention encoding.

3 years

[MM3-users] Re: Advice on upgrading..

by Stephen J. Turnbull

Mark Sapiro writes: > On 8/3/26 6:41 AM, Stephen Daniel wrote: > > > > I'd like advice on how to migrate mailing lists and archives from > > the old install to the new one. Is there a standard procedure? > > Just point the new installation to the existing database(s) and run > the django admin migrate command. You will get a working installation with all your lists in place with this simple approach. There are a few caveats that probably do NOT apply to you: 1. You need your config files to be outside of Mailman's installation tree. (Most people have them in /etc/mailman3, so no problem.) 2. You may have edited some template files in place in $var_dir. These edits need to be merged into the new ones, which may have changed. (Most people use Postorius to customize email templates, which are saved in the database rather than the file system. More installations have customized Postorius's own templates and CSS for corporate logos and disclaimers, etc., which need merging.) 3. You may have customized the code, most likely by using an external text indexer for HyperKitty. Any code to link the indexer to KyperKitty will need to be installed by hand in the new venv. (This is pretty likely, in fact, since Whoosh is very inefficient and no longer recommended for production.) > > My current implementation uses the Python venv installation > > method. I'd prefer a more container-focused installation, but > > since I don't believe Mailman 3 has official container images > > yet, I plan to continue with the venv approach. Please let me > > know your thoughts. > > See https://docs.mailman3.org/en/latest/install/docker.html I take it from your (OP's) preference for containers that you're familiar with them. I'm a Docker newbie, and found the documentation confusing. I think because there are aspects (like use of environment variables in config files) that must have been implemented in Mailman but are not commonly used in plain venv installations. There are a number of comments in the docker-compose.yaml(s) and Dockerfile that are bitrotted, and docker itself emits some deprecation warnings. I'd have to say this is not ready to be promoted to "supported" for those reasons, but they're mostly cosmetic. FWIW, I do think the implementation itself is detailed and solid. It appears to be getting quite a lot of attention from beta testers, including patches. The only thing I should warn is that mail routing demands a lot of the network admin. The most common complaints I've seen about the package is that trying to integrate with a larger network of containers gets messy. If Mailman suite is isolated in its own network, it should be straightforward, Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month, 4 weeks

[MM3-users] Re: Process on migrating mailman

by Mark Labeste

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

2 years, 8 months

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/9/25 14:23, Dan Caballero wrote: > Hello, > > At the request of a list owner, we changed the settings on a list to "Anonymous = No" so that list members could see who a message was coming from. > > It seems a side effect of the setting is that users are now using "reply-to" and some messages are going out to the list addressed in the manner below. > > "Last Name, First Name via list-name <list-name(a)caltech.edu>" This is a consequence of DMARC mitigations. > The list owner feels this is confusing and some members may inadvertently email the list when they intend to email the individual. When the From is munged in that way for DMARC the orikinal From is put in Reply-To: or perhaps Cc: depending on other settings. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc… for details of this process and its goals. Assuming your list's Reply goes to list setting is No Munging The original From: should be in Reply-To: of the delivered. It appears that the messages that are sent To: Last Name, First Name via list-name <list-name(a)caltech.edu> are sent by an MUA that is ignoring Reply-To: and replying to From:. > I understand this is likely a client side caching issue since most email clients create an index of contacts based on previously received emails. > > Aside from reverting back to "Anonymous = Yes", is there any setting we can change at the list level to force the "to" field to persist as the list email address? Do you mean you want the From: in delivered messages to be the original poster's From: so that replies to the From: go to the OP. You can accomplish this by setting DMARC mitigation action to No DMARC mitigations, however this will ensure that any mail whose From: domain publishes a DMARC policy of quarantine or reject will most likely be bounced by all large ESPs. We do are best to ensure that a simple reply to a message to which DMARC mitigations are applied will go to the poster unless the Reply goes to list setting says otherwise. But I am confused as to your goal. Previously when the list was anonymous, all replies went to the list. Maybe your goal is to have list replies be addressed to <list-name(a)caltech.edu> rather than Last Name, First Name via list-name <list-name(a)caltech.edu>. If that is the goal, you could try setting Reply goes to list setting to Reply goes to list. That will set a Reply-To: list's short description <list-name(a)caltech.edu>. That may be what you want as long as the responder's MUA honors Reply-To: over From: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 11:53 AM, Ken Alker wrote: > > Is the var/messages hierarchy also where all the archived emails are > stored for future viewing via the web interface? No. They are stored in the hyperkitty_email and hyperkitty_attachment tables in the database. >> Also, there is a long thread at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa >> d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be >> relevant. > > I have never used the mailman shell before, but based on the referenced > thread I learned to do this (note that the thread also taught me how to > rewrite it to narrow down to just the list with issues so I didn't > delete held messages in other lists, if my case): > > for verification: > > venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print (f"""\ > ... Sender: {data['_mod_sender']} > ... Subject: {data['_mod_subject']} > ... Date: {data['_mod_hold_date']} > ... Reason: {data['_mod_reason']} > ... """) > ... > and then to delete the two messages: > > (venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print(f'request id: {request.id}, deleting') > ... requests.delete_request(request.id) > ... > sbarc-list.lists.netlojix.com > request id: 27, deleting > request id: 28, deleting > >>> > > The result of this, however, was that the web interface still claimed I > had two held messages. I wasn't sure if there was some cron-type > "sweeper" process I had to wait to auto-run or if I had to manually do > something to create an update. I then realized that the sample script > had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered > the script (but it didn't spit out that it deleted anything this time) > and got an error when I did the commit. Was this in the same `mailman shell` interaction or a new one? What was the error? > So, I figured the messages HAD > been delete and the commit wasn't really necessary. When I went back to > the web interface, the number of held messages was at 0 and I no longer > get the original error when clicking on "Held messages", so my issue is > solved. But this does leave me with some educational questions: > > 1) Did I affect something somehow with my "commit", or was there a job > that cleaned things up (if so, what job)? I'm not sure of the sequence of events, but I think you probably looked in Postorius before you quit `mailman shell` and then you quit `mailman shell` with ctrl-D which did an implicit commit. > 2) Is the "commit" even necessary (I saw it in someone else's script in > the thread)? It is necessary to explicitly commit() or quit with ctrl-D to actually update the database. > 3) Is there a way to save a script and then execute it via shell rather > than typing it in every time (it appears from the examples that people > are typing them in every time, which is super tedious; I didn't paste > for fear of doing something damaging, but maybe that would work)? Yes, you can save a script in the bin/ directory in your venv and run it with `mailman shell -r`. See `mailman shell --details`. > 4) Are the request.id's of the messages dynamic/changing, or are they > fixed for life? I thought I'd delete based on exact request.id without > looping but I was afraid maybe they were changing over time and that > this wouldn't be a good idea. Might be nice to know for the future. The request.id is constant for that request object. The request object is fixed for a specific held message request. I.e., a specific held message's request object and its request.id and other attributes are fixed until that request is handled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Fri, Dec 21, 2018, at 12:18 PM, Odhiambo Washington wrote: > > > On Fri, 21 Dec 2018 at 20:19, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> On Fri, Dec 21, 2018, at 4:00 AM, Stephen J. Turnbull wrote: >> > Abhilash Raj writes: >> > >> > > Exim experts would be able to help you better with this. >> > >> > I'm the one who set up the original sample Exim .conf, because (a) I >> > didn't want to migrate all my bots to Postfix, and (b) the one-real- >> > host .conf turned out to be trivial. I'm an Exim expert only for my >> > own configuration, which is a (pre-global-warming) glacially-moving >> > target. I've never seen anything like the problems described here, >> > sorry. Can't help. >> > >> > Since it's looking like we don't have any real Exim experts hanging >> > around here, perhaps we should move the sample containers and other >> > default configs to assume Postfix and document "Exim should work but >> > you're kinda on your own, we'll do what we can but it's limited." At >> > least Mark is maintaining such systems, and they're probably better >> > documented than Exim for the single-real-host configuration, though >> > they would probably run into similar problems with the containerized >> > setup. WDOT? >> >> >> Originally, the reason I went with Exim was because the postmap + hash >> files were hard to generate for Mailman from within the container when >> the postfix was running on the host. Exim checks existence of certain >> paths to verify that the Mailing List exists, which was easier to do. >> >> However, now Mailman Core supports regex maps for Postfix, which >> can be used with containers. >> >> Images already support using Postfix, it is just not the default in setup >> scripts and documentation. I have opened an issue[1] to maybe change >> that if some initial testing doesn't goes fine. >> >> [1]: https://github.com/maxking/docker-mailman/issues/282 > > > Hello Maxking, > > It is importantest to maintain Exim support :-) I didn't mean to say that we are going to stop supporting Exim, it is just that I'll make Postfix default in Container given that most of the Mailman Devs are more comfortable helping out people with Postfix issues, as they use it for their own personal setups. Switching between default and non-default would be easy and both of them will be supported, to the best my own abilities :) > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) -- thanks, Abhilash Raj (maxking)

7 years, 9 months

[MM3-users] Re: Importing mbox files into archive defect with lines with From

by Alex Schuilenburg

Hi again. On 20/09/2023 17:59, Stephen J. Turnbull wrote: > [...] > I suspect that "DROP DATABASE mailmanweb;" and then loading the dumped > database, followed by `mailman-web migrate` will work. (Usual caveat > of you should have a backup onsite, a backup in a bank vault, and a > backup store on the dark side of the moon before trying this!) That exactly what I did in my initial attempt. It was a straight dump and restore which does as its first cmd "DROP DATABASE mailmanweb;" As per https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, the migrate error was the table django_content_type already exists. Indeed it exists in the old database, but other tables do not (list owner & moderator, and other social media tables). So if a mailman-web dpkg update also updated the database, then Debian's update clearly did not properly log the changes. Or maybe they were logged elsewhere like in /var/lib/mailman3 in the old machine which also needed to be carried over to the new - so updating on a new machine involved copying over not just the database, but some other files that provide db state? [...] > > After all, I would expect that an export of the archive to mbox, > > followed by a delete of the archive, followed by a > > hyperkitty_import of the archive, should leave you at the same > > place. > > You would expect, for sure. You would be wrong, because mbox is a > lossy format by design. (Or by lack of design, if you prefer.) I'll stick with "whatever mechanism you provide to produce an export should include a mechanism that can import it". It's like: Here is a way you can back up your data (through an mbox export), but by the way, the format we back it up in is broken so restores (mbox import) are not guaranteed. That's just broken logic IMHO, especially since the "fix" in this case is so simple. Yes, mbox is broken in a multitude of ways, but if hyperkitty is going to produce an mbox export of a list that is stored in a database (i.e. it has to construct the mbox), hyperkitty ought to do so in a format that it can at least re-import. My 2 pence worth... Of course this may all work for you, if you are using other backend combinations... I should mention that I had to re-apply and rework some of my old patches back into Debian's libs. For example, update_index_one_list fails when using xapian with "Key too long" errors, so I had to re-apply the patch I contributed in https://gitlab.com/mailman/hyperkitty/-/issues/322. Sad that I am now of the age where I search for an issue only to discover I provided a patch for it 2 years ago ;-( -- Alex

3 years

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

by nate

(In case the list admin/moderator sees this message I sent this email again from the wrong FROM: address a few minutes ago, re-sending with the right one now, please discard that bad message(have not gotten confirmation it was held for moderation) -- side note with MM2 it gave the user the option to discard their own message if it was held for moderation if I recall right. My very first post to this list was held for moderation (sent from correct FROM: address), not sure why it was held(it got through eventually), was assuming that perhaps I triggered a bug in that the fact I am using the text mailman in my email address maybe tripped something I don't know, but I was seemingly unable to view the status/discard that message.) On 2022-01-26 7:22, David Newman wrote: > Yes, this is possible. The IETF, the body that defines Internet > technical standards, is still on MM2. I’m with them; given my druthers > I’d run MM2 forever because it Just Works. > > Then again, I put a high priority on keeping the base OS and > applications patched against current security vulnerabilities. That’s > getting harder to do with MM2. > > Debian and FreeBSD have deprecated Python 2. MM2 still has maintenance > releases but no new development. MM2 also has some archaic design > decisions such as sending user passwords in plaintext email. > > Like it or not, MM3 and related components are current, and currently > maintained. I wasn’t crazy about the learning curve to get MM3 > working, but I pressed on because it will provide a platform I can > keep running much farther into the future. Thanks for the insight, I read another post from someone yesterday saying they had 35 years of experience and were having a bunch of issues, much more serious situation(real users impacted) than mine. I think I will go the route of MM2, probably setup a new VM and get postfix to just route the email for MM2 to the other system for processing. Then I guess I would need some proxypass rules in Apache to forward the cgi requests to the other system. I don't recall any serious security issues over the years with MM2 (at least ones that made tech news), grand scheme of things for my use case I think it would be ok, just stick with Devan 3.x for MM2 for the foreseeable future. Feels super weird building a dedicated system for just this but I have plenty of hardware resources to do it. I already have an LXC container at home for a legacy software product (TV Mobili, AFAIK last version came out in 2015) on Devuan 3 which I never plan to upgrade just to be safe. Time for one more, well this case would be a VM running at my colo. Hopefully can work on it today, though am not in any rush. thanks nate

4 years, 8 months

[MM3-users] Re: Archive not updated

by Marc SCHAEFER

Hello, On Mon, Sep 02, 2024 at 09:08:09AM -0000, mailman3--- via Mailman-users wrote: > Debian bookworm Archival works here. Here is my simplified auto-deployement script (some might not be useful to you, I am using a local Postfix): PS: replace services_install by apt-get install djangoauth=@@@REPLACE # this is a bash array: server, user, pw psqlauth=@@@REPLACE services_install postfix (while read line do case $line in *=*) postconf -e "$line";; *) echo "TOSSING: $line" >&2;; esac done) <<EOF myhostname = $lists mydestination = $lists mynetworks = 127.0.0.0/8 inet_protocols = ipv4 inet_interfaces = all transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains relayhost = @@@REPLACE EOF cat >> /etc/aliases <<EOF postorius: root www-data: root root: ${djangoauth[1]} EOF newaliases services_install dbconfig-pgsql cat > /etc/dbconfig-common/mailman3.conf <<EOF dbc_install='true' dbc_upgrade='true' dbc_remove='false' dbc_dbtype='pgsql' dbc_dbuser='${psqlauth[1]}' dbc_dbpass='${psqlauth[2]}' dbc_dbserver='${psqlauth[0]}' dbc_dbname='mailman' dbc_dbadmin='postgres' EOF sed < /etc/dbconfig-common/mailman3.conf \ > /etc/dbconfig-common/mailman3-web.conf \ "s/^dbc_dbname=.*/dbc_dbname='mailmanweb'/" chmod 600 /etc/dbconfig-common/mailman3.conf \ /etc/dbconfig-common/mailman3-web.conf services_install mailman3-full mailman3-web sed --in-place "s/^site_owner: .*/site_owner: ${djangoauth[1]}/" \ /etc/mailman3/mailman.cfg # archiving mails from mailing-lists automatically cat >> /etc/mailman3/mailman.cfg <<'EOF' [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg [styles] default: private-default EOF # enable archiver key sed -i "s%^api_key:.*%api_key: $(egrep MAILMAN_ARCHIVER_KEY /etc/mailman3/mailman-web.py | awk '{print $NF;}' | sed "s/'//g")%" /etc/mailman3/mailman-hyperkitty.cfg # work-around: SQLAlchemy no longer supports "postgres" sed --in-place "s%^url: postgres://%url: postgresql://%" \ /etc/mailman3/mailman.cfg sed --in-place "s/.*'Mailman Suite Admin', 'root@localhost').*/('Mailman Suite Admin', '${djangoauth[1]}'),/;s/^EMAILNAME\s*=.*/EMAILNAME = '$lists'/;/django_mailman3.lib.auth.fedora/d" /etc/mailman3/mailman-web.py # aliases mailman <-> postfix mkdir -p /var/lib/mailman3/data chown list:list /var/lib/mailman3/data for i in postfix_lmtp postfix_lmtp postfix_domains do touch /var/lib/mailman3/data/$i postmap /var/lib/mailman3/data/$i done chown list:list /var/lib/mailman3/data/postfix_* # work-around for django_q # (does not seem to work, and DEFAULT_AUTO_FIELD should be also # configured to django.db.models.BigAutoField) dpkg-divert --rename /usr/lib/python3/dist-packages/django_q/conf.py sed < /usr/lib/python3/dist-packages/django_q/conf.py.distrib \ > /usr/lib/python3/dist-packages/django_q/conf.py \ 's%TIMEOUT = conf.get("timeout", None)%TIMEOUT = conf.get("timeout", 59)%' pkill -e -2 --full 'python3 manage.py qcluster' || true # fix example.com PGPASSWORD=${psqlauth[2]} psql -h ds-services-psql -U ${psqlauth[1]} mailmanweb -c "UPDATE django_site SET domain = '$lists', name = '$lists' WHERE id = 1" # workaround required? #chgrp list /var/lib/mailman3/locks/ #chmod g+rwx /var/lib/mailman3/locks/ chgrp list /var/log/mailman3/*.log # https://docs.djangoproject.com/en/3.0/ref/django-admin/#django-admin-create… env DJANGO_SUPERUSER_PASSWORD=${djangoauth[3]} \ DJANGO_SUPERUSER_USERNAME=${djangoauth[2]} \ DJANGO_SUPERUSER_EMAIL=${djangoauth[1]} \ mailman-web createsuperuser --noinput \ || echo "django super user already exists in DB, ignored" # then I migrate the lists

2 years

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

by Odhiambo Washington

On Sun, 26 Jul 2020 at 00:17, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > > > Finally, I have adapted your init script to get some rudimentary one > that I > > could use on FreeBSD. > > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > > have "live" MLs on this server, using mailman-2.1.34. > > I am not sure if they can co-exist. I suppose they could, but what might > be > > the security implication, if any?? > > I manage more than one server that supports both Mailman 2.1 and Mailman > 3 running as user `mailman`. I'm not aware of any security issues. > > > > This is what the init script looks like (rudimentary!!): > > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > > ### BEGIN INIT INFO > > # Provides: GNU Mailman > > # Short-Description: Mailman3 Service > > # Description: service control for Mailman3 > > ### END INIT INFO > > > > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > > DESC="GNU Mailman service" > > DAEMON=/opt/mailman/mm/bin/mailman > > NAME=mailman > > USER=mailman3 > > GROUP=mailman3 > > > > # Needed by click > > export LANG=en_US.UTF-8 > > > > # Exit if the package is not installed > > [ -x "$DAEMON" ] || exit 0 > > > > # Load the VERBOSE setting and other rcS variables > > #. /lib/init/vars.sh > > > > # Define LSB log_* functions. > > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > > # and status_of_proc is working. > > #. /lib/lsb/init-functions > > > > case "$1" in > > start) > > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > > # use --force to remove a stale lock. > > /usr/local/bin/sudo -u $USER $DAEMON start --force > > T don't recommend using --force in init scripts. It *shouldn't* matter > because even with --force the master shouldn't break the lock if the pip > that set it still exists, but I prefer not to use it. > > > > ;; > > stop) > > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > > /usr/local/bin/sudo -u $USER $DAEMON stop > > ;; > > status) > > /usr/local/bin/sudo -u $USER $DAEMON status > > ;; > > reopen) > > /usr/local/bin/sudo -u $USER $DAEMON reopen > > ;; > > restart) > > log_daemon_msg "Restarting $DESC" "$NAME" > > /usr/local/bin/sudo -u $USER $DAEMON restart > > ;; > > *) > > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > > exit 3 > > ;; > > esac > > > > It does start mailman3 for sure, but also complains after a few seconds > > with the message: > > > > (venv) [root@gw /usr/local/etc/rc.d]# > > > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > > DeprecatedWarning: Call to deprecated function __init__(...). API class > may > > be removed in a future release, use falcon.App instead.* > > * **kws)* > > > Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 > and 3.0.0a1 and I don't see this warning, but it is only a deprecation > warning. It doesn't mean it won't work. > > > > But: > > > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman > ... > > It seems Mailman core and the rest runner and its workers are all running. > > > > > > Assuming that I am using mod_wsgi with Apache, and that I have configured > > apache right using > > > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > .. > > should I be able to access the MM3 web UI?? > > Yes, I think so. > > > > At that point, I am feeling somewhat confused as to what to try next. > > > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > > Jul 25 22:53:16 2020 (40670) Master started > > Jul 25 22:53:18 2020 (42036) bounces runner started. > > Jul 25 22:53:18 2020 (45205) out runner started. > > Jul 25 22:53:19 2020 (41191) archive runner started. > > Jul 25 22:53:19 2020 (46670) retry runner started. > > Jul 25 22:53:19 2020 (44567) nntp runner started. > > Jul 25 22:53:19 2020 (43069) in runner started. > > Jul 25 22:53:19 2020 (46960) virgin runner started. > > Jul 25 22:53:20 2020 (45720) pipeline runner started. > > Jul 25 22:53:20 2020 (47326) digest runner started. > > Jul 25 22:53:20 2020 (43755) lmtp runner started. > > Jul 25 22:53:20 2020 (45922) rest runner started. > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > > http://127.0.0.1:8001 (45922) > > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > > Jul 25 22:53:21 2020 (42743) command runner started. > > > The above is all fine, but it is just Mailman core. > > > > How do I access the web UI for MM3 now? > > > The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which > is at > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > >. > Do you have that? > Yes, I have that file. > If you installed the Apache config literally, the location for Mailman 3 > is defined by > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > and the URL would be http(s)://your.server/mm3 - have you tried that? > > There is still some confusion on my part about the directives in the file so allow me to seek some clarifications. The following are the contents of a file I have created and placed in my Apache Includes/ directory. I was hoping that with it, I can now access http://lists.my.server/mm3 and get the UI. <CUT> # Global section 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 WSGIRestrictSignal Off <VirtualHost *:80> ServerName lists.my.server ServerAdmin odhiambo(a)gmail.com # (I'm not sure that WSGIRestrictSignal Off is required, but it was in the # provided example so I kept it. I also made changes to WSGIDaemonProcess # based on my own mod_wsgi experience elsewhere.) ErrorLog /var/log/myserver-error.log LogLevel debug # This goes in the VirtualHost block for the domain. # Mailman 3 stuff Alias /static "/var/spool/mailman-web/static" *<----- Where is this directory supposed to be and what/who creates it and with what permissions?* <Directory "/var/spool/mailman-web/static"> Require all granted </Directory> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py <Directory "/opt/mailman/mm/"> <Files wsgi.py> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> </CUT-HERE> I end up with an "Internal server error" and from the error log I see: [Sun Jul 26 12:04:43.444127 2020] [wsgi:info] [pid 6444] [remote 197.232.81.246:53383] mod_wsgi (pid=6444, process='mailman-web', application='lists.my.server|/mm3'): Loading Python script file '/opt/mailman/mm/wsgi.py'. [Sun Jul 26 12:04:44.091922 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] mod_wsgi (pid=6444): Failed to exec Python script file '/opt/mailman/mm/wsgi.py'. [Sun Jul 26 12:04:44.092006 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] mod_wsgi (pid=6444): Exception occurred processing WSGI script '/opt/mailman/mm/wsgi.py'. [Sun Jul 26 12:04:44.092940 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] Traceback (most recent call last): [Sun Jul 26 12:04:44.093019 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "/opt/mailman/mm/wsgi.py", line 38, in <module> [Sun Jul 26 12:04:44.093029 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] application = get_wsgi_application() [Sun Jul 26 12:04:44.093048 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] 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 [Sun Jul 26 12:04:44.093057 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] django.setup(set_prefix=False) [Sun Jul 26 12:04:44.093071 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/__init__.py", line 19, in setup [Sun Jul 26 12:04:44.093090 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Sun Jul 26 12:04:44.093108 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 76, in __getattr__ [Sun Jul 26 12:04:44.093117 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] self._setup(name) [Sun Jul 26 12:04:44.093130 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 63, in _setup [Sun Jul 26 12:04:44.093138 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] self._wrapped = Settings(settings_module) [Sun Jul 26 12:04:44.093158 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 142, in __init__ [Sun Jul 26 12:04:44.093166 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] mod = importlib.import_module(self.SETTINGS_MODULE) [Sun Jul 26 12:04:44.093179 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module [Sun Jul 26 12:04:44.093187 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] return _bootstrap._gcd_import(name[level:], package, level) [Sun Jul 26 12:04:44.093210 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "<frozen importlib._bootstrap>", line 994, in _gcd_import [Sun Jul 26 12:04:44.093224 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "<frozen importlib._bootstrap>", line 971, in _find_and_load [Sun Jul 26 12:04:44.093239 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked [Sun Jul 26 12:04:44.093265 2020] [wsgi:error] [pid 6444] [remote 197.232.81.246:53383] ModuleNotFoundError: No module named 'settings' -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 2 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/22/23 14:48, ceo(a)sartrack.nz wrote: > Thanks; > There has never been a 'Mailman' user. I do have a www-data user (all Apache2 data' and there is a 'list' user. So what I refer to as the Mailman user (a generic term) is `list` in your case. > I may have run the import fuction as root, but I then used chown() to set the directory tree /var/lib/mailman3/* to user 'list'. OK > So I upgraded Debian 10 to Debian 11. > This also upgraded Apache2 I assume, but I kept the original (single) config file. > > I then installed the whole Mailman3 package with 'apt'. I may also have installed additional missing bits afterwards, as I think it was not complete. I initially tried to use MariaDB but the installation failed completly because it never asked for the MariaDB root password, and as a result of that everyting else failed too. > Then I un-installed 5 times, and then I finally went for the 'default' database system. > > I then edited the file with the recommended settings for Mailman3: > 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> > > So clearly Apache2 manages to access the data supplied by Postorius because it sees the lists (at least the empty ones). > -What user should the whole system running under: 'list'? of 'www-data'? > - Is there anything else I should tell Apache2? All the web based stuff is a Django application. Django is run by uWSGI which probably runs as www-data, but Django only accesses hyperkitty, postorius and django-mailman3 and other Django related tables in the database. It doesn't need access to file system files other than things like wsgi.py, urls.py, settings.py and settings_local.py and only read access to these. All the mailman3 file system stuff has to be read/write/searchable by `list`. > Now I tried to use "django-admin createsuperuser". This also fails because of this error: > ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) > And I cannot find where this 'force_text' is called from. It must be removed as it is too old. It seems your Django installation is broken. Do cd /usr/local/lib/python3.9/dist-packages/django grep -r force_text to find where force_text is called, or maybe add def force_text(s, encoding='utf-8', strings_only=False, errors='strict'): return force_str(s, encoding, strings_only, errors) to /usr/local/lib/python3.9/dist-packages/django/utils/encoding.py -- 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: Broken web UI after upgrade

by Guillermo Hernandez (Oldno7)

El 14/12/22 a las 18:16, Odhiambo Washington escribió: > On Wed, Dec 14, 2022 at 8:02 PM Stephen J. Turnbull < > stephenjturnbull(a)gmail.com> wrote: > >> Odhiambo Washington writes: >> >> > The site is public, so I can share the link: >> https://list.rc.org/archives/ >> >> The CSS is not working. Two possibilities to try first: >> 1. (more likely) You didn't run the command that compiles the CSS. >> (probably) mailman-web compress >> 2. (much less likely) The CSS got replaced in the upgrade and the >> ownership changed because you were working as root, and the server >> process can't access the files. >> 3. other possibilities: the SASS compiler (usually sassc, possibly sass) >> >> > 1. The post-update script runs everything required. For the avoidance of > doubt, here it is: > <CUT> > #!/bin/bash > > set -e > > BINDIR="/opt/mailman/mm/bin" > CONFDIR="/opt/mailman/mm" > SETTINGS="settings" > DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" > STATIC_DIR="$CONFDIR/static" > DEBUG="False" > > set -x > > if [ "$DEBUG" == "False" ]; then > mkdir -p "$STATIC_DIR" || : > "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput --verbosity 0 > "$DJANGO_CONTROL_SCRIPT" compress Odhiambo, I had problems in the compress process in the last updates. I would make sure the process is running ok. I had to disable the off line compression for this matter. > "$DJANGO_CONTROL_SCRIPT" compilemessages > fi > > syncdb_cmd="$DJANGO_CONTROL_SCRIPT migrate" > if [[ ! -t 1 ]]; then > # stdout is not a terminal > syncdb_cmd="$syncdb_cmd --noinput" > fi > $syncdb_cmd > echo 'Do you want to rebuild the search index? This takes a long time.' > echo 'Type "Yes" to continue; anything else to quit.' > read -p "> " response > if [ "x$response" != "xYes" ] ; then exit; fi > "$DJANGO_CONTROL_SCRIPT" update_index > </CUT> > > The script is run within the venv. > > 2. That isn't possible. Why? Because when I do 'su -mailman' it > automatically activates the venv via a .bashrc. > I have run this: > find /opt/mailman -type f -name "*.css" -exec ls -al {} \; > > And all files are owned by mailman.mailman. > > 3. I have the following in settings_local.py: > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > COMPRESS_OFFLINE = True > COMPRESS_ENABLED = True > > And: > root@list:/home/wash# su - mailman > (venv) mailman@list:~$ which sass > /usr/bin/sass > (venv) mailman@list:~$ `which sass` --version > Ruby Sass 3.7.4 > (venv) mailman@list:~$ > > Anything else that might be the issue? > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-03 09:44, mhazan(a)mandint.org a écrit : > Le 2022-05-02 17:32, Mark Sapiro a écrit : >> On 5/2/22 06:39, Michael Hazan wrote: >>> Hello, >>> >>> When creating a list via postorius, i can see 3 style appear >>> (announce, discussion, private). Is it possible to either create a >>> new style and add it to that list or modify one of those style ? >> >> >> See this thread >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> > > Thanks i will look into setting up that plugin, hopefully an easier > way to do that can make it's way to the default install. working on that plugin, i have found where to inserts the various setting, however it's not clear what types and possibles value are excepted for each ? ie "advertised" is bool True/false, but what about "default_member_action" ? i've tried hold 'hold' "hold" all throw error when trying to apply the style. i cannot find the types in the documentation and all the other non bool settings. >>> Also, coming from mailman2, you could directly set the members post >>> moderation action when subscribing, now you can only do it via the >>> user menu, is there a way to automate this in mm3 ? >> >> >> I don't understand what you mean here. In MM 2.1 a member had only one >> setting - moderated yes or no and if moderated there was a list >> setting for the moderation action. There was also a list setting for >> whether new members were moderated by default. How were you setting >> the new member's moderation when subscribing? >> >> You are correct that when subscribing a new member, the member gets >> the default action for members and different action has to be set in a >> separate operation. I don't think this is significantly different from >> MM 2.1. Also, can you describe what you mean by "automate this". > > in MM2.1, if you set the list to moderated and default action to hold > posting, you can set a some member to be un-moderated (mod bit off) to > automatically allow their posting. In the web interface of MM2.1 there > is a checkbox with moderated bit on/off on the member list itself, in > the postorius interface for MM3 you have to open each members settings > page to access that. For automation, as list owner, upon registering a > member (via mass subscription) the possibility to change that ? also > the me too/dupe setting for example. > > Thanks > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

[MM3-users] Re: Reg Archive Inactive Status

by Nirmal J

mailman.log :- File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 388, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1050, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 414, in connect self.sock = ssl_wrap_socket( ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl( ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket return self.sslsocket_class._create( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 1108, in _create self.do_handshake() File "/usr/lib/python3.11/ssl.py", line 1379, in do_handshake self._sslobj.do_handshake() ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/requests/adapters.py", line 489, in send resp = conn.urlopen( ^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 789, in urlopen retries = retries.increment( ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 594, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)'))) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.11/dist-packages/mailman_hyperkitty-1.2.0-py3.11.egg/mailman_hyperkitty/__init__.py", line 151, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/mailman_hyperkitty-1.2.0-py3.11.egg/mailman_hyperkitty/__init__.py", line 195, in _send_message result = requests.post( ^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/api.py", line 115, in post return request("post", url, data=data, json=json, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/api.py", line 59, in request return session.request(method=method, url=url, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/sessions.py", line 587, in request resp = self.send(prep, **send_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/sessions.py", line 701, in send r = adapter.send(request, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/adapters.py", line 563, in send raise SSLError(e, request=request) requests.exceptions.SSLError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)'))) -----Original Message----- From: Mark <mark(a)msapiro.net> To: Nirmal <nirmal(a)iitm.ac.in>; MM3 <mailman-users(a)mailman3.org> Date: Friday, 26 September 2025 9:56 PM IST Subject: Re: [MM3-users] Re: Reg Archive Inactive Status On 9/25/25 22:29, Nirmal J wrote: > I have ensured that the IP Address of list1.iitm.ac.in is in the Mailman_Archiver_From List in settings. But still not working. Please help. You may also need variuos localhost IPs such as '127.0.0.1', '::1', '::ffff:127.0.0.1' What archiving failures do you now see in mailman.log? Do not post the entire log, just the relevant message(s). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Login confusion

by Stephen J. Turnbull

Markus Grandpré writes: > Dear Steve, dear list > > > That's not true on the systems I've worked with most recently -- those > > will be recognized as duplicate addresses (...) > > You are right. I am sorry for this confusion. Please let me correct my > initial posting to this list from yesterday, saying: > > >> (...) <markus.grandpre(a)uni-konstanz.de> and > <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate > identities. > > That is not the case. Meanwhile I discovered an error with logging into > Postorius when an account is associated with two semantically identical > email addresses that differ in their formatting, e.g., Yes. Apparently this is a problem of a policy difference between Mailman 3 and the Django allauth package, as Bernhard Lichtinger pointed out in <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> allauth takes the point of view that the localpart of an email address is the "property" of the provider of the mailbox, and therefore should be taken verbatim by third parties. Mailman takes the more practical point of view that, in practice, almost all providers treat localparts as case insensitive. (Some -- Gmail, grrrrr -- go farther and ignore whole characters such as periods.) The problem is that users treat email addresses as case insensitive, and aren't very careful about using the same case every time. That's why I think the Mailman approach is appropriate. > To resolve the issue, the only solution I found was to manually delete > the second email address from the database: That will work in the short run, but I'm not sure that's a long-term solution. It's not clear to me that allauth won't do the same thing again. > Could I have achieved the same deletion using the REST interface? I don't know. I would think not. I suspect Mailman code can only find the lowercase version. Mark has a script that looks for such duplicates using psycopg, not mailmanclient, so it accesses the database via the PostgreSQL API, not Mailman's REST API. It deletes any duplicate that is not all-lowercase: https://github.com/pennersr/django-allauth/issues/3019#issuecomment-2440231… > I am not entirely sure how the duplicate email address came into the > system. allauth did it. It's explained in the issue where Mark's script is attached. It's not very easy to follow the discussion, though. And there's something weird going on because in your stack trace, it appears that allauth is doing a case insensitive database search. So I would just grab the script and run it, in case there are other users with extra addresses that compare equal when comparison is case insensitive. > I apologize again for the incorrect information in my initial message to > this list. No need to apologize. It's extremely complicated. Of course we're happy if you look around and figure out most of it for us! Steve

1 year, 7 months

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

by John Covici

On Sat, 13 Mar 2021 05:42:53 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > On 13/3/21 9:44, John Covici wrote: > > 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 mean the part when you activate the virtualenv (Virtualenv > setup & activate virtualenv) in > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > The servers in which I was migrating from mailman2 were jailed > servers and I didn't want to add more virtualization layers (and > I read some articles documenting problems using virtualenv in > FreeBSD) so, I prefered to install all of it system wide as it > was before with mailman2. > > > > > I will certainly look at your thread. > > Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version? -- 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

5 years, 6 months

[MM3-users] Re: help with startup scripts

by Piet Barber

this mailman3.service file seems to work better than the one on the mailman website: ( https://docs.list.org/en/latest/install/virtualenv.html#setup-virtualenv ) Thanks to "oneshot" ! # /etc/systemd/system/mailman3.service[Unit]Description=GNU Mailing List Manager (Mailman Core, venv)After=network.target postgresql.service [Service]Type=oneshotUser=mailmanGroup=mailmanEnvironment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg"# Optional but nice if PATH matters elsewhere:# Environment=PATH=/opt/mailman/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # Start/stop via Mailman's own supervisor. --force avoids stale-lock wedging.ExecStart=/opt/mailman/venv/bin/mailman start --forceExecStop=/opt/mailman/venv/bin/mailman stop # Tell systemd we consider the service 'up' after ExecStart exits.RemainAfterExit=yes # Reasonable timeouts so systemd doesn't kill slow boots/shutdownsTimeoutStartSec=60TimeoutStopSec=60 [Install]WantedBy=multi-user.target On Thu, Aug 14, 2025 at 7:58 PM Piet Barber <pb(a)pietbarber.com> wrote: > > > On Thu, Aug 14, 2025 at 3:03 AM Stephen J. Turnbull <steve(a)turnbull.jp> > wrote: > >> Piet Barber via Mailman-users writes: >> >> > However, when I follow the systemctl startup scripts as per the >> > instructions at the URL above, it get stuck in the startup >> > ... forever >> >> What makes you think it's stuck? Have you actually tried to use it? >> If not, it's probably just that systemd messages were not written to >> be understood by ordinary mortals. >> > > root@arcus:/etc/systemd/system# systemctl start mailman3 > (extreeeeemelllyyy loooooong wait of nothing ensues) > > Eventually I get: > > > root@arcus:/etc/systemd/system# time systemctl start mailman3 *Job for mailman3.service failed because a timeout was exceeded.**See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details.* > > real 0m19.442s > user 0m0.002s > sys 0m0.012s > root@arcus:/etc/systemd/system# > > the journalctl output is as follows: > > > Aug 14 23:48:24 arcus mailman[5624]: Starting Mailman's master runner > Aug 14 23:48:24 arcus mailman[5624]: Generating MTA alias maps > Aug 14 23:48:24 arcus systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: No such file or direct> > Aug 14 23:48:29 arcus mailman[5645]: /opt/mailman/venv/lib/python3.12/site-packages/mailman/rest/wsgiapp.py:185: DeprecatedWarning: The RequestOp> > Aug 14 23:48:29 arcus mailman[5645]: self.req_options.auto_parse_form_urlencoded = True > Aug 14 23:49:53 arcus systemd[1]: *mailman3.service: start operation timed out. Terminating.* > Aug 14 23:49:55 arcus systemd[1]: *mailman3.service: Failed with result 'timeout'.*░░ Subject: Unit failed░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ The unit mailman3.service has entered the 'failed' state with result 'timeout'. > Aug 14 23:49:55 arcus systemd[1]: *Failed to start mailman3.service - GNU Mailing List Manager.*░░ Subject: A start job for unit mailman3.service has failed░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ A start job for unit mailman3.service has finished with a failure.░░ ░░ The job identifier is 1153 and the job result is failed. > Aug 14 23:49:55 arcus systemd[1]: mailman3.service: Consumed 13.298s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ The unit mailman3.service completed and consumed the indicated resources. > Aug 14 23:50:10 arcus systemd[1]: mailman3.service: Scheduled restart job, restart counter is at 3.░░ Subject: Automatic restarting of a unit has been scheduled░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ Automatic restarting of the unit mailman3.service has been scheduled, as the result for░░ the configured Restart= setting for the unit. > Aug 14 23:50:10 arcus systemd[1]: Starting mailman3.service - GNU Mailing List Manager...░░ Subject: A start job for unit mailman3.service has begun execution░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ A start job for unit mailman3.service has begun execution.░░ ░░ The job identifier is 1525. > > > The system works fine when i su to mailman and run the startup script in > /opt. > The system doesn't work when I use the systemctl command. Apparently it's > waiting for something to happen before the system creates a pidfile in > /opt/mailman/m/var/master.pid > > Do you have mailman3 starting from a startup script? What does your > /etc/systemd/system/mailman3.service file look like? Mine looks just like > the one on the mailman configuration site. I have to be doing something > stupid for it not to work. I just can't figure out what stupid thing I'm > doing wrong. > > Also, removing the word "Forking" from the systemctl configuration file > has no effect, except that it takes longer for the mailman3 startup script > to fail. > > > > root@arcus:/etc/systemd/system# time systemctl start mailman3 *Job for mailman3.service failed because a timeout was exceeded.**See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details.* > > real 1m23.491s > user 0m0.006s > sys 0m0.004s > root@arcus:/etc/systemd/system# > > I'm about to jump out the window on this one. I've been stuck on this for > four weeks. > > Here's my mailman3.service file: > > > [Unit]Description=GNU Mailing List ManagerAfter=syslog.target network.target postgresql.service > [Service]#Type=forking#PIDFile=/opt/mailman/mm/var/master.pidUser=mailmanGroup=mailmanEnvironment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg"ExecStart=/opt/mailman/venv/bin/mailman startExecReload=/opt/mailman/venv/bin/mailman restartExecStop=/opt/mailman/venv/bin/mailman stopRestart=on-failureRestartSec=15 > > [Install]WantedBy=multi-user.target > > > > -- > Piet Barber > http://www.pietbarber.com/ > http://blog.pietbarber.com/ > -- Piet Barber http://www.pietbarber.com/ http://blog.pietbarber.com/

1 year, 1 month

[MM3-users] Re: Deactivate list without deleting it?

by Colin Watson

On Wed, Jan 17, 2018 at 04:34:48PM +0900, Stephen J. Turnbull wrote: > Colin Watson writes: > > I possibly should have explained our situation in a little more > > detail. > > Well, I was pretty clear on your requirements, it turns out. I don't, > and I believe I'm in agreement with the rest of the team here, need to > know why you want something (at least not at this "let's see if we can > hash out the requirements and the design a bit" stage). After all, > even if we end up WONTFIXing it, it's open source and we're happy to > talk about how you might do something even if we won't do it for you! I appreciate that approach. At the same time, I also asked because I suspected I didn't quite understand the design principles involved. Thanks to both you and Barry for clarifying the intent of IArchiver; I'll drop that idea. > > Postorius wouldn't come into it in our case > > That's an interesting detail. Thing is, at present Postorius *is* the > "control panel" for the whole suite (all the best bands are run by > their bassists, you know), so we would bring it up if you left it out. I'm not ruling out using it in future, but right now I think we'd prefer to stick with the approach of having the "control panel" integrated tightly into LP. > However, if you don't want to use Postorius, I think the > mailman-client functionality will make it strightforward to implement > your UI within Launchpad, and it now includes a nicer CLI so if you > prefer to implement core and Hyperkitty functionality before the > Launchpad side, mailman-client will allow you to test core features at > that stage. Indeed. And I'd managed to miss the existence of mailmanclient, so thanks for bringing that up. > > I'd been thinking more of a new enum in HyperKitty for the visibility > > state, since it does seem like quite an archiver-specific thing. > > Well, there is an enum in core for it already. I'm not sure how that > works currently (specifically, how you go about telling Hyperkitty if > that changes). Keeping that in sync is an issue (at least for us), > since Postorius can query it, IIRC. I just looked into what HK does, and I notice that it syncs the archive policy from Core as part of a regular update job. So I think the answer is that we just use that: perhaps set the ArchivePolicy to private and arrange that nobody has the ability to view it other than maybe list owners, or possibly add a new item to ArchivePolicy that's something like "deactivated" or "hidden". At any rate that looks a lot more tractable since most of the mechanism already exists. Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

8 years, 7 months

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

by Abhilash Raj

> On Mar 22, 2021, at 7:56 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Abhilash Raj writes: > >> Typo :( Page in Postorius is what I meant to say. > > :D No problemo, mon, I just did it too -> > >> Is that necessarily required? Every user in Django has a corresponding >> user in Core, but the converse isn’t true and I am not sure if that is even >> required. > > I meant "accessed from Postorius or HyperKitty." :-) > >> You will be able to see: >> - Does the user have a Django account? >> - All Subscriptions for the User >> - All addresses of the User >> >> You will be able to perform following actions: >> - Add or remove a user’s address >> - Verify or un-verify an address >> - Set any address as primary for the user >> - Update display name of the user >> - Update address on any of the subscriptions > > I don't think we *need* a Django account for what I'm thinking of. I > do think that creating the account on User access from Postorius might > make the implementation logic simpler. > >> What I am on fence about: >> - Provide a full blown preferences menu to the admin for that user. This >> will also make the UI extremely complex to see and implement. > > Wait to decide on that until I have a mockup or maybe a full MR. > >> But, when you have an account in Django with a different email >> (email2) and a different Mailman user (user2) and you add a second >> email (email1) to your account and are able to prove ownership by >> verifying the address, Django will ask Core to add that second address >> (email1) to your Mailman user (user2) and absorb “user1”. This >> process is already implemented. > > Good. > >> However, if two Django accounts are created for “user1” and “user2” >> then situation becomes more tricky and currently we don’t have a >> way to resolve that short of delete one of the accounts and add the >> addresses to other account. > > Delete "that" and add its attributes to "this" is what I had in mind. We could automate the absorb other account and copy all settings and subscriptions over in a user based workflow. I don’t see a lot of unknowns in implementing that. You have to manually do it today, and deleting account will delete subscriptions so when you add them to your other account you have to resubscribe. So, the path could really use some changes. I think I have a ticket open in P to allow deleting P account but not delete the Mailman User and subscriptions, which would make this manual process much better. -- thanks, Abhilash Raj (maxking)

5 years, 6 months

[MM3-users] Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by John Covici

I am interested in your docr instructions. I don't use postfix, instead I use sendmail, but I think I can figure that out, but I have been having lots of problems installing without docr, and I do have apache, so this would be great. Send off list if you think that would not be of general use. On Wed, 27 Oct 2021 19:51:17 -0400, Shawn Heisey wrote: > > On 10/26/2021 11:43 AM, Michael Heseltine wrote: > > after upgrading an older server to Ubuntu 20.04, I tried to first upgrade my old mailman 2 installation to mailman 3. I've been on it for three weeks now, but unable to get anything working. I have long forgone the idea of upgrading and thus purged everything from mailman2 on my machine, and installed and removed mailman3 several times to no avail. > > I just ran into a lot of trouble myself getting the Ubuntu > packages working. And I got the same advice you did from this > mailing list -- don't try to install it that way. > > My first attempt at installing it without using packages was the > virtualenv method. After beating my head against that for a few > hours and not making any progress at all, I gave up. > > I now have the docker install fully functional, and imported my > list configurations from data I saved from an ancient mailman2 > install. It was giving me grief too when I first installed it, > but I managed to work through each of the problems. One of the > issues was a basic networking problem -- mailman in the container > wasn't able to talk to Postfix on the host. Rebooting the host > cleared that up. Side note: There are no details in the docker > instructions about how to upgrade the containers to newer > versions. Easy upgrades was a big reason why I wanted to use the > Ubuntu packages. Upgrading other packages has always been pretty > straightforward. > > I'm using Apache, not nginx. It was already installed, and I > know more about configuring it than nginx. It wasn't too > difficult to set up Apache to proxy over to uwsgi running in the > web container. I had to work out the config myself ... the > docker instructions only have a config example for nginx. > > Email isn't very interactive, but works. You can find me on the > IRC channel for the next few days if you want something faster. > If you want to try the docker method, I can try to help. > > Thanks, > Shawn > _______________________________________________ > 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/ -- 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, 11 months

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

by Mark Sapiro

On 4/8/25 18:45, MegaBrutal via Mailman-users wrote: > > User-profile shows my GMail address as primary and my own-domain address as > secondary. The third address is not present, because I actually wanted to > get rid of it, and it seems I succeeded in that. This is your Django user which has the two addresses associated with it. > Mailman3/users shows me with the address I wanted to get rid of. If I click > Manage, I see all 3 addresses, with (for some reason) only the GMail one > being verified (strange because I'm sure I verified the other as well). And > here's something interesting: it shows me as a member with my GMail address > under subscriptions, but shows me with my megabrutal.com domain under > ownerships. These are your Mailman user and its addresses. They are not the same as your Django user and its addresses. I don't think you can unlink an address from your Mailman user in Postorius/HyperKitty. You can do that in `mailman shell`. ``` $ 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() ``` It may not be clear from the above, but the idea is that you are deleting the address you don't want from usr.addresses, but before that if the one you don't want is the preferred_address, you need to set the preferred address to one of the others. Also, `del usr.addresses[n]` deletes the address record, but it is still in the addresses list, thus the `usr.addresses.remove(n)`. This is untested, so before committing you may want to verify that `usr.addresses` now lists just the two addresses you want > This might be the cause? Maybe HyperKitty wants to use my owner identity, > which is not subscribed? Btw, is the owner not automatically considered as > someone who can post to the list, they also need to be subscribed? An owner is not a list member and has no special posting privileges. If only members are allowed to post, the owner address must also be a member to be allowed to post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

Hi Mark, Thank you for your reply. I admit that I don't know Mailman 3 as well as I knew Mailman 2. And the 2 -> 3 upgrade was handled by someone else, who has since left the org. As near as I have been able to discern, Mailman 3 is running on a docker host with four containers running, with mailman, postfix, nginx and django-uswgi in separate containers. % sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1b4262f81b98 mailman-nginx:1.21.3 "/docker-entrypoint.…" 3 years ago Up 3 weeks 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp mailman-nginx a5e4fa75ccb3 mailman-postfix:3.5.10-r0 "postfix start-fg" 4 years ago Up 2 weeks 0.0.0.0:25->25/tcp mailman-postfix 7a358c807714 mailman-django-uwsgi:2.0.19.1 "uwsgi --ini uwsgi.i…" 4 years ago Up 3 weeks 8000/tcp mailman-django-uwsgi 9a917897da10 mailman-core:3.3.1 "master" 4 years ago Up 3 weeks 24/tcp, 8001/tcp mailman-core When I look at main.cf inside mailman-postfix: transport_maps = hash:/opt/mailman/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/var/data/postfix_domains virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap-exceptions, hash:/opt/mailman/var/data/postfix_vmap When I look at the domains in mailman-core, I see: >>> show_domains() <Domain fhcrc.org> <Domain fredhutch.org> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> <Domain lists.hanc.info, , alias: > - owner: cit-sys-engineering(a)fredhutch.org >>> When I look at /opt/mailman/var/data/postfix_domains inside the postfix container, that seems to match: fredhutch.org fredhutch.org lists.fredhutch.org lists.fhcrc.org lists.hanc.info lists.hanc.info Now, when I look at the entries for a test list on lists.fhcrc.org, postfix_vmap looks like: pattest(a)lists.fhcrc.org pattest(a)lists.fredhutch.org pattest-bounces(a)lists.fhcrc.org pattest-bounces(a)lists.fredhutch.org pattest-confirm(a)lists.fhcrc.org pattest-confirm(a)lists.fredhutch.org pattest-join(a)lists.fhcrc.org pattest-join(a)lists.fredhutch.org pattest-leave(a)lists.fhcrc.org pattest-leave(a)lists.fredhutch.org pattest-owner(a)lists.fhcrc.org pattest-owner(a)lists.fredhutch.org pattest-request(a)lists.fhcrc.org pattest-request(a)lists.fredhutch.org pattest-subscribe(a)lists.fhcrc.org pattest-subscribe(a)lists.fredhutch.org pattest-unsubscribe(a)lists.fhcrc.org pattest-unsubscribe(a)lists.fredhutch.org and postfix_lmtp looks like: pattest(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-bounces(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-confirm(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-join(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-leave(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-owner(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-request(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-subscribe(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-unsubscribe(a)lists.fredhutch.org lmtp:[mailman-core]:24 But for a test list on lists.hanc.info (the lists that I want to modify the bounce processing for), there is nothing in postfix_vmap, but there are entries in postfix_lmtp: phtest(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-bounces(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-confirm(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-join(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-leave(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-owner(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-request(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-subscribe(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-unsubscribe(a)lists.hanc.info lmtp:[mailman-core]:24 And in postfix_vmap-exceptions, I added: phtest-bounces(a)lists.hanc.info lmtp:[mailman-core]:24, user(a)gmail.com I tried the above with and without a comma, and moving the email address before the lmtp entry as well. Everything else seems to be working — there are over 40k lmtp: entries in postfix_lmtp, and messages are being delivered. I sort of assumed that the lmtp:[mailman-core]:24 thing was a result of all this being dockerized.... Suggestions appreciated. Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, June 26, 2025 09:33 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies 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 6/25/25 10:53, Hirayama, Pat wrote: > Thanks, Mark. > > I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. > > The current postfix_vmap has entries like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 This looks very strange. It should be something like ``` list-bounces(a)lists.domain.info list-bounces(a)alias.domain ``` where alias.domain is the configured alias domain for the mail host lists.domain.info. > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. > > If I do: > > list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 > > Then it goes to the gmail address, and no bounce processing happens. The issue here is the value `lmtp:[mailman-core]:24` is completely wrong. It should be an email address with a syntactically valid domain name. The domain name isn't a real domain. It is only a name exposed to Postorius in the postfix_vmap and postfix_lmtp files. What do you have configured for the alias domain for the lists.domain.info domain? See https://urldefense.com/v3/__https://docs.mailman3.org/projects/mailman/en/l… If you have this properly configured, adding user(a)gmail.com in either order in postfix_vmap should work. -- 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.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

1 year, 3 months

[MM3-users] Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by Stephen J. Turnbull

Brett Delmage writes: > On Thu, 26 Aug 2021, Stephen J. Turnbull wrote: > > > However, it turns out that bots are almost as good at solving captchas > > as humans, and they can retry a lot faster. Captchas are also really > > horrible from an accessibility perspective. > > I have to disagree. > > I previously put a captcha on a Joomla website which stopped 100% of all > bogus account signup attempts. > > What was it ? "How many letters are in the word 'jazz'"? > This captcha is fully accessible, too. Of course, point taken. I've done similar things, and know quite a few such anecdotes. It's a good method, as long as *only a few of us use it*. But if enough people use it, patterns will show up, and we'll get into a "proof of waste" race with the spammers as we try to come up with logic puzzles people can solve but spammers' ML can't. I don't think it really addresses the issue that attackers can solve it easily if they want to, and will eventually automate that solution, although it does address the issue of accessibility (mostly -- I am not an expert but I wouldn't be surprised if long-time screen reader users are relatively poor spellers!) And it's not a satisfactory solution for a lot of our users. We can't safely add enabling functions to Mailman, because I'm sure there are a dozen Spamming as a Service (SpAAS) groups out there with Mailman 3 clone repos. So you need a skilled admin to implement custom CAPTCHAs. > If there's a captcha problem out there, it's because too many people just > use the same old, same old - Of course they do. After all, that's what software is for -- very cheaply using others' solutions for common problems. In this case, though, the "problem" is smart -- it's human attackers and their tools. > which is worth the bots cracking because it is used everywhere. That evaluation is close, but not exact in the age of SpAAS. If they want you, they'll get you, it's trivial for an open-subscription site. And if they need a human to crack your trivial CAPTCHA, a smart spammer (or even somebody who hates you for banning them from your comments) will add it to their box of tricks. I bet you'll get tired sooner than they do. Eventually it will make it into kiddie-scripts. The other thing is that if such simple captchas become popular, you know that the pros will start scanning sites for them just to make a database of patterns, and add hacks for any popular ones (or if they're smart, for every pattern they find -- I bet on a regular basis they'll get as lucky as I did when I stopped Klez, and then Fretham too, with just "iframe.*height=1"). Steve

5 years, 1 month

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

by David Newman

On 1/25/22 2:59 PM, gordon(a)dickens.com wrote: > Thanks to David and everybody else that have replied to my problem. I have proceeded to uninstall the debian mailman3 packages and then endeavored to install everything with venv. I have implemented all of David's configuration suggestions which were very helpful. Now, mailman3 (core) appears to be working properly in that I can start/stop/restart/status the service. Also, the command "mailman info" from the venv prompt yields output which appears to be correct and the same as in the venv instructions. However, I have not been able to get mailman3-web working. One general comment: Debian packages install files with a different owner than the pip install. You want to be sure all your directories and files are owned by the Mailman user ('mailman' on Debian). > > All of my configuration files may be viewed here: > > https://dickens.com/etc-mailman3/ > > The above files are basically a mirror of the contents of my /etc/mailman3 directory except that I have obfuscated sensitive info such as keys, passwords and email addresses. > > Executing the mailman3-web service script with the command "systemctl start mailman3-web" starts everything without errors, however, the command "systemctl status mailman3-web" then generates the following output with errors: > > ● mailman3-web.service - GNU Mailman Web UI > Loaded: loaded (/etc/mailman3/mailman3-web.service; enabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Tue 2022-01-25 17:10:30 EST; 6s ago > Process: 1718478 ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini (code=exited, status=1/FAILURE) > Main PID: 1718478 (code=exited, status=1/FAILURE) > CPU: 12ms > > Jan 25 17:10:29 slc.mailhub4u.com systemd[1]: Started GNU Mailman Web UI. > Jan 25 17:10:30 slc.mailhub4u.com uwsgi[1718478]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini > Jan 25 17:10:30 slc.mailhub4u.com systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE > Jan 25 17:10:30 slc.mailhub4u.com systemd[1]: mailman3-web.service: Failed with result 'exit-code'. > > Also, /var/log/syslog and "journalctl | grep mailman3-web" contain these two lines of errors: > > Jan 25 14:00:46 slc systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE > Jan 25 14:00:46 slc systemd[1]: mailman3-web.service: Failed with result 'exit-code'. Do you have anything further in any of the logs in /opt/mailman/web/logs ? > > Also, other commands in the venv instructions do not work such as "mailman-web migrate" which produces volumes of error dialog starting with: > > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.9/site-packages/django/template/utils.py", line 66, in __getitem__ > return self._engines[alias] > KeyError: 'django' This one might be due to a bug I hit as well. There's a problem with mistune, one of the components. If that's the issue here, this should address it, run as the mailman user: pip install mistune==2.0.0rc1 mailman-web migrate mailman-web compress mailman-web collectstatic mailman-web compilemessages dn

4 years, 8 months

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

by Florian Sukup

On 6/13/25 01:58, Mark Sapiro wrote: > On 6/12/25 15:05, Florian Sukup wrote: >> >> I always restart mailman3 after changing main.cf > > I asked if you restarted/reloaded Postfix. I would assume that you had, Sorry, I meant postfix which I restart after changing main.cf or master.cf. > 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: vvvvvvvvvvvvvvvvvvvvvvvvvvvvvv smtp inet n - y - - smtpd submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth -o smtpd_tls_auth_only=yes -o smtpd_reject_unlisted_recipient=no pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache postlog unix-dgram n - n - 1 postlogd maildrop unix - n n - - pipe flags=DRXhu user=vmail argv=/usr/bin/maildrop -d ${recipient} uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} 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. Is there a possibility to debug in more detail? To find out when and where it takes the wrong turn? The system running has grown over many years and even if the hardware changed the configuration was kept. So there may a flaw outside the postfix/mailman configuration which causes the error, ie. network configuration. Another thing I can do is to upgrade from bullseye to bookworm. Which I haven't done yet because I was with mailman2/sendmail. That's the reason to change to mailman3/postfix. Since, mailman2 doesn't work anymore I could do it and hope for a miracle ... . This would mean postfix 3.5.25 -> 3.7.11 and mailman3 3.3.3 -> 3.3.8 . That's more an act of desperation. Thanks for your help, Florian.

1 year, 3 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/19/20 7:42 PM, Brian Carpenter wrote: > On 10/19/20 10:23 PM, Mark Sapiro wrote: >> And the import21 created the user and address records for this user. > > Does the same thing for a new subscriber as well. So there is no pathway > to change a real name that is associated with an email address. None. > Zilch. Mailman 2 made this so easy and Mailman 3 made it impossible. I > will let someone else file the bug report. You don't really think that > this is an issue which means it will be years before it is addressed. So > I will save me some time. I will learn to live with it. I didn't say I didn't think it was a real issue. I mostly questioned whether a new subscription should change an existing display_name. I agree that there should be a way for a user to change the display_name associated with her address. I'm not so sure about a list admin. And in any case, I'm only one person. I'm not the only one deciding what's important and what's not. I only decide what I want to work on, not what anyone else thinks is important or wants to work on, so even if I think something is not worth doing, that doesn't mean it won't get done, and once again for emphasis, I do thing a user should be able to change the display name associated with her address(es). Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman 2.1 had no concept of user. All it knew was addresses subscribed to lists and an address subscribed to one list had no connection to the same address subscribed to another list or being an owner or moderator of a list. Mailman 3 does have a concept of user and addresses belonging to a user. This complicates things in some ways. In Mailman 2.1 we could have "The Boss <user(a)example.com" as a member of one list and "Just a Peon <user(a)example.com>" as a member of another list. In Mailman 3 that is not possible unless the addresses are tweaked in some way to make them different. You don't seem to be concerned about the case where I subscribe to a second list with a different display name and am surprised to find my display name changed on the first list, but it's something that I have to consider. As far as filing or not filing an issue, issues in the GitLab trackers are how we track these things. Threads on mailing lists are appropriate for discussion of issues, but if something is going to get changed or fixed, an issue in the tracker is the way to ensure it doesn't get put aside and forgotten. If this is as important to you as it seems to be, please file the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Stanisław Findeisen

Thank you for your clarification. I am now wildcard (*) DKIM-signing the (arbitrary) From: address domain with the host domain key. However my mailing list is a virtual host (actually there are several of them), which is different than the host domain. Do you know if such a setup is harmful? Or if there is a way to select the VHOST key? This is Postfix + OpenDKIM. With DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = Yes the VHOST key gets selected, which also results in (existing and) valid DMARC. Perhaps this setup makes it easier to pass through the spam filters?... But the cost is the abused From:. Thank you Stanisław On Sat, Mar 12, 2022 at 12:49:38PM -0800, Mark Sapiro wrote: > On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: > > > Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your > > > valid DKIM signature and no prior Authentication-Results:. > > > > Ok, you mean after replacing the From address with the list address, right? > > I can see no way (or sense) to DKIM sign arbitrary From: addresses. > > > Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. > validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. > > If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we > have DMARC mitigations suck as replacing the From: with the list address. > > > > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). > > > And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you > shouldn't need to rewrite From:. If it is because of DMARC, you do. > > > > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? > > > This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. > > We DKIM sign all outgoing mail from lists.mailman3.org. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 6 months

[MM3-users] Re: Mailing lists as the main collaboration centre at SME

by Stephen J. Turnbull

Rodrigo Camacho writes: > Currently I’m recommending mail.app for our mac users and > thunderbird for windows. Mail.app has a very annoying bug and a minor lacking feature. They probably won't affect you at all, but just in case: - Mail.app can produce "MUST NOT" mail, specifically it will specify Content-Transfer-Encoding: quoted-printable on multipart messages and parts. Mailman (2.1 as well as 3) will reject that. Since it is implemented in the Python stdlib, it's a wontfix for us. It's rare, so just be aware that if somebody's mail gets occasionally rejected at the SMTP level (not Mailman moderation), that might be the cause. I don't have a work around for users. - Mail.app cannot handle encapsulated message/rfc822 parts, at least on handheld devices like iPhone and iPad. This annoys me NO END :-) because I originated the "wrapped" option for DMARC mitigation. But in practice nobody uses it, so ... don't you either. ;-) > It’s truly rare to find GUI email clients which show threads > properly (who answered to what message precisely). It's weird: JWZ threading (https://www.jwz.org/doc/threading.html) was standardized for IMAP (RFC 5256) and I believe both Cyrus and Dovecot implement that extension. But I'm an Emacs person, so I rarely have a clue what developers of "popular" user clients think is good UI. I just know they pretty much invariably do something else. > For now, I have settled on the practices suggested by the LKML. We > will modify these to fit our specific needs as we notice they are > lacking. Seems reasonable. > > 4. The HyperKitty archiver was designed with the "we demand Discord" > > crowd in mind. > > I find that HyperKitty is difficult to read - the indentation on > threads is not clear enough to understand complicated threads. I'll keep that in mind. I don't know if any of the active devs deeply understand HyperKitty (it was a contribution by Red Hat, once they had it where they wanted, the devs became much less active). But it might be as simple as new CSS, or maybe new templates and a little CSS. > I find it very useful to see a graph which shows the precise > hierarchy of a thread. From an archive I’m looking only for ease of > navigation, robust search and easily being able to send a link to a > particular message, I find that https://lkml.org/lkml/2008/7/4/174 > has a super clear archive. That *is* *very* nice. Perhaps that archiver is open source, If not, it might not be hard to substitute similar page templates in HyperKitty. Not clear if you've already visited, so; Mailarchive (git@github.com:ietf-tools/mailarchive.git) is available from the IETF. You can check it out: https://mailarchive.ietf.org/. If you don't know what else to search for, there's a list named "ietf" to see the list-level interface. > If you know of any good netiquette practices which have been > documented (à la https://subspace.kernel.org/etiquette.html) please > let me know! Well, there's always ESR's how to ask questions: https://www.catb.org/~esr/faqs/smart-questions.html, but I think of that more as a threat than advice. There are a lot of netiquette posts out there. I love Brad Templeton's "Emily Postnews Answers Your Questions About Netiquette" (https://www.templetons.com/brad/emily.html) but it might be a little too tongue in cheek for the young'uns. > We are looking for a service which would host and manage our > mailing list setup (like mailmanlists.net) If you own or run such > a service, we are interested in being a client! Please let me know! First look at https://wiki.list.org/COM/Mailman%20hosting%20services, On that list EMWD was the odds-on recommendation, as the previous proprietor Brian was a frequent contributor to the lists and had a lot of support from their users. They were early adopters of Mailman 3 among hosting services and Brian went to the extent of creating alternative (simplified, proprietary) web UIs for archiving and administration. They also support Postorius and HyperKitty, I think. The principal of the mailman3.com and mailman4.com services (same dude) also regularly contributes on the lists, but I don't have direct knowledge of their services. I have nothing good or bad to say about the other services, I assume most are competent. Most use something like cPanel, and many are not Mailman specialists. Make sure they provide Mailman 3; not all do because cPanel decided to port Mailman 2.1 to Python 3 rather than make all their users migrate to Mailman 3. For custom and managed services, see https://wiki.list.org/COM/Mailman%20consulting%20services. Can't really be specific, because it's not clear at this point what you might want from a managed service that a list hosting service wouldn't provide. If you're not clear about yourself and want to explore what a managed service might do, we can discuss that here to the extent it would be of general interest. As for Sirius, yes, we're open for business, and I'm happy to talk about how Sirius Open Source can work with you offlist. See also https://www.siriusopensource.com/en-us/opensource/mailman. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year, 1 month

[MM3-users] Member name management by list owner

by mark＠suburbia.org.au

Bottom line up front: site admins can do some of the things below via https://example.com/mailman3/postorius/users thanks to https://gitlab.com/mailman/postorius/-/issues/403 - I am going to include my original post, in case it helps for visibility should others come up against this in future: -- Continuing in my initiation in the MM2.1 -> MM3 migration. I will say that while the software overall seems good, and the support in here has been excellent. I don't recall a more frustrating experience migrating a service in a long time. One of my list moderators runs a closed list for their non-profit organisation, whose demographic is on the more 'wise' side of life. As such, the organisation's committee pretty much handles all the list management for members, who receive a distribution list newsletter. They don't promote the ability to subscribe/unsubscribe/manage list settings to their membership as for some, replying to emails can seem complicated. It's been seen, (and based on the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… appears to be expected) that once an email address is first associated with mailman3, that whatever that member's name is sticks, including if the name wasn't initially used. And, that if you want to change it, you need to have the member login to/created an account at https://example.com/mailman3/user-profile/. E.g. if I as list owner/admin: 1) Add via mass subscription a new member whose email has never been seen by Mailman3 before `Wrong Name <specificemail(a)example.com>` 2) Search members and see it listed as `"Wrong Name" <email(a)example.com>` 3) Unsubscribe the member from the list 4) Add via mass subscription a same member with a new name `Correct Name <specificemail(a)example.com>` When I look at the members list it still shows `"Wrong Name" <email(a)example.com>` If I'm mistaken about any of the above or that does seem like a bug, feel free to let me know. Otherwise, is there any way, without expecting the members themselves to do it, for a site admin or list admin to change the name associated with an email address? I guess in order of preference, I'd like 1) list owner/admin to be able to modify list member name through web UI 2) site owner/admin to be able to modify list member name through web UI 3) list or site admin to be able to modify list member name through command line 4) direct editing of the mariaDB database. (And if this is the best option for now, if you can tell me the name of the db/table to look at it would be appreciated) -- Back to post BLUF solution - I guess my next ask, since the site admin can modify any user's name - would it be possible for me to grant a list owner/admin the ability to change names of any user without giving them full site admin access, and perhaps add the `Manage` button to the list's members list for them?

1 year, 10 months

[MM3-users] [Mailman-Users] Mailman 3 Ready?

by Stephen J. Turnbull

Reply-To set to mailman-users(a)mailman3.org. Allan Hansen writes: > I need to upgrade from Mailman 2.1 - my hardware needs upgrading > (badly) and the address mangling is having my subscribers rip their > hair out. That's not going to go away. We have ARC support in Mailman 3, but (a) like most envelope manipulation, that should be done in boundary MTAs, not in Mailman, and (b) ARC implementation is not universal. *Very likely* some of your subscribers are going to lose mail if you depend on ARC, rather than munge from. > I need to get this done before they start on my already thinning > hair! I sympathize. I tell the little kids I meet that my hair grows out of the bottom of my face, not the top (it's very alliterative in Japanese[1], the kids frequently don't get it but the accompanying adults usually laugh). > I’m ready and eager to move on to MM3 on a Linux box. The obvious "turn-key" installation is to use the Docker containers, which Abhilash keeps fairly up-to-date. But see comment below about universal working solutions. Which distro do you have? Are you using the distro's packages of Mailman 3 (not yet a good idea, unfortunately), or installing from source? > I have looked into it a few times now and I keep running into the > same blocks. I don't see much moving either. I was hoping someone > (Mailman developing community) would come up with a better working > solution. It's email. There are no universal working solutions. > [Some third party wrote:] My concern is that the Mailman3 is not > ready. There are too many dead ends and undocumented stuff. Who is this guy and has he consulted us? I'd like to do an archive search if he's done so to see what the issues are. > For Mailman2 I have a working integration with iRedMail, that does > not seem to work with 3. What's iRedMail? How does it fit into the community your lists serve? > So, is MM3 ready for the big screen? Works for us, for values of us including python.org. > If so, is there some way/how/where/when that my friend can get help > helping me with the installation other than the published > installation docs, which did not work for us? mailman-users(a)mailman3.org is the Mailman 3 version of this list. If your friend is the type to get his hands dirty with code, and has the time for development activity, mailman-developers(a)python.org would also be useful. You might be better off getting bids from consultants. There's a page listing them on wiki.list.org. > I have looked for both free and commercial alternatives to MM, There are sites that support MM commercially. I think the prices are reasonable, of course YMMV on that. Again, there's a page for those services on wiki.list.org. Footnotes: [1] "hage dakara hige o" -- the vowels are pronounced as Spanish or Italian, the consonants as in English.

6 years, 10 months

[MM3-users] Re: Internal Server Errors in mailmanweb.log

by Washington Odhiambo

On Fri, Jan 23, 2026 at 5:27 PM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Washington Odhiambo via Mailman-users writes: > > On Thu, Jan 22, 2026 at 10:07?PM Stephen J. Turnbull <steve(a)turnbull.jp > > > > wrote: > > > > The patch seems very simple, I don't see why it would cause the > > > problems you see. Are there any other changes vs. the stock > > > version you have? > > > > > > > None. > > Well, at least that means we know exactly what you're running in > Mailman. But this could be a problem in any of the dependencies > pulled in, as well. > > > I have not been in close contact with this situation ever since I > > switched to Gunicorn. > > And TBH, I have not seen any OOMs happening on the host. > > So you do not have a resource limitation, specifically memory, set on > the processes? This can be done with ulimit in the shell, and I'd bet > it can be done by systemd, but if you didn't do it it's very unlikely > that such a limit is in effect. > None. > > > Many multiprocess or multithread server implementations have a > > > tuning parameter where each task is limited to processing N > > > requests, then it exits and a new one is initialized. If > > > gunicorn has such a feature, lowering the number of tasks before > > > exit might help keep memory usage down if there's a leak. > > Limiting the number of requests before a worker thread/process exits > is still my best guess for immediate relief. See 'max_requests' > https://gunicorn.org/reference/settings/#max_requests > and 'max_requests_jitter' (next on the same page). 'max_requests' > defaults to 0, meaning "unlimited". > > > I am only having issues with mailmanweb. No other application - > > unless I haven't realized it. > > I don't know how the OOM killer makes its decisions. But it might > know which processes have grown quickly and kill those. If so, and it > is a memory leak in gunicorn or some other aspect of the mailmanweb > processes, other processes might not notice (except that the whole > system likely slows down when you run out of memory). > > > I don't have markdown enabled. IIRC, we checked this last time. > > Ah, that's right. I have trouble keeping track of who's had which > problems, and mistune is on the execution path for plain text, too, > which I have a tendency to forget. > That is okay. -- 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]

8 months, 1 week

[MM3-users] Re: Error on timeout vs retry values

by Andrew Hodgson

Hi. I just received the same error this evening when rebuilding Mailman3 on a new Debian 11 instal. There is a later version of Django on the new install. I got the original settings from the Mailman-Suite Gitlab project. I have made the modification but does this need to be made in that Gitlab project as well as that is where a lot of folks are getting their base Settings.py from? Thanks. Andrew. -----Original Message----- From: Robert Moody <robert(a)kneedrag.org> Sent: 18 July 2021 22:35 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Error on timeout vs retry values Thank you, that's fixed it. On 19/07/21 7:28 am, Abhilash Raj wrote: > > On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >> Hi everyone, >> >> I have recently setup a new mailman3 service using the venv method. >> Everything is functionally working however I keep getting an error >> sent to the mailman email every min which I can not seem to figure out why. >> >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: >> UserWarning: Retry and timeout are misconfigured. Set retry larger >> than timeout, >> failure to do so will cause the tasks to be retriggered >> before completion. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry for details. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry >> for details.""" >> >> I have edited the timeout and retry values in the >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file >> and restarted both mailman and mailman-web however this still keeps repeating. > You shouldn't edit files in `site-packages` directory as they are part > of the package itself and could cause issues. > > What you want to do is override it in your settings.py (or > settings_local.py) file for Django. I am not sure which guide you > followed to install Mailman, but it should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). > > It should look something like this > > > https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web > .settings.mailman.Q_CLUSTER > > Just the value of retry should be just > than timeout as the error > says, so not necessarily same values, but so far 300 and 360 has been > working good for us and I haven't seen any report to increase them. > > >> Any ideas? >> >> Regards, >> >> Robert >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> _______________________________________________ >> 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/

5 years, 1 month

[MM3-users] Re: OperationalError: database is locked

by Sten Aus

Hi I've had this problem when mailman was importing new lists (I had script running) and I wanted to access those lists. I am using sqlite as well. Sten On 11/01/2018 11:21, cyp(a)trojina.si wrote: > On our installation, we are often gettting Internal Server Error (500). The logs look like this: > > ERROR 2018-01-09 13:52:57,640 1604 django.request Internal Server Error: /hyperkitty/list/test(a)seznami.cjvt.si/ > Traceback (most recent call last): > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/exception.py", line 42, in inner > response = get_response(request) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 249, in _legacy_get_response > response = self._get_response(request) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/HyperKitty-1.1.0-py2.7.egg/hyperkitty/lib/view_helpers.py", line 133, in inner > mlist = MailingList.objects.get(name=mlist_fqdn) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/manager.py", line 85, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 379, in get > num = len(clone) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 238, in __len__ > self._fetch_all() > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 1087, in _fetch_all > self._result_cache = list(self.iterator()) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 54, in __iter__ > results = compiler.execute_sql() > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/sql/compiler.py", line 835, in execute_sql > cursor.execute(sql, params) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute > return self.cursor.execute(sql, params) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/utils.py", line 94, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute > return self.cursor.execute(sql, params) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 337, in execute > return Database.Cursor.execute(self, query, params) > OperationalError: database is locked > > Does this suggest I should switch from sqlite to postgres (https://stackoverflow.com/a/26864360)? I'm happy to do that, but how do I migrate the data between the databases (after installing postgres and creating the database)? I've found this doc (http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html#data…) but I don't think I understand this and I haven't used alembic: these instructions are just for when you modify the model within the same database, right? > > Thanks in advance! > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 8 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > On 13/2/21 20:00, Mark Sapiro wrote: > > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > But... here is a thing that I can not understand: If the source (the > > > .po > > > file) is from november 7th, it doesn't matter how many times you > > > recompile it: the result will be the same. > > Correct, but the point is if you download the latest > > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 > > file > > in the distribution, you will find they are identical, so it it appears > > that the weblate translation hasn't changed since that time. > > > > If there are issues in this mailman.po, they exist in weblate too and > > need to be fixed there. > > That clarifies all. Thanks. As I said in my previous message, I'll wait > for the next upgrade and hopingly the translations done after 7h of > november (by others and me) will be there. I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version. Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-) > > Also note that the translations on weblate only affect strings in the > > core code. The Mailman core templates are not currently translated in > > weblate and there are currently no Spanish language templates. One > > would > > need to create Spanish translations of all the templates in > > < > > https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en > > > > > and submit a merge request to add them to a mailman/templates/es/ > > directory. > > > I will make the template translations locally, test them, and then, if > they are yet lacking in the main repo, follow your suggestion. I'm a bit short on time, but I'll help Guillermo with that, at least reviewing or doing a second pass. I'm not proficient enough to speak about Mailman core templates, but for Django templates, there is a nice tag for marking text with translations in the .mo files ... -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 7 months

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

by Simon Handfield

Thanks Stephen and Mark for your replies. I have been able to identify a file in the shunt queue that threw a matching error when I performed mailman qfile on it. I moved this file out of the queue in the hope that I would then be able to load the held_messages page successfully. Unfortunately I am still seeing a 500 error on loading the page. I temporarily reenabled debug logging to confirm that the same error was being thrown. I have run a loop over all remaining files in the shunt queue and all the remaining files can be accessed by mailman qfile without error. Assuming that file was the cause are there other steps I need to perform in addition to removing the file from the shunt queue directory? Thank you, Simon. ________________________________ From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Sunday, 30 August 2020 12:52 To: Simon Handfield <simon.handfield(a)sl.nsw.gov.au> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius Simon Handfield via Mailman-users writes: > I have been working through other threads that indicate the same > symptom (500 error when loading held_messages for a list). You want threads that deal with Unicode: > Error reported in log with debug enabled: > > Traceback (most recent call last): And that last call is:: > 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) It appears that the message is improperly constructed, and either a Content-Type field has a omitted or inappropriate charset parameter, or perhaps the Content-Type field is omitted entirely (ASCII is the default charset). This is frequently a problem created by spam messages. The message should be in the shunt queue. You can examine it with the command "mailman qfile /path/to/message_file.pck". Unfortunately it's not clear from the backtrace where in the message this is: it's at the beginning of a part ("position 8-9") or maybe line, but the part could be late in the message. If it's spam, you can just delete the file (and do whatever else you do about spam, of course). If it's not spam, it would help if you can guess what language and charset are being used in the message, and we can go from there. If this is unclear, feel free to ask more. _ [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.

6 years, 1 month

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Odhiambo Washington

On Mon, Aug 4, 2025 at 4:53 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/3/25 00:09, Odhiambo Washington via Mailman-users wrote: > > I wonder what this means and whether it's fatal. > > > > How do I fix it? > > > > ``` > > ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) > ... > > *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() > > returned more than one EmailAddress -- it returned 2!* > > It appears you created a new list, and that list' owner email address > has two Django user records with emails differing only in case. I did not create a new list actually. I was working on an existing list. See https://www.msapiro.net/scripts/UC_fix for a script to fix this or you > can just go to the Django web UI and delete the mixed case user. > The script did not work for me as-is because I use MySQL on this site. > > I suspect it's something to do with my action yesterday while attempting > to > > reply to a thread from HyperKitty. > > Possibly, if hyperkitty was looking at a mixed case email address that > it didn't recognize as a list member and subscribed it. > Happens to not have been the case either. No mixed case address. > > The superuser account uses my address - odhiambo at gmail dot com.I am > also > > the listowner for most lists. > > I tried unsuccessfully to create an account on Postorious using the same > > email address. > > I kept getting sent links to verify the account, over and over. > > Finally, I was able to verify the account, but cannot login with it. > > This too is probably because there are two accounts with email addresses > differing only in case. > With assistance from ChatGpt, I went digging into the DB and what I found (as I expected) turned out to be slightly different: [email slightly obfuscated!] ``` MariaDB [mailmansuite]> SELECT id, user_id, email, verified, `primary` FROM account_emailaddress WHERE LOWER(email) = 'odhiambo__gmail.com'; +------+---------+--------------------+----------+---------+ | id | user_id | email | verified | primary | +------+---------+--------------------+----------+---------+ | 1844 | 1823 | odhiambo__gmail.com | 1 | 0 | | 2548 | 4 | odhiambo__gmail.com | 0 | 0 | +------+---------+--------------------+----------+---------+ 2 rows in set (0.002 sec) ``` MariaDB [mailmansuite]> SELECT id, username, email, is_active FROM auth_user WHERE id IN (SELECT user_id FROM account_emailaddress WHERE LOWER(email) = 'odhiambo__gmail.com' ); +------+----------+-------------------------+-----------+ | id | username | email | is_active | +------+----------+-------------------------+-----------+ | 4 | odhiambo | odhiambo__gmail.com | 1 | | 1823 | admin | odhiambo__kictanet.or.ke | 1 | +------+----------+-------------------------+-----------+ 2 rows in set (0.011 sec) So I resolved it by deleting the duplicate: MariaDB [mailmansuite]> DELETE FROM account_emailaddress WHERE id = 1844; Now I need to find a way for me to subscribe my email address as an ordinary user for starters. This is refusing. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 1 month

[MM3-users] Re: Sendgrid experiences (now Office 365)

by Tom Smyth

Thanks Stephen. I think it would kind of be a dealbreaker if some folks couldn't get mail with no way to remedy. Are there other hosts? How is this not a bigger issue for Mailman users? Maybe most are big institutions that have their own SMTP relays and dedicated staff to keep deliverability/reputation high? Or maybe a lot of people are using DMARC mitigation so that the 'from' address is always the list address? I am curious how well that works. I'll start a separate thread on that. On Sun, Sep 28, 2025 at 8:53 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > How do you even debug email/SMTP transactions on google workspace? > > > On Sun, Sep 28, 2025 at 3:38 PM Stephen Daniel <swd(a)pobox.com> wrote: > >> I am running mailman3 in google's cloud. I have a google workspace >> account >> with a single authorized user. ($8/month) I use those account >> credentials and have mailman3 using google's smtp servers as the outbound >> relay. Works OK. There are still some members of my organization who >> don't receive list emails, for reasons I've never been able to debug. >> >> On Sun, Sep 28, 2025 at 7:43 AM <tom(a)tomsmyth.ca> wrote: >> >> > Reviving this old thread... >> > >> > Are folks still using Google Workspace or Sendgrid for Mailman? >> > >> > For Sendgrid, don't all sending addresses have to be verified? How do >> you >> > get around that? Surely you don't have all list members go through the >> > verification process? >> > >> > Does Google not have this restriction? >> > >> > Or am I missing something about how this works? Are people just having >> all >> > list emails come from the list email address and using the Reply To >> header >> > or something? >> > _______________________________________________ >> > 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 >> > >> _______________________________________________ >> 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 odhiambo(a)gmail.com >> > > > -- > 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] > -- Tom Smyth (he/him)

1 year

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

by tlhackque

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

9 years, 1 month

[MM3-users] Re: Dmarc settings and

by Abhilash Raj

On Sat, Sep 7, 2019, at 7:36 PM, paul(a)arenson.org wrote: > Can ANYONE help? I guess it is bad form to create more threads. But I > am losing confidence. > > - - - - - - - - - - - - -- - - - - - - - - - - - - > MAILMAN 2.1.27 (CPANEL > - - - - - - - - - - - - -- - - - - - - - - - - - -) > 1) I checked our old list. (I no longer manage it but I have access > to the settings) > > 2) Those settings are: > -->Should the Sender header be rewritten for this mailing list to avoid > stray bounces? > Yes is recommended., Details for include_sender_header > > -->Privacy Options Sender rules > > -->Action to take when anyone posts to the list from a domain with a > DMARC Reject/Quarantine Policy. Munge > > --->Shall the above dmarc_moderation_action apply to messages From: > domains with DMARC p=quarantine as well as p=reject > > Yes > > > Shall the above dmarc_moderation_action apply to messages From: domains > with DMARC p=none as well as p=quarantine and p=reject > No > > - - - - - - - - - - - - -- - - - - - - - - - - - - > 3) MAILMAN 3 ( Hyperkitty 1.2.2) > - - - - - - - - - - - - -- - - - - - - - - - - - - > Now i want to make sure that my new list does not encounter problems > My settings are > > -->Alter > > REPLY GOES TO THE LIST is selected This option controls if the `Reply-To` header is always changed to the list, instead of letting it be whatever the email came with. This list is configured with "No Munging". "Reply goes to the list" basically means that if I send an email to the list with "Reply-To" set to my own address ( so that replies are directed to me instead of the MalingList because I don't want people to send replies the list), Mailman will unconditionally change the "Reply-To" header to list's address. "Reply-To" header is used when for some reason "From" address can't be used by mail clients. Unless you have a strong reason to change this, the default value is "No Munging". > > -->DMARC Mitigations > > a) Dmarc mitigation Action replace From: With list address > > b) Dmarc Mitigate unconditionally > > Now NO. SHOULD I CHANGE THIS TO "Yes" Let this be the default option, which is "No", unless you have strong reason to do so. DMARC policies are published per domain, so, some of your senders will have DMARC policy that will cause emails from Mailman to be rejected by receivers. For those senders, Mailman will replace the "From" header to list's address so that DMARC doesn't fail for the receiver. Doing it unconditionally means that you replace "From" header of every email to the list address. > > > Can anyone approve or disapprove? Please. I need to make sure this is > right BEFORE going live. > _______________________________________________ > 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)

7 years

[MM3-users] Re: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:46 PM, Jeff wrote: > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > 1) some emails that arrived before I got the archive working are still sitting in: > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a collection of messages in maildir format. This is how the prototype archiver stores messages. This has nothing to do with HyperKitty. It is a separate archiver. If you don't want messages to be stored there, you can disable the prototype archiver for the list by unchecking prototype in Postorius -> Settings -> Archiving -> Active archivers or disable it entirely for the installation by setting ``` [archiver.prototype] enable: no ``` in mailman.cfg > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > /usr/local/mailman3/mm/var/queue/shunt > > What should I do to get these messages processed? Assuming the issues that caused them to be shunted have been fixed, just run the command ``` mailman unshunt ``` > 3) Similar to above, some messages are in: > > /usr/local/mailman3/mm/var/queue/bad > > How can I get these messages processed? First examine the messages with ``` mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> ``` To be sure you want them. Also examine mailman.log for the times they were stored in the `bad` queue. You are looking for 'Skipping and preserving unparseable message: <file>' and/or 'SHUNTING FAILED, preserving original entry: <file> messages and you want to determine which runner preserved the message. There may be a 'whichq' entry in the message's metadata in which case, that's the answer. Once you have determined the queue, you can just move the .psv file from the bad queue to the appropriate queue, renaming it from .psv to .pck in the process. > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? I know little about uwsgi. setting it to `uwsgi://localhost:8000` might work. You could also set it to the base URL that a user would use to access the web UI, e.g. `https://example.com` and that would presumably be proxied to uwsgi. For example, on the server for this list we have ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' ``` which gets proxied to gunicorn, but the idea is the same. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 11/14/25 15:36, Cathryn McGuire wrote: > Hi Mark, > > "It appears in your case that Gateway to news is Yes and Newsgroup > moderation is Moderated" > > I don't see any Gateway to mail or Gateway to news, but Newsgroup moderation was set to Moderated (as you said). I changed it to Not Moderated. That's good. As I've said, I don't know what the affinity UI looks like. If you send me (off list) a screen shot of the page where you see Newsgroup moderation, I can advise you further, but basically, anything to do with Newsgroups should be set to Off or No. > In the following case, they are cc'ing to the mailist, and To: is to a member. Sometimes they are not members. Sometimes they To: to the mailist and cc: to the member or non-member. > > Subject:Re: [Neighbours] Furnace problems > To:Bill McCreery <billmccreery1(a)gmail.com> > Cc:neighbours@mailist.dunbar-vancouver.org > Content-Type:multipart/alternative; boundary="000000000000f9e5900643322d20" > X-MailFrom:dunontime@gmail.com > X-Mailman-Rule-Hits:header-match-neighbours.mailist.dunbar-vancouver.org-0 > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation My understanding is you want to hold for moderation any message with a Cc: unless it it To: the list with a Cc: to a member, and I said that with what's available to you in the list's settings, you can't distinguish between Cc: to a member and Cc: to a nonmember, so you have to hold any message with a Cc: > "If the reason was actually what is posted above with 'neighbors' > rather than 'cc:', that's a problem with EMWD's Mailman core." > > Does that mean that any cc: to neighbours or to a member or non-member should be blocked (held)? > Or, does that mean if the cc: is to neighbours, it should be allowed through? That quote was in response to your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… wherein you said > The message is being held because: > > Header "neighbours > > <neighbours(a)mailist.dunbar-vancouver.org>" matched a > header rule I thought that was a typo and the real reason was Header "Cc: <neighbours(a)mailist.dunbar-vancouver.org>" matched a header rule. If that was the case, it was expected and was due to your header filter on Cc: headers. My confusion was I couldn't see how the reason could have been Header "neighbours <neighbours(a)mailist.dunbar-vancouver.org>" matched a header rule. And if it was, that was an EMWD issue. I think the header rule you have will hold any post with a Cc: to anywhere. If you want to not hold posts with a Cc: <neighbours(a)mailist.dunbar-vancouver.org> regardless of To:, you can do that by adjusting your header rules, but I don't think you want that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

I created a new list with this setting. This new created list can send to Gmail addresses, this is very strange, because I have changed the problem list (The list that cannot send to @gmail addresses) settings to match the new one, but still the issue is there. The only difference is that the problem list has been imported from mailman2. Question: is there a command line that displays all the settings of a list? I think it might be some hidden settings that are not visible in the UI? Thanks Mohsen ________________________________ From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, September 6, 2023 1:32 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Issues with @gmail.com addresses Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

3 years

[MM3-users] Re: Upgrade path

by David Krantz

Hi. Getting back to this... Some log of what I'm doing. * First git fetch; git pull on all parts. Started new envs to simplify rollback etc. * activate the new 3.5 venv. ( I run the commands one at a time, but this is more compact in text form:) > cd git/mailman; python setup.py build; python setup.py install > cd ../mailman-hyperkitty; python setup.py build; python setup.py install > deactivate activate 2.7 venv, then > cd ../mailmanclient; python setup.py build; python setup.py install > cd ../django-mailman3; python setup.py build; python setup.py install > cd ../postorius; python setup.py build; python setup.py install > cd ../hyperkitty; python setup.py build; python setup.py install So far no errors. Just warnings. Backups: * deployment directory (as user with rw in directory) > tar -cvzf backup.tgz deployment_directory * postgres databases (as user with postgres-priv) > pg_dump maiman | gzip -9 > mailman.bak.gz > pg_dump mailmanweb | gzip -9 > mailmanweb.bak.gz Create new .wsgi-file based on mailman-suite (I used the kludge in the script to get the python path correct) Change apache2.conf to point to new venv and new wsgi-version Updated the mailman3wrapper.sh I use for init to start the service. I could not get hyperkitty interface to run so I deactivated it and set mailman as index instead. It complains that a column is missing, but I cannot get the migrate script to run so I decided that I do not need the archiver as I currently don't use it. So I will have to get back to this and either remove the archiver completely or get it to run. So the line with ^$ in urls.py now is url(r'^$', RedirectView.as_view(url=reverse_lazy('list_index'))), instead, and the line "hyperkitty," is commented in the django application list. cheers. // David On Tue, Aug 8, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/08/2017 04:42 AM, David Krantz wrote: >> >> What is the rekommended way to upgrade to the newest version? (newest >> _usable_ version, of course)? Is it docker-only with a migration from >> the current solution to a docker based? If so, any ideas or pointers >> on how to go about this? > > > You may find this wiki article helpful <https://wiki.list.org/x/17891998>. > > I started with bundler on both this (lists.mailman3.org) and the > mail.python.org installs, but have been updating from the heads of the > various gitlab branches since very early on. > > At the moment, these installations are somewhat ahead of the 3.1 > release, but I am not updating as the latest core has dropped Python 3.4 > support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu > 14.04) servers. (I will probably install 3.6 from source at some point.) > > Please feel free to ask here if you have more specific questions. > > -- > 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/

9 years

[MM3-users] Re: Mailman web Stopped working after upgrade

by David Krantz

But now that it is working the order of the mailing lists on the index page are in random order again. When it worked initially they seemed sorted by name. Whey I follow the link "see all lists" the order is correct, though. Annoying. BR // David On Tue, Mar 3, 2020 at 10:26 PM David Krantz <gazorg(a)gmail.com> wrote: > > Hi, > > I tried psycopg2-binary and a few other rehashes of that. Now I got it > working by downloading the source for psycopg2 manually and building > it myself, then I installed it into my venv like any other self-built > package. https://pypi.org/project/psycopg2/#files > > I run mod_wsgi in Apache so I thought it should be enough to restart > Apache. I am quite convinced that I did that (and for that matter > restart the machine at a few points). But I might have been sloppy and > reversed the order in the end when I got it running, this process is a > bit to manual. I will use another solution when I rebuild the server > one day. The problem with rebuilding the server is that I'd have to > install a MTA with all its modules, milters, setups and what not, and > mailman. To just reinstall on a fresh machine would be easy, the trick > is that I want to rebuild some things in a better way which will take > me some time. E.g. using a separate wsgi service and a more modern > spam filter than Spamassassin. Otherwise it is easy. But my situation > now is a bit short on time so if I can postpone that a bit I will. > > Thanks. > // David > > // David > > On Tue, Mar 3, 2020 at 10:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 3/3/20 12:33 PM, David Krantz wrote: > > > > > > I think that this might be due to some kind of python misfeature where > > > compiled code behaves slightly differently to interpreted code, that > > > might explain the delay in it working initially before breaking. I > > > have no idea of how to solve this. I have tried to uninstall and > > > reinstlall psycopg2 in different versions without any luck. > > > > You need to activate your virtualenv and do > > > > pip install psycopg2-binary > > > > it must be psycopg2-binary, not just psycopg2. It's probably best to do > > > > pip uninstall psycopg2 > > > > first. > > > > As far as it working for a while, did you restart your wsgi service > > (gunicorn, uwsgi, ??) after upgrading? > > > > -- > > 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/

6 years, 6 months

[MM3-users] Re: Verification Failed Error

by Odhiambo Washington

I agree with you. On Fri, 21 Dec 2018 at 23:21, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Fri, Dec 21, 2018, at 12:18 PM, Odhiambo Washington wrote: > > > > On Fri, 21 Dec 2018 at 20:19, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > On Fri, Dec 21, 2018, at 4:00 AM, Stephen J. Turnbull wrote: > > Abhilash Raj writes: > > > > > Exim experts would be able to help you better with this. > > > > I'm the one who set up the original sample Exim .conf, because (a) I > > didn't want to migrate all my bots to Postfix, and (b) the one-real- > > host .conf turned out to be trivial. I'm an Exim expert only for my > > own configuration, which is a (pre-global-warming) glacially-moving > > target. I've never seen anything like the problems described here, > > sorry. Can't help. > > > > Since it's looking like we don't have any real Exim experts hanging > > around here, perhaps we should move the sample containers and other > > default configs to assume Postfix and document "Exim should work but > > you're kinda on your own, we'll do what we can but it's limited." At > > least Mark is maintaining such systems, and they're probably better > > documented than Exim for the single-real-host configuration, though > > they would probably run into similar problems with the containerized > > setup. WDOT? > > > Originally, the reason I went with Exim was because the postmap + hash > files were hard to generate for Mailman from within the container when > the postfix was running on the host. Exim checks existence of certain > paths to verify that the Mailing List exists, which was easier to do. > > However, now Mailman Core supports regex maps for Postfix, which > can be used with containers. > > Images already support using Postfix, it is just not the default in setup > scripts and documentation. I have opened an issue[1] to maybe change > that if some initial testing doesn't goes fine. > > [1]: https://github.com/maxking/docker-mailman/issues/282 > > > > Hello Maxking, > > It is importantest to maintain Exim support :-) > > > > I didn't mean to say that we are going to stop supporting Exim, it is just > that > I'll make Postfix default in Container given that most of the Mailman Devs > are > more comfortable helping out people with Postfix issues, as they use it for > their own personal setups. > > Switching between default and non-default would be easy and both of them > will be supported, to the best my own abilities :) > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > > > -- > thanks, > Abhilash Raj (maxking) > > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 9 months

[MM3-users]Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Hello World! Very nice to meet you all this afternoon! 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. 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.

10 years, 4 months

[MM3-users] Re: Mailman3 in AWS

by Barry Warsaw

On Aug 19, 2016, at 05:02 PM, Andrew Hodgson wrote: >-Any issues with runner processes being ran on more than one machine talking >-to the same DB backend? There shouldn't be, especially with PostgreSQL or MySQL (MM3.1), although we're pretty much relying on SQLAlchemy to do the right thing. Cheers, -Barry

10 years, 1 month

[MM3-users] Find a smtp server to send out emails

by Leon

Hi, This problem is not caused by mailman, but I still want to give it a shot here. I'm hosting a mailing list on top of mailman3. Emails are supposed to be sent out by AWS ses. However, ses requires that sender address must be verified, which leads to a problem that emails sent by subscribers to mailing list cannot be sent to other subcirbers, since their addresses are not verified. And it is impossible to verified every subscriber. Are there smtp service providers allowing unverified email address to send out emails, or do I have other solutions? Thanks. -- Best wishes, Leon

9 years, 9 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 03, 2016, at 09:22 PM, Florian Fuchs wrote: >I think it's OK to put out a separate beta of the core, because the >version pulled from pypi will still be 3.0 if I'm not terribly mistaken. BTW, I did upload a beta of Core to PyPI before I started my travel. >For the real 3.1 we should probably do a coordinated release of all >components, once everything's tested a little more thoroughly. For sure. Cheers, -Barry

9 years, 9 months

[MM3-users] Re: Domain in welcome message

by Maadix

Hi, I'm having problems with customizing welcome message It's working fine for var/templates/site/en/welcome.txt but not for domains or lists , so maybe I'm doing something worng I'm using a subdomain as mail_host which is different from the URL Host. I've been trying all these combination, with no success: var/templates/domains/sub.example.com/en/welcome.txt var/templates/lists/listname.sub.example.com/en/welcome.txt var/templates/lists/listname(a)sub.example.com/en/welcome.txt I'm running mailman-bundler version 3.0.0 Thank you

9 years, 7 months

[MM3-users] Mailman 3 api php

by david.terni＠gmail.com

Hi, I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Someone can help me? Thank's a lot

9 years, 6 months

[MM3-users] Auth question

by David Krantz

Hi, I have of course activated password login as it was not possible to get the provider based logins to work (might be but not worth the time for me right now). Is there any way for an user to request a new password when it is forgotten? I presume that the Persona login is removed now. I cannot hide it in my version or at least I do not know how. cheers // David

9 years, 6 months

[MM3-users] Remove footer link

by David Terni

Hi, I need to remove footer message like "to unsubscribe etc etc" from all lists. How i can do it or edit text? Thanks alot for any suggestion. David

9 years, 5 months

[MM3-users] Re: "Private archives" aren't private

by Simon Hanna

>> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Looks like you want to run the Hyperkitty management command "mailman_sync" You could also just grab the MailingList object you want and run "mlist_object.update_from_mailman()" on it. I couldn't get the command to run, will investigate later...

9 years, 3 months

[MM3-users] Confirm on mass subscription

by David Krantz

Hi, Is there a way of requiring all mass subscribed users to confirm their email adress? I have an use case where we have a current mail list but when moving it to mailman I for different reasons would like to confirm all subscribers. Some very shallow testing suggests that if I just add them using mass subscribe, they will not have to confirm at all. I have yet to upgrade to 3.1 but I will do so in due time. cheers // David

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Dear Simon, I did Simon's steps and got this: [root@localhost ~]# useradd -r -m -d /var/lib/mailman mailman useradd: user 'mailman' already exists [root@localhost ~]# su - mailman Last login: Wed Jul 12 15:19:42 EDT 2017 on pts/0 su: warning: cannot change directory to /var/lib/mailman: No such file or directory What should I do? [excessive quoting removed]

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Dear Kyle, sorry ... El jue., 13 jul. 2017 a las 12:58, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Dear Simon, > > I did Simon's steps and got this: > [root@localhost ~]# useradd -r -m -d /var/lib/mailman mailman > useradd: user 'mailman' already exists > [root@localhost ~]# su - mailman > Last login: Wed Jul 12 15:19:42 EDT 2017 on pts/0 > su: warning: cannot change directory to /var/lib/mailman: No such file or > directory > > > What should I do? > [excessive quoting removed]

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Kyle Richardson

Try this... # userdel -r mailman # useradd -r -m -d /var/lib/mailman # su - mailman Then continue on with the steps outlined. -Kyle On Thu, Jul 13, 2017 at 1:58 PM, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: > Dear Simon, > > I did Simon's steps and got this: > [root@localhost ~]# useradd -r -m -d /var/lib/mailman mailman > useradd: user 'mailman' already exists > [root@localhost ~]# su - mailman > Last login: Wed Jul 12 15:19:42 EDT 2017 on pts/0 > su: warning: cannot change directory to /var/lib/mailman: No such file or > directory > > > What should I do? > [excessive quoting removed]

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Dear Kyle, I got this running the useradd command: [root@localhost ~]# useradd -r -m -d /var/lib/mailman Usage: useradd [options] LOGIN useradd -D useradd -D [options] Options: -b, --base-dir BASE_DIR base directory for the home directory of the new account -c, --comment COMMENT... It seems that the params are not ok, what do you think?? El jue., 13 jul. 2017 a las 13:25, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > Try this... > > # userdel -r mailman > # useradd -r -m -d /var/lib/mailman > # su - mailman > > Then continue on with the steps outlined. > > -Kyle > [excessive quoting removed]

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Kyle, After doing the steps and running mailman info I got: Permission denied: '/var/lock/mailman' El sáb., 15 jul. 2017 a las 13:53, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > Rafael, > > I have validated that these steps [1] work on a clean CentOS 7 x64 build. > > [1] > https://gist.github.com/kylerichardson/9dcf72082feccf77a7bee4be5c390400 > > -Kyle > > -- Atentamente / Best Regards Ing. Rafael Mora

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Kyle Richardson

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

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, What are the suggested steps in order to install the web UI ?? 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

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 12:07 PM, Rafael Mora wrote: > 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?? It's another case of incorrect docs. It should be git clone https://gitlab.com/mailman/mailman-suite.git See <https://gitlab.com/mailman/mailman-suite-doc/issues/15>. -- 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: Installing mailman 3

by Mark Sapiro

On 07/21/2017 12:33 PM, Rafael Mora wrote: > > I'm getting an error doing: > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py migrate > Traceback (most recent call last): > File "manage.py", line 8, in <module> > from django.core.management import execute_from_command_line > ImportError: No module named django.core.management Have you installed Django in your 'env' virtualenv? -- 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: Installing mailman 3

by Mark Sapiro

On 07/21/2017 02:05 PM, Rafael Mora wrote: > > (env2) [mailman@localhost mailman-suite_project]$ python2 manage.py > runserver > Performing system checks... > > System check identified no issues (0 silenced). > July 21, 2017 - 20:50:29 > Django version 1.11.3, using settings 'settings' > Starting development server at http://127.0.0.1:8000/ > Quit the server with CONTROL-C. And did you try to go to http://127.0.0.1:8000/ or http://localhost:8000/ from a browser on that machine? If you're truing to access it from another machine, you need to do something like python2 manage.py runserver 192.168.1.42:8000 -- 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: Installing mailman 3

by Mark Sapiro

On 07/23/2017 06:00 PM, Rafael Mora wrote: > Hello guys, > > This is what I've got on ../var/data: > > [root@localhost data]# pwd > /var/lib/mailman/var/data > [root@localhost data]# ls -l > total 76 > -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db > > > What should I do in order to let mailman install the DB files? Run bin/mailman aliases -- 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: Installing mailman 3

by Mark Sapiro

On 07/24/2017 07:41 AM, Rafael Mora wrote: > Ok, I ran 'mailman aliases', what should I do now? Assuming mail delivery is not working, look in /var/log/maillog for messages with timestamps around the time that the mail was generated. Then try to figure out what they are saying. -- 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: Installing mailman 3

by Mark Sapiro

On 07/24/2017 03:31 PM, Rafael Mora wrote: > I got this on maillog: > > > > [root@localhost log]# cat maillog There's nothing in that log that shows any attempts by anything to connect to Postfix. You have to look at logs from the processes you think are trying to send mail and see what they're doing. -- 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: Installing mailman 3

by Mark Sapiro

On 07/25/2017 12:58 PM, Rafael Mora wrote: > I got this error starting mailman service: > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > create_server > sock.bind(sa) > OSError: [Errno 99] Cannot assign requested address ... > What do you think? I think you have configured lmtp_host: mail.example.com which is wrong. -- 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: Installing mailman 3

by Mark Sapiro

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

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 08/01/2017 02:48 PM, Rafael Mora wrote: > Postfix is listening on 127.0.0.1:25 is it ok? or should listen on > 0.0.0.0:25?? Listening on the loopback address is sufficient if you just want to send mail. If you want Postfix to receive non-local mail to be delivered to Mailman, you need to listen on an internet connected interface. If you put inet_interfaces = all in main.cf replacing any other inet_interfaces setting, that should do it. -- 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] Whitelist non subscriber

by Mark Ziranski

Hello, 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. Thanks in advance. M.Z.

9 years, 1 month

[MM3-users] Bounce processing

by Mark Ziranski

Hello, I read that mailman3 supports 'bounce processing' but I do not know how to configure it. I want to delete members automatically from a mailing list if the delivery has failed after a certain time of attempts because his mailbox has been removed or his mail server has been shutdown etc. There is also the case that an users mailbox is full (mailbox limit exceeded). Is possible to deal with this case too? Thanks.

9 years, 1 month

[MM3-users] Which documentation to follow for installation

by ribanez＠sciops.esa.int

Hi everyone, I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to look for documentation. I found two different sites: https://mailman.readthedocs.io/en/latest/ http://docs.mailman3.org/en/latest/ Do you know which one should be followed? Both at the same time? I find it quite unclear... and this installation will be for an operational environment. Also, there are some (official?...) docker images, but all images are for mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. Thanks in advance! Regards, ribanez

9 years, 1 month

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Mark Sapiro

On 09/01/2017 04:29 PM, Andrew Hodgson wrote: > bin/mailman import21 > > I saw this in the image, do you have any idea about what may be missing from this? I don't specifically recall. I know I tried it only once and it threw some exception and died, but not before creating some templates in an obsolete (for current MM 3) format. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Mark Sapiro

On 09/01/2017 04:29 PM, Andrew Hodgson wrote: > > bin/mailman import21 > > I saw this in the image, do you have any idea about what may be missing from this? I did report this at the time. See <https://gitlab.com/mailman/mailman/issues/270>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Social Auth, howto?

by Mark Sapiro

On 09/02/2017 01:06 PM, Claus-Justus Heine via Mailman-users wrote: > Github: > internal server error 500, Django log: DoesNotExist: SocialApp matching > query does not exist. > > Same with GitLab and Google. > > Ok, seemingly I need to do something to make it work, has anyone a link > to some snippet of documentation of example setup? Assuming you have created appropriate apps at GitHub, GitLab and Google, go to your Django administration web UI and add the apps with their credentials under SOCIAL ACCOUNTS -> Social applications. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Installing mm3 with docker

by Tom Browder

I am trying to follow instructions but when I get to the actual docker pull command (with trust enabled): # docker pull maxking/mailman-core:release I get an error message: No trust data for release I have tried adding various tags but no changes. What am I doing wrong? Thanks. -Tom

9 years

[MM3-users] restrict sending to owner/moderator

by m.dohmen＠xconnect.de

Hello, I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. Is there a way to do this?

9 years

[MM3-users] Change Base URI for Mailman 3.1

by Dmitry Makovey

I'm tinkering with docker container of mailman 3.1 however I'm trying to utilize existing nginx server thus I need to map "/mailman" to mailman-web docker container vs default "/" mapping. Where do I configure base URI for mailman-web ? (quick search of archives and googling didn't yield any positive results thus far) -- Sr System and DevOps Engineer SoM IRT

9 years

[MM3-users] Re: How to get Mailman core to provide more debug info in a running environment

by Barry Warsaw

On Sep 29, 2017, at 07:38, Henrik Rasmussen <her(a)adm.ku.dk> wrote: > > Oh okay. I suppose that smtp failures will be logged in the smtp.log by default then? Or otherwise, how do I increase logging if needed. For now I found the problem by consulting the mailman.log. Yes, that’s correct. Just use smtp.log. Cheers, -Barry

9 years

[MM3-users] Re: How to get Mailman core to provide more debug info in a running environment

by Mark Sapiro

On 09/29/2017 04:38 AM, Henrik Rasmussen wrote: > > how do I increase logging if needed. You can get more logging by changing the level. The default level for most loggers is 'info', but you can set it to 'debug' with an override like [logging.template] level: debug or for a specific logger, e.g. [logging.smtp] level: debug -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: Templates

by Mark Sapiro

On 09/29/2017 01:33 PM, David Krantz wrote: > On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is clearly a bug and should be fixed. If you report this issue at >> <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. > > I'll do that. @gazorg beat you to it. See <https://gitlab.com/mailman/mailman/issues/407> and feel free to comment there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] default language ignored

by Marc Sluiter

Hi, one last question for now: how do switch the language of the mails sent by mailman? I have this in my configuration, but without effect: [language.de] charset: iso-8859-1 [language.de] description: German [language.de] enabled: yes [mailman] default_language: de Is it also possible to change the language for a single list? Greetings, Marc

9 years

[MM3-users] Disabling max_message_size and send_welcome/goodbye_msg globally or by API

by Peter Mueller

Hello, is it possible to turn off max_message_size and send_welcome_msg / send_goodbye_msg globally? If there are no global options, how can I turn off these feature using the REST API? In python you can do it with >>> mlist.max_message_size = 0. If I send a PATCH request to lists/some@list/config with body max_message_size=0, I get "Unknown attribute". Same for send_welcome_msg and send_goodbye_msg. Thank you! P.M.

8 years, 11 months

[MM3-users] Mails from Django are not sent

by Bjoern Franke

Hi, I'm using the "mailman-suite" setup for Postorious and Hyperkitty. I've set EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' in settings.py, but no mails are sent. Files with the e-mails are in the emails folder, but nothing happens, also no errors regarding emails are logged. Postfix as MTA can be connected via localhost:25 and e.g. mailman-core can use it fine. What can I do for further debugging? Kind regards Bjoern Franke

8 years, 11 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Mark Sapiro

On 10/18/2017 09:00 AM, Dmitry Makovey wrote: > > It seems like mailman-core is still operating properly, but for some > reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? I'm not very well versed in the docker images, but I think mailman-web uses uWsgi and sending the uwsgi process a SIGHUP should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Mailman installation results in KeyError: 'env_py'

by Mark Sapiro

On 10/22/2017 03:40 AM, Marvin Gülker wrote: > Hi, > > I'm trying to install Mailman 3 on Debian 9. However, it doesn't > let me do. ... > KeyError: 'env_py' > ~~~~~~~~~~~~~ This is the issue reported at <https://gitlab.com/mailman/mailman/issues/423>. It is caused by a change in Alembic 0.9.6. If you downgrade Alembic to 0.9.5, it will work, or you can install the fix at <https://gitlab.com/mailman/mailman/commit/24f2439aeabb5919d387d84aa9f66b5d7…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] scheduled tasks in docker-based deployments

by Dmitry Makovey

I came across the section http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required that claims that crontab entries are *required* for normal MM3 operations, but I do not see anything like that in docker-based implementation. Should I add similar cron jobs manually to the host box? -- Sr System and DevOps Engineer SoM IRT

8 years, 11 months

[MM3-users] Re: Moderating posts via email

by Dmitry Makovey

On 10/26/2017 02:59 PM, Abhilash Raj wrote: > Given how emails are not so good at being secret, I'd not advise using > it despite it's current state. Although, if it is a feature, it should > work regardless! agreed. but how do I strip that from the message sent to user since instructions are hardcoded into chains/hold.py ? -- Sr System and DevOps Engineer SoM IRT

8 years, 11 months

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

by Mark Sapiro

On 10/26/2017 06:44 PM, Abhilash Raj wrote: > > 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. If that's the issue, it's <https://gitlab.com/mailman/mailman/issues/401> and the fix is in this MR <https://gitlab.com/mailman/mailman/merge_requests/323>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

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

by Simon Hanna

On 10/27/2017 04:58 PM, Andrew Hodder wrote: > Sure thing: > > https://imgur.com/a/EXv3B > Looks like your stylesheets aren't loaded. if you are running in production (with DEBUG=False) django won't serve static files You need to configure your webserver to do that. You need to make sure to load all the static files using `python manage.py collectstatic` to gather everything and put them in one directory that can then be served by your webserver

8 years, 11 months

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

by Mark Sapiro

On 11/03/2017 08:29 AM, Fabian A. Santiago wrote: > > I've noticed that even simply restarting the mm3 components those alias maps get rewritten and the problem returns until I can manually edit it. I don't know how this works in the docker container or what you mean by "restarting the mm3 components". I do know that bin/mailman {stop|start|restart|reopen} does not rebuild the postfix maps. Only bin/mailman aliases or creating|deleting a list does that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 10 months

[MM3-users] Bounces

by David Krantz

Hi. How do I config mailman 3.1x to send any unrecognized bounces to e.g. the list owner? Now they just end up in the bounces table but I would like to see the entire message in this case. Cheers // David

8 years, 10 months

[MM3-users] Unknown attribute: max_message_size

by Thor Atle Rustad

If I make changes here: https://example.com/postorius/lists/test2.example.com/settings/message_acce…, I get a warning that the Maximum Message Size field at the bottom is mandatory. However, if I put a number in that field and save, I get "Unknown attribute: max_message_size". That makes sense, since Mark states in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… that max_messages_size is not exposed in REST. What to do? I have Maxking mailman-docker but can easily copy files into the image if necessary. Thor

8 years, 9 months

[MM3-users] Re: help for new installation.

by claudio.jofre＠yandex.com

Hi: thanks for your help. I find the docker proposal interesting. I'm trying to follow it, according to the documentation they sent. I only have two doubts left until now. First: where I find the file docker-compose.yaml, I could not find it anywhere. (Install the docker and docker-compose using yum and using the epel repositories. second: How do I access the mailman configuration files inside the docker? Is there any way to mount it? as a unit, to make the modifications?

8 years, 9 months

[MM3-users] Re: Postorius: Show only own lists

by Mark Sapiro

On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > What I called "local admin" should have > rights to add and remove members of, say, the poodle-regionA mailing list. By "local admin", do you mean "list owner", i.e., a list owner should be able to see her own "hidden" lists. Is that what you mean, or to you envision some new category of user that has more access than a list owner? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] Re: Where is postorius.wsgi?

by Peter Münster

On Fri, Jan 26 2018, Peter Münster wrote: > ImportError: No module named settings Ok, I've found the solution: In wsgi.py: import sys sys.path.append('/srv/www/htdocs/ckc3r/postorius/example_project') But now, I get another error: File "/usr/lib/python2.7/site-packages/postorius-1.1.2-py2.7.egg/postorius/views/rest.py", line 33, in <module> from django_mailman3.lib.scrub import Scrubber File "/usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py", line 26, in <module> from email.message import EmailMessage ImportError: cannot import name EmailMessage What should I do please? TIA, -- Peter

8 years, 8 months

[MM3-users] Re: list of subscribers

by Peter Münster

On Tue, Feb 06 2018, Simon Hanna wrote: >> user = User.objects.get(email = ...) >> if user is found then >> print next to email address: user.first_name + user.last_name >> > Yeah, that way you make quite a lot of database queries. Is this a problem? Let's say, only moderators can see such a list. And I guess, that they won't do it so often, that the server crashes... Could you please show me, where I should add these 3 lines, so that I can patch my local mailman installation? TIA, -- Peter

8 years, 7 months

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

by Mark Sapiro

On 02/21/2018 05:00 AM, Henrik Rasmussen wrote: > Does Mailman 3 have something similar to https://www.msapiro.net/scripts/last_post.py displaying the last post time for a list or all lists? It wouldn't be difficult to do, but at the moment, it wouldn't provide anything useful because of <https://gitlab.com/mailman/mailman/issues/453>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: disable sign-ups

by Peter Münster

On Wed, Jan 31 2018, Simon Hanna wrote: > Not sure how this error happens. You might want to ask the allauth guys about > that... It seems, that I need to create an application: https://github.com/pennersr/django-allauth/issues/1939 Unfortunately, I don't know, how to do that... > You probably don't want to display the signup link in the first place. No, I want the link, and display some information when the user follows it. -- Peter

8 years, 6 months

[MM3-users] Templates and docker-mailman

by jwhathaway＠locklaw.com

I have mailman installed through docker-mailman and I'm trying to get rid of the footer decoration in our messages. Based on earlier threads, I have placed an empty file on the host running Docker at: /opt/mailman/core/var/templates/site/en/list:member:generic:footer But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do?

8 years, 6 months

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

by Chris McMacken

Thanks for the prompt response. Why does the application store messages on the local disk? 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?

8 years, 6 months

[MM3-users] Mailman 3 Installation Assistance

by brian＠emwd.com

I am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server: https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/ I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell: curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; Connection refused I assume this has something to do with uwsgi which I have no experience with. Appreciate any assistance with getting Mailman 3 up and running. Thanks! Brian Carpenter

8 years, 6 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

So it looks like no database was setup. My understand is the docker installation does that: The default compose file do these things: Run a wsgi server using [uwsgi](https://uwsgi-docs.readthedocs.io/en/latest/) for the Mailman's Django based web frontend listening on http://172.19.199.3:8000/ . It will run 2 worker processes with 4 threads each. Run a PostgreSQL server with a default database, username and password as mentioned in the docker-compose.yaml . Run mailman-core listening an LMTP server at http://172.19.199.2:8024/ for messages from MTA.

8 years, 6 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

Ok I just discovered the docker-compose-mysql.yaml file. I assume I can just use that file: docker-compose-mysql -d Is that correct? Do I need to remove the previous docker installation that I did using docker-compose.yaml? Sorry for being so needy. This is the 2nd time I am installing an application using Docker. The first one was Discourse which had really good installation instructions. I am struggling with the instructions for Mailman 3 via Docker.

8 years, 6 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

I bet it has something to do with selinux being enabled. I am disabling it now and rebooting the server.

8 years, 5 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

I have posted the error on Github. Did you see anything wrong with my docker-compose.yaml file? I also have another question. For the HYPERKITTY_API_KEY setting, is there an API key I need to generate and retrieve from somewhere or do I just make one up? Thanks, Brian

8 years, 5 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

Is there a way to get this new release and how do I update the existing one with it? Another question: Should I update the following settings with my own custom ones? POSTGRES_DB: mailmandb POSTGRES_USER: mailman POSTGRES_PASSWORD: mailmanpass Or does the docker installation configure those automatically?

8 years, 5 months

[MM3-users] Re: Disabling Gravatar

by Stephen J. Turnbull

Daniel writes: > I meant that it is against RFCs to use this IP address range in the real > internet. It's also against RFC 5737 to use it locally: it should *never* resolve to a real host. So if the purpose is to substitute a non-working address, this would do (especially if you implement the RFC's suggested restriction that it be filtered locally, but packets to that addressed should be rejected, not discarded by such a filter). On the other hand, if Marvin wants to implement a GDPR and Gravatar- compatible server, he should use a private address outside of the reserved ranges listed in RFC 5737. Steve

8 years, 5 months

[MM3-users] Attachments

by Darren Smith

Guys, Is there a setting to disallow attachments in mailman3? Doing a cursory search I can't find it.

8 years, 3 months

[MM3-users] Re: Attachments

by Simon Hanna

On 06/06/2018 05:16 PM, Darren Smith wrote: > Guys, > > Is there a setting to disallow attachments in mailman3? Doing a cursory > search I can't find it. > AFAIK you can't forbid attachments, but you can set a maximum message size.

8 years, 3 months

[MM3-users] Re: Attachments

by Mark Sapiro

On 06/06/2018 08:16 AM, Darren Smith wrote: > > Is there a setting to disallow attachments in mailman3? Doing a cursory > search I can't find it. It's content filtering and it works the same in Mailman 3 as in Mailman 2.1. See <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filtering…>. The issue is that the list settings pass_types, filter_types, pass_extensions and filter_extensions are not exposed in Postorius. A few of the settings are exposed on the List Settings -> Alter Messages view, but not those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Is there a reason not to implement the config_list command ?

by Asaf Ohayon

Hello Is it meant to be implemented ? and if so, how is it recommended to do (for someone new to mailman 3 programming) Thanks

8 years, 3 months

[MM3-users] Pre-approved howto

by thor.rustad＠gmail.com

I have tried to understand the concept of pre-approved messages, but I'm spending way too much trying to figure it out. Help! The scenario is as follows: Mailman installation with hundreds of lists. Each list's owner is only supposed to add/remove members, so approving/rejecting messages is not in the "job description". Then we have a small group of superusers who will be the ones sending documents etc to all 800 lists. The superusers should be able to do so without being stopped by size limits etc. How can I achieve this? ---- Thor Atle Rustad ----

8 years, 2 months

[MM3-users] Re: Announcing Mailman Suite 3.2 release

by Alexander Klotz

Am 11.07.18 um 08:50 schrieb Abhilash Raj: > I am very pleased to announce the release of Mailman Suite 3.2.23 Dear Abhilash, great! Thanks a lot to you and everyone involved! Is it already possible to install the latest version? We tried doing so in the docker by changing the tag of the image from 0.1 to 0.2, but that doesn't seem to work. Or are we just a bit too impatient? ;) Thanks & Regards, Alex Klotz (CultureBase editorial staff)

8 years, 2 months

[MM3-users] Re: Mailman3 Issue

by Mark Sapiro

On 7/12/18 10:56 AM, jon.kokko(a)us.fujitsu.com wrote: > I'm experiencing the same error on a clean install. The issue in the OP appears to be leading whitespace in the domain name. If you go to <https://example.com/postorius/domains/>, what do you see? Can you edit the domain? Does it contain leading whitespace? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] receiving digest

by Abhijith PA

Hello. How a subscriber can receive the digest of a list ( assuming the list has enabled digests. Is there something to do for a subscriber in web interface to receive. Abhijith

8 years, 1 month

[MM3-users] Re: receiving digest

by Mark Sapiro

On 08/14/2018 07:24 AM, Abhijith PA via Mailman-users wrote: > > How a subscriber can receive the digest of a list ( assuming the list > has enabled digests. Is there something to do for a subscriber in web > interface to receive. The user can log in to Postorius and in the pull-down list at the right of the nav-bar (from the user's name) select Mailman Settings From there the user can select Delivery Mode for any of Global, Address based or List based preferences. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] changing adverstised status

by Alexander Klotz

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? Thanks & Regards, Alex (Kulturserver editorial staff)

8 years, 1 month

[MM3-users] Re: Configuration Question

by Abhilash Raj

On Thu, Aug 23, 2018, at 12:08 PM, Ryan McClung wrote: > Greetings, > > Is there a simple way to force the mailman3 install to run off of a > specified config/specified db without having to enter it manually each > time? > > I just want any administrator to be able to enter mailman without wrecking > the config/db. What do you mean by "enter Mailman"? -- thanks, Abhilash Raj (maxking)

8 years, 1 month

[MM3-users] ARC

by David Krantz

Hi, I just found out that gmail uses ARC (sometimes, at least). Is there support for that in Mailman 3? Without having had the time (yet) to read about in depth it it seems as if ARC is intended to solve at least some of the problems that mail lists have with DKIM. Probably causes others... It might be that no support really is needed in mailman so that just milters in sendmail, postfix etc. might do the trick. regards // David

8 years, 1 month

[MM3-users] Re: Avoiding the List name in TO or CC headers

by Mark Sapiro

On 08/27/2018 06:06 AM, Asaf Ohayon wrote: > > I've made a list personalized ( =2 in mailinglist table), > So in TO: I see the actual member, > But still I have the list address in CC header, > Can this be removed ? No. It is placed in Cc: to facilitate replies to the list. To not do this you would need to modify mailman/handlers/cook_headers.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] How to connect mailman into existing postfix server

by Hagen Bauer

Hi to all, I am trying to setup mailman3 with the Docker Image. Everythings works relative nicely but I am blocked by the Postfix integration part. I have a small postfix server that is delivering mails to known domains and an alias map. The standard use case assumes that the external postfix is only routing mails to the mailman lmtp. If I do this all my old users are recected. I am looking for an example(s) to integrate mailman into a Postfix configuration as an additional target for postfix. Any hints Regards Hagen

8 years

[MM3-users] Re: New platform administrators

by Simon Hanna

On 9/18/18 5:42 PM, Hellen Cubero wrote: > Hello! > I would like to know how to add a new site administrator to the mailman 3.2 > platform. Can you help me please? You are probably referring to Postorius the webui? If yes, you just add another superuser. If the admin is enabled, you can just visit https://you-url/admin sign in, and create a new user with staff and superuser permissions. You can also do that on the cli using ./manage.py createsuperuser There currently is no "siteadmin" that can only create/edit domains. You either have all the powers or none :-)

8 years

[MM3-users] Disable "confirmation emails"

by Hagen Bauer

Hi to all, even after a lot of google search I could not find a way to disable the Confirmation Mails like .... The results of your email command are provided below. - Original message details: ....... Is there a way to do this? I have users who would be irritated and I dont want them to recieve this Regards Hagen

8 years

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

by leith＠khimaira.com

I apologize for posting to the wrong forum. I didn't realize cPanel's mailman 2.1.26 was somewhat behind. I do appreciate your assistance and will followup if necessary on the correct forum.

8 years

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Mark Sapiro wrote: > On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > > 2) How do I change the default for existing lists > > Postorius -> Settings -> Digest Sorry, I was unclear here. I was aware of changing the size in the web interface, but what I meant was changing the Digest Size Threshold value for all lists using REST API. Is that possible? -- Henrik Rasmussen

8 years

[MM3-users] how to integrate subscription into static jekyll website

by Hagen Bauer

Hi, I am running a static website with jekyll and I want to integrate a form that executes a subription rest api call to mailman. From my first investigation this seems to be a bad idea from a security perspective (rest api needs managaer access). Is there a secure way to do this? Any other ideas? Regards Hagen

7 years, 11 months

[MM3-users] Mailman 3 on RHEL 7 help

by A Almeda

Hi. I am trying to install mailman 3 on RHEL7. Docker install is not a possibility. I am trying to install it using a bundler by following https://media.readthedocs.org/pdf/mailman-bundler/stable/mailman-bundler.pdf, but after logging in as mailman, I can't do virtualenv venv. It works if I login as root, but still fails during buildout. In short, I need help. Has anyone of you guys installed mailman 3 on RHEL 7 or CEntOS 7? If so would you share me detailed instructions? Thank you in advance.

7 years, 11 months

[MM3-users] Re: Hyperkitty Archives - Sidebar years/months

by Enrique Terrazas

Thank you Mark I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: /bin/sh: django-admin: command not found If I run: django-admin --help I get the following: Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). I'm not sure how to go about correcting this. Thank you, Enrique

7 years, 10 months

[MM3-users] Rerun emails in the queue/bad

by Kaleb White

How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks.

7 years, 10 months

[MM3-users] Re: Verification Failed Error

by brian＠emwd.com

I am using Exim as the MTA. I followed the instructions located at: https://github.com/maxking/docker-mailman In particular the "Setting up your MTA" Are you saying I need to do something with Django because your documentation at github makes no reference to that? Where would I find the settings.py file? I used your image to install Mailman3. FYI I am referencing the "# To be added to Django's settings.py" instructions at http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required

7 years, 9 months

[MM3-users] Re: Verification Failed Error

by brian＠emwd.com

Thanks. I removed the following from /opt/mailman/web/settings_local.py: EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password> Do I need to restart mailman and if yes how?> Thanks again, Brian

7 years, 9 months

[MM3-users] Re: Verification Failed Error

by brian＠emwd.com

Abhilash Raj wrote: > Yes, you do need to restart mailman-web container. > > $ docker-compose restart mailman-web When I added the following to /opt/mailman/web/settings_local.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 I got network not found error message in the log file when I tried to reset my password. Should EMAIL_HOST be something else besides localhost?

7 years, 9 months

[MM3-users] timezone in hyperkitty

by erlonmz＠hotmail.com

How do I change the hyperkitty timezone?

7 years, 9 months

Search results for query "dO"