Am 01.11.2013 23:39, schrieb Jorge Bastos: >> still there, you can override most options in the service specific >> section >> >> [LMTP] >> bindip = 127.0.0.1 >> port = 24 >> timeout = 1800 >> banner = LMTP >> max_db_connections = 1 >> file_logging_levels = 511 > > Reindl, > > I'd preffer him to gdb it without touching any configuration
that's another question he asked for options, they are present :-) > I want to upgrade to 3.1x or 3.2x and LMTPD can't crash in any way or form!! AFAIK only in early 3.1 LMTP had troubles with multiple RCPT's my cry out is for sure in the list-archive the last months LMTP is hyperstable maybe the "max_db_connections = 1" for the service and lmtp_destination_concurrency_limit = 1 dbmail-lmtp_destination_concurrency_limit = 1 for postfix are general a good idea, Paul explained why as the bug was a topic, too much beer and whine for seek the archive, LMTP in that context does not need to be multithreaded at all postfix accepts the message and put it in the queue, no need for parallel deliver, in doubt it maybe even faster without concurrency because less concurrency read/write on the mysql side
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
