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

[MM3-users] Re: Emergency Moderation

by Allan Hansen

> On May 24, 2020, at 11:34 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/24/20 10:59 AM, Allan Hansen wrote: >> In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. >> I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. > > >> My own current top-of-the-list issues: >> >> A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? I can only speak for my own application of MM3: Desiring consistency between the lists, I don’t want to turn all the moderators into owners who can change list settings. Many of my moderators keep asking me to see the list of members and to subscribe and remove members. I end up servicing those requests. So... a. Moderators should be able to unsubscribe and subscribe members. b. Moderators should be able to set the member’s moderation status. c. Moderators should not be able to see/modify any other member settings. > > >> A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Awesome!!!! Thank you, Allan > > -- > 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, 2 months

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Mark Sapiro

On 9/8/25 13:20, Sam Darwin via Mailman-users wrote: >> I don't understand what you envision such a rendering to do. > > To achieve a level of rendering emails (and web) similar to gitlab or github. That includes bold, italics, code blocks, and possibly more. In both Hyperkitty and email clients. If an incoming message contains HTML and it is not filtered or replaced by content filtering, it will be in the outgoing message and the message sent to HyperKitty. Thus, all you are asking here is that there be an option for HyperKitty to render the HTML (perhaps sanitized) inline as opposed to leaving it as an attachment. I understand that request. > Hyperkitty is one of the two main components. It's the web UI part. The other being the outgoing emails. Actually Mailman core is the main component. Postorius and HyperKitty are really just examples of web based list management and archive rendering applications that communicate with Mailman core via it's REST API. Others have been developed, e.g. EMWD's Affinity and Empathy applications. This is really just and aside, but my point is that Postorius and HyperKitty are not integral parts of Mailman. >> If you're suggesting a text/html part outside of a multipart/alternative part > > I was probably imagining just "multipart/alternative", containing alternatives. Is the "outside" method also a possibility? I did not intend that. I was asking if you envisioned that a text/html part outside of a multipart/alternative part would cause mailman to create a text/plain alternative and package it with the text/html part in a multipart/alternative part. But if that was not your intent, OK. >> For example if in Yahoo mail one composes in "rich text" and drags and drops or copy/pastes or in some ways even types a link, the generated text/plain alternative doesn't contain the url in any form. > > Our lists are set to "Convert html to plaintext". > I just tested from Yahoo email, with rich text, and hyperlinks. Everything was fine. The problem didn't exhibit itself. I also "copied" a link from a website, and pasted it into the email, but it was ok. Perhaps other clients "aol.com, att.net, netscape.net, pacbell.net, prodigy.net, rocketmail.com, sbcglobal.net and ymail.com" have a problem? But today in mail.yahoo.com , no... The issue is not in the plain text converted from the HTML by Mailman's Convert html to plaintext feature. The issue is in the text/plain alternative created by Yahoo when a message is composed as "rich text" and created by Yahoo as multipart/alternative. Were you looking at that text/plain alternative part from Yahoo., i.e. what you see in the outgoing mail if Collapse alternatives is Yes. > If most mail clients include Yahoo and Gmail send both HTML and plain-text versions in a multipart message, there would theoretically be two choices for mm3 with "Convert html to plaintext". > > 1. Mail out the included plain-text copy from the multipart email. Or, > 2. Parse the HTML part of the message and "convert html to plaintext". > which of those is occurring? 1 occurs if content filtering Collapse alternatives is Yes. 2 occurs if Convert html to plain text is yes, but the result depends on Collapse alternatives. If Collapse alternatives is Yes only the original text/plain alternative will be in the outgoing mail. If Collapse alternatives is No, both the original text/plain alternative and a second text/plain alternative consisting of the Mailman converted HTML will be in the outgoing messages multipart/alternative part, and most MUAs will render the converted html alternative. > To summarize again, the goal is to show in Hyperkitty and in email clients a format (based on HTML) that includes bold, italics, bullet items, and code blocks. If you want email clients to display the HTML, either don't filter content or filter content and pass both multipart and text main types and set both Collapse alternatives and Convert html to plaintext to No. This will accomplish what you want minus the possible sanitizing of the HTML for Mailman core and delivered messages. In HyperKitty, the HTML part(s) will still be rendered as attachments. If we receive a merge request to implement inline rendering of HTML, it will be considered but no guarantees. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: Apple Mail encoding again

by David Newman

