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

[MM3-users] Re: Incorrect error log message in OutgoingRunner._dispose()

by Mark Sapiro

On 4/26/26 10:42 AM, Craig Leres wrote: > On 4/26/26 06:52, Mark Sapiro wrote: >> >> Did you by chance run import21 as root or another non-mailman user >> resulting in template files unreadable by Mailman? > > Yes and no. I ran it as a user in group mailman; the template files are > owned by the user but are group mailman read/write... Then those templates in Mailman's var/templates/LIST-ID/LC/ should be used for the list for that language as long as they are readable and not overridden by a Postorius template or other URI for the list in the template table in the database. Was there anything in mailman.log prior to your defining a Postorius template indicating why they weren't used? >>> Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server >>> 127.0.0.1 on port 25 >> >> This is a well known issue. See <https://gitlab.com/mailman/mailman/-/ >> work_items/582> and related issues referenced therein. > ... > What really bothers me about the error message is that it's reporting a > SMTP connection failure when what really happened was a HTTP connection > failure. That is all part of the above referenced issues. It is a bug and should be fixed but hasn't been yet. It is caused by the low level socket error upon trying to fetch the template, ultimately being caught by the try/except in outgoing runner's sending of the message. >>> I'm using the default webservice port (8001) so I would not expect >>> anything to ever be listening on 8000. >> >> The default web service port (Postorius and HyperKitty) is 8000. Port >> 8001 is Mailman core's rest api. > > Ah. I never noticed anything telling me the apache config needed to also > listen on 8000. It's also confusing to me to call the rest api port the > "web service port" (Also, I'm not running hyperkitty.) Apache doesn't listen on port 8000. The WSGI server (uWsgi or Gunicorn or ...) listens on port 8000 and Apache listens on ports 80 and 443 as normal and proxies the mailman requests to port 8000. > Ok, I added apache config to handle 127:0.0.1:8000 and that solves the > "SMTP" (HTTP) connection error and cpu bound runner. I don't know what you did, but see <https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…> for how Apache should proxy to port 8000. > I still can't get templates to work but I'll debug further and ask for > help later if I still can't get it to work. Do you have a WSGI server running and listening on port 8000? See <https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws…>. You need this for Postorius as Postorius is a Django project and Django is a WSGI application. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

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

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: Link to account

by Mark Sapiro

On 4/11/23 12:04, Lars Bjørndal wrote: > Thanks a lot. Maybe I've done a mistake, it doesn.t work. > > At the bottom of /etc/mailman3/settings.py I have: > > ROOT_URLCONF = 'urls' > > `cat /etc/mailman3/urls.py` > > [...] > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('lists/mailman3/', include('postorius.urls')), > path('lists/archives/', include('hyperkitty.urls')), > path('lists/', include('django_mailman3.urls')), > path('lists/accounts/', include('allauth.urls')), > path('lists/admin/', admin.site.urls), > ] > > In Apache config for the domain, I now have: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" > ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives" > ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts" > ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin" > ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile" > </IfModule> > > Restarted mailmanweb, httpd and mailman3. > > If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser. > > So what's wrong, do you think? You followed https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… literally. The literal instructions where to access everything via URLs like https://mydomain.org/lists/.... If you were to replace `lists` with `mailman3` everywhere in the abpve, you would then access HyperKitty via a URL like https://list.punktskriftutvalget.no/mailman3/archives/ and Postorius via https://list.punktskriftutvalget.no/mailman3/mailman3/ If that's not what you want, it's more complicated and some things might not be possible. What exactly do you want for access to Postorius, HyperKitty, user accounts, user profiles and the Django admin UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: log rotation for bounce.log

by Mark Sapiro

