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

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

by Mark Sapiro

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

1 year, 6 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/24/20 7:20 PM, Alan So wrote: > Really thanks for your hard work Mark! It is a bit strange that parseaddr behave differently with CRLF and LF. Maybe if the server is a Windows, the behavior is consistent. It might be that on Windows, `mailman inject` would create the message with CRLF line endings. > May I know when or whether will this patch be committed to the repository so that it will be effective in future release of Mailman? Thanks. In the absence of an issue at <https://gitlab.com/mailman/mailman/-/issues>, probably never. <hint> The bottom line is the original mail created by Outlook is defective.[1] While Mailman could defend against this defect, starting to do that opens the possibility that there are other areas of the code that need a similar defense. Have you asked Microsoft to fix Outlook to not create these defective messages? That's the real solution. That said, if an issue is filed, someone might consider adding something along the lines of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> to the code base. [1] given an address of the form display-name (comment) <addr-spec> in a header, it can be folded either between the display-name and the (comment) or between the (comment) and the <addr-spec>, but if display-name (comment) is quoted as in "display-name (comment)" <addr-spec> "display-name (comment)" is now a phrase within which folding is not allowed and this can only be folded between the "display-name (comment)" and the <addr-spec>. -- 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: Change language to welcome message in mailman3

by Mark Sapiro

On 7/24/20 2:10 PM, Massimo Zappalà wrote: > Hi everyone, > > My Version installed on Debian buster: > mailman3: 3.2.1 > postorius: 1.2.4 > hyperkitty: 1.2.2 > > All interfaces work well in Italian language, but "Welcome message" is in English. First question: Is the Subject: in English or Italian? If the Subject: is in English you need to compile the Italian message catalog as I described in my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Then, as far as the message body is concerned, it is built from a template. At present, in the Mailman source distribution, the only templates that are translated are French and German You will find the complete set of English templates at /usr/lib/python3/dist-packages/mailman/templates/en/. You have choices. 1) You can create /usr/lib/python3/dist-packages/mailman/templates/it/ and make Italian translations of all the English templates in the it/ directory in files of the same names, and submit a merge request at <https://gitlab.com/mailman/mailman/-/merge_requests> to merge them into the source distribution. If you are not familiar with software development in general and Mailman development in particular, this is probably beyond what you can do. 2) Find Mailman's var/ directory. This is the directory containing archives/, data/, etc/, lists/, locks/, logs/ and perhaps other sub-directories. You then need to create the full path to var/templates/site/it/ and place Italian translations of some or all the templates there. When doing so, you can add site customizations. 3) You can use Postorius to create templates for individual lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/24/20 7:22 PM, Abhilash Raj wrote: > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). It's more complicated than that. Sometimes the fragment name is the heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor #3.3.3 work at all as these are #id2 and #id1 respectively. Currently the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but when a Command line section is added under 3.3.3, that will probably get the command-line id. Thus, the note "Permalink to this headline" es misleading at best because it isn't very permanent fo an evolving document. > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. I too think this is correct. I suppose it might be worth doing for NEWS.rst in particular since Sphinx doesn't seem to like fragments like n.n.n. Another way to deal with this would be to always use code names. It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: what process creates webui tables (mailmanweb db)?

by Mark Sapiro

On 9/26/22 09:14, tflatley(a)gmail.com wrote: > hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate Probably not. First of all, `mailman-web migrate` will only affect the mailmanweb database, not the mailman database, migrations for which are run implicitly when Mailman core is started. Also, migrations will only affect tables for which there are migrations, not all tables. > this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file > > python3 manage.py migrate Yes. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. The above message saying you need to make migrations because of changes to models indicates that your Debian/Ubuntu package is broken as the packager should have created all necessary migrations. > i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? I am confused as to why you are trying to run an out of date and possibly broken Debian/Ubuntu package when it appears you have successfully installed the latest PyPI packages in a venv. -- 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: Deleting A List

