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

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 9:51 AM, Andy Smith wrote: > > Over in Exim's mainlog I then see that delivered out to list > members. One of them rejects it at SMTP time, which I think causes > this: > > Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces(a)mailman.bitfolk.com>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces(a)mailman.bitfolk.com > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost > Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client() The SMTP rejection should not cause that. An SMTP recipient reject is processed internally and does not result in anything sent via SMTP to the list-bounces address. > …and I think that bounce message somehow incremented the bounce > score for andy(a)bitfolk.com even though that address was only present > in the original post's Cc: and body. If the original post was the message delivered to users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or another recognizer parsed those addresses from the message body. > Is there a good way to further debug this? Maybe by being able to > see the full content of the DSNs that Mailman generates? As I posted previously, the DSN that Mailman generates is defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…, but this message is not sent anywhere. It is only saved for possible inclusion in an admin notification or a probe message. If you send me the post as received from the list, I can run it through flufl.bounce and see what that produces. You might also be able to find the fake dsn and/or the message received via SMTP to users-bounces(a)mailman.bitfolk.com in Mailman's var/messages/ directory, although these are pickles and need to be examined with `mailman qfile`. > I think I've seen this before in the last couple of weeks so I'm > sure it'll crop up again soon. I've seen it mention about bounce > score for users-leave before, but I only really paid attention today > when it also listed my own address. users-leave probably is parsed out of the message footer. -- 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: Database read only error on mailman_sync job

by Ugnius

Thank You, Mark for guideline. I accidentally posted here. I wanted to start new thread and just replaced subject of messages. Message was sent to this thread anyway. The reason of this issue was very simple. I creadet symlink in /usr/local/bin/django-admin to /project/home/manage.py, because I was unable to set original django-admin file to work as it should to work. Later I decided to run mailman project under other user and forgot about that symbolic link. So it was normal, that previous user had no privileges on database file. Thank You for helping. > On 12 Sep 2019, at 21:50, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/1/19 1:02 AM, Ugnius S wrote: >> >> I guess that issue is hyperkitty database, but I even do not know the name >> and location of that database. > > See the DATABASES definition in your Django settings. The default is a > sqlite3 database named mailmansuite.db in the same directory as the > Django settings. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 5 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/20/22 11:40 PM, Josef Dietl wrote: > Dear all, > > > > Sorry for coming back to a topic that seems to be done for 18 months now. > > I'm staring at this issue for a few days now (on and off). But I still get > these messages: > > > > Jan 19 22:43:27 2022 (149439) HyperKitty failure on > https://lists.[...]/hyperkitty/api/mailman/urls: > <html><title>Forbidden</title><body> > > <h1>Access is forbidden</h1><p>Please check the IP addresses > > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > > </p></body></html> (403) > > > > . and consequently, nothing ends up in the archive. > > > > I have checked (among others): > - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP > address, different orders, '*'. OK. > (Asterisk makes a difference, see at the bottom) ??? I didn't see what. > - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in > mailman-hyperkitty.cfg (except for the quotes). According to the editor's > color coding, the quotes are "right", too. I have removed special characters > to circumvent diverging treatment in different environments > > - I guess it doesn't matter, but wget --user restadmin --password [.] > http://localhost:8001/3.1/lists works, too. That is Mailman core's REST API which is not the issue here. > - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter > > > > I'm running a fresh package installation from Debian Bullseye with > certificates from Certbot with nginx, so Certbot may have messed with my > nginx config, but even that seems to be OK: Yes, Certbot has inserted > http->https redirection, but I'd expect that a https base_url and > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. It should. Note that your primary resource for help with issue with Debian packages should be Debian. > Mailman info says ... > To provide all possible information, I'm also adding the nginx log that > seems to correspond to that request (no other requests at that time, give or > take five minutes): Yes, everything yields 403 response codes. > > > > [.] - - [19/Jan/2022:22:43:27 +0000] "GET > /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] > HTTP/1.1" 403 175 "-" "python-requests/2.25.1" The issue here is accessing the hyperkitty API. The base URL for these accesses is configured in mailman-hyperkitty.cfg. From what I see here, that is something like `http(s)://host.example.com/hyperkitty/` If you append `api/` to that base URL and go there in a web browser do you get a page of documentation of the HyperKitty API? If so, then figure out why it works from a web browser and not when Mailman core does it. If you get the 403, figure out why. This is probably an nginx issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

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

by Shashikanth Komandoor