On 4/14/22 9:50 AM, Mark Sapiro wrote: > On 4/14/22 08:21, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> >> > That combination at least produces multipart/signed messages with >> > multipart/* parts containing a Content-Transfer-Encoding: header. >> > >> > The Python 3 email library considers this to be a >> > InvalidMultipartContentTransferEncodingDefect() message defect. >> >> Merely containing C-T-E is not an error per RFC 2045, although it >> seems to consider it a stupid thing to do. If present, it may be >> "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). >> >> Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening >> that restriction been published since? (I don't know why it would, >> though.) > > > Yes. The C-T-E on all the multipart parts was quoted-printable, not > allowed under RFC 2045. > > >> Even with a non-cleartext C-T-E, it seems reasonable for Mailman to >> treat it as application/octet-stream and pass it through, unless the >> list is configured to do something like strip application/octet-stream >> or that requires decoding like spam-filtering (Postel principle, >> although one could argue it shouldn't be sent on on the same principle >> -- ah, the joys of being an e-mail Mediator). That would be >> especially true it if were quoted-printable, since any relevant MIME >> headers would (presumably) be pure ASCII and therefore unencoded. > > > The Python email library says the message is defective. Mailman's lmtp > runner in turn rejects the defective message with a 501 status > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… > Yes. To be clear, this is an Apple Mail issue. Mailman 3 accepted PGP-signed messages from Apple Mail on versions prior to 15.0 running on MacOS 12.0.1. Something changed on Apple's part. > > It could accept a defective message or one with specific defects, but > this is problematic for further processing. For example, at least one > MUA, Thunderbird, renders such a message with an empty body. That's not my experience. Mailman 3 accepted without complaint a PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to list subscribers with the message body intact. dn

4 years, 4 months

[MM3-users] Re: Mails sent by mailman-web runjobs hourly

by Abhilash Raj

On Fri, Jun 17, 2022, at 2:38 AM, Mark Sapiro wrote: > On 6/16/22 03:44, Eggert Ehmke wrote: >> I get lots of mails originating from the mailman-web runjobs hourly. They are >> sent to mailman@<mytld>. The content looks like >> >> 07:00:03 [Q] INFO Enqueued 12571 >> 07:00:03 [Q] INFO Enqueued 12572 >> 07:00:03 [Q] INFO Enqueued 12573 >> >> How can I disable these emails? > > These message come from Django Q, https://django-q.readthedocs.io/en/latest/ > > I don't think there is a way to disable those specific messages which > occur at times when tasks are queued instead of started immediately. > They are sent to `mailman` because `mailman` owns the crontab and the > crontab has no MAILTO=. You can't stop those specific messages, but you can set up the log level of django-q to WARNING from INFO so that it doesn't send out these logs. You want to add something like this in your settings.py in LOGGING config: https://github.com/Koed00/django-q/blob/15155c7a99ea85a092b1d11da730ba0c4fa… "loggers": { "django_q": { "handlers": ["file"], "level": "WARNING", }, }, Please make sure to *add* "django_q" settings as there might be other existing loggers defined there. Also, I used "file" as the handler for example, so it won't even write to stdout for warning and/or send emails. Make sure that you change that to your liking to include "console" if you want emails for warning logs. > > You can redirect these and all other messages from hourly jobs by > surrounding the hourly jobs command in the crontab with MAILTO= as in > ``` > MAILTO=other(a)example.com > @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > MAILTO=mailman > ``` > or possibly discard them with something like > ``` > @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > /dev/null > ``` > but either of these could redirect or discard other messages from hourly > jobs which you might want. > > -- > 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, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: Issues installing postorius and hyperkitty

by Mark Sapiro

On 10/23/19 6:43 AM, thushantha.lakmal(a)arm.com wrote: > Hi All. > > Im trying to install the mailmain suite with the postorius and hyperkitty . Mailman installation completed successfully but for postorius and hyperkitty Im getting the following errors .. > > Please can someone help me .. > > > > For postorius (Using pip3 install postorius ) > > ERROR: django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have django 2.2.6 which is incompatible. How is Django 2.2.6 installed? If you are only using Django for Mailman (Postorius and HyperKitty), just do pip3 install Django<2.2 > For hyperkitty (Using pip3 install hyperkitty ) All of the below is saying that the install of hyperkitty is trying to install rcssmin, that in turn requires building '_rcssmin' extension which requires gcc. Do you have some other C compiler not named gcc? If so, you might be able to work around this by creating a symlink to your C compiler from /usr/bin/gcc, but it would be better to install gcc using apt, rpm, or whatever your package manager is. > > de41118f448bcb3b8df405c5228e1 > Stored in directory: /root/.cache/pip/wheels/79/50/a5/9410f4b2e62e35c285de46ffa88c2562403cb576e1e7859d68 > Building wheel for rcssmin (setup.py) ... error > ERROR: Command errored out with exit status 1: > command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-491rzr5s --python-tag cp36 > cwd: /tmp/pip-install-563o314q/rcssmin/ > Complete output (12 lines): > running bdist_wheel > running build > running build_py > creating build > creating build/lib.linux-x86_64-3.6 > copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 > running build_ext > building '_rcssmin' extension > creating build/temp.linux-x86_64-3.6 > gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o > unable to execute 'gcc': No such file or directory > error: command 'gcc' failed with exit status 1 > ---------------------------------------- > ERROR: Failed building wheel for rcssmin > Running setup.py clean for rcssmin > Successfully built robot-detection django-haystack > Failed to build rcssmin > Installing collected packages: rjsmin, django-appconf, rcssmin, django-compressor, robot-detection, django-haystack, djangorestframework, decorator, networkx, django-extensions, wcwidth, blessed, arrow, django-picklefield, django-q, hyperkitty > Running setup.py install for rcssmin ... error > ERROR: Command errored out with exit status 1: > command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile > cwd: /tmp/pip-install-563o314q/rcssmin/ > Complete output (12 lines): > running install > running build > running build_py > creating build > creating build/lib.linux-x86_64-3.6 > copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 > running build_ext > building '_rcssmin' extension > creating build/temp.linux-x86_64-3.6 > gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o > unable to execute 'gcc': No such file or directory > error: command 'gcc' failed with exit status 1 > ---------------------------------------- > ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile Check the logs for full command output. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

Yeah I'll set up some advanced debugging in Postfix on the relays to see whats' coming in and out. Will take time though 'cause we have a TON of messaging going through that smtpproxy out to the 'net so it'll take a bit for me to dissect the message logs. Give me a bit since it's EOD for me now. Thomas On 12/6/23 15:44, Mark Sapiro wrote: > On 12/6/23 11:11, Thomas Ward via Mailman-users wrote: >> See, that's the oddness. There appears to be SOME weird mail loop >> here where $ORIGIN (MS365/Exchange) hands it once, then there's >> back-and-forth between SMTPPROXY and Mailman. IT's really odd how it >> behaves, and I have no explanation for it. >> >> Right now I'm away from the office where this happens, but when I'm >> back there I'll grab logs from both sides. >> >> >> Thomas >> >> On 12/5/23 17:54, Mark Sapiro wrote: >>> On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >>>> We use a multi-hop SMTP system to go from the inside of our network >>>> out to the Internet at the domain test.lists.example.com. >>>> >>>> The setup is this way for ingress: >>>> >>>> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >>>> Connector) -> Mailman for delivery to listserv > > > Presumably the EXTERNAL to MS365 SMTP transaction includes > > MAIL FROM: <user(a)example.com> > RCPT TO: <invalid(a)test.lists.example.com> > > It seems that somewhere in the path to Mailman this is getting changed to > > MAIL FROM: <invalid(a)test.lists.example.com> > > so the outbound DSN is sent to invalid(a)test.lists.example.com instead > of user(a)example.com. The question is which one of the MTAs in the path > is doing this and why. > > But even more mysterious is the fact that the DSN from Mailman should > be sent with > > MAIL FROM: <> > > so when it's undeliverable, no further DSN is sent. >

2 years, 8 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 23:53, Mark Sapiro wrote: > On 2/13/21 11:52 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 13/2/21 20:00, Mark Sapiro wrote: >>> If there are issues in this mailman.po, they exist in weblate too and >>> need to be fixed there. >> That clarifies all. Thanks. As I said in my previous message, I'll wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. > Well.. It surely is in the case of mailman core, but not in postorius, hyperkitty and django_mailman3. And these are what are serving the translated terms what the users see. I did some exploration this morning (Spain time) in the weblate statistics and archives and I found that the changes done from Victoriano and me were recorded. I did a screencopy of all that if someone has any doubt about it. I downloaded this files: -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po The thing is that they differ from the .po installed via pip upgrade. Mostly, as said, postorius, hyperkitty and django_mailman3. I saved a backup copy of the "django.po" that lies in the packages path for the es language. In my case /usr/local/lib/python3.7/site-packages/[package]/locale/es/LC_MESSAGES and replaced by the downladed file, changing the name (as all of them was named django.po in destination). Then I did, as you pointed in a message and Victoriano found the right way in our systems, a django-admin compilemessages for each package. And now I have all the postiorius web interface correctly translated (at least almost all of it). Now I can make a tutorial for my moderators and users without them complaining about the mixing language terms. I have also a screencopy of before-after If someone wants to see the changes. Thanks all for your support.

5 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello guys, This is what I've got on ../var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 76 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db What should I do in order to let mailman install the DB files? Thanks El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 08:16 AM, Rafael Mora wrote: > > This is the content of my /var/log: > > > > > > [root@localhost log]# pwd > > /var/log > > [root@localhost log]# ls > > anaconda grubby messages-20170716 spooler-20170710 > > audit grubby_prune_debug messages-20170723 spooler-20170716 > > boot.log httpd mysqld.log spooler-20170723 > > btmp lastlog php-fpm tallylog > > btmp-20170701 letsencrypt ppp tuned > > chrony maillog rhsm wtmp > > cron maillog-20170702 samba xferlog > > cron-20170702 maillog-20170710 secure xferlog-20170702 > > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > > cron-20170723 mailman secure-20170716 xferlog-20170723 > > dmesg messages secure-20170723 yum.log > > dmesg.old messages-20170702 spooler > > firewalld messages-20170710 spooler-20170702 > > > Your current postfix log is /var/log/maillog. The files like > /var/log/maillog-20170702, etc are older versions rotated by logrotate. > > On 07/23/2017 08:14 AM, Rafael Mora wrote: > > content of the file maillog-20170723 (I didn't find mail.log in > /var/log): > > > > [root@localhost log]# cat maillog-20170723 > > You want to be looking at /var/log/maillog for current messages. > > > ... > > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory > > > Is this where these files are? You should have at least postfix_domains, > postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the > /var/lib/mailman/var/data/ directory. It this the case? > > > output command 'postconf -n': > > > ... > > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp > > > This is missing a / > > > transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp > > > -- > 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

9 years

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (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 > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (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 > SocialAccountConfig.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. This is from Django >=3.2 can be fixed by adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to your settings. This has been done in HyperKitty's example_project/settings.py for the not yet released 1.3.6 version. These warnings are only warnings, they aren't fatal. ... > Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows > the same warning listed before and some new errors: > > *-*-*-*-*-*-* > > Migrations for 'postorius': > /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py > > - Alter field name on emailtemplate > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 419, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 413, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 354, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 398, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 89, in wrapped > res = handle_func(*args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 190, in handle > self.write_migration_files(changes) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 228, in write_migration_files > with open(writer.path, "w", encoding='utf-8') as fh: > PermissionError: [Errno 13] Permission denied: > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > > > *-*-*-*-*-*-* > > The file > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > does not exist at all makemigrations is trying to create that migration and you don't have permission to create the file. I don't know why it's trying to do that. Postorius 1.3.6 has migrations through 0016_auto_20210810_2157.py and shouldn't need more. To you have modificationd to Postorius? > Despite the error, I did a 'su -m mailman3 -c "python3 manage.py > compress"' and the subsequent "django-admin compilemessages" in > > /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and > ../django_mailman3 > > And the log continues showing the same error when trying archive a new > message. > > ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. These messages come from some HyperKitty version between commit b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 -0700 and commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 2021 +0000 They do not come from HyperKitty 1.3.5 but from something later than 1.3.4 which makes be think your mailman-hyperkitty version is not 1.2.0 either. I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: logrotate

by Christian

Thank you! Would I run your script weekly in cron or ? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, May 2, 2023 4:37 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: logrotate Please don't hijack threads. Post a new topic as an original post, not as a reply to an old thread. On 5/2/23 15:45, Christian via Mailman-users wrote: > I noticed that my mailman logfiles are not being rotated. I followed > the instructions in > https://mail.python.org/archives/list/mailman-developers@python.org/me > ssage/ > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Those instructions are for Mailman 2.1. > Now when I try and run logrotate I get the following error > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file > or directory > error: stat of /opt/mailman/mm/error.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file > or directory > error: stat of /opt/mailman/mm/smtp.log failed: No such file or > directory > root@zarathustra: > > What am I doing wrong please? Here's a logrotate script I use: ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` A couple of caveats. The first line of the postrotate script may be wrapped. `sudo ... true` is all one line. That line could also be ``` /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true ``` I.e., it either has to run as the mailman user or specify the --run-as-root option. Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't in /opt/mailman/mm/var/ those paths need adjusting. Finally, there may be an issue with `mailman reopen` in the postrotate scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 -- 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/ JTUKYJDD5Y5JIAVK3OOFNVCK4CVDGK6O/ This message sent to csa(a)web-analysts.net

3 years, 3 months

Search results for query "sapiro"