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

[MM3-users] Re: Hyperkitty on Debian 12

by Markus Grandpré

short addendum: I was able to correct the following warnings when performing database operations on the mailman-web database: 1) /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. 2) django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. on our Debian 12 system in file </etc/mailman/mailman-web.cfg>: 1) Q_CLUSTER = { 'orm': 'default', 'retry': 360, 'save_limit': 100, 'timeout': 300, 'worker': 2 } 2) DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField' Best Markus Am 26.03.24 um 08:06 schrieb Markus Grandpré: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > > > Am 25.03.24 um 18:56 schrieb Mark Sapiro: >> On 3/25/24 07:58, Markus Grandpre wrote: >>> Dear list members, >>> >>> when following the instructions to migrate list archives from >>> Mailman21 to Mailman3 (see [1]), I face the following problem: >>> >>> # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 >>> /var/mailman21/testlist.mbox >>> python3: can't open file '/var/mailman21/manage.py': [Errno 2] No >>> such file or directory >>> >>> and have no clue, where to find the right <manage.py> file. The command >> >> >> This depends on how you installed Mailman 3. You may or may not want >> `python3 manage.py` at all. The required command could be something >> like `django-admin` or `mailman-web`. >> >> Also the `#` prompt indicates you may be running as root. Mailman >> related commands should be run as the Mailman user (could be `mailman` >> or `list` or ... depending again on how you installed Mailman). >> Running as root can create files owned by root that later can't be >> read by the Mailman user. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 10 months

[MM3-users] Re: postfix malformed address with confirm replies

by Stephen Willey Mats Mats

> On Feb 26, 2021, at 16:08:35 PST, Mark Sapiro <mark(a)msapiro.net> wrote: > > >>> The mail system >>> >>> <matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>: >>> host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address >>> (in reply to RCPT TO command) >>> Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal >>> X-Postfix-Queue-ID: E144B8BC3C5 >>> X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com >>> Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST) >>> >>> Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >>> Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >>> Action: failed >>> Status: 5.1.3 >>> Remote-MTA: dns; 172.19.199.2 >>> Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address > > I have no idea why Postfix is saying > `matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu` > is a malformed address, but this is a Postfix issue, not Mailman. > > Can you successfully post to `matsmats-mm3-test1 > @mm3.aca-aws.s.uw.edu` how about a `help` command to > `matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu` > Yep, all day long. A ‘help’ command succeeded. As did sending the confirm command to the -request address. oh, and looking further at the postfix logs the message was accepted by postfix but the error pops-up when postfix tries to pass it on. Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: connect from mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: E144B8BC3C5: client=mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/cleanup[5966]: E144B8BC3C5: message-id=<9B650420-A50D-4E25-8B5B-C696C388B7DA(a)selby.com> Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: E144B8BC3C5: from=<stephen.s.w.matsmats(a)gmail.com>, size=4575, nrcpt=1 (queue active) Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: disconnect from mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/lmtp[5967]: E144B8BC3C5: to=<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>, relay=172.19.199.2[172.19.199.2]:8024, delay=0.08, delays=0.05/0.01/0/0.01, dsn=5.1.3, status=bounced (host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address (in reply to RCPT TO command)) Feb 26 14:08:54 ip-172-31-18-222 postfix/cleanup[5966]: F0C468BC3C6: message-id=<20210226220854.F0C468BC3C6(a)ip-172-31-18-222.us-west-2.compute.internal> Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: F0C468BC3C6: from=<>, size=6993, nrcpt=1 (queue active) Feb 26 14:08:54 ip-172-31-18-222 postfix/bounce[5968]: E144B8BC3C5: sender non-delivery notification: F0C468BC3C6 Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: E144B8BC3C5: removed The mailman smtp.log show that the message came in but not much else. the mailman.log (and bounce.log) don’t show anything for that time. Feb 26 22:08:54 2021 (27) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Feb 26 22:08:54 2021 (27) Peer: ('172.19.199.1', 51934) Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) handling connection Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'LHLO ip-172-31-18-222.us-west-2.compute.internal' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> SIZE=4575' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) sender: stephen.s.w.matsmats(a)gmail.com Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'RSET' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'QUIT' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) connection lost Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) Connection lost during _handle_client() I’ve also reproduced this another address that is on an exchange server which is maybe a more vanilla example. steve > -- > 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/

