I was under the impression that Dovecot does not look at .forward by default, since of course, Sieve is where that kind of logic should go. However, I'm seeing a .forward file being honoured by the LMTP delivery agent. Is this to be expected?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 2 Dec 2016, MRob wrote:> I was under the impression that Dovecot does not look at .forward by default, > since of course, Sieve is where that kind of logic should go. However, I'm > seeing a .forward file being honoured by the LMTP delivery agent. Is this to > be expected?What version of Dovecot are you using? In my installation the MTA handles .forward. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEUUw3z1H7kL/d9rAQI18Af+PErZBLD76iIaPitbT2dimCgkTAc1jnxT jYsi85LF2QILdWGvqE3KETzSD8U8zx0Nf0krqU7Lj7WgaVnxdMWR2+kt+HsMdsz8 Px8pywSYQWYOwO/I3ELSouZlBuJgMEga/itT9zklLi/NOXQr0qQ9BACAjbk3HdpU 7Mwdx986sBctD6+R+nOaMCj1gB+FHTVmsdktveG9kViyXTGbHJbRFKmZg25T8bir j1c/V4KzsRIjF0pC9Jcxj66rPLdMWKpQqu9jc7MSSC2bdVxnjerRgMdH4xIj/tqV LUjtDqV35/q48kWj814eQ8Hz4exXQ0js55wUPA4dRegwMyVFx73HpQ==blfZ -----END PGP SIGNATURE-----
On 2016-12-04 23:18, Steffen Kaiser wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 2 Dec 2016, MRob wrote: > >> I was under the impression that Dovecot does not look at .forward by >> default, since of course, Sieve is where that kind of logic should go. >> However, I'm seeing a .forward file being honoured by the LMTP >> delivery agent. Is this to be expected? > > What version of Dovecot are you using?2.2.22> In my installation the MTA handles .forward.Using with postfix connected to dovecot's LMTP for delivery. So what you are saying is that postfix first looks at the .forward in the user's home before handing off to dovecot LMTP? Why would it do such a thing?