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

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

by Mark Sapiro

On 8/13/21 7:18 AM, Richard Rosner wrote: > > I set them all to https. which solved the https error. But I still get Error 500. >>From apache log: > [Fri Aug 13 15:47:58.833305 2021] [mpm_event:notice] [pid 26720:tid 139986206332032] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 \ > Python/3.7 configured -- resuming normal operations > [Fri Aug 13 15:47:58.833436 2021] [core:notice] [pid 26720:tid 139986206332032] AH00094: Command line: '/usr/sbin/apache2' > [Fri Aug 13 15:49:41.673108 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ > rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] > [Fri Aug 13 15:49:41.905868 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ > 7.0.0.1) > [Fri Aug 13 15:59:25.049708 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ > rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] > [Fri Aug 13 15:59:25.059217 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ > 7.0.0.1) You need SSLProxyEngine on and possibly one or more of the SSLProxyMachineCertificate* directives in your apache config to proxy via https. See <https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslproxymachinecertifica…> et seq. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Problem creating list members using REST API

by Mark Sapiro

On 1/18/22 10:53 AM, Stephen Daniel wrote: > 2nd follow-up. Apologies for spamming this list. > > I went wandering through the code as suggested by the traceback. I > discovered that thee "as_boolean" routine is expecting a string argument > but getting a boolean argument. > > So, If I send the booleans as strings, with values "true" or "false", all > is well. > This is not what the API documentation suggests I should do. Can someone > either fix the documentation or the code? Those snippets in the documentation are doctests. That code is actually executed by unit testing and passes. In all those snippets, dump_json is passing the second argument as `data` to mailman.testing.documentation.dump_json() which in turn calls mailman.testing.documentation.call_http() which calls mailman.testing.helpers.call_api() which ultimately calls requests.request() with the same `data` argument. So basically, the issue is the difference between how requests.request() handles that `data` dictionary in creating the POST data and whatever you are doing. Possibly we could add some caveat to <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> or possibly elsewhere. Do you have a suggestion as to what? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Weird startup problem after upgrade

by Mark Sapiro

On 12/2/22 08:21, Odhiambo Washington wrote: > I am facing an odd situation in which MM3 doesn't start successfully on > reboot, but I can start it manually. > This is a venv install. > This started after I did an upgrade (pip install --upgrade mailman > postorius hyperkitty mailman-hyperkitty) followed by the requisite > collectstatic|compress|compilemessages|migrate > post-update commands. Was the venv activated when you ran pip? You should also include django-mailman3 and mailmanclient in the packages to be upgraded although they are dependencies and "should" upgrade anyway. Also, at least one person has noted that --force-reinstall was required to get all dependencies upgraded <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > Secondly, it appears that the upgrade did NOT change the versions for the > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > the latest. What does `pip freeze` in the venv show for versions? > Thanks in advance for any insights into what could be causing this. How do you start it manually? `mailman start` or `systemctl start mailman3`? What's the content of /etc/systemd/system/mailman3.service? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: default language ignored

by Mark Sapiro

On 10/02/2017 05:46 AM, Marc Sluiter wrote: > Hi, > > one last question for now: how do switch the language of the mails sent by mailman? > I have this in my configuration, but without effect: > > [language.de] charset: iso-8859-1 > [language.de] description: German > [language.de] enabled: yes > > [mailman] default_language: de It has no effect because there are as yet no translations in Mailman 3. You need to create templates in the desired language. See <http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html> That refers to setting URLs for templates which does work, but the easiest way is to put them in the default search path in Mailman's file hierarchy at $var-dir/templates/. Sitewide ones in $var-dir/templates/site/, Domain specific in $var-dir/templates/domains/ and list specific ones in $var-dir/templates/lists/. For example, a list specific, English language regular (non-digest) message footer might go in $var-dir/templates/lists/mymaillist.example.com/en/list:member:regular:footer > Is it also possible to change the language for a single list? Yes, although that is not yet exposed in Postorius. The list has a preferred_language attribute which you can set via REST or 'mailman withlist' aka 'mailman shell'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: list of subscribers

by Mark Sapiro