by Mark Sapiro

On 5/3/24 03:59, Odhiambo Washington wrote: > On Thu, May 2, 2024 at 8:11 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/2/24 03:42, Odhiambo Washington wrote: >>> I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. >>> I can see from Django Admin UI that the archives are still intact. >>> I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke >>> Is there a way to move the archives from the old list to the new list? >> >> >> Change the `name` and `list_id` in the list's entry in the >> `hyperkitty_mailinglist` table in the database. If there is already an >> entry there for the new list, delete it >> >> > ``` > mysql> select id, name, list_id from hyperkitty_mailinglist; > +----+----------------------------+----------------------------+ > | id | name | list_id | > +----+----------------------------+----------------------------+ > | 1 | skunkworks(a)lists.my.co.ke | skunkworks.lists.my.co.ke | > | 2 | list(a)nog.ke | list.nog.ke | > | 3 | eanog(a)lists.my.co.ke | eanog.lists.my.co.ke | > | 4 | isoc(a)lists.my.co.ke | isoc.lists.my.co.ke | > | 5 | kazi(a)lists.my.co.ke | kazi.lists.my.co.ke | > | 6 | kenog(a)lists.my.co.ke | kenog.lists.my.co.ke | > | 7 | mechanics(a)lists.my.co.ke | mechanics.lists.my.co.ke | > | 8 | science(a)lists.my.co.ke | science.lists.my.co.ke | > | 9 | security(a)lists.my.co.ke | security.lists.my.co.ke | > | 10 | vmware_tech(a)lists.my.co.ke | vmware_tech.lists.my.co.ke | > | 11 | water(a)lists.my.co.ke | water.lists.my.co.ke | > | 12 | wordpress(a)lists.my.co.ke | wordpress.lists.my.co.ke | > | 13 | list(a)lists.nog.ke | list.lists.nog.ke | > +----+----------------------------+----------------------------+ > 13 rows in set (0.00 sec) > > mysql> delete from hyperkitty_mailinglist where id = 13; > ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key > constraint fails (`mailmansuite`.`hyperkitty_mailinglist_owners`, > CONSTRAINT `hyperkitty_mailingli_mailinglist_id_a47e04ec_fk_hyperkitt` > FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperkitty_mailinglist` (`id`)) > ``` > > Is there an easier way? > I need to delete id=13 then rename id=2 > There are several tables that reference the hyperkitty_mailinglist table by id. These are hyperkitty_email, hyperkitty_mailinglist_owners, hyperkitty_mailinglist_moderators and hyperkitty_thread. Ideally, you wouldn't have created the list(a)lists.nog.ke before updating the hyperkitty_mailinglist entry, but now, do the following: ``` update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_owners set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where mailinglist_id = 13; update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = 13; delete from hyperkitty_mailinglist where id = 13; update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = 'list.lists.nog.ke' where id = 2; ``` If there have been no posts to the list(a)lists.nog.ke list the updates of hyperkitty_email and hyperkitty_thread won't do anything, and likewise the update of hyperkitty_mailinglist_moderators if the list has no moderators -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Place holders

by Mark Sapiro

On 5/27/25 23:23, Mark wrote: > Hi, > > The place holders listed as available on the "Add new template" page are: > > $hyperkitty_url > $listname > $list_id: > $display_name > $short_listname: > $domain > $info > $request_email > $owner_email > $site_email > $language What Postorius version is this? You may be missing some things added in 1.3.11. A more complete list including the ones that only work in certain contexts is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… a pointer to which was added in 1.3.11. > The only one that seems to sort of work on my template is $list_id - > which displays as "testlist". (I was expecting to see > "testlist(a)example.com"). $listname should be replaced with the fqdn list name like "testlist(a)example.com" and $short_listname should be replaced with the list name without the @domain as in "testlist". The others should all work as documented. I don't know why they wouldn't. Can you give an example of a template that doesn't get these substituted. > The others just get displayed as a variable. Eg. $owner_email > > Have I missed a setting somewhere? The actual substitution is done by the Python `string` library module Template class, safe_substitute method. See the doc at https://docs.python.org/3/library/string.html#template-strings Note that because we use the safe_substitute method, invalid substitutions don't produce errors, they just aren't substituted. In particular if `$identifier` is followed immediately by a letter, digit or underscore, `identifier` must be wrapped in `{}` to separate it from the following characters, e.g., `${identifier}x`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 4 days

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Mark Sapiro

