Search results for "Postorius" - Mailman-users

New Lists Appear in HyperKitty Archives, But No Mail Data is Shown

by Asif Muzammil

Hello, I have been troubleshooting an issue with our Mailman 3 archives. I have made a key observation that has helped narrow down the problem. While a newly created list appears in the HyperKitty archives, no email data is shown inside that list. *Problem:* When I create a new mailing list in Mailman Core and then visit the HyperKitty archives, the list is correctly displayed. However, when I send an email to that list, no mail data (messages) are shown inside it. The message count for the list remains at zero in the archives UI. *Expected Behavior:* I expect that when a new list is created, it should appear in the archives, and any emails sent to it should also be correctly displayed within that list. *System Environment:* - *Mailman Version:* Mailman 3.x - *Archiver:* HyperKitty - *Web Interface:* Postorius - *Database:* PostgreSQL - *Setup:* Mailman Core (/opt/mailman/venv) and the web components (venv_hk) are running in separate virtual environments on the same server. *Troubleshooting Steps Taken:* 1. *List Synchronization:* Creating a new list in Mailman Core immediately makes it visible in the HyperKitty archives, which confirms that the mailmanweb service is correctly communicating with the hyperkitty_mailinglist table. 2. *Email Injection Test:* I used the mailman shell to inject a test email directly into a list. The inject_message function executed without errors. 3. *Configuration Check:* I have verified that the base_url in the Mailman archiver configuration (mailman-hyperkitty.cfg) and the MAILMAN_ARCHIVER_KEY in the HyperKitty settings file (settings.py) are correctly set and match. Could this be due to an API key or permissions issue preventing the data from being written, even though the tables exist? Any advice on what to check next would be extremely helpful. Thanks

2 months

IsADirectoryError: [Errno 21] Is a directory: '/usr/local/lib/python3.7/site-packages/mailman/templates'

by sunil soprey

Has anyone encountered this error? I pulled the latest mailman suite (versions below), and facing this error in two places * mass subscription add of users -> Click on mass-subscription for list, enter email Django 2.2.11 django-allauth 0.41.0 django-appconf 1.0.3 django-ca 1.15.0 django-compressor 2.4 django-extensions 2.2.8 django-gravatar2 1.4.4 django-gunicorn 0.1.1 django-haystack 2.8.1 django-health-check 3.12.1 django-mailman3 1.3.2 django-object-actions 2.0.0 django-picklefield 2.1.1 django-prometheus 2.0.0 django-q 1.2.1 django-redis 4.11.0 django-redis-cache 2.1.0 django-rest-auth 0.9.5 django-saml2-auth 2.2.1 djangorestframework 3.11.0 djangorestframework-jwt 1.11.0 python3 -V Python 3.7.6 django-mailman3 1.3.2 HyperKitty 1.3.2 mailman 3.3.0 mailman-hyperkitty 1.1.0 mailmanclient 3.3.0 postorius 1.3.2 sADirectoryError: [Errno 21] Is a directory: '/usr/local/lib/python3.7/site-packages/mailman/templates' [2020-03-17 03:56:54 +0000] [4220] [ERROR] Socket error processing request. Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 190, in andle_request util.reraise(*sys.exc_info()) File "/usr/local/lib/python3.7/site-packages/gunicorn/util.py", line 625, in reraise raise value File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 175, in andle_request respiter = self.wsgi(environ, resp.start_response) File "/usr/local/lib/python3.7/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.7/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/usr/local/lib/python3.7/site-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/local/lib/python3.7/site-packages/mailman/app/subscriptions.py", line 523, in register list(workflow) File "/usr/local/lib/python3.7/site-packages/mailman/app/workflow.py", line 69, in __next__ return step()

5 years, 5 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

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

3 years, 7 months

Re: Strange error in uwsgi-error.log

by Derek Lambert

Brian, I'd presume it's from something recent since you only started seeing it after updating. Do you recall what the prior version was? To drop the constraint on postgres I did: alter table hyperkitty_mailinglist alter column description drop not null; That's pretty standard SQL so I'd imagine it'd work on other platforms. After dropping it the error message is no longer logged, but none of the maillists have descriptions in HK. To add the constraint back after the bug is fixed: alter table hyperkitty_mailinglist alter column description set not null; Derek On 2/6/19, 4:23 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: Derek Lambert wrote: > Brian, > > When I was seeing this, new lists weren't showing in HyperKitty. > > I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from > functioning. I had to drop the constraint to get the lists in. None of them have a > description now. > > Was this working for you in the past? If so, did you do any updates recently? > > Derek Lambert Hi Derek, Actually you are right. None of my new lists are showing in https://urldefense.proofpoint.com/v2/url?u=http-3A__mailmam3domain_hyperkit…. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install. How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched. Brian _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

6 years, 7 months

Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

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

3 years, 3 months

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

by Guillermo Hernandez (Oldno7)

