Hi Matus (and list :-)
> I'm not Dan. This is a mailing list. Meny people read it and many can
> respond your mail.
Yes, thanks, I had responded to him directly and probably didn't need to,
but the reply-to must not be set to the list address?
/spam sample/ will match the test anywhere on line
On 18.06.09 19:14, MySQL Student wrote:
> Hi Dan,
I'm not Dan. This is a mailing list. Meny people read it and many can
respond your mail.
> > Do I need the backslashes to escape the spaces?
> >
> > no, although \s would be fine.
> Okay, so either \s or nothing at all works just the same?
the \
Hi Dan,
> Do I need the backslashes to escape the spaces?
>
> no, although \s would be fine.
>
Okay, so either \s or nothing at all works just the same?
> this can be much more effectively written as:
> /.spam\ssample./i
> That will match the words "spam sample" in the subject as long as ther
On Thu, 2009-06-18 at 18:01 -0400, MySQL Student wrote:
> I'm also having a problem with one of my rules:
>
> [32692] info: config: invalid expression for rule LOCAL_XPS: "Subject
> =~ /Free\ DELL\ XPS/i": syntax error
>
> Here is the full rule:
>
> meta LOCAL_XPSSubject =~ /F
At 03:01 PM 6/18/2009, you wrote:
Hi. I'm relatively new to spamassassin and perl scripting, and I
must already be doing a few things wrong that I hoped the list could
help me to solve. I'm receiving the following output when running
"spamassassin -D < spam-test.txt 2>&1|less'
[32692] warn: N
Hi. I'm relatively new to spamassassin and perl scripting, and I must
already be doing a few things wrong that I hoped the list could help me to
solve. I'm receiving the following output when running "spamassassin -D <
spam-test.txt 2>&1|less'
[32692] warn: Number found where operator expected at