On 7/23/20 12:38 AM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > I understood that gunicorn is a front end that is used like web server like > nginx. > > But I don't think I am using it instead I am using the httpd to redirect > requests to postorius. Steve has addressed this. > So, in this case, do you think configuring gunicorn as below would work: You do need to configure gunicorn timeout to solve your issue. > *calling gunicorn.cfg in mailman.cfg as below * > > *[webservice]* > *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* Do NOT do this. Make your own gunicorn.cfg outside of /var/lib/mailman/mailman/src/mailman/ and point to that. Otherwise any upgrade will reverse your changes. > > *and content of gunicorn.cfg as below* > > (venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg > [gunicorn] > # All the options that can be put here are available at > # http://docs.gunicorn.org/en/stable/settings.html#settings > # No of seconds to wait before killing the worker processes. > > workers = 4 > graceful_timeout = 90 > > Also what is the difference between timeout and graceful_timeout ? graceful_timeout is not what you want. It addresses something different. As it says in the comment, all the gunicorn settings are described at <http://docs.gunicorn.org/en/stable/settings.html#settings>. timeout and graceful_timeout are near the bottom of that page at <https://docs.gunicorn.org/en/stable/settings.html#timeout> and <https://docs.gunicorn.org/en/stable/settings.html#graceful-timeout>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 9:24 PM, Alan So wrote: > Just FYI. > > I omitted the "<" and ">" when I replace the real testing address with name(a)example.com. > > It should be, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> Actually, you didn't omit them. It's just the way HyperKitty renders what it thinks is an email address that makes it appear they aren't there. If you download the thread from HyperKitty, you'll see they are there. Anyway I am unable to duplicate your issue with your example data. I sent this raw message ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Cc: abc def (ghi) <abc(a)example.com> "abc def (ghi)" <def(a)example.com> Subject: test Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 Hi ``` and the message I received from the list included these headers ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 CC: "abc def (ghi)" <abc(a)example.com>, "abc def (ghi)" <def(a)example.com> Subject: [List] test ``` I do observe something similar to what you report that has nothing to do with folding. If I omit the trailing ">" in an address as in ``` From: Mark <mark(a)msapiro.net ``` the address becomes ``` From: "Mark <mark"@msapiro.net ``` So possibly your issue involves missing angle brackets. In order to say more, I'd need to see the actual headers as sent and received or at least an accurate munged representation. -- 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: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 4:19 PM, Ken Alker wrote: > > What else is stored in /var/messages, if not archives? I see 4711 > messages in that directory (which I presume would be as many messages > are in the archive database). If there is a write-up on this, feel free > to point me to it. I found > <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode…> but this isn't really answering my question. These are probably artifacts from your old Debian package. There have been issues in the past with handled messages not being removed from the message store. See https://gitlab.com/mailman/mailman/-/issues/257 This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes orphaned messages from the message store, but if they are still referenced in pendings they won't be deleted. > I didn't think so, but I'll certainly buy that. So, I'm assuming by > this you are implying that there is no helper function that needed to > run and the number of held messages should have dropped to zero > immediately upon a refresh of the web page? Correct, assuming your changes were committed. > So if I run the script, exist the shell, then come back in again, I > can't rely on the request.id being the same? I'd need to re-run the > script and get a new request.id? No. The request id for a given held message won't change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Search results for query "sapiro"