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

[MM3-users] Re: slow restart time for mailmanweb

by William Oliver

On Tue, 2021-12-28 at 13:52 -0800, Mark Sapiro wrote: > On 12/28/21 1:28 PM, William Oliver wrote: > > > > > > > These log entries are from restarting mailman, not mailmanweb Damn. Sorry about that. Brain fart. Yep, it's still slow with mailmanweb: Dec 28 17:41:00 emergenus systemd[1]: Stopping GNU Mailman Web UI... Dec 28 17:41:01 emergenus uwsgi[20860]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Dec 28 17:41:01 emergenus CRON[44474]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) Dec 28 17:41:06 emergenus kernel: [12494.670812] [UFW BLOCK] IN=eth0 Dec 28 17:42:01 emergenus CRON[44755]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) Dec 28 17:42:07 emergenus kernel: [12555.550730] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.112 DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=9540 PROTO=TCP SPT=57024 DPT=25238 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: State 'stop- sigterm' timed out. Killing. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 20860 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44476 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44477 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44478 (sh) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44480 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44483 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44484 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44485 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44486 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44487 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44479 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44481 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Failed with result 'timeout'. Dec 28 17:42:30 emergenus systemd[1]: Stopped GNU Mailman Web UI. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Consumed 2min 27.819s CPU time. >

3 years, 8 months

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

by Andy Smith

On Mon, Jul 11, 2022 at 02:44:59AM +0000, Andy Smith wrote: > Hi Mark, > > On Sat, Jul 09, 2022 at 12:05:32PM -0700, Mark Sapiro wrote: > > 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. > > For now I've configured a copy of all mails to -bounces addresses, > so if/when it happens again I can inspect the actual email that > triggered it. This just happened again. As a refresher, the issue I'm seeing is that Mailman registers a bounce against addresses that aren't subscribed, including addresses for the list itself and for the -leave address that is in some footer text. Here's the bounce.log: Sep 30 17:12:25 2022 (8428) Member [elided1](a)[elided1].force9.co.uk on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email mailto:[elided2]@gmail.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided2](a)gmail.com on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided3](a)[elided3].org.uk on list users.mailman.bitfolk.com, bounce score = 1. I have elided parts of the email addresses of real subscribers. Attached is the actual non-delivery report from the MTA that triggered this. In it I have done my best to elide the names and addresses of real people, but nothing else. They match the same elisions from the bounce log. Any ideas why Mailman is interpreting this NDR so over-zealously? It seems like a pretty standard one. [elided1].force9.co.uk is the subscriber who rejected the mail, yet also users(a)mailman.bitfolk.com, [elided2](a)gmail.com, users-leave(a)mailman.bitfolk.com and [elided3](a)[elided3].org.uk (sender) were punished. Thanks, Andy

2 years, 11 months

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by Jason Glazer

Mark Thanks for the link to the test archive. That and your information has clarified things a lot. Jason On 7/12/2017 11:39 AM, Mark Sapiro wrote: > On 07/12/2017 04:47 AM, Jason Glazer wrote: >> Does anyone know if Hyperkitty can be configured to allow for inline >> images to be maintained so that an HTML file looks like a normal HTML >> message? >> >> Also, can attachments to a message under Hyperkitty preserve their name >> rather than being "scrubbed" into "attachment-*.*" files? > > The answer to some of this is at > <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DC…>. > > One question unanswered by that post is what happens with an inline > image in an HTML message body. In the original message, the image is > referenced by an IMG tag with "src=" pointing to the image MIME part. > Since this structure is not maintained in HyperKitty, inline images > probably don't work. > > Also, with respect to Mailman 2.1, if you want the scrubber to preserve > file names and extensions, set the following in mm_cfg.py > > SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False > SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True > > and if you want scrubbed HTML to not be HTML escaped so it renders > rather than looking like raw html, set > > ARCHIVE_HTML_SANITIZER = 3 > > but note this comment from Defaults.py > >> # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this >> # is very dangerous because it essentially means anybody can send an HTML >> # email to your site containing evil JavaScript or web bugs, or other >> # nasty things, and folks viewing your archives will be susceptible. You >> # should only consider this option if you do heavy moderation of your list >> # postings. > > This is an issue with HyperKitty as it appears this is what HyperKitty > does and there's no way to turn it off. > -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

8 years, 2 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

