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

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > Mark Sapiro writes: > > > > Some of the `path` settings are probably not in the same order as > > > in that file. The > > > > > > ``` > > > path('mailman3/', include('postorius.urls')), > > > path('archives/', include('hyperkitty.urls')), > > > ``` > > > settings should come after the > > > ``` > > > path('postorius/', include('postorius.urls')), > > > path('hyperkitty/', include('hyperkitty.urls')), > > > ``` > > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > > ones or you can add > > > ``` > > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > > ``` > > > to your Apache config. > > > The odd thing is that the HOWTO that he followed never involves the > > manipulation of any urls.py at all - it's not even mentioned at any > > point. So obviously the issue is caused by something else and I > > suspect something within Apache needs to be re-evaluated in the > > guide. > > I believe this is the Apache configuration the OP is using: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > > Note that Apache doesn't know about the "/postorius" and "/hyperkitty" > URI paths. It is quite unclear to me how this works at all with > either the > > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > > version of urls.py or the reverse order version > > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > > I think Mark must have a configuration with > > ProxyPass "/" "http://127.0.0.1:8000/" > > in the Apache configuration in mind? Or an alias or rewrite rule. > Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever > get transmitted to the WSGI server. > My thinking then is that the documentation at https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration needs to be fixed by adding the missing bits, or a urls.py be provided for inclusion in /etc/mailman3/ and which sysadmins can edit to their liking. For example, I'd prefer to have /mm3 instead of /mailman3 to save on transmitted bytes and not clog the Internet pipes :-) -- 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]

2 years, 2 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Thank you for the clarification! Am 19.03.21 um 18:48 schrieb Abhilash Raj: > > >> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: >> >> Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > You seem to have landed on a very old version of the docs that I didn’t unfortunately knew > was even available. I have disabled that page now. > > The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > >> >> I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> How could I check, that the setting is used!? >> >> But maybe some additional information: >> - I use the Debian installation on a stable buster, so mailman is version 3.2.1 >> - I use apache2 as my web-server and use the given alias-conf-file >> - Python is version 3.7.3 >> - Postorius is Version 1.2.4 >> - HyperKitty is version 1.2.2 >> >> -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de >> -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above >> -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de >> -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de >> -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains >> >> What do I miss? Or where to investigate? >> >> Thank you in advance, best regards. >> >> By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html > > Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and > Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to > individual projects. The second one is the individual Mailman Core project. Historically, Core was the > only project and hence claims the name “mailman” in most places. > >> >> Am 18.03.21 um 21:52 schrieb Mark Sapiro: >>> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >>> Set FILTER_VHOST = True in your settings_local.py or where ever you put >>> your site Django settings. >> _______________________________________________ >> 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/ >

5 years, 2 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Thomas Ward

On 10/18/23 20:25, Mark Sapiro wrote: > On 10/18/23 15:06, Thomas Ward via Mailman-users wrote: >> Is there a way to oerhaps custom-plugin my way through to set this up >> as an integration into Core? And specify the custom handler process >> or such to allow that integration? I see that there are ways to code >> plugins into existence so it may be a custom-processor plugin or such >> for this purpose. > > > The issue is Mailman core would have to keep track of the message-ids > and thread number of all prior posts to know whether the current post > is a reply to some other post or not. > > You would need a new database table or some other mechanism to keep > track of this and then you may need to keep everything forever because > you can't know that there won't be a future post in reply to some very > old post. > I think this is doable in our (read: Employer) use case, but without needing to modify Mailman Core much beyond a custom plugin and some fussing around. This is a side effect of a custom implementation of "Tagging" data by thread ID in a separate data / intel tagging system that reads from received emails in a custom intel processing mailbox. That has zero care as to how Mailman or Hyperkitty index items, and actually is pretty trivially implemented with `PREFIX` format being [ListName-NNNNNNN]: 1. If subject does not match `PREFIX` format: * Get next thread number from DB (In postgres, this is a serial matched to {list_id}_thread we call with nextval()) * Add subject prefix as [ListName-{ZeroPaddedThreadNumFromDB}] 2. If subject matches `PREFIX` form: * Do nothing As for how HyperKitty handles this, it replies entirely on RFC 5322 fields (see section 3.6.4 in that RFC) for identifying reply to, etc. to identify replies to things, which in turn it seems is fully capable of handling that. We simply need the message to be sent *with* a thread ID that members can hit reply to and keep the prefix in the subject line. We don't care how that's done in the Hyperkitty side of things, we only care about it being sent in the subject line. I noticed that Mailman3 has the capacity for external / custom plugins, and with some work I believe I can achieve this with a customized pipeline with a custom handler of `thread-prefix` instead of `subject-prefix`, otherwise calling the other handlers done by the traditional system, and just handle prefix differently in the thread-prefix handler in the custom pipeline. I'm following this attempt currently, but will keep it internal to employer. It'll also be kept internal to our use-case because it isn't easily exportable to other Mailman3 implementations. But yes, you're right it needs additional DB table to map list_id <--> thread_id and then would need some kind of "Subject prefix uses thread IDs instead of Post IDs config option", or only handle based on a custom pipeline. I"m going to deep dive into this on my end and see if I can come up with a solution that relies direct on the DB calls. Which hopefully should be safe to do, but we'll see in testing. Thomas

