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?
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?
After asking on the postfix list, I learned that postfix only inspects .forward if you use the postfix local delivery agent.
So Dovecot LMTP is doing this - when and why? It's not unwelcome, but I'd like to know how it is configured.
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?
After asking on the postfix list, I learned that postfix only inspects .forward if you use the postfix local delivery agent.
So Dovecot LMTP is doing this - when and why? It's not unwelcome, but I'd like to know how it is configured.
Never mind. Turns out this IS postfix after all.
-----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-----
participants (2)
-
MRob
-
Steffen Kaiser