On 1/22/24 14:50, Quanah Gibson-Mount wrote: > I noticed that our smtp.log and bounce.log files haven't been rotated in > years. I see the reason for smtp.log not being rotated is due to > <https://gitlab.com/mailman/mailman/-/issues/931>. Does this same issue > affect bounce.log or is it safe to rotate similar to mailman.log? Rotating all the logs in Mailman's var/logs/ directory is appropriate. This is the logrotate script I use. ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate if [ -r /opt/mailman/mm/var/master.pid ]; then PID=`cat /opt/mailman/mm/var/master.pid` kill -s HUP $PID fi if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` You will still have the issue #931 in that the smtp.log will rotate, but as it says in that issue, the runners that write smtp.log directly will write to the new generation, but aiosmtpd continues to write to the older log until such time as mailman core is restarted. I'm not sure what will happen if mailman core is not restarted before the log aiosmtpd is writing to is rotated out of existence, but that could be an issue too. You could avoid this by replacing ``` if [ -r /opt/mailman/mm/var/master.pid ]; then PID=`cat /opt/mailman/mm/var/master.pid` kill -s HUP $PID fi ``` in the above postrotate script with ``` if [ -r /opt/mailman/mm/var/master.pid ]; then sudo -u mailman /opt/mailman/mm/bin/mailman restart &>/dev/null || true fi ``` but there is a potential issue in that if Mailman is delivering list mail when the `mailman restart` command is issued, some recipients may receive duplicates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 10:41, Bryan Fields wrote: > On 7/26/24 1:30 PM, Bryan Fields wrote: > >> mailman=> \c mailmanweb >> You are now connected to database "mailmanweb" as user "mailman". >> mailmanweb=> SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM >> date_active) < 1000; >> id | thread_id | date_active | >> category_id | mailinglist_id | starting_email_id >> -------+----------------------------------+------------------------+-------------+----------------+------------------- >> 35670 | GHLCKUC7TDEBAI27SKRQN5PWX3TGB26Q | 0102-04-15 20:06:12+00 >> | | 3 | 150555 >> (1 row) >> >> mailmanweb=> SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM >> date) < 1000; >> id >> -------- >> 136872 >> 150555 >> (2 rows) >> >> Does this mean it imported archives with an invalid date somehow? Yes, I suspect this bad date is part of the issue. I would do a few things. First, SELECT message_id FROM hyperkitty_email WHERE thread_id = 35670; If this returns just the one message_id, I would then DELETE FROM hyperkitty_thread WHERE id = 35670; DELETE FROM hyperkitty_email WHERE id = 150555; and see if that fixes the internal server error when accessing the archive. I would also SELECT * FROM hyperkitty_email WHERE id = 136872; and maybe update the `date` in that entry. After deleting that one message and thread, you can make a mbox with just the one message with the date corrected and run hyperkitty_import with `--since 2000-01-01` and that mbox as input to add the message back to the archive. Also, FYI, assuming those messages with very old Date: headers had reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script would fix them, except you have to get the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… or https://www.msapiro.net/scripts/cleanarch3 because the script in the latest release has a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 10/1/20 3:23 PM, Mohsen Masoudfar wrote: > Hi Mark, > Thanks again for the helpful hint. It seems that I still miss something. I am running Mailman3.1.1. I ran the following on my test server. > I am trying, for test purpose only, to filter PDF attachments. > > First I just used the pass_type, assuming once this is set, everything else is filtered. That's how it should work. > # mailman withlist testlist3(a)x.com >>>> m.pass_types = ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>>> commit() >>>> print(list(m.pass_types)) > ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] > > This let PDF be send by Mailman3. Well, I need to add filter_types too, so I did this: It shouldn't unless athe Content-Type: of the PDF part was text/* or application/pgp-signature >>>> m.filter_types = ['application/pdf'] >>>> commit() >>>> print(list(m.filter_types)) > ['application/pdf'] This should allow ONLY the PDF and nothing else, not even the text/* message body parts. > Mailman3 still distributes PDF files as attachment. What am I doing wrong? > > This is the final settings: > >>>> print(list(m.pass_types)) > ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>>> print(list(m.filter_types)) > ['application/pdf'] This is wrong. set m.filter_types =[] Look at the raw message you receive from the list. What is the VConten-Type of the PDF part? Actually, what's m.filter_content? I suspect it's False which means don't do any content filtering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Request for help debugging a hyperkitty connection issue

by Mark Sapiro

On 1/6/22 12:12 PM, Stephen Daniel wrote: > > I have two problems. One is with getting list mail out of GCP. I am > working on that. The issue I don't know how to address is a problem with > hyperkitty. Nothing is being archived. When I send an email through my > test list, this message shows up in the mailman log: > > Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver > > Traceback (most recent call last): > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", > line 175, in _new_conn > > (self._dns_host, self.port), self.timeout, **extra_kw > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", > line 73, in create_connection > > for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): > > File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo > > for res in _socket.getaddrinfo(host, port, family, type, proto, flags): > > socket.gaierror: [Errno -2] Name or service not known > > > This triggers a bunch more tracebacks. > > Then I get this: > > Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed: > HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', > port=443): Max retries exceeded with url: /archives/api/mailman/archive > (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object > at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name > or service not known')) What is your setting for base_url: in mailman-hyperkitty.cfg?. Can you get wget -O- xxx where xxx is base_url with `api/` appended. This should return an html page of API documentation. If your base_url: seems good and its scheme is `https`, try changing it to `http`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/26/23 12:25 AM, mrl(a)psfc.mit.edu wrote: > I've asked the wrong question. The correct question is that my MM2 imported mailing list, shows the setting "Default action to take when a member posts to the list" is set to "Hold for moderation". That is expected because your MM 2.1 list had member_moderation_action = Hold. > However, when I add a user via Mass Subscription, and view the user in the member's list, it states "None" in the moderation column for him. Doesn't that imply, not to hold for moderation? Or am I wrong? No. That means apply the list's default. > Note that when I look at the user's "Administration options Moderation" personal setting, it is set to "List Default." I assume that because the List's setting in the above first paragraph is "Hold for moderation", that this means the "List Default" is set for moderating. And that newly added email addresses should be moderated. Or am I wrong? Newly added users get their moderation action set to None. This means the same thing as the List Default you see as an admin looking at the user. If you set the user to something other than List Default and then set it back to List Default, the actual value set for the member's moderation_action is None. I.e., List Default is a more admin friendly way of displaying/setting None for the value. Presumably, your MM 2.1 list had default_member_moderation = Yes and member_moderation_action = Hold and this mimics that behavior. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Where to start looking?

by Mark Sapiro

On 3/11/26 17:05, Paul Tomblin via Mailman-users wrote: > So I imported all our mailman2 lists into mailman3, and it appears it didn't preserve passwords. So my wife (who administers 3 lists of her own) tried to use the reset password link (multiple times) but she never gets the email. I don't see any outgoing email to her in mail.log, or any of the mailman logs. I do the exact same thing as her and I get the email. Any suggestions on what I should be looking for? Mailman 2.1 passwords have no meaning in Mailman 3 and aren't imported. in MM 2.1 passwords were per list per member. In Mailman 3 core, there are no corresponding passwords. Passwords are for logging in to the web UI which is separate. Bottom line. You need to go to <https://your.site/accounts/signup/> and signup for an account. Then if you have more than one email address, go to <https://your.site/accounts/email/> and add your other addresses. Then, once logged in you should be able to manage any lists for which one of your addresses was imported as an owner and moderate any lists for which one of your addresses was imported as a moderator. Your wife can't get a password reset email because she hasn't signed up for an account and there is no password to reset. Apparently you did sign up for an account or maybe if you've configured any social account logins, you logged in with one of those which will create an account for you. You might find <https://docs.mailman3.org/en/latest/django-primer.html> useful. It discusses a bit about Django which is the web framework for Postorius and HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Flushing/syncing hyperkitty with mailman

by Mark Sapiro

On 06/16/2018 06:38 PM, Eric Abrahamsen wrote: > > > A bump for this, I've been getting this series of errors once a minute > for weeks now. There must be some way to clear out dangling thread > references? And I take it that for the meantime we shouldn't be using > the "delete thread" feature of hyperkitty... > >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] >> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >> [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] >> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >> [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> >> Is there something more I should be doing to sync hyperkitty's database >> with mailman? I've got the crontab file in place, and that appears to be >> running without error. Anything else? Except that 'django-admin runjobs minutely' is probably what's producing the errors. You might try 'django-admin runjob empty_threads' (normally a monthly job) or 'django-admin runjob thread_order_depth' (normally a yearly job). I don't know if they will clear this up or not, but I don't think it would hurt to try. See 'django-admin runjob --list' to see the various jobs and note that 'django-admin runjob update_index' which runs minutely and does an incremental update is not the same as 'django-admin update_index' which only runs manually and does a full search index update. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

Search results for query "sapiro"