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

[MM3-users] Re: Mailman3-Web lots of database queries

by Abhilash Raj

On Thu, Nov 22, 2018, at 2:14 AM, Stefan Tatschner wrote: > On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > > No. This is not normal. This is apparently coming from Django qcluster. > > At least it is qcluster that uses the django_q_ormq table, but these > > repeated queries are not normal, at least I don't see them in the sites > > I administer. > > These calls are normal, since qcluster polls the database at a high > rate: > > https://django-q.readthedocs.io/en/latest/configure.html#poll > > Fortunately this setting can be reduced, but yeah, polling happens > though. So, if you are using Django's ORM to keep the task states in Django Q, this is bound to happen depending on how frequently do you run tasks. In Hyperkitty, we have some minutely tasks, which means the polling is going to be high. You can however, configure Django Q to store the tasks outside of database in a better high-speed in-memory database like Redis for example[1] for queuing the tasks. Other options like MongoDB, Amazon SQS is also available. [1]: https://django-q.readthedocs.io/en/latest/configure.html#redis > > Stefan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Separating Lists by Domain

by Abhilash Raj

On Sun, Dec 23, 2018, at 4:42 PM, brian(a)emwd.com wrote: > I have successfully setup a second domain with my Mailman3 setup. I > also created a list using the second domain. So I have two domains with > one list each. The issue I see at this point is all of the lists are > shown via Postorius regardless of the list domain used. Is it possible > to have only the lists to show that are part of the domain being used > to access? For example: > > http://domaina.com/postorius/lists/ > > Only listnames(a)domaina.com show up. > > http://domainb.com/postorius/lists/ > Only listnames(a)domainb.com show up. > > Right now both domaina AND domainb lists showup regardless of the > domain being used to access Postorius. The same goes for Hyperkitty as > well. You can do that this in Hyperkitty. Setting FILTER_VHOSTS = True in Django's settings.py (or settings_local.py, if you are using container images) will filter the lists for the current "Host:" header in the request. Postorius doesn't have this ability yet, but wouldn't be too much work to add that. Pull requests are welcome :) > > Brian > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Migrating Mailman 3 lists

by Andrew Hodgson

Brian Carpenter wrote: >I know how to migrate mailman 2 lists to a new mailman 3 server. However I do not know how to migrate a mailman 3 list from one mailman 3 server to another one. Are there any instructions or protocol on how to accomplish this? >The Mailman 3 server I want to migrate *from* was setup using Docker. The Mailman 3 server I want to migrate these lists *to* was setup using a python virtual environment via pip. I did this the other week, the difference I think we've got here is that I migrated the whole instance (Mailman Core's var files plus complete Postgresql database) over to the new server rather than trying to add the lists to an existing setup, which I couldn't work out either which is what prompted me to complete the server migration before adding more lists. The only issue I ran into was not copying the Mailman Core var files to the new server, this actually gave me a bit of trouble later on as firstly Mailman doesn't create the lists directory which is what I was checking with Exim for list existence, and also I had an issue where I was missing a moderated message from the messages directory which stopped the admin interface from displaying for that list. However if anything would help on my experience would be happy to share more info. Andrew.

5 years, 3 months

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

by Henrik Rasmussen

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

8 years

[MM3-users] Re: ARC signing outgoing mails

by Mark Sapiro

On 11/1/19 4:04 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > in > https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign… > I found this hint > > "It is highly recommended that Mailman maintainers configure ARC siging > of their outgoing email. ..." > > So I added in my mailman.cfg: > " > [ARC] > privkey: /path/to/private.key > " > > > But I don't understand the meaning of > > > "... and located at: > " > #{config.ARC.selector}._domainkeys.#{config.ARC.domain} –ex.– > test._domainkeys.example.com > " This doesn't seem correct. The DNS TXT record should be added to #{config.ARC.selector}._domainkey.#{config.ARC.domain} (note _domainkey, not _domainkeys) I.e., this is a normal DNS TXT record containing the public key for DKIM signing. > Where can I find this string or where do I have to place it. I am using > bind9 as dns-handler. Read the entire ARC section beginning at <https://gitlab.com/mailman/mailman/blob/master/src/mailman/config/schema.cf…>. You have to configure more than just privkey. Once you have configured enabled: yes privkey: /some/location/yourprivatekey.pem selector: test (or whatever you want) domain: your_domain.com The substitutions for #{config.ARC.selector} and #{config.ARC.domain} should be more clear. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Dadgar

On Feb 15, 2021, at 10:14 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. >> >> The resulted in a broken web interface. >> >> Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. >> >> Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. >> >> Anyone got a solution to this? > > > From the tracebacks it looks like Django is broken. I would suggest > starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ > aside and create a new venv > > virtualenv /opt/mailman/mm/venv/ > > and then activate it and pip install everything. Ok, that worked. THANK YOU. My lists are back up. The CPUs getting pounded by some failing process is back, though. I’ll post about that separately. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 5 months

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

by Kimmo L

Hi Stephen! Thanks for trying to help me out! > > That's an unfamiliar format to me. Is this a Linux system running > systemd? Our mailman + hyperkitty runs on RHEL 8 and yes, all the services are systemd format. > How much swap do you have, and how much is in use? > What other daemons are running on the host besides Mailman? Host has 8GB swap at the moment ,which decreases in small steps if main memory is consumed. But if this happens, then something happens and there is again couple of hundreds free memory. In addition to the above mentioned services, there is also NGINX and postfix services as well. > Have you modified any web pages associated with Mailman, including any > of the Django templates? Are there any pages with unusually long load > times? No and usually all pages are very smooth. Only if i open archives, then sometimes it will load like sec or three. I also noticed that after midnight, if one of the mailman-web cronjob was finished, the free memory jumped from 100mb to 1gb. And then it will start to decrease again. I will try to investigate little bit more and play little bit with the services to be sure, that the issue is related with mailman or gunicorn or with something else.

2 years, 11 months

[MM3-users] Upgrading a Ubuntu Mailman 3 Installation

by Allan Hansen

Dear Mailman 3 wizards, Several years ago I tried upgrading to Mailman 3 (I did install Mailman 2), but quickly ran into a thicket too complex for me to get out of. Two others - way more experienced than me at system-level manipulations - tried as well but did not succeed. Brian Carpenter of EMWD installed the system seemingly effortlessly, and seemingly overnight. We had a good relationship, and I was a beta site for his new product, SAAS. Brian also did the system MM3 upgrades as they appeared and would check that all was well a couple of times a year. Unfortunately, and I respect that, the current management at EMWD "don't provide working hands service for foreign Mailman 3 installations." I do not dare touch it, based on my earlier attempts with the installation. With Brian's passing I'm thus faced with a system that has no capable system support (I manage the lists, not the core). I have 50+ lists with 10000+ subscription total, and a lot of people depend on this tool. (It's a non-profit organization). So, I'm interesting in hiring someone for part-time, occasional work (a few times a year). Update MM3 as new versions are made available. Diagnose and fix the system if anything goes awry. I will pay you, as I did Brian, out of my own pocket, for your time. Yours, Allan Hansen

2 years, 8 months

[MM3-users] Re: Must every Moderator/Admin be member of a list to be able to use Postorius?

by Mark Sapiro

On 1/31/23 10:25, mm3-omf(a)sh.werbittewas.de wrote: > we're using debian/devuan with distribution-mailman3 and tried to add > admin/mod for a list, but if logging in as this user, there's no item to > manage the list at all. That's strange. If the logged in user is a moderator she should see the Subscription requests and Held messages tabs and with Postorius >= 1.3.9b1 also the Members tab, and if she is an owner she should see the full admin UI without needing to be a member. Are you sure the logged in user is the same user that's an owner/moderator? Log in as a superuser and find the user in the User's view fron the top nav bar in Postorius, click Manage to see all that user's roles and web account. > do we have to add this user as member of this list? > (that wouldn't be nice, because the user doesn't want to get normal > Mails from List, but only admin-Mails) It shouldn't be necessary, but a delivery can always be disabled for a member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- 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: bounces with empty message-id

by Peter Münster

On Wed, Jan 31 2018, Mark Sapiro wrote: >> I have verp_delivery_interval = 10 ... > > Which says only every 10th message will be VERPed. You want > verp_delivery_interval = 1 to VERP every message. Hi, Why? The smtp relay host would get much more outgoing messages. With verp_delivery_interval = 10, only 10% of the messages would be personalized. Shouldn't this be enough to detect sooner or later, that a recipient address is no more valid? Or is it important, to detect such failure immediately? > The message does appear in the mail log, but until the issues below are > fixed, even if Mailman receives it, you won't see it. Ok. For now, I could do a grep of the syslog messages of Postfix, for example once per month, to check for DSNs. > They should be processed by Mailman and scored as bounces for the > recipient if recognized and forwarded if not (depending on settings), > but they currently are only stored. Ok. >> The question for me is: does the remote MTA needs a fix (i.e. the >> Message-ID is required by some RFC), or mailman (i.e. a DSN without >> Message-ID should be acceptable)? > > I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. Thanks! That means, that I won't need to teach Postfix to add a Message-ID to the DSNs. :) Kind regards, -- Peter

7 years, 6 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/9/21 4:05 PM, Duane Raymond wrote: >> As I said there, Mailman is going through the roster of regular >> (non-digest) list members to find those with delivery enabled and it >> finds a member that has no associated address. Can you view the members >> of this list? > > Yes - the list has three members (test list): me and two others. For my subscription I have gone through the membership options and explicitly set them. For the others their membership options are all unselected and thus I assume defaulting to a fallback value. (not sure if that matters) What matters is at least one of those members doesn't have an associated address record. If you have access to `mailman shell` do the following: mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... And see what that gives you. (At the last ... prompt just type `enter`) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

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

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210530 09:19]: > Mark Sapiro writes: > > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > > > Membership adapter is a Mailman 2 feature that allowed use of an > > > external membership database (such as a corporate LDAP system). I > > > thought it was ported to Mailman 3 but maybe not. > > > Actually, it's not quite that simple. Mailman 2.1 defines a > > MemberAdaptor class, [...]. > > The Mailman 3 analog of this is the IMember interface defined in > > mailman/interfaces/member.py and implemented in mailman/model/member.py > > OK, but for Andi it is "simple" in the sense that he doesn't have an > existing MemberAdapter, so the plan is "Implement the IMember interface". Not sure if this is the right approach, or if it wouldn't be more appropriate to "just" replace the dependency on allauth in postorius, and do all the magic in the frontend only (because that's where people actually subscribe). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands. That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not? Andi

4 years, 2 months

[MM3-users] Hyperkitty django.request forbidden

by Stephen J. Turnbull

Arpad Horvath via Mailman-users writes: > I moved from mailman to mailman3 in 2021. I hadn't have the time to > fix the archiving. I can see the emails older then that in > Hyperkitty, but none of the once still there is mailman3. What can > be the problem? I don't understand "none of the once still there is mailman3". Do you mean none of the emails sent since the upgrade from Mailman 2 to Mailman 3 are not visible in HyperKitty? > It's a Debian 12, I use the packages from the repo. > ERROR 2025-02-26 06:47:31,705 861 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP xxx.xxx.xxx.xxx, your MAILMAN_ARCHIVER_FROM setting may be misconfigured [...] > I have this line in /etc/mailman3/mailman-web.py > > MAILMAN_ARCHIVER_FROM = ('https://lists.somewhere.xx/hyperkitty', '::1') Where did that line come from? Did you put it there? If so, don't worry about it, we'll figure out what goes there. If not, investigate a bit and if it seems like it came from debconf, you may want to report an issue to Debian. I think Django is failing to parse that. It expects hosts, not URLs. The default is: MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') I would just comment out that line in mailman-web.py and restart. If it starts working, then I suggest removing it entirely. Steve

5 months

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

by Thor Atle Rustad

2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> Imagine an installation with 500+ mailing lists and almost as many local >> admins that are supposed to maintain their own local lists with a few >> local >> members. As site admin, I see all 500+ lists, but I was expecting *local* >> admins to see only the lists they maintain. I have set all lists to >> "advertised = False", so they are hidden from ordinary view. Is there a >> way >> to show only relevant lists to local admins? >> > Are we talking about Postorius or Hyperkitty? > There is no way for users that do not have the django superuser permission, > to see unadvertised lists in the Postorius list index. I just > doublechecked the source. > There is an issue about list filtering/search for the index page. > I believe I wrote Postorius in the subject line, but it may not be so obvious. So yes, in Posterius I would like to hide the lists from email harvesters, while relatively "untrusted" admins should have access to basic operations on the one list he/she "owns" (and without having to browse through 50 pages of mailing lists). Somehow I don't think 500 superusers in our system is a good idea!

7 years, 6 months

[MM3-users] Re: Running Mailman3 under supervisord

by Abhilash Raj

On Mon, Jul 27, 2020, at 9:49 AM, Odhiambo Washington wrote: > > > On Mon, 27 Jul 2020 at 18:38, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> >> On Sun, Jul 26, 2020, at 6:08 AM, Odhiambo Washington wrote: >> > Hello world, >> > >> > Is it possible to run MM3 under supervisord? >> > What would I use for command= ?? >> >> >> If you want something that doesn't fork into the background, then you can run "master start" command. It will stay in the front and supervisord can monitor the pid. >> >> I do the same for the container images. > > > Hi Abilash, > > Might you be able to share your how you have configured that all that in supervisord.conf? I don’t use supervisord, I simply run “master —force” in the container images. Container managers often negate the need to have supervisord. Edit: Sorry for the wrong command in the last email, it is simply “master” and I run with “—force” to skip any issues with locks that happens when the container is stopped faster than Core can shut down cleanly. For refernce https://github.com/maxking/docker-mailman/blob/master/core/Dockerfile#L31 Abhilash > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) -- thanks, Abhilash Raj (maxking)

5 years

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

by skenny＠scss.tcd.ie

I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? Thanks for any advice. Stephen PS: The Mailman web interface "System Information" link reports: Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0]

2 years, 10 months

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

by Alex Schuilenburg

We're migrating from 2.1 to 3.2.1 and an odd issue has popped up. It may be something different in the way mailman3 works, or a misconfiguration on my part. Most of the lists migrated so far don't have moderators, just owners. However, when these lists have messages requiring moderation, the owners dont get notified of held messages - unlike 2.1 where they did. Is this a change or is there something I am missing in the configuration? I have the minute/quarterly/hourly etc cron jobs running, although I have had to tune down the frequency of minute to hourly as it takes 6.5 minutes to run* - but I doubt this is the cause. While for the moment I have found the held messages in files in /var/lib/mailman3/messages and figured out which lists are in need of attention (and notified the owners), it seems I may have to do a bit of coding myself to walk through the lists and notify owners when their list is in need of attention. There must surely be something that does this already - or is this moderators only in mailman3? Guidance appreciated. Thanks -- Alex * From the list I realise this is because I am still using the default whoosh backend to haystack and need urgently to switch to xapian or solr, but the info on how to get this working for a noob like me is unfortunately lacking :-(

4 years, 9 months

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

by Mark Sapiro

On 3/17/22 12:25, Quanah Gibson-Mount wrote: > > I've done nothing in regard to this user. Neither command returns > anything. Well, something has deleted the user, but ... >> If the user is gone, you should be able to replace >> ``` >> ... sub_mgr.confirm(token) >> ``` >> in the above with >> ``` >> ... wfm = getUtility(IWorkflowStateManager) >> ... pendings.confirm(token, expunge=True) >> ... wfm.discard(token) >> ``` >> to clear the pending subscription and workflow and then be able to mass >> subscribe the user. > > I did this, and can confirm that they no longer show up in the list of > pending subscriptions via the mailman shell interface for that list. > > However, if I go to mass subscribe them via the interface, I get: > > HTTP Error 409: b'Subscription request already pending' I don't understand. If there is no entry for that address when you do ``` >>> for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['email'] != 'user(a)example.com': ... continue ... print(data['email']) ... ``` You should not be getting that 'Subscription request already pending' response. -- 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: running a script for the mailman-shell (to discard held messages) gives errors about a package argument for relative import

by Mark Sapiro

On 6/15/24 03:10, via Mailman-users wrote: > > 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 ... > TypeError: the 'package' argument is required to perform a relative import for './mm_discard_held' To run a script named mm_discard_held.py in that way, the script must define a function mm_discard held. The content needs to be something like ``` from mailman.app.moderator import handle_message from mailman.config import config from mailman.interfaces.action import Action from mailman.interfaces.request import IListRequests # The above are needed. These imports are done automatically when # running mailman shell interactively, but not when running a script. def mm_discard_held(mlist) rdb = IListRequests(mlist) for req in rdb.held_requests: if req.request_type == RequestType.held_message: config.db.commit() ``` See `mailman shell --details` > I've tried moving it to the path where the mailman binary lives, as suggested. That is what you should do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Mark Sapiro

On 4/13/20 3:22 AM, Andrew Hodgson wrote: > > I was working round my own backup strategy a few weeks ago as I discussed earlier on this list. One thing I found when the directory structure that Mailman Core uses is that the lists directories do not get re-created when Mailman Core starts if they don't already exist. Is this something that should happen, and when would those directories get created? Every other directory did get re-created. > > In my case I was moving from a Dockerised installation to one using venvs, and as the directories from the Docker installation were empty as there hadn't been any postings for a few days, I didn't transfer those over. I created the list directories myself and everything carried on. These var/lists/<list-id>/ directories hold the digest.mmdf files which are mailboxes containing the messages for the next digest. A list post will be added to the digest.mmdf file which will be created if necessary, but if the var/lists/<list-id>/ directory doesn't exist, the create will fail. Thus, the var/lists/<list-id>/ directories need to exist. Normally, they are created when the list is created so they need to be part of a backup. -- 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: Migrating to mailman-web and Ubuntu 22.04

by Andrew Hodgson

Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: >Andrew Hodgson via Mailman-users writes: > > I have instructions for Mailman-web for setting up Uwsgi but I > would prefer to keep Gunicorn working as per the instructions here: > > DOC/Mailman 3 installation experience - Mailman Wiki > (list.org)<https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > > > > Has anyone done this before? >I'm in the process of doing just that now. I'm not following that install exactly, but very closely, so far no problems. In particular, Apache to Gunicorn to Django and mailmanclient to Gunicorn to core are both working fine in light testing (we have a large number number of lists to migrate and a lot of >corporate QA to pass so things are going step-by-step). >Is there anything in particular you're worried about? I'm having trouble getting Gunicorn to see the Mailman-Web installation at mailman_web.wsgi:application. Note the installation documentation I linked to uses mailman-suite which is an older (deprecated?) method of getting the web interface hooked up. I'm trying to migrate to mailman-web so that I can take advantage of changes going forward with a simpler setup. I've potentially resolved to use Uwsgi for this and install another package which makes the installation more in line with this: https://docs.mailman3.org/en/latest/install/virtualenv.html Andrew.

2 years, 8 months

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

by Bill

Hi, All this is very helpful. Thank you. And it leads me to think about timelines. I'm aware that the freeze for Debian 9 (Stretch) is scheduled for the end of this year, and that we can expect it to be released sometime in mid-2017. (Don't quote me on that though ;) And I'm not sure about Centos, I didn't see a Mailman 3.0 package there or in Fedora. But is there any chance that a Mailman 3.0 or 3.1 package is going to make it into current release cycles? From what I can gather, we're very early to the table here, and nothing's going viral yet. As a Debian user, I certainly get the bit about "selling no wine before its time", so I completely understand long development cycles. But we're in the evaluation/design phase of this project and from the providers point of view it would be helpful to know if they should wait a few months for Mailman 3.0/3.1 or just go ahead now with 2.1.x and upgrade to 3.1 at some point down the road. While their list admins are experienced, they are new to Mailman and the fewer burps the better. Although they may very well take a run at 3.0 now and see how things work out. We just need some sort of timeline to consider. I'm not looking for firm dates of course, best guesstimates will do. Thanks, b.

9 years, 1 month

[MM3-users] Re: So near, and yet so far (Configuring Mailman)

by Jack Lenox

On 2021-01-29 19:52, Peter Chubb wrote: > On 30 January 2021 4:01:02 am LHDT, Jack Lenox via Mailman-users > <mailman-users(a)mailman3.org> wrote: >> Hello all, >> > >> >> This to me appears to be an issue with my DNS settings, but I can't >> work this out either. I have an A record for lists.fiftyshadesof.green >> pointing at my server, and an MX record pointing at that: >> >> lists.fiftyshadesof.green. 0 IN MX 0 >> lists.fiftyshadesof.green. >> lists.fiftyshadesof.green. 0 IN A 193.37.35.191 > > Why is the timeout on the names zero? > > When looking them up they'll always come up as expired and invalid. > > If you have static IP assignments I suggest setting the timeout to > 86400 rather than zero. If you're on a system that changes up address > more frequently, then 300 (five minutes) may be more appropriate. Thank you Pete, that's strange. The TTL is set to 86400 seconds. That might have just been a peculiarity of dig when I ran it. Good news everyone! I've got it working. It turns out my issue was with the mynetwork IP settings in my Postfix config. Things do now appear to be working. My only remaining issue is that the posts aren't appearing in the archive. Hmm.

4 years, 6 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/30/22 08:41, Jan Eden via Mailman-users wrote: > > Changing the PATH value to a full path (/opt/mailman/fulltext_index) > and restarting mailman-web generates a different error: Yes, it should be a full path. >> ERROR 2022-11-30 16:38:37,953 1028315 django.request Internal Server Error: /archives/list/testing@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest >> Traceback (most recent call last): >> File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner >> response = get_response(request) >> File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response >> response = wrapped_callback(request, *callback_args, **callback_kwargs) >> File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner >> return func(request, *args, **kwargs) >> File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 454, in reattach_suggest >> sugg_thread = msg.object.thread >> AttributeError: 'NoneType' object has no attribute 'thread' This says that searching the archive for this list for messages matching the current message subject returns None. It is probably a bug that we don't test for this, but what exactly are you doing? See the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for the only way I've been able to create an error like this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Hiding an ML from a site

by Odhiambo Washington

On Tue, Feb 6, 2024 at 2:22 PM Mark <imark(a)posteo.net> wrote: > > > On 2024-02-06 21:34, Odhiambo Washington wrote: > > I host two MLs on the same server/same MM3 instance. > > Under the Django Admin interface, I created two sites. I expected that > > each > > ML will belong to its own site and should not be visible on another > > site. > > On https://mm3-lists.kictanet.or.ke/mm/lists/, you can see the two > > lists. > > How do I stop the "Users" list from showing up on this site ( > > https://mm3-lists.kictanet.or.ke/mm/lists/) since it belongs to its own > > site - https://exim4u.org/mm/lists/ ? > > > In your settings file, add the line: FILTER_VHOST = True > > # Mailman Web configuration file. > # /etc/mailman3/settings.py > ... > #Filter visible Mailing Lists based on the current host being used to > serve. > FILTER_VHOST = True > I had this set to True in settings_local.py, but False in settings.py. So it seems to not make a difference in my setup. -- 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, 5 months

[MM3-users] Re: Strange URL in error message

by Mark Sapiro

On 7/17/24 11:47 PM, waps(a)tantalus.jena.thur.de wrote: > Hi Mark, > thanks for your patience. But now I get a little spinning wheel on the archive site, 3 "Error 500" in the Browser console and /var/log/mailman3/web/mailman-web.log shows repeatedly the error: > > ERROR 2024-07-18 08:34:38,261 1760 django.request Internal Server Error: /mailman3/hyperkitty/list/latex-team(a)latex-project.org/posted-to > Traceback (most recent call last): ...> File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > Since the archive is still quite empty and we have only one mailing lis, it would not be a big loss if it could resettet. But how I can do the, without resettinh the member data? Could it be that the Sqlite interface is not as stable as one the the "real databases"? As a superuser, you can go to /mailman3/hyperkitty/list/latex-team(a)latex-project.org/ and delete the archive. This will not delete the mailing list, and an empty archive will eventually be recreated, and new posts will be archived. Regarding the issue, see https://gitlab.com/mailman/hyperkitty/-/issues/504. Ensure that cron is running the Django hourly, daily, etc. tasks and that qcluster is running. -- 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: Archive import fails: "IndexError: list index out of range"

by Stephen J. Turnbull

