Re: Run two instances of dbmail-lmtpd
Paul J Stevens <[email protected]>
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I find it easier to start more MX virtuals that run their own postfix + lmtpd to increase throughput and use multiple MX records on domains to distribute the load over the virtuals. If running multiple instances of lmtpd on a single machine is needed, you need either: a preforking setup (which share the address of the listening socket), a threaded lmtpd, or completely separate processes that listen on different addresses or unix-sockets. To use the last solution while sending all mail to the same address (myhost:24) you would need a proxy like haproxy. On 26-11-14 22:04, Reindl Harald wrote: > > Am 26.11.2014 um 21:59 schrieb Jorge Bastos: >>>> DNS is a prerequisite for email and >>>> http://en.wikipedia.org/wiki/Round-robin_DNS should be well >>>> known >>>> >>>> mailbox_transport = dbmail-lmtp:some-DNS-hostname:24 >>> >>> Ah, I was not getting how postfix would work, that was my >>> doubt. >>> >>> But yes got it, thanks for that :) >>> >>> So if postfix looks up the host in every delivery, it's >>> solved! >> >> Some extra thinking on this. Would this bring any collision in >> id's or so, if the two processes get the same msgid on the >> insert, or not possible since auto-increments are used, so >> database will handle it fine (since they are autoincrements)? > > that's why dbmail is using a database > > * dbmail-lmtpd is currently not designed for parallel delivery * a > RDBMS is by definition designed for parallel inserts > > > > _______________________________________________ DBmail mailing > list [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail > - -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, github, linkedin www.nfg.nl/[email protected]/+31.85.877.99.97 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlSf5lEACgkQ8iITvBH4zTE9JQCgvq0Y1La7qNpR0ROGnQjoZJX9 x+YAoMcrZcsBn8LG8zZQlLGW+LIZJ+jN =UEPT -----END PGP SIGNATURE-----