Set X-Original-To based an ORCPT?
Since
http://dovecot.org/pipermail/dovecot-cvs/2014-November/025241.html
Dovecot's LMTP does support ORCPT.
Is it possible to set X-Original-To-Header based on that ORCPT?
Peer
-- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein-support.de
Tel: 030 / 405051-42 Fax: 030 / 405051-19
Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
On 2015-09-02 22:01, Peer Heinlein wrote:
Since
http://dovecot.org/pipermail/dovecot-cvs/2014-November/025241.html
Dovecot's LMTP does support ORCPT.
Is it possible to set X-Original-To-Header based on that ORCPT?
Any news or response on this? I too am in need of this header being passed and saved correctly.
Thanks.
-- Tom
Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command (http://postfix.1071664.n5.nabble.com/pipe-flags-vs-lmtp-td11587.html#a11596).
Be carefully: in this way DSN notification is broken, but they were broken in any case at the time I wrote the patch (read the entire post linked above).
The first patch is for Dovecot 2.2.x: after apply, you cannot disable the DSN advertisement. The other is for Dovecot 2.3.0: you can enable/disable the advertisement using the new bool parameter 'lmtp_lhlo_dsn'.
I'm using it for the past two years, without any problem.
Thanks, Marco
On 2018-08-07 11:48, Tom Sommer wrote:
On 2015-09-02 22:01, Peer Heinlein wrote:
Since
http://dovecot.org/pipermail/dovecot-cvs/2014-November/025241.html
Dovecot's LMTP does support ORCPT.
Is it possible to set X-Original-To-Header based on that ORCPT?
Any news or response on this? I too am in need of this header being passed and saved correctly.
Thanks.
-- Tom
-- Marco Giunta - ITCS SysAdmin Via Bonomea, 265 34136 - Trieste, Italy Tel: +39-040-3787-503 Fax: +39-040-3787-244
On 2018-08-07 13:07, Marco Giunta wrote:
Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command (http://postfix.1071664.n5.nabble.com/pipe-flags-vs-lmtp-td11587.html#a11596).
Be carefully: in this way DSN notification is broken, but they were broken in any case at the time I wrote the patch (read the entire post linked above).
The first patch is for Dovecot 2.2.x: after apply, you cannot disable the DSN advertisement. The other is for Dovecot 2.3.0: you can enable/disable the advertisement using the new bool parameter 'lmtp_lhlo_dsn'.
Interesting that support is actually built in, but simply not advertised.
https://github.com/dovecot/core/commit/38f624b427aa8b6fad3765e6efd97c85a7f97...
Maybe there is a plan?
-- Tom
I really wish this was foxed. this is the only thing preventing me from using LMTP...
On Tue Aug 07 2018 09:29:18 GMT-0400 (Eastern Standard Time), Tom Sommer mail@tomsommer.dk wrote:
On 2018-08-07 13:07, Marco Giunta wrote:
Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command (http://postfix.1071664.n5.nabble.com/pipe-flags-vs-lmtp-td11587.html#a11596).
Be carefully: in this way DSN notification is broken, but they were broken in any case at the time I wrote the patch (read the entire post linked above).
The first patch is for Dovecot 2.2.x: after apply, you cannot disable the DSN advertisement. The other is for Dovecot 2.3.0: you can enable/disable the advertisement using the new bool parameter 'lmtp_lhlo_dsn'.
Interesting that support is actually built in, but simply not advertised.
https://github.com/dovecot/core/commit/38f624b427aa8b6fad3765e6efd97c85a7f97...
Maybe there is a plan?
-- Tom
Op 07/08/2018 om 15:29 schreef Tom Sommer:
On 2018-08-07 13:07, Marco Giunta wrote:
Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command (http://postfix.1071664.n5.nabble.com/pipe-flags-vs-lmtp-td11587.html#a11596).
Be carefully: in this way DSN notification is broken, but they were broken in any case at the time I wrote the patch (read the entire post linked above).
The first patch is for Dovecot 2.2.x: after apply, you cannot disable the DSN advertisement. The other is for Dovecot 2.3.0: you can enable/disable the advertisement using the new bool parameter 'lmtp_lhlo_dsn'.
Interesting that support is actually built in, but simply not advertised.
https://github.com/dovecot/core/commit/38f624b427aa8b6fad3765e6efd97c85a7f97...
That is for Dovecot to Dovecot proxying. It only recognizes the ORCPT parameter. Servers advertising DSN have a responsibility to send the required DSN messages, which Dovecot LMTP currently omits and which is why it doesn't advertise DSN support.
Maybe there is a plan?
There is some talk on the subject. Main problem is that DSN is not documented for LTMP.
Regards,
Stephan.
participants (5)
-
Marco Giunta
-
Peer Heinlein
-
Stephan Bosch
-
Tanstaafl
-
Tom Sommer