Am 03.11.2014 um 18:12 schrieb Jorge Bastos:
In fact it has a more solid behavior, I've set it to 2 processes.
too much - Paul *explicitly* recommends 1 and in fact it can't handle more than one at the same time
But delivery is slowwww in this way, at least for the traffic that I have, I have around ~200/250 inbound emails/min
then you need more then once instance on different ports so that each domain can have it's own lmtpd-daemon in transport maps or find a proxy solution between the MTA and dbmail spread incoming mail to the different instances
frankly at such a high amount one has typically not only a single MTA but DNS round robin and each of them has it's own lmtpd-instance connecting to the same database over network
just because with that mail traffic you hardly have a single machine able to process the load of a contentscanner and with a contentscanner and sensible filtering (postscreen with dnsbl scoring...) i doubt the lmtpd will see 250 messages per minute :-)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
