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

[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

2 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

2 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

9 months, 2 weeks

[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

7 months, 2 weeks

[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

6 years, 4 months

[MM3-users] Re: What is the recommended format for mailbox interchange as files?

by Mark Sapiro

On 6/21/19 10:05 PM, Andrew Bernard wrote: > > This issue could very well go in an FAQ for mailman. Can I add a topic > somehow? Many others will hit the same problem. There is a FAQ article at <https://wiki.list.org/x/4030689>. If you wish to edit that or create a new article, see the first paragraph at <https://wiki.list.org/> about obtaining write permission. There is also some documentation of hyperkitty_import at <https://hyperkitty.readthedocs.io/en/latest/install.html#importing-the-curr…>, the source for which is at <https://gitlab.com/mailman/hyperkitty/blob/master/doc/database.rst>. You could create a merge request to update that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 1/3/20 7:55 AM, brunol(a)agro.uba.ar wrote: > I've found something, the imported list preferred language is Spanish (es), changing it to 'en' : ... > seems to fix everything, as soon as i hit ctrl+d the messages are delivered properly. > > Even when i set it to french which has the same charset as spanish it works as expected. Any ideas why? Actually, since Mailman 3.2.1, the default charset for 'fr' is utf-8, not iso-8859-1, although I don't offhand understand why the language would affect this even if the encoding is different. In any case, at this level the message should be pure ascii with any non-ascii having been base64 or quoted_printable encoded. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Mailman web Stopped working after upgrade

by Mark Sapiro

On 3/3/20 12:33 PM, David Krantz wrote: > > I think that this might be due to some kind of python misfeature where > compiled code behaves slightly differently to interpreted code, that > might explain the delay in it working initially before breaking. I > have no idea of how to solve this. I have tried to uninstall and > reinstlall psycopg2 in different versions without any luck. You need to activate your virtualenv and do pip install psycopg2-binary it must be psycopg2-binary, not just psycopg2. It's probably best to do pip uninstall psycopg2 first. As far as it working for a while, did you restart your wsgi service (gunicorn, uwsgi, ??) after upgrading? -- 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: migration plan and auto responder

by Mohsen Masoudfar

Thank you so much Mark! It worked perfectly. Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, July 21, 2020 6:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: migration plan and auto responder [EXTERNAL EMAIL] On 7/21/20 3:13 PM, Mark Sapiro wrote: > > You probably also want to set Privacy options... -> Sender filters -> > member_moderation_action to Discard and on Membership Management... -> > Membership List under Additional Member Tasks, set everyone moderated. I answered a bit too quickly. Just s/probably/definitely/ in the above. This works because the autoresponses are sent before the moderation checks. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 9 months

[MM3-users] Re: [SOLVED] Re: Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/27/21 4:05 PM, William Oliver wrote: > > Again, a quick DuckDuckGo search reveals that this has come up a couple > of times. It required that I modify /etc/postfix/main.cf to add the > non-localhost ip4 address of the box to the mynetworks line: > > mynetworks = 127.0.0.0/8 10.0.0.0/24 > > to > > mynetworks = 127.0.0.0/8 10.0.0.0/24 2.56.57.28 > > > I assume that means that postfix uses localhost for regular mail, but > mailman3 uses the 2.56.57.28 address. Because you set smtp_host: mail.libertyfp.org in mailman.cfg. If you leave the default settings smtp_host: localhost smtp_port: 25 you won't have this issue. -- 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

Search results for query "sapiro"