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

[MM3-users] Re: postorius configuration of the from-part

by Mark Sapiro

On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > can someone give me an advice how I can configure in the > postorius-menues the view of the from-part of my list-member like in > this mailinglist: > > Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> The above is the result of Settings -> DMARC Mitigatations -> DMARC mitigation action = "Replace From: with list address" You can apply that to only messages From: a domain the publishes a DMARC policy of reject or quarantine or to all messages depending on DMARC Mitigate unconditionally. > case 1 reply goes to the list or to the member > case 2 reply goes only to the list The DMARC Mitigatations settings are independent of the various reply settings on the Alter Messages tab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/8/21 8:35 AM, Sarah H wrote: > > When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive. What if anything is in Mailman's var/archives/hyperkitty/spool/ directory? Do you have something like ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg ``` in your mailman.cfg? Do you then have ``` [general] base_url: ... api_key: ... ``` in the mailman-hyperkitty.cfg file and is base_url set to a url tha accesses hyperkitty and is api_key set to the same value as the MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but not in mailman-hyperkitty.cfg, i.e., ``` api_key: xxx MAILMAN_ARCHIVER_KEY = 'xxx' ``` -- 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: New messages not being archived

by Mark Sapiro

On 7/12/21 1:40 PM, Sarah H wrote: > I took a look at the pickle files, this last one didn't have the archive locations but another had > > Archived-At: <> > List-Archive: <> > > as well, so it looks like it's not being passed properly to the archive location? Messages in the spool were not successfully delivered to HyperKitty[1] and will be retried each time there is a new post. There should be log messages in mailman.log about the failures. Likely issues are problems with the base_url or api_key settings in mailman-hyperkitty.cfg [1] It doesn't matter if they originated from HyperKitty or elsewhere. Messages originating as replies or new threads from HyperKitty are posted to Mailman core for processing and only archived when core sends them back to 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, 11 months

[MM3-users] Re: Email discard

by Mark Sapiro

On 4/1/23 08:33, qro(a)xs4all.nl wrote: > Hi > > I have a good working mailman3 list server with 3 mailing lists. > 2 of them work OK, but 1 has a little odd behaiver > > If a non member send an email it will discard while the setting in /postorius/lists/list.name.nl/settings/message_acceptance shows Hold for moderation > > A snip from var/mailman3/mailman.log > Apr 01 10:48:32 2023 (49342) DISCARD: <4359976d-d4bb-9b30-0901-c842aa1fecb3(a)xs4all.nl>; ['The message is not from a list member'] > > Changing and saving a other choice makes no difference. > > Where can I look more to find a solution? (in mysql?) In Postorius, find the nonmember in the Users->Non-Members list. Does that nonmember have a moderation action of discard. Also, what's in Postorius->Settings->Message Acceptance->Discard these non-members? -- 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 -owner messages

by Mark Sapiro

On 6/15/23 13:47, ssehi--- via Mailman-users wrote: > > They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? No. In Postorius you can set the delivery status for members and non-members, but you can't set it for owners or moderators. Owners and moderators do have a delivery_status which will control whether they receive notices sent via the listname-owner address, but it is not exposed or settable in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: customized welcome message

by Mark Sapiro

On 12/7/23 03:01, Nils wrote: > Hi, > > I've created a template "The notice sent to a member when they are > subscribed to the mailing list.". > When I subscribe to the list, I don't get the message I've created. > Instead I get a plain text message, containing the html source of the > parent domain. These messages are sent with `Content-Type: text/plain`. Any html included in a template will be rendered as plain text. I.e., you can't include html in templates. > When I try to change the value of Settings > Automatic Responses > URI > for the welcome message in postorius frontend, I always get this error > message: I see no URI setting in Postorius Settings > Automatic Responses. What Postorius version is this? Any local mods? -- 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: Hiding the "subscribe without creating an account"

by Mark Sapiro

On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: > > Is there a configuration option that does this, or was it a custom change made in > the templates? Was the change made to reduce fake registrations? Did it work? It was added in Postorius 1.3.9. See the UI section at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 Yes, the change was made in an attempt to reduce fake registrations. We haven't really studied it's effectiveness. It seems to help somewhat, but it also seems that bots may already have a template to POST so removing it from the UI is not a complete solution. There is also a lot of email to innocent third parties and non-existent addresses from attempts to register them for an account. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: footer template priority

by Mark Sapiro

On 6/19/25 15:42, Sam Darwin via Mailman-users wrote: > It takes time to figure out a new feature. I see what is happening. :-) Or, merely one step further. > > After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL because the value is cached in the DB. That explains the caching. > > Next, without POSTORIUS_TEMPLATE_BASE_URL, it assumes http://localhost:8000/mailman3/ . On our server this is not correct, because it's listening on a unix socket, as well as 80 and 443, but not 8000. Actually, it assumes whatever the default is which might be `http://localhost:8000`. See https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/m…. It's Postorius that adds the /mailman3/... when setting the template table entry. If that is not correct for your server, you need to set the correct value in settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: upgrading Mailman

by Mark Sapiro

On 10/1/25 11:02, Christian Stalberg via Mailman-users wrote: > I am operating an old platform. I am currently running GNU Mailman Core > version 3.3.5, API version 3.1, Python Version 3.7.3, on Debian 4.19.316-1 > > What version of Mailman 3 is current and what is the recommended server > please? Are there upgrade instructions available? Please do not hijack threads. When posting a new topic compose a new message, not a reply to an unrelated post. The current released version of Mailman core is 3.3.10 and it requires Python >= 3.9. If you are asking about upgrading Debian Mailman packages, that's a question for Debian. There is information on upgrading at https://docs.mailman3.org/en/latest/upgrade-guide.html. You can install Mailman in a virtualenv following the instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html. You can do this and keep your existing database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: Setting up From: field as list address

by Mark Sapiro

On 11/24/19 11:54 PM, Steven Maddox wrote: > Hi folks, > > I'm trying to configure our mailman3 lists (via postorious) in a way > that'll mean they'll behave in the way way that I've witnessed on > another 3rd party list (one running mailman2). > > This is where (when receiving a message from the list) the From: is the > list itself, and the person who actually sent it bizarrely appears as a > CC:, for example... > > From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> > Subject: [Shropshire LUG] Whatever > To: shropshire(a)mailman.lug.org.uk > CC: s.maddox(a)lantizia.me.uk Go to Settings -> DMARC Mitigations and set DMARC mitigation action to "Replace From: with list address" and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

Search results for query "sapiro"