Hello,
I am currently working on upgrading our Mailman system from Mailman 3.3.1 to Mailman 3.3.5. Our configuration utilizes containers that run on Alpine Linux. While working on updating the containers I noticed that the recent version of Alpine has dropped support for Berkeley DB lookup tables. Due to this change I think our only option is to switch over from using hash tables to regexp tables (or switch the OS the containers are running on). In addition, while I was working on the updates I realized that even though the Berkeley DB support has been dropped Mailman seems to work ok with the new default lookup table for Postfix on Alpine: LMDB. I was hoping to get a few answers to some of the questions I have with regards to the options we have moving forward. Any help is greatly appreciated!
- 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?
- 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.
Thank you for any guidance you can provided with this and have a nice day, Peter
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Peter Williams