On Sat, Jul 23, 2011 at 08:40:57AM +0200, Paddington Chidziva wrote: > Good day > > I am running a mail server with postfix but my clients who uses the SBS 2008 > pop3 connector are having problems when they send a read/delivery request in > their e-mails. The SBS event viewer says because of invalid headers the pop3 > connector could not download the e-mails. > > I checked on web-mail and saw that the e-mails that cannot be downloaded > have the return path set to mailer daemon. How can I change the return path > on the e-mails that sent back as a delivery/read notification to the > original sender.
The pipe(8) man page (or http://www.postfix.org/pipe.8.html) documentation describes the handling of the error (null) sender address by pipe(8). null_sender=replacement (default: MAILER-DAEMON) Replace the null sender address (typically used for delivery status notifications) with the specified text when expanding the $sender command-line macro, and when generating a From_ or Return-Path: message header. If the null sender replacement text is a non-empty string then it is affected by the q flag for address quoting in command-line arguments. The null sender replacement text may be empty; this form is recommended for content filters that feed mail back into Postfix. The empty sender address is not affected by the q flag for address quoting in command-line arguments. Caution: a null sender address is easily mis-parsed by naive software. For example, when the pipe(8) daemon executes a command such as: Wrong: command -f$sender -- $recipient the command will mis-parse the -f option value when the sender address is a null string. For correct parsing, specify $sender as an argument by itself: Right: command -f $sender -- $recipient This feature is available as of Postfix 2.3. So, just put null_sender= in the pipe(8) transport definition that delivers mail to the POP mailboxes. You can also leave out "R" (or add it if missing) to control the absence or presence of the "Return-Path:" header. -- Viktor.
