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

[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.

6 years, 1 month

[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, 7 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, 6 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, 3 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Mark Sapiro

On May 24, 2023 9:45:45 AM PDT, Quanah Gibson-Mount <quanah(a)fast-mail.org> wrote: >That shell script seems to have errors: > >>>> pendings = getUtility(IPendings) >>>> for token, data in pendings.find( >... token_owner=TokenOwner.subscriber, >... pend_type='subscription'): >... print("hello") >... >Traceback (most recent call last): > File "<console>", line 3, in <module> > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) >TypeError: find() got an unexpected keyword argument 'token_owner' Your Mailman core is too old for that script. Tell me your core version and I will try to make one that works for you. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

3 years, 2 months

[MM3-users] Re: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/29/23 10:45, mrl(a)psfc.mit.edu wrote: > Thanks. Although IMHO I would prefer that the display show the actual action, and adding with a red asterisk to denote that it's the list default. It's a somewhat simple fix, although I've omitted the asterisk, because it's not important to me that it's the list default. Something like: I plan no further changes beyond <https://gitlab.com/mailman/postorius/-/merge_requests/811>, but if you were to submit a merge request, we'd consider it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Postorius admin/user guide

by Mark Sapiro

On 11/8/24 02:59, Florin Pasăre via Mailman-users wrote: > Hello, > We're trying to update mailman to version 3 from version 2, and I can't > seem to find some non-technical guide for Postorius, something like an > owners manual for all the configurations available in Postorius. > Is there such a thing? No, at this time there is not. All we have at the moment is https://docs.mailman3.org/projects/postorius/en/latest/ which isn't what you're looking for. You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- 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: Issues with Mail delivery after Mailman 3 installation

by Mark Sapiro

On 1/31/26 13:11, Ibiam Chihurumnaya via Mailman-users wrote: > I finished installing mailman3, setup lmtp and smtp for mail delivery and I followed the instructions on the mailman 3 installation page. > > Mail delivery doesn't work and the logs show this; ... > Jan 31 12:53:54 lists postfix/lmtp[4128841]: connect to localhost[::1]:24: Connection refused > Jan 31 12:53:54 lists postfix/lmtp[4128840]: connect to localhost[::1]:24: Connection refused ... Your /etc/hosts file has an IPv6 address for localhost and Postfix isn't listening for IPv6 connects Either set the `localhost` IP in /etc/hosts to IPv4 as 127.0.0.1 localhost or set inet_interfaces = all inet_protocols = all in Postfix main.cf -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: "Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'

by Mark Sapiro

On 05/28/2017 06:07 AM, Simon Liebold via Mailman-users wrote: > Is deleting threads from the archive (via Hyperkitty) currently > supported? I am getting the error indicated above if I click on "Delete > this thread". I just tested this on another list on this server. and both 'delete message' and 'delete thread' worked for me with the latest release Hyperkitty 1.1.0, django_mailman3 1.1.0 and Django-1.10.7. Did you get to the confirmation page and then get the 500 or did the 500 come before getting the confirmation page? Is there a full traceback in mailman_web.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: MM3 & postfix ... (mail loops back to myself)

by Mark Sapiro

On 01/18/2018 02:25 PM, Dmitry Makovey wrote: > > transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains The initial implementation of Mailman's regexp maps for Postfix was broken. This was fixed by <https://gitlab.com/mailman/mailman/merge_requests/323>. The bottom line is if /opt/mailman/core/var/data/postfix_lmtp contains entries like /^foo-bounces(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 /^foo-confirm(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 these entries (only the -confirm and -bounces, not the others) need to be /^foo-bounces(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 /^foo-confirm(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 because Postfix recipient_delimiter = + is not effective for regexp tables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Search results for query "sapiro"