-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 5 Dec 2016, MRob wrote:
On 2016-12-05 16:37, MRob wrote:
On 2016-12-05 05:53, MRob wrote:
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?
The why: ".forward" is a way to let an user specify a forward address,
IMHO, it origins from the times, when sendmail delivered the messages to
mailboxes in the user's home and when users could manage the mail flow
from their home directory as well.
Maybe just to redirect local deliveries to somewhere else.
Never mind. Turns out this IS postfix after all.
fine you found it. :)
- --
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEVAwUBWEZn1Xz1H7kL/d9rAQL9tQgAgBOgK7oM8Ay2f0DdNpKrgRr3CLELRHva
hTuiYHWWXB44uK4+04tMUP1TuiJUFknO6r7MiNHVNR6CFDEUrlrQAjzaCSOk9nkP
EWX14gyMthxe8JsLkpFFK8ORvdsbMsrfMYIl7fHGFPD/cVlmZd18Hx6ZjXHU1SXD
5dsI2YVX8kE8A+W3VkIpiee9/B+FKgYrxL+Yq0E2OxEMcPxappkNxDD1MHw/Mb7I
v17eB0yXlePH7Ka7d09iYVpgYMZgSu7of0wNKgXeDHQCrIbmD/TYkEl3E9DiI6g8
b386j02f7ay9kWVA8ObM+dTGAKsFMyHcFYbWSswaVNw6wmwqj+UdMQ==
=JSVy
-----END PGP SIGNATURE-----
