LMTP delivery honours .forward by default?
MRob
mrobti at insiberia.net
Tue Dec 6 01:56:30 UTC 2016
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.
More information about the dovecot
mailing list