DSN "success" issue caused by pipe process and virtual alias

Hi, I setup a Postfix based plateform whith DSN enabled to support "success" NOTIFY as described below : 1) Mails are forwarded to Cyrus through LMTP ("delivered" action is fixed since thread "LMTP delivery and DSN action value for "success"") 2) mailboxes on Cyrus are internal addresses, virt

RE: LMTP delivery and DSN action value for "success"

>> Hi all. >> I use LMTP transport to deliver mails into Cyrus and when asking >> DSN success I got an action "relayed". > Besides final delivery, LMTP is also used to deliver mail into > content filters. The advantage of LMTP is that the protocol reports > one end-of-message status for each reci

LMTP delivery and DSN action value for "success"

Hi all. I use LMTP transport to deliver mails into Cyrus and when asking DSN success I got an action "relayed". I think LMTP is a final transport like local and virtual mailbox, but the DSN action value for both is "delivered". This should be "delivered" too for LMTP transport ? See example belo