Re: change return-path to custom value

Razvan Cosma: > Hi - understood. Now, as the messages are received from other hosts, I can't > change the MAIL FROM part of the conversation. Also, as they are sent from > .net (using system.net.mail) the sender application can't change the > envelope sender without changing the From: line too (it'

Re: change return-path to custom value

Hi - understood. Now, as the messages are received from other hosts, I can't change the MAIL FROM part of the conversation. Also, as they are sent from .net (using system.net.mail) the sender application can't change the envelope sender without changing the From: line too (it's a limitation of that

Re: change return-path to custom value

Razvan Cosma: > /^Return-Path: (.*)/REPLACE X-Original-Return-Path: $1 > /^X-bounces-to: (.*)/REPLACE Return-Path: $1 The Return-Path: header DOES NOT CONTROL delivery of bounce messages. Instead, bounce messages are sent to the envelope sender address (the address in the MA

Re: change return-path to custom value

Razvan Cosma a écrit : > Hi everyone, > I am trying to get message bounces/delays piped into a script while > keeping the user-visible From: header intact. To do this, I have asked > the senders to relay through me and include a header of the form > X-bounces-to: scriptal...@mydomain.com >

change return-path to custom value

Hi everyone, I am trying to get message bounces/delays piped into a script while keeping the user-visible From: header intact. To do this, I have asked the senders to relay through me and include a header of the form X-bounces-to: scriptal...@mydomain.com. In the postfix relay host I added main.cf