One more, sorry: Looking in the mailman-users archive, I'm not sure if I understand the bounce settings. Is it the case that if I set the 'Bounce info stale after' to 3d then in 3 days the bounces will be reset to 0 if no further bounces have arrived? I saw a post that made me doubt this. Yours, Allan On 2/1/23, 09:59, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/31/23 22:32, Allan Hansen wrote: > Hi all, > > Apparently Google just started to get very aggressive about DKIM settings. Some hundreds of my subscribers have had their subscriptions disabled because of Google's bounces. > > I tried to 'Enable' some of them, expecting that their bounce scores would be reset, but when I list the users, the bounce scores are still 5. > > Please advise. Will enabling them without the bounce score being reset just cause the server to disable them again. Yes, Google has started enforcing a policy which is effectively DMARC p=reject even for senders whose domains don't publish DMARC p=reject or quarantine. To avoid this issue, you may need to set DMARC Mitigate unconditionally to Yes as well as DMARC mitigation action to Replace From: with list address if it isn't already. As far as enabling without resetting the bounce score is concerned, I think you are correct that they will just be disabled again on the next bounce. This is a bug and should be fixed. However, all of the above can be avoided without any DMARC changes by enabling bounce probes. in the [mta] section of mailman.cfg, set ``` verp_probes: yes ``` Since the probe is sent From: the list's domain, it should pass googles SPF and DKIM checks and not bounce. -- 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: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/56WVO6NIOGOBAOOS2B4YCIDJN7VCIXTF/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 7 months

[MM3-users] Re: Hyperkitty on Debian 12

by Michael Oberrauch

On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: > 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 > > Hi Markus, we are also running MM3 on Debian 12 from Package Repositories. First of all, you should not try to directly switch user (su) to the lists user, it's generally intended to executes commands as that user, if necessary; either using `runuser`, `sudo`, or `su -c`. However, the prepackaged scripts `mailman-wrapper` and `mailman-web` already do this and therefore you ca run those as root without permission problems. On Debian there are two relevant users for MM3: the list user runs mailman core, whereas the www-data user runs Postorius and Hyperkitty. So you have to make shure, that the www-data user can access the .mbox files while importing. Hope that helps. Cheers, Michael -- Michael Oberrauch (er/ihm) Computerreferent Fachschaft Mathematik/Physik/Informatik/Chemie Studentische Vertretung Technische Universität München Boltzmannstraße 3 85748 Garching eMail: oberrauch(a)fs.tum.de Tel: (+49) 089 289 18545 Fax: (+49) 089 289 18546 https://mpic.fs.tum.de

1 year, 5 months

[MM3-users] Re: Timeout error on anonymous subscribe

by vogt＠spamcop.net

Mark Sapiro wrote: > On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > > localhost tcp port. Any local user can do that. > I am trying to duplicate what Mailman does in an attempt to find the issue. > > I can access the template content with > > curl > > http://localhost:8000/mailman3/api/templates/list/community.lists.example.co... > > as well as > > curl > > http://lists.example.org/mailman3/api/templates/list/community.lists.example... > > as any user on the mailman server. > > How about > curl -A 'python-requests/2.32.3' > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as the Mailman user? I have tried anything I could think of but I cannot reproduce the issue using curl as user mailman (or any other for that matter) Going directly for localhost:8000, using some or all of the headers I can capture with tcpdump: ``` $ curl -v -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… ``` as well as going through the local httpd: ``` $ curl -v --http1.1 -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' https://lists.example.org/mailman3/api/templates/list/community.lists.examp… ``` Running tcpdump during those runs shows me it's sending the same headers as mailman does. Thus on http protocol level it's the same, but still the server returns immediately. What I have just noticed is that the Date header in the delayed response is the "late" time. I have even compared tcp headers from either capture. They look identical down to the frame sizes. The only difference the last times is that with curl, the server side sends the ACK for the request and milliseconds later a PSH,ACK with the response headers. When it comes internally from mailman it sends the ACK for the request and then 5 seconds later it sends the PSH,ACK with the response headers. Thanks, Gerald