2 years, 7 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Guillermo Hernandez (Oldno7)

El 3/4/23 a las 1:25, Mark Sapiro escribió: > On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I'm NOT blaming any of the parts involved... Sure, most probably is >> my fault. But the last upgrade shows that the process that fail is >> involved with mailman upgrade. The last server was working smoothly >> and it has higher traffic than the first I tried. It cannot be that I >> missed that something was not working for weeks (since the last >> upgrade of the OS) > > It depends on what you did. Mailman's lmtp runner would only encounter > this issue at startup, so unless you restarted Mailman or rebooted the > server, lmtp runner would have continued without issue even if there > was an underlying OS problem. I thought I said it: I reboot this server everyday at 06:40 CEST time. That's why I'm sure it's not an undetected problem for weeks. The lists in this last upgraded server are with daily traffic. I'm suscribed to all. > > Also, I don't think the problem is with Mailman per se. The underlying > issue is in the Python library socket module. Try the following in a > Python 3 shell > ``` > $ python3 > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock > >>> sock = makesock(AF_INET6, SOCK_STREAM) > >>> sock.bind(("::1", 0)) > >>> sock.close() > ``` > This is essentially what aiosmtpd does and I expect that `sock = > makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] > Protocol not supported` exception. > And you are right (ther is more down of this): Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported Buuuuuut, if I do the same in the "father" server: Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() File "<stdin>", line 1 sock.close() IndentationError: unexpected indent >>> sock.close() >>> The server can open a socket without problem. As I though previously it has to be something with the jailed envviroment. Your test had probe me right (and wrong in my jail tests). It's very valuable. I know now where I can dig more. Thanks a lot -- ___________________________________________ 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.

3 years, 1 month

