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

[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, 1 month

[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, 9 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, 8 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, 4 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, 3 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, 7 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, 5 months

[MM3-users] Re: Add an extra option for "Delivery status" for users?

by Mark Sapiro

On 11/19/25 12:50 PM, Thomas Ward via Mailman-users wrote: > > We have a unique case where we have a user we want to disable for mail > receiving, etc. for the reason "Disabled by IT Security Team" but I > don't even know if it's possible to add a delivery status that is that > custom. At a minimum, you would need to add that choice to the DeliveryStatus(Enum) in mailman/interfaces/member.py and the choice and its description to the DELIVERY_STATUS_CHOICES tuples in postorius/forms/fields.py. I don't know offhand if that would be sufficient, or if more would be required. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/6/24 14:27, Mark Sapiro wrote: > > Is this with only one browser? It's a long shot, but clearing browser > cache might work. Actually, I see the same issues from my browsers, so it's not a browser caching issue. The only thing left is nginx caching, but, while I know very little about nginx, I think it doesn't cache by default and I don't see where in your posted config it's enabled. Perhaps there's more in your config that you didn't post. If there is a proxy_cache_path directive in your config try find /the/proxy/cache/path -type f -delete to clear the cache. As a last resort, your /opt/mailman/mm/static/CACHE/ directory should contain a css/ directory with 3 files and a js directory containing one file and a manifest.json file with a template for the `link` directives referencing those files. The js/ directory is easy as its only one file, so your server is looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create a symlink in the js/ directory from output.3aaa7705d68a.js to the actual file. For the css directory, your server is looking for output.158acc288604.css and output.6dab123e4897.css, and I don't see the third file in the logs you posted, but if I go to pages in your archive that I see as unstyled and look at the stylesheet references, they are to output.44ea6c55e917.css, output.e68c4908b3de.css and output.9efeb5f3d52b.css so you could just symlink those to the actual files, it doesn't matter which as all three are loaded on each page. -- 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: Auth question

by Mark Sapiro

On 1/3/19 11:00 AM, kelly.close(a)lrewater.com wrote: > Hi David, > > Did you ever find a resolution to these Authorization errors? I'm experiencing the same problem in a new setup. Would love to know if you figured it out! The code that produces that error is: if request.GET.get("key") != settings.MAILMAN_ARCHIVER_KEY: return HttpResponse( """<html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html>""", content_type="text/html", status=401) I.e., the key in the request which comes from the [general] api_key: setting doesn't match the key set as MAILMAN_ARCHIVER_KEY. Do you have quotes around the api_key setting? That would be a mistake. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

Search results for query "sapiro"