Matt,

Thanks for pointing the correct thread, I got lost and could not find it in the list...

There's a workaround for the bug by using RegEx. For example the following:

((?-s)subject:.*refinance)

will search for the word refinance anywhere in the subject. We've been concentrating on implementing the new SPF (Sender Policy Framework) filter and adding antivirus support, so have set aside a public fix for this issue (which contrary to what it may seem is very complex to fix due to the innerworkings of the subject filter...) while the enhancements are completed.

Roberto F.
LogSat Software

Roberto,

Yours was the second post on this thread:

‘Re: How does the Subject: attribute work ?’
Posted by:	LogSat Software Support (‘LogSat Software Support’)
Posted on:	Monday, 7th June 2004
Lee, You are correct, the filter should detect the word in any part of the subject, but it is not. We're classifying this as a bug and will try to patch it as soon as possible. Roberto F. LogSat Software

You'll note there are other threads relating to the same frustrations about keyword filtering of the subject: not working properly as the keyword filtering of message body does. I'm certain that you have just been busy and have overlooked this bug as promised on June 7.

Matt, I was not able to follow the thread. Can you please explain what bug you refer to?

Roberto F.
LogSat Software

This is a significant bug.  Any ideas of when a fix will be available?

Thanks.

Hi Lee,

We try to keep a standard with RegEx by identifying a search string to be RegEx if surrounded by parenthesis. So the correct syntax, if you wish to perform a RegEx search, would be the second:

(Subject:weightloss)

Please note that you may want to add the (?-s) parameter to make the search case-insensitive, as follows:

((?-s)Subject:.weightloss)

Roberto F.
LogSat Software

Roberto I have been working on this Subject: issue and I am a little confused. (whats new) :)

When you use a regex statement in the Subject: field do you put the entire statement in Parens ?  Your example showed the word subject: in parens as well.

So if I wanted to find the word 'weightloss' in the subject would I use

1. Subject:(weightloss) or would it be (Subject:weightloss) ??

I have been using the first example and maybe this is one of my problems.

I poured over the docs before asking because really did want to figure this out without bugging you.

Lee

Roberto, obviously you are a smart guy and so your comments really make me feel a whole lot better. I thought it was just me. :)

If I wanted to write a more criptic piece of code I do not think I could come up with something as complicated as regex.

What surprises me is that someone has not designed a reverse regex builder. Some thing you can put standard search criteria into and have it spit out regex syntax.

I have found a lot of regex testing tools but not a real builder. I ran across some thing called Regexbuddy and Expresso. The express is free.

Thanks again, your comments are reassuring.

Lee

Lee,

Yes, RegEx should help. Can you try something like:

((?-s)subject:.*refinance)

..and we absolutely agree on the German Enigma piece. RegEx nad Perl are the most painful things we've seen....

Roberto F.
LogSat Software

Roberto, (or any one)

If the Subject: doesn't search the entire subject is there a simple way to use a RegEx to do a search in the subject ?

I know everyone is tried of answering Regex questions but for a lot of us it is easier to decode the German Enigma than to figure out regex's. I have learned assembly, Cold Fusion, Javascript a hundred other applications but Regex is painful. :)

If I wanted to search for "re-finance" or "refinance" what would be a basic regex ?  Would (re.?finance) be a valid expression ?

I should say I have download a couple of expression tools but what works in one doesn't seem to work in the SF regex testing tool.

Thanks Lee

Roberto, thanks for the reply and glad to know I was not going nutz. Well maybe I am any way. :o)

I try to read the docs and do a lot of trial and error before posting a message so it's nice to know that I was at least on the right track.

Keep up the great work and the product sure has come along way since you first started.

Lee