Dan Caballero writes: > I've got a message that keeps getting re-queued to the > /hyperkitty/spool/ folder. [...] > "During handling of the above exception (expected atom at a start > of dot-atom-text but found > '[1db292f04b54496ab40544b0989a2122-JFBVALKQOJXWILKNK4YVA7CPNZSVMZLUPRCW2YLJNRKGK43UPRCXQ32TNV2HA===(a)microsoft.com]>')" This is arguably a HyperKitty bug. The email package is correctly refusing to parse that as a Message-ID (it's been illegal syntax since RFC 822 if I remember correctly), but something, presumably HyperKitty, should catch the error and do something to sanitize it to message-id syntax. On the other hand, I never heard of a message trigger that exception before a couple months ago, so maybe it's the responsibility of spam filters. I think when I ran into it, just moving it out of the HyperKitty archive queue fixed the queue. The client then put in a filter (it was indeed spam) in the MTA, and I haven't heard from them again. In a later post you say that message came back, but I suspect it isn't the same message, but a new one likely from the same source. I would say filter message-ids containing '[' either into /dev/null or a holding pen. Even Microsoft software knows how to generate syntacticly-valid message IDs, pretty sure that was not an @microsoft.com sender! Steve

1 year, 6 months

[MM3-users] Re: MM3 gateway errors and frequent reboot needs

by Brian Carpenter

On 4/19/20 4:38 PM, Mark Sapiro wrote: > On 4/19/20 1:21 PM, hansen(a)rc.org wrote: >> We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? > > We are not seeing an issue like this on either lists.mailman3.org (this > list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) > > What are you seeing in web server logs? > I concur with Mark. I am not seeing any such behavior on none of my MM3 servers. One server we were having similar problems and that was due to a bunch of bad behaving indexing bots (semrush, ahrefbot) hammering the server. So definitely check your web server log. -- 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/

5 years, 3 months

[MM3-users] Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 21, 2021, at 2:05 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: > > postorius, admin, hyperkitty and user-profile work now, accounts doesn't > > WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts > WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts > [pid: 3975|app: 0|req: 26/26] 127.0.0.1 () {56 vars in 1208 bytes} [Sat Aug 21 10:52:41 2021] GET /accounts => generated 5651 bytes in 433 msecs (H\ > TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) /accounts itself is going to 404, because it doesn’t point to a valid path. Can you try /accounts/login/ or /accounts/signup/? > > pid 3975 is /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini > > PS: now I seem to have done something stupid. I wanted to switch everything from example.com to the real domain. So I added it in admin and got rid of example.com. Seems there was some configuration missing, now nothing is working. How do I get everything back and have it use the right domain? There is a SITE_ID = 1 configuration somewhere in your settings.py, you need to replace that with SITE_ID = 2. Each Site is basically representing one domain, so you can service multiple sites from same setup by changing just the SITE_ID. Since you removed example.com with SITE_ID = 1, that would fail to find any domain with that id. -- thanks, Abhilash Raj (maxking)

3 years, 11 months

[MM3-users] Ansible role to install Mailman3

by Stephen J. Turnbull

samuel.d.darwin(a)gmail.com writes: > Would it make sense to mention these roles in the official > documentation? Not sure. I'm not sure either. Maybe a "contrib" section in the docs that we don't promise to maintain proactively. Of course we would respond to 3rd party information that URLs 404 or for some reason don't work in recent environments etc. You didn't request this, but as long as I'm here, I would resist trying to maintain an "official" set of roles for the Mailman suite and supporting packages. I've been in projects that try to do that[1] and it always ends in pain. The project just can't keep up with all the environments that want a piece of it, and then there would Chef users etc.... > Installing mailman3 is complicated and because of that, is a good > fit for Ansible. Agreed. It's just that my impression is that the technology is really better suited to meeting the needs of particular downstream users who know the configuration they want, than to the needs of the upstream project whose users demand flexibility. It would be an interesting test if people who prefer Postfix and Postgresql would try Ruth's roles and see if they can be slotted in as easily as she suspects. Thenk you for your input, and thanks to Ruth for her information. Steve

1 year, 11 months

[MM3-users] Installing mailman 3

by Rafael Mora

Hello, I want to install mailman 3 in a centos 7 virtual machine. I'm following these steps and I cannot make it work: 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` 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 (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 -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Question about "envelope-from" header

by Stephen Daniel

Mailman Gurus -- I run a small mailman3 implementation in a VM inside Google's cloud. The same VM runs both mailman3 and postfix. Because outbound SMTP is blocked by Google, my postfix relays outbound mail through smtp-relay.gmail.com, using credentials from my google workspace account. Works pretty well. For reasons unrelated to my mailing lists, I'd like to have the same VM provide a couple of mail aliases. Mail that comes in to " alias1(a)mydomain.com" should be relayed to "random1(a)somedomain.com". I am trying to do this by setting up virtual aliases in postfix, as per http://www.postfix.org/virtual.5.html. This works except that smtp-relay.gmail.com rejects the forwarded message because of "invalid credentials". I believe that email going out through smtp-relay.gmail.com can only come from a small set of previously authorized domains, and a random person who sends to "alias1(a)mydomain.com" is unlikely to be on that list. I think I could fix this by having postfix edit the "envelope-from" header as it relays the mail, so that the "envelope-from" header contains something like "admin(a)mydomain.com". Not sure, but I think so. My question is this: If I edit the envelope-from header in my outbound emails to say "admin(a)mydomain.com" am I going to break my email lists? Will bounce processing still work? Will replies to the list still work? Thanks! -- Stephen Daniel

1 year, 10 months

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

by Guillermo Hernandez (Oldno7)

On 7/8/21 13:55, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > Yesterday I had a problem with a private list. A spammer sent a mail > > forging one address that was a non-member (in fact was an "accept this > > no subscriber mails" from mailman 2.1 import) with very bad intentions > > and it was distributed. > > If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers > list for each list is grandfathered into the Mailman 3 list (from > rules/moderation.py): > > # Check the '*_these_nonmembers' properties first. XXX These are > # legacy attributes from MM2.1; their database type is 'pickle' and > # they should eventually get replaced. > for action_name in ('accept', 'hold', 'reject', 'discard'): > legacy_attribute_name = '{}_these_nonmembers'.format( > action_name) > > > There were no list of "accept this non members" in the Postorius > > config > > If there is no such list in Postorius, I would guess that some > developer thought "OK, this is a legacy feature and I'll get back to > it when we move it to the proper database" (unfortunate, but most of > us have open-subscription member-posts-only lists, and the current > workflow seems to work well, so this feature may not be so salient). > > > I think it is solved now (deleting all and putting to hold just the > > non-members addresses that I would want to pass messages on) > > This should not be necessary, unless there were pre-approved addresses > that are no longer appropriate. But Mailman can't know that! > > > The fact is that any sender address of mails sent to the list is saved > > as a "non member", and it make me nervous as it will grow despite it is > > a legitimate message or not. > > As far as I can see there is no other rule except that legacy rule > (and the rule that accepts all posts, which is rarely used) that will > accept a post from nonmembers. > > > Anybody knows if there is a per list config to avoid saving all that > > addresses as non members? o a overall config? > > No, there isn't, and there never will be. This is a basic design > decision about the representation of "people who participate in any > way in mailing lists". The only way to prevent creation of an Address > object for the sender of an email is to reject or discard the post (in > which case the "create an Address" path isn't entered), and don't set > a moderation action on the sender. Obviously if you set a moderation > action, that will create an Address in the database. > > The problem you encountered is not preventable by any means > whatsoever: a malicious actor discovered an address that is allowed to > post. The specific case you're worried about, that nonmembers will > automatically be allowed to post, is not possible. Well, as I couldn't locate which legacy accepted to post non-member addresses were permitted, I solved it deleting all of them (thanks again Mark) and adding via Postorius to the list of "hold these non-members messages" that I will examine and decide if it is a legitimate send. Thanks a lot for your detailed explanation. I can do better decisions now adjusting the configuration as needed. > The only way to > get on the list of "accept_these_nonmembers" is to be inherited from > accept_these_nonmembers on the parent Mailman 2 list, or an explicit > decision by a moderator. > > The fact that this list is not exposed in Postorius is a bug, but I > can't say when it might be fixed. It appears that the current process > (the moderator can set the sender's persistent moderation action > separately from approving or rejecting a particular post) works fine, > since this is the first time I've heard of this issue, and as you > present it, Mailman is doing the best it can since Somebody Authorized > put that sender on the approved list in Mailman 2. > > If a particular nonmember becomes a problem, you can access that > User or Address in Postorius and set them to Hold, Reject, or Discard. > > The process of deleting all nonmembers has been more difficult than it > should be, but this is being fixed, IIRC in the next release. > > Steve > --

3 years, 11 months

[MM3-users] Re: URLs in moderation messages

by Odhiambo Washington

On Fri, Mar 3, 2023 at 8:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/3/23 01:55, Tim Cutts wrote: > > > > I’ve clearly got something wrong in my configuration, but I can’t work > out what. > > > > All my URLs seem to have the “mailman3” part duplicated, i.e. > > > > Https://example.com/mailman3/mailman3/lists > > > > Is where I have to go to get a list of my mailing lists, which just > doesn’t seem right. > > > > In my settings.py file I have: > > > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com/mailman3/' > > > > If I change the value of this to just https://example.com/ it doesn’t > change this, > > > That setting has nothing to do with your issue. It only determines the > base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the > problem lies. See > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > for a suggested nginx config and > > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… > for Apache. > Are these proposed VirtualHost configs independent of whether one is using gunicorn/mod_wsgi/uwsgi? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is from the file /var/log/maillog: Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the Postfix mail system Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 25 03:30:05 localhost postfix/pickup[2785]: 03F4160D143F: uid=0 from=<root> Jul 25 03:30:05 localhost postfix/cleanup[3191]: 03F4160D143F: message-id=<20170725073005.03F4160D143F(a)localhost.localdomain> Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: from=<root(a)localhost.localdomain>, size=508, nrcpt=1 (queue active) Jul 25 03:30:05 localhost postfix/local[3195]: 03F4160D143F: to=<root(a)localhost.localdomain>, orig_to=<root>, relay=local, delay=0.11, delays=0.07/0.03/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox) Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: removed It seems that postfix is working, isn't it? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 1:31 PM, Mark Sapiro wrote: > On 2/14/21 5:44 AM, Tom Stoddard wrote: >> I'm a list owner who has recently (within the last week) had my lists >> migrated from mailman 2 to mailman 3. The UI that we are using is >> Affinity. > So you should be getting your support from EMWD. > > >> I've reviewed all of the list templates and begun to customize >> some of them. My issue is that I'm receiving messages that don't match >> any of the templates. Here is an example of one that I just received >> this morning. (The x's are inserted by me. The actual message provided >> valid addresses.) >> >> Thexxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. >> >> >> Held Subscriptions: >> User:xxxxxxxxxx@gmail.com >> >> Please attend to this at your earliest convenience. Yeah, the funny thing here Mark is he is not asking for support for the interface. He is wanting to know why isn't there a way for List Owners to modify moderation notices. It had nothing to do with Affinity. BTW - I told this client CLEARLY there was no template for that notification but he was welcome to join the list to ask for the source of it since I did not know. Geez. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Mark Sapiro

On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > Prasanth Nair writes: > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec can't > > encode character '\ufffd' in position 252: ordinal not in range(128).* ... > > I ran the check_hk_import script before migrating and it was not > > giving any error. > > In order to catch this kind of error, the check script would have to > pretty much do the import but throw it away. The check_hk_import script <https://www.msapiro.net/scripts/check_hk_import> is designed to detect and report conditions which would cause the django hyperkitty_import process to abort and stop processing the mbox. It doesn't catch errors like the above, but these are non-fatal and just cause the offending message to be skipped. As Steve says, the Message-ID was reported so find it in the mbox and if you want it in the archive, extract it from the mbox, fix it and then just rerun the import with just that message as input[1] and a --since=1970-01-01 option. Note the issue could be in a header, but also could be in a body part implicitly or explicitly declared as charset="us-ascii". -- 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: No DBA password when installing Mailman3 with remote database server

by Markus Ludwig Grandpré

> but apparently dpkg wants to > create databases for Mailman and Mailman Web. During the installation process dpkg creates not only a database and a database user with approriate permissions, but also many tables. Dpkg allows to skip database configuration. Is there routine or skript to create database, database user and all required tables after the installation process has finished? Best regards, Markus On 31.10.22 18:52, Mark Sapiro wrote: > On 10/31/22 07:04, Markus Ludwig Grandpré wrote: >> Dear Mailman3 list, >> >> I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system >> with a remote Postgres database server. During the installation >> process dpkg is asking for the DBA password that our DBA team would >> not provide to me. So what can I do? > > > This is really a question for Debian, but apparently dpkg wants to > create databases for Mailman and Mailman Web. You will need to get your > DBA team to create these databases (probably named `mailman` and > `mailmanweb`) and a Mailman user (probably `list`) with all access to > these databases and probably manually configure the `[database]` section > of mailman.cfg and `DATABASES` on Django's settings > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

2 years, 9 months

[MM3-users] Mailman 3 Privacy Policies, GDPR, etc and social logins

by Jered Floyd

Greetings, I host a variety of lists for social, community, and software projects, and updated my infrastructure from Mailman 2 to Mailman 3 last year. As part of this, I enabled Django allauth modules to simplify login and management for subscribers. Recently, Facebook notified me that they would be disabling the "application" because it failed to provide a sufficient Privacy Policy. Previously I had linked the app to [ https://www.gnu.org/software/mailman/privacy.html, | https://www.gnu.org/software/mailman/privacy.html, ] but they have said: Platform Terms 4.b: Your privacy policy must comply with applicable law and regulations and must accurately and clearly explain what data you are Processing, how you are Processing it, the purposes for which you are Processing it, and how Users may request deletion of that data. During testing, we found that your privacy policy doesn’t explain how users can request data deletion. Update your privacy policy to include this information before you submit an appeal. This is a bit of a headache. Do we have a draft of a community Privacy Policy for a vanilla Mailman 3 install that meets Facebook's requirements? Is this going to be a constantly unraveling thread of future GDPR and Right to Be Forgotten troubles, since there doesn't seem to be an easy way to scrub a subscriber from Hyperkitty archives if they request so? How have others addressed this situation? Regards, --Jered

1 year, 10 months

[MM3-users] Re: Importing mbox file into MM3

by Mark

On 2023-06-23 12:19, Mark Sapiro wrote: > On 6/22/23 7:00 PM, Mark wrote: >> Hi All >> >> I'm trying to import a large mbox file from a MM2 list into a new list >> on MM3. >> >> The new MM3 list has 3 test emails in its archive. >> ... >> The import or rebuild has failed as it's just rebuilding the existing >> archive of the 3 test messages. >> >> What am I doing wrong? > > > Presumably, the 3 test emails are newer than the messages in the > archive .mbox. The default for hyperkitty_import is to not import > messages older than the newest message in the existing archive. > You need to specify something like `--since='1970-01-01'` on the > hyperkitty_import command to import these older messages. > Thanks Mark. That looks more promising. It's been chugging away now for 3 hours with only 4 errors reported so far. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import --since='1970-01-01' -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox "Failed adding message ......(a)mail.yahoo.com>: A string literal cannot contain NUL (0x00) characters". The mbox file is about 3 GB. The errors look like they're for messages that aren't kosher (maybe misplaced "From"s in replies). I can live with a few missing messages. Back to watching the spinning pipe. Chug chug. Cheers Mark

2 years, 1 month

[MM3-users] Re: including a template failed

by Mark Sapiro

On 9/23/20 3:03 PM, Wolfgang Bock via Mailman-users wrote: > > Dear Mark, > > Q: Can you get > https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li > sts.domain-03.de/list:member:regular:footer on the Mailman machine? > > A: No > > Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? > > A: > was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' > > Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Can you get https://localhost/mailman3/postorius/api/templates/list/mylist.lists.domain… on the Mailman machine? > Now another problem occurs: > > Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool ... 'localhost' doesn't match either of > 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', > 'domain-04.de', 'www.domain-04.de'"))) The 'HTTPSConnectionPool' message has nothing to do with the 'Cannot connect' issue. > Port 25 entry results from the manual regarding the postfix configuration: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht > ml > > e.g.: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com > smtp_port: 25 And I wonder why it's trying to connect to localhost when smtp_host is mail.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I am pleased to announce new stable releases for Mailman Core, Postorius, > Hyperkitty. > > These include both new features and bug fixes. Complete change log for > each components: > > Mailman Core 3.3.3: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > Postorius 1.3.4 > https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4 : > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Minimum supported Python version is 3.6. > > You can install them using: > > $ pip install --upgrade postorius hyperkitty mailman > I don't know if this is necessary, but I used to do it with another update method documented by Mark. After running the upgrade script (from that method) I would run these too: /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 /opt/mailman/mm/bin/django-admin compress /opt/mailman/mm/bin/django-admin compilemessages /opt/mailman/mm/bin/django-admin migrate Now I did run them and got an error and I wonder if I should be worried: (venv) [mailman3@gw ~]$ /opt/mailman/mm/bin/django-admin compress CommandError: *An error occurred during rendering /opt/mailman/mm/venv/lib/python3.7/site-packages/django_allauth-0.42.0-py3.7.egg/allauth/templates/account/password_reset.html: /bin/sh: sass: Permission denied* Compressing... (venv) [mailman3@gw ~]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

[MM3-users] Re: Ann: Postorius 1.3.6 is now out

by Mark Dadgar

On Sep 29, 2021, at 9:28 AM, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > On Wed, Sep 29, 2021 at 6:28 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> Hey Everyone, >> >> I just tagged and released Postorius 1.3.6. This release includes both bug >> fixes and >> new features. >> >> Some of the notable features include >> - Ability to list and handle un-subscription requests to the list >> - Option to choose delivery mode and delivery_status directly when >> subscribing to a list >> - Addition of a user management interface, which allows updating a users >> password, >> manually verifying their email addresses, update user’s Display Name >> etc. >> - Expose a number of Bounce processing related options in List’s settings >> >> A full list of changes is available here >> >> >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 >> >> You can install this release using pip >> >> $ pip install postorius django-mailman3 mailmanclient —upgrade >> > > root@svr:/usr/local/mailman # pip install postorius django-mailman3 > mailmanclient —upgrade > ERROR: Invalid requirement: '—upgrade' > > Why do you think I got this? I had this issue too. I think some mail clients are turning a double-dash into an emdash. It should be: --upgrade - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 10 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by Mark Sapiro

On 12/28/21 11:56 AM, William Oliver wrote: > > 1) I got the error > > django.template.library.InvalidTemplateLibrary: Invalid template > library specified. ImportError raised when trying to load > 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' > from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site- > packages/mistune/scanner.py) > > when I ran 'mailman-web migrate' > > The fix was trivial: I just added the lines: > > from mistune.util import escape_html > from mistune.util import escape_url > to > /opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py This is fixed at https://gitlab.com/mailman/hyperkitty/-/merge_requests/379. Unfortunately, that fix is not in the latest release version. We will need to address that as mistune 2.0.0 moved those functions from their prior location in mistune 2.0.0rc1 > 2) Similarly, migrate (using postgres) also gave the error: > > File "/opt/mailman/venv/lib/python3.9/site- > packages/django/db/backends/postgresql/utils.py", line 6, in > utc_tzinfo_factory > raise AssertionError("database connection isn't set to UTC") > > I was able to find a discusson of this one at > > https://stackoverflow.com/questions/68024060/assertionerror-database-connec… > > which had me downgrade to an older version of psycopg2-binary: > > pip install psycopg2-binary==2.8.6 > > There might be a different fix, but this worked. This should be fixed in psycopg2-binary, but it isn't. The work around is what you did and I'll update the doc. > 3) When I ran the test "uwsgi --ini /etc/mailman3/uwsgi.ini" I got the > error: > > ModuleNotFoundError: No module named 'settings' > > This was also trivially fixed by adding the path: > > export PYTHONPATH=$PYTHONPATH:/etc/mailman3 > > in /opt/mailman/.bashrc The recommended uwsgi.ini includes pythonpath = /etc/mailman3/ according to https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… this should work. Did you have that? If you did and it doesn't work, perhaps adding env = PYTHONPATH=/etc/mailman3 would work. > 4) Sometimes when I rebooted the machine, when I ran 'systemctl start > mailman3' I'd get the error that mailman wouldn't start because the > lock was stll there. I never could figure out where the lock was, so I > worked around it by replacing > > > ExecStart=/opt/mailman/venv/bin/mailman start > > with > ExecStart=/opt/mailman/venv/bin/mailman start --force > > in /etc/systemd/system/mailman3.service > > I'm sure there's something bad about doing that, but it works for me, > so far. The lock is /opt/mailman/mm/var/locks/master.lck* The problem with using --force unconditionally is you can start a second instance when mailman core is already running and that causes other issues. > 5) I had a problem with mail to outside people not being delivered > while mail to the local host was delivered. It turned out that this was > because in my mailman.cfg I had "smtp_host:my.listserver.tld when it > should have been localhost. The error was "relay access denied." To > fix this, I had to add my.listserver.tld to "mynetworks" in > /etc/postfix/main.cf, ie change: > > mynetworks = 127.0.0.0/8 10.0.0.0/24 > > to > > mynetworks = 127.0.0.0/8 10.0.0.0/24 111.222.333.444 <--- my ip address > > However, Mark Sapiro (a God) told me this was because I had changed a > line in the [mta] section of mailman.cfg. I had changed > > smtp_host: localhost > > to > > smtp_host: mydomain.tld > > Here's the thing. The reason I did this was because the instructions at > https://docs.mailman3.org/en/latest/config-core.html > > give this as their model: > > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com <---- not localhost > smtp_port: 25 I'll add some clarification to the doc. > The instructions are good, but there are a few places where one size > does not fit all, I guess. > > 6) A second error in delivery to outside addresses resulted in an > "Access denied" error. A search on the internet revealed that this had > to do with (for me) smtpd_recipient_restrictions in postfix. See, for > instance: > https://know.mailsbestfriend.com/postfix_error_relay_access_denied_noqueue_… > > Changing this fixed things. > > I'm not sure, but I think this shows up mostly with installations that > include dovecot. This is a Postfix configuration issue. <big snip> Thanks for your feedback. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

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

by Mark Sapiro

On 1/2/22 11:18 AM, Mark Sapiro wrote: > > Please do send me the shunted .pck. what is going on is this is an > English language list which has character set `ascii` and the notice for > some reason has non-ascii, possbbly the Subject: or the user's display > name has non-ascii. But possibly the message itself is defective. > > In any case, I'd like to get the shunted message to see if there's > something we should fix. Thanks for sending me the shunted .pck. It turns out I didn't need it. Had I looked more closely at the Traceback, I would have realized that the issue is that the list's list:admin:action:post template contains non-ascii. In particular, the character in position 5 is ’ which is a unicode right_single_quote, not an ascii apostrophe. There may be other unicode fancy quotes ad well. You can fix the template to contain only ascii or you can set the character set for English to utf-8 by adding ``` [language.en] charset: utf-8 ``` to mailman.cfg. The downside of the latter is that outgoing message bodies will always be base64 encoded which generally precludes grepping mailboxes to find things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Configuration Question

by Ryan McClung

Greetings, Sorry, I wasn't entirely clear. That message was written pretty quickly and without much thought to explaining my situation. A while back I opened a ticket talking about how mailing lists keep disappearing when running: mailman lists In a directory that wasn't the same as the config/db original location. What I was wondering is if there was a way to make it so that the location remains static regardless of how you invoke the mailman command. Ryan On Thu, Aug 23, 2018 at 8:46 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > 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) > _______________________________________________ > 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/ > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

6 years, 11 months

[MM3-users] # comment allowed in a template file?

by Stephen J. Turnbull

skenny(a)scss.tcd.ie writes: > I've found that dropping files in to the templates directory is a simple and convenient way to make certain things happen. E.g. I can set a default footer for all posts by putting the desired content in a file called var/templates/site/en/list:member:generic:footer.txt. > > I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: > # This file is managed by Puppet. This is a pure comment, right? I mean, Puppet doesn't pay any attention to it, that's just so you don't go editing that file. As Mark says, there's no supported way to add comments to a template. But as a horrifying hack, assuming a pure comment, one could add the key 'This_file_is_managed_by_Puppet' with value "" to the dict used for template rendering. Then your file would look like ${This_file_is_managed_by_Puppet}\ This is the original text of the template string. I'm not sure if the \-newline hack would actually work. You might need to accept an initial newline in the rendered text, or have a long first line like ${This_file_is_managed_by_Puppet}This is the original text of the template string. It's probably too ugly for prime time, but thinking about hacks like this give me joy. ;-)

5 years

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

by Mark Sapiro

On 3/2/21 12:10 AM, David Partain via Mailman-users wrote: > > I'm not on the latest mailman, unfortunately. I use the bundled packages on Ubuntu 18.04, which are > > mailman3 3.1.1-9 > mailman3-doc 3.1.1-9 > mailman3-full 3.1.1-9 > mailman3-web 0+20170523-14 > >>From the mailman-web logs, it looks like it's using python2. That would explain a lot. In particular, it would explain why the .pyc files aren't located per PEP 3147 <https://www.python.org/dev/peps/pep-3147/>. But it also raise the question of how anything works at all. Python >= 3.6 is required. HyperKitty and Postorius used to run under Python 2, but haven't for some time. I'm not sure what versions are in Debian/Ubuntu 0+20170523-14 package. > Put the symlink back, and it works again. (But still without the emojis working, of course.) > > Postgres is what's in settings.py, but I assume that should be overriden by what's in settings_local.py. > > Baffling. I don't really know what to do next, but I'll keep looking. I suggest removing all the .pyc files and restarting the services. That will probably recreate .pyc files, but they should then be good. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

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

by Stephen J. Turnbull

Andreas Barth writes: > Of course, [git main always has features, sometimes lots of them, > not in the distro packages] is true not only for mailman3, but also > for exim, kde, gimp, whatever. Well, this is more true of Mailman than those other packages for a few reasons. As Mark points out, Mailman is evolving, but I wouldn't say more rapidly than those other examples. However, one important driver of Mailman 3 evolution is that the Internet is a hostile environment, and many changes in Mailman are driven as a response to security or other issues that are out of your control as admin of an Internet host. It's true that distros are pretty responsive to that kind of issue, and frequently backport security patches to the version they support quickly, but heavily patched versions have their issues, too. In general I would say that distro packages are extremely well-suited to establishing a stable baseline for your host (and for Debian, at least, you can flexibly choose how stable various parts are), but for mission-critical applications you shouldn't *default* to the distro package. You should carefully evaluate whether the distro version historically has kept pace with upstream, whether it is featureful enough, and whether it's worth your time to do work that will eventually be done by the distro's package maintainer (you hope ;-).

4 years, 4 months

[MM3-users] Re: Help! Duplicate DKIM key

by Jose Bernal

Mark - adjusting this setting in mailman.cfg seemed to do the trick. No more errors and postfix is able to send mail out to our Amazon SES relays just fine now. Thank you, On Mon, Mar 10, 2025 at 6:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/11/25 7:06 AM, Jose Bernal via Mailman-users wrote: > > > > Here is the message. We've got several thousand log entries like this > now: > > > > *554 Transaction failed: Duplicate header 'DKIM-Signature'* > > Mar 10 08:31:10 mail1 postfix/smtp[217753]: 738B53F15E: to=< > > brian(a)brianmichaelslaw.com>, relay=xxx.org[44.225.xxx.xx]:587, delay=37, > > delays=2/35/0.16/0.13, dsn=5.0.0, status=bounced (host said: 554 > > Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end > of > > DATA command)) > > This is Amazon SES being stupid, but you can avoid this issue by setting > ``` > remove_dkim_headers: yes > ``` > in the `[mta]` section of `mailman.cfg`. > > -- > 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 jbernal.web.dev(a)gmail.com >

4 months, 3 weeks

[MM3-users] Re: Speed/progress of update_index_one_list?

by Philip Colmer

On Fri, 14 Jan 2022 at 07:50, Mark Dadgar <mark(a)pdc-racing.net> wrote: > On Jan 13, 2022, at 11:46 PM, Philip Colmer <philip.colmer(a)linaro.org> > wrote: > > Yesterday, I ran "mailman-web update_index_one_list" against a mailing > > list. The command output "Indexing 328077 emails" and that is the last > I've > > heard from it. > > > > The process is still running but, looking in ~mailman/web/logs, I can't > see > > anything happening related to that list. > > > > Is there any way to determine how far this process has got, or what it is > > actually doing? (Without stopping it) > > > > For future indexing, what makes the most difference to the speed? Does it > > benefit from having multiple cores if I resize the AWS instance to a > larger > > processor? What is the bottleneck for this process? > > > Which indexer are you using? Whoosh is interminably slow. Think “days to > generate a list index” slow. > Yeah, we're using Whoosh. Good to see it lives up to its name :) > I recommend Xapien. It is ridiculously fast. > Thank you. I had been put off using Xapian because the documentation, from a MM3-perspective, seemed sparse and confusing, but I'll stick with it to try and get it working if Whoosh is the root problem here. Philip

3 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

