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

[MM3-users] Re: Lookup Table Questions

by Mark Sapiro

On 12/7/21 4:09 PM, Peter Williams wrote: > > - The Mailman documentation notes that either hash or regexp tables are > supported. Is it ok to use LMDB or will I run into issues at some point? Mailman only supports hash and regexp tables for automatic maintenance of the tables as lists are created and removed. If you use LMDB tables you will need to maintain them yourself. The `mailman aliases` command won't do it. > - If LMDB tables are not a good idea to use, are there any drawbacks to > switching over to regexp tables? My main concern is that we currently have > 7000+ mailing lists, and I'm worried that switching over to regexp may > result in slower lookups. I am also wondering if there are potential issues > if the 'mailman aliases' command is run simultaneously alongside another > 'mailman aliases' command. In the past it seems like the hash table was > locked (which was good), and I'm not sure if this behavior is kept by > moving over to regexp. This may be more of a Postfix question and I > apologize in advance if I am asking the wrong mailing list for this. The locking is done in mailman/mta/postfix.py regardless of table type. I.e. it's the same for hash and regexp table updates. I wonder why you are manually running `mailman aliases`. This really shouldn't be necessary as the files are regenerated automatically as lists are created and removed. As far as performance of regexp vs hash tables, I have no idea. That's really a Postfix question. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/8/24 12:48 PM, Steve Brown wrote: > I'm a list administrator for a list hosted by mailmanlists.net on a server in Germany. Only one member uses the digest option, but she doesn't receive a digest until the Digest size threshold has been exceeded. (I also am subscribed as a member with the Mime Digest option and see the same behavior.) The option for Send Digest Periodically is checked but doesn't trigger a daily digest on the days that there is some activity if the aggregate size doesn't exceed the threshold. I think "periodically" means daily, and the administrator doesn't seem to have any way of checking or changing the periodicity. The hosting service has attempted several fixes, including fiddling with the cron settings, but hasn't found something that works. They even upgraded to ver. 3.3.9 recently, and that didn't fix the problem. Periodic digests are sent by the `mailman digests --periodic` command which should be run daily by cron. That and the `mailman notify` command should be run from mailman's crontab. See https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-cron-jobs I don't know what "fiddling with the cron settings" means, but if these commands are in mailman's crontab, including ``` MAILTO=some_human(a)example.com ``` at the beginning of the crontab will ensure any diagnostic output is sent to some_human(a)example.com where it will be seen. Also, putting ``` LANG=en_US.UTF-8 ``` near the beginning of the crontab may be required in some cases. See the Attention notice at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/insta… -- 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: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. Mailman 3 consists of several pieces. There is a core engine which is Python 3. The core does the basic email list management and exposes many options and settings via a RESTful API. There is also mailman.client which provides Python bindings for the REST API. This is Python 2. We also provide a web management UI, Postorius and an archiver, HyperKitty. These are Django applications and all of this is Python 2. There are other pieces as well. > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler. This is only the core. You can install it with python3 setup.py install either in a python 3 virtualenv or not, but this will only give you the core. I suggest you see the docs at <http://docs.list.org/en/latest/>, and if you don't want to use bundler, see <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the recommended way to set up a working, non-development Mailman suite. In short, the core requires Python 3.4, most of the rest of the suite requires Python 2.7 because of dependencies not yet ported to Python 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: Bounces

by David Krantz

