1.1 --- a/README.txt Fri Oct 23 14:37:30 2015 +0200
1.2 +++ b/README.txt Fri Oct 23 20:01:38 2015 +0200
1.3 @@ -255,10 +255,18 @@
1.4 routing to local system users is typically supported "out of the box", this
1.5 can provide a usable solution with minimal effort.
1.6
1.7 +Where the mail system must instead route messages to mailbox providers
1.8 +employing LMTP, some more effort is required. For Exim, some sample
1.9 +configuration files are provided in conf/exim/lmtp to route messages for local
1.10 +users to LMTP endpoints.
1.11 +
1.12 By using LMTP from the agent software, the issue of configuring the mail
1.13 system to integrate with storage solutions is avoided, but then those
1.14 solutions must expose their LMTP interface appropriately.
1.15
1.16 +Configuring Mail Storage Providers for LMTP
1.17 +-------------------------------------------
1.18 +
1.19 Although this topic is largely beyond the scope of this document, systems such
1.20 as Cyrus and Dovecot can be configured to provide a Unix domain socket
1.21 offering support for LMTP connections.
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/conf/exim/lmtp/30_exim4-config_dovecot_lmtp Fri Oct 23 20:01:38 2015 +0200
2.3 @@ -0,0 +1,5 @@
2.4 +dovecot_lmtp:
2.5 + debug_print = "T: dovecot_lmtp for $local_part@$domain"
2.6 + driver = lmtp
2.7 + socket = /var/run/dovecot/lmtp
2.8 + batch_max = 200
3.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
3.2 +++ b/conf/exim/lmtp/890_exim4-config_dovecot_lmtp_local Fri Oct 23 20:01:38 2015 +0200
3.3 @@ -0,0 +1,7 @@
3.4 +dovecot_lmtp_local:
3.5 + debug_print = "R: dovecot_lmtp_local for $local_part@$domain"
3.6 + driver = accept
3.7 + domains = +local_domains
3.8 + local_parts = ! root
3.9 + transport = dovecot_lmtp
3.10 + cannot_route_message = Unknown user