Hello there Django. Yes that is how we are doing it right now, using transport_map. But our goal is to go independent if one site goes down — both for high availability and live backup. Would love to replicate the CipherMail database same as we are replicating our mailbox storage and other services.
I tested out converting the PostgreSQL database to MySQL, but found some issues already. Seems that some of the tables (certificates for example) are given a very large size in PostgreSQL, where as in MySQL they are capped at 255. I don’t know about the restrictions in MariaDB, but I was unable to copy the data from the certificates table. Other than that, it seems to be a very possible option as Hibernate supports MySQL just the same. Any thoughts about the data type mismatch? ~ Laz Peterson Paravis, LLC > On Jun 30, 2015, at 12:18 AM, Django [BOfH] <[email protected]> wrote: > > Hello! > > Am 30.06.2015 um 05:03 schrieb Laz C. Peterson: > >> Currently, any mail we want to send through CipherMail must travel to a >> specific server in one site, versus going out (or in) through any site. > > Incomming emails to different sites are routed with transport_maps's > hashtable: > > domain_1 lmtp:backend_domain_1:24 > doamin_2 lmtps:backend_domain_2:24 > domain_3 smtp:[10.10.10.10]:25 > >> I can share my experiences here. > > Grait, please do it! ;) > > > Best regards > Django > -- > "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God > http://wetterstation-pliening.info > http://dokuwiki.nausch.org > http://wiki.piratenpartei.de/Benutzer:Django > _______________________________________________ > Users mailing list > [email protected] > https://lists.djigzo.com/lists/listinfo/users _______________________________________________ Users mailing list [email protected] https://lists.djigzo.com/lists/listinfo/users
