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

[MM3-users] Re: Mail configuration

by Mark Sapiro

On 03/27/2018 03:43 PM, Stephen J. Turnbull wrote: > > My feeling is that you want to ask on Postfix channels, since I don't > see a good reason to involve Mailman itself in what is really a task > for the MTA. Mailman was deliberately designed to not know anything > about outgoing mail except a host and port to send to. Which brings up the point I've been meaning to post for days but it keeps slipping off the back burner and falling on the floor. I can think of a couple of ways to hack the code in Mailman 2.1 to select a different outgoing MTA by list. It can also be done in Mailman 3 by having separate MTA configs per list, but I can't give you a recipe off hand. But, the way I would do this is what you are presumably doing anyway. That is have separate Mailman installations on the old and new server. Then you can move the lists incrementally and gradually. Then all you need is a transport map in Postfix on the old server to route mail to the new server for the already moved lists, and then finally update DNS after all the lists are moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: duplicate dkim headers w/ AWS SES

by Mark Sapiro

On 6/2/20 9:44 AM, sunil soprey wrote: > Periodically, I've seen these errors from few senders, and wondering if community has a idea? Mailman - 3.3.1rc1 Tom Sawyer > > "554 Transaction failed: Duplicate header 'DKIM-Signature'" while sending AWS-SES as the MTA? > > Possible to strip from postfix? I've submitted a AWS ticket. It appears that AWS SES is intended only for delivery of locally generated mail and not mail that is received and resent by a mailing list or forwarding arrangement. This page <https://docs.aws.amazon.com/ses/latest/DeveloperGuide/header-fields.html> gives a list of a large number of headers that can appear only once in a message, among them are Delivered-To:, DKIM-Signature: and a few others that might legitimately appear more than once in messages from a mailing list. There are a couple of ways to remove incoming DKIM sigs. If you are signing with opendkim, there is a RemoveOldSignatures config setting which if true will remove existing signatures when signing. In Mailman itself you can put [mta] remove_dkim_headers: yes in mailman.cfg and Mailman will remove all DomainKey-Signature, DKIM-Signature and Authentication-Results headers from the message before delivery to the MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/19/21 11:50 AM, Sarah H wrote: > Hi Mark, > > I wanted to make another note on the documentation, the migration documents (https://docs.mailman3.org/en/latest/migration.html#fn2) reference using > > 'python manage.py hyperkitty_import' > > it should be > > 'mailman-web hyperkitty_import' That is a can of worms. It all depends on how you installed Mailman 3. If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html, the django management command will be `mailman-web`, but installation in other ways can result in its being `manage.py` or `django-admin` or almost anything. For example, https://docs.mailman3.org/en/latest/pre-installation-guide.html#what-do-i-n… refers to a typical Django project in which the management command is `manage.py`. https://docs.mailman3.org/en/latest/config-web.html is inconsistent in itself in that it uses `mailman-web` in most places except the note about qcluster at https://docs.mailman3.org/en/latest/config-web.html#running-the-task-queue which also links to http://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks which uses `django-admin`. I'm thinking that we should put a note about this near the top of https://docs.mailman3.org/en/latest/ and let it go at that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 7/18/25 5:37 PM, Cathryn McGuire wrote: > > The .* pattern did not do the job of blocking cc's and bcc's in the Header Filters of Affinity. It lets them go through, even as hold for moderation has been chosen. First, you can't filter on Bcc because Bcc is removed from the message before being sent. That's the whole point of Bcc. In otherwords, if I mail To: the list with Bcc: to others, the list never sees that Bcc: header and can't filter on it. As far as Cc is concerned, if in Header filters you have a rule with 'cc' in the header box and '.*' in the pattern box, the action box action should be applied to any message with a Cc: header. > I've asked EMWD to advise me because I think Affinity is very new, even though Brian Carpenter was developing it in 2020, is that correct? Affinity is not new, but it is a proprietary product of EMWD. If you have set the header filter as above and it is not working, only EMWD can help with that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Mailman3 equivalent of list_owners binary

by Mark Sapiro

On 10/2/25 08:38, l.reilly(a)ucl.ac.uk wrote: > > I've tried using the command 'mailman members --role administrator LISTSPEC' whilst looping through each list from the output of 'mailman lists'. It almost does the job, but in cases where an owner has a display name set the sync fails as it cannot parse these lines. > > e.g. Cannot parse as valid email address (skipping): Smith, John <john.smith(a)example.com> The issue here is when the display name contains a comma or other special character, it should be quoted as in "Smith, John" <john.smith(a)example.com> to be parsed as an email address/display name. The absence of quotes in the output of `mailman members` is not really a bug as that output is intended only for humans, but you could apply this patch to provide them. ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -112,7 +112,7 @@ if email_only or not dn: print(address.original_email, file=outfp) else: - print(f'{dn} <{address.original_email}>', + print(f'"{dn}" <{address.original_email}>', file=outfp) ``` Otherwise, you could supply the -e/--email-only option to `mailman members` to not include the display names in the output. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: "Something went wrong | Mailman REST API not available. Please restart Mailman core.