What would be the config for a simple one way announcement type list ???? El vie., 21 jul. 2017 a las 21:09, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 06:46 PM, Rafael Mora wrote: > > Can I use it for mailing lists? like MailChimp? > > > Yes, if all you want is a simple one way announcement type list, Mailman > can do that quite well, with appropriate list configuration[1], but as I > tried to say, MailChimp has many more features that are oriented towards > that kind of mailing. > > [1]There are many horror stories of people setting up a mailing list and > subscribing a bunch of people to it without ensuring that members can't > post back to the list. > > Then with the first post, people start posting back to be removed and > then others reply that they didn't send that mail and it snowballs and > within an hower, the poor list server is so backlogged that the clueful > replies take hours to be delivered. I personally have been added to more > that one list to which this happened. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: Flushing/syncing hyperkitty with mailman

by Eric Abrahamsen

On 05/19/18 12:24 PM, Eric Abrahamsen wrote: > I've got mailman running on Ubuntu 14.04, with systemd service files to > govern the mailman and hyperkitty qcluster processes. > > I notice in the systemctl status call for the qcluster command that > there are a bunch of errors like: A bump for this, I've been getting this series of errors once a minute for weeks now. There must be some way to clear out dangling thread references? And I take it that for the meantime we shouldn't be using the "delete thread" feature of hyperkitty... > [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. > [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] > [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. > [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] > [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. > [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] > [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. > [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] > [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. > > Is there something more I should be doing to sync hyperkitty's database > with mailman? I've got the crontab file in place, and that appears to be > running without error. Anything else? > > Thanks, > Eric > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 1 month

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/23/19 7:12 AM, Franklin Weng wrote: > Hi list, > > I set up a mailman3 server and built a few lists to test. > > When I set the list name using Chinese characters, the web site shows > correctly. However in the subscribing welcome mail the list name was > shown in question marks. Screenshot is here: > > https://nextcloud.slat.org/index.php/s/CxPjpYMbQzQ6444 The name of the list from the screenshot seems to be zh-l10n(a)lists.linux.org.tw. The thing shown with ?s in the screenshot is the list's display_name (called Display name in Postorius). > The LANGUAGE_CODE settings.py (in Debian /etc/mailman3/mailman-web.py) > is set to zh-tw , and USE_I18N and USE_L10N are all set to True. These settings are all for Django and have nothing to do with how the list welcome message is sent. > Is there any other setting I should look at? The list's preferred_language setting (Postorius -> Settings -> List Identity -> Preferred Language. The list welcome message is encoded in Mailman's character set for the list's preferred_language. If this is English (USA), the character set is us-ascii. If it is set to Chinese (Taiwan), the character set is utf-8, and it should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Debian 12 postfix errors: "warning: connect to transport private/lmtp: Connection refused" and "status=deferred (mail transport unavailable)"

by Mark Sapiro

On 4/7/25 12:00, Philip Bondi wrote: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 127.0.0.1 > lmtp_port: 9024 Why are you setting this? Testing uses port 9024 to avoid conflicts, but the default port 8024 should be used for production. > [799] # postconf -n ... > virtual_mailbox_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp Why do you have this? It may well be the issue. > ebill(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-bounces(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-confirm(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-join(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-leave(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-owner(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-request(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-subscribe(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-unsubscribe(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > > [797] # telnet localhost 9024 > Trying ::1... > Connection failed: Connection refused > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > 220 shackleton12.systemdatabase.ca GNU Mailman LMTP runner 2.0 > QUIT > 221 Bye > Connection closed by foreign host. It looks like you can connect to port 9024 in this way. However I recommend removing `lmtp_port: 9024` from your mailman.cfg and rerunning `mailman aliases` to regenerate the postfix maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: REST API notes

by Barry Warsaw

On Jun 28, 2017, at 01:47 AM, tlhackque--- via Mailman-users wrote: >As a beginner with the REST API, I found it necessary to read code and >experiment to figure out how to get things done. Thanks for the feedback. Other than the work supporting Postorius and HyperKitty, I think you've done some of the more extensive exploration of the REST API, so your comments here (and greatly appreciated bug reports) are quite valuable, and I think will help us make the REST API both more usable and more discoverable. It's important to point out some history of the REST API. Originally, we used the restish library (which was Python 2 and eventually abandoned upstream). That choice informed the essentially dynamic nature of the REST API. Which means that unlike many other systems, we don't have -nor do I think we could if we wanted to- easily and automatically generate a static description of the REST API. When I switched to Falcon (which is both Python 3 compatible and well maintained upstream), I had to reimplement what I called "object based traversal". Falcon by default supports a routes based traversal mechanism, similar to Flask and other systems. But by plugging in (originally, by monkeypatching, but now through an official Falcon API) support for object based traversal, I was able to port the extensive existing REST implementation to the new underlying library fairly easily. All this to say that some of the problems you describe are due to historical accident. And that's served us well(-ish) while we only had to support mailmanclient and P/HK. But as the REST API is used in more places, those deficiencies are becoming more glaring. I think if we ever make progress on Lemme (our authenticating REST proxy), we'll likely encounter the same problems. But at this point, it's infeasible to completely reimplement the REST machinery. >There are a number of implementation choices that are unusual. No doubt. :) >There is some documentation in src/mailman/rest/docs. It's oriented toward >Python and intermixes the mailman client & REST API, apparently trying to >show equivalence. Much of that is because these are doctests, i.e. testable documentation. It's a tradeoff between making them useful as docs but also testable without too much clutter. It's very much oriented toward Python because that makes testability easier. It would be good to have documentation for pure HTTP/JSON consumers, but it would be imperative for that also to be testable so we're sure it remains accurate, aside from any requirements to keep the docs in sync. Suggestions and contributions would be very much welcome here. >The REST API has a hybrid interface: Requests are made with >application/x-www-form-urlencoded POST, PUT, PATCH and delete http requests. >Requests are also accepted as parameter strings. > >The responses are JSON. (This is rather surprising - one would expect JSON >requests - and I hope someday they'll be accepted, as the split complicates >clients. I suspect this evolved to simplify the initial Web GUI client >(Postorious), but it precludes using standard JSON-in/JSON-out client >libraries.) Absolutely. I want to support JSON-in/JSON-out. Again, the current mismatch is due to historical implementation decisions, but there's nothing in principle preventing us from accepting JSON in, afaict. We'd have to continue to accept both, for backward compatibility reasons. >Error responses are often misidentified as content-type: application/json, >but actually contain a text/plain error message. This isn't universally >true; for example the 401 response actually IS JSON. A client has to guess >and handle decoding exceptions. That's clearly a bug. The Content-Type should always be accurate. It would be a new feature to also support JSON error responses. >The API presents resources hierarchically, rooted at '/'. The top level >resources include /users, /lists. /addresses, /domains, /system > >The next level is a resource id. Kind of. It all depends on what the top-level resource is returned. This makes sense when you think about the object based traversal machinery. Each path component points internally to an object, and the subsequent path component is handled by that object. If that returns another object, then the next remaining path component is consumed by *that* object. And so on until we reach the end of the path. Then the object at the leaf responds to the HTTP command, and each object knows how to represent itself as JSON, and it knows its canonical location within the resource tree (there can be multiple paths to any particular object, but there's always one canonical location). >There is a an id which is stable for the lifetime of an object, and a current >name (which can be changed). For example, a list has a name like >mylist(a)example.com, and a list_id of mylist.example.com. But if you change >the list name, it becomes mynewname(a)example.net, while the list_id remains >mylist.example.com. Lists are weird in that they have two identifiers. One is the posting address, what we internally (and slightly incorrectly) call the "fully qualified list name". I don't particularly like that nomenclature anymore, but we live with it. A posting address can change, e.g. if you rename or rehome a list. The (RFC 2919) List-ID is assigned when the mailing list is created and it's immutable. Section 4 discourages changing the List-ID and Mailman takes that as a requirement. Rename a list or rehome it to a different domain on the same server and the List-ID will never change. Again for historical reasons, many APIs both internal and external used the posting address to identify the list, but this is wrong exactly because that can change. I've slowly been converting APIs to accept both the posting address and the List-ID when identifying the mailing list. New APIs generally accept only the List-ID. Bottom line, it's best to use the List-ID. >Lists are associated with "domains", which are the "domain part" of the >list's address. That is, the part after the @. This is sometimes referred >to as the "mail host", but there need not be a real host. Yep, again historical nomenclature. >A domain has to be created before you can create a list with an address in >that domain. Some APIs (e.g. `mailman create` CLI) will create the domain automatically if it doesn't already exist, and unless you disable that explicitly. >Resources are created with a POST to their top-level resource. To create a >domain, post to /domains with mail_host => the domain, and (optionally) >description => a description for the GUI. The response isn't JSON as one >would expect. In fact, it's an empty application/json response with a 201 >status. > >To create a list, one POSTs to /lists. This post takes a restricted set of >parameters; in the case of a list, just its fqdn_listname, (and an optional >style - which isn't well defined). The response isn't JSON as one would >expect. The Location header of the response contains a URL of the new list. What else would you expect? From my reading of books like RESTful Web Services (admittedly a long while ago), that's exactly the proper response to an appending POST. Return a 201 with a Location header to the new resource and empty content. >To configure the list, you have to follow up with a PUT or PATCH to that URL >+ /config This is where you can set the description, posting policy, etc. >It's unrealistic to do a PUT; even if you're cloning another list, there's no >programatic way to determine which attributes are writable. PATCH what you >know... Mailing list resources are somewhat unique in that they probably have the most properties of any resource/object in the system. That's not surprising if you think about it, but it does make PUTing to a mailing list more or less impractical. That's certainly not true of other, smaller resources though, and of course, you still want symmetry there (plus, implementation-wise, it's almost a no brainer to support both PUT and PATCH). >Members are associated with e-mail addresses - which belong to Users. Users can have multiple addresses, addresses can be linked to only one user, but may be unlinked, and members associate "subscribers" to mailing lists, where a subscriber is either a user-with-preferred-address, or an address. >You create a user by posting to /users with email => the email address, and >optionally display_name => the name string. (A user can also be implicitly >created by subscribing an e-mail address, but that gets confusing.) The >e-mail address is the primary email address for the user. More later. >Again, you get a Location header in the response, which you can use to PATCH >/preferences to set delivery_status, etc. .These preferences are part of a >hierarchy - many have a system default, a list default, the user default, and >a subscription to that list value. You can find the User associated with a >list by a GET of /addresses/address(a)example.net. Technically, the returned user isn't necessarily associated with a list. It *may* be subscribed to the list, but that relationship is represented by a member. >This GET returns two URLs: user => the user owning this address, and >self_link => the address object. *All* resources in the REST API have a self_link, and while that may seem redundant, it's not. As mentioned above, you can take various paths through the resource tree to get to a particular resource, but regardless of that, every resource has exactly one canonical location. That location is represented by the self_link. >Note also that there are both an email and original_email attribute. The >latter preserves case. The former is used internally by Mailman as a >resource key, etc. (Though exactly what happens if John(a)example.net and >john(a)example.net both subscribe is unclear.) They can't. Mailman is case-preserving case-insensitive for email addresses. Technically speaking, john(a)example.com and JOHN(a)example.com can be different mailboxes, but that never happens in practice anymore, and Mailman has always explicitly treated them as the same address. This goes back to the earliest days of Mailman. >Once a list is configured, you can add members. This requires the list_id - >which you don't (officially) have. So you do a GET on the list resource, to >get the list_id. Then you can subscribe a member with list_id => (the list >id), subscriber => email address. Optionally you can >pre_verify/confirm/approve the member and/or add a display_name.. POST to >/members. Again, you get a Location header back. You can't specify >everything you might like. as a creation attribute. So you may have to PATCH >the member to, for example, set the moderation_status. This is true, but it also kind of makes sense if you grok the way preferences work, i.e. hierarchically as you describe above. TBH, I don't particularly like the way preferences are modeled either internally or through the REST API, but I haven't been able to come up with anything better. >You may also need to PATCH the member /preferences if you want to set >list-level delivery status, etc. All true. In each of those cases, you may be talking to a different preference resource. >Consider adding at least an owner when creating a list. I think that would be a useful addition to the REST API for list creation. >One challenge is that almost everything requires multiple REST operations to >set up. But REST (by definition) is stateless. So the best you can do is >order operations & hope. I don't understand this. REST is stateless, but not all HTTP operations are idempotent. POST certainly isn't, by definition, so if you use it to create a new resource under a collection, you clearly cannot modify that resource through PUT or PATCH until the resource is created, which only happens when POST succeeds. >The mailman client examples refer to transactions (e.g in users.rst, there is >'transaction.commit(); - but REST can't hold state. It does appear that the >server uses DB transactions to ensure that any given REST operation is ACID, >but the composite operations (e.g. create a list and set it's config) can not >be Atomic. This is an architectural flaw in the API. I think what you're getting at is that some POSTs to create new resources do not accept the same parameters as the subsequent PUT or PATCH on the newly created resource. I think that may be true, but it's not universally so. E.g. POST on /domain creates a new domain, returning the location of the new resource. You can provide both a description and an owner, and you can also provide a mail_host. But mail_host is immutable, and PATCH or PUT support changing all mutable attributes on the domain. That should be the general rule; if an attribute on a resource is mutable, you should be able to PATCH and PUT it, *and* you should be able to specify all mutable attributes, plus some immutable ones on the POST that creates the resource. GET should return all attributes, mutable or immutable. This rule may not be strictly adhered to for all resources and collections, but I would consider that a bug, not an architectural flaw. AFAIK, this is all working as any well-defined web service should work. >Symbolic names (which are required) for attributes are in the >src/mailman/interfaces/(class).py. Please note that the interfaces under this package are for the *internal* API, which often, but not always, is exposed in the REST API. These two APIs serve different purposes so they cannot be a one-to-one mapping, and there are many resources in the REST API that don't correspond directly to internal objects, and there are many internal objects that are not exposed to the REST API. >What you can get/set comes from src/mailman/rest/(class).py. Yes, so clients of the REST API are served by objects in this package. Plugins and other internal operations are served by the objects that implement interfaces in the src/mailman/interfaces package. This is a strict separation of concerns, and it mirrors other 'external facing' interfaces, of which the command line is another example. Hope that helps. -Barry

8 years, 1 month

[MM3-users] Re: Implicit destination

by Mike

My suggestion, which most don't people buy into, is don't worry about giving a response to a spammer. They are not going to magically drop your address just because they have not heard from you in 2 years. If it doesn't bounce you will be kept on the list and the e-mail list likely be sold. Go about your business and don't worry about sending confirmation to spammers. If you want another suggestion that people really don't like, Reject with Notification to anybody posting to the list, but they are not a member. I know - the reply sent to them is awful, but that is what I do for all my lists. Mike On 8/26/2018 2:54 PM, David Krantz wrote: > Hi, > > I have a spam-problem like anyone else. Most of the spam my listserver > receives has some kind of impilict destination so the implicit rule > catches most of the spam that way. This is fine. What is not so fine, > however, is that this results in a moderation message to the sender. > I'd like to stop that so that the spammer has no confirmation that the > mail was received. > > I can probably stop this in postfix before the mail reaches mailman3, > but I'd prefer changing the behaviour of the rule. Is there any > setting that could be used or should I just modify the rule? > > Cheers. > // David

6 years, 11 months

[MM3-users] Re: problems in setting up mailman3 containers.

by Abhilash Raj

On Wed, Jun 19, 2019, at 7:02 PM, Steven Jones wrote: > Hi, > > > Trying to setup the 2 mailman3 containers, they fail to start, config > and failure messages are, Check the required configuration for container images [1]. [1]: https://github.com/maxking/docker-mailman#configuration > > > ======== > > [root@rhel8-svr-001 mailman]# pwd > /opt/mailman > [root@rhel8-svr-001 mailman]# !269 > more core/mailman-extra.cfg > # mailman-extra.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > > [mailman] > site_owner: steven(a)xx.co.nz > > SECRET_KEY: testing123 > [root@rhel8-svr-001 mailman]# !271 > more web/settings_local.py > SECRET_KEY: testing123 > > [root@rhel8-svr-001 mailman]# !272 > podman run mailman-core > DATABASE_URL is not defined. Using sqlite database... > No MTA environment variable found, defaulting to Exim > HYPERKITTY_API_KEY not defined, please set this environment variable... > exiting... > [root@rhel8-svr-001 mailman]# !273 > podman run mailman-web > SECRET_KEY is not defined. Aborting. > [root@rhel8-svr-001 mailman]# > ========= > > > Could really do with some examples of these files as well... > > > regards > > Steven > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: Database running VERY hot

by Darren Smith

Thanks for the response about how to fine tune postgres - that's some good documentation there, and I certainly appreciate what you've found in your work. Darren On Thu, Mar 8, 2018 at 12:28 PM, C. R. Oldham <cro(a)ncbt.org> wrote: > Greetings, > > 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. >> > > Out of the box Pg performs pretty well but still benefits from tuning. > Recommend you head over to https://wiki.postgresql.org/wi > ki/Tuning_Your_PostgreSQL_Server and see what makes sense for your > configuration. > > Anectodally, at my work we produce an app with Pg as the backend > database. Simple tuning, including turning `synchronous_commit` off, > yielded us 10x better performance. Granted, our app is very write-heavy and > typically Mailman and friends will be far more read-heavy, so giving Pg > enough RAM for in-memory sorts and caching will benefit you more. > > --cro > _______________________________________________ > 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/ >

7 years, 4 months

[MM3-users] Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Thomas G

Hi, I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh install in Mailman3.2. I didn't found how migrate the archives. From : HyperKitty - Version: 1.1.1 - Python2.7 To : HyperKitty - Version: 1.2.1 - Python3.5 I exported a mbox from hyperkitty (web interface) and tried to re-import it, without result. """""""""""""""""""""""""""""""""""""""" xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to listedetests(a)hatlab.fr Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the 'manage.py update_index_one_list listedetests(a)hatlab.fr' command. """""""""""""""""""""""""""""""""""""" The database stay empty (and web interface): """""""""""""""""""""""""""""""""""""" mailmandbnameprod=# select * from hyperkitty_email; id | message_id | message_id_hash | subject | content | date | timezone | in_reply_to | archived_date | thread_depth | thread_order | mailinglist_id | parent_id | sender_id | thread_id | sender_name ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- (0 rows) """""""""""""""""""""""""""""""""""""" Any idea to do this importation ? Thanks !

6 years, 10 months

[MM3-users] Re: Issue with mySQLdb-module on Debian

by js＠jslz.de

Hello, when you look a bit further up in the logs, you might see another error with mysql - error creating the mainman database (something like 'index too long'. This error can be found in some other applications as well and has to do something with the mysql backend setup. This can be fixed manually for other apps, but the necessary steps are hard to be implemented in the scripts. I only recollect my memories here - cannot look up in my notes currently. Yes, a switch to postgres will help you if this fits into your architecture. Jörg 24. Januar 2019 12:01, "Bjoern Franke" <bjo(a)nord-west.org> schrieb: > Hi, > > I already opened a debian bugreport for it, but I'm still wondering why > the following issue appears: > > File > "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", > line 30, in <module> > 'Did you install mysqlclient or MySQL-python?' % e > django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb > module: No module named 'MySQLdb'. > Did you install mysqlclient or MySQL-python? > > python3-pymysql, which is a dependency of mailman3-web and provides > mySQLdb, is installed. > > (Maybe it's time to migrate to postgres.) > > Kind regards > Bjoern > _______________________________________________ > 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] cc'd e-mail addresses rewritten with @invalid.domain

by peterbw＠gmail.com

Hi, We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: To: test_user(a)gmail.com cc: listserv(a)lists.test.org; Williams, Peter; "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: to: test_user(a)gmail.com cc: listserv(a)lists.test.org, Williams(a)invalid.domain, Peter(a)invalid.domain This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org. This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org; it would route properly. Do you know what may be causing this? Please let me know if there is any additional information I may provide regarding this and I will try to respond as soon as possible. Thanks and have a nice day! Peter

4 years, 10 months

[MM3-users] Two Questions: One General, the Other Specific

by David Wilson

Salutations; For context, I have been lurking on this site for a number of years now, in order to track the progress of this wonderful mailman3 project. Further context, I am chair of a 66 unit condominium and pay for two lists provided by EMWD.com and get a hands on feel from an mailman3 operations perspective. *Is there another site that might best communicate the future goals, plans, objectives, and time frames for mailman3 or is the status of the project at the state of being primarily reacting to problems, as evidenced in this problem solving forum, at least as it seems to me, with no offense meant or intended?* Something I find surprising is a problem described in an image grab below relating to an inability to amend a list entry to include a name to be associated with an email address, as if the data needs to be immutable. When a workaround was unsuccessfully explored to delete the entry and then resubmit an amended entry but with the same already deleted email address, that was still refused, presumably because of pointers to archived data don't permit, but this seems like a particularly onerous restriction, or perhaps even a bug, or at least a severe design constraint. *Is this item on an existing to do list?* *Comments please?* Thank you in advance for any responses to the questions in bold to facilitate faster reading, etc. Best regards. Dave Wilson ------------------------------------------------------------------------

4 years, 5 months

[MM3-users] Re: Bulk update of members' moderation settings

by Mark Sapiro

On 11/18/21 12:37 PM, Alex King via Mailman-users wrote: > I imported a list from mailman 2.1 using > https://docs.mailman3.org/en/latest/migration.html. > > It happens that emergency moderation was set on the mailman 2.1 list, > and this has resulted in all members having Moderation set to Hold. I > now want to change that to Default Processing for all members. > > Is there a way to achieve that in bulk without clicking through the > members options for each member in Postorius? I don't understand how this happened. The mailman 2.1 list's emergency setting should hsave been imported as the emergency setting of the Mailman 3 list and should not affect individual member's moderation at all. However, to set the moderation action for all members of a list to default processing You can do something like this in mailman shell ``` bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.interfaces.action import Action >>> for member in m.members.members: ... member.moderation_action = Action.defer ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: "Unsubscribe all" button

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/20/22 17:32, Philippe B wrote: > > Would it be possible to add a confirmation screen after you click > > on it? Like: WARNING! Clicking "Confirm" will empty the list of > > all its existing members, regardless of what was entered on the > > previous screen. That operation cannot be reversed. Are you > > absolutely sure that you want no one to be on your list anymore? > > There is a confirmation screen although it is not as strongly worded as > you suggest. I'll go check the issue, but let me say I think a confirmation screen is bad UI here. People who know what they're doing shouldn't have to pay the price of a confirmation screen. I know of at least two universities where they "unsubscribe all" from thousands of class mailing lists every term. Of course they automate that pretty quickly when they get to thousands, but it seems plausible to me that such lists for groups that regularly turn over (nearly) 100% of subscribers are a reasonably common use case. Instead, there should be a check for selected users, either disabling the "unsubscribe all" button itself (if we decide to implement more Javascript in the UI) or presenting the confirmation screen if there are any selected users. Also, at least for native speakers, "Unsubscribe everyone" will probably be a better label for the button.

2 years, 9 months

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

by Abhilash Raj

On Sat, Dec 19, 2020, at 4:32 PM, Carlo Landmeter wrote: > We are not running in debug mode, we simply set the loggers to log > DEBUG or else we don't see much info. > I also doubt the shown error is the problem as I see more template > errors. > I have also tried to run the official docker images mailman-docker but > im having the same issue. > > When I post via the online form, i can see uwsgi requests with http > status 200 from the ajax call, so i would expect it to work, but it > does not leave a message in hyperkitty nor sends an email. > > PS emails are send just fine via smtp posting. Unless I am missing something basic, I don't really know why it doesn't fail on our servers. May have something to do with Django versions or something. I need to work a bit more on verifying it. This is the line in template[1], rendered using this context[2] which seems to be causing the issue. [1]: https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/templates/hy… [2]: https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/messag… > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Installation -- error on mailman-web migrate

by Mark Sapiro

On 9/16/21 8:43 PM, Mark Dale via Mailman-users wrote: > > ... and then at the beginning of many errors printed to screen I now have... > > /opt/mailman/venv/lib/python3.9/site-packages/django_q/conf.py:139: 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. The current version of mailman_web/settings/mailman.py has ``` Q_CLUSTER = { 'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default', } ``` Earlier versions omitted the `'retry': 360` which is the issue. > Completely not comprehending the above doc (and being absolutely clueless about django), I blindly added "retry: 30" ... > root@mx:~# nano -c /opt/mailman/venv/lib/python3.9/site-packages/django_q/tests/settings.py > > # Django Q specific > Q_CLUSTER = { > "name": "django_q_test", > "cpu_affinity": 1, > "testing": True, > "log_level": "DEBUG", > "django_redis": "default", > "retry": 30, Make that "retry": 360, > } > > > ... but no joy. Is it me or are there some pieces missing from the documentation? > > > _______________________________________________ > 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/ > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

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

by Odhiambo Washington

On Sun, Jul 28, 2024 at 4:42 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 00:39, Mark Sapiro wrote: > >> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: > >>> > >>> The server runs power-mailinabox, which uses Postfix indeed. All my > >>> mail, and quite a few others' mail is sent from the using SMTP-Auth > >>> on port 465. Actually, this message is sent via that server too. > >>> So it's clear to me that MM3 is not authenticating for some reason. > >> > >> What do you see in Mailman's smtp.log and in the mail.log on the mail > >> server? > > > > The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log > > *** Starting uWSGI 2.0.20-debian (64bit) on [Sun Jul 28 15:27:48 2024] *** > compiled with version: 11.2.0 on 21 March 2022 11:00:44 > os: Linux-5.15.108-1-pve #1 SMP PVE 5.15.108-2 (2023-07-20T10:06Z) > nodename: mailman > machine: x86_64 > clock source: unix > pcre jit disabled > detected number of CPU cores: 1 > current working directory: / > detected binary path: /usr/bin/uwsgi-core > setgid() to 33 > setuid() to 33 > chdir() to /usr/share/mailman3-web > your processes number limit is 513922 > your memory page size is 4096 bytes > detected max file descriptor number: 1024 > lock engine: pthread robust mutexes > thunder lock: disabled (you can enable it with --thunder-lock) > uwsgi socket 0 bound to UNIX address /run/mailman3-web/uwsgi.sock fd 4 > Python version: 3.10.12 (main, Mar 22 2024, 16:50:05) [GCC 11.4.0] > Python main interpreter initialized at 0x561ce813d1d0 > python threads support enabled > your server socket listen backlog is limited to 100 connections > your mercy for graceful operations on workers is 60 seconds > mapped 166752 bytes (162 KB) for 2 cores > *** Operational MODE: threaded *** > /usr/lib/python3/dist-packages/django_q/conf.py:139: 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. > warn( > WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter > 0x561ce813d1d0 pid: 113 (default app) > *** uWSGI is running in multiple interpreter mode *** > spawned uWSGI master process (pid: 113) > spawned uWSGI worker 1 (pid: 339, cores: 2) > [uwsgi-daemons] spawning "python3 manage.py qcluster" (uid: 33 gid: 33) > /usr/lib/python3/dist-packages/django_q/conf.py:139: 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. > warn( > System check identified some issues: > > WARNINGS: > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > django_mailman3.Profile: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Attachment: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Email: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Favorite: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.LastView: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.MailingList: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Profile: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Tag: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Tagging: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Thread: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > hyperkitty.Vote: (models.W042) Auto-created primary key used when not > defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > HyperKittyConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > postorius.EmailTemplate: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > PostoriusConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > 15:27:55 [Q] INFO Q Cluster low-vermont-harry-fillet starting. > 15:27:55 [Q] INFO Process-1 guarding cluster low-vermont-harry-fillet > 15:27:55 [Q] INFO Q Cluster low-vermont-harry-fillet running. > 15:27:55 [Q] INFO Process-1:3 pushing tasks at 386 > 15:27:55 [Q] INFO Process-1:2 monitoring at 385 > 15:27:55 [Q] INFO Process-1:1 ready for work at 384 > # Asynchronous tasks # https://django-q.readthedocs.io/en/latest/configure.html Q_CLUSTER = { 'name': 'mailman3-web', 'workers': 8, 'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default', } # Maintain type of autogenerated keys going forward # https://docs.djangoproject.com/en/3.2/releases/3.2/#customizing-type-of-aut… DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' -- 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

[MM3-users] Re: Google Summer of Docs

by Abhilash Raj

On Sun, Mar 24, 2019, at 11:58 PM, Terri Oda wrote: > > > On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" > <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >Ralph Seichter writes: > > > * Mark Sapiro: > > > > >> > If you post an issue at > ><https://gitlab.com/mailman/mailman/issues>, > > > > one of our GSOC aspirants may pick it up. > > > > > > Done, although I wonder if any GSOC participant would want to write > > > documentation instead of code... ;-) > > > >For their actual, Google-supported, project, Google explicitly > >excludes documentation. > > > > They do for Google Summer of **Code** but they've just announced Google > Summer of **Docs** which sounds really neat and we might want to > participate. They are calling it Season of Docs, happening in winter I think Sept-Dec AFAIK. Yep, we should participate in that, I sent out an email earlier about this too. > > (It's my personal opinion that our docs have really suffered since I > finished my PhD and stopped using them as a warmup exercise when I was > procrastinating on writing my thesis. *grin*) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 01:19, Odhiambo Washington wrote: > > Apart from all the defaults in settings.py (derived from gitlab), I also > > have this line: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > > Before the New Year releases of MM3, I used to get errors written to this > > file. > > Not anymore after I updated to the New Year releases. > > Another thing that I have realized is that prior to the New Year > releases, > > I would get an error logged to that file and also mailed to me. > > I don't think that I have changed anything in settings,py related to > > logging. > > > Nothing in those releases per se would affect this. This is Django and > django-allauth. Perhaps when you updated the Mailman packages, you also > updated these dependencies. > Which dependencies would those be? When I upgraded, the command I ran was: pip install --upgrade --force mailman mailmanclient postorius hyperkitty mailman-hyperkitty django-mailman3 And how do I find out what is suppressing the logging for the social accounts? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

[MM3-users] How to set up mailman 3

by David Krantz

Hi. I have tried and failed to set up mailman 3 using the mailman_bundle. I get the mailman3 server running correctly, but the problem is the extremely sensitive web user interface... Now when I found this mail list I understand that mailman bundle is depricated and that I must restart from scratch. Is this true? This annoys me quite a lot, can someone responsible within the project please mark the deprecated package as such? Almost none of the documentation is completely correct. It is useful but very incomplete. The mailman_bundle generated configuration examples for e.g. apache simply is wrong or incomplete. That said I got it running using http only, but when I switched to HTTPS the login simply ceased working. I use password+username as the other solution is quite complicated to get running. I could of course switch to e.g. google login, but that would require at least some documentation on how to do that. So, is there any documentation on how to use mailman 3? The error I get now is "Please enter a correct username and password. Note that both fields may be case-sensitive." I know that I enter the correct password as it worked before I added HTTPS. Sorry for the rant, but I am very annoyed by this. I just need a mail list server that works and thought it would be very neat to run mailman3 after running a hoste mailman2 for many years. Best regards // David

8 years, 4 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 5:39 PM, Mark Sapiro wrote: > On 10/21/20 12:14 PM, Brian Carpenter wrote: >> >> Well I can't dictate that to my list owners and there is no confirm >> token sent with the moderation notice. Why include this option in >> Postorius when it can't be properly handled? > > Postorius is still a work in progress. The unsubscription policies are > in core and are exposed in Postorius. Certainly the ability to moderate > an unsubscription should be in Postorius, but it isn't yet. We are an > all volunteer project and there aren't that many of us, and perhaps I'm > overreacting, but the tone of some of your recent posts seems a bit > demanding. I apologize. I didn't think I was coming across demanding but I am somewhat exasperated at some of these issues. I have a list owner who is now going to get a moderated request notice everyday that he can't do anything about it. But my question still remains: why is this option in Postorius when it can't be handled properly? Surely the option can be easily removed, right? Is the ability to list (via the pending moderation notices tab) and handle (as in the List owner can decide a moderation response) an unsubscribe moderation request there in Mailman core so that I can properly address it via Affinity? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: Internal Server Error: /archives/

by Christian

Thank you Mark! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, November 29, 2024 10:02 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /archives/ On 11/29/24 7:51 AM, Christian via Mailman-users wrote: > What is this error and how can I fix it please? Running Debian > 4.19.316-1 ... > Request Method: GET > Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! ... > Traceback (most recent call last): > None ... > GET: > sort = 'active"\'!' Some remote user has requested `https://lists.domedoman.ie/archives/?sort=active"'!` The `"'!` appended to the sort=active query fragment caused the error. This sort of thing happens when bots and script kiddies crawl your web site. You can find the request in your web server logs for more information about where it came from, but the bottom line is this will happen from time to time and it's not an indication that anything is broken. It would be possible to harden HyperKitty to defend against malformed URLs like this, but without a traceback it is not clear where to do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ XH5USTRI7JUHJT7UGWCGALENPDSSXWXE/ This message sent to csa(a)web-analysts.net

8 months

[MM3-users] Re: Changing delivery mode for ALL subscribers on a SINGLE list using REST

by Abhilash Raj

On Mon, Feb 18, 2019, at 4:56 AM, Henrik Rasmussen wrote: > While in Mailman Settings a user can change delivery mode for either > Global (all subscriptions regardless of address or list), Address based > (regardless of list name) or List Based (regardless of address). > > The list admin can change a user's delivery mode setting on a single > list (affecting only that address and only that list), but only one > subscriber at the time on the list. > > Changing a user's delivery mode can also be done using REST[1], but I > asume this will affect the user's subscription on all the lists where > she subscribed using the same address. > > How do I change ALL the subscribers[2] on a _single list_ to a certain > delivery mode, using REST? You watch to PATCH the preferences of a Member object, so that you don't affect other subscriptions of that address or user. http://localhost:9001/3.0/members/1/preferences > [1] > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/preferences.… > [2] Most likely by iterating through all subscribers, one at the time, > on the list in question. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 5 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Abhilash Raj

On 12/14/22 03:31, Mark Sapiro wrote: > On 12/13/22 10:38, Dan Caballero wrote: >> Hi Mark, >> >> I ran the commands and it took about 35 seconds for the loop to run. >> >> Here's the result. >> >>>>> count >> 4168 > > > So that's at least part of the issue. How does 35 seconds compare to the > length of time to process one moderated message through Postorius? > It seems it has to do with in-efficient lookup of the actual entry in the pendings table which needs to be purged after handling a held message. It scales linearly with how many entries are there in pendedkeyvalue and pendings tables. I was actually browsing through the perf metrics on mail.python.org and found the slowest API response from Core is handling held messages and spent some time last night trying to improve it [1]. The linked MR should significantly reduce the time, although there is more that can be done to make it even better. I haven't had a chance to benchmark my solution yet, but I am hoping it will reduce the latency quite significantly. I'll report on the linked issue [2] after deploying [1] on m.p.o. how much it helped. [1]: https://gitlab.com/mailman/mailman/-/merge_requests/1068 [2]: https://gitlab.com/mailman/mailman/-/issues/1045 -- thanks, Abhilash Raj (maxking)

2 years, 7 months

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

by Mark Sapiro

On 1/2/23 03:54, Onyeibo Oku wrote: > > I pulled the plugs on uwsgi and installed Gunicorn. Gunicorn gave more > mileage but something is still not right. When I visit the mailmanweb > home with a browser, I see the following: > > "Server Error. An error occurred while processing your request." > > Mailmanweb and mailman3 services are running. I perused the log file > at /opt/mailman/web/logs/mailmanweb.log and found the following: > > > raise MailmanConnectionError( > mailmanclient.restbase.connection.MailmanConnectionError: ('Could not > connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', > port=8001): Max retries exceeded with url: > /3.1/lists?advertised=true&count=0&page=1 (Caused by > NewConnectionError(\'<urllib3.connection.HTTPConnection object at > 0x7f7f4b128c40>: Failed to establish a new connection: [Errno 111] > 0x7f7f4b128c40>Connection refused\'))"))') Postorius is unable to connect to Mailman core's REST API. Are your settings for accessing Mailman's REST API correct? E.g., does MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' match $ mailman info ... REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Note the 3.1/ in REST root url is not included in MAILMAN_REST_API_URL. What do you get from, e.g. curl -urestadmin:restpass http://localhost:8001/3.1/lists It should return JSON with information about your lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

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

by Christian

Ok. This is what I am getting in my mail.log: May 17 06:20:40 lists postfix/smtp[28437]: C14F8101260: to=<billb6951(a)gmail.com>, relay=gmail-smtp-in.l.google.com[142.250.114.26]:25, delay=0.45, delays=0.01/0/0.14/0.29, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[142.250.114.26] said: 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: [192.46.218.224]. I have two SPF records in dns for the server as follows: mail v=spf1 mx -all lists v=spf1 ip4:45.79.28.18 -all please advise. Thank you! -----Original Message----- From: Jeremy Stanley <fungi(a)yuggoth.org> Sent: Wednesday, May 17, 2023 7:15 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: spf/dkim/dmarc On 2023-05-17 07:07:53 -0700 (-0700), Christian via Mailman-users wrote: > Thank you for your reply. I'm being driven mad by Gmail rejecting my > SPF record, this while I get SPF record approvals everywhere else. > > I read that having two SPF records for the same server will generate > errors. Is this true? [...] I'm not an SPF expert (I don't even use it for my domains), but I do know how to query standards documents. IETF RFC 7208 "Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1" states in §3.2: "A domain name MUST NOT have multiple records that would cause an authorization check to select more than one record." https://www.rfc-editor.org/rfc/rfc7208#section-3.2 Hope that helps! -- Jeremy Stanley

2 years, 2 months

[MM3-users] Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > > connect to Unix domain socket */run/mailman3-web/uwsgi.sock* > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > uwsgi running outside virtualenv?? I don't think that's a problem, unless also running in a chroot, which would be confusing no matter where uswgi is running. "Cannot connect" might mean - uwsgi is running chrooted, and mailman-web should be looking in /path/to/chroot/run/mailman3-web/uwsgi.sock (mentioned first only because I have chroot on the brain because Debian Postfix config) - uwsgi isn't running (this is my bet, because all the mailman-web URLs except mailman3/ were working and they all go through that socket -- I bet they're not working now!) - /run/mailman3-web/uwsgi.sock got deleted - /run/mailman3-web/uwsgi.sock got wrong permissions - the socket is actually /run/mailman3_web/uwsgi.sock or similar (with an underscore!) and mailman-web is misconfigured But as Mark said, the problem you have with "mailman3/" is urls.py. Personally, I think you *should* do the things that Mark said are unnecessary. He's right, but I strongly prefer to keep all my changes to default configuration in one place, and that's /etc/mailman3 for you if I recall correctly. The very fact that you have /etc/mailman3/urls.py screams "I have changed this file" and that's often useful. Steve

4 months

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

by Mark Sapiro

On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 24 jan 2024, om 12:24 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> het volgende geschreven: >> >> On 1/23/24 05:49, Marco van Tol wrote: >>> Small unfortunate twist, this leads to: >>> --- >>> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >>> --- >>> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? >> >> This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. >> There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. >> >> I use the one from the PR, but it requires a substitution `s/force_text/str/`. > > Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? > > I found a comment on this topic regarding django-4 where they advice to use force_str. > https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… Hm, never mind, sorry. I now see the current file already has str() rather than force_text() in it. Marco

1 year, 6 months

[MM3-users] Re: Posting replies vs starting a thread via email

by Abhilash Raj

On Tue, Sep 3, 2019, at 9:26 PM, paul(a)arenson.org wrote: > In my tests where replies go to the list, when a person uses the email > client? So far a reply to the original message and a reply to a reply > to a reply all go in the same thread. Is this standard? Do I have to > warn users not to have endless Re re re re? Yes, the threading is implemented using a bunch of email headers, especially "In-Reply-To" and "References". If you reply to a message, it will go to the same thread. Did you expect something else to happen? > > And the other question is what happens if a user sends a message via > email with a new subject? Does the list accept it as a new thread? Like I mentioned before, the threading happens with email headers and not using the Subject. So, changing the subject will continue to keep the thread. If you want a new thread, you send in a new email to the list's posting address instead of replying to an old thread. > > This should be one of my last big questions. > > Thank you. > > Paul > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Shashikanth Komandoor

Thank you Mark for you response in time. On Tue, Aug 11, 2020 at 9:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > > I am currently automating a few things using the CURL commands but > only > > postorius related as of now. Now I have a requirement. > > > > I need to create a lot many users and their mapping email ids through > > Site Administration almost daily. But it is becoming to do the same > through > > Graphical Interface. > > > > So, I just want to know the CURL commands that can be used to create > the > > user accounts and email ids mapped to user accounts. > > The accounts you are talking about are Django accounts. You cannot > create these via CURL to the Mailman core REST API. > > You might find > <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. > > -- > 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, 11 months

[MM3-users] MM3 not starting

by Stephen J. Turnbull

max.diener(a)hpi.de writes: > Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo > Aug 22 09:54:12 mailman3test mailman[55146]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags): > Aug 22 09:54:12 mailman3test mailman[55146]: socket.gaierror: [Errno -2] Name or service not known This appears to be a DNS problem, probably for Mailman's host, since it occurs during startup. The following three lines aren't relevant. > Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) > Aug 22 09:55:01 mailman3test CRON[55177]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) > Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): > session closed for user root I'm not sure what timeout is referred to here. > Aug 22 09:55:34 mailman3test systemd[1]: mailman3.service: start operation timed out. Terminating. > Aug 22 09:55:35 mailman3test systemd[1]: mailman3.service: Failed with result 'timeout'. > Anybody knows whats going on and what i am doing wrong? Need more information about your configuration, but it sure looks like there's either a DNS problem or a problem binding to the LMTP port. Not sure what your Mailman is using but I think we normally use the submission port, 587, which is a port for restricted use. Perhaps there's a system security issue, eg, from SELinux. But I would check DNS twice first (unless you're definitely using enhanced security like SElinux). Steve

