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

[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

5 years

[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, 9 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

11 months, 3 weeks

[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, 10 months

[MM3-users] Re: Mailman-web showing "An error occurred while processing your request."

by C. Souza

Hello Guys, Thank you for the help. Mark, I followed your recommendation running your code and it's done, problem solved. Just for curiosity, does anyone know the reasons for this kind of problem and how to avoid it? Thank you very much. -- Carlos Adean On Thu, Feb 9, 2023 at 1:55 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/8/23 08:34, C. Souza wrote: > > I'm trying to manage 2 held messages in a specific list and I'm getting > > this error below when I click on /held_messages. It never happened > before. > ... > > ==> mailmanweb.log <== > > ERROR 2023-02-08 16:01:30,149 1516 django.request Internal Server Error: > > /mailman3/lists/mylist.domain.com/held_messages > > Traceback (most recent call last): > ... > > File > > > "/opt/mailman/venv/lib64/python3.6/site-packages/django/utils/dateparse.py", > > line 107, in parse_datetime > > match = datetime_re.match(value) > > TypeError: expected string or bytes-like object > > > I'm not certain, but it looks like one of the held messages has a bad or > possibly missing Date: header. Working around this is tricky. You can do > the following in mailman shell. > ``` > $ mailman shell -l list(a)example.com > > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> requests = IListRequests(m) > >>> msgstor = getUtility(IMessageStore) > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if data['_request_type'] == 'held_message': > ... print(f'request ID = {request.id}Message-ID = {key}\n ' > ... f'message = {msgstor.get_message_by_id(key)}') > ... > This will print for each held message output like > > request ID = nnn > Message-ID = <the message id> > message = the message content > > > You can then handle these messages with > > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, nnn, action) > > where nnn is the request ID and action is either Action.discard to > discard the message or Action.accept to accept it. And finally > > >>> commit() > ``` > If you decide you want to edit the message content before accepting it, > you could find the message in the file system. One of the headers in the > displayed message is something like > > Message-ID-Hash: IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL > > the message is saved as a python pickle in the file system in Mailman's > var/messages/ directory. This has subdirectories of the first two > characters of the Message-ID-Hash value and those have subdirectories of > the second two characters of the Message-ID-Hash value, so if the above > were the actual Message-ID-Hash the pickle would be at > var/messages/IW/L2/IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL. You would need to > pickle the new message content and save that over the existing file. > > -- > 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… > > This message sent to skooperit(a)gmail.com >

3 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, 9 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, 11 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

3 years, 1 month

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

The difference in behavior was using social login buttons for an existing account vs. creating a new account. This is another damn django-allauth regression, starting in 0.57.0. It seem to be this commit that is to blame: https://github.com/pennersr/django-allauth/commit/be779dfee5a328a3a42edc2c9… In allauth/socialaccount/models.py:lookup(self):285 there is an attempt to look up the social account as one that already exists. If that fails, this commit calls self.account.get_provider() without passing the request object, which leads to the eventual error. I believe this is a django-allauth bug, and have submitted a pull request to fix it here: https://github.com/pennersr/django-allauth/pull/3548 Patch also included below. --Jered --- a/allauth/socialaccount/helpers.py +++ b/allauth/socialaccount/helpers.py @@ -205,7 +205,7 @@ def _add_social_account(request, sociallogin): def complete_social_login(request, sociallogin): assert not sociallogin.is_existing - sociallogin.lookup() + sociallogin.lookup(request) try: get_adapter().pre_social_login(request, sociallogin) signals.pre_social_login.send( --- a/allauth/socialaccount/models.py +++ b/allauth/socialaccount/models.py @@ -274,12 +274,12 @@ class SocialLogin(object): return False return get_user_model().objects.filter(pk=self.user.pk).exists() - def lookup(self): + def lookup(self, request=None): """Look up the existing local user account to which this social login points, if any. """ if not self._lookup_by_socialaccount(): - provider_id = self.account.get_provider().id + provider_id = self.account.get_provider(request).id if app_settings.EMAIL_AUTHENTICATION or app_settings.PROVIDERS.get( provider_id, {} ).get("EMAIL_AUTHENTICATION", False): ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise ImproperlyConfigured( > 'You\'re using the Django "sites framework" without having ' > "set the SITE_ID setting. Create a site in your database and " > "set the SITE_ID setting or pass a request to " > "Site.objects.get_current() to fix this error." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > 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… > > This message sent to jered(a)convivian.com

2 years, 8 months

[MM3-users] Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Stephen J. Turnbull

Mail Person writes: > Hello everyone. I am trying to sort out an error happening when > messages are sent to the mailman server. The emails are being sent > to the list but I get this error each time: > > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") This looks like the MySQL "we don't do 4-byte UTF-8" bug. > File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute > 209. res = self._query(query) and it is MySQL, so the problem is most likely that your MySQL is not configured to handle Unicode properly. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… for a lot of information about this. All the posters have useful comments but start with Mark Sapiro's.

3 years

Search results for query "sapiro"