[MM3-users] compress failed (was Re: Solved Re: after last upgrade I've got a CSRF failed verification)

by Guillermo Hernandez (Oldno7)

El 28/10/22 a las 9:18, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 27/10/22 a las 21:39, Mark Sapiro escribió: >>> After that the compress part showed errors... but the postorius web >>> maintenance was working well except for the CSRF error verification. >>> I will trace the compress errors and will try to find the problem >>> later. >> >> >> Do you have `COMPRESS_ENABLED = True` in your settings? If that's not >> the issue, it may be in the settings for COMPRESS_PRECOMPILERS > > While I'm tracing the problem out, this is the configuration I had > working and the error it shows after upgrade: > > <------- snip of settings.py> > > # > COMPRESS_PRECOMPILERS = ( > ('text/less', 'lessc {infile} {outfile}'), > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > # On a production setup, setting COMPRESS_OFFLINE to True will bring a > # significant performance improvement, as CSS files will not need to be > # recompiled on each requests. It means running an additional "compress" > # management command after each code upgrade. > # > http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression > #### activo compresion 18/12/20 > COMPRESS_OFFLINE = True > ###COMPRESS_OFFLINE = False > <---------- end snip> > > And below is the error it shows: > > /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" > Traceback (most recent call last): > File "/usr/local/mailman3/manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 49, in load_command_class > return module.Command() > File > "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", > line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > After searching around, I've got a hint of what can be happening. It seems a variable has changed in Django 4.1 its nature from boolean to a tuple https://github.com/painless-software/django-probes/issues/24 I've upgraded another server with mailman3 lists, with the same config listed above, and it shows the same error in the "compress" part. I'm not sure where to set the requires_system_checks variable as in one of the comments of the link, and as it doesn't seems to break anything more, I will wait for more info before trying to avoid it. I'm sure it will have some repercusion on the performance, but I'll have to live with it. Thanks again for your supporting advices. > > > > > -- ___________________________________________ 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.

3 years, 6 months

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

by Ruth Ivimey-Cook

Thanks Mark, On 20/06/2020 03:53, Mark Sapiro wrote: On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. What are your Django settings for MAILMAN_REST_API_URL, MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with the [webservice] settings for hostname, port, use_https, admin_user and admin_pass in mailman.cfg in core and is the port open to the outside on the core machine? greyarea-post is the mailman-core and exim server. greyarea-web1 is the postorius and hyperkitty server. On greyarea-web1, in django-settings.py, MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = XXXX and both the above-named hosts are also included in ALLOWED_HOSTS along with localhost. On greyarea-post, in mailman.cfg: [webservice] admin_pass: XXXXX admin_user: restadmin api_version: 3.1 hostname: 0.0.0.0 port: 8870 use_https: no The password and username are as on web1. Do you see REST requests from the Postorius machine in core's mailman.log and access.log? Yes, there are lots of requests of the form: [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" I made a new list using the core CLI, and as a result of navigating directly to the list archive page I get to see: [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" ... but in neither case do I get a complete screen on the browser or 'follow-up' requests. I don't have a file access.log on the greyarea-post. On the greyarea-web1 I have mailmansuite.log with the last few lines: File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba se.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co nnection.py", line 124, in call 'Could not connect to Mailman API: ', repr(e)) mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection object at 0x7f5416db8518>: Failed to establish a new connection: [Errno 111] Connection refused\',))",),)') ERROR 2020-06-03 01:02:06,115 29002 django.request Service Unavailable: /postorius/lists/ the uwsgi-error_*.log contains many lines of the form: api: url is [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= 1 api: url is [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= 1 My reason for thinking, in my original post, that the wrong host address is being used is that the ConnectionError above contains 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as the listen address on the core web service and does not appear in the config for postorius. I hope this helps, Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: [4]http://www.ivimey.org/blog LinkedIn: [5]http://uk.linkedin.com/in/ruthivimeycook/ References 1. http://greyarea-post:8870/ 2. http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 3. http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 4. http://www.ivimey.org/blog 5. http://uk.linkedin.com/in/ruthivimeycook/

5 years, 11 months

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

by Allan Hansen

Thank you, Mark. That makes sense. And, as you suggested, this will not work for me, because a lot of people log in and then apply to more lists. I can't exhort them to get the accounts set up and do their subscription maintenance while logged in, and they tell them that if they want to sign up for another list they have to log out first. __ I do need to find another way. I suggested these options: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Of course, (a.) and (b.) are preferred in the short term, as I'd like to get our procedure simplified. Any idea which file to change for either, and some suggestion as to what to change? Yours, Allan On 3/28/23, 10:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: 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 <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/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/D4WXXVOHXTDLRDGXV66GV4BAMWBRYEPF/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

3 years, 2 months

[MM3-users] mailman.cfg (use_https: yes) fails

by Wolfgang Bock