Thank you for the tip. In the end I changed mailman/runners/bounce.py instead by moving the maybe_forward line so that it is always run. Smaller change (just removing one indention level) and preserves the handling. Might break something else, but I do not think so. diff --git a/src/mailman/runners/bounce.py b/src/mailman/runners/bounce.py index 57b259f..e772765 100644 --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -86,6 +86,6 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False Cheers // David On Sun, Nov 5, 2017 at 10:39 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/05/2017 01:29 PM, Mark Sapiro wrote: >> >> The bottom line is we aren't doing anything with bounces other than >> storing them. We need to fix that, and we will (It's targeted for 3.2). >> If you could help with code, that would be great. > > > As an interim work around, if you wanted to send ALL bounces to the list > owner instead of what little we currently do, at about line 65 in > mailman/runners/rest.py, you'll see > > SUBADDRESS_NAMES = dict( > admin='bounces', > bounces='bounces', > confirm='confirm', > ... > > If you change the > > bounces='bounces', > > line to > > bounces='owner', > > that will cause all bounces to be just sent to the list owner(s). > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 7 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 5:43 PM, Ralph Seichter wrote: > With archiving enabled, mail is sent with headers like the following: > > Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> > List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> > List-Post: <mailto:foo-users@lists.example.com> > List-Subscribe: <mailto:foo-users-join@lists.example.com> > > The 'mailto:' entries are fine, but I need all 'https:' links to be > prefixed with https://lists.example.com instead of https://example.com . > > Does Mailman extract CN parts from the SSL certificate to populate the > header values (that would explain 'example.com' in my tests), or is this > something I can influence using configuration parameters? I searched the > docs for Mailman Suite and HyperKitty, but did not find an answer. It has nothing to do with the ssl certificate. It comes from _get_url in hyperkitty/views/mailman.py > def _get_url(mlist_fqdn, msg_id=None): > # We can't use HttpRequest.build_absolute_uri() because the mailman API may > # be accessed via localhost. > # https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.Htt… > # https://docs.djangoproject.com/en/dev/ref/contrib/sites/#getting-the-curren… > # result = urljoin(public_url, urlunquote( > # reverse('hk_list_overview', args=[mlist_fqdn]))) > # We use the MailDomain association from django_mailman3 to find out the > # proper domain. What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/ Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:02 AM, Marc SCHAEFER wrote: > > I have a few questions: > > 1) persistence: as I can regenerate the configuration files (mailman, > mailman-web, hyperkitty), is all what's useful in the DB, or are some > things in /var/lib/mailman3 worth saving? > > obviously messages to be moderated, hyperkitty failed messages, > etc are stored there, but shall I assume that all mailing-lists > configuration, all users configuration and all archives are > in the DB? I don't know the details of where the Debian package puts things, but there may be Postfix related files in /var/lib/mailman3/data, but yes, all mailing-lists configuration, all users configuration and all HyperKitty archives are in the DB? > 2) I imported a list and all messages get a footer of: > %(web_page_url)slistinfo/%(_internal_name)s > which I guess changed between MM2 and MM3; however when I > look at that list configuration in the web interface of MM3, > I see no templates defined, nor any clue where this is > configured: where may I change this? import21 creates these templates in (I think in your case) /var/lib/mailman3/templates. > 3) is there a configuration somewhere that can allow someone to > create a mailman web account ONLY if he is already referenced > somewhere in a mailing-list, and not otherwise? (or to > create accounts that need approvals from an admin > before being usable?) No. > also, can a non-yet-referenced e-mail From: still subscribe to > a private list (confirm+moderate) via e-mail regardless of > the above? Yes -- 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: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 7:45 AM, robert.kydd(a)gmail.com wrote: > Hi Mark, thanks for this. I was away and only got back now. > It's great to get rid of the reason text. > Is there any way I can find out what is i18n message catalog. It would be nice to give a more pleasing message to the users I am still not clear on what Mailman version you are using. If it is Mailman 3, i18n translations for Mailman core are still a work in progress, and I can't tell you how to do this. For Mailman 2.1, you will find within Mailman's file system, a messages/ directory with several 'language code' subdirectories, but not 'en'. You need to create messages/en/ and messages/en/LC_MESSAGES/ and then create the file messages/en/LC_MESSAGES/mailman.po with contents like: ---------------------------------------------------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR ORGANIZATION # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: Sun Jun 17 12:22:07 2018\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: ENCODING\n" "Generated-By: pygettext.py 1.4\n" #: Mailman/Handlers/Hold.py:61 msgid "Post by non-member to a members-only list" msgstr "WHAT YOU WANT TO REPLACE IT WITH" ---------------------------------------------------------- with the various UPPERCASE things replaced appropriately and then 'compile' it via > msgfmt -o messages/en/LC_MESSAGES/mailman.mo messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Mirroring a mailman3 server