2 years, 11 months

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

by Abhilash Raj

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

5 years, 10 months

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

by Abhilash Raj

> On Aug 18, 2021, at 1:00 PM, bob B <bader(a)cchmc.org> wrote: > > Thanks, > > but if I put SMTP_HOST: 172.25.0.1 in the docker.yaml, and then down and up (docker-compose down, docker-compose up -d) > the images then container grab a new IP range, (like 172.26.0.X). but my smtphost is 172.25.0.1, so that would break again, correct? That is correct. > What should i put for SMTP_HOST: XXXXX in doicker.yaml to keep this from happening? You can grab a static subnet and assign it to your compose file. This is what old version of the docker-compose.yaml used to do, see this for example https://github.com/maxking/docker-mailman/blob/v0.3.11/docker-compose.yaml#… You probably don’t need to assign static IPs to each container like in the compose file above, since all you need the gateway address to be static to reach SMTP_HOST. > > And are you saying my /opt/mailman/core/mailman-extra.cfg should be > > # cat /opt/mailman/core/mailman-extra.cfg > # mailman-extra.cfg > > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: XXXX(a)XXXX.XXXXX That is correct! -- thanks, Abhilash Raj (maxking)

3 years, 11 months

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

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > My point was after you remove the newly minted mailmandb database and > then create a new blank one, and import into that, you should then run > manage.py migrate to apply any new migrations to the imported database. Ah, right ... ok, I've done that now, and all's good. Actually, I've noticed something related. It looks like the mailman-web container runs manage.py as part of its startup procedure in any event. After the import completes, I start up the mailman-web container and, its logs say this: mailman-web | Operations to perform: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Applying auth.0012_alter_user_first_name_max_length... OK mailman-web | Applying django_q.0014_schedule_cluster... OK mailman-web | Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK mailman-web | Applying postorius.0014_auto_20210329_2248... OK mailman-web | Applying postorius.0015_auto_20210619_0509... OK mailman-web | Applying postorius.0016_auto_20210810_2157... OK If the container is restarted again, it shows that there's nothing to do this time: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | No migrations to apply. These latter diagnostics are also what I see if, at this point, I enter the mailman-web container and run "manage.py migrate" explicitly. I really appreciate the help, thanks so much.

3 years

[MM3-users] Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Odhiambo Washington

