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

[MM3-users] Re: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 05:25, Odhiambo Washington wrote: > I looked at my list archives and saw that the latest post was on Dec 8, > 2022. > Then, because I wanted to import any posts that happened from 8th to now(), > I looked at two posts: > 1. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > This talks about 'hyperkitty_import *--since=01.01.2022* -l mylist@mydomain > my-mbox-file' > > 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html > Which talks about 'hyperkitty_import *--since='1990-01-01'* -l > mylist@mydomain my-mbox-file' The default without the since= option is to import only those messages from the mbox which are newer than the newest message in the existing archive which is exactly what you want. > I am concerned about the implication of the date format here, especially > because our species from America write their dates differently than the > British, even though > the British colonized us all :P hyperkitty_import uses python-dateutil <https://dateutil.readthedocs.io/en/stable/> to parse the since date. See <https://dateutil.readthedocs.io/en/stable/parser.html> for info on formats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Add member to a list by email

by Mark Sapiro

On 11/12/24 02:00, via Mailman-users wrote: > Hello, > > I'm trying to add members by email with the following content. > > Recipient: testlist-request(a)xxxxxxxx.de > Email content: join address=max.mustermann(a)xxxxxxxx.de > > After I've sent this email, it still has to be confirmed in the Postorius web interface under member requests. How can I confirm membership by email, or deactivate this confirmation for moderators? You can use the email `confirm` command to confirm the request, but you need the token associated with the request to confirm it, and there is no good way to find it as it is not in the confirmation request notice sent to the list admins. To not require moderator confirmation at all, you can set the list's subscription policy. Normally, subscriptions should require confirmation by the user, a list admin or both. You can set it to require neither, but this is normally a bad idea if list addresses are accessible from outside your local network as it allows anyone to subscribe anyone else by spoofing their address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/2/22 12:04 PM, Andy Smith wrote: > > For ~6k messages it still took approx 16 hours to run that monthly > job, and during that time spewed out thousands of these errors: > > Failed to remove document 'hyperkitty.email.29351' from Whoosh: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove > self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query > w = self.writer() > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer > return SegmentWriter(self, **kwargs) > File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ > raise LockError > whoosh.index.LockError > > …so I'm not even sure if it worked. I think the warnings come from the hourly update_index job which can't obtain a lock on the index because the update_and_clean_index job already has it locked. Once the update_and_clean_index job finishes the update_index job should run and do the right thing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Owner's or Moderator's Lists

by Mark Sapiro

On 7/31/20 11:09 AM, Johnny Cison wrote: > > It's 1.1.2, which is the python3-django-postorius version included with the > package manager on Ubuntu 18.04. > > Is there by chance a mechanism for viewing that information in 1.1.2? You have several choices. 1) Do nothing and wait for Debian/Ubuntu to upgrade the package and backport it. 2) Try upgrading Postorius from source or with pip. This will probably result in disaster, and even if it doesn't, will probably also require upgrading django-mailman3, mailmanclient and mailman core to support new features in Postorius. 3) See the merge requests at <https://gitlab.com/mailman/postorius/-/merge_requests/349>, and if you have >50 lists, <https://gitlab.com/mailman/postorius/-/merge_requests/437> and try patching installing those changes as patches. Note that!349 patches 15 files, but one of them is the change log and 12 are related to tests. The only ones you need to patch are postorius/templates/postorius/index.html and postorius/views/list.py. Likewise, these two are all you need from !437. 4) Abandon the Debian/Ubunto package and install the whole suite from source or with pip. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Question about adding addresses using the REST API

by Mark Sapiro

On 1/15/22 10:03 AM, Stephen Daniel wrote: > > The only way I've found to create a standalone address (not linked to any > user) is to create a user with that address, unlink the address, then > delete the user. > > Is there a more straightforward way to just create an address with no user? The more straightforward way is via the IUserManager create_address method. This method is not exposed directly in REST, so you can't do it via REST. My question is why do you want to? Granted when an unknown nonmember address posts to a list we create a standalone address record, but maybe we should be creating a user too. We don't because it's tricky. Suppose User A with address A posts to a list from nonmember address B. We create the standalone address B record as a nonmember, but now user A can add address B as another address. If we also created User B, this would not be possible. But again, what is your use case for creating standalone addresses? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: How to fix lists with characters errors?

by Mark Sapiro

On 3/22/24 05:37, Helio Loureiro wrote: > Hi, > > I just found several lists have the issue like this regarding charset: > > (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members ... > Traceback (most recent call last): ... > line 109, in display_members > print(f'{address.display_name} <{address.original_email}>', > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > position 9: ordinal not in range(256) There is something in your python that has set the encoding for stdout to latin1 instead of the default utf-8. E.g. ``` $ python3.10 Python 3.10.9 (main, Dec 11 2022, 12:59:24) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> name = 'abc\u0142def' >>> print (f'{name}') abcłdef >>> import sys >>> sys.stdout.reconfigure(encoding='latin1') >>> print (f'{name}') Traceback (most recent call last): File "<stdin>", line 1, in <module> UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in position 3: ordinal not in range(256) >>> ``` -- 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

[MM3-users] Re: Upgrade to 3.3.2 fails

by Mark Sapiro

On 12/27/20 12:12 AM, Torge Riedel wrote: > > Nice to hear, but I fear you could be hit by this issues again, > depending on changes in the future on the table. Either when more > columns are added or on runtime when rows are added / updated. It seems that is a possibility with MySQL. It may not be an issue with MariaDB. It isn't completely clear to me from <https://mariadb.com/kb/en/innodb-limitations/#limitations-on-size>, but it seems that VARBINARY, VARCHAR, BLOB and TEXT columns are only counted as a few bytes in the "roughly half the page size" calculation. > @Mark: Would it be a good approach to split the table 'mailinglist'? I > see some groups of columns like "bounce_*" or "dmarc_*" which could be > managed in separate tables. Currently, those list attributes which are stored in tables separate from the mailinglist table are (some of) those that have lists of values rather than a simple value, but it would certainly be possible to separate groups of related attributes into separate tables. Care to submit a merge request? -- 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: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 04:35, Thomas Stein wrote: > > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE This is a packaging issue in the Debian/Ubuntu package and should be reported to Debian. See the BREAKING CHANGE item in the 1.3.10 section at <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. You need to add `allauth.account.middleware.AccountMiddleware` to the MIDDLEWARE setting in your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > Is nntp common enough these days to be a useful default runner? > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > resources (yet another Python interpreter running) for a fairly edge > case of mailing list <--> nntp transits. You raise an interesting point. By default, the runner runs, but if there are no lists gating to usenet, its queue is always empty and it mostly sleeps between waking, finding its queue empty and going back to sleep. A more significant use of resources is every (default) 5 minutes spawning `mailman gatenews` which goes through a startup process and then looks at every list figuring out there's nothing to do. We could default mailman.cfg to contain `start: no` in the runner.nntp section so people would need to enable it if they wanted it. What do others think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/9/19 11:16 AM, kelly.close(a)lrewater.com wrote: > I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. > > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… Thank you for this. I'm sure it will be helpful. One caveat. The Mailman 3 package for Ubuntu 18.04 is core version 3.1.1. This version when used with the MySQL back end database can have a serious issue. It doesn't affect the PostgreSQL back end database, only MySQL and maybe MariaDB, and it is fixed in Mailan core 3.2.0. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Search results for query "sapiro"