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

[MM3-users] Fwd: Re: Re: How to upgrade to 3.10

by Paul Tomblin

On Sun, Mar 8, 2026, at 10:56 PM, Mark Sapiro wrote: > > Actually I think the issue is because of the version not being bumped When I did pip with a file path, it looks like it did uninstall and reinstall Building wheels for collected packages: postorius Building wheel for postorius (pyproject.toml) ... done Created wheel for postorius: filename=postorius-1.3.13-py3-none-any.whl size=3844417 sha256=b0ca99e0c77a2fd3a7460a38d5e917855170432610e123f6cbe03f1ab054888d Stored in directory: /tmp/pip-ephem-wheel-cache-nz_847ds/wheels/58/f2/fa/13dfd8d8589c1b34506c170121d1cc3ab9245e2a684d0be026 Successfully built postorius Installing collected packages: postorius Attempting uninstall: postorius Found existing installation: postorius 1.3.13 Uninstalling postorius-1.3.13: Successfully uninstalled postorius-1.3.13 Successfully installed postorius-1.3.13 Looks like I've got base_url working! Thanks very much. As a feature request, could we get the unsubscribe email address as a template variable? Maybe I should dust off my python skills and submit a pull request. Do I need a gitlab account to do that? -- Paul Tomblin

7 months, 1 week

[MM3-users] Re: Cannot setup announce-only mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/1/20 9:53 AM, Abhilash Raj wrote: > > Mark, do you think we should make the actual announce-only style reflect > > these settings so folks don't have to manually set these after they create > > a announce-only list? > > > > I am not sure the reason behind these settings lacking for the current > > announce-only style. Are there situations where announce-only list would > > have different list setting? > > I think it was probably done as it is just as a start. I do think it > would be good to set more things appropriately for the announce-only > style, ultimately we may need to add templates for post rejection > notices and things like that. If this involves a fair amount of coding maybe it could be a suggested GSoC task? Steve

6 years, 8 months

[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 '^$|^.*#' :-)

5 years

[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, 8 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/ >

8 years

[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

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

1 year, 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, 10 months

Search results for query "sapiro"