Hi Mark, Thank you for your help. I have traced the versions of different components of mailman 3. I am downloading through GIT LAB because I need to modify the code according to my organization's requirements like to add SMS notifications when a mail is waiting for pending approval and so. With your help, I have found out the commits I am using in my environment. I got them using the way you suggested "git log". That may be helpful for you to help dummies like me. *### Mailman Core Version ###* *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* *Merge: 98cf97b 0bca998* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Thu Oct 15 14:02:36 2020 -0700* * Merge branch 'template' into 'master'* * Clarify the posting instruction in the list welcome message.* * See merge request mailman/mailman!723* *### django-mailman3 Version ###* *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* *Merge: ea2b33a c091e43* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:40:51 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/django-mailman3!108* *### Hyperkitty Version ###* *commit 36f43466763c2686cf4d69c982ea64b956c30939* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Mon Oct 5 04:54:44 2020 +0000* * Use GH registry to pull CI image.* *### Mailmanclient Version ###* *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* *Merge: ff39dd8 8670751* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 01:09:32 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/mailmanclient!130* *### Mailman Hyperkitty Version ###* *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* *Merge: 35ff801 04deff5* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Fri Jun 19 18:15:57 2020 +0000* * Merge branch 'fix_25' into 'master'* * Add a test for the presence of surrogates in the stringified message.* * Closes #25* * See merge request mailman/mailman-hyperkitty!7* *### Mailman-suite Version ###* *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* *Merge: 74e7927 4463b31* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Sat May 30 00:32:40 2020 +0000* * Merge branch 'doc_mb4' into 'master'* * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* * See merge request mailman/mailman-suite!8* *### Postorius Version ###* *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* *Merge: 61242d2 321310c* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:43:14 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use the GHCR registry for CI image.* * See merge request mailman/postorius!549* I have removed only mailmanclient and re-cloned it from gitlab and ran the python setup.py develop command. But still the same error. Is there anything else I can do to get rid of that error. Thanks in advance. <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, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > > > How to find out the versions of the each and every component > > of the mailman 3 like mailman core, mailmancilent, postorius, > > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > > after installation? > > > cd to the directory in which you cloned the gitlab project for the > component and do `git log` > > > > If I am running an old mailmanclient or older version of any > > other mailman component, please suggest how to upgrade either one or > > multiple components based on the requirement. Is there any link that > > would help me to upgrade ? > > > > I have used the > > link https://docs.mailman3.org/en/latest/devsetup.html to install the > > mailman 3 components. I expected that the procedure followed in this > > link would install the latest versions of the mailman 3 components. > > Please correct me if I am wrong. Is there any latest version > > compatibility table ? > > > If you installed each of mailman, mailmanclient, django-mailman3, > postorius and hyperkitty according to instructions like > > $ cd ~/mailman > $ git clone https://gitlab.com/mailman/mailmanclient.git > > Then set up mailmanclient: > > $ cd mailmanclient > $ python setup.py develop > $ cd .. > > from that document, you should have the latest version. If that is the > case, `git log` in the mailmanclient directory should begin like > > commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, > origin/master, origin/HEAD) > Merge: ff39dd8 8670751 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Thu Oct 15 01:09:32 2020 +0000 > > Merge branch 'fix-ci' into 'master' > > Use GHCR for the CI image > > See merge request mailman/mailmanclient!130 > > commit 8670751caff689733751ef323ef521c4a3fa1237 > Author: Abhilash Raj <raj.abhilash1(a)gmail.com> > Date: Wed Oct 14 17:36:58 2020 -0700 > > Use GHCR for the CI image > > commit ff39dd8f03a820f442f2251553c444370df3b914 > Merge: 80ebed4 76d44e1 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Fri Aug 7 19:35:05 2020 +0000 > > Merge branch 'invite' into 'master' > > Add support for inviting an email address to join a list. > > See merge request mailman/mailmanclient!129 > > or if you did this before Oct 15, maybe it starts with > commit ff39dd8f03a820f442f2251553c444370df3b914 > > The particular commit you need for your issue is > > commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 > Merge: c8dcb1e 28d1c3a > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Sat May 16 08:02:21 2020 +0000 > > Merge branch 'held-count' into 'master' > > Add a new get_held_count() API to get a count of held messages. > > See merge request mailman/mailmanclient!122 > > > > Note that unless you intend to do actual development of Mailman 3, you > should be following > <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather > than <https://docs.mailman3.org/en/latest/devsetup.html>. > > -- > 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, 3 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

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

2 years, 9 months

[MM3-users] Re: Installing Mailman for the first time

by Jim Berg, Jr.