Hello, I configuered 3 domains in postorius https://[mydomain]/mailman3/postorius/domains/ ... also shown here: https://[mydomain]/mailman3/admin/sites/site/ (django) I installed mailman3 with debian command apt-get install mailman3-full. The package mailman3-full is described as follows: Paket: mailman3-full (3.2.1-1) (for debian-buster, W.B.) ... Betreuer: * Debian Mailman Team <mailto:pkg-mailman-hackers@lists.alioth.debian.org> (QS-Seite <https://qa.debian.org/developer.php?login=pkg-mailman-hackers%40lists.aliot…>, E-Mail-Archiv <https://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/>) * Pierre-Elliott Bécue <mailto:peb@debian.org> (QS-Seite <https://qa.debian.org/developer.php?login=peb%40debian.org>) * Jonas Meurer <mailto:jonas@freesources.org> (QS-Seite <https://qa.debian.org/developer.php?login=jonas%40freesources.org>) Full Mailman3 mailing list management suite (metapackage) This is GNU Mailman, a mailing list management system. This metapackage depends on all components of the full Mailman3 suite: * mailman3: The core Mailman3 delivery engine * mailman3-web: Django project integrating Mailman3 postorius and hyperkitty * python3-mailman-hyperkitty: Mailman3 server plugin for Hyperkitty archiver ..... That's the output of # mailman info GNU Mailman 3.2.1 (La Villa Strangiato) Python 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://[-secret-][mydomain]/mailman3?charset=utf8&use_unicode=1 devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:[-secret-] I dont know what version of mailman client is included in the package. Should I wait until an update includes a higher Version of the mailman-client? In this context I faced a strange behavior: In the database mailman3web in table django_site are listed several domains, either in the django-domain-management site https://[mydomain]/mailman3/admin/sites/site/ id domain name 1 example.com Example.com 2 [mydomain-1] [mydomain_name_1] 3 [mydomain-2] [mydomain_name_2] 4 [mydomain-3] [mydomain_name_3] In case I delete line 1 with the id 1, in the database or in the django-web-site, postorius fails to work. After re-inserting this line, postorius works again. Regards Wolfgang Am 16.11.2019 um 01:02 schrieb 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. >

6 years, 6 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Thor Atle Rustad

There is a way around it! I have had two issues with the the maxking docker image. One is that the regexp is not working properly. I reported that, and it has been fixed in newer code. My other problem is that the docker image creates a user, mailman, that receives uid 103. Well, uid 103 on my system is already taken by systemd-bus-proxy (grep 103 /etc/passwd returns "systemd-bus-proxy:x:103:105:systemd Bus Proxy,,,:/run/systemd:/bin/false"). My solution includes downloading the corrected postfix.py, and replacing the Dockerfile. I put the postfix.py in <docker-mailman>/core/assets/. My Dockerfile: FROM maxking/mailman-core RUN grep mailman /etc/passwd && grep mailman /etc/group \ && deluser mailman \ && addgroup -S -g900 mailman \ && adduser -S -u900 mailman mailman \ && grep mailman /etc/passwd && grep mailman /etc/group COPY assets/postfix.py /usr/local/lib/python3.6/site-packages/mailman/mta/postfix.py I then run docker build (with -t parameter, you must look up that yourself). I use a different name for my images, so I end up with (note, there are two tags per image): root@mailer:/home/mailman/docker/docker-mailman_mods/core# docker images REPOSITORY TAG IMAGE ID CREATED SIZE local/mailman_core_900 20171110_2 9649e84767e1 2 days ago 176MB local/mailman_core_900 latest 9649e84767e1 2 days ago 176MB local/mailman_web_900 20171110_2 07a9b3d7ddd6 2 days ago 247MB local/mailman_web_900 latest 07a9b3d7ddd6 2 days ago 247MB I do the same with the web image, as I need to change the user there, too. Then, in docker-compose.yaml, I change the line(s) referring to the image name(s): services: mailman-core: image: local/mailman_core_900 container_name: mailman-core hostname: mailman-core mailman-web: image: local/mailman_web_900 container_name: mailman-web hostname: mailman-web I don't know if this is a good solution, but at least it fixes some serious issues with the 3.1's postfix integration that wouldn't otherwise be fixed until the 3.2 release. The bottom line is that it works for me, but it adds an additional layer of complication. 2017-11-03 19:40 GMT+01:00 Abhilash Raj <maxking(a)asynchronous.in>: > On Fri, Nov 3, 2017, at 08:29 AM, Fabian A. Santiago wrote: > > October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > > > > > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" < > fsantiago(a)garbage-juice.com> wrote: > > > > > >> That was it. Perfect. I manually modified my regexp map and it works > > >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh > > >> those maps or only as I add new domains / lists? > > > > > > Only when you make changes to domains or lists. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> > > > Sent from my Not_an_iThing with standards compliant, open source > software. > > > > Mark, > > > > I've noticed that even simply restarting the mm3 components those alias > > maps get rewritten and the problem returns until I can manually edit it. > > Yeah, that is true. Transport maps are re-generated everytime the > container restarts. > > I don't think think there is any way around this right now :( > > > -- > Abhilash Raj > maxking(a)asynchronous.in > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 6 months

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

