Search results for "2021" - Mailman-users

Re: Setting for archiving multi email domains?

by Duane Raymond

FYI: in the mailman log was also the following traceback Mar 04 14:08:24 2021 (5044) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 84, in process for member in mlist.regular_members.members File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 83, in <genexpr> recipients = set(member.address.email File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 239, in members yield from self._get_members(DeliveryMode.regular) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 226, in _get_members if member.delivery_mode in delivery_modes: File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 212, in delivery_mode return self._lookup('delivery_mode') File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup pref = getattr(self.address.preferences, preference) AttributeError: 'NoneType' object has no attribute 'preferences' Mar 04 14:08:24 2021 (5044) SHUNTING: 1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4

4 years, 4 months

Re: docker mailman-core mailman3 image not responding on port 8024

by bob B

thanks, so i stop all containers ******************************** docker-mailman]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [SERVER1 docker-mailman]# ******************************* I added this to my docker.yaml ************************* networks: mailman: driver: bridge ipam: driver: default config: - subnet: 172.19.199.0/24 gateway: 172.19.199.1 ************************* I specified ips on my containers in docker.yaml i.e ************* . . . mailman: ipv4_address: 172.19.199.3 ************** When I try to start I get the below i get the below error? ******** docker-compose up -d Removing dockermailman_database_1 Recreating 2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_dockermailman_dRecreating 2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_dockermailman_database_1 ... error ERROR: for 2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_2eaf91c7d09d_dockermailman_database_1 b'user specified IP address is supported only when connecting to networks with user configured subnets' ERROR: for database b'user specified IP address is supported only when connecting to networks with user configured subnets' ERROR: Encountered errors while bringing up the project. ****** Here is my docker version could that be the issue??? *************** Client: Docker Engine - Community Version: 20.10.7 API version: 1.41 Go version: go1.13.15 Git commit: f0df350 Built: Wed Jun 2 11:58:10 2021 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.7 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: b0f5bc3 Built: Wed Jun 2 11:56:35 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.6 GitCommit: d71fcd7d8303cbf684402823e425e9dd2e99285d runc: Version: 1.0.0-rc95 GitCommit: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7 docker-init: Version: 0.19.0 GitCommit: de40ad0 docker-mailman]# ***************

3 years, 10 months

Re: New messages not being archived

by Sarah H

I took a look at the pickle files, this last one didn't have the archive locations but another had Archived-At: <> List-Archive: <> as well, so it looks like it's not being passed properly to the archive location? (venv) [mailman@sysname spool]$ mailman qfile 1626122072.7275724+5f84b41c279cea5ae5476554fefbfc514222f582.pck [----- start pickle -----] <----- start object 1 -----> Received: from sysname (localhost [IPv6:::1]) by sysname.localdomain (Postfix) with ESMTP id E01A9DDA309 for <admin(a)lists.client.org>; Mon, 12 Jul 2021 13:34:29 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: sarah@email To: admin(a)lists.client.org Date: Mon, 12 Jul 2021 20:34:29 -0000 Message-ID: <162612206991.3661556.4632729438422001860@sysname> User-Agent: HyperKitty on http://lists.client.org/ Message-ID-Hash: JZP2CHGVCD4THRJ5KPF3GFAK2MOW26VN X-Message-ID-Hash: JZP2CHGVCD4THRJ5KPF3GFAK2MOW26VN X-MailFrom: sarah@email X-Mailman-Rule-Hits: member-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address X-Mailman-Version: 3.3.4 Precedence: list Subject: [Admin] one last test List-Id: admin testing list <admin.lists.client.org> List-Help: <mailto:admin-request@lists.client.org?subject=help> List-Owner: <mailto:admin-owner@lists.client.org> List-Post: <mailto:admin@lists.client.org> List-Subscribe: <mailto:admin-join@lists.client.org> List-Unsubscribe: <mailto:admin-leave@lists.client.org> try this one more time. <----- start object 2 -----> { '_parsemsg': False, 'mlist': <mailing list "admin(a)lists.client.org" at 0x7f34eecc1a20>, 'version': 3} [----- end pickle -----]

3 years, 11 months

Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote: > > > > > On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > > > On Sat, 13 Mar 2021 14:46:55 -0500, > > Mark Sapiro wrote: > >> > >> On 3/13/21 11:14 AM, John Covici wrote: > >>> > >>> Now one thing came up while trying to create the database, I got a > >>> traceback complaining about a revision error because gentoo had a > >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I > >>> upgrade mailman, am I going to have to do something to the database as > >>> well and why should the database have some kind of reference to the > >>> mailman version? > >> > >> > >> I don't know why this is an issue. You shouldn't need to do anything > >> with the database when you upgrade. Please post the full traceback and > >> error message. > > > > Sorry I can't reproduce it, after dropping and recreating the database > > the error went away, but it was in alembic and it was talking about an > > invalid revision and gave a long hex string. > > > > > 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. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 3 months

Re: installing a new instance of mm3

by Christian Stalberg