10 months, 3 weeks

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 5 feb 2024, om 15:45 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 29 jan 2024, om 18:29 heeft Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> het volgende geschreven: >> On 1/29/24 03:09, Marco van Tol wrote: >>> Right now I’m back at the original issue as I see no other solution than to go back to whoosh. >>> Thanks! >>> Marco van Tol >>> Paste: >>> ---- >>> Indexing 194620 emails >>> [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… >> >> >> I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like >> ``` >> SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; >> ``` >> and modify or delete it - it's probably spam anyway. > > I tried the other patch, which looked very promising until something that had come in over SMTP some day threw a spanner in the wheels: > ``` > [ERROR/MainProcess] Failed indexing 287001 - 288000 (retry 5/5): Term too long (> 245): XTEXTº@[åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë= > ;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/'ûvksqé (pid 404): Term too long (> 245): XTEXTº@[ > åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë=;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/' > ûvksqé > ``` > > I agree that this is very likely the result of some spam, but the main point is that something that comes in over SMTP shouldn’t cause manual work on the listserver side. > > I’ll try it with a maximum length of 122 which should never explode into more than 244 bytes, unless I overlook something. This ended up working. :-) Summary: Patch from https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4… But with `TERM_LENGTH_LIMIT = 122` And str() instead of force_str() Thanks so much for all your efforts! Marco van Tol

1 year, 7 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Mark, Thank you for this reminder, but it’s not really sufficient for most. The ‘Mailman Settings’ dialog does, indeed show the other preferences tags, and yes, as you say, the dialog for ‘List-based preferences’ only shows values that are not inherited and when you set a value there, it shows. There a two problems with this: a. Once a value is overridden on the ‘List-based preferences’ dialog, you cannot go back to it being inherited by removing the override. b. You cannot see, on this dialog, what the inherited value is. This is not user-friendly. May I suggest the following: That each option shows the following: o Value 1 o Value 2 (or the equivalent for pull-down menus) A box showing inheritance status: [ ] Use inherited value from address-based preference: Value2 If the ‘Use inherited value’ is chosen, then the inherited value shows. but the value radio buttons become non-selectable. If not, then whatever value the value radio box has become the value for the list, From what I see, the ‘Use inherited value’ is the default for new lists/addresses. To change a value, the user would uncheck this box, making the radio buttons selectable, and then set the desired value. Yours, Allan > On Feb 12, 2021, at 11:52 , Mark Sapiro <mark(a)msapiro.net> wrote: > >> I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? > > > If the user has a Django account, she can see all that info at (e.g. for > this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/ <https://lists.mailman3.org/mailman3/accounts/subscriptions/>> > She gets there from `Mailman settings` in the dropdown under her user > name. She can also get there via the `Manage Subscription` button on the > list's Info page. That takes her to `List-based preferences` for the > list. Any setting not selected there is inherited from the Address-based > preferences or Global Mailman preferences

4 years, 7 months

[MM3-users] Re: Lost posting in archives

by Axel Rau

> Am 22.01.2022 um 02:39 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: > > On 1/21/22 3:06 PM, Axel Rau wrote: >> I created a list, did migration from 2.1 and run update_index_one_list. >> Then I posted a test mail to the list and it got distributed and was seen in the archive. >> Now 2 days later it does no longer show up in the archive. >> What is going on here? >> May this have to do with >> HYPERKITTY_RENDER_INLINE_IMAGE >> which I have turned on meanwhile. > > It may. Is there anything in Django's log about this? Yes: - - - Jan 19 16:46:59 2022 (1997) HyperKitty failure on https://lists.framail.de/hyperkitty/api/mailman/urls: <https://lists.framail.de/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) - - - I have: - - - MAILMAN_ARCHIVER_FROM = ('{{ fqdn }}') - - - Should I put localhost here? > If you have the original message from the list, can you go to the URL in the Archived-At: header? Is empty: - - - Archived-At: <> - - - > is the message in the hyperkitty_email table in the database? E.g., > > SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx'; > > (xxx is the value of the Message-ID-Hash: header from the message) No. > > If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com <mailto:var/archives/prototype/list@example.com>/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. No. How can it be enabled? That’s all I have: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# ls -lR var/archives total 1 drwxrwx--- 3 mailman mailman 3 18 Jan. 18:05 hyperkitty var/archives/hyperkitty: total 25 drwxrwx--- 2 mailman mailman 6 19 Jan. 16:46 spool var/archives/hyperkitty/spool: total 1310 -rw-rw---- 1 mailman mailman 838274 19 Jan. 16:46 1642610819.7180374+05663686ecac2e85272bac93299d8469aa299a6d.pck -rw-rw---- 1 mailman mailman 8888 19 Jan. 16:46 1642610819.7836225+51d3aa9170bfb408821d5d05bd50acb687f23c19.pck -rw-rw---- 1 mailman mailman 13215 19 Jan. 16:46 1642610819.846788+bdfe7825a5a718d081683cf9cfa53cc1f36e64f2.pck -rw-rw---- 1 mailman mailman 469150 19 Jan. 16:46 1642610819.9367082+6c8adeae7d43ec9f721959a57bc1d1415c0b4857.pck - - - Thanks for your time, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 years, 7 months

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

by Abhilash Raj

On Tue, Oct 3, 2017, at 12:28 AM, Henrik Rasmussen wrote: > > Fra: Mark Sapiro [mailto:mark@msapiro.net] > > Sendt: 2. oktober 2017 17:26 > > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > > > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > > > There is no user or list admin workaround, but the defense is a fairly > > simple patch. See the MR at > > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > > at > > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > > The commit changes 7 files, but only two are needed. The rests are tests > > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't > >necessary. > > > > The only changes you need are those to mailman/email/message.py and > > mailman/mta/connection.py. > > I am using Docker-mailman (not yet very familiar Docker and version > control). I would expect I have to wait for a Docker-mailman release > including this change, right? > > I have at least five+ lists which almost haven't been working since my > switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am > desperate trying to figure out whether it is best to fall back to the > Mailman 2 server, for the time being, where the lists came from, or it is > better to wait for an update to the Docker-image. > > Will https://github.com/maxking/docker-mailman/milestone/2 fix my > problems regarding failed mail handling and will it become available soon > (when?) (https://github.com/maxking/docker-mailman/issues/147)? The container images have stable releases of Mailman components, so those changes will make in to the container when a new Core release happens. The next image release is pending a version upgrade of Hyperkitty, to 1.1.3, but other changes are just meant to make the process of setting up Mailman better. They do not include changes from git repo after the release. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

Search results for query "sapiro"