Apostrohpe Trouble Again

[GoneShootin]

Hi. Recently we experienced issues with email addresses and apostrophes. We recently attempted to implmenet the following Catch-All Rule:

/(.)(payroll\@cxcglobal\.ie)(.)/

But it still fails to grab 'paytroll@cxcglobal.ie' [including wrapped apostrophes]. See below the mail header:


Return-path: <user.name@boigm.com>
Envelope-to: payroll@cxcglobal.ie
Delivery-date: Mon, 28 Jul 2008 15:32:24 +0100
Received: from smtp1.boitib.com ([213.190.148.132] helo=mail2.boigm.com)
by cxcglobal.blacknight.ie with esmtp (Exim 4.60)
(envelope-from <user.name@boigm.com>)
id 1KNTln-0000TO-8M
for payroll@cxcglobal.ie; Mon, 28 Jul 2008 15:32:15 +0100
Received: from unknown (HELO EXCHSRV1.BOIGM.COM) ([19.90.3.205])
by mail2.boigm.com with ESMTP; 28 Jul 2008 15:29:56 +0100
X-IronPort-AV: i="4.31,266,1215385200";
d="scan'208,217"; a="8010306:sNHT78060840"
Received: from EXCHSRV2.BOIGM.COM ([19.90.3.209]) by EXCHSRV1.BOIGM.COM with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 28 Jul 2008 15:32:25 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8F0BE.C1A9EA98"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: FW: Invoice July 2008
Date: Mon, 28 Jul 2008 15:32:20 +0100
Message-ID: <830DA9F36720A949B7B624F01FDE8B2D02A18848@EXCHSRV2 .BOIGM.COM>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Invoice July 2008
Thread-Index: AcjbQgF6xEwIYUECTLKEd5ullG+DcQTz6qGwAGtBzrA=
From: "Name, User" <user.name@boigm.com>
To: "payroll@cxcglobal.ie" <'payroll@cxcglobal.ie'>
X-OriginalArrivalTime: 28 Jul 2008 14:32:25.0990 (UTC) FILETIME=[C170B260:01C8F0BE]
X-Cxcglobal-MailScanner-Information: Please contact the ISP for more information
X-Cxcglobal-MailScanner: Found to be clean
X-Cxcglobal-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-2.098, required 6.5, BAYES_00 -2.60, BOTNET_SERVERWORDS 0.50,
HTML_MESSAGE 0.00)
X-Cxcglobal-MailScanner-From: user.name@boigm.com
X-Spam-Status: No

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F0BE.C1A9EA98
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

=20

________________________________

From: Name, User=20
Sent: 26 July 2008 12:36
To: 'payroll@cxcglobal.ie'
Subject: Invoice July 2008

=20

Hi,

=20

[bear]

/(.)(payroll\@cxcglobal\.ie)(.)/

But it still fails to grab 'paytroll@cxcglobal.ie' [including wrapped apostrophes].

Forgive me, as I don't use the regex or filters in Kayako, but I don't think that regex is correct.
Have you tried:

\'payroll\@cxcglobal\.ie\'

[GoneShootin]

The regex I'm using is what was given to me by Kayako support when I originally rose this issue. You're saying that what they gave me is incorrect?

[bear]

As I mentioned, I'm not using it.
Even if you got it from them, if it's not working, then yes, I'd say it's incorrect.

/(.)(payroll\@cxcglobal\.ie)(.)/
- "/" matches "/" literally
- (.) match any single character as back reference 1 (you can refer to it later as $1)
- (email address) captures the whole email address as back reference #2, escaping the @ and ".")
- (.) back reference #3, single char, etc
- / Literally "/"

How is that supposed to work?
Bearing in mind, I'm not sure of the regex engine they're using, and the tokens may be different

[GoneShootin]

Seems logical. How does your version compare to what I used previously?

Past thread on this : Problem with single quotes around email address

[bear]

It doesn't appear that you've given the regex you were using in that other thread, where you managed to get it working. Was it the same one you gave here?

Your best bet may just be to get back with support and see if they can help.

[GoneShootin]

I wasnt using any regex at the time until support got back to me towards the end of that thread.

Thanks anyway bear. Appreciated.

[John Haugeland]

Originally Posted by GoneShootin

You're saying that what they gave me is incorrect?

It is. @ is not a special character in regex, and should not be quoted. Also, those (.) should be (.*) . I suspect that second (.) shouldn't be there at all.

If you'd tell me where you got that regex, I can help whomever wrote it improve. We're all human, and regex is way too complicated for humans, frankly.

Please describe to me in English the effect you want. /(.*)payroll@cxcglobal\.ie/ would match any address ending in payroll@cxcglobal.ie, such as staffpayroll@cxcglobal.ie ; if that isn't the effect you're after, lemme know what is, and I'll help out.

[John Haugeland]

'paytroll@cxcglobal.ie'

This is a typo, right? (And if not, where can I get a pay troll? There are some outstanding debts I'd love to collect by means of mythical creature.)

[GoneShootin]

John - you're damn right on regex. Sometimes I can get a handle on it, but debugging it drives me simple.

Anyway what I need is to somehow handle single apostrophes at the beginning or end of the email address. So the regex would catch for example

'payroll@cxcglobal.ie'

and then I can have it assigned to the payroll@cxcglobal.ie queue. It should be straightforward, but I think the apostrohpe was escaping whatever regex attempt I made.

I've found the support ticket and pmm'd you details.

[John Haugeland]

Er. Just put the quotes in the regex. The problem isn't the quotes, it's the \ before the @. (I guess it probably didn't help that I referred to that @ as "quoted", which is a programmer phrase; sorry.)

Here's one that should work with or without the quotes:

/(')?payroll@cxcglobal\.ie(')?/

Incidentally, the single quotes are likely to go away soon. That's a defect in the Thunderbird mail client which we are rushing to accomodate.

[GoneShootin]

Here's a question. In my parse log I have a failed item [this is before I've tried your regex suggestion John]. Now with your regex implemented, should I not just be able to "Re-Process" the email? Or does the catch-all rule work only before parsing takes place?

[John Haugeland]

Only before. Sorry.

(I still want a pay troll.)

[GoneShootin]

Originally Posted by John Haugeland

Only before. Sorry.

(I still want a pay troll.)

You'll get one when v3.30 is released to the masses!

[John Haugeland]

You'll get one when v3.30 is released to the masses!

I'm gonna hold you to that. Incidentally, I'd prefer my troll be shipped overnight, to minimize the stress on the poor thing.