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

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/25/21 5:18 AM, Marco Marinello wrote: > Finally have found my issue... Apache automatically removes the header, see https://stackoverflow.com/questions/26549250/apache-strips-down-authorizati… . Hope it can be useful for somebody else! I'm glad you found this, but I'm a bit confused. I run a few servers with apache 2.4 proxying to gunicorn and I don't see the issue. Perhaps this is a uWSGI or mod_wsgi issue. In any case, it can possibly be avoided by setting base_url in mailman-hyperkitty.cfg to something like base_url: https://127.0.0.1:8000/archives or whatever localhost port the WSGI application is listening on to bypass apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/16/21 10:35 AM, dancab(a)caltech.edu wrote: > Mark, > > I updated mailman.cfg to point at our shared EFS mount. > > cache_dir: /mnt/var-mailman3/cache > > But I'm still getting reports of this issue. Is there somewhere else I need to set that location? If your layout is other than fhs, I would set var_dir: /mnt/var-mailman3/ For fhs layout, I would ensure that at a minimum, /var/lib/mailman, /var/spool/mailman and /var/lock/mailman are all shared. However for your issue with shared cache, you need to wait 7 days for all the old cache entries to expire or do getUtility(ICacheManager).clear() in `mailman shell` to clear the cache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Database permission problem?

by Mark Sapiro

On 10/15/24 15:03, Bill Oliver wrote: > > I'll also add that the instructions get a little hazy when you get to > the "Unusual Postfix configuration" part, which is me, with multiple > virtual domains, virtual mailboxes, and use dovecot. > > For instance, it's not clear to me in the "Unusual Postfix > configuration" when you should use > > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} > > versus > > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp I don't know anything about postfix configurations for dovecot delivery. I've only used dovecot for sasl authentication. In any case, dovecot delivery should not be involved in delivery to Mailman. -- 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: Python backtrace from `mailman -h`

by Mark Sapiro

On 8/24/25 17:03, Peter Chubb via Mailman-users wrote: > Hi Folks, > I'm running the Debian-packaged mailman3 (yes I know ...) > and running: > sudo -u list mailman -h > gives a python backtrace (which I've appended the tail end of). > Can someone who has the upstream installed version (using venv) > please check that `mailman -h` works there before I waste too much time > investigating in the wrong places? Yes, `mailman -h` works and produces the same help output and list of subcommands as `mailman` with no arguments or options. Does it work with no options? Does it work if you do `mailman -C path/to/mailman.cfg -h`? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: MM3 Docker

by Mark Sapiro

On 1/6/19 6:54 AM, Odhiambo Washington wrote: > > If I could run MM3 using the apt-get install method, perhaps that would > have made my life a bit easier, hoping that MM3 can actually be run in > parallel with MM2.1 on the same host. Is anyone doing that already?? Yes. I am on two production and one development machines. See, e.g. <https://mail.python.org/mailman/listinfo/> and <https://mail.python.org/mailman3/> One caveat here is I install both Mailman 2.1 and Mailman 3 from source on all these machines. I don't know for example if the Debian/Ubuntu packages play well together. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> for more on how I install MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Affinity Mailman Is Now Beta

by Mark Sapiro

On 6/18/20 12:44 PM, Brian Carpenter wrote: > Dear Mailman Admins and Users, > > Affinity Mailman is our new admin interface for Mailman 3 and we intend > to use it to replace Postorius. It has been under development for about > 3 months now and it recently reached beta. Just to be clear, Brian has the full support of the GNU Mailman project in his endeavor to create a new web UI for Mailman 3, but "our" above means Brian and EMWD, not the GNU Mailman project. We of the GNU Mailman project are delighted that Brian is working on an alternative web UI, but we have no plan to abandon Postorius and HyperKitty. -- 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: Using external services for deliverability?

by Mark Sapiro

Mark Sapiro wrote: > On 7/10/20 8:10 PM, tom(a)gather.coop wrote: > > Makes sense. So given that the opendkim milter > > matches on the From header, am I correct in telling opendkim to sign emails from > > any email address with my domain? > > So my whole SigningTable might be something like > > > > * mail._domainkey.mydomain.com > > > > Yes. Actually, I knew there was more to it than that, but I had forgotten the detail. You can have *(a)mydomain.com mail._domainkey.mydomain.com as your SigningTable entry, but you need to specify SenderHeaders List-Post,Sender,From in your opendkim.conf. This will find the list address in the List-Post header of mail from your lists and that will be list(a)mydomain.com which will match the above SigningTable entry.

5 years, 9 months

[MM3-users] Re: Make archives private by default

by Mark Sapiro

On 1/8/23 06:40, Johannes Rohr wrote: > Dear all, > > in mailman2 there was a setting that ensured that the archives of newly > created lists are by default privat ( > > DEFAULT_ARCHIVE_PRIVATE = 1 > > > Is there something similar in Mailman3? Set [styles] default: private-default in mailman.cfg. There are other effects to this style. namely, in addition to setting archives to private, it also sets the subscription policy to confirm then moderate and sets the list unadvertised. If you want a style that's like ordinary discussion list style except with private archives, but advertised and subscription policy = confirm, you'd need to create a plugin with your own style. -- 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: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/28/23 11:48, Stephen J. Turnbull wrote: > Odhiambo Washington writes: > > > from mailman_web.settings.base import * > > from mailman_web.settings.mailman import * > > I think just putting these as close to the top as possible, and > including a comment (or two) saying that this is importing defaults > that can be overridden by any assignment made later in the file is > about as far as we can go for explaining. I've Just updated this. It now says: ``` # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * # Settings below supplement or override the defaults. ``` -- 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: Python is updated

by Mark Sapiro

On 4/29/23 01:44, Odhiambo Washington wrote: > On Sat, Apr 29, 2023 at 8:25 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > >> So you have settings.py in /opt/mailman/mm rather than in /etc/mailman3? >> > > That's right - based on an earlier installation method before the official > virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > one was put together, and that's why he has that shell file. > For a virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > setup, your settings should live in /etc/mailman3 as stated. If you are interested in background on prior installation methods and their evolution, see https://wiki.list.org/x/17891998 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Search results for query "sapiro"