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

[MM3-users] Re: Good choice of defaults for content filtering?

by Allan Hansen

Excellent. Thank you, Mark. Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Jul 30, 2020, at 18:00, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/30/20 5:00 PM, hansen(a)rc.org wrote: >> Hi all, >> >> I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: >> a. What were those MM2 defaults (My MM2 server is long gone now). > > > You will find the content filtering defaults beginning at > <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. > These have been the defaults for new lists since Mailman 2.1.21. Prior > th that, the the default for pass_mime_types was > > ['multipart/mixed', > 'multipart/alternative', > 'text/plain'] > > >> b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. > > > If you go with the current defaults, except of course for setting filter > content on, you can add text/html to pass_types and any html parts that > aren't collapsed out by collapse alternatives will be kept and converted > to plain text. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 10 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/14/2016 07:11 AM, Mark Sapiro wrote: > On 5/13/16 5:05 PM, Simon Hanna wrote: >> On 05/12/2016 09:26 PM, Barry Warsaw wrote: >>> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >>> >>>> It is the intent that Postorius will eventually expose all these >>>> settings. We're not there yet. At present you could possibly do this by >>>> interacting with mailmanclient, although I'm not certain the settings are >>>> exposed there. >>> >>> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >>> core's REST API, on the member resource. It's the `delivery_mode` attribute >>> and it takes as legal values one of 'regular', 'plaintext_digests', >>> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >>> DeliveryMode enum). > >> They are exposed in mailmanclient and are used in postorius. They can be >> found in the users personal subscription settings >> https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > > You are correct. When I checked this before my initial reply, I never > pulled down the Delivery Mode list to see all the options. My bad. > > However, please correct me if I'm wrong, but there does not appear to be > a way in Postorius to set a list's mime_is_default_digest attribute. > You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.

10 years

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/26/26 07:27, Ibiam Chihurumnaya via Mailman-users wrote: > > Mark Sapiro wrote: > > On 2/25/26 2:43 PM, Ibiam Chihurumnaya via Mailman-users wrote: > > I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save(). > > accept_these_nonmembers is a list hence the append, I didn't add the argument to append, maybe that's what caused the confusion. > > Again, the above makes no sense. In what context are you doing this? > mailman shell or something else? What is list_name is it a mailing > list object or something else? mailing list objects have no settings > attribute? There is no settings mapping with keys so > settings['accept_these_nonmembers'] is meaningless. What is > list_name.settings? I'm doing it in `mailman shell`, list_name is a List object, and it seems to have a `settings` attribute as `list_name.settings` returns {'acceptable_aliases': [], 'accept_these_nonmembers': [], 'admin_immed_notify': True, 'admin_notify_mchanges': False, 'administrivia': True, 'advertised': False, 'allow_list_posts': True, 'anonymous_list': False, 'archive_policy': 'public', 'archive_rendering_mode': 'text', 'autorespond_owner': 'none', 'autorespond_postings': 'none', 'autorespond_requests': 'none', 'autoresponse_grace_period': '90d', 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounces_address': 'systems-logs-bounces(a)lists.sugarlabs.org', 'bounce_info_stale_after': '7d', 'bounce_notify_owner_on_bounce_increment': False, 'bounce_notify_owner_on_disable': True, 'bounce_notify_owner_on_removal': True, 'bounce_score_threshold': 5, 'bounce_you_are_disabled_warnings': 3, 'bounce_you_are_disabled_warnings_interval': '7d', 'collapse_alternatives': True, 'convert_html_to_plaintext': False, 'created_at': '2026-02-04T21:53:10.928951', 'default_member_action': 'defer', 'default_nonmember_action': 'accept', 'description': '', 'digest_last_sent_at': '2026-02-26T10:54:11.703949', 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': 'monthly', 'digests_enabled': True, 'display_name': 'Systems-logs', 'discard_these_nonmembers': [], 'dmarc_mitigate_action': 'no_mitigation', 'dmarc_mitigate_unconditionally': False, 'dmarc_addresses': [], 'dmarc_moderation_notice': '', 'dmarc_wrapped_message_text': '', 'emergency': False, 'filter_action': 'discard', 'filter_content': False, 'filter_extensions': [], 'filter_types': [], 'first_strip_reply_to': False, 'forward_unrecognized_bounces_to': 'administrators', 'fqdn_listname': 'systems-logs(a)lists.sugarlabs.org', 'gateway_to_mail': False, 'gateway_to_news': False, 'hold_these_nonmembers': [], 'include_rfc2369_headers': True, 'info': '', 'join_address': 'systems-logs-join(a)lists.sugarlabs.org', 'last_post_at': '2026-02-26T11:28:37.171138', 'leave_address': 'systems-logs-leave(a)lists.sugarlabs.org', 'linked_newsgroup': '', 'list_name': 'systems-logs', 'mail_host': 'lists.sugarlabs.org', 'max_message_size': 40, 'max_num_recipients': 10, 'max_days_to_hold': 0, 'member_roster_visibility': 'moderators', 'moderator_password': None, 'newsgroup_moderation': 'none', 'next_digest_number': 53, 'nntp_prefix_subject_too': True, 'no_reply_address': 'noreply(a)lists.sugarlabs.org', 'owner_address': 'systems-logs-owner(a)lists.sugarlabs.org', 'pass_types': [], 'pass_extensions': [], 'personalize': 'none', 'post_id': 298, 'posting_address': 'systems-logs(a)lists.sugarlabs.org', 'posting_pipeline': 'default-posting-pipeline', 'preferred_language': 'en', 'process_bounces': True, 'reject_these_nonmembers': [], 'reply_goes_to_list': 'no_munging', 'reply_to_address': '', 'request_address': 'systems-logs-request(a)lists.sugarlabs.org', 'require_explicit_destination': True, 'respond_to_post_requests': True, 'send_goodbye_message': True, 'send_welcome_message': True, 'subject_prefix': '[Systems-logs] ', 'subscription_policy': 'confirm', 'unsubscription_policy': 'confirm', 'usenet_watermark': None, 'volume': 1} > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: MTA setup

