Thanks for the help. should also be corrected in the file sender_canonical?
/@gmail.com/ [email protected] /@gmail.cl/ [email protected] /@hotmail.com/ [email protected] /@outlook.com/ [email protected] /@satena.com/ [email protected] /@mayair.com/ [email protected] /@gmail.co/ [email protected] /@octopus.com.co/ [email protected] /@taccolombia.com/ [email protected] /@turpialairlines.com/ [email protected] /@.*/ [email protected] Regards!! On Tue, Apr 19, 2022 at 11:31 AM Wietse Venema <[email protected]> wrote: > Wietse Venema: > > SysAdmin EM: > > > Hi!! > > > > > > I am using the prepend option as follows: > > > > > > / From: (.*@mydomain.com)/ PREPEND Reply to: $1 > > > > > > When the mail arrives I see that it does this way: > > > > > > Reply-to: "[email protected]" <<[email protected] > > > > > > I see an additional symbol added (<) > > > > The '<' was already present in the From: header. > > > > > any help? > > > > If you must do this, why not copy the entire From: value? > > > > /^From:(.+@example\.com\b.+) Reply-To:$1 > > > Correction for missing '/' at te end of the pattern: > > /^From:(.+@example\.com\b.+)/ Reply-To:$1 > > > Note: the \b matches a word boundary, and the \. matches . instead > > of every character. > > > > Test your patterns agains the following: > > > > postmap -q 'From: First Last <[email protected]>' pcre:/path/to/file > > postmap -q 'From: [email protected] (First Last)' pcre:/path/to/file > > > > Wietse > > > > >