by Mark Sapiro

On 10/29/25 14:31, Hirayama, Pat wrote: > > The weird thing is that it is not all lists. Most of them seem to be fine. Which suggests to me that the issue is with a few lists, but not systemwide, so I think my settings in mailman.cfg, settings.py, settings_local.py are likely correct. So Postorius can connect to Mailman core's API on behalf of some, but not all lists. This is very strange. > For the problem lists, I see this in the log: > > ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available > ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ > ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ > > So, Postorius can't communicate with the API, I guess? These are the normal messages when the REST API is not available. But it apparently is available for at least some API endpoints. What is the traceback from the ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available error and what is in the web server logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 4 weeks

[MM3-users] Re: Is it possible to add non-members in regex format in Mailman 3 ?

by Mark Sapiro

On 6/16/20 7:09 AM, Shashikanth Komandoor wrote: > > But in mailman 3, I am not allowed to add the non members in > the regex format. Of course it is allowing me to add individual mail ids > and give permissions. But I want to add a non-member which may be something > like the entire cisco.com domain on which I want to set the rule. You cannot add a non-member with a regexp email, but the legacy *_these_nonmembers list attributes still exist in Mailman core and accept regexps. These settings are exposed in Postorius 1.3.3+ under Settings -> Message Acceptance. With older Postorius, you ned to set these directly in core, e.g. with `mailman shell` as in $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> m.accept_these_nonmembers [] >>> m.accept_these_nonmembers = ['^.*[.(a)]good\.domain$'] >>> m.accept_these_nonmembers ['^.*[.(a)]good\\.domain$'] >>> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Membership list changes

by Mark Sapiro

On 2/18/21 9:37 AM, Vako Nicolian wrote: > Using MM 2.1.33 > When I send an email to /{list}-request(a){domain.com} /with /who > <password> /on the subject line, I get a list of the members of the list. > > Here are my questions: > A) Is there a way to export the list to cvs or txt format? copy/paste > B) Can we format the list to have it come in name 1st and then email> C) display number of members > D) Sort the list These things can be done by manipulating the copy/paste result to turn it into a .csv and importing that into a spreadsheet. For example, piping this input ``` Non-digest (regular) members: user1(a)example.com (User One) user2(a)example.com Digest members: user3(a)example.com (Three, User) user4(a)example.com ``` through this script ``` #! /usr/bin/env python import sys from email.utils import parseaddr flag = '' for line in sys.stdin.readlines(): if line.startswith('Non-digest'): flag = 'Reg' continue if line.startswith('Digest'): flag = 'Dig' continue name, addr = parseaddr(line) print('"{}",{},{}'.format(name, addr, flag)) ``` produces this output ``` "User One",user1(a)example.com,Reg "",user2(a)example.com,Reg "Three, User",user3(a)example.com,Dig "",user4(a)example.com,Dig ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/4/22 11:15, gordon(a)dickens.com wrote: > > 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 > 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 > > So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: It's not the alias for static > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > # ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > </IfModule> It's the fact that ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost is commented out. This should not be commented assuming you are using uWSGI and it is listening on the socket /run/mailman3-web/uwsgi.sock -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Rejection based on total message size including attachments

by Mark Sapiro

On 09/19/2018 03:34 PM, leith(a)khimaira.com wrote: > As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro. > > Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers. Is this a Mailman 3 question or a Mailman 2.1 question? If Mailman 3, the architecture is quite different. This would be done with a rule, not a handler, but based on details in your question, I think you are asking about Mailman 2.1. In that case, the appropriate list is really mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>, but since you're here, the basic info on custom handlers for MM 2.1 is at <https://wiki.list.org/x/4030615>. There is an example called MyHandler.py linked from that page. It won't do what you want but can be used as a starting point. Also, look at Mailman/Handlers/Hold.py, in particular the code following the "# Is the message too big?" for how to determine the message size. That handler will compare the size to the list's max_message_size and hold the post if it's too big. You probably want to compare the size to a fixed value or a size defined in mm_cfg.py and either reject or discard the message. If you put your handler between Moderate and Hold, it's probably safe to reject the message because it is from a member or an address in accept_these_nonmembers. Rejecting post from arbitrary non-members is a bad idea because of spam backscatter. If you need more help, please join mailman-users(a)python.org and post to that list. In any case, this could be generally useful enough that I will probably add it to the stuff at <https://www.msapiro.net/scripts/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

Search results for query "sapiro"