by Arte Chambers

The shunt queue is empty. I see a 400 error "Bad Request" in the mailman logs, not sure what my next troubleshooting steps should be. mailman log: Dec 23 16:58:51 2024 (684048) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!doctype html> <html lang="en"> <head> <title>Bad Request (400)</title> </head> <body> <h1>Bad Request (400)</h1><p></p> </body> </html> Dec 23 16:58:51 2024 (684058) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/urls: <!doctype html> <html lang="en"> <head> <title>Bad Request (400)</title> </head> <body> <h1>Bad Request (400)</h1><p></p> </body> </html> (400) Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Dec 23, 2024 at 1:29 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 09:03, Arte Chambers via Mailman-users wrote: > > Update: After changing the DMARC settings messages are now going through > to > > my inbox, however they are still not being archived. > > > Yes, that's always been a separate issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

1 year, 5 months

[MM3-users] Re: Incoming command emails (i.e. listname-leave) routed to list itself

by Mark Sapiro

On 04/20/2017 05:37 PM, Mark Lindsay wrote: > > I'm new to Mailman 3 and Mailman in general, but I've got it up and > running, and my external app is communicating quite well with the > administrative REST API. Cool. > Here's the only problem I haven't been able to figure out: > > Say I have a list called "potato." List members can post to the list by > emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail > for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to > the list too. The command email gets sent out to all members, as if the > user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. > This is also the case with the potato-request(a)lists.mydomain.org address. > > I am using exim4 on Ubuntu. I followed the instructions here: > http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The > only change I had to make to the exim4 config files in the readthedocs > instructions was in this line: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > I had to change it to: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > > That is how the subdirectories are named in my lists directory. e.g. > potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from > readthedocs, I get 550 Unrouteable bounces. OK. That document needs updating. Also, the '-admin' local_part_suffix should not be there, but that's not related to your issue. '-admin' is from MM 2.1 and isn't used in MM 3. > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >> `? That's the key question. The transport is supposed to just relay the message to Mailman via LMTP to MM3_LMTP_PORT, but it appears to be rewriting the envelope recipient from potato-leave(a)lists.mydomain.org to potato(a)lists.mydomain.org. I suspect the router is somehow stripping local_part_suffix from the recipient address, but why, I don't know. > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through it. We want to make MM 3 work with Exim as an MTA. Unfortunately, I have not used Exim as an MTA in a long time and not with Mailman 3 at all, so I may not be much help. I think the person who set up Exim is on this list and may reply. If not, I'll try to research this further. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Receiving Email from ListName-bounce@Domain for Unsubcribe

by Marin Sok

Hi Mark, I changed it and it works as expect now. Thanks a lot for your help guide me on this. [cid:1c0306de-6190-48ad-a8f3-b67ffd1a48a3] Thanks, Marin <http:\\probonoweek.lalawlibrary.org> [http://www.lalawlibrary.org/sigimages/logo-sig.png] Marin Sok IT Director P 213.785.2556 | F 213.680.1727 http://www.lalawlibrary.org/<http://www.lalawlibrary.org/> | MSok(a)lalawlibrary.org Access to Information = Access to Justice <http://probonoweek.lalawlibrary.org/> Follow us: [http://www.lalawlibrary.org/sigimages/facebook.png] <http://facebook.com/LALAWLIBRARY> [http://www.lalawlibrary.org/sigimages/twitter.png] <http://twitter.com/LALAWLIBRARY> [cid:SocialLink_Instagram_32x32_dc37fa34-8ab4-41db-9940-9cb519436518.png] <https://www.instagram.com/lalawlibrary> ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, February 16, 2026 2:44 PM To: Marin Sok <MSok(a)lalawlibrary.org>; Stephen J. Turnbull <steve(a)turnbull.jp> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Receiving Email from ListName-bounce@Domain for Unsubcribe [You don't often get email from mark(a)msapiro.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] On 2/16/26 13:55, Marin Sok via Mailman-users wrote: > > Should I try to modify the code in file notifications.py in line 137. You could change that line from address, mlist.bounces_address, to address, mlist.owner_address, if you feel it's important. I will probably do something about https://gitlab.com/mailman/mailman/-/issues/1260<https://gitlab.com/mailman/mailman/-/issues/1260> so it will be fixed for the next release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Content-Type: image/png Name: SocialLink_Instagram_32x32_dc37fa34-8ab4-41db-9940-9cb519436518.png Replaced multipart/alternative part with first alternative.

3 months, 2 weeks

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 11:19 AM, Mark Sapiro wrote: > Here's a thought. For Affinity/Empathy at least, how about using Mailman > core's user as the Affinity registered user. I.e., if someone's first > interaction is to register with Affinity, have that registration create > a core user to keep the Affinity registration data. This core user > already accommodates a display_name and password and email address(es). > > If the person already is a core user when registering for Affinity, just > update the core user as needed, probably only a password reset or just > setting it if it is currently None. > > Then you don't have the issue of another, separate registration for > Affinity. > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San > Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ Mailman-users mailing > list -- mailman-users(a)mailman3.org To unsubscribe send an email to > mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ How would a person already be a core user outside of a registration with Affinity? Via a list subscription or the import21 script? I do agree overall that we can more easily address some/all of these issues more easily and quicker due to not being tied to Django. I hope to get all of this address in our Nov development cycle. I do want to apologize for my tone Mark. I was wrong in the way I communicated. > -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 7 months

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

So the MTA option that doesn't involve any regex is better than no? On Thu, Mar 30, 2023, 20:17 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 08:55, Zaheer Abbas wrote: > > Hi All, > > > > I need to whitelist a domain for a specific mailing list on your > platform. > > Only *(a)example.com email addresses should be allowed to post messages to > > this list. > > > > Could you please provide me with documentation or instructions on how to > > achieve this? I have already searched the knowledge base and user manuals > > without success. > > > In Postorius Header filters add a filter with Header = from, pattern = > ^.*(a)(?!example\.com(\W|$)) and Action as desired. That pattern will > match anything in a From: header which contains an @ followed by > anything other than example.com and a non-alphanumeric or the end of > string. I.e., things that won't match are for example > > xxx(a)example.com > xxx(a)example.com> > xxx(a)example.com yyy > > Things that will match are for example > > xxx(a)other.domain > xxx(a)example.comp > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

3 years, 2 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; +---------------+--------------+ | list_name | howManyBytes | +---------------+--------------+ | <snip> | 65535 | | <snip> | 65535 | | <snip> | 65535 | +---------------+--------------+ 3 rows in set (0.01 sec) So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:15 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 7:35 PM, Bryan Loniewski wrote: > $ /opt/mailman/mm/bin/mailman version > GNU Mailman 3.3.2 (Tom Sawyer) > > So, I'm running > 3.2. Any other advice on debugging the truncated data? The traceback indicates sqlalchemy is unpickling data whose type is PickleType. The only mailinglist columns which are PickleType are the legacy *these_nonmembers and topics. You could try invoking mysql on Mailman's database and doing SELECT list_name, accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, discard_these_nonmembers, topics FROM mailinglist; and look for the longest values to possibly identify the problem list and attribute. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 9 months

[MM3-users] Re: Social signup?

by Duane Raymond

Wow - thanks for the redirection on where to patch it and the first-cut code. I'll look into this in 2 weeks when I am able to focus on it. Cheers, Duane On Wed, 15 Mar 2023 at 16:18, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/23 05:08, Duane Raymond wrote: > > > > I'll jump over to the developers list when I start this (I'm about to > > travel for a week to run an annual event in Oxford - so the far removed > > from programming)...but which chatGPT suggested so far was > > > > 1. Extending postorius/signups.html with a loop to get the configured > > social login providers PLUS adding a csrf_token field to the form > > 2. Modifying postorius/views.py (which doesn't seem to exist but > there > > is a postorius/views folder) - so perhaps this is views/urls.py > > > This is not what you want to do for this. The changes need to be in > django-mailman3, not postorius. I have attached a patch which might work > for you. I think it is good, but some of the wording is stuff that may > not be appropriate. See what you think. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to duane(a)fairsay.com >

3 years, 2 months

Search results for query "sapiro"