[SOLVED] CBSubs Mailer -> Conditions

Hi,

Am a little confused about the conditions tab in CBSubs Mailer. There's nothing on it in the CBSubs manual, and I didn't find anything here on the forum, either.

I had a mailer set up and working fine with one condition so far: the CB field named "cb_user_block" must not be 1.

Now I need a second condition: independent of the above field, the user's email must not be of a certain domain ("xyzzy.com" in my example here -- see attachment).

1.) No clue what the "does not contain" in the second condition really means. Is it a query NOT LIKE? Then my string '%@xyz.com' would be right. Or is something else happening there? (Again, nowhere documentation I found, the tooltips are a tad vague, and I can't risk trial & error.)

2.) Confused about the logic of AND or OR in between the two conditions which are both "must be not this". The mailer should not go out if either the CB field is 1 or the mail domain is xyz.com, so OR should be correct, or?

Thank for a quick hint!

1.) No clue what the "does not contain" in the second condition really means. Is it a query NOT LIKE? Then my string '%@xyz.com' would be right. Or is something else happening there? (Again, nowhere documentation I found, the tooltips are a tad vague, and I can't risk trial & error.)

The operator is "Value A does not contain Value B". I'm not sure how to clarify it further than that and is why it is undocumented as it's relatively self explanatory. Example as follows.

Date A, Field A or Value A: Following CB field
CB Field A: email
Date B, Field B or Value B: Constant Value or String (CB substitutions can be used)
Value B: @xyz.com
Condition 1 (> for Dates): Value A does not contain Value B

This means if the email contains @xyz.com (anywhere in the email address) then the mailer won't send for that user.

2.) Confused about the logic of AND or OR in between the two conditions which are both "must be not this". The mailer should not go out if either the CB field is 1 or the mail domain is xyz.com, so OR should be correct, or?

Yes, or should be fine.

Many thanks for the heads-up, Kyle.

Re. #1, yes, if the 'bare-naked' string is to be entered, then that's simple enough and doesn't need further explanation, indeed.

Sorry, too much SQL lately... need to get my head in the sun instead!
Thanks again.