by Odhiambo Washington

On Sun, Jul 28, 2024 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/28/24 09:54, Roland Giesler via Mailman-users wrote: > > > > These settings from the Django docs look like the ones in mailman.cfg. > > Do I have to set them somewhere else too? > > > Yes. The settings in mailman.cfg only affect mail from Mailman. For mail > from Django, you have to set things like > > EMAIL_HOST = 'box2.gtahardware.co.za' > EMAIL_PORT = 465 > EMAIL_HOST_USER = 'roland(a)giesler.za.net' > EMAIL_HOST_PASSWORD = '...' > > and possibly others as desired, See the links to the Django docs for these. > > > > * |use_tls|:|EMAIL_USE_TLS| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T… > > > > * |use_ssl|:|EMAIL_USE_SSL| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S… > > > > * |timeout|:|EMAIL_TIMEOUT| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO… > > > > * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K… > > > > * |ssl_certfile|:|EMAIL_SSL_CERTFILE| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C… > > > > This all goes in your Django settings which from other posts I gather is > /etc/mailman3/mailman3-web.py. I'm guessing you are using the Debian > packages and that's where the package puts the Django settings. > I am following this thread out of curiosity. So I added the same lines to my /opt/mailman3/settings.py - on a virtualenv install of the latest MM3 code.It's my test VM. After adding the lines and restarting mailmanweb, I then entered the virtualenv and did 'mailman-web createsuperuser' which completed successfully, but NO MAIL! As matter of fact, there isn't even anything in the logs of the MTA running at w.kictanet.or.ke. ``` root@ubuntu24:/home/wash# su mailman (venv) mailman@ubuntu24:~$ tail -n 5 /etc/mailman3/settings.py EMAIL_HOST = 'gw.kictanet.or.ke' EMAIL_PORT = 587 EMAIL_HOST_USER = 'mailman(a)gw.kictanet.or.ke' EMAIL_HOST_PASSWORD = 'XXXXXXYYYYYYYZZZZ' (venv) mailman@ubuntu24:~$ mailman-web createsuperuser Username (leave blank to use 'mailman'): mm3admin1 Email address: odhiambo(a)outlook.com Password: Password (again): Superuser created successfully. (venv) mailman@ubuntu24:~$ tail -n 5 /opt/mailman/web/logs/mailmanweb.log [Nothing in that file] (venv) mailman@ubuntu24:~$ tail -n 10 /opt/mailman/mm/var/logs/mailman.log [2024-07-29 13:41:22 +0300] [301491] [INFO] Starting gunicorn 22.0.0 [2024-07-29 13:41:22 +0300] [301491] [INFO] Listening at: http://127.0.0.1:8001 (301491) [2024-07-29 13:41:22 +0300] [301491] [INFO] Using worker: sync [2024-07-29 13:41:22 +0300] [301537] [INFO] Booting worker with pid: 301537 [2024-07-29 13:41:22 +0300] [301538] [INFO] Booting worker with pid: 301538 Jul 29 13:41:23 2024 (301485) bounces runner started. [29/Jul/2024:13:45:52 +0300] "GET /3.1/domains HTTP/1.1" 200 333 "-" "GNU Mailman REST client v3.3.5" [29/Jul/2024:13:45:52 +0300] "GET /3.1/domains/lists.wash.lan HTTP/1.1" 200 228 "-" "GNU Mailman REST client v3.3.5" [29/Jul/2024:13:45:52 +0300] "GET /3.1/users/odhiambo(a)gmail.com HTTP/1.1" 200 395 "-" "GNU Mailman REST client v3.3.5" [29/Jul/2024:13:45:52 +0300] "POST /3.1/lists/find HTTP/1.1" 200 503 "-" "GNU Mailman REST client v3.3.5" -- 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, 9 months

Search results for query "sapiro"