On Sat, May 25, 2024 at 5:05 PM <schaefer(a)alphanet.ch> wrote: > Hello, > > I already have some success in auto-migration from Mailman 2.1 (Debian > buster) to Mailman 3 (Debian bookworm), using a new container (not > upgrading the existing installation, which is obsolete e.g. 32 bit x86). I > am doing this using custom scripts. The idea being to be able to import > most of the existing configuration and archives, let the list > administrators test the new system, and progressively advertise this to > users. Then, the old container will be disabled. > > The basic stuff works (From: domain is OK, HTTP transport works, mail go > out, etc) > lsnip] Also, I have a question: if I import my 2.1 config for each ml, will DKIM > work-arounds work (e.g. replace This User <user@domain> by This User > user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some > config changes and also I had to modify mailman using a Debian diversion, > AFAIR. > I remember that when I imported my 2.1 configs to MM3, the DKIM workarounds just worked. -- 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, 2 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

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

by Mark Sapiro

On 9/23/23 02:54, Jana Berger wrote: > > 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. It seems you are saying these messages are valid. I.e. they specify "Content-Transfer-Encoding: base64" and the body is in fact base64 encoded. This is as they should be. > Of course that is not proof, but an indication that it is either done by > the mail server itself or widely across MUAs. As you say, this suggests that some MTA in the path to your user or the user's MUA is responsible for decoding the base64 encoded body but leaving the "Content-Transfer-Encoding: base64" header as is. > 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. The Subject: and body of these messages should be ascii, not utf-8 unless you have something like ``` [language.en] charset: utf-8 ``` in your mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Single Click Unsubscribe

by Mark Sapiro

On 1/25/24 15:21, olebra(a)samfundet.no wrote: > > To me, "subscribed messages" in the above means the policy applies to > everyone sending over 5k emails daily, whether for marketing or not. > > All the best, > Ole > > [0]: https://support.google.com/a/answer/81126 > _______________________________________________ > 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… You can always put something like the above "To unsubscribe ..." line in the lists footer as we do. Gmail's web UI renders that as a mailto: link. Further, at least in some cases, Gmail's web UI recognizes the List-Unsubscribe header in the message and provides it's own Unsubscribe buttons in the web UI. Granted, these aren't truly "one click" as they require confirmation, but that can be avoided by setting a list's unsubscribe_policy to `open`. Also granted that Gmail is the 900 pound gorilla here, but unsubscribe links that don't require confirmation are a bad idea. Even if the link contains some kind of encrypted data to ensure it can't be spoofed, there is still a danger if I forward list mail to a 3rd party and they click my unsubscribe link. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

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

by Mark Sapiro

On 3/13/21 7:08 PM, John Covici wrote: > On Sat, 13 Mar 2021 16:22:59 -0500, > Abhilash Raj wrote: >> >> My guess is that you updated the database (perhaps, by invoking the mailman >> command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes >> up and sees a new revision for the database migration added from 3.3.3 but >> can’t find the same migration in its source (because it is 3.3.2). > > That is sort of what happened, except in the opposite direction, it > was from 3.3.3 to 3.3.2. My question is therefore, do I have to > update this alembic_version when I upgrade mailman to a newer version? > That is what I was getting at. Abhilash's conjecture is that the error was due to a Mailman version accessing a database that had been previously accessed by a newer version so that the version_num in the alembic_version table didn't exist in mailman/database/alembic/versions/. This normally would not occur on an upgrade of Mailman, but if you went from a gentoo Mailman core to a version obtained by pip, it's possible that the gentoo Mailman had an alembic version that wasn't known to the pip Mailman even though the pip Mailman was newer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Installing Mailman3 on Debian Bullseye

by Andy Smith

Hi Franklin, On Sat, Aug 26, 2023 at 04:59:04PM +0800, Franklin Weng wrote: > I had a blog article describing how I did it. Maybe there were something > you find it ridiculous, but they are all what I found important and may not > be shown in the current documents. > > https://blogs.slat.org/node/1012 Having been through this process with Debian 11 last year, in addition to several of your discoveries, I found that the default Whoosh full text indexer was just not usable. It is ridiculously slow and memory-hungry, and used 6+ gigabytes of RAM and days of CPU time to try to index some of my Mailman 2 mboxes. I should think almost everyone will want to switch to Xapian instead. That is accomplished on Debian with: # apt install libxapian30 python3-xapian python3-xapian-haystack and then in mailman-web.py: HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'xapian_backend.XapianEngine', 'PATH': '/var/lib/mailman3/web/fulltext_xapian_index', }, } As far as I understand Xapian is not the default because although Xapian has an open source license, it is one that's not compatible with Mailman's GPL3 license. At the time I installed, Debian 12 had not yet been released, and I won't upgrade that host until necessary, but I personally would not do a new install on Debian 11 so I would want to resolve the problems you had with Mailman 3 on Debian 12. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

1 year, 11 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/22/20 12:23 PM, Ruth Ivimey-Cook wrote: > >> I agree with this, we need a setting for which interface for Gunicorn >> to listen on, and what Mailman Core sends out in the self_link >> attribute when responding to REST requests. >> > Exactly! :-) Except if there were a `bind_host` setting to specify the host to bind the REST API to and you set that to `0.0.0.0` you would have exactly what leads to the situation below, so we need to understand what's happening there (although I think I do - see below). On 6/22/20 12:21 PM, Ruth Ivimey-Cook wrote: > > I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and > changing the cfg file hostname back to the full name of the host, and > that now works!! -- in that the problem I showed earlier is gone. > > > However I then get another issue. From the mailman.log file I now see in > the last few lines. For clarity I've numbered them like this "{1}": > > {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" > "GNU Mailman REST client v3.3.1" > {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk > HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" > {3} [22/Jun/2020:00:58:24 +0000] "GET > /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > At this point the browser screen reports "Something went wrong" and the > message "HTTP Error 404: {"title": "404 Not Found"}" Tracebacks would really help. You should be able to find them in the log configured as LOGGING['handlers']['file']['filename'] in your Django settings. > Previously, the process stopped at line {1}. Now that and line {2} is > executed (AFAIK) correctly, but then line {3} is isssued. I have no idea > why something is looking for "domains/greyarea-web1": > > - Only the "ch-bc.org.uk" domain is listed in the reply to line {1}, as > expected; Go to your Django admin web UI and look at your Django Mailman 3 Mail domains. This will be at a URL like https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ Do you see this domain there? If so, delete it. > - "greyarea-web1" doesn't appear in any lists I can show with the > "mailman" cli command (and I think I tried them all); But that's looking at Mailman core which is not where Postorius is getting this list. > - "greyarea-web1" doesn't appear anywhere in the source or config other > than as the name of the host its running on or as an ALLOWED_HOST; > > - I tried using "curl -X DELETE" (from the api docs) to delete a domain > called that and it says no such list exists. Again, you're talking to core, not Django. > My only possible clue is that I think, at some point in the journey of > configuring mailman, I might have created a list called that on the > host. However since then I have wiped the install files and reinstalled. > I cannot make sense of this being the answer given the checks just listed. Did you wipe the database on greyarea-web1? > I went looking through the python source and can see that the get() > function does indeed throw a 404 exception if the domain isn't found, > but I cannot see which code is parsing the reply from the first line > > So I have two questions: > > 1) How can I fix this problem? See above. > 2) why does getting an 404 reply here cause the postorius web page to > produce a "something went wrong" /404 and nothing else, when it could > have simply reported that something had gone wrong with one specific > domain; Because the code isn't robust enough :( ... > Ideally, and this is icing on the cake, a listen address specification > should allow multiple IPs to be passed in, in which case the server > listens on all of them. I expect the python libraries already support this. We could implement a bind_address setting that would pass to gunicorns --bind parameter anything acceptable to gunicorn, although multiple values are tricky as they apparently require multiple -b/--bind options and a single -b/--bind doesn't support a list of values. But, I'm not convinced that this is something anyone needs. I'm still waiting for a response to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/19/21 1:26 PM, Sarah H wrote: > I think you've just hit the nail on the head as far as my biggest issue with this project. The documentation lays out an install method that should be roughly followable for anyone (though it needs a bit of fine tuning here and there) and then the rest of the configuration guide and documentation assumes that you have installed the software in a completely different way and doesn't work the same as the guide laid out. Because virtually all that documentation was written by different people and long before the https://docs.mailman3.org/en/latest/install/virtualenv.html was added. > The documentation should be uniform, if you want users to install it one way then write the guide and documentation so that's the "default". Sure present alternatives or notes "if you've installed via git, your commands will look like this xxx" but ultimately the biggest issue I've had with getting this deployed is inconsistent or lacking documentation. I'm not trying to make excuses. I know the docs need improvement, but we are a very small, all volunteer project doing the best we can. If you feel you can offer improvements to the documentation, we'd love to have your help. You are more than welcome to submit merge requests to update the docs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: DKIM header not added to subscribe/unsubscribe notification email

by Philip Colmer

On Fri, 19 Aug 2022 at 18:11, Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > My guess is that the address Mailman uses for From in those messages > is not in OpenDKIM's SigningTable. This is probably the > $LIST-owner@$LISTDOMAIN address. You should also add the > mailman@$LISTDOMAIN address. > Thank you - it was precisely this bit (the Signing Table) that I was missing. Adding that configuration has fixed it. > Neither can we, although for a different reason. ;-) Please don't > hesitate to send full configuration files to us on the grounds of > absolute size or bandwidth. Such reports are relatively rare, they're > not actually that big, and almost everybody on our lists are admins > who know that it could be them tomorrow. Unfortunately at present I > don't think you can send it as attachments. > > If you're worried about system security, you can either redact > sensitive information such as passwords, domain names, mailboxes, and > IP addresses, or you can send it to one of the developers directly > (me, at the moment; Mark, when he gets back in a few weeks -- I > believe Mark prefers a zipfile if there are multiple files, and I know > I do) if you're willing to trust us. > Thanks, Steve. I appreciate that gesture. Thanks again for your help. Very much appreciated. Regards Philip

2 years, 11 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Jered Floyd

> Consequent upon this django-allauth issue and the previous issue > with psycopg2, how likely is it that new MM3 installations will suffer the > effects? > I am asking because I am doing my tests on a relatively vanilla system and > just following the official documentation sin any deviations. The allauth issue will happen until the allauth package is patched. Mark's patch was merged yesterday, so I suspect a new release will be imminent. I've noticed the django-allauth ecosystem seems to be somewhat prone to breaking changes. I'm sure this discussion has happened before, but it may be worth pinning "known good" dependency versions for django-mailman -- either in the project, or in your documentation. It's definitely a headache for me since I rebuild my mailman container roughly weekly, and always need to allow time for functional testing or rollback to my last image. There's not really a right answer here; either dependency versions are left open and the end user gets security updates for dependencies on their own schedule, or the Mailman maintainers have to monitor for security updates in the dependency tree and push a new mailman release. (This can also help ameliorate supply-chain attacks where an unverified update ends up in PyPI, but I'm not sure that's a realistic threat model for us.) I'm sure this is something the maintainers have considered in the past. --Jered

1 year, 9 months

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

Well ... each list has 9 email addresses — the list address, the -bounces, the -confirm, the -join, the -leave, the -owner, the -request, the -subscribe and the -unsubscribe ... I think I'm around 4500 listservs right now..... Anyway, as Mark explained in his most recent replies, the alias domains were not setup correctly, so that needs to be addressed, but I didn't see that his solution would reduce the number of lmtp entries ... Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Ron <admin(a)bclug.ca> Sent: Thursday, June 26, 2025 14:40 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. Hirayama, Pat wrote on 2025-06-26 11:37: > Everything else seems to be working — there are over 40k lmtp: entries in postfix_lmtp, and messages are being delivered. Apologies for "butting in", but >40,000 entries in LMTP? That seems like a bit excessive. Is it due to a failure of my imagination or could there be something (unrelated) awry here? _______________________________________________ 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 month, 1 week

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

by Mark Sapiro

On 04/23/2018 02:59 PM, Darren Smith wrote: > Well, using the mailman shell we were able to find the request that was > causing the problem - it was apparently a spam message that had some > chinese characters in it. I am trying to duplicate this issue in a test environment. I can create a message with an invalid RFC 2047 encoded subject, i.e., Subject: =?gb2312?Q?=ff=fe=de=21=a2?= and send it to a list where it gets held, but I don't get a 500 in postorius and I see the held message with a raw (not decoded) header. I think there were some recent changes that affect this. I'll look some more. > We used the shell to delete the held request... > > And postorius is still giving me an error 500. > > If I'm not mistaken the held messages are kept in .pck files - do you know > if when postorius asks for held messages through the API, does mailman go > to the database or to the .pck? I would actually suspect the latter, or > removing the request should have fixed the problem. They were held in .pck files in Mailman 2.1, but not in Mailman 3. They should just be in the database and deleting them via mailman shell should delete them as long as you quit the shell or commit(). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

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

by Mark Sapiro

On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote: > I added the additional hosts to ALLOWED HOSTS in settings_local.py and > mailman is distributing mail to subscribers again. However, I then received > many emails of valid users subscriptions being disabled. What would cause > that? Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users(a)mailman3.org/threa… > Can subscriber management be done via command line? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… for description of the available mailman subcommands. If you are interested in re-enabling delivery for members whose delivery is disabled by bounce, you can do this fairly easily in an interactive `mailman shell` session. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… Something like the following session: ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print("Re-enabled delivery for bouncing member {} on list {}" ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() ``` -- 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: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Mark Sapiro

On 5/7/23 10:51, Volkmar Grote wrote: > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: >> >> >> Page not found (404) >> >> Request Method: GET >> Request URL: >> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >> >> ... > > Nginx, /etc/nginx/conf.d/me.domain.de.conf >> server { >> listen 80; >> listen [::]:80; >> >> server_name me.domain.de; >> ... >> location /static/ { >> alias /opt/mailman/mm/static/; >> } > > Again, many thanks in advance for any clue The above in nginx is correct, but you aren't getting the static files via nginx. You need to go to a URL like http://me.domain.de/postorius/lists/. Going to http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi server and doesn't involve nginx at all. You need to go to port 80 where nginx is listening and nginx then proxys requests to 127.0.0.1:8000. Do you also have location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } in /etc/nginx/conf.d/me.domain.de.conf. You need that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Tue, 8 Jan 2019 at 16:58, <brian(a)emwd.com> wrote: > Odhiambo Washington wrote: > > So you just added: > > - stop_grace_period: 30s > > > > to the block?? > > I actually did not add it. It was already there from the docker files that > I pulled from: > > https://github.com/maxking/docker-mailman That's odd, because I also pulled the same file, but it doesn't have it. > > > > > > I don't know if that setting makes any difference. I am also > > > using the > > > included postgres database instead of mysql. > > > > > > For the mailman-web section, you need to add the following: > > > > > > - SERVE_FROM_DOMAIN=yourdomain > > > - MAILMAN_ADMIN_USER=youruser > > > - MAILMAN_ADMIN_EMAIL=youradminemailaddress > > > > > The mailman-web section has sub-sections. Under which one do I add > > these? environment?? Or networks below the IP address? > > Under the environment sub-section. > Added those now. > > > I have apache2 and nginx on the server. Apache listens on 80 and 443 > while > > nginx listens on 8080 and 8443. > > I won't be of much help here I am afraid. My server is just using nginx. > Well, I suppose https://FQDN:8443/something should lead to the MM3 web UI?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 6 months

[MM3-users] Re: How to modify system preferences

by Allan Hansen

The other way is to tell all your users to use gmail, as that is how they handle messages from email lists, no matter how much I and others have complained to them about it. :-) Yours, Allan Hansen hansen(a)rc.org > On Feb 19, 2021, at 9:50 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/19/21 5:15 AM, Jack Lenox via Mailman-users wrote: >> >> The documentation states that these are only accessible in a read-only >> format via the REST API, but presumably there is a way of modifying >> these somewhere? I can't find a way of specifying this in my config and >> can't find a relevant example in the sample schema.cfg. >> >> At this stage, all I want to do is set the default for >> "receive_own_postings" to False. Can anyone point me in the right >> direction here? > > > The defaults for settings like this are not directly configurable. You > need to patch the relevant entry in mailman/core/constants.py > > I have just filed <https://gitlab.com/mailman/mailman/-/issues/832> for > this. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

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

by Simon Coggins

On 5 Nov 2021, at 6:30 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. That should work well. I’m happy to do some testing of any patches you create in our test environment if you need extra testing. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> —Simon

3 years, 8 months

[MM3-users] Linking to a forum thread from a (news) website.

by Paul Arenson

I have been struggling to get this right and I think I have finally done it. I have a website with many opinion and news articles. I have linked from the article to a pre-written thread, such as from here: EXAMPLE WEBSITE ARTICLE https://www.tokyoprogressive.org/remembering-the-tsushima-maru-disaster-75-… to EXAMPLE THREAD ON LIST Title: Remembering the Tsushima Maru Disaster 75 Years Later https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… PROBLEM The problem is that this does not show the subsequent comment that was added. And SHOW REPLIES BY DATE does not do it either. SOLUTION I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. So if I click https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… you will see all the subsequent posts. Since I want to post a link BEFORE anyone starts replying, I have to make my first post in the thread titled Re: EXAMPLE OF NEW POSTING STYLE Make sure the thread has a Re: in it. (Actually I made a mistake and wrote Re; and it still worked.) https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… Or: https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… ----------------- QUESTION Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? -----------------

5 years, 10 months

[MM3-users] Re: Changing default message limit (max_message_size)

by Abhilash Raj

On Mon, May 27, 2019, at 8:23 AM, Mark Sapiro wrote: > On 5/27/19 12:05 AM, roger(a)reasonal.com wrote: > > I found the field in settings that would appear to do this, but it just throws an error for whatever I give it ("An error occured**: Unknown attribute: max_message_size"). > > This should be fixed at > <https://gitlab.com/mailman/mailman/merge_requests/329>. > > Perhaps you need to update your Docker images > <https://asynchronous.in/docker-mailman/> That's right. You are probably using a new version of Postorius but not of Mailman Core. Please make sure the container images you have are updated. > > Also, see > <https://gitlab.com/mailman/postorius/issues/246#note_69323948> for a > not about changing this via `mailman shell` (withlist), but see the > subsequent comment about `quit()` > > > > PS As a suggestion, may be a good idea to indicate what units it's expecting... bytes? kB? Nybbles? > > Reported at <https://gitlab.com/mailman/postorius/issues/362>, thanks. > > > PPS ** Psst: occurred with two r's... > > Reported at <https://gitlab.com/mailman/postorius/issues/361>, thanks. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: exposing Mailman3 API securely

by Abhilash Raj

On Mon, Jul 8, 2019, at 3:12 PM, dancab(a)caltech.edu wrote: > I'm working on a container based Mailman3 solution for my university. > We have a help desk tool which needs to access the API remotely for > creating and deleting Mailman lists. The API will be restricted to a > private network, behind a firewall, etc. > > What is the simplest way to expose the API to an external host? I do want to stress the fact that we wouldn't advise exposing the API to internet since there is a very basic authentication in the API an the API is an administrative API. > > At the moment, I seem to have this partially working via an Apache > virtual host configuration which simply proxies via > api.example.edu:80 to localhost:8001 on the container. > > I'm able to remotely use the mailmanclient module for the client.lists, > client.system and client.members commands. However running > client.domains generates an API connection error. So it seems unstable. Does it *always* happen when you run `client.domains`? Did you get an error traceback? > > Any thoughts or suggestions? > > Thanks. > > > ---- > Dan Caballero > Systems Administrator > Academic Computing Solutions > IMSS - Caltech > https://imss.caltech.edu > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Gilles Filippini a écrit le 15/06/2020 à 22:05 : > Mark Sapiro a écrit le 15/06/2020 à 21:58 : >> On 6/15/20 12:37 PM, Gilles Filippini wrote: >>> >>> There are 4 emails stored into this folder. 3 of them are spam, and the >>> last one is a legitimate email. This is annoying that such emails could >>> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >>> more and more hyperkitty errors. >>> >>> Any idea how to make their processing more error proof? >> >> >> Change the offending .encode() method to add errors='replace'. >> >> The traceback from the error should tell you where it is. >> >> You could also open an issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If >> you do that, please include an error traceback if possible. If there is >> not a traceback in mailman.log associated with the error, there might be >> one in HyperKitty's log (configured in Django's settings). Also, >> including enough of a message to duplicate the issue is very helpful. > > I've now deleted the offending messages. Will open an issue with related > details the next time this error occurs. I've experienced this error again today. Filed issue #301. Thanks, _g.

5 years, 1 month

[MM3-users] Re: disable body transcoding

by Mark Sapiro

On 9/22/21 9:02 AM, Markus Schaaf wrote: > Hi, > > I have disabled all message modifications and filtering from within the > webUI, and created empty header and footer template files. Still, some > list messages get their body encoding changed to base64, breaking DKIM. > What can I do to prevent this? (I'm a newbie to mailman3, so please give > somewhat complete commands. I have read other threads with similar > questions, but did not understand some shortened configuration commands.) This is probably due to the message body charset being utf-8. The Python email library used by Mailman encodes utf-8 message bodies as base64. There are no configuration settings in Mailman to avoid this. Calling email.charset.add_charset('utf-8') at some point in Mailman's processing might avoid this. E.g. ``` --- a/src/mailman/handlers/validate_authenticity.py +++ b/src/mailman/handlers/validate_authenticity.py @@ -23,6 +23,7 @@ import logging from authheaders import authenticate_message from authres import AuthenticationResultsHeader, SyntaxError from dns.resolver import Timeout +from email.charset import add_charset from itertools import chain from mailman.config import config from mailman.core.i18n import _ @@ -121,5 +122,7 @@ class ValidateAuthenticity: def process(self, mlist, msg, msgdata): """See `IHandler`.""" + # Try to avoid base64 encoding of utf-8. + add_charset('utf-8') if config.arc_enabled: authenticate(msg, msgdata) ``` Note this is just a guess and could be a disaster so test it before trying it in production. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Apache Conf

by Thomas G

Hi tried both. Same result. xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > Hi, > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > I tried to do the same with Apache, but the statics files are not > > delivered (404). > ... > > <VirtualHost *:80> > > ServerName mailing.ddd.fr > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > <Location /static/> > > Alias "/opt/mailman/static/" > > </Location> > > > > <Location /> > > ProxyPass http://localhost:8000/ > > ProxyPassReverse http://localhost:8000/ > > ProxyPreserveHost On > > </Location> > > </VirtualHost>/ > > > In Apache, location > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > appropriate for resources in the file system. > > Try > > Alias /static/ /opt/mailman/static/ > > not within a location block. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 9 months

[MM3-users] Re: Verification Failed Error

by Odhiambo Washington

On Fri, 21 Dec 2018 at 15:00, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> 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? > > Steve > > Hi Steve, I will handle the Exim bits for him! I am familiar with Exim, so I will be able to help him overcome all the errors. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 7 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Sun, 6 Jan 2019 at 18:55, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/19 6:54 AM, Odhiambo Washington wrote: > > > > If I could run MM3 using the apt-get install method, perhaps that would > > have made my life a bit easier, hoping that MM3 can actually be run in > > parallel with MM2.1 on the same host. Is anyone doing that already?? > > > Yes. I am on two production and one development machines. See, e.g. > <https://mail.python.org/mailman/listinfo/> and > <https://mail.python.org/mailman3/> > > One caveat here is I install both Mailman 2.1 and Mailman 3 from source > on all these machines. I don't know for example if the Debian/Ubuntu > packages play well together. > On my Ubuntu machine, I decided to install MM21 from source so I am willing to install MM3 either from source, package or docker. The sparse documentation is my undoing. > > See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > for more on how I install MM 3. > I have seen that link, but it's missing a ton of details within the process. As I mentioned before, these virtualenv stuff are new to me too, so I thought dockernization would simplify things. If you could include the missing steps that you left out then I could possibly be able to follow the steps :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 6 months

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

by Stefan Bauer

Hi Steve, thank you for your time. Thats it :) Works now. I had to set it in /etc/mailman3/mailman-web.py After first logon, django tries to send a mail to confirm email address. Nov 10 08:44:56 mal02 postfix/qmgr[2893767]: 9255C5E0BE2: from=<postorius(a)lists.mydomain.tld>, size=920, nrcpt=1 (queue active) Nov 10 08:44:56 mal02 postfix/smtpd[879486]: disconnect from localhost[::1] ehlo=2 *starttls=1* mail=1 rcpt=1 data=1 quit=1 commands=7 This now works with STARTTLS. Hoooray :) Am Di., 9. Nov. 2021 um 16:50 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > No matter what i try, mailman still only connects without STARTTLS: > > Earlier you wrote: > > > SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a > STARTTLS command first', 'postorius(a)lists.mydomain.tld') > > Request Method: POST > > Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ > > Django Version: 2.2.12 > > This looks like Django errors, not Postorius (Mailman). So this is > something Django is doing, not Mailman (including Postorius). I'm not > sure why Django is sending email (somebody made a password reset > request seems likely, but I'm not that familiar with Django authn > stuff). Anyway, if it's internal to Django, it would not consult > Mailman's configs. This recent StackOverflow seems relevant: > > > https://stackoverflow.com/questions/60025730/530-5-7-0-must-issue-a-starttl… > > HTH > > Steve > >

3 years, 8 months

[MM3-users] Re: Problem creating list members using REST API

by Mark Sapiro

On 1/18/22 2:11 PM, Stephen Daniel wrote: > The REST API documentation is a bit informal. As someone who is not > familiar with mailman, and who doesn't know python, they are a bit of a > slog. Agreed. I guess we sort of assume that people dealing directly with the REST API are familiar with both. > It might be worth seeing if the code can be enhanced to allow the boolean > values to be sent in using JSON booleans as well as JSON strings. I think here we only have to deal with the REST API because other uses of as_boolean are all on strings that come from config files. We can't modify as_boolean directly, as it is part of a third party dependency and is intended to be used with config files, not JSON objects, but I think something like this will do it. ``` --- a/src/mailman/rest/helpers.py +++ b/src/mailman/rest/helpers.py @@ -249,6 +249,8 @@ class GetterSetter: """ if self.decoder is None: return value + if self.decoder is as_boolean and isinstance(value, bool): + return value return self.decoder(value) ``` Perhaps you could try to test that. I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. It would help me in fixing this if you could provide a small piece of your code that throws the error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Python program to create lists and import settings from Mailman 2 to Mailman 3

by Greg Newby

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

11 months, 3 weeks

[MM3-users] Re: Shorted Subjects in Mailman

by Stephan Krinetzki

Victoriano Giralt wrote: > On mar, 2022-07-26 at 10:09 +0000, Stephan Krinetzki wrote: > > Hi, > > Hi, > > i tried now with a Postfix 3.x -> Mailman > > Postfix has en extremely useful setting called debug_peer_list where > you can list addresses of machines whose messages you are interested in > and the level of detail can be set with debug_peer_level. this will > result on very detailed logging of the SMTP conversation. > But, before resorting to this very invasive method, I'd put messages on > the HOLD queue and inspect them with postcat, before releasing them to > be passed to Mailman. this way, you will be able to see if the subjects > are cur "before" reaching Mailman. > > Original to Mailman: https://pastebin.com/c4BHeEkJ > > Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV- > LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?= > > After Recieving: https://pastebin.com/JG0NKbjq > > Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV- > LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?= > Both of then show the same Subject: header. In https://pastebin.com/c4BHeEkJ, Line 79+80 it says `Subject: [SAV-LINUX] Notice from Sophos Anti-Virus on server.example.com [DEMO1]` So this correct. in https://pastebin.com/JG0NKbjq, Line 177 its truncated `Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV-LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?=` So my guess is, that the local Postfix on the Mailman Server is doing the QP. In the Chain there are postfix 3.x -> MS Exchange -> Postfix 2.x -> Mailman After Releasing the mail from hold Mailman -> Postfix 2.x -> Exchange Regards Stephan

3 years

[MM3-users] 120 gmail users removed from lists !

by Stephen J. Turnbull

elemac(a)free.fr writes: > Hello, on 15th October, 120 users with gmail address where suddenly > removed from lists in mailman3, something changed in google ? Google is evil, who knew? Google decided to publish a DMARC policy of "p=none". This announces to the world that you have to decide for yourself whether to accept mail from Gmail with a broken DKIM signature from gmail.com. Gmail has decided that they will not accept such email from themselves, even though they know more about the sender than anyone else, and even have access to the original sender copy. Mark has a patch that applies your preferred DMARC mitigation to Gmail authors unconditionally. I think it's in the new version just released 3.3.9, so you can upgrade. The name of the variable is dmarc_addresses, and in Postorius it will be in the same settings group as other DMARC settings, with a similar tag. If for some reason you strongly prefer not to upgrade immediately but want this feature, it's commit #8532f751b6b8bfee3210c1327d755756f99d99ac (you can shorten that to 8532f). I do not recommend this. It probably is independent of other changes in 3.3.9 from other releases. But if not you could have issues. I think you also need the patches in Postorius, but I don't think they've been released yet. "Coming soon" as they say. The relevant commit is #770add1ebf27fd335c675607f26bb8f7cf313ddd, If you search back in the archives, I think Mark posted a link to his original patches. Steve

1 year, 9 months

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Thu, Dec 20, 2018, at 10:25 AM, brian(a)emwd.com wrote: > 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 The documentation at Github does makes reference to it. It might not be in the most visible manner, which I have opened an issue to fix[1] > To configure the mailman-web container to send emails, see these configuration settings. The documentation also mentions about the Django configuration file, settings_local.py (which is imported by settings.py at runtime). [3]. I have opened another issue to make that clear as well. [2] You can add all your Django related settings in `/opt/mailman/web/settings_local.py` if you using the images and docker-compose.yaml file from the above mentioned repo. [1]: https://github.com/maxking/docker-mailman/issues/277 [2]: https://github.com/maxking/docker-mailman/issues/278 [3]: https://github.com/maxking/docker-mailman#configuration > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/15/19 3:45 AM, Wolfgang Bock via Mailman-users wrote: > > That doesn't solve the problem. I changed that in mailman-web.py > (MAILMAN_REST_API_URL = https://localhost:8001) and after that in > mailman.cfg (use_https: yes). But got the same errormessage on postorius > website. You posted this log excerpt: Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type The first 3 GETs are a normal sequence of GETs from Postorius when you go to the Mailing Lists view. That should be followed by a GET like "GET /3.1/domains/domain.tld HTTP/1.1" where domain.tld is a configured domain. Do you have any domains configured?/0.9'? I'm not sure what the issue is. You have an older version of mailmanclient < 3.2.3a1 which uses httplib2 rather than requests. https://pypi.org/project/httplib2/ says: HTTP and HTTPS HTTPS support is only available if the socket module was compiled with SSL support. but I don't think this can be the issue because the first 3 GETs work. You might try upgrading mailmanclient to 3.3.0. I don't know if that will help, but it may. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 6/30/20 7:03 AM, Brian Carpenter wrote: > On 6/30/20 9:56 AM, tom(a)gather.coop wrote: >> I have a Mailman 3 server up and running but I'm terrified to migrate >> to it from my existing Mailman 2 provider for fear that services like >> Gmail will randomly start blacklisting my IP with little I can do >> about it. I have SPF records set up so I'm hoping I'll be Ok but I'd >> like to have a backup plan. ... > There is no reason to be afraid if you are sending out legitimate > communications. SPF records will help. You will also need to enable > DMARC mitigation on your lists and Mailman 3 does that very well as > Mailman 2 did. It also helps if you sign your outbound mail with DKIM. > With those 3 things in place, you should have no problem sending mail. > Keep in mind AT&T will probably block you if the IP address you are > using is new. That is standard practice for them. It's easy to get that > block remove. Same goes for Comcast using their Vader RBL. You also need to ensure you have full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. That together with SPF and DKIM signing of outbound mail is virtually essential for deliverability. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Strange password problem

by Eggert Ehmke

Hello Steve, my configuration is very much like the one described by Roland. Am Samstag, 23. September 2023, 13:02:46 CEST schrieb Stephen J. Turnbull: > Eggert Ehmke via Mailman-users writes: > > So for now I use the same password for all logins, and that > > works. But is that a good solution? The other option would be to > > assign multiple superusers for each domain, but they would still > > allow to log in via some other domain. > > If you own the domains, you can probably set up some sort of > trivial website on each that does nothing but admin stuff, with the > same database backend. Then you can have different passwords for > "admin" and the browser will remember them. > > Probably more tricky than it's worth. I have already URLS like lists.domain1.tld lists.domain2.tld ... not sure what you mean. > What are you doing that requires admin privileges, but you want to > authenticate separately for each domain? I ask because we've always > envisioned creating a domain-level administrator role, but until now > we've had no demand for it. I just thought it would be cleaner to have separate accounts for each list. Now I understand that the superuser has privileges on all lists. I also have a setting so that on each URL only the lists are visible that belong to that domain. Sadly I don't remember the setting, but that works. Cheers, Eggert

1 year, 10 months

[MM3-users] Clearing webserver cache - Nginx

by Odhiambo Washington

I am having an ugly-looking https://mm3-lists.kictanet.or.ke/archives/ page because of cached content: ``` 2024/08/05 17:00:31 [error] 694#694: *9562 open() "/opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No such file or directory), client: 172.70.111.39, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.6dab123e4897.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" 2024/08/05 17:00:31 [error] 694#694: *9564 open() "/opt/mailman/mm/static/CACHE/css/output.158acc288604.css" failed (2: No such file or directory), client: 162.158.159.31, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.158acc288604.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" 2024/08/05 17:00:31 [error] 705#705: *9566 open() "/opt/mailman/mm/static/CACHE/js/output.3aaa7705d68a.js" failed (2: No such file or directory), client: 162.158.63.166, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/js/output.3aaa7705d68a.js HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" ``` That IP address appearing there is not my actual IP, but Cloudflare's, which is acting as proxy for the site. Having cleared MM3-web cache, is there anything else I can easily do (apart from disabling CF proxying) to help deal with the above issue? Or am I barking the wrong tree? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 4 weeks

[MM3-users] Re: error changed after restart

by Abhilash Raj

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

4 years, 5 months

[MM3-users] Re: Subscribe only to one thread

by Terri Oda

We've already got the code for it. It was the "dynamic sublists" project. Systers built dlists for their needs with mailman 2 and we had a student implement it on mailman 3. The problem has just been in getting the patches integrated, which was mostly on me not being able to follow through at the critical time (as opposed to there being technical reasons it wasn't done). I still don't have the volunteer time necessary to port them forward to the latest version of mailman now and do the integration, but would be happy to help answer questions if someone else is interested in working on it. Terri On May 7, 2018 12:59:32 PM PDT, Ivan Perez <ivanperezdominguez(a)gmail.com> wrote: >Dear Mailman users, > >There are many high-traffic mailing lists in which I would only be >interested in receiving messages in specific threads (not all messages, >nor >some topics, nor a daily digest). > >Is there a way of "subscribing" to individual threads only, mainly >those I >initiate, or I actively participate in, but generally not receiving any >emails from the list? > >If not, would others find this useful, and could it be implemented? (I >understand that everyone wants features; I just don't know if it's a >2-hour >patch or a 2-month project). > >Best wishes > >Ivan >_______________________________________________ >Mailman-users mailing list >mailman-users(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 2 months

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 15:49, Christian via Mailman-users wrote: > Mail.log > > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from > box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: > client=box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: > header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; > from=<christian(a)naturalintelligence.us> > to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP > helo=<box.ecovillage.cc> > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: > message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: > from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from > box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: > to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces(a)lists.ccalternatives.org? 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? -- 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: HyperKitty misreporting statistics

by Cameron Smith

Abhilash, I think the location of the message, in the error log, is correct: in the uwsci-cron.log, the entries show that the “minutely” jobs run for 32-33 seconds, whereas the entries in the error log show the jobs as running for only 2 seconds, suggesting an error. (As an aside, what is “minutely” doing that takes 32-33 seconds?) How best can I diagnose the problem? If need be, I can simply tear down the whole system, including deleting /opt/mailman on the host, start again and see if the problem persists. I think it would, however, be more helpful if we could figure out what has gone wrong. > On 2017.08.20, at 14:34 , Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Sun, 20 Aug 2017 08:38:53 -0700 > Cameron Smith <ccsmith(a)cetsi.com> wrote: > >> Hmm… something is definitely not right. >> >> /opt/mailman/web/logs/uwsgi-cron.log has not been updated since Aug 11, which is when I installed the container images 0.1.1. However, /opt/mailman/web/logs/uwsg-error.log is being updated every minute with entries similar to this: >> >> Sun Aug 20 13:40:00 2017 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 123) >> [uwsgi-cron] command “./manage.py runjobs minutely" running with pid 123 exited after 2 second(s) > > > This seems like a bug in the uwsgi configuration, it should actually go to > uwsgi-cron.log. I have opened a new bug[1] to track this problem. > > [1]: https://github.com/maxking/docker-mailman/issues/119 > Cameron Smith

