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

[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

3 years, 5 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

7 months

[MM3-users] Re: Confirmation for subscriptions

by Mark Sapiro

On 6/23/19 7:28 PM, Mark Sapiro wrote: > On 6/23/19 7:11 PM, andrew.bernard(a)gmail.com wrote: >> I have had some trouble with uwsgi, now resolved. Not that there may be any connection, but now, email requests to join are sent a confirmation mail, but the webui just signs you up with no confirmation despite having the subscription policy set to Confirm, and the right code in the database table underneath. > > > Is this a web subscribe for a logged in user or and "anonymous > subscribe" for a non-logged in user or both? I have done some further investigation. With subscribe policy 'confirm': A person without an account can subscribe to a list anonymously. The person is sent an email requesting confirmation of her address and intent to subscribe. Replying to the email confirms the address and subscribes it. A person can sign up for an account with an email address. This results in an email request to the address with a link to confirm it. Following the link and confirming the address then creates the account with the confirmed address. Subsequently, the user can log in and subscribe to the list without further confirmation because the user has already confirmed the address and has logged in, so further confirmation is not required. If subscribe policy is 'moderate', both of the above cases send the request to the moderator for approval. I think this behavior, particularly allowing a logged in user with a confirmed address to subscribe without further confirmation, is reasonable. Is this what you see, or are you seeing something else. -- 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: Emailing a list from the list server

by Mark Sapiro

On 6/1/20 11:56 AM, Mark Dadgar wrote: > On Jun 1, 2020, at 11:45 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> What's in Postfix's mail.log? > > > Jun 1 11:54:55 mail postfix/lmtp[238922]: 1F42613BEB5: to=<test3(a)pdc-racing.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.02/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) OK. It was delivered to Mailman's LMTP runner which presumably accepted it and queued it because that's the only case in which it returns '250' You could set [logging.smtp] level: debug in mailman.cfg to get more logging, but I think that that will just add confirmation of what we already know, i.e., it was queued in the in queue. So that leaves us with: some error in processing shunting the message. In that case the error would be logged in mailman.log and the message would be in var/queue/shunt. or some rule discarding the message. In that case, there should be a DISCARD: <message-id> entry in mailman.log. If that's the case, we still don't know which rule did the discard and why. One thing you might consider is the possibility that you've missed some message because it was delivered to a local mailbox rather than where you expect it. In my case, msapiro.net has an MX record pointing to my real mail server, but it is also the host name of my development box so mail generated on that box for me winds up in /var/mail/mark instead of being delivered to my real mail server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 02:30, MegaBrutal via Mailman-users wrote: > On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > >> so it is saying there is only one choice for sender which I think means >> there is only one address associated with your login. That still doesn't >> explain why it thinks you're not a list member. >> > > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries > you recommend to run to get to see what's happening under the hood? Not offhand. What is the exact email address that you are logging on to the web UI with. Does it match exactly with the address of a list member or are there mixed-case differences? You might try an interaction like this: ``` mailman-web shell Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_mailman3.lib.mailman import get_mailman_client >>> client = get_mailman_client() >>> list_id = 'test.example.com' # your actual list_id >>> rest_list = client.get_list(list_id) >>> email = 'user(a)example.com' # your actual email >>> member = rest_list.get_member(email) >>> member This should print something like <Member 'user(a)example.com' on 'test.example.com' with role 'member'> ``` This is exactly what HyperKitty is doing except in your case rest_list.get_member(email) is throwing a ValueError exception instead of returning the member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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

6 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

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

4 years, 10 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

2 years, 4 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

2 years, 3 months

Search results for query "sapiro"