4 years, 11 months

[MM3-users] Re: How to see the admin password reset in docker with mailman3

by Jeremy Stanley

On 2023-04-06 14:38:41 -0700 (-0700), Mark Sapiro wrote: [...] > I can't answer that question, but you can set an admin user and > password with the django admin createsuperuser command. And for reference, here's how it's run at setup for the containers: https://github.com/maxking/docker-mailman/blob/b581310/web/docker-entrypoin… python3 manage.py createsuperuser --noinput --username \ "$MAILMAN_ADMIN_USER" --email "$MAILMAN_ADMIN_EMAIL" For a maybe more automate-able example, here's how we call it from outside the container via docker exec on our deployments: https://opendev.org/opendev/system-config/src/commit/ab0e6e1/playbooks/role… docker exec mailman-web bash -c \ "DJANGO_SUPERUSER_PASSWORD={{ mailman3_admin_password }} \ python3 manage.py createsuperuser --no-input --username \ {{ mailman3_admin_user }} --email \ '{{ mailman3_admin_email }}'" The things in {{}} are Jinja2 templated values we supply through Ansible, you could just replace them with whatever values are appropriate for your deployment. -- Jeremy Stanley

2 years, 10 months

[MM3-users] Re: not correct language in subject(s)

by Jens Günther

Am 23.05.23 um 00:54 schrieb Mark Sapiro: > For list welcome and goodbye messages to users, this is > https://gitlab.com/mailman/mailman/-/issues/993, fixed by > https://gitlab.com/mailman/mailman/-/merge_requests/1000 but since that > was fixed in Mailman 3.3.6, this would be a separate issue. I find those changes, but: in the merge request there is mentioned a /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po -> but I don't find a mailman-de.po ... is it maybe that? > Please be more specific than `all types of system mails`. Which specific > message subjects are not translated. It's exactly as mentioned in issue 993 the welcome and goodbye-messages that I don't see translated. But also other examples: - bounce-mail for the user that moderator approval is necessary (there the text is in german, but the reason is in english) - approval-mail for moderator (also text is in german, but subject and reason in english) Thank you for checking!

2 years, 8 months

[MM3-users] Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210526 17:24]: > Mark Sapiro writes: > > > As far as I know, none of this has ever been migrated to Mailman 3. > > It has been migrated to Mailman 3, there were at least two related > GSoC projects, and the repo was on GitHub, but it's not at the same > URL now. Not sure if they've stopped using it, I haven't mentored > there for four or five years. Let me look around. https://github.com/systers/systers.github.io/wiki/Features-for-Mailman-3 seems to be existing but some links broken. https://github.com/khushboo9293/mailman/tree/Feature-CountUnsubscribers is a clone, the original code being moved or removed. However, looking through I don't see so many additions, especially not a membership adapter. I can't find the result of GSoC 2018 which should have worked on the membership adapter. That's so far as I can find. Andi

