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

[MM3-users] Re: Change Member's Address

by Mark Sapiro

On January 15, 2026 9:00:52 AM PST, dap1--- via Mailman-users <mailman-users(a)mailman3.org> wrote: >I think we can wrap this up. Magically the original superuser is now showing confirmed and seems to work. The only remaining issue is the from header showing up as lllllllll.bounces rather than just llllllll. What is the exact From: header? Does your mailman/handlers/dmarc.py look like <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc…>? -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

7 months

[MM3-users] Re: Domain defaults for new lists

by Mark Sapiro

On 1/29/26 15:43, Peter Chubb via Mailman-users wrote: > > Thanks Mark --- how do I make that the default though? in the [styles] section in mailman.cfg set default: private-default -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Phantom Email Address in Nonmember List

by Mark Sapiro

On 1/31/26 15:13, Steve Brown via Mailman-users wrote: > The good news is that I now know what "grepping" is. Am I correct that I cannot do that as a mere list manager and not a Mailman3 platform operator with Linux? One needs shell access to the server and permission to read log files. -- 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: Permissions Error on /var/mail/mailman

by Mark Sapiro

On 2/3/26 11:47, dap1--- via Mailman-users wrote: > > I assume you meant sudo chown mailman /var/mail/mailman. Yes, That's what I meant. After you do that, any further such messages should be delivered to that mbox where you can see what they are. -- 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: Issues with Mail delivery after Mailman 3 installation

by Mark Sapiro

On 2/4/26 02:21, Chihurumnaya Ibiam via Mailman-users wrote: > > You're right about "localhost" causing confusion, I switched to using the > IP address instead, the logs > showed that Mailman tried to connect on [::1] and there wasn't a response, > that might be from Mailman itself though as the > port is open. > > I don't have a preference for IPv6. Edit /etc/hosts and change the `localhost` entry from ::1 to 127.0.0.1 -- 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: Mailman and Postfix Conflicting Information

by Mark Sapiro

On 2/6/26 10:06, dap1--- via Mailman-users wrote: > Yes, I see this: > > 2026-02-06T10:33:49.632822-05:00 dap002 postfix/lmtp[185616]: 7304C500071: to=<lllllllll(a)gmail.com>, relay=127.0.0.1[12 > 7.0.0.1]:8024, delay=0.17, delays=0.09/0.02/0/0.06, dsn=2.0.0, status=sent (250 Ok) So the mail is delivered to Mailman's lmtp runner as it should be. What's in mailman.log and smtp.log? You can get a bit more log info by setting ``` [logging.smtp] level: debug ``` in mailman.cfg. -- 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: Mailman and Postfix Conflicting Information

by Mark Sapiro

On 2/8/26 09:03, dap1--- via Mailman-users wrote: > A bounce was logged for each list member. Yes, I do get a bounce notice as list owner but that goes via the default relay rather than gmail. So the issue is not with Mailman per se. What MTA is bouncing the messages and for what reason? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Mark Sapiro

On 2/9/26 12:17, Ibiam Chihurumnaya via Mailman-users wrote: > It would be great if mailman can ban domains and not just users, just noticed a flurry of spam from a particular domain. It can. Entries in the ban list can be addresses or regexps beginning with ^ that match addresses such as ^.*[@.]example.com$ to match any address in the example.com domain or a subdomain thereof. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Confirmation emails aren't sent to users.

by Mark Sapiro

On 2/13/26 12:41, Ibiam Chihurumnaya via Mailman-users wrote: > Makes sense, I didn't think I needed to. > > Couldn't see them with mailman conf though. Mailman conf only shows Mailman core settings - defaults and things you set in mailman.cfg. It doesn't know about any Django settings. To see the Django settings that differ from default values use django-admin diffsettings To see all settings with defaults flagged with ### use django-admin diffsettings --all -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Mark Sapiro

On 2/14/26 01:04, Stephen J. Turnbull wrote: > > `mailman-web diffsettings` also works. (As far as I know > `mailman-web` is effectively an alias for django-admin.) Actually, in our recommended virtualenv install mailman-web is preferred because django-admin doesn't load /etc/mailman3/settings.py by default. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

Search results for query "sapiro"