Re: sender_bcc - patterns questions

2011-08-12 Thread Jeroen Geilman
On 2011-08-12 01:37, Troy Piggins wrote: On Thu, Aug 11, 2011 at 10:02:21AM +1000, Troy Piggins wrote: On Wed, Aug 10, 2011 at 09:47:37AM +0200, Jeroen Geilman wrote: snip / It is not a variable expansion. Use this instead: /(user1)@mydomain.com/ $1_s...@mydomain.com Read

Re: sender_bcc - patterns questions

2011-08-11 Thread Troy Piggins
On Thu, Aug 11, 2011 at 10:02:21AM +1000, Troy Piggins wrote: On Wed, Aug 10, 2011 at 09:47:37AM +0200, Jeroen Geilman wrote: snip / It is not a variable expansion. Use this instead: /(user1)@mydomain.com/ $1_s...@mydomain.com Read http://www.postfix.org/pcre_table.5.html, section

sender_bcc - patterns questions

2011-08-10 Thread Troy Piggins
Hi there, I have a few questions about sender_bcc_maps. Until recently I have been using these to archive sent mail with a hash table like this: us...@mydomain.com user1_s...@mydomain.com and some procmail rules took messages sent to user1_s...@mydomain.com and piped it through gzip into a

Re: sender_bcc - patterns questions

2011-08-10 Thread Ansgar Wiechers
On 2011-08-10 Jeroen Geilman wrote: On 2011-08-10 09:20, Troy Piggins wrote: 2. Can you recommend a better or more elegant solution to the second part of the table with the /us...@mydomain.com/ etc? I tried using something like this: /(user1)@mydomain.com/ \1_s...@mydomain.com but

Re: sender_bcc - patterns questions

2011-08-10 Thread Troy Piggins
On Wed, Aug 10, 2011 at 09:47:37AM +0200, Jeroen Geilman wrote: On 2011-08-10 09:20, Troy Piggins wrote: snip / 1. Could you please confirm that the pattern between the slashes is just the sender's address that we're trying to match? sender_bcc_maps matches the envelope sender address.

Re: sender_bcc - patterns questions

2011-08-10 Thread Troy Piggins
On Wed, Aug 10, 2011 at 10:11:49AM +0200, Ansgar Wiechers wrote: On 2011-08-10 Jeroen Geilman wrote: On 2011-08-10 09:20, Troy Piggins wrote: snip / It is not a variable expansion. Use this instead: /(user1)@mydomain.com/ $1_s...@mydomain.com Read