escaping: must have lost requests

Hi! I tried to run SA 3.1 pre3 and pre4, but I've lots of troubles with lost DNS requests. I tried pre 4 now on (with updated but original perl rpms) redhat 7.3 and FC1-4 on different hosts, networks and DNS (even local caching NS). With or without custom rules...doesn't make any difference.

RE: sa-stats.pl generates a zero report

> -Original Message- > From: Steve Brorens [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 04, 2005 11:18 PM > To: users@spamassassin.apache.org > Subject: RE: sa-stats.pl generates a zero report > > > > Interesting. I get all zeros using either the factory config as shown > *or* the

RE: sa-stats

Did this ever get figured out? I'm running into the same problem, and not matter what options I try I always come back with zeros. Debug shows it's processing the log file. Thanks, Steve > -Original Message- > From: Ben Hanson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 22, 2005 9

Net::DNS::Resolver errors

Hi all, I have just done a fresh install of SA 3.0.4 on a Linux Enterprise release 4 box. All is well except for the pesky Net::DNS::Resolver errors that everyone else seems to have fixed (read through a year's worth of archived messages) without a problem. I cannot however, resolve the proble

Re: sa-stats

As far as I'm concerned it has not been fixed, although I've seen a number of similar threads, and could have missed something else. Worked great until the very moment in time I applied the first 3.10 pre update. No problem with versions 3-3.04. Ben Steve Dimoff wrote: Did this ever get f

Rule for subjects that start with a whitespace

Does anyone know how I would create a rule that detected any subject lines that start with a whitespace? For example: Subject: " This would be tagged as spam" Thanks! Matt -- Matthew Yette Senior Engineer - NOC/Operations MA Polce Consulting, Inc. [EMAIL PROTECTED] 315-838-1644 (w) 315-356-0597

RE: sa-stats

If you call Spamassassin from amavis, the script won't work. On one of my servers I had to change the line that says something like ($sl->{'program'} eq 'spamd') To ($sl->{'program'} eq 'spamassassin') because of how it was getting logged in my maillog. I am runnin

Re: Rule for subjects that start with a whitespace

On Fri, Aug 05, 2005 at 03:09:50PM -0400, Matthew Yette wrote: > Does anyone know how I would create a rule that detected any subject > lines that start with a whitespace? For example: > > Subject: " This would be tagged as spam" By convention, all subjects start with whitespace. "Subject: Re: Ru

RE: Rule for subjects that start with a whitespace

Hmm maybe I wasn't all that clear.. When I wrote quotes, it was just to imply the actual subject. I'm looking to detect messages that have a space before the first letter of the subject. -- Matthew Yette Senior Engineer - NOC/Operations MA Polce Consulting, Inc. [EMAIL PROTECTED] 315-838-1644 (w)

Re: Rule for subjects that start with a whitespace

Matthew Yette wrote: > When I wrote quotes, it was just to imply the actual subject. I'm > looking to detect messages that have a space before the first letter > of the subject. If I recall the appropriate RFC correctly, you're looking for something that - by definition - doesn't exist. Whitespac

Re: Net::DNS::Resolver errors

To reply to my own message: One of my more Perl-savvy co-workers typed: # perl -e "use Net::DNS::Resolver" and found that it was missing the module called "Net::IP" (I don't recall that error when installing Net::DNS::Resolver::Base" (I always ask CPAN to add dependant modules to the queue). N

Re: Rule for subjects that start with a whitespace

Kris Deugau wrote: > If I recall the appropriate RFC correctly, you're looking for > something that - by definition - doesn't exist. Whitespace is > whitespace, so the content of a header begins with the first > non-whitespace character after the colon. I checked

Re: Rule for subjects that start with a whitespace

If I understand you then you are looking at a subject line that looks like this in the raw mail file. Subject: " This would be tagged as spam" This would render in email programs as a subject including the quotes: " This would be tagged as spam" The normal subject header begins with the first non

Re: Rule for subjects that start with a whitespace

From: "Ralph Seichter" <[EMAIL PROTECTED]> > Kris Deugau wrote: > > > If I recall the appropriate RFC correctly, you're looking for > > something that - by definition - doesn't exist. Whitespace is > > whitespace, so the content of a header begins with the first > > non-whitespace character a

RE: sa-stats

10 minutes ago I ran sa-stats.pl for the first time, and receive the same zero output This is how I solved the issue with my setup (qmailrocks.org setup on WBEL4, SpamAssassin-3.0.4) vi sa-stats.pl $opt{'end'} = ""; $opt{'start'} = ""; Then run ./sa-stats.pl -h for options... However, run witho

Re: Rule for subjects that start with a whitespace

jdow wrote: > If I understand you then you are looking at a subject line that looks > like this in the raw mail file. > Subject: " This would be tagged as spam" > > This would render in email programs as a subject including the quotes: > " This would be tagged as spam" > > The normal subject head

GeoCities Link-only spam

Over the last few days, we've been seeing a lot of spam that contains nothing but a pair of names and a link to a URL at uk.geocities.com. No image, no obfuscation, only a small percent has any bayes poison. Just the link and two names. Most of it is pill spam, some mortgage. SURBL can't ca

Re: Rule for subjects that start with a whitespace

Ralph Seichter wrote: > I checked for this: > >2.2. Header Fields >Header fields are lines composed of a field name, followed by a >colon (":"), followed by a field body, and terminated by CRLF. >A field name MUST be composed of printable US-

Re: Rule for subjects that start with a whitespace

From: "Matt Kettler" <[EMAIL PROTECTED]> > jdow wrote: > > If I understand you then you are looking at a subject line that looks > > like this in the raw mail file. > > Subject: " This would be tagged as spam" > > > > This would render in email programs as a subject including the quotes: > > " This

Re: Rule for subjects that start with a whitespace

From: "Kris Deugau" <[EMAIL PROTECTED]> > Ralph Seichter wrote: > > I checked for this: > > > >2.2. Header Fields > >Header fields are lines composed of a field name, followed by a > >colon (":"), followed by a field body, and terminated by CRLF.

Re: Rule for subjects that start with a whitespace

> That said, the rule I think you're looking for might look something > like: > header SUBJ_SPACE_START Subject:raw =~ /^\s+/ > But I don't think that will ever trigger. I was just looking at a bunch of stock market spams last night. One of the most notable characteristics of them was th

Re: Rule for subjects that start with a whitespace

--On Friday, August 05, 2005 6:03 PM -0700 Loren Wilton <[EMAIL PROTECTED]> wrote: I think a lot of mail/news programs assume that the subject body starts immediately after "Subject: ", unless the character immediately after the colon isn't a space, in which case the subject starts there. How

Re: GeoCities Link-only spam

Kelson wrote: Over the last few days, we've been seeing a lot of spam that contains nothing but a pair of names and a link to a URL at uk.geocities.com. No image, no obfuscation, only a small percent has any bayes poison. Just the link and two names. Most of it is pill spam, some mortgage.

Re: Rule for subjects that start with a whitespace

From: "Kenneth Porter" <[EMAIL PROTECTED]> > --On Friday, August 05, 2005 6:03 PM -0700 Loren Wilton > <[EMAIL PROTECTED]> wrote: > > > I think a lot of mail/news programs assume that the subject body starts > > immediately after "Subject: ", unless the character immediately after the > > colon isn

Re: Rule for subjects that start with a whitespace

Matt Kettler wrote: 1) \b is NOT a substitute for spaces. It's zero-width. For things other than the beginning/ending of a rule, use \s unless you REALLY understand the difference. i.e. you should know why /hello\bWorld/ will never match anything. In this case /\"\bT/ would match both " T