I am not so sure what I am doing. Is there someone who does this for a fee? Jim Berg > On Mar 24, 2023, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/24/23 16:43, comprepair_jimberg--- via Mailman-users wrote: >> I am running Debian 11 Server and wanting to install Mailman 3 >> Will this work for what I am trying to do? >> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > > Yes, but <https://docs.mailman3.org/en/latest/install/virtualenv.html> is our current recommendation. > >> If not is there a shorter list of steps to accomplish what I am trying to do? > > The above may not be shorter. There are a lot of steps no matter how you 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… > > This message sent to comprepair_jimberg(a)icloud.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 10 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > When held mails are released in Mailman (maybe also mails which are not held) they are sometimes not sent nor archived, as mentioned in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > One of my list admins reported that he released two mails on Sep 25 07:20:48 2017 UTC, and only the first was sent to the members. In the mailman.log I found the following from that particular release: > ... I will look at the above as time permits, but ... > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 This one at least is a known issue. See <https://gitlab.com/mailman/mailman/issues/256>. As noted there, the underlying cause is <https://bugs.python.org/issue27321>, a bug in the Python email library (not yet fixed as of Python 3.6.2, but there are references to patches in the bug report). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

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

by Mark Sapiro

On 3/17/20 8:58 AM, Quanah Gibson-Mount wrote: > Now that we are on mailman3, I'm finding things that were really useful > in mailman2 are completely missing in mailman3, which seems odd, since > they in particular affect the ability of list moderators to do their job > well. > > a) When a post was made to a moderated list in mailman2, I would get an > email that included a LINK to the held email. Now I just get a canned > email saying I need to go to the dashboard, blah blah. Why was this > link removed? It was extremely useful and now I have to jump through > extra hoops. The message comes from Mailman core. Mailman core does not know what web management UI you are using or the URI to access it. You need to change the template for the message to include the URL. E.g. on this iist, in var/templates/sitr/en/list\:admin\:action\:post.txt we have 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 to approve or deny the request. > b) When a post is made to a moderated list in mailman2, when I went to > the page to approve/deny/discard, there was additionally an option to > remove the moderated flag from the user for all future emails. This > option no longer exists. This was EXTREMELY useful, as we force all new > members of the list to be moderated for a time while we evaluate the > quality of their postings. Now I have to go manually track down the > user and their settings. Unnecessary extra hoops to jump through 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'. > c) When a post is made to a moderated list, one of the options when > selecting REJECT was it allowed me to set a custom message when > rejecting the email. This was extremely useful. For example today, > someone emailed our bug tracking list directly instead of filing a bug. > In the past, I would have added a note to them about what they should do > (in this case, I would have told them to send their email to our > community technical discussion list). Now I can no longer do that, I > can only reject it or discard it. Why was this removed? This was not "removed". It just hasn't been implemented in MM 3 yet. See, e.g., <https://gitlab.com/mailman/postorius/-/issues/368> and <https://gitlab.com/mailman/postorius/-/issues/368>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: how should I implement multiple domains for receiving emails to a list

by Mark Sapiro

On 4/15/25 16:51, Philip Bondi wrote: > > I have two domains: systemdatabase.ca, systemdatabase.homelinux.com > > All my lists should be on both domains. So h(a)systemdatabase.ca is the same list as h(a)systemdatabase.homelinux.com. I found this was the mailman2 behaviour on my old CentOS 7 installation and I am accustomed to it. While Mailman 2.1 had some support for multiple domains, list names had to be globally unique because a given list name referred to that one list regardless of domain. Mailman 3 is different in that the domain is part of the list name so h(a)systemdatabase.ca and h(a)systemdatabase.homelinux.com are different lists. > I edited /opt/mailman/venv_mm/var/data/postfix_lmtp directly. Duplicated and edited all the lines. And compiled with postmap /opt/mailman/venv_mm/var/data/postfix_lmtp > > I sent a test email. This appears to work. > > Is this the best method to achieve this goal? What would you recommend? If all you want is for mail to h(a)systemdatabase.ca or h(a)systemdatabase.homelinux.com to wind up at the same list, what you've done is OK, but whatever fqdn name your list is created as, it needs the other fqdn name added to it's Acceptable aliases setting, at least if Require Explicit Destination is Yes. The other issue is every time you start Mailman core it will implicitly run `mailman aliases` and overwrite your changes. I have a similar situation on one of the servers I support. The lists are all in a domain I'll call example.com, but we also want to allow mail to <list>@otherexample.com to reach the <list>@example.com list. We use this patch to add all those names. ``` --- a/src/mailman/mta/postfix.py +++ b/src/mailman/mta/postfix.py @@ -261,5 +261,10 @@ class LMTP: '{}@{}'.format(alias, mlist.true_mail_host)) line = VMAPTMPL.format(true_addr, width, addr) print(line, file=fp) + if mlist.true_mail_host == 'example.com': + true_addr = self._decorate( + '{}@{}'.format(alias, 'otherexample.com')) + line = VMAPTMPL.format(true_addr, width, addr) + print(line, file=fp) print(file=fp) return True ``` However, this only works because example.com has an alias domain. If that weren't the case, we would need something like this instead. ``` --- a/src/mailman/mta/aliases.py +++ b/src/mailman/mta/aliases.py @@ -43,9 +43,14 @@ class MailTransportAgentAliases: """See `IMailTransportAgentAliases`.""" # Always return yield mlist.posting_address + if mlist.mail_host == 'example.com': + yield '{}(a)otherexample.com'.format(mlist.list_name) for destination in sorted(SUBDESTINATIONS): yield '{}-{}@{}'.format( mlist.list_name, destination, mlist.mail_host) + if mlist.mail_host == 'example.com': + yield '{}-{}@{}'.format( + mlist.list_name, destination, 'otherexample.com') def destinations(self, mlist): """See `IMailTransportAgentAliases`.""" ``` Do not use both those patches. If your list domain has an alias domain, use only the first one and if not, only the second. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

