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

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 9/29/23 08:52, paulrubin37(a)gmail.com wrote: > Does this make any sense to you? > > ERROR: Could not find a version that satisfies the requirement flufl.bounce (from versions: none) > ERROR: No matching distribution found for flufl.bounce was that in response to ``` pip install -U --force-reinstall flufl.bounce flufl.i18n flufl.lock ``` If so, I don't understand. https://pypi.org/project/flufl.bounce/ https://pypi.org/project/flufl.i18n/ and https://pypi.org/project/flufl.lock/ all exist. However, I now suspect the issue is somewhat different. See https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929 although that refers to $VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt and in your case, that might instead be $VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.dist-info/METADATA -- 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

[MM3-users] Re: Removing Moderators

by Mark Sapiro

On 7/20/24 1:27 PM, steve.bachinsky(a)tena-sda.org wrote: > > If I know the moderator's email address, is there a way to do this in a python function? Something like ``` import os import sys from mailman.core import initialize from mailman.database.transaction import transaction from mailman.interfaces.listmanager import IListManager from zope.component import getUtility os.environ['MAILMAN_CONFIG_FILE'] = '/path/to/mailman.cfg' initialize.initialize() def delete_moderator(list_id, email): mlist = getUtility(IListManager).get_by_list_id(list_id) if not mlist: print(f'No such list {list_id}', file = sys.stderr) sys.exit(1) with transaction(): moderator = mlist.moderators.get_member(email) if moderator: moderator.unsubscribe() else: print(f'No such moderator {email}', file = sys.stderr) sys.exit(1) if __name__ == '__main__': delete_moderator('list.example.comg', 'user(a)example.com') ``` -- 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: External MTA incoming mail: configuration

by Mark Sapiro

On 8/2/24 08:12, Roland Giesler via Mailman-users wrote: > > It seems though that since I'm not running a local MTA, when then mail > arrives at the mailman3 server, there's nothing that can process it. So > should I run postfix in it's most basic setup to allow mail to be > received or what is the best way to deal with it? Mailman3 has to > receive mail like signup confirmations, etc after all, not? If you use transport_maps on the remote MTA to relay the list mail to port 8024 on the Mailman server, Mailman's LMTP runner will receive the mail and you don't need a local MTA. -- 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: digests are created but not sent out

by Mark Sapiro

On 1/9/19 12:53 PM, "Jörg M. Schulz" wrote: > To make it work, I have to comment out like this: > > Also only commenting out the .de section doesn’t help > > > # The default language for this server. > default_language: en > # [language.en] > # charset: utf-8 > # enabled: yes > > # [language.de] > # description: German > # charset: iso-8859-1 > # enabled: yes First, everything there should be a default, at least upstream, with the one exception of [language.en] charset: utf-8 I confess, I don't understand this, but please see <https://wiki.list.org/x/12812344>, and if you want to pursue it, report the issue to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Mailman3 command line issue: NameError: name 'cli' is not defined when executing command=cli

by Mark Sapiro

On 5/13/20 7:10 AM, John W wrote: > Hi, I am following the guide here: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/create.h… > and am falling at the first hurdle. > > command = cli('mailman.commands.cli_lists.create') > NameError: name 'cli' is not defined. In order to run the doctest snippets, you need to import the helpers. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…>. However, If all you want to do is create a list just run the `mailman create` command directly instead of trying to run the snippets in `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: New releases

by Danil Smirnov

The issue has confirmed by other users: https://github.com/maxking/docker-mailman/issues/382 вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >>> COMPRESS_OFFLINE = True > >>> COMPRESS_ENABLED = True > >> > > > > These two are commented out. > > > Then compress shouldn't be trying to do anything. I can't explain what's > going on. > > -- > 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/ >

5 years, 10 months

[MM3-users] Re: Problems after Upgrade

by Mark Sapiro

On 10/30/22 17:37, Jeff Steele wrote: > Thanks Mark, > > I was able to fix this problem easily by modifying: > > mailman3/lib/python3.8/site-packages/compressor/management/commands/compress.py > > to change the line: > > Command.requires_system_checks = None > > to > > Command.requires_system_checks = [] > > Now, bin/mailman-web compress runs but outputs: > > CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. > > which I guess is fine. If you want to do off line compression which is a good thing, you need to set ``` COMPRESS_ENABLED = True ``` in your Django settings. I recently added this and also a note about CSRF_TRUSTED_ORIGINS to https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > also belongs to the core, doesn't it? In any case, I changed the > configuration parameter for [archiver.hyperkitty] as you suggested and > all settings are in one place now. In that case, it's probably just an oversight. The instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html are an evolution of a process that started with an obsolete mailman-bundler package, the initial iterations of which are documented at https://wiki.list.org/x/17891998 and prior revisions of that page. https://docs.mailman3.org/en/latest/install/virtualenv.html is still a work in progress. -- 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: using SSH/TLS with external MTA

by Mark Sapiro

On 7/27/24 13:05, Odhiambo Washington via Mailman-users wrote: > > ASMTP works on the premise of "we can relay mail for you if we can > authenticate you with certain credentials" > Adding the IP to "hosts we can relay mail for" negates the need to > authenticate, IMHO. > So I am still waiting for how MM3 does ASMTP. Does it? If by ASMTP, you mean SMTP AUTH, Mailman does it if smtp_user: and smtp_pass: are provided in mailman.cfg. I agree that an authenticated user should be able to submit mail to be relayed. Just guessing here, but perhaps the issue is the OP is submitting to the deprecated port 465 instead of 587. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 9/30/24 12:15, jkoral(a)luc.edu wrote: > We have figured out how to migrate from one server to another, but after removing the list from the old server, the e-mails are still trying to go there. Is there something that needs to be done in mailman so that the e-mail list will hit the new server instead? Does it just take time? This is a DNS issue. You need to update the MX and/or A records for the domain to point to the new server. After that is done, it still takes time for those changes to propagate depending on the TTL of the original records. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Search results for query "sapiro"