Search results for "2021" - Mailman-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, 4 months

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

4 months

"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, 9 months

Re: multiple sites on a mailman3 server question

by William Oliver

On Tue, 2021-12-28 at 18:23 -0800, David Newman wrote: > > > > [snip] > > I'm using nginx > I'd asked about this a few weeks ago for a MM3 host running Ngnix > with a > few virtual domains, one of which runs Roundcubemail as its default. > > Mark Sapiro suggested the following, and it seems to be working OK. > You'll need these lines in the Nginx config file for each virtual > host > you define. > > # begin mailman3 stuff > > location /static/ { > alias /opt/mailman/web/static/; > } > [snip] No joy. This just makes it kind of work as the mailman interface when it gets rewritten. My problem is that the url is getting referred to domainname/mailman3/lists even when I don't want it to. Adding these changes just (partially) loads the mailman3 interface when it gets rewritten. What I'm trying to figure out is where uwsgi yanks control from nginx and does the rewriting. Pulling that proxypass stuff out will stop mailman3 from coming up, and adding it allows mailman3 to show its interface, but the address gets referred regardless. Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell nginx not to push it to port 8000. But I don't see where nginx is getting told to go to 8000 in the www.domain.com section. billo

3 years, 6 months

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

by Nelson Strother

Well, this is using the default libsqlite 3.34.1 . One improvement is to use write-ahead logging: mailman@localhost:~$ sqlite3 /var/tmp/mailman/data/mailman.db SQLite version 3.34.1 2021-01-20 14:10:07 Enter ".help" for usage hints. sqlite> PRAGMA journal_mode = WAL; wal sqlite> This setting is persistent, and based on a small sample this seems to dramatically speed up the completion of root@localhost:~# systemctl stop mailman ## consumes <2 minutes with journal_mode = WAL; root@localhost:~# ## instead of up to 20 minutes with the default journal_mode = delete But this does not make a big change the completion time for: root@localhost:~# systemctl start mailman Since there is no point in busy waiting when running on a processor with only one core (as this virtual server), the next setting that I would like to try is change the sqlite busy_timeout from the default of none to 1 or 2 seconds, e.g.: sqlite> PRAGMA busy_timeout = 2000; 2000 sqlite> However, this setting is not persistent, and thus needs to be applied to each connection (i.e. tens of database connections are made during `systemctl start mailman`). I have not yet found where to insert this directive in mailman's database wrapper for SQLite. Might someone who has read more of the source be able to offer me a clue? On 6/8/23 15:47, Mark Sapiro wrote: > I would look to your database manager for the issue.

2 years

Re: Ann: Mailman Core 3.3.5b1 is out

by Brett Delmage

On Tue, 7 Sep 2021, Abhilash Raj wrote: > 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. Thanks for this. > 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. Does Mailman release stable versions with only software defects fixed and no new features? Are features frozen at this time for 3.3.5? If so, I'd be interested in helping test. > A full list of changes in this version can be found here[1]. > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… The heading "Bugs" has always bugged me because I star reading it as an list of outstandign bugs. . I believe that "Bug fixes" or "Software defects corrected" would be better heading. > 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 for your announcement and to everyone moving this forward. Brett

3 years, 9 months

Re: 3rd Party Account is not working

by Matthew Alberti

Same thing happens to me. If I comment out all the socialauth plugins, the web service doesnt work. Are you using the docker-mailman installation method? ⁣Get BlueMail for Android On Feb 16, 2021, 7:32 PM, at 7:32 PM, kwp.klein(a)gmail.com wrote: >Here is my /mailamn/config/mailman-web/settings_local.py. I get an >error message > >curl http://172.19.199.3:8000/postorius/lists/ >curl: (7) Failed connect to 172.19.199.3:8000; No route to host >Please comment out all the lines that are not necessary. > > >MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >EMAIL_HOST = '172.19.199.1' >EMAIL_PORT = 25 >USE_SSL = False > >INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > # 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'paintstore', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > #'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > #'allauth.socialaccount.providers.google', >) >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

Domain ownership issues

by peter＠chubb.wattle.id.au

Hi, I wanted to give another user the ability to create lists, so added that user as 'owner' of the domain. But he does not see the 'create list' button. I decided to try deleting him as owner, and the result is a python exception: KeyError: 'file' ERROR 2021-03-01 20:35:07,195 550 django.request Internal Server Error: /postori us/domains/sel4.systems/owners/b55d58c434c94f6dbd19ae338502dd2e/remove Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40 , in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/auth/decorators.py", line 75, i n wrapper return fn(*args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/domain.py", line 182, in remove_owners remove_email = client.get_user(user_id).addresses[0].email File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 324, in get_user display_name=display_name)) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 111, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: 404 Not Found Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.9.0+ (default, Oct 19 2020, 09:51:18) [GCC 10.2.0] Peter C

4 years, 4 months

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

Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

Dear Users, I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the web-interface via https://my.mailinglistserver.local/mailman3/postorius/lists/ I receive Not Found: /mailman//postorius/lists/ [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1) Where does the wrong path come from (mailman vs. mailman3) After enabling Debug, i see in the browser the following: Page not found (404) Request Method: GET Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ Using the URLconf defined in urls, Django tried these URL patterns, in this order: ^$ ^postorius/ ^hyperkitty/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] ^accounts/ ^admin/ The current path, /postorius/lists/, didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. My apache configuration is very simply: # more /etc/apache2/conf-enabled/mailman3.conf 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> I dont see where the path gets traversed in the wrong way. Any help is greatly appreciated. thank you. Stefan

3 years, 8 months

Mailman-users search results for query "2021"