Tim Wilson wrote:
On Wed, Oct 31, 2007 at 8:47 PM, in message
<[EMAIL PROTECTED]>, Darren Ellis
<[EMAIL PROTECTED]> wrote:
I am using ExtractCustomField to try to populate some custom fields by
scanning for values in the body of the incoming message. My regexp
needs to match
Hello Darren,
for historic reason ECFV uses "|" as delimiter in the template. If you use
"|" in your regexp what you do the template will not behave as you might
expect.
You can redefine the separator ECFV uses by inserting a line at the
beginning of your scanner template, e.g.
Separator=<
On Nov 1, 2007, at 9:20 AM, Tim Wilson wrote:
On Wed, Oct 31, 2007 at 8:47 PM, in message
<[EMAIL PROTECTED]>, Darren Ellis
<[EMAIL PROTECTED]> wrote:
I am using ExtractCustomField to try to populate some custom
fields by
scanning for values in the body of the incoming message. My regexp
>>> On Wed, Oct 31, 2007 at 8:47 PM, in message
<[EMAIL PROTECTED]>, Darren Ellis
<[EMAIL PROTECTED]> wrote:
> I am using ExtractCustomField to try to populate some custom fields by
> scanning for values in the body of the incoming message. My regexp
> needs to match a starting string and t
Hello,
I am using ExtractCustomField to try to populate some custom fields by
scanning for values in the body of the incoming message. My regexp
needs to match a starting string and then grab everything to the end
of the line. I have the regexp working with egrep in the bash shell,
but