On 1/6/20 11:16 PM, hansen(a)rc.org wrote: > Mark Sapiro wrote: > >> What's the setting for base_url in mailman-hyperkitty.cfg? > > It's > base_url: https://<OLDHOSTNAME>/archives > > I suppose it should be changed to > base_url: https://<NEWHOSTNAME>/archives That's part of it, but see below. > But: > What if we decided to have more than one domain, as the UI indicates is kosher? Again, see below. >> Are there any errors in var/logs/mailman.log? > > Yep. Lots. They all are of this nature: > > Exception in "hyperkitty" archiver > Traceback: > ... > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 430, in _match_hostname > match_hostname(cert, asserted_hostname) > File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname > % (hostname, dnsnames[0])) > ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHOSTNAME'",) OK. So the real issue is you are trying to access HyperKitty via an https URL and the certificate presented by the web server doesn't allow the domain in the URL. The domain in the URL doesn't really matter as long as it resolves to the HyperKitty host, but if it's an https URL the host's certificate must include that domain. It looks like in your case, the certificate is for 'NEWHOSTNAME', so setting base_url: https://<NEWHOSTNAME>/archives should be enough >> qcluster is not what you need to restart. You need to restart whatever >> is supporting the wsgi interface to Django. This may be uwsgi or >> gunicorn or ??. Whatever it is, that's what needs to be restarted. > > Beats me, Mark. Brian, do you know? Brian has answered: systemctl restart gunicorn >> If you do ps ax|grep runner=, what do you see? If you don't see at >> least three processes with --runner=rest:0:1, stop Mailman and start >> Mailman. > > Yep. I did not get the whole string before. With your options I see three > of these rest:0:1 processes. So I guess the REST stuff is running anyway. OK >> If so, what's >> in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as filename in the file handler in the LOGGING >> definition in settings(_local).py. > >> hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log >> return Site.objects.get_current(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", >> line 60, in get_current >> return self._get_site_by_request(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", >> line 45, in _get_site_by_request >> SITE_CACHE[domain] = self.get(domain__iexact=domain) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", >> line 82, in manager_method >> return getattr(self.get_queryset(), name)(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line >> 408, in get >> self.model._meta.object_name >> django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. > >> This is because of the domain change. In settings(_local).py you have a >> setting for SITE_ID. Possibly, setting that in settings_local.py to a >> value one greater that the current setting will do. > > Trying setting it to 1 (it was 0 before). OK. You can just shotgun trying numbers until one works, or >> To be certain of the >> correct value, you need to look at the django_site table in mailman's >> database. That table has 3 columns, id, domain and name. The id for the >> row of your domain is what needs to be set as SITE_ID. > > You lost me here. No idea how to access the Mailman database. > Brian, do you know? It depends on the database engine. In the database section in your mailman.cfg there is a class: definition which will mention sqlite, mysql or postgresql. The tools for interacting with these are sqlite3, mysql and psql respectively. >> Stop Mailman and then start it. > > No idea here, either. I looked online and found this: > > $ from mailman.commands.cli_control import Stop > But it complained: > from: too many arguments That's a Python statement, not a shell command. You would do systemctl stop mailman systemctl start mailman alternatively, you could do /path/to/bin/mailman stop /path/to/bin/mailman start but that appears to not be the issue. -- 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

Search results for query "sapiro"