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

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 12:05 PM, Brian Carpenter wrote: > On one of my mailman 3 servers, I am having a problem with Postfix > failing to deliver email to Mailman. I keep seeing this in the mail.log: > > status=deferred (connect to 127.0.0.1[127.0.0.1]:8024: Connection refused) > > What is causing this and how can I fix it? > Do you have lmtp_host: 127.0.0.1 lmtp_port: 8024 in the [mta] section of mailman.cfg? (these are the defaults) $ /opt/mailman/mm/bin/mailman conf|grep lmtp [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 Is Mailman's lmtp runner listening on port 8024? $ sudo netstat -lntp|grep python tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 1867/python tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 1199/python tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 1871/python Is there some firewall issue blocking access to the port even from localhost? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Moderation Action Changed After Import

by Mark Sapiro

On 2/12/21 11:26 AM, Brian Carpenter wrote: > I migrated a Mailman 2 list using import21 and the list's config.pck > into a Mailman 3 list. The list owner reported back that about 98% of > the list members had their moderation setting changed to Reject (with > notification). He said the previous moderation was the list's default > which was hold for moderation. Is such a thing possible with an import > job? Is this perhaps a bug that has been reported previously? > It seems you imported to an existing list with import21. This is probably not a good idea. Those members who were moderated members of the MM 2.1 list will have their moderation action set to Hold, Reject or Discard based on the 2.1 list setting. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: remove non members from a list

by Mark Sapiro

On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to remove all non members from a list. I know I can do it via > Postorius, but it has to be done one at a time. (you can delete ALL > suscribers but not all non members...) > > Anyone has a python recipe to do this? $ /opt/mailman/mm/bin/mailman shell -l list.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 >>> for nonmember in m.members.nonmembers: ... nonmember.unsubscribe() ... >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Updating installed pkgs in MM3 venv

by Mark Sapiro

On 10/15/22 03:39, Odhiambo Washington wrote: > What is the recommended way for updating installed the installed pkgs in > MM3 venv - to ensure that nothing breaks? Upgrading to what? To upgrade from PyPI you can do ``` pip install --upgrade xxx ``` for all the mailman packages where xxx is the package name. However, this may create an issue with Hyperkitty because of https://gitlab.com/mailman/hyperkitty/-/issues/431 To update from the heads of the GitLab branches, the commands would be ``` pip install --upgrade git+https://gitlab.com/mailman/xxx@master ``` With either of the above, it may be necessary to add the `--force-reinstall` option to `pip install`. See this post https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/23/24 05:49, Marco van Tol wrote: > > Small unfortunate twist, this leads to: > > --- > [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... > --- > > I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. I use the one from the PR, but it requires a substitution `s/force_text/str/`. -- 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: Strange URL in error message

by Mark Sapiro

On 7/14/24 11:16 AM, waps(a)tantalus.jena.thur.de wrote: > Hi Mark, on the entire server there is no string "demailman3". The base_url looks good: > > # grep -v ^# /etc/mailman3/mailman-hyperkitty.cfg > [general] > base_url: http://www.XXXXX-project.de/mailman3/hyperkitty/ > […] > > Where should I search at first, if the archive remains empty? Mailman core can't communicate with HyperKitty. Thus all the messages to be archived are saved in Mailman's var/archives/hyperkitty/spool/ directory. When the underlying issue is fixed, mailman-hyperkitty will process and archive those messages. Can you go to http://www.XXXXX-project.de/mailman3/hyperkitty/api in a browser and get a REST API documentation page. If that redirects to https, change the scheme in the base_url setting to https and restart Mailman. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/14/24 10:10, jkoral(a)luc.edu wrote: > I understand that now. I was able to delete it, re-create it and am now getting e-mails into the server. But now, it is not sending out to the e-mails that are subscribed to that list. > > Will running mailman aliases fix that? Also, I don't see a mailman command, but am running mailman3 aliases. Does this process take while? It has been running for a couple minutes now. No. `mailman aliases` will not affect delivery from Mailman to list members. `mailman aliases` should be almost instantaneous. How did you install Mailman? If you followed our recommendations at https://docs.mailman3.org/en/latest/install/virtualenv.html there is no `mailman3` command. -- 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: Auto discard after max_days_to_hold not working.

by Mark Sapiro

On 4/28/25 07:59, Stephen J. Turnbull wrote: > > This doesn't seem to be exposed in Postorius. It's not all that old > in Mailman 3 (April 2020) so it's possible that it is not moved from > Mailman 2 to Mailman 3 by the migration scripts. This is comments in postorius/forms/list_forms.py ``` # TODO: Expose after this functionality actually works in Core. # max_days_to_hold = forms.IntegerField( # min_value=0, # label=_('Discard held posts after'), # required=False, # help_text=_( # 'No. of days after which held messages will be automatically' # ' discarded.')) ``` `mailman import21` will import the setting, but per the above comment, it doesn't yet work. The setting exists and is exposed in REST, but it appears it is not actually implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Delete User

by Mark Sapiro

On 05/25/2018 03:14 PM, Kaleb White wrote: > Where exactly is the Django admin interface? > > I can't find it. It's not this, is it? > https://lists.mailman3.org/user-profile/ If you're looking for it on lists.mailman3.org it's at <https://lists.mailman3.org/admin> but you won't be able to log in there. In another installation you would look in urls.py for the list of urlpatterns for something like # Django admin url(r'^admin/', admin.site.urls), If you are authorized to create domains, on the Add a new domain page, the description of Web Host says in part "This can be same or different from the Mail Host. You can edit the list of available web hosts here." and 'here' is a link into the admin interface. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Removing banned emails

by Mark Sapiro

On 08/02/2018 11:47 AM, Kaleb White wrote: > I am trying to remove a banned email with a special character via the rest api and it's not working. It's also not working via the UI. Any ideas? > http://localhost:8001/3.0/lists/example.com/bans/provisor#41@bankofamerica.… > <Response [404]> You can't do it from Postorius (This should be considered a bug in Postorius or perhaps mailman-client). You can do it via rest if you URL encode the request as http://localhost:8001/3.0/lists/example.com/bans/provisor%2341@bankofameric… The issue is whatever client is making the HTTP request is considering '#41(a)bankofamerica.com' to be a fragment identifier so it issues the request for the resource '3.0/lists/example.com/bans/provisor' and expects to find sub-resource identified by '41(a)bankofamerica.com' in the response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

Search results for query "sapiro"