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

[MM3-users] Re: Centralizing logging

by Odhiambo Washington

On Wed, Sep 29, 2021 at 7:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/29/21 4:51 AM, Odhiambo Washington wrote: > > > However, there is this process that *forced* me to create > > usr/local/mailman/*logs/mailmansuite.log > > *as opposed to it just writing to var/logs/ path above > > > > Is there a way to make it write its log $var_dir ? > > > This is Django's log. Django knows nothing about mailman.cfg which is > for core only. You can set the path in your Django settings. See > LOGGING['handlers']['file']['filename'] > > I deal with this by creating a symlink like > > /usr/local/mailman/logs -> /usr/local/mailman/var/logs > Wuah. I did not even think about a simple symlink. Thank you so much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 6 months

[MM3-users] Re: All users getting disabled after upgrade of mailman3

by Quanah Gibson-Mount

--On Thursday, January 18, 2024 6:09 PM -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/24 15:08, Quanah Gibson-Mount wrote: >> Hello, >> >> We just upgraded our mailman to the latest provided from Debian bookworm >> (I know, not the recommended installation method). >> >> >> >> Now everyone's having their addresses disabled due to "bounce" errors. >> This is odd, because I'm disabled, even though I received the 2 emails I >> sent to the list today (and that's the only list traffic today). > > > Did you upgrade mailman core from a version older than 3.3.1? > > If so, see this post > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess > age/IC3LXQMANJGOVUOCVUBHIOGYZ4PA24F7/>. That's it! Thank you so much Mark! Excellent help as always. Regards, Quanah

2 years, 2 months

[MM3-users] Looking for large sites that have migrated to mailman3

by Stephen J. Turnbull

ssw(a)washington.edu writes: > We're looking for information on large sites that have migrated to > mailman3. Preferably academic institutions. As we start to look > at a migration project we're hoping to hear any 'lessons learned' > from those who have gone before us. The largest site I know of that has begun migration to Mailman 3, and has a non-trivial (dozens, maybe?) number of lists in operation is python.org. You can try searching the archives for this list and in mailman-developers(a)python.org for python.org and mailman3.org postmaster Mark Sapiro's opinions on the matter. I think the EMWD hosting site is also in process of migrating. I know there are several others (specifically a couple of academic institutions) basically at the very beginning of their migrations, but I don't know any in the later stages. Steve

6 years, 8 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

On 10/24/23 18:29, Mark Sapiro wrote: > On 10/24/23 12:34 PM, Thomas Ward via Mailman-users wrote: >> >> ... I get a hard load error on "ModuleNotFoundError: No module named >> 'MailmanCustomizations'" >> >> To confirm this is a Python module/class, I did a pure python shell >> with `from mailman_customizations.hooks import >> MailmanCustomizations` and it properly imports that class, so I'm >> not sure where to go from here in debugging. > > What if you try this with `mailman-web shell`? > Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. Thomas

2 years, 5 months

[MM3-users] Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Flo

On 8/25/25 23:36, Mark Sapiro wrote: > On 8/25/25 12:42, Flo via Mailman-users wrote: >> Hi, >> >> I have setup in Debian Trixie mailman3-full and came that far, that I >> have created a mailing list. I can sent emails to the members. > > Your primary support resource for the Debian package is Debian. See > https://wiki.list.org/x/12812344 > That's right. > > You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in > settings.py. If you Debian packages don't do this, it should definitely > be reported to Debian. > In /usr/share/mailman3-web/settings.py there is: INSTALLED_APPS = ( ... 'django.contrib.humanize', ... ) And POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8001' I think this has also something to do with it. But looks correct for me. Flo But maybe the path

7 months, 1 week

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/8/21 6:44 AM, rrosner5(a)gmail.com wrote: > > I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. Please see <https://wiki.list.org/x/12812344>. > I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. > > I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. > Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: > > /usr/share/mailman3-web/manage.py mmclient > Python 3.7.3 (default, Jan 22 2021, 20:04:44) > [GCC 8.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> client.system > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect > raise socket_err > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect > sock.connect((self.host, self.port)) > ConnectionRefusedError: [Errno 111] Connection refused The REST API is apparently not listening on the host/port this is trying to connest to. > An excerpt from /var/log/mailman3/web/mailman-web.log: > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ > command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute > settings.INSTALLED_APPS > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ > self._setup(name) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup > self._wrapped = Settings(settings_module) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ > mod = importlib.import_module(self.SETTINGS_MODULE) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/share/mailman3-web/settings.py", line 486, in <module> > from settings_local import * > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 724, in exec_module > File "<frozen importlib._bootstrap_external>", line 859, in get_code > File "<frozen importlib._bootstrap_external>", line 916, in get_data > PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' > [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds > > not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. What is executing the manage.py command to start Django. Is it user list? > The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are > [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully > [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations > [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2' I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000 -- 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: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Thomas G

Hi, It's a complete migration, not just a upgrade. I rebuild every things on the new server, without data transfers (mailman data dir) other than archives. "" You can't import a gzipped mbox. You have to gunzip it. "" Omfg, yes indeed, it's work better... I have just a problem with statistics not available. "" it won't import any messages older than the most recent message in the existing archive "" It should be not a problem. I will do a dead time to process this change. > Stop prod / migrate archives / start prod on new server. Thanks, Thomas. Le mar. 2 oct. 2018 à 05:11, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 09/30/2018 11:42 PM, Thomas G wrote: > > Hi, > > > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > > install in Mailman3.2. > > > > I didn't found how migrate the archives. > >>From : HyperKitty - Version: 1.1.1 - Python2.7 > > To : HyperKitty - Version: 1.2.1 - Python3.5 > > > As Abhilash said, you shouldn't need to migrate anything but the search > index. > > > > I exported a mbox from hyperkitty (web interface) and tried to re-import > > it, without result. > > """""""""""""""""""""""""""""""""""""""" > > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > > listedetests(a)hatlab.fr > > > You can't import a gzipped mbox. You have to gunzip it. > > > > Computing thread structure > > Synchronizing properties with Mailman > > Warming up cache > > The full-text search index is not updated for this list. It will not be > > updated by the 'minutely' incremental update job. To update the index > > for this list, run the 'manage.py update_index_one_list > > listedetests(a)hatlab.fr' command. > > """""""""""""""""""""""""""""""""""""" > > The database stay empty (and web interface): > > """""""""""""""""""""""""""""""""""""" > > mailmandbnameprod=# select * from hyperkitty_email; > > id | message_id | message_id_hash | subject | content | date | timezone > > | in_reply_to | archived_date | thread_depth | thread_order | > > mailinglist_id | parent_id | sender_id | thread_id | sender_name > > > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > > (0 rows) > > """""""""""""""""""""""""""""""""""""" > > > > Any idea to do this importation ? > > > Why is the database empty? It should be as it was with the prior > HyperKitty. > > Also, it doesn't seem to be the issue here, but if you don't specify a > --since option to hyperkitty_import, it won't import any messages older > than the most recent message in the existing archive. i.e., if there are > any messages in the existing archive, the default for --since is the > date of the most recent such message. > > -- > 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/ >

7 years, 6 months

[MM3-users] Re: Messages in var/queue/shunt

by Brian Carpenter

On 10/20/20 6:15 PM, Mark Sapiro wrote: > On 10/20/20 2:29 PM, Brian Carpenter wrote: >> I have a large number of messages in the shunt directory due to some >> testing done. What is the proper method of dealing with them? Is there a >> way to release them again to the archiver or can I safely delete them? > > I'm assuming based on what you say above that these were all shunted in > the archiving process because of some issue in that process which has > been fixed. > > If that is the case, you have choices. If you want the messages to be > archived, just run `mailman unshunt`. If you don't want them archived > you can run `mailman unshunt` --discard` or you can simply remove the > .pck files from var/queue/shunt. That worked wonderfully. Thank you. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Mark Sapiro writes: > This apparently confuses the Python email package so that the > get_payload() method returns a list of strings rather than a list of > message objects. Yes, I got that far too. I'm guessing that in the absence of a Content-Type, which then *should* default to text/plain, the email package goes ahead and detects the MIME headers anyway (although I don't think it should do that) and breaks the message into MIME parts. I would think we'd raise an Exception here. If there's a reason for the email package to do that detection (*shrug*, it seems to work), then the dispatching in _handle_text should be done on the Python type rather than the MIME Content-Type. I forget exactly how the code is structured, the relevant dispatching may be in _dispatch or in _dispatch_meth. Steve

3 years, 6 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Ken Alker

--On Saturday, June 24, 2023 2:09 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/23/23 10:44 PM, Ken Alker wrote: > > > 4) python3: can't open file 'manage.py': [Errno 2] No such file or directory > > > > The last one looks the most concerning, and is looping. > > > If you installed the mailman-web package from PyPI, the django admin > command is bin/mailman-web in your venv, not manage.py. I found that in /etc/mailman3/uwsgi.ini and changed it and it solved the problem. Thank you! I sent a reply to my original email this morning but when I view it in the web archives, it see that it didn't get threaded with my original email. I hope this one does. I wonder why the original did not. Ken

2 years, 9 months

Search results for query "sapiro"