7 years, 11 months

[MM3-users] Re: Mailman3 and Exim setup

by Stephen J. Turnbull

brian(a)emwd.com writes: > Ok, since you wrote the documentation and specifically had exim > preconfigured, I was hoping for a more definitive answer than "I > think". I am not trying to be difficult here but the installation > support, both via the documentation and the forum has been less > than stellar. I got Discourse up and running with far less hassle > than Mailman3 and from what I can see, it is a more feature rich > app. Sure, but from the point of view of its network configuration I suspect Discourse is far less complex than Mailman 3. There's been a fair amount of effort put into "literate programming", so most things *are* documented, but the organization of the documentation reflects the source organization, not that of the user/admin interface. Please do keep the doc bugs coming. > Would it be easier to try get Mailman3 setup with Postfix than > Exim? Possibly if you install from source on a single host, the overall experience would be less frustrating, Postfix or Exim. Don't know if that's an option. Also, if you run into issues down the road there is relatively more expertise in Postfix here, I believe. For real MTA help, I don't know whether the upstream projects are comparable. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 7 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/28/20 10:20 AM, Shashikanth Komandoor wrote: > > I tried for the command to know if any entry in the "address" table for > which 'id' is not an integer. > > But unfortunately, I could not get any command or idea how to find that. > > But out of my extra talent, I tried the below commands which, I thought, > may print the records which contain a non integer id value. ... > select id,email from address where id NOT BETWEEN 1 AND 84203; > id | email > ----+-------(0 rows) > mailman=# select id,email from address where id NOT BETWEEN 1 AND 84202; > id | emai> -------+-----------------------------> 84203 | user(a)exampl.com > > *1 and 84203 are the minimum and maximum values of the id:* > > Please see the above outputs and suggest if anything possible or please let > me know the command what should I run to find a non integer id value. > The above looks qood to determine if there is a non-integer value. > I also doubt this error as if my REST API is contacting postgresql in a > delayed manner. If possible, can you say what optimal setting I can do at > Postgresql so that faster responses would be given to REST API. I'm out of ideas. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

Bob, Can you run the command "sudo docker logs mailman-core" and see what the end of that says? Another good command to run is "sudo docker ps" and make sure the mailman-core container is actually running. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, August 11, 2021 1:25 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: > DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: > DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost > connection with 127.0.0.1[127.0.0.1] while receiving the initial > server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 11 months

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

by Allan Hansen

Sure: >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... >>> Nothing here, either. Yours, Allan On 9/17/22, 10:30 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- 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/

2 years, 10 months

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

by Mark Sapiro

On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > --------------------------------------------------------------------------- > First issue:Postfix v3.5.8 on RHEL 8. > The below is from journalctl -xe: > --------------------------------------------------------------------------- > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > directory > > I manually created the var_dir: /opt/mailman3/mm/var directory > specified in the mailman.cfg file. > How do I find out how to populate the postfix_domains.db files, and > the postfix_lmtp.db file? The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. > --------------------------------------------------------------------------- > Second issue: Postgresql authentication. > PostgreSQL v10.23. > --------------------------------------------------------------------------- > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > same complex password in the mailman3 config file: > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 I don't think you should have two /mailman3 at the end the form is `postgresql://user:password@host:port/database_name` The default port is 5432. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[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: > > When Digest Size Threshold is not reached, mails seems to be sent > > according to digest_volume_frequency': which is set to 'monthly'. The web > > interface doesn't seem to have a setting for this. > > No. digest_volume_frequency only controls how often the digest volume > number increments (and issue number resets). > > In order to send periodic digests, you need to run 'mailman digests > --periodic' via cron. Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). As I understand, using --sent should send a digest immediately (except when used with --dry-run). As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? -- Henrik Rasmussen

6 years, 9 months

[MM3-users] Re: Is it possible to add non-members in regex format in Mailman 3 ?

by Abhilash Raj

On Tue, Jun 16, 2020, at 7:09 AM, Shashikanth Komandoor wrote: > Hi Team, > > In mailman 2, I was able to add the non-members in the > respective privileged box even using the regex also which will be used to > add the domains instead of a single mail id. > > But in mailman 3, I am not allowed to add the non members in > the regex format. Of course it is allowing me to add individual mail ids > and give permissions. But I want to add a non-member which may be something > like the entire cisco.com domain on which I want to set the rule. > You can do that with Postorius 1.3.3 (which was released recently) and Mailman Core 3.3.1. > Please help me out by suggesting over this or if mailman 3 is > not providing then please hint me out with a work around at least. > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Moderation of posts via email is not working in mailman 3

by Shashikanth Komandoor

Thank you Mark Sapiro for your response. After going through the discussion at the link you provided, I understood as of now, it is not possible to moderate the posts through the mails in Mailman 3. But since the user is getting the "confirm" attachment to the mail, the users are getting confused. Is there any work around to achieve this? or Is there any way to remove that "confirm" attachment so that users would not get an idea of confirming via email? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 30, 2020 at 2:46 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/29/20 12:24 AM, Shashikanth Komandoor wrote: > > > > Is there any bug or limitation in mailman 3 or if I am doing > > any wrong at the server side? Please suggest. > > > > This is a known issue in Mailman 3. See > <https://gitlab.com/mailman/mailman/-/issues/169>. > > -- > 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

5 years, 1 month

[MM3-users] Getting connection timed out

by blackout69

Il 22/05/21 23:52, Mark Sapiro ha scritto: > It's probably not blacklisting. It's not getting that far. Your `glugct` > is attempting to connect to port 25 at mail.simail.it and the connect is > not being answered. Normal blacklisting will not occur until after the > remote MTA answers the connect and determines the IP of the caller. And > in any case, if it is some kind of blacklisting it is your `glugct` > server that is blacklisted by mail.simail.it. > > I just did the following > ``` > $ telnet mail.simail.it 25 > Trying 217.27.113.30... > Connected to mail.simail.it. > Escape character is '^]'. > 220 mail.simail.it ESMTP ready. > quit > 221 mail.simail.it closing connection > Connection closed by foreign host. > ``` > so it did answer my connect. In any case, this is not a Mailman issue. > It is between Postfix on your server and the remote server at > mail.simail.it. Thanks Mark for the reply, I had already checked with the telnet command on port 25 and everything is fine. The suspicion of the blacklist came to me, but now, after checking https://mxtoolbox.com/blacklists.aspx I saw that the mail.simail.it server is in the SORBS SPAM blacklist. Because my lists work fine on any other mailing address. I also checked my email server reputation at https://www.mail-tester.com and I get 10/10 Apparently it doesn't depend on my postfix server. In this case, what strategy do you recommend? Thank you -- blackout69

4 years, 2 months

[MM3-users] More Mailman releases!

by Abhilash Raj

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

1 year, 9 months

[MM3-users] Legit login attempts yield, "An error occurred while processing your request."

by Greg Newby

Hi friends. Following up on my message over the weekend about getting web (Django) logins for users who were ported from MM2 to MM3, I now have some people trying to create a new username. Something broke following a system update and reboot. MM3 is installed using the venv method, and the services (mailman and mailman-web) seem to be running ok. Mailing list delivery is happening as usual. I've now come upon a few related situations where a 500 error results, "Server error. An error occurred while processing your request." My primary question is: *How can I find out what's causing this*? I've looked in all the MM and web logfiles, by "tail -f" while generating the error, and nothing is logged there. Apache logs shows something like this: x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" I've come across this error while trying to do authentication-related activities that worked before the reboot: - "Forgot password" (happens whether or not the entered email existed in MM2 or already exists in MM3) - Sign up (ditto) - Email unsubscribes gave a verification email, but then didn't unsubscribe the address (might not be the same problem) Thanks for any breadcrumbs that might guide me to the solution. ~ Greg

11 months, 2 weeks

[MM3-users] Errors while importing mm2 list archives

by Odhiambo Washington

MM3-3.3.7, Hyperkitty-1.3.6 While importing, I encountered several of this error: <CUT> MySQLdb.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A, ...' for column 'content' at row 1") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 232, in from_mbox add_to_list(self.list_address, message) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 812, in save self.save_base( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 863, in save_base updated = self._save_table( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 1006, in _save_table results = self._do_insert( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 1047, in _do_insert return manager._insert( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", line 1791, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1660, in execute_sql cursor.execute(sql, params) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 319, in _query db.query(q) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/MySQLdb/connections.py", line 254, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A, ...' for column 'content' at row 1") </CUT> That occurred several times, but the import process went all the way, to 99% then came to the point below. Message 253d9d44-cc3e-fed1-144b-34da88c52b39(a)emailplus.org failed to import, skipping Computing thread structure Synchronizing properties with Mailman 904 emails left to refresh, checked 0 764 emails left to refresh, checked 0 Warming up cache Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 411, in handle call_command("hyperkitty_warm_up_cache", list_address) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 198, in call_command return command.execute(*args, **defaults) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", line 53, in handle self.warm_up_mlist(mlist, options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", line 61, in warm_up_mlist for thread in mlist.recent_threads: File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", line 162, in recent_threads return self.cached_values["recent_threads"]() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/common.py", line 58, in __call__ return self.get_or_set(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", line 317, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", line 317, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", line 650, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. (venv) [mailman@gw ~/mm]$ Should I take it that the import was successful, or what should I do next? PS: This is the 1st run after installing MM3 on this server and the MM3 list hasn't gone live. So if anything, I am okay with doing what needs to be done and rerun the import. TIA -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

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

by Richard Shetron

On 5/30/2016 3:13 PM, Simon Hanna wrote: > On 05/30/2016 07:19 PM, Rubén Rivero Capriles wrote: >> Dear mailman team, >> >> Before installation of postfix, I would like to remove >> a cron scheduled mail from awstats that arrives every 30 minutes >> to /var/log belonging to a misconfigured, deleted awstats configuration, >> reminding me that such file does not exist. >> Still looking for the most suitable way to learn about cron. > Your OS docs should have information about what program is responsible > for handling cron entries. `man crontab` should have information on how > to read and write the cron config >> Awstats documentation informs there is statistics support >> for mail activities besides traditional website visits monitoring. >> Does mailman work along well with awstats? > I have no idea what awstats does, but it probably only reads postfix' > logs. So it actually doesn't care about mailman. There might be a way > for it to parse mailman logs directly. If there is a way it's most > probably for mailman 2 and might be incompatible with mailman 3 awstats (http://www.awstats.org/) is a logfile analyser used mostly for analysing and generating stats for websites. It can do email and other logs as well. Depending on what OS you are using determines where to find the cron files,which may or may not run as root ;)

9 years, 2 months

[MM3-users] MM3 vs. Sympa

by Tom Browder

I still haven’t gotten around to getting a new MM3 service up and running, and now I’m looking at Sympa. I’ve seen a few comparisons of the two systems on the net, but the ones I’ve seen are for announcement lists only. I did see one university that did a study of list managers to replace Listproc and chose Sympa. I must admit my short-lived MM2 experience (used for my social sites for my high school and college classmates) seven years ago wasn’t the best was for two reasons: (1) no duplication of list names even for different domains and (2) it’s written in Python (instead of Perl). But, thanks to much help from Mark, I did get it runnng. I think it would be running today but it failed after about a year when Gmail (whose sntp server I was using) stopped allowing that, and I just didn’t know enough to get around the situation and had too much else to do. I waited expectantly for MM3 to come out and was ready to try again, but the separation of a formerly-integrated system into several systems was a bit daunting. Now I’m considering using Sympa: it’s coded in Perl, it’s monolithic, and it can support identical list names for different domains, so I am leaning in that direction. Before I go, I would appreciate anyone giving me a good reason to stay with MM (besides excellent support and a welcoming community—one which is a member of an unfortunately small group of such communities). Thanks so much. Best regards, -Tom

6 years, 9 months

[MM3-users] Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:21 AM, Nate Coraor wrote: > > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. I'm trying to get a new > list to behave the same way so I can figure out what's going on without > spamming a production list, but have been unsuccessful: despite setting > nearly all the list options the same as the old lists, new lists pass HTML > portions and attachments just fine. > > I've verified the settings using mailing list objects directly with > `mailman withlist` on the command line and the only differences are things > that I can't imagine would be related like admin_notify_mchanges, > advertised, and archive_policy. Are there are really old options that can't > be accessed via mailing list objects obtained with `withlist` on the > command line? No, there aren't "hidden settings" The relevant settings are filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext These are exactly analogous to the MM 2.1 settings filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext and should behave the same way. Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: A new issue with installation

by Brian Carpenter

On 2/20/21 12:35 PM, Abhilash Raj wrote: > Also, it is possible depending on your distro that packaged Rust compiler > is too old. cryptography requires a more recent version of Compiler, 1.45 > is the min supported version I think. > > FAQ:https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-with-error-can-not-find-rust-compiler > > You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` > but that would work just for this release and you won't be able to > skip from the next release of cryptography. I am going to need further assistance here. It is easy enought to install the rust compiler using rustup but I am still getting the same error: =============================DEBUG ASSISTANCE============================= If you are seeing a compilation error please try the following steps to successfully install cryptography: 1) Upgrade to the latest pip and try again. This will fix errors for most users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip 2) Read https://cryptography.io/en/latest/installation.html for specific instructions for your platform. 3) Check our frequently asked questions for more information: https://cryptography.io/en/latest/faq.html 4) Ensure you have a recent Rust toolchain installed: https://cryptography.io/en/latest/installation.html#rust 5) If you are experiencing issues with Rust for *this release only* you may set the environment variable `CRYPTOGRAPHY_DONT_BUILD_RUST=1`. =============================DEBUG ASSISTANCE============================= error: Can not find Rust compiler Running root@list:/opt/mailman/mm# rustc --version returns: rustc 1.50.0 (cb75ad5db 2021-02-10) I am doing this as the mailman user using a virtual environment. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Problems getting started with postorius

by Mark Sapiro

On 11/13/24 16:46, Alain D D Williams wrote: > > I eventually tracked it down. The problem was that I had signed in with an > account "addw@localhost". That, for some reason, failed validation above. > I hacked the database and changed to "addw(a)localhost.localdomain" and creating > the new domain worked. > > I could send email to addw@localhost - so at the MTA level it is correct. > > So please can the initial account creation do the same validation as does > adding a new domain. Mailman doesn't allow local, unqualified addresses, see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/validate… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/emai… On the other hand, Account creation/validation is done by django-allauth over which we have no control. > I have looked but cannot find any documentation on postorius than > https://docs.mailman3.org/projects/postorius/en/latest/ > which is not helpful for a user or system admin. Can you point me to something > better. Unfortunately, there is not user/list owner documentation for Postorius. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Which documentation to follow for installation

by Ruben Ibanez

Hi Abhilash, Finally we decided to install Mailman through the docker images provided by you (https://github.com/maxking/docker-mailman) The deployment was very quick, and it works flawlessly, so we will keep this solution. On the side I will try to deploy Mailman 3 through its independent modules, just for fun :) Many thanks! Cheers, R. From: "Abhilash Raj" <maxking(a)asynchronous.in> To: "Ruben Ibanez" <ribanez(a)sciops.esa.int> Cc: "mailman-users" <mailman-users(a)mailman3.org> Sent: Sunday, August 20, 2017 11:25:34 PM Subject: Re: [MM3-users] Which documentation to follow for installation On Sun, 20 Aug 2017 20:50:39 +0200 (CEST) Ruben Ibanez <ribanez(a)sciops.esa.int> wrote: > Hi Abhilash, > > Thanks for your reply. > > The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? There are production environments running Mailman 3.1 right now if that is your questions, see https://lists.mailman3.org. Although, I guess you already saw that when subscribing to this list ;) > Of course, I'm not asking for .rpm, .deb, etc... because I understand that's > quite complex, but I tried it following all available guides, including the > Contributor's Guide, and it seems impossible to get it running at the first > time (or just to get it running) without getting crazy or fixing lots of > unexpected errors during installation. It would be helpful if you send in those errors here. It will help us debug your problem and also improve the guide for the people using it in future. One small problem about the configuration, off the top of my head, can cause some problems in the "Mailman Suite Installation" Guide[1]. I have that on my todo to fix. But, apart from that everything else should work! [1]: http://docs.mailman3.org/en/latest/prodsetup.html You would have to do some additional configuration for the web frontend to work and for the mail servers to talk to Mailman and Frontend separately, both of which is also mentioned in the documentation under "Configuring Mailman Core" and "Configure Web Frontend". Contributor's guide is not focused on deploying but just setting it up locally to play with and modify the source itself. > Have you tried to deploy Mailman 3.x strictly following the documentation? I think people have used it in past to successfully deploy Mailman 3.x, but without looking at the errors you are facing I don't have any clue as to why it doesn't work for you! > > By the way, many thanks for your hard work! > > Cheers, > RI > > > From: "Abhilash Raj" <maxking(a)asynchronous.in> > To: ribanez(a)sciops.esa.int > Cc: mailman-users(a)mailman3.org > Sent: Saturday, August 19, 2017 8:55:20 AM > Subject: Re: [MM3-users] Which documentation to follow for installation > > On Fri, 18 Aug 2017 09:40:37 -0000 > ribanez(a)sciops.esa.int wrote: > > > 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/ > > Both of the above are actually latest documentation, > > docs.mailman3.org should be the one to look for installations guidelines for > the entire Mailman 3.x Suite, > > mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles > the mail. > > http://docs.mailman3.org/en/latest/prodsetup.html > > This should be the best place to start, be sure to look at the Pre-Installation > Guide if you are new to the Python ecosystem. > > > > > 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. > > It is meant for Mailman 3.X series and is maintained by me. It currently > includes the latest releases for all the Mailman's sub-projects, also Mailman > 3.1. > > > Hope that helps! > > -- thanks, Abhilash Raj This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.

7 years, 11 months

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

by Abhilash Raj

Hi Tom, On Tue, Aug 1, 2017, at 07:54 AM, Tom Browder wrote: > The mm3 installation instructions have been somewhat fluid over the > development period, butI'm finally ready to dig in and give it a shot and > need some last-minute advice. > > I'm leaning toward installing using the docker method but I would > appreciate any recent thoughts about which method to choose. It really depends on what way you want to go, container images will be much less hassle to use right now, mostly because all the dependencies are bundled in and the moving parts are already configured to work with each other. Also, the upgrade process for container images is pretty easy and you can even setup auto-upgrades if you want using some pretty-easy-to-use tools. I do that to test each commit that goes in the Github Repo for container images. Installing from sources isn't that bad right now, but you would need some knowledge of Django and Python based ecosystem for web applications. The documentation has most of them with pointers to other things you might need to know in order to run, if you feel it is inadequate, I would encourage you to open bug reports. > Thanks so much to the MM3 dev team! > > Best, > > -Tom > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years

[MM3-users] Container Images for Mailman 3.2 release

by Abhilash Raj

Hi All, I have updated and pushed releases for Container Images with 3.2 release of the suite. They are available at: docker.io/maxking/mailman-web:0.2 docker.io/maxking/mailman-core:0.2 A similar copy of both is also available at quay: quay.io/maxking/mailman-web:0.2 quay.io/maxking/mailman-core:0.2 The releases contain the following versions of components: mailman-core: - Mailman Core 3.2.0 - Mailman-hyperkitty 1.1.0 mailman-web: - Postorius 1.2.1 - Hyperkitty 1.2.0 - Django-mailman3 1.2.0 - MailmanClient 3.2.0 The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: $ docker exec -it mailman-web bash bash # python manage.py rebuild_index If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. Documentation for these images is available at: https://github.com/maxking/docker-mailman -- thanks, Abhilash Raj (maxking)

7 years

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 10:12, andrea.janna.unipd(a)gmail.com wrote: > >>From the database debug log I guess that mailman gatenews abruptly terminates the database connections. > For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry. > > 70759 Connect mailman3web@localhost on mailman3web using Socket > 70759 Query SET sql_mode='STRICT_TRANS_TABLES' > ... > 240131 18:54:34 70759 Quit > > There is a "Quit" at the end. > While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end. You could try the following in `mailman shell` ``` $ 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. >>> for mlist in getUtility(IListManager).mailing_lists: ... print(mlist.fqdn_listname) ... (here should be a list of your mailing lists) >>> ``` Does this produce the expected list of mailing lists and does it produce the error in the database debug log? If it does produce the expected list of mailing lists and the error in the database debug log, I'd say this is some issue between SQLAlchemy and MariaDB, but it seems harmless. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

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

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 19:23): > What is the exact email address that you are logging on to the web UI > with. Does it match exactly with the address of a list member or are > there mixed-case differences? You might try an interaction like this: > ``` > mailman-web shell > Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) > >>> from django_mailman3.lib.mailman import get_mailman_client > >>> client = get_mailman_client() > >>> list_id = 'test.example.com' # your actual list_id > >>> rest_list = client.get_list(list_id) > >>> email = 'user(a)example.com' # your actual email > >>> member = rest_list.get_member(email) > >>> member > This should print something like > <Member 'user(a)example.com' on 'test.example.com' with role 'member'> > ``` > This is exactly what HyperKitty is doing except in your case > rest_list.get_member(email) is throwing a ValueError exception instead > of returning the member. I get: <Member 'megabrutal(a)gmail.com' on 'the.correct.list.address' with role 'member'> So it's even weirder – however, I'm really not sure if this is the address HyperKitty is checking for, as I have 3 attached to my account! How may I know which one it's trying to use?

3 months, 3 weeks

[MM3-users] Re: Editing the "example.org" site

by Odhiambo Washington

On Sun, Dec 31, 2023 at 11:16 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Hi all, > > I don't know how many people will need this, but I just realized that > you can edit Django's SITE 1 and (probably, 100% untested but I'm > going on the clock so want to get this done quick :-) use that. > > When you add your first domain, there's a link in that page (not a > button, a link!) to edit the domain list. Then you can click on the > link to "example.org" in the list, and edit both display name (which I > assumed) and the domain name. > > Maybe I'm just slow, but I've been adding SITE 2 = "Whatever site > <whatever.tld>" the whole time. :-) But then you have to edit the > SITE = 1 statement in settings.py (which I often forget and hilarity > ensues). > > Of course adding a web site and editing settings.py (which you have to > do anyway for other variables) works too, but this seems cleaner to > me. > > Steve > This is interesting. However, you meant the default example.com, right? And that link also let's me DELETE the site :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 7 months

[MM3-users] Re: Mailman3 via Docker and NGINX

by Abhilash Raj