by Mark Sapiro

On 1/16/22 9:09 AM, Axel Rau wrote: > > What else must be synced (by rsync)? Aside from the database, there are multiple directories containing Mailman mutable data. Where these directories are depends on Mailman's layout configuration. For all layouts except `fhs` they are all in a single directory, but for `fhs` they are split. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/mailman… Depending on exactly what's going on between the two servers, you need to decide what needs to be synced. For example, you probably don't want to sync .pid files or or the locks directory. You probably should sync archives/, cache/, data/, etc/, lists/, messages/, templates/, public_suffix_list.dat and the search engine's (Whoosh, Xapian, whatever) index files. Syncing Mailman's queue files is problematic. They are very dynamic and it isn't practical to rsync them. The same is true to a lesser extent with messages/ > While creating a domain, what should I enter into the fields? > > Mail Host lists.framail.de (currently lists5.lrau.net) Mail Host is the FQDN of the host's email address. > Alias Domain listsl.framail.de Alias Domain is a special case to handle situations where Mail Host is a Postfix virtual domain rather than a local destination. It is normally None (not set), and if requires would never be the same as Mail Host. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > Web Host lists.framail.de (currently lists5.lrau.net) Web Host is the host name of the web web server, i.e., the host in the URL that accesses the web UI -- 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: List of "site admin" commands in Mailman 3.1 docker-mailman

by Mark Sapiro

On 07/17/2017 07:55 AM, Henrik Rasmussen wrote: > > On another note: Is it a setting in the mailman-users(a)mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."? I suspect this is something in the MTA/MDA chain between the lists.mailman3.org server and you. I suspect that something in that path doesn't like the fact that your original message's DKIM signature has been broken by such things as subject prefixing and addition of the list's msg_footer. When your message reaches my server at msapiro.net, it sees > Authentication-Results: sbh16.songbird.com; > dkim=pass (1024-bit key; unprotected) header.d=mailman3.org header.i=(a)mailman3.org header.b=QBeM9elY; > dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=alumni.onmicrosoft.com header.i=(a)alumni.onmicrosoft.com header.b=GeTpYnXK; > dkim-atps=neutral I.e., the list's DKIM sig is valid but your original sig is not, even though it was valid when received by the list > Authentication-Results: mail.mailman3.org; dkim=pass > reason="1024-bit key; unprotected key" > header.d=alumni.onmicrosoft.com header.i=(a)alumni.onmicrosoft.com > header.b=GeTpYnXK; dkim-atps=neutral If my suspicion is correct, you should be seeing the same thing with other people's posts such as this reply and your posts to other lists. If you don't then my suspicion about DKIM is not the reason and it is something else or the conditions are more complex. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Bounce handling after upgrade

by Mark Sapiro

On 7/8/20 6:05 AM, David Krantz wrote: > > To my surprise mailman core started by sending tens of mails and > blocking the corresponding users for very old bounces. What is worse > is that this happens every time I start mailman core. Now I have > blocked (almost) all outgoing mail in postfix using a transport map > which discards it but this is a temporary testing measure of course. Sorry about that. Yes this is an issue when first upgrading from a prior version to 3.3.1, there are lots of old unprocessed bounce events which all of a sudden get processed. See below for solutions. > When I deploy this server into production, I do not want these > recipients to be blocked as the old problems have been solved since > very long. My plan is to reload the database from a newer backup > anyway... Would it be enough to empty the bounce table (bounceevent) > or is there anything else driving this behaviour? Or is there a better > way to do this via the mailman shell? For me a "delete from > bounceevent" seems a lot simpler than anything via the shell but there > may be dependencies in the database. You are on the right track. The "delete from bounceevent" is a perfectly acceptable solution. So is "update bounceevent set processed = true". Another way to deal with this is to set [mta] verp_probes: yes in mailman.cfg. This will still send a lot of probe messages which may be undesirable, but if the probes don't bounce, the user's delivery won't be disabled. -- 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

Search results for query "sapiro"