On 02/04/2018 11:37 AM (UTC -0800), Peter Münster wrote: > On Sun, Feb 04 2018, Simon Hanna wrote: > >> IIRC one person(postorius account) can also signup at different lists using >> different names (regardless of address). > > You mean the "display_name" of mailmanclient here? I won't use it. > For my usage, I prefer a clear association of email, first name and > last name in one account, no need for "display_name" here. This would seem to be specific to your use case. I think in general what we would want to display is the display_name from the list's member record. > Off topic: I have "Receive own postings = Yes", but I don't receive > copies of my postings to this list... We tried to send your copy of your post to you, but your MTA called it spam. Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command)) (time stamp is UTC -0000) I suspect it doesn't like the fact that it's From: you but not sent by your server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 5/5/20 8:55 AM, Mark Dadgar wrote: > I moved my mail server to a Digital Ocean droplet. I basically installed all the appropriate packages and then rsync’d everything that matters from my metal server up to the cloud instance. Everything more or less works fine. > > However, I am now getting this hourly error - see below. ... > [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 36301): Term too long (> 245): XSUBJECT95251413 > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update > backend.update(index, current_qs, commit=commit) > File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 488, in update > database.replace_document(document_id, document) > xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 This error comes from Xapian. It is due to a (new) message in your archive that contains a 'word' longer than 245 characters. There is a PR at <https://github.com/notanumber/xapian-haystack/pull/181> that addresses this plus another suggested fix in that PR's comment thread. Note: I got there by googling "xapian term too long" which gave <https://github.com/notanumber/xapian-haystack/issues/153> as the first hit and that led me to the above. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/28/20 12:58 AM, r.woithe(a)callassoftware.com wrote: > Hello, > i set the necessary config params like descriped at https://wiki.list.org/x/17892072 with timeout = 9000. > But we still get the nigthly email. If you are still using Mailman core 3.2.2, those settings have no effect because the REST server doesn't use gunicorn prior to 3.3.0. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > I guess the best way would to upgrade to mailman-core 3.3.3 to avoid this error. > Unfortunatly i can not use the ubuntu package-manager... > Or is there a second way to avoid this error? I don't know if upgrading Mailman core would avoid the error or not. As I indicated, it's almost certainly not a REST timeout after all. We need to understand what causes the error. As I've said, the sync_mailman goes through the message senders and tries to set the senders mailman_id. If you apply the attached patch to hyperkitty/models/sender.py, it will log the error and ignore it. Then, we'll get a bit more info from the log message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/2/23 07:06, Jan Eden via Mailman-users wrote: > On 2023-01-02 14:36, Eggert Ehmke via Mailman-users wrote: > >> Thank you, that worked! Now all my addresses are clean. >> >> Still, don't you think this should be possible via Postorius, or by some mailman cli command, like >> mailman rename_member <old> <new> Yes, it should be possible to change the display name for an address via Postorius. See https://gitlab.com/mailman/postorius/-/issues/451. >> It happened I had still the patched cli_members.py where I had both the old and new line active: >> print(formataddr((address.display_name, address.original_email)), file=outfp) >> print(f'{address.display_name} <{address.original_email}>', file=outfp) >> The first (old) line still produces the output with utf-8 codes. Is this to be expected? > > I would assume the original line outputs the QP-escaped names, to be > used in an email header. Yes. The original `formataddr((address.display_name, address.original_email))` creates the format `display name <email>` suitable for use in an email header. Thus, if the display name contains non-ascii, it is RFC 2047 encoded. The encoding may be quoted-printable or base64 depending on which is shorter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Social signup?

by Mark Sapiro

On 3/12/23 14:32, Duane Raymond wrote: > > Thanks for clarifying. Once I implemented social login, the buttons for > social login did appear fine on the login page, but not on the signup > page. I noticed for this list as well, there are no social signup > buttons. The buttons do not appear on the sign-up page. They probably should, but they don't. > So if it works, how does this happen? > > 1. Is there something I am missing adding to my settings.py and > settings_local.py files to make it appear on the Posterius/Hyperkitty > signup (vs login) page? (I searched but couldn't find anything) You aren't missing anything. > 2. Do I manually add this code to the Posterius/Hyperkitty signup > template? No > 3. If a user tries to login via the login page and isn't registered will > it be counted as a signup? Yes, that's how it works. > I'm trying to get my head around where this is working from / what I need > to do to get social signup obvious on the signup page (or other route) I just created https://gitlab.com/mailman/django-mailman3/-/issues/67 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 11/11/22 16:36, Caballero, Danny (Dan) wrote: > Thanks for some clarification. > > I cleared out 2800 held messages via Python shell "mailman -l" option and it took about 28 hours. Anything done via Mailman shell is a connection from Mailman core to the database, correct? That's correct. > Although I can't replicate that many messages via Postorius/DJango, I do see similar slowness there as well at a message per minute or more of processing. > > I recreated the above Mailman shell clean up via Docker container running MariaDB and noticed similar processing time for discarding held messages. That leads me to conclude that the issue isn't network related or specific to AWS RDS. I'm assuming the docker container installation also had all the lists/users? It seems this must be related to a large number of lists/users and we must be doing a number of queries that doesn't scale well. This seems excessive. We'll have to look at the processing to see what we're doing. There have been some recent improvements in scaling. What Mailman core version is this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Search results for query "sapiro"