Re: [exim] catching newlines with ${sg {}{}{}}

2008-06-20 Thread Marten Lehmann
Hello, Exim uses real PCRE; Philip Hazel is the original author of both. .*\nX-purgate-ID: (.*?)\n.* whereas $1 would contain the id. Unfortunately, the sg expansion item does seem to work with newlines. If you double-check the documentation on ${sg ...} then you'll see the reminder:

Re: [exim] catching newlines with ${sg {}{}{}}

2008-06-20 Thread Phil Pennock
On 2008-06-20 at 14:48 +0200, Marten Lehmann wrote: I read this, but I don't understand where is the difference wether \n is expanded by exim to a newline (without using \N or using \\n) or using \N so PCRE transforms \n to a newline. In this case, not much. Just be sure to also use \$

[exim] catching newlines with ${sg {}{}{}}

2008-06-17 Thread Marten Lehmann
Hello, I need to extract the value X-purgate-ID from $spam_report: X-purgate: Spam X-purgate-ID: 150741::080616223818-6C9786C0-73CE72D8/2129941411-0/0-3 X-purgate-Ad: For more information about eXpurgate please visit http://www.expurgate.net/ With real PCRE, the expression

Re: [exim] catching newlines with ${sg {}{}{}}

2008-06-17 Thread Jakob Hirsch
Marten Lehmann wrote: I need to extract the value X-purgate-ID from $spam_report: X-purgate: Spam X-purgate-ID: 150741::080616223818-6C9786C0-73CE72D8/2129941411-0/0-3 X-purgate-Ad: For more information about eXpurgate please visit http://www.expurgate.net/ Does this work?

Re: [exim] catching newlines with ${sg {}{}{}}

2008-06-17 Thread Phil Pennock
On 2008-06-17 at 20:53 +0200, Marten Lehmann wrote: I need to extract the value X-purgate-ID from $spam_report: X-purgate: Spam X-purgate-ID: 150741::080616223818-6C9786C0-73CE72D8/2129941411-0/0-3 X-purgate-Ad: For more information about eXpurgate please visit