4 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Clever idea Abhilash! Thanks El mié., 2 ago. 2017 a las 11:50, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > When you set DEBUG=False, Django doesn't serve static files because of > which you see only text and no styles. > > > http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… > > If you do set DEBUG=False, you need to serve the static pages somehow. > > Alternatively in you case, you can remove the part of the `settings.py` > which changes the Emailbackend when `DEBUG=False` so that you don't have > to worry about serving static files and still send out emails. > > On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > > For testing purpose I turned back to false the DEBUG var and everything > > started working fine with HyperKitty > > > > I don't understand... this is the trace when I click Login from Postorius > > to HyperKitty > > > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > > HTTP/1.1" 200 10950 > > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > > HTTP/1.1" 200 156657 > > > > > > What should I check? > > > > > > > > > > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > > HyperKitty is looking for some files in /static/CACHE/... but it > doesn't > > > > find them: > > > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > > > > You need to ensure you have a working sass compiler. As I said at > > > < > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >, > > > See the third bullet under > > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > > > Then you need to run commands like > > > > > > django-admin collectstatic --clear > > > django-admin compress > > > > > > > > > -- > > > 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 > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 6 months

[MM3-users] Re: set a new default for max_message_size

by Abhilash Raj

> On Apr 22, 2022, at 13:09, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 4/22/22 12:28, Paul Paulchen wrote: >> According to the answer of Mark you can change the "/usr/lib/python3/dist-packages/mailman/styles/base.py" - mlist.max_message_size. >> Now time went by, is there a possibility to use the mailman.cfg to set a new default? > > > No. It still is not configurable except by patching or creating a new style, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… It is however possible to create new Styles using Mailman plugins, without having to patch Mailman. We have an example style that demonstrates how to do that: https://gitlab.com/mailman/example-mailman-plugin/-/blob/master/example_mai… The repo’s README has more details on how to create and install the plugin. There is more documentation about plugins in Mailman Core’s docs: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… -- thanks, Abhilash Raj (maxking)

3 years, 9 months

[MM3-users] Re: Postorius not HTML-decoding < to "<" characters

by Ron / BCLUG

Mark Sapiro wrote on 2024-11-09 13:05: > This is a HyperKitty issue. Ah, I see, I thought it'd be on the display process. Does that mean the DB has data with mismatched tags in it? If so, will that require a query to fix? Interestingly, the quoted part of my message has < where my message has proper less-than and greater-than for the Apache tags. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… It's inconsistent with the archive rendering mode at lists.mailman3.org. I haven't currently got an instance that I can test on but will keep this in mind when the time comes to migrate. Should the rendering at lists.mailman3.org get modified, please share the procedure. Testing: less-than and greater-than around a tag: <Location /mailman/accounts/signup> Testing: less-than and greater-than around a tag in a quoted block: > <Location /mailman/accounts/signup>

1 year, 3 months

[MM3-users] Re: Announce Only List

by Stephen J. Turnbull

Mark Sapiro writes: > On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > > So if we want to make a list announce only (e.g. only specific > > folks) can post, I've found I can set the list settings to > > automatically discard messages from members and non-members. Then > > I go into the individual permissions on each user to be allowed > > to post without moderation. This works fine, however it seems > > cumbersome. Don't we have a list style for announce lists? If we don't, we should.... I don't see what's "cumbersome" about the individual permissions. You need to do *something* per allowed user, if only sending email to their individual addresses to tell them the password in the anternate method: > There is an alternative. Set a moderator_password for the list. Then > anyone can successfully post with an `Approved: <password>` header or > pseudo header if they know the password. Steve

5 years, 6 months

[MM3-users] Re: [RESOLVED] REST API authorization failed

by Axel Rau

> Am 10.01.2022 um 19:30 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/10/22 1:58 AM, Axel Rau wrote: >> Is something wrong with my installed python packages? > > > The relevant code is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/wsgiapp.p… > > Does that match yours? I suspected the cryptography package for which I did a fake install, because there is no wheel for my platform and I could not build it. After an odyssey with strange cert errors while building the rust tool chain from their website, I finally managed to install it and could build the wheels for 36.0.1 and created the complete installation in a dedicated jail with ansible. Authentication now works and the website shows 'There are currently no mailing lists.‘ (-: After all these delays, I have only one day left to import 2 lists and to get them up. Thanks for all your help, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

4 years, 1 month

Search results for query "sapiro"