> On Mar 6, 2019, at 8:40 AM, Marek Kozlowski <m.kozlow...@mini.pw.edu.pl>
> wrote:
>
> I'm using dovecot for IMAP/POP. I've read that since dovecot 2.0 I may use
> dovecot
> as an LMTP and implement desired solution by adding sieve/pigeon classifier to
> dovecot LMTP. It perfectly(?) integrates with postfix.
The Dovecot LMTP service can be used either directly as a transport
for some set of domains, via transport_maps or via virtual_transport
or even local_transport, or indirectly as the mailbox_transport for
local deliveries after aliases(5) expansion and .forward processing.
Since I generally recommend against using aliases(5) for address to
address rewriting (use virtual(5) instead, and use aliases(5) only
for pipes, and mailman or majordomo mailing lists), unless you need
to support user-managed .forward files (your email users also have
"shell accounts" and have custom .forward files) you can skip
local(8) entirely, and deliver directly to LMTP without indirection
through local delivery and mailbox_transport.
Regardless of how you plug it in your dovecot LMTP server will
be listening on some unix-domain stream or TCP socket, and your
transport definition will direct the mail there.
main.cf:
virtual_transport = lmtp:unix:/some/path
mailbox_transport = lmtp:inet:127.0.0.1:24
local_transport = lmtp:inet:192.0.2.1:24
transport:
example.com lmtp:unix:/some/path
--
Viktor.