El 21/4/23 a las 11:03, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 21/4/23 a las 10:37, Odhiambo Washington escribió: >> >> >> On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via >> Mailman-users <mailman-users(a)mailman3.org> wrote: >> >> I'm having troubles with Django and cannot access to web admin. >> >> I need to unhold a message while figures out what is happening. >> >> Searching the mailman cli help commands didn't help me. >> >> Anyone who knows how to unhold a message, please? >> >> >> TBH, I find it a lot easier to fix the web UI than mess with the >> python shell :-) > Well... I found you where right. Messing with the CLI seems a nightmare to me. The problem with the UI seems solved. What I finally have done: Detected that the module "asgiref" was in a different version that the server (with all the same config) that is working. pip upgraded it. This didn't work, but it raised new error messages (about hyperkitty parsing messages) Installed pip-review and upgraded ALL python modules with pip-review --local --interactive (Re)upgraded all mailman3 packages with pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi Restarted apache24 And then all begun to work. Thanks a lot for your advising and help. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 4 months

Re: Create a mailman-web admin user

by Roland Giesler

On 2024/07/30 17:10, Odhiambo Washington via Mailman-users wrote: > On Tue, Jul 30, 2024 at 4:55 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/30 15:48, Roland Giesler via Mailman-users wrote: >>> However, which user in the mailman user mentioned? >>> >>> I tried to do this as root, but login in as an admin doesn't give me >>> any option to create new lists in postorius. What am I missing / >>> doing wrong? >>> >> I seem to have solved the riddle. The "mailman-web createsuperuser" >> command suggest the the mailman user is www-data, which I accepted. That >> worked and I can now create a new list from Postorius. >> > Actually, it wasn't a riddle. > You looked at documentation meant for the virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html>installation > method while your installation seems to be done from your OS package > distribution. > The OS package installation is fraught with pain. The virtualenv method is > the officially recommended. I use Linux LXC containers mostly in Proxmox, so adding another layer by using docker or something else to mean seems like another layer of complication. The documentation is obviously good enough for people that know how already, but need to look up a detail here or, but for a first time mailman user it is a bit of a nightmare. Once I have chewed my way through all the traps and tunnels, I intend to do something about this. I can't contribute to code here, but I can make it easier for the next person coming along. > > >

1 year, 1 month

MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Hi, I've spent the past week slowly migrating from MM2.1 to MM3.3. One of the lists migrated was set to hold all user posts for moderation, as the list isn't a discussion list but a newsletter sent out on occasion to user/members. I am seeing unexpected behaviour post-migration. The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a non-member posts to the list" -- it says `Hold for moderation` The migrated members when viewed all have a Moderation Action of `Hold for moderation`, which is also expected. When I add new members through Mass operations -> Mass subscribe, the new members have a Moderation Action of `None`. I've looked through the archives of this list, and from what I can tell: According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > None does not mean no moderation. None means use the list default > as opposed to one of the specific actions defined The thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… seems to also repeat the above, that `none` means the configured setting for the list. However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is `None`, but when I posted to the list from the address, it was not held for moderation, and went through. Am I missing something with the expected functionality? If it helps; Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] Postorius Version 1.3.8 Cheers, Mark

9 months, 3 weeks

Re: How to add new Domain?

by Mark Sapiro

On 2/4/25 15:59, c.benner--- via Mailman-users wrote: > > After that I'll go to the admin page xxxx/mailman3/admin which brings django admin page up. > On that page I'll add "websites" and add testdomain2.net That tells Django that this is a known domain for accessing the web UI, but you also have to add it to the ALLOWED_HOSTS setting in your Django settings. > Last step is adding "mail domain" site: testdomain2.net mail domain: testdomain2.net > > After that I can add lists to that domain and mails to any list @testdomain2,net should be routed right? That's all correct. > Maybe I'm to old (56yrs) but I've read a lot of documentation and everything was clear and understandable. It was never a question of linux or windows OS but on who'S writing the doc. I can't find any doc about the web part? What about Users having no acces to the shell but the Web-Frontend? Some pictures and a "How to" and "what if" would be great! > > But it's alos possible that I'm not finding it and it's somewhere out there. You may find https://docs.djangoproject.com/en/5.1/ref/contrib/sites/to be helpful. Documentation of the Postorius UI is sorely lacking. The good news (hopefully) is the UI itself is fairly straight forward and self-documenting, but there is really no separate documentation for list owners or site admins. There is a user's manual for list members at https://docs.mailman3.org/en/latest/userguide.html but nothing similar for list admins. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

Re: Easiest way to install a new mailman3 deployment?

by Brian Carpenter

On 12/31/20 8:13 PM, ieso(a)johnwillson.com wrote: > So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time. > > I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner. > > A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test. > > The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front. > > Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?) > > Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-) > _______________________________________________ > 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/ If you are looking for commercial assistance, please visit our Mailman 3 hosting site at https://mailmanhost.com (Harmony Lists). Feel free to contact me off list if you have any questions. For us, we chose Debian 10, Postfix, Nginx, and PostgreSQL as the server environment for Mailman 3. We used PIP via a Python virtual environment to install Mailman 3 from source. The Debian packages I believe have older versions of Mailman 3/Postorius/Hyperkitty which is why we went with source. I have a walk-through that is a work in project at: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I am available to hire to install Mailman 3 for you if you want to run your own server. With Harmony Lists, we went a step further with Mailman 3 and created our own custom interfaces: Affinity (admin) and Empathy (forum/archive). However they are only available to our own Mailman 3 clients. Have a Happy New Year. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

Mailman-users search results for query "Postorius"