On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote: > On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. > ... > > location / { > > include uwsgi_params; > > uwsgi_pass 172.19.199.3:8000; Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for uwsgi protocol. See the docs[1]. [1]: https://github.com/maxking/docker-mailman#setting-up-your-web-server > > uwsgi_read_timeout 300; > > proxy_set_header Host $host; > > proxy_set_header X-Forwarded-For $remote_addr; > > } > > } > > > Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the > correct output, uwsgi or whatever your wsgi process is is working at > that level, and I don't think you should be invoking uwsgi in nginx. I > think you should be using proxy_pass. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > for the nginx config used on 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Delayed password requests & migrating users from mm2

by Brian Carpenter

On 3/17/21 9:51 AM, Duane Raymond wrote: > With my new mm3 instance, password reset email to members are being received many hours late or not at all. They seem to be sent fine and when I trigger one to one of my addresses, it works instantly. But many users report getting it many hours later or not at all (despite looking in spam and bulk folders). > > Anyone else experience this password reset mail delay/vanishing and/or have any suggestions for diagnosing it and resolving it? > > The main reason this is problematic is that in migrating lists from mm2, I've set a 'fake' password for them in the mm3 db and instructed members to reset their password to set a new one so they can access the list and update their subscription and/or subscribe to other lists (which they can also do without an account of course - but then lose the ability to use the web interface and access archives). > > So if, as an alternative, there is another way to get list members to access their account then I'm open to it. Have you checked /var/log/mail.log for the time that the request was sent out? Have you looked in the mail queue for deferrals (# mailq)? For instance, Yahoo users will experience great delays if Yahoo starts deferring mail which it most certainly will on new IP addresses that starts sending out mail. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

[MM3-users] Re: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 1:59 PM, Quanah Gibson-Mount wrote: > >> Click on the subject in the held messages list. At the bottom of the >> dialog that opens, there is a drop down to set the user's moderation. >> Normally, you would set it to 'default processing'. > > I do not see any such option. After clicking on the header the only > options available at the bottom are: > > Accept, Reject, Discard, Show Source, Show Header > > There are zero drop downs anywhere. This was implemented by <https://gitlab.com/mailman/postorius/-/merge_requests/397> and released in Postorius 1.3.0. >> This was not "removed". It just hasn't been implemented in MM 3 yet. > > So in terms of available functionality that was present in MM2, it was > removed. It may need to be re-implemented, but this was a core feature > that was present in the prior version that is no longer available. Yes, we are aware of many things that are not yet exposed/implemented in Postorius and elsewhere. There are currently 580 open issues at <https://gitlab.com/groups/mailman/-/issues>. We are working on these things as we can. We would love to have your help in fixing these. In the mean time, there are really only 2 or 3 core developers working on this and we are all volunteers, so it takes time. -- 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: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > Because those aren't the settings that matter for this. > What if anything are your settings in the mailman.cfg [webservice] > section for > hostname: > port: > admin_user: > admin_pass: > use_https: > (defaults in our distribution are localhost, 8001, restadmin, restpass > and no respectively - I don't know if Debian changes these). > These need to match the Django settings > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = 'restpass' They do match. Even the port (still on 8001). > > The REST API is apparently not listening on the host/port this is trying > to connest to. Apparently. The question is why. > > What is executing the manage.py command to start Django. Is it user list? Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. > > I don't use uwsgi and know little about it so I don't know what the Unix > domain socket /run/mailman3-web/uwsgi.sock connection is for, but this > appears to be some miscunfiguration between apache and uwsgi. > Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via > tcp port 8000 and uwsgi is configured with > [uwsgi] > uwsgi-socket = 0.0.0.0:8000 I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.

3 years, 11 months

[MM3-users] Re: Hyperkitty

by Mark Sapiro

On 1/30/23 13:17, Onyeibo wrote: > > The mails don't have that header. I suspect I may have to investigate > SELinux. I think it's unlikely a SELinux issue unless you mean it's an issue writing the log, but if there are any entries at all in mailman.log, that should be OK. what does `mailman conf -s archiver.hyperkitty -k configuration` show? The default is `/etc/mailman3/mailman-hyperkitty.cfg`. Whatever it is, what's in that file. It should be something like ``` [general] base_url: http://127.0.0.1:8000/archives/ api_key: some_key ``` some_key needs to match ``` MAILMAN_ARCHIVER_KEY = 'some_key' ``` in /etc/mailman3/settings.py and the base_url setting needs to access hyperkitty. It could be as above or it could be the URL that accesses HyperKitty externally as in ``` base_url: http:://example.com/archives/ ``` Is all of that correct? To verify base_url, you can do ``` curl http://127.0.0.1:8000/archives/api/ ``` where the initial part of that is the base_url setting. That should return the html for a page of documentation. Look at https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperki…. This is Mailman Core's interface to the archiver. If any of the methods there fail to connect to HyperKitty or get an appropriate response, they all log errors. In particular, the archive_message() method at line 171 is saving the message in the spool queue. Immediately before that at lines 164 and 167 it is writing log messages. You should be seeing them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Where does sender postorius@ come from?

by Odhiambo Washington

The addresses are defined in Django settings if I'm not mistaken. And callout isn't evil. On Wed, Jun 7, 2023, 23:31 Jens Günther <jens.guenther(a)posteo.de> wrote: > I just realized, that mails for registering an account and/or resetting > ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why > are they not sent from MAILMAN_ADMIN_EMAIL? > > The problem is: > - an account is trying to register with a mailaddress from a > HostEurope-server > - HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to > verify that a mailaccount exists > - mail is then bouncing, b/c those are not answered (shoud I?): > status=bounced (host [80.237.138.5] said: 550-Sender verification is > required but failed. > - bounce then can't be processed, since mailaccount does not exist :-D > status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself) > > Am I missing something are shouldn't it be better to send those mails > from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender > callouts or change anything, HostEurope has been a little bit of a pain > in the ... with mailinglists and not much help at all). > > Thanks in advance, Jens. > _______________________________________________ > 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 >

2 years, 1 month

[MM3-users] Re: Patch/kludge suggestion and a question on adding accepted addresses

by Barry Warsaw

On Apr 23, 2017, at 10:33 PM, David Krantz wrote: >I found out that I had a broken email in one of my held messages >queues). That gave a HTTP 500 error although that should be fixed . >After some digging I found out that where the error occured. > >I'd suggest adding a catch for AttributeError similar to the one for >KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my >immediate problem at least. I run the version from git with the tag >263711b3b7988c7c474e3b8952dc7e0f02f04fa2 Can you file a bug and attach either the problematic message or the traceback? >The message causing this was probably one where I had sent a minimal >email via telnet to the SMTP port and forgot the MessageID-header or >something similarily silly. But it prevented me from seeing the held >messages-list in postorius. Did you talk to your MTA's SMTP port, to Mailman's LMTP port, or some other process? It matters because LMTP is the way messages get from the upstream SMTP daemon (e.g. Postfix, Exim) into Mailman, and the LMTP server rejects any messages that don't have a Message-ID. >I have another question: In the old mailman you could add accepted >senders without adding them to the list. Is that possible in Mailman >3/Postorius? You do this by creating a "nonmember" subscription for the sender, and then setting that member's moderation_action to Action.accept. Cheers, -Barry

8 years, 3 months

[MM3-users] Re: List of "site admin" commands in Mailman 3.1 docker-mailman

by Barry Warsaw

Hi Henrik, On Jul 17, 2017, at 02:55 PM, Henrik Rasmussen wrote: >1) Should I enter the container using "docker exec -it mailman-web bash" and >run "python" in order to get a python prompt, and from there run commands >like those documented at >mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html ?. In Mailman 3, there's a command called `mailman` which has many subcommands. if you type `mailman --help`, it will give you some sense of the commands available to you. E.g. whereas in Mailman 2 you'd use `list_lists` at the prompt, in Mailman 3 you would use `mailman lists`. You can get help on the subcommand with `mailman lists --help` of course. >2) Where do I define the what was previously known as the site admin user >and site admin e-mail? There's no real equivalent of the site list or site admin password in Mailman 3. There is a `site_owner` address you can configure in your mailman.cfg file, but it's really just a fallback in a few cases where Mailman otherwise can't reach a human. >On another note: Is it a setting in the mailman-users(a)mailman3.org list setup >that make each of my postings to the list come back with the note "This >sender failed our fraud detection checks and may not be who they appear to >be."? It's not something in Mailman. Possibly in the toolchain on mailman3.org? -Barry

8 years

[MM3-users] Re: Mailman 3 database restore unexpected behavior

by Odhiambo Washington

Have you looked at the tables and actually seen the duplicates? SELECT COUNT... Again, restoring a database usually should drop the table before restoring. On Tue, Mar 28, 2023, 14:00 Tibor Molnar <tibor.molnar(a)waltoninstitute.ie> wrote: > Mailman3 built from source using virtual environment. > Version: > GNU Mailman 3.3.8 (Tom Sawyer) > Python 3.9.2 (default, Feb 28 2021, 17:03:44) > [GCC 10.2.1 20210110] > config file: /etc/mailman3/mailman.cfg > > Issue: > I have restored the database number of times recently and experienced that > every time after restoration (an hour after) all members getting an email > that they are unsubscribed due to bounces, however non of the users are > actually unsubscribed from any lists. It looks like there are duplicates in > database and all the duplicates are getting unsubscribed? > > Bounces message: > name(a)email.com unsubscribed from [listname] mailing list due to bounces > > Only restoring two files: mailman3 and mailman3web > > Did anyone come acroos this behavior ? > It is not right that after restoring a database all 1000 user get an email > that they are unsubscribed, but they are actually not. > I may do something wrong during the restoring process. > Please advise me. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 4 months

[MM3-users] Re: Message Sent to A Re-Created List Results In Error

by Morris Jones

Matt, I think you're describing exactly the problem that's handled by /virtual alias domains/ that were added to support this case. https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… I did an integration between Mailman3 and Zimbra which uses Postfix, and came across the same issue with domains managed by Postfix and Mailman simultaneously. I documented the case in my Zimbra - Mailman3 integration document here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration/-/blob/master/m… See if that helps ... Best regards, Mojo On 12/14/20 9:38 PM, matthew(a)alberti.us wrote: > I checked all over the mailman core logs and couldn't find a > problem. But then I noticed that the 550 error was coming from dovecot-lmtp. > I should rename this thread because the actual problem seems to be unrelated > to re-created lists. > > It seems like the actual problem seems to occur in the following > situation: > > * Using Postfix > * Using Dovecot > * /etc/postfix/virtual includes addresses with same domain as mailman > lists. > * An e-mail address subscribed to a mailman list is in the > /etc/postfix/virtual file as an alias (possibly also if destination address > for an alias). > * (Possibly related) E-mail address is also one of the list owners. > > In that environment, Postfix seems to check only 'virtual_transport' > list, which in my case is dovecot-lmtp, and when it doesn't find the mailman > listname@domain entry in there, it sends a 550 user unknown. It seems to be > that it isn't getting passed to 'transport_maps', which is mailman-lmtp. > > When I remove that one address (that is in /etc/postfix/virtual) > from the list of subscribers, I'm able to post again. Interestingly enough, > when I put it back in as a subscriber. I'm still able to post. So it seems > unsubscribing and re-subscribing that address fixed it, or adding an > additional list owner and deleting it fixed it, or some combination of > those. > > I know this might be shaping up to be a very unlikely scenario. But > basically the account is mine, an admin, doing testing before/after a > deployment.. I'll try to create a few test procedures to document the method > to reproduce the problem, and also hopefully fix it. If I can do that, I'll > open another thread. This could also be a postfix config error of some kind, > which is definitely possible if not likely. > > Thanks for reading. > > - Matt Alberti > > > > -----Original Message----- > From: Abhilash Raj <maxking(a)asynchronous.in> > Sent: Monday, December 14, 2020 11:42 PM > To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> > Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error > > > > On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us > <mailto:matthew@alberti.us> wrote: >> I created a list in the Postorius interface, used it, and then deleted >> it. A week or so later, I re-created the list, and things were fine >> thru the creation and subscription process. But when I sent a message >> to the list, a >> "550 user unknown" error was sent back. > > Can you share more error details from the Mailman logs? If 550 error > response was sent, there must be some internal error traceback in the logs. > >> >> >> I tried to determine if this is a known issue by searching the issues >> in Gitlab; but didn't find anything. But wanted to ask if this was a >> known issue or not? > > I personally don't remember seeing such an issue, but Mark or others might > know. > >> >> >> >> Thanks. >> >> >> >> - Matt Alberti >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> To >> unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> To unsubscribe send an email to > mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > _______________________________________________ > 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/ > -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 7 months

[MM3-users] Mailman3-web/Postorius behind Lighttpd

by Élodie BOSSIER

Hi, I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from packages : #dpkg -l | grep mailman ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty ii python3-mailmanclient 3.3.2-1 all Python bindings for Mailman3 REST API (Python 3 version) I can access from localhost to http://127.0.0.1:8000/ which move me correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be correct. But 127.0.0.1:8000 listen only in localhost : #netstat -tanpu | grep 8000 tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 626175/python3 So I try to use my lighttpd as proxy as recommanded with this config : > scgi.protocol = "uwsgi" > scgi.server = ( > "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => > "disable" )), > ) but it's return me a "502 Bad Gateway". I see nothing on there logs : - /var/log/lighttpd/error.log - /var/log/mailman3/web/error.log - /var/log/mailman3/web/access.log But on the file : /var/log/mailman3/web/mailman-web.log I can see that : > QUERY_STRING > REQUEST_URI/postorius/lists/REDIRECT_STATUS200 > SCRIPT_NAME" 400 - I don't know what I'm doing wrong ... There is a way to solve it with lighttpd or bind the port 8000 to 0.0.0.0 instead 127.0.0.1 (which is not recommanded) ? Thank you in advance. Best regards, Elodie

3 years, 5 months

[MM3-users] Re: best pratice - set default MM settings and make them update-save

by Stefan Bauer

Thank you very much. But this is a _new_ mailman behavior. In previous versions, there was no checkbox at all and mass-subscription was done without any confirmation. Stefan Am Mo., 16. Mai 2022 um 18:35 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 5/16/22 07:16, Stefan Bauer wrote: > > > > Is there also a way to have this box checked by default or do not > request a > > verifcation at all? > > Could not find any flag in base.py. > > To have the box checked by default would require a patch to Postorius > like this. > ``` > --- a/src/postorius/forms/list_forms.py > +++ b/src/postorius/forms/list_forms.py > @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): > > pre_verified = forms.BooleanField( > label=_('Pre Verified'), > - initial=False, > + initial=True, > required=False, > help_text=_( > 'If checked, users will not have to verify that their ' > ``` > Not requiring verification at all would require patching Mailman core > but would be a bad idea as it could allow someone to subscribe anyone > without that person's consent. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 2 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 08:01, Mark Sapiro wrote: > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > contents) are readable and writeable by mailman:mailman: > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > I fail to see where haystack tries (and fails) to create the directory. > > FWIW, deleting threads is not a problem. > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > add that user to the `mailman` group. That's what baffles me – uwsgi is run as the mailman user: mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini - Jan

2 years, 8 months

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

by Mark Sapiro

On 10/17/20 10:39 AM, Torge Riedel wrote: > > The message is being held because: > > Header "Yes" matched a header rule > > At your convenience, visit your dashboard to approve or deny the > request. > > I think this is wrong, it should read 'Header "x-spam" matched a header > rule'. Cause the header rule is configured for header "x-spam" and > pattern "Yes". The message is defined as 'Header "{}" matched a header rule' where {} is replaced with the value of the matching header. I agree it would be better if it were something like 'Header value "{}" matched a header rule for {}:' with {}s replaced with the header value and name. That would make it in your case 'Header value "Yes" matched a header rule for x-spam:' > I haven't found a bug report for this yet on gitlab. If someone of the > developers confirm this is wrong, I will file a bug on gitlab for it. Please do file a bug. It won't be fixed until after the upcoming 3.3.2 final release because we not making i18n changes between the candidate and final releases. Also, if you don't like my suggestion, feel free to suggest something else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Urgent help needed...

by Darren Smith

Hello, This morning our Mailman 3/Hyperkitty/Postorius installation has become unresponsive. When looking at the machine, postgres is pegging all 4 CPUs on the machine. We did some digging in postgres, and here is the query that is causing problems: "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY hyperkitty_email.date ASC LIMIT 1;" We have found that it doesn't matter what mailinglist_id is being used. We have also found that this might be an issue with the LIMIT 1 - our investigation is showing that using LIMIT 1 in postgres makes things execute very differently than if you use a limit 2 or more, and that this is probably what is going on. Basically, every time this gets called, it pegs an entire CPU for 20-30 seconds. It appears to be called a LOT. So our users are getting 504 gateway timeouts right now. What has changed: We have been in the process of importing our 40 million archived emails from our old mailman 2 archives. Questions: 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, postorius, django - basically anything that might be calling this code, but we can't find it. Does anyone know what generates this query? 2) We are positing that it might be our archive imports that are causing this problem. Does anyone know of any sort of limit/threshold that might cause this to go haywire? Any help you can give, any direction you can point us would be useful. Right now our lists are just down for our users. Thank you, Darren

7 years, 2 months

[MM3-users] Re: Upgrade to 3.3.2 fails

by Joel Lord

innodb_page_size can not be increased after the fact. In order to actually make that change would involve dumping all the databases and re-initializing mysql with the new page size in place, then reloading from all the dumps. I'm not working with a dedicated database server, it's got quite a lot on it other than mailman, so that would be an enormous undertaking. -Joel On 12/27/20 3:12 AM, Torge Riedel wrote: > Am 26.12.20 um 23:00 schrieb Joel Lord: >> but now we're up and running > > Nice to hear, but I fear you could be hit by this issues again, > depending on changes in the future on the table. Either when more > columns are added or on runtime when rows are added / updated. > > I've read the following documentation, but I do not clearly understand > whether innodb_page_size can be increased later via config or not: > > https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innod… > > > @Mark: Would it be a good approach to split the table 'mailinglist'? I > see some groups of columns like "bounce_*" or "dmarc_*" which could be > managed in separate tables. > > Whereas reaching limits on upgrade is already annoying enough, > reaching limits on runtime can be fatal. I guess. > > Kind regards > Torge > _______________________________________________ > 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/ -- Joel Lord

4 years, 7 months

[MM3-users] Re: Is it possible yet to install Mailman 3 for Ubuntu 22.04?

by Andrew Hodgson

Hi. The issue is still unresolved with the Ubuntu 22.04 packages. This is because when Ubuntu 22.04 shipped it came with Python 3.10 and the Mailman version that supports Python 3.10 3.3.8 wasn't released. Here is a bug on the Ubuntu side about this: https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1999197 The instructions posted to this list to get Mailman running in a venv work fine with Ubuntu 22.04 and Python 3.10 and is what I am using for a couple of hosts. My own view is there are too many moving parts for the distro packages to keep track of, so I will do that myself using the venv and let the distro manage the system packages. There are newer Debian packages available in Debian testing, but they don't seem to have been migrated over to Ubuntu 22.04 yet, possibly they are in 23.04 and those versions could be used (unsure). Thanks. Andrew. -Original Message----- From: Mark London <markrlondon(a)gmail.com> Sent: Friday, April 14, 2023 8:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Is it possible yet to install Mailman 3 for Ubuntu 22.04? Is it possible yet to install Mailman 3 for Ubuntu 22.04? If not, will it be possible in the near future? Thanks. Mark _______________________________________________ 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 andrew(a)hodgson.io

2 years, 3 months

[MM3-users] Re: Removing the footer from mails

by Mark Sapiro

On 10/21/2017 01:46 PM, Peter Mueller wrote: > Hi, > > mailman2 had the configuration variable "msg_footer" to edit/remove the > footer. How can I get rid of the footer in mailman3? The doc is at <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/decorate.…>, but it's a bit complex. First, the message footer template name is 'list:member:regular:footer' and the digest footer template name is 'list:member:digest:footer' and if you want the same template for both, the name 'list:member:generic:footer' will do. The easiest way to set these is to create a template for the desired language (probably 'en') or an empty file if you want no footer. Then, there is a 'var' directory in the Mailman installation which contains sub directories named 'archives', 'cache' 'data', 'etc', 'ext', 'lists', 'locks', 'logs', 'messages', 'queue' and 'templates'. You can put list specific templates in var/templates/lists/LIST.ID/en/, domain specific templates in var/templates/domains/DOMAIN/en/ and sitewide templates in var/templates/site/en/. For example if you put an empty file at var/templates/site/en/list:member:generic:footer and a non-empty file at var/templates/lists/list.example.com/en/list:member:regular:footer, all messages and digests will have no footer except for regular deliveries from the list.example.com list which will use it's template. list overrides domain overrides site overrides default. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

I tried this way but in this method I don't find any files to edit for my customizations like 1. Removal of social accounts, 2. Addition of SMS integration and so. If I can do my required customizations through pip installation I am fine with that. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 11:48 PM, Shashikanth Komandoor wrote: > > Though you are for sure that the current versions as I am claiming the > > above one is perfectly without any issue, please also suggest what would > be > > the best previous version which definitely does not have that issue > because > > I even checked out the immediate previous version of mailmanclient but > > still I am getting the same error. > > > Follow this document > < > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > and install with pip. > > -- > 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, 9 months

[MM3-users] Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Odhiambo Washington

