Steve, I'm referring to Postfix specific records, not Mailman records which are not the topic of conversation here.
Presently, Mailman creates two files under "/opt/mailman/mm/var/data"... "postfix_lmtp" which is a "transport_maps" table "postfix_domains" which is a "relay_domains" table The instructions in the docs says to set these up as "hash" table entries in Postfix so that when they're updated by MM Postfix references get updated accordingly. What I'm doing is, converting the "hash tables" to MariaDB tables stored in a Postfix specific database. Two primary objectives are intended with this updated architecture design... 1. allow management of Postfix tables through my web UI 2. Offer future scalability whereby the database for MM and Postfix amongst other things may get placed on a separate node, and/or setup in a Master-Master mirror cluster. *** On a segway, but related to the overall goal... I'm adding OpenDKIM management into my admin UI, which also is tied to a MariaDB database for key signing tasks and management. For the same reasons above, this is why I'm moving from files to databases. *** _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@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/ZKOXMJ2K27NCBCG4TM3WQJC6TUNVWDXI/ This message sent to arch...@mail-archive.com