mailman.log is showing this: ERROR 2021-10-18 22:19:12,385 616 django.security.DisallowedHost Invalid HTTP_HOST header: 'subdomain.domain.tld'. You may need to add 'subdomain.domain.tld' to ALLOWED_HOSTS. ERROR 2021-10-18 23:01:15,318 616 django.security.DisallowedHost Invalid HTTP_HOST header: '192.168.0.1'. You may need to add '192.168.0.1' to ALLOWED_HOSTS. Where do those entries go? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 11:44 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: installing a new instance of mm3 On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm > getting nowhere with diagnostics and troubleshooting (which was easier > with mailman 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

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

Re: mm3 floods syslog

by Mark Sapiro

On 10/31/21 4:18 AM, Wolfgang Bock via Mailman-users wrote: > Dear friends, > > I got another problem: mailman floods my syslog. > > I deleted a domain/webdomain (further mentioned as deleted.org) in > postorius, django web. No entries are now in > /var/lib/mailman3/data/postfix_domains or postfix_lmtp or > /var/lib/mailman3/lists. > > > Here an extract of my syslog (anonymized): > Oct 31 10:49:02 myserver mailman3[1284]: Oct 31 10:49:02 2021 (1284) > Certificate did not match expected hostname: localhost. Certificate: > {'subject': ((('commonName', 'deleteted.org'),),), 'issuer': > ((('countryName', 'US'),), (('or > ganizationName', "Let's Encrypt"),), (('commonName', 'R3'),)), 'version': 3, > 'serialNumber': '0326A733CA7B16D13C830EE707EA614E25F9', 'notBefore': 'Oct 30 > 20:21:08 2021 GMT', 'notAfter': 'Jan 28 20:21:07 2022 GMT', > 'subjectAltName': (('DN > S', 'deleteted.org'), ('DNS', 'lists.deleteted.org'), ('DNS', > 'mail.deleteted.org'), ('DNS', 'ns.deleteted.org'), ('DNS', > 'www.deleteted.org')), 'OCSP': ('http://r3.o.lencr.org',), 'caIssuers': > ('http:/ > /r3.i.lencr.org/',)} > > This appears nonstop. Your ssl certificate is for the domain `deleted.org` with alt names `lists.deleted.org`, `ns.deleted.org`, `mail.deleted.org` and `www.deleted.org`. Django is accessing things at a URL for a different domain. Get a new certificate for the domain(s) you are actually using. -- 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

Trying basic install of mailman3 in docker, but how do you set allowed hosts?

by bob B

I am starting small, My goal is just to get mailman3 running in docker and test the website access via curl from the host, then I will move on from there In the docker instructions it says SERVE_FROM_DOMAIN: The domain name from which Django will be served. To be added to ALLOWED_HOSTS in django settings. Default value is not set. This also replaces Django's default example.com SITE and becomes the default SITE (with SITE_ID=1). But where do I set the ALLOWED_HOSTS I added this to the yaml file - ALLOWED_HOSTS=127.0.0.1 under environments mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - ALLOWED_HOSTS=127.0.0.1 - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - SECRET_KEY=333blah-blah-secret - HYPERKITTY_API_KEY=333someapikey ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: But when I try: [docker-mailman]# curl 127.0.0.1:8000 <h1>Bad Request (400)</h1>[root@bmimailmandr1 docker-mailman]# [root@bmimailmandr1 docker-mailman]# I see this in the logs [docker-mailman]# cat /opt/mailman/web/logs/mailmanweb.log WARNING 2021-07-08 17:40:46,979 1642 django.request Bad Request: / ERROR 2021-07-08 19:20:58,416 1641 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: /

3 years, 11 months

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

No matter what i try, mailman still only connects without STARTTLS: /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: smtp_verify_hostname: false smtp_verify_cert: false smtp_secure_mode: starttls systemctl restart mailman3 Nov 9 12:14:52 al02 postfix/smtpd[4183267]: connect from localhost[::1] Nov 9 12:14:52 al02 postfix/smtpd[4183276]: connect from localhost[::1] Nov 9 12:14:52 al02 postfix/smtpd[4183276]: disconnect from localhost[::1] ehlo=1 mail=0/1 rset=0/1 quit=1 commands=2/4 Did i miss something? Am Mo., 8. Nov. 2021 um 18:06 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com>: > awesome! Thank you a lot! > > Am Mo., 8. Nov. 2021 um 17:37 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > >> On 11/8/21 1:03 AM, Stefan Bauer wrote: >> > >> > how can we configure mailman3, to use STARTTLS when dropping mails to >> local >> > postfix for final delivery? >> >> >> Set `smtp_secure_mode: starttls` in the `mta` section of mailman.cfg. >> See >> >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… >> >> -- >> 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, 7 months

Re: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 12:39 PM, Mohsen Masoudfar wrote: > Hi Mark, > > Thanks again for the nice Python script. There is an issue with outlook.com. They add a '^M' (carriage Return) before msgid!! > Here is part of the log that shows that. This is not in every log, though. I updated the get_log_data function (please see below), I believe it is not the smartest solution, but it seems to be working for me. Does the script with your change produce a different result than the original? This has nothing to do with outlook.com per se. It only has to do with the length of the log message. Further, I do not think there are actually newlines in these log messages. I think that is just an artifact of how you are viewing the log. > Mar 14 12:53:21 2021 (11701) > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds I suspect if you do ``` grep namprd20.prod.outlook.com /path/to/var/logs/smtp.log ``` The result will be lines like ``` > Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds ``` whereas if they are really split, the result would be ``` > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Mailman-users search results for query "2021"