On Sun, Oct 1, 2023 at 10:46 AM Wikinaut <mail(a)tgries.de> wrote: > I could not fix the problem, apparently there is a mismatch somewhere now. > > sudo pip uninstall django-q > Found existing installation: django-q 1.3.9 > Uninstalling django-q-1.3.9: > Would remove: > /usr/local/lib/python3.9/dist-packages/CHANGELOG.md > /usr/local/lib/python3.9/dist-packages/django_q-1.3.9.dist-info/* > /usr/local/lib/python3.9/dist-packages/django_q/* > Proceed (y/n)? n > > whereas > dpkg -l | grep django-q: > > ii python3-django-q 1.2.1-1 > > /usr/lib/python3/dist-info: > 4 drwxr-xr-x 8 root root 4096 21. Jun 2022 django_q > 4 drwxr-xr-x 2 root root 4096 21. Jun 2022 django_q-1.2.1.egg-info > > sudo apt remove python3-django-q > the following packet will be REMOVED: > mailman3-full mailman3-web python3-django-hyperkitty python3-django-q > Continue [Y/n] n > > What to do? I don't want to remove mailman3, I just want to bring the > 1.2.1-1 to 1.3.9... > Maybe you can make your life a little more bearable by abandoning the use of Debian packages and embracing the virtualenv install documented at https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install and we'll find it easier to help you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] LMTP on unix socket

by Stephen J. Turnbull

Hristo Venev via Mailman-users writes: > How do I configure mailman to use a unix socket for lmtp > connections? I don't think it's currently possible. Using a Unix socket is undocumented in Mailman. Mailman's LMTP server is based on aiosmtpd, which as far as I can tell from its documentation does not support Unix sockets. > Setting > > [mta] > incoming: mailman.mta.null.NullMTA > lmtp_host: /path/to/socket That's the smtpd package's style of configuration, but I don't think it works with aiosmtpd. The underlying asyncio package does support Unix sockets, so it's *probably* not too hard to add this feature *in principle*. However, if aiosmtpd doesn't support it, somebody (preferably not us) will have to fork and go through the feature submission process, and maintain it separately for quite some time since we support fairly old Python versions. And async code is fundamentally hairy, if we have to get into any details (*probably* not, but speaking for myself I'm not going to dig into something without a reserve of time on "probably"). Also, I don't think we have any experts in this code at this time, and I'm not going to have enough time to work on it for a month, at least, and more likely around the new year. Maybe somebody else does, but I know some of our developers will be out of touch for a while. You could try the aiosmtpd package maintainer, or the upstream Python channels (python-list(a)python.org) Steve

5 years, 9 months

[MM3-users] Re: # comment allowed in a template file?

by Mark Sapiro

On 7/27/20 5:15 AM, skenny(a)scss.tcd.ie wrote: > > The effect of the template files not being readable by user "mailman" was interesting. Hundreds of lines like the following got written to mailman-core's var/log/smtp.log file at the rate of 4 per second: > > Jul 23 17:09:54 2020 (25) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fdf9e7b5f28> > > (the hex number was different each time). That's a `debug` level log message written for every delivery. It has nothing to do with the unreadable templates except that the unreadable template causes looping in an attempt to send the message. Did you perhaps set [logging.smtp] level: debug in an effort to diagnose the template issue? > Having excessively restrictive permissions on the template files is a silly - but easy enough - mistake to make. If it were possible to add it to Mailman 3, a more descriptive logging message could point others who make it in the right direction, perhaps. I spent a long time trying to figure out why messages weren't getting sent out from Mailman core, and in the end it was luck in form of a colleague's suggestion about file permissions that got me out of the rut. There is clearly a bug in that an unreadable template should just be skipped and the fact logged. I have reported <https://gitlab.com/mailman/mailman/-/issues/745>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: REST API authorization failed

by Axel Rau

Hi Mark, thanks for your patience. > Am 10.01.2022 um 04:56 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Anyway, the above is saying that restadmin:??? doesn't match what's configured in Mailman core and reported by `mailman info`. Please check carefully that these are the same in both mailman.cfg admin_pass and settings MAILMAN_REST_API_PASS. Yes, again with password disclosed: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# service mailman restart Restarting the Mailman runners (mailman_33) [root@lists5 /usr/local/mailman3]# su -m www -c "curl -v -u restadmin:restpass http://localhost:8001/3.1/lists" * Trying 127.0.0.1:8001... * Connected to localhost (91.216.35.42) port 8001 (#0) * Server auth using Basic with user 'restadmin' > GET /3.1/lists HTTP/1.1 > Host: localhost:8001 > Authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz > User-Agent: curl/7.80.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Server: gunicorn < Date: Mon, 10 Jan 2022 09:39:43 GMT < Connection: close * Authentication problem. Ignoring this. < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" < content-type: application/json < vary: Accept < content-length: 77 < * Closing connection 0 {"title": "401 Unauthorized", "description": "REST API authorization failed“} (mailman_33) [root@lists5 /usr/local/mailman3]# (mailman_33) [root@lists5 /usr/local/mailman3]# grep REST settings.py MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' (mailman_33) [root@lists5 /usr/local/mailman3]# grep admin var/etc/mailman.cfg admin_user: restadmin admin_pass: restpass (mailman_33) [root@lists5 /usr/local/mailman3]# - - - What am I doing wrong? Is something wrong with my installed python packages? pip freeze attached. clueless, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 years, 6 months

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

by Mark Dadgar

On Oct 5, 2019, at 12:22 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > You could just run, e.g., `sudo -u list bin/mailman import21 ...` which > will work even if 'list' can't log in. That’s what I get for being old school and just su’ing to the user. Thanks. > If you run hyperkitty_import --since=1990-01-01, that should do it. > Awesome - rerunning now. Thank you. > As far as "the archives for many months consist of just a single > identical thread", were there error messages when you ran the initial > import? Were there issues in the imported mbox that you have corrected? > Mailman 2.1's bin/cleanarch can help identify unescaped 'From ' lines > that cause problems. Yes, I ran the archive mbox through cleanarch before importing it. It’s a 24GB mbox file with 17 years of archives for a very active mailing list. > If unescaped 'From ' lines is the issue and you have fixed them, > rerunning the import should import the messages correctly, but it won't > delete the bogus threads. You can delete these threads manually in > HyperKitty if you are logged in as a Django superuser. Great - thank you. I see the occasional “table is locked” error (I am running against sqlite because I only run a couple of lists and I was having issues getting the postgres config working) so it skips the occasional message. We’ll see what happens this time. Your help is much appreciated. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

[MM3-users] Re: Monthly Password Reminders

by Stephen J. Turnbull

Odhiambo Washington writes: > On Thu, Feb 2, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/2/23 06:29, Odhiambo Washington wrote: > > > Does MM3 send these monthly subscription reminders the way MM2 used to > > do? > > > I am looking for the setting, but can't find that in the list settings. > > > > No, it does not. > > The rationale behind the decision to toss away that feature? Security?? For the passwords, yes. It was frequently reported as a bug, in fact. Mostly the reminders generate requests to know how to shut them off. You're the first in probably a decade who's asked how to turn them on! While in theory we could protect in transit with SMTP over TLS, we can't guarantee end-to-end encryption (eg, if there's a .forward at the subscribed address), and while TLS is widely implemented, it's still not universal. And there's no way to protect unencrypted email from admins at the receiving host. Receiving encrypted email is pretty much not implemented at all, except in some specialized communities. Also, now that passwords (if they're used) are attributes of Users who may have several Addresses and worse, they may have admin privileges. So Mailman 3 passwords are generally higher value than in Mailman 2. I can imagine a use for the list of subscriptions part that a few users might like, but most folks would prefer not to get another regular mailing. Steve

2 years, 5 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 9/30/24 14:44, jkoral(a)luc.edu wrote: > That makes sense. Are there instructions on how to do this? It depends on the MTA. For Postfix you probably have a set of aliases for each of the form: mailman: "|/path/to/mail/mailman post mailman" mailman-admin: "|/path/to/mail/mailman admin mailman" mailman-bounces: "|/path/to/mail/mailman bounces mailman" mailman-confirm: "|/path/to/mail/mailman confirm mailman" mailman-join: "|/path/to/mail/mailman join mailman" mailman-leave: "|/path/to/mail/mailman leave mailman" mailman-owner: "|/path/to/mail/mailman owner mailman" mailman-request: "|/path/to/mail/mailman request mailman" mailman-subscribe: "|/path/to/mail/mailman subscribe mailman" mailman-unsubscribe: "|/path/to/mail/mailman unsubscribe mailman" You could change these, preferably in a separate aliases file so Mailman's genaliases won't overwrite them, to mailman: mailman@new_server mailman-admin: mailman-admin@new-server mailman-bounces: mailman-bounces@new-server mailman-confirm: mailman-confirm@new-server mailman-join: mailman-join@new-server mailman-leave: mailman-leave@new-server mailman-owner: mailman-owner@new-server mailman-request: mailman-request@new-server mailman-subscribe: mailman-subscribe@new-server mailman-unsubscribe: mailman-unsubscribe@new-server For exim, you would need to add another Mailman router ahead of the existing one which would match only the migrated lists and specify an smtp transport which relays to the new server. > Then once we are done migrating to the new server, then we can just change the DNS, correct? Yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users] Re: How to process emails with Mailman3?

by Kyle Lahnakoski

Thank you for this answer. In both the inject case and the netcat case I must know the recipient. My complex setup looses that metadata; leaving me with only the message. I guess I will be parsing the message to find that recipient. Thanks again On 2025-03-09 10:50 p.m., Mark Sapiro wrote: > Mark Sapiro wrote: >> The issue is you are not using nc correctly. >> When you do >> >> $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr >> >> you are telling nc to take commands from the file >> /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send >> the file. > Actually, what I said is not correct. The issue is you are just sending the data rather than engaging in an LMTP dialog. > > You need to send LMTP commands so you might prepend the message with > ``` > LHLO mymaillist.org > MAIL FROM: <sender(a)example.com> > RCPT TO: <all-request(a)mymaillist.org> > DATA > ``` > and append to the message > ``` > . > QUIT > ``` > > -- > 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 kyle(a)lahnakoski.com >

4 months, 3 weeks

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-24 10:38, Mark Sapiro wrote: > Try the following in `mailman shell` running as user mailman > ``` > (venv) $ 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. > >>>> import requests >>>> r = requests.get( > ... > 'https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD…', > ... timeout=5) >>>> t.text > ``` > Note the URL above is all on one line. > This is exactly what Mailman core is doing to get the template > assuming the `uri` in the template` table entry is the argument of the > requests.get(). > > If this times out, try increasing the timeout= value. ************************************************ I crossed emails with you on my last post. I reset the POSTORIUS_TEMPLATE_BASE_URL (in settings.py) back to the domain name, restarted everything, created a new Welcome template (using Postorius) and ... >>> import requests >>> r = >>> requests.get('https://MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/li…', >>> timeout=5) >>> r.text 'Another test Welcome message for new members.' >>> ... so all well there. And mailman is running mailman core ... # cd /opt/mailman/venv/bin/ # ls -la ... -rwxr-xr-x 1 mailman mailman 230 Jan 26 04:00 gunicorn -rwxr-xr-x 1 mailman mailman 231 Jan 26 04:00 mailman -rwxr-xr-x 1 mailman mailman 230 Mar 25 22:18 mailman-web ...

1 year, 3 months

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

by Jeff

> On May 11, 2021, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > Set base_url: in /usr/local/mailman3/mailman-hyperkitty.cfg to a url > that will reliably access HyperKitty, probably the same base URL that a > user with a web browser would use. > Thanks Mark, 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? 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? 3) Similar to above, some messages are in: /usr/local/mailman3/mm/var/queue/bad How can I get these messages processed? 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? Thanks again for any help anyone can provide. Jeff

4 years, 2 months

[MM3-users] Re: How to remove a message with an invalid Message-Id?

by Mark Sapiro

On 6/14/23 15:12, McGuire, Tommy M. (MSFC-IS61)[EAST2] via Mailman-users wrote: > I have a fun problem: apparently a message sent to a mailing list has an invalid Message-Id (I think), which is causing the message parse to fail while attempting to archive the message. Unfortunately, the message seems to be trapped somewhere and resulting in error logging every few minutes. Is there any way to find and remove the message? > > Literally, the only thing I've been able to find out about it is that the Message-Id contains the text "[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>". This is https://gitlab.com/mailman/mailman/-/issues/1065 which is fixed for the next release by https://gitlab.com/mailman/mailman/-/merge_requests/1099 You will find the message queued at Mailman's var/archives/hyperkitty/spool/ directory. You can examine the pickled message object with `mailman qfile` and you can simply remove the file. If you want to "fix" it and archive it, A `mailman shell` interaction like this will do it ``` >>> import pickle >>> with open('/path/to/.pck/file', 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Message-ID', '<83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com>') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Can't send emails to list users

by Stephen J. Turnbull

Rob Passalacqua writes: > I've looked on the forums and haven't found someone with the exact same issue as me. > It appears that my mailman 3 server is either only sending to the > first3 recipients on the list or only sending out mail to users > that are members in Django because only 3 recipients are getting > the emails. How many people are on each of the lists which exhibit this problem? Have you checked for unsubscriptions or disabled subscriptions? Are you sure all subscribed addresses have been validated by the subscribers? How do you know only 3 recipients are getting the emails, did someone complain they're not getting them? Is it the same person every time? Is it the poster themself? If so, is that person's email service provided by Google? (Google discards mail sent by the recipient in favor of the copy in the sent folder.) Is it a person who is also an explicit addressee, or are they on multiple lists and only receiving one copy? If so, is that person's email provided by an Exchange server? (Exchange automatically deduplicates delivered email.) > Here is my /var/log/mailman3/smtp.log: > Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.028921127319335938 seconds This shows delivery to FOUR recipients? Which of the log messages are relevant to your report? There are only three or four patterns there, you could have edited down to make it comprehensible. Steve

1 year, 10 months

[MM3-users] Re: Moving mm3 -> mm3 to different host

by Mark Sapiro

On 10/19/23 02:38, Axel Rau wrote: > Hi all, > > There are lots of threads for mm2 -> mm3 moves, but only one > thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining > the steps, but I can't find it again. > > I have created a working mm3 installation on the new host with both > mailman and mail-web dbs imported. > hyperkitty archive seems to in the db. > > What are the next steps to complete the transfer? > > - rsyncing messages, lists and templates to new host You may want to add archives/prototype to that. Also note that the contents of the messages/ directory should correspond to the entries in the message table in the mailman db. > - Setting up DNS CNAMES to the new server > - Adapting exim to accept mails to the aliased domain > > - Can I keep the old listname, with the old domain name? As long as mail to the list at that domain gets delivered to the new server. Note that in DNS if the domain has an MX record it must point to a domain with and A record and if there is no MX record, there must be an A record. CNAMEs won't do for mail delivery. > -What else has to be done ? I think that's it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Problems getting started with postorius

by Alain D D Williams

I am having another go with mailman3, being a long time MM2 user, but am getting increasingly frustrated. I am using on Debian 12 (Bookworm) and have installed the various Debian packages - mailman3-full does that. I have successfully started the mailman3 and mailman3-web services. I went to: http://localhost/mailman3/postorius/domains/new/ 'Add a new domain' I enter a 'Mail Host' -- a domain that does exist on this machine I choose a Web host from the drop down list -- same as Mail Host I click on 'Create Domain' and the page refreshes with the same information but under the Mail Host I see in red: {"title": "500 Internal Server Error"} I eventually tracked it down. The problem was that I had signed in with an account "addw@localhost". That, for some reason, failed validation above. I hacked the database and changed to "addw(a)localhost.localdomain" and creating the new domain worked. I could send email to addw@localhost - so at the MTA level it is correct. So please can the initial account creation do the same validation as does adding a new domain. I have looked but cannot find any documentation on postorius than https://docs.mailman3.org/projects/postorius/en/latest/ which is not helpful for a user or system admin. Can you point me to something better. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

8 months, 2 weeks

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

by Dmitry Makovey

On 10/18/2017 01:41 PM, Abhilash Raj wrote: > Hi, > > $ docker-compose rm -f mailman-web > $ docker-compose up -d mailman-web > > This will basically create a new container for Mailman-web, but, since > the state of mailman-web is stored completely in database (database > container), I am not sure how to reset *just* mailman-web without > dropping mailman-core related tables too (they share the same database > but have their own separate tables). The above command will get you a > fresh copy of code running. > > You can potentially get the list of tables and drop them, or maybe > Diango has some way to reset it's state from Django shell (python > manage.py <http://manage.py> shell, from inside mailman-web will get you > shell). I may have to look it up. > > Also, just by looking at the traceback, I am not sure about the exact > error. I may have to debug more to arrive at a better conclusion, which > I won't able to do until after this weekend. after a full remove of the DB - I still get this error. I left some of the directories intact but for the most part it's a fresh new install that gets the same error where previous didn't give us as much trouble. Something else must be messed up. logs show very little detail other than originally posted exception. I'll try to dig up some more info... -- Sr System and DevOps Engineer SoM IRT

7 years, 9 months

[MM3-users] Re: "Approved:" header from mailman2 times

by Mark Sapiro

On 04/09/2018 03:59 PM, Abhilash Raj wrote: > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: >> Hi, >> >> is there any equivalent to "Approved" header that was present in MM2 in >> MM3 land? Google is not very helpful in that. > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. I don't think it is broken, but it requires setting the moderator_password attribute for the list which can be set visa REST but I think not by mailmanclient. > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > Agreed. This is a shared password. and would be sent in plain text as a header or body line. It would be nice though to have some feature to enable, for example, spoof proof posting to a one-way (announce only) list. One thought on how to do this would be to have a list attribute that says posts from 'authenticated' owners and moderators can be auto approved and authentication could be by PGP signing the post. This would require Mailman to have the ability to verify a PGP signature from an owner or moderator which is not currently the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Mailman3 Issue with Sending Mail to Yahoo/AOL

by Mark Dadgar

Yes. I have been running a private motorsports community mailing list in the SF Bay Area for ~20 years and the only ISP that consistently does this is anything Yahoo touches. And there’s not much you can do about it, other than continue to follow deliverability best practices. Fortunately, most of the time the email is merely deferred semi-briefly. But it is a gigantic PITA. - Mark ----- mark(a)pdc-racing.net | 408-348-2878 > On May 12, 2021, at 8:53 AM, Apollinaris Schöll <aschoell(a)gmail.com> wrote: > > It’s not you. I am managing a neighborhood list too and yahoo flags them for many users as spam. And few times yahoo bounced messages for a day for at least 50% of subscribers. ATT has been even worse. Full bounce of all emails for a week at a time. No problems with any other provider > >> On May 12, 2021, at 8:00 AM, chris--- via Mailman-users <mailman-users(a)mailman3.org> wrote: >> >> That's the trouble ... I'm certain SPF and DKIM are correct. I've ran them thru the checker, and all appears to pass properly. So I'm really at a loss. >> _______________________________________________ >> 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, 2 months

[MM3-users] Logging subscriptions and unsubscriptions

by Christian Schoepplein

Hi, I am in the process to migrate from mailman 2 to mailman 3 and currently I am setting up the new environment and do some tests and play around with the new system. I'd like to have a seperate log for list subscriptions and unsubscriptions. For that reason I added the following section to the mailman-extra.cfg file: [logging.subscribe] path: subscribe.log That created a file called subscribe.log but not everything regarding subscription / unsubscriptions is added to the file. When subscribing and unsubscribing a user via mail only the following line is shown: Aug 27 10:58:31 2021 (28) tmod(a)mm3.example.com: held subscription request from chris(a)example.com Nothing regarding the finished subscription and absolutely nothing regarding the unsubscription performed later. Also in mailman.log I can find the following lines: Aug 27 10:58:05 2021 (28) deque: do_confirm_verify Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 356, in _step_send_confirmation raise StopIteration StopIteration Aug 27 10:58:31 2021 (28) deque: subscribe_from_restored Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 326, in _step_get_moderator_approval raise StopIteration StopIteration Aug 27 10:58:33 2021 (29) OWNER: <163005471133.28.13827351997075408419@mailman-core> Is this because a higher logging level or is this an error? I can find nothing really helpfull regarding subscriptions and unsubscriptions in any logfile. Is this wanted or can this changed by any configuration setting or are this information stored in the database? Cheers, Schoepp

3 years, 11 months

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

by Mark Sapiro

On 5/22/23 12:42, ceo(a)sartrack.nz wrote: > I found the problem with Exim4. > The Exim4 config file should contain this: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > and NOT > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > Somewhere the documentation is wrong. The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} Where did you see MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > But I now have the next problem: > I send an email to a new mailing list called templist(a)sartrack.nz (I imported my old list members). > in /var/log/mailman3 I get an error regarding this; > The (final) error states: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/lists/templist.sartrack.nz/digest.mmdf' > > The file digest.mmdf does not exist there at all. Because Mailman was trying to create it and couldn't. I suspect you ran `mailman create` as root and the /var/lib/mailman3/lists/templist.sartrack.nz/ got created with user:group as root:root rather than the mailman user and group. Recent Mailman versions won't run the `mailman` command as root without a --run-as-root option for this reason. How are you installing Mailman? > The mailing server does not send out any emails for "templist" This is a separate issue from the above error, but it might also be a permissions error. What other errors do you see in /var/log/mailman3/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

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

by Mark Sapiro

On 6/8/19 4:33 PM, Andrew Bernard wrote: > Hi Mark, > > Thanks for your great help. But despite decades of UNIX experience, my area > is not Django (yet). The nub of my question is that I thought you have to > have a manage.py file for Django to be able to set up the various affairs, > such as making the database migrations and so on. It is that that is > eluding me. Apologies for this hopelessly newbie question. The equivalent of manage.py in what I suggested is /opt/mailman/bin/django-admin. > I was impressed with your method of installation in the page referenced, > and I have foolwed that closely. But I am puzzled about the build script. > If I run as user mailman, not root, it wanted to install under /usr. which > of course results in permission denied. I had to modify the script to say > this: > > python setup.py install --prefix /opt/mailman/mm/venv If you want to install in the virtualenv, you should just activate the virtualenv and it should work. Perhaps the issue is that the build script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> assumes the virtualenv is at /opt/mailman/mm/venv. You need to insure that the '. ../mm/venv/bin/activate' line is actually pointing to your 'venv/bin/activate' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Bounce processing

by Mark Sapiro

On 4/23/20 2:27 PM, Andrew Hodgson wrote: > > When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. The message the user is sent in built from the list:user:notice:warning template. The next release of Postorius will offer that template as one you can edit, but the current release doesn't. You can make an edited template in the var/templates/ directory. The logged-in user can go to her settings pages in Postorius at accounts/subscriptions/ to set delivery status. The generic template can't be that specific because Mailman Core doesn't even know if you have Postorius. > I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. The bounce recognition for Mailman 3 is essentially the same as Mailman 2.1. If you post one of these complete bounce messages, we'll investigate why it isn't recognized. -- 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: Welcome message template errors

by Mark

On 2024-04-28 01:32, Mark Sapiro wrote: >> I also note that this timeout only occurs when it is a subscription >> via REST. I.e. subscription via email or `mailman addmembers` sends >> the proper welcome message. >> >> So it has something to do with the retrieval being done by a rest >> runner, but I still don't know what the underlying issue is. I created a text file as a custom welcome message and chowned it to mailman:mailman, then edited the database record (template.uri) from http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… TO file:///home/mark/welcome.txt This delivered the custom welcome message to the user when subscribed via Mass Subscribe. I'm not sure what this tells me other than a call can be made to a file but not the database. > More strangeness. I've now done a test on one of the production > servers I manage, and there is no error. Both the production server > and the development server are running the identical Mailman code > installed in a venv, they both have the same version of urllib3 and > similar Python versions, 3.9.16 on the development server and 3.9.10 > on the production server. Both servers are running under Ubuntu > 20.04.6. The only other difference I see is on the production server > everything runs as user mailman and on the development server > everything runs as user mark. Mine is Debian 12 with Python 3.11.2. Could a newer Python version really cause this amount of grief?

1 year, 3 months

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

by Stephen J. Turnbull

Allan Hansen writes: > What is the best, easiest, guaranteed-to-work way to get this > Mailman 3 up and running (OS, add-ons, options, etc.). When I tried > myself, I saw a lot of options that I really did not really care to > have because I did not know the consequences of each. I’m an > application programmer, not a systems programmer. It's email, there are no guarantees. I hate to say that, but that's the way it is. In particular, I'm concerned about the "iRedMail" integration, which may be a complete wildcard from my point of view. With respect to the relevant iRedMail components, I can say that Mailman 3 is perfectly happy with Postfix as MTA (it's the recommended configuration, although I use Exim4 for historical reasons), and I've been satisfied with a small-scale set of lists (about 10 active ones, with at most 20 subscribers total) using Apache+mod_swgi to host Postorius and HyperKitty. The problem would be if your friend (is that the Frank in the CC? hi, Frank!) really really wants to manage Mailman 3 through iRedAdmin -- that will get messy I suspect, and pragmatically speaking, we can't support it, we don't have the cycles. So he'd be on his own, especially since the iRedMail folks have their own bespoke mailing list manager. I would recommend avoiding iRedAdmin integration, and just using Postorius since the subscribers and non-site-admin moderators (if any) will need to use Postorius anyway. Ignoring the iRedAdmin issue, the absolute simplest is 1. Install any Linux distribution with a Docker package. 2. Install the distribution's Docker package. 3. Download and install Mailman Project's Mailman 3 container. 4. Upgrade the container manually (ie, download and reinstall) as appropriate. For reference, what I would recommend to my friends, who would give me hands-on access in emergencies: 1. Install the Debian distribution. (What I use.) 2. Pin the Mailman 3 packages to "experimental". The idea would be to get Mailman 3 upgrades as fast as possible, even at the risk of packaging issues. (My experience with default-to-experimental system for several years was that this happened at most once a year, and the three or four cases all got fixed within days.) 3. Install the Mailman 3 packages. 4. Adjust any dependencies that need non-"stable" versions. 5. Upgrade via apt or whatever occasionally. 6. When Mailman 3 is working well, downgrade the pins to a more stable level. Since you do have such a friend, there's probably a similar process that works for his distribution-of-choice. > The problem is that my MacOS users are getting tripped up by the > mangling, as it is hidden by the mail clients. I have instructed > them to remove previous recipients regularly from the list of such, > if they contain the ‘via list’ string. But they don’t read my > emails, and we see many embarrassing email ssent to the lists that > are meant for one-on-one communication. I guess we could provide a setting where reply-to goes *only* to author, instead of to author *and* list as we currently recommend. But that is going to make you (or list owners) the focus of user ire because their intended replies to list go only to author. What do you think? tl;dr The rest is me blowing off steam. :-) > The fact that the mangling will continue is a disappointment. It's a disappointment to the sane people at the IETF, too, including the rep from Yahoo!, who's a very smart lady (I may be biased, she gave me a kitten once. ;-) Yahoo! is violating the original concept (DMARC "p=reject" was supposed to be used *only* for "transactional" mail, i.e., direct private communication between a business and its clients), but I see her point: when you've had a hundred million or so address books hacked and sold to spammers, and the spammers are sending literally millions of "recommendation from a friend" spams per hour for days on end, you use the tools to hand. > I’m inclined to tell all my AOL and Yahoo users and others in the same > boat to find another email service. I know the feeling. I'm lucky in that respect: the Ministry of Education prohibits use of yahoo mailboxes at Japanese universities. (Which is a WTF of a different kind: yahoo.co.jp is a franchise, not controlled by yahoo.com, and doesn't use p=reject at least at the time MoE issued that policy.) Mail is just hard. It was designed for a "friendly network of users", not for today's rather hostile open Internet, and even if they had envisioned this in the 70s when the message format and SMTP mail transmission protocol were designed, the fundamental problem is that pretty much everyone has a genuine need, even if only occasional, to receive messages from untrusted and even unknown senders.

5 years, 8 months

[MM3-users] Re: Cannot start lmtp runner due to error while attempting to bind on address ('127.0.0.1', 8024): address already in use

by Stephen J. Turnbull

actionmystique(a)gmail.com writes: > Dovecot is the LMTP server > (https://doc.dovecot.org/configuration_manual/protocols/lmtp_server/) > listening on port 8024. > I thought that ```lmtp_port``` was precisely the port where to > contact the LMTP server, as described in the comments (cf. first > post). > - Are those comments wrong? In Mailman documentation, Mailman's LMTP server is *the* LMTP server. Mailman wouldn't send *to* an LMTP server, it would send to the MTA's "submission" port or to the SMTP port. > - Is mailman trying to act as a LMTP server instead? Yes. > - If so, wouldn't there be an issue with 2 LMTP servers if I choose > another port number for ```lmtp_port```? No. Apparently Dovecot made the same architectural decision that Mailman did: "I want to receive incoming mail via LMTP because all the MTAs I'm willing to talk to can do it that way so I don't have to worry about pipes and configs and sockets, oh my!" Both want to receive via LMTP. So it has to be different ports. Only the MTA and Mailman need to know Mailman's port, and ditto for MTA + Dovecot. Ie: LMTP SMTP +-----> Mailman @ 9024 -----> subscribers SMTP | (or whereever) Internet -----> MTA -+ | LMTP IMAP +-----> Dovecot @ 8024 -----> local users or whatever. (note to me: needs to be in dox) Steve

5 years, 7 months

[MM3-users] Mailman 3 centos7 installation issues

by bader＠cchmc.org

So I am working with our Linux admin to install mailman3 in centos7 following this instructions https://docs.mailman3.org/en/latest/install/virtualenv.html# (and adjusting for centos versus Debian) The install went fine with the command “pip install wheel mailman psycopg2-binary”until the config file. /etc/mailman3/mailman.cfg The /etc/mailman3 directory did not get created? Should it have? We created it and the config file But “mailman info” throws errors venv) [mailman@bmimailmandr2 var]$ mailman info Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2336, in _wrap_pool_connect return fn() File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 364, in connect return _ConnectionFairy._checkout(self) File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 778, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 495, in checkout rec = pool._do_get() File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/impl.py", line 140, in _do_get self._dec_overflow() File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ with_traceback=exc_tb, File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/impl.py", line 137, in _do_get return self._create_connection() File "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 309, in _create_connection return _ConnectionRecor I suspect it is not using the config file at /etc/mailman3/mailman.cfg But we do not even see a mailman service in /etc/systemd/system/mailman3.service. Also, we are using python 3.6, will that be a major issue? or should spend the time to install 3.7 from source?

4 years, 4 months

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Perry Kollmorgen

Ok, thanks for the information. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, 10 June 2024 2:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

1 year, 1 month

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

by Stephen J. Turnbull

Mihai Moldovan writes: > The imported messages, do have a Message-ID-Hash, but the > Archived-At and List-Archive headers are empty (literally <>). [...] > What are the proper header values for this module? Empty or omitted. See site-packages/mailman/archiving/prototype.py. If they're produced at all, I suppose that's a bug. Mailman core get the contents of those from the 'list_url' and 'permalink' callbacks defined by the archiver, which in the case of the prototype archiver return None. So Mailman should omit those headers and log an error message IMO. I believe your web-facing archive is HyperKitty. I suppose you should import those callbacks from HyperKitty (I think they're actually in the mailman_hyperkitty Python package) in order for your backup to reflect "archived message plus headers omitted by HyperKitty", (I haven't checked to see if you can actually just from mailman.archiving.prototype import Prototype from mailman_hyperkitty import Archiver class Backup(Prototype): list_url = Archiver.list_url permalink = Archiver.permalink but it that doesn't work cargo-culting the code should be straightforward. I forget if your goal was to reproduce the incoming message or the outgoing message. If the incoming message, archiving happens pretty late in the pipeline so banned attachments have been stripped and HTML-to-text conversion and the like have already been done. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 1 week

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

by Odhiambo Washington

@Eggert, I believe you used apt to install and so you have to wait for the package maintainer to avail the upgrades via apt. On Wed, Sep 29, 2021 at 7:48 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would > have > to bypass the Debian installer. Or will there be Debian packages > available? > Same question for Postorius 1.3.6 > > > Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb 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 > . > > html#news-3-3-5 > > > > 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/NE > > >> WS.html#news-3-3-5 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) > > > > > _______________________________________________ > 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/ > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 10 months

[MM3-users] Re: Your Dashboard

by Mark Dadgar

On Feb 11, 2020, at 12:26 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via Postorius. Awesome - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/9/21 8:56 AM, Richard Rosner wrote: > Mark Sapiro wrote: > >>> The REST API is apparently not listening on the host/port this is trying >> to connest to. > > Apparently. The question is why. You are in a better position to answer that than am I. What does `sudo netstat -lntp` show? What does `ps -fwwa|grep rest` show? >>> What is executing the manage.py command to start Django. Is it user list? > > Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. mailman3-web.service must also run as list. >>> I don't use uwsgi and know little about it so I don't know what the Unix >> domain socket /run/mailman3-web/uwsgi.sock connection is for, but this >> appears to be some miscunfiguration between apache and uwsgi. >> Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via >> tcp port 8000 and uwsgi is configured with >> [uwsgi] >> uwsgi-socket = 0.0.0.0:8000 > > I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx. So, what do you have in your apache config for proxying to uwsgi and what's your uwsgi configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: CPU usage when idle

by Mark Sapiro

On 5/28/25 08:27, roughnecks via Mailman-users wrote: > > It's the manage.py qcluster whatever is called. I have shut down MM for > the time being, because I'm not fully motivated to have it running, so I > can't be more accurate right now. I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend. Settings that control this are typically ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` and possibly a setting like `'workers': 2,` (default is the CPU count of the system but see <https://django-q2.readthedocs.io/en/master/configure.html#f1>). ``` CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION': '127.0.0.1:11211', } } ``` although the default if not set is ``` CACHES = { "default": { "BACKEND": "django.core.cache.backends.locmem.LocMemCache", } } ``` It is the `'orm': 'default'` setting that says to use Django's CACHES. See <https://django-q2.readthedocs.io/en/master/brokers.html#django-orm>. You can get info about what qcluster is doing with `manage.py qinfo` and monitor things with `manage.py qmemory` and `manage.py qmonitor`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

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

by Mark Sapiro

On 4/5/25 13:00, megabrutal--- via Mailman-users wrote: > Hi Everyone, > > I've recently installed Mailman3 and still testing it. I tried to reply to a topic on my own list while also being a superuser from HyperKitty, but I got this error message: > > "This list is moderated, please subscribe to it before posting." Is your login a member of the list? > Then why I even see the archive of the private list? What might be wrong? You can see the private archive because you are logged in as a superuser. > One thing that might confuse the system is that I added a secondary e-mail to my account. I thought it would allow me to post from any of my addresses, but it seems like it's not the case, looks like I can only subscribe with one of the addresses. How did you add that email? When you find yourself at https://example.com/mailman3/users and click Manage, do you see the expected addresses? > It also looks like HyperKitty has trouble matching up the addresses, as it lists 4 participants for the conversation, while 2 of them is my account, the other 2 is my test address. In reality, it should list 2 posters. This is normal. Hyperkitty lists participants by address whether or not the addresses are linked to the same user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 4 weeks

Search results for query "dO"