--- email builder <[EMAIL PROTECTED]> wrote:
> > But again, since almost no legitimate email is ever
> > greylisted only almost nothing DESIRABLE EVER gets
> > delayed.
>
> So you ONLY greylist what the RBLs tell you is on their list? Maybe I need
> to go back and re-read your original emai
> Fascinating the man page seems to indicate this is not one of the options
> for add_header. They mention other headers but not "Report". I guess you
> found a cheat.
What is not one of the options? 'add_header', 'all', and '_REPORT_' are all
mentioned directly in the perldoc for Conf. How is my
> But again, since almost no legitimate email is ever
> greylisted only almost nothing DESIRABLE EVER gets
> delayed.
So you ONLY greylist what the RBLs tell you is on their list? Maybe I need
to go back and re-read your original email, which I skimmed perhaps too
lightly... because even back
--- Herb Martin <[EMAIL PROTECTED]> wrote:
> > I am new to postfix and spamassassin, but we are already
> > using greylist, and I liked a lot what you said here.
> >
> > How can I greylist messages by means of RBL checking? How
> > should I setup Postfix to do that?
> >
> > Regards,
> > Carl
SARE's General Subject rules files and the Whitelist rules files have
been updated.
R> I get from --lint:
R> Failed to run header SpamAssassin tests, skipping some: Global
symbol
R> "$C" requires explicit package name at
R> /etc/spamassassin/70_sare_genlsubj_eng.cf, rule
SARE_SUB_ACCENT_CHAR
To all,
I am running SA 3.0.4 and it has done a great job of blocking most spam. The one thing I still see getting through a lot are survey spam messages. Does anyone else see this problem and if so what rules are you using to combat them. I have most of the SARE Rules on my system. Thanks.
Hi John,
First off, did you modify the rules_du_jour script in any way? It
appears that it is trying to execute the names of the rulesets as
commands. May I see your config file? Are you by chance using this on
cygwin?
John Fleming wrote:
I've had such good results with SA that I haven't
At 05:32 PM Monday, 9/26/2005, Theo Van Dinter wrote -=>
On Mon, Sep 26, 2005 at 01:15:36PM -0700, Ed Kasky wrote:
> FWIW, from here, I see the error in the results from handlespam on every
> message processed.
Ok, I did some more digging. Apparently in 3.1, we reversed the return code
for repo
NFN Smith wrote:
Following up on my own post. I'm still thrashing, and not getting any
difference in results.
...snip...
Sorry, I just have to ask. Since you're using MIMEDefang... you are
remembering to restart (or reload) mimedefang after making your changes,
right? and you're making c
Hi,
Are the rules on the webpage going to be updated ?
I had a weird problem on one of my 20 or so servers where the scanning
time was 4.x seconds vs 0.8 seconds on most others.
Turns out it was the completewhois.com dns lookups failing with
input/output errors, timeouts, etc but a search on
On Mon, Sep 26, 2005 at 01:15:36PM -0700, Ed Kasky wrote:
> FWIW, from here, I see the error in the results from handlespam on every
> message processed.
Ok, I did some more digging. Apparently in 3.1, we reversed the return code
for report_as_spam() to be correct, ie: 1 is ok, 0 is error, which
I've had such good results with SA that I haven't worried about rulesets,
updating rulesets etc. Lately I've had a few getting through and decided it
must be time to update my rulesets. I've decided to use RDJ, but below is
what I get when I run the bash script. Would someone kindly tell me w
From: "Jacob Cord" <[EMAIL PROTECTED]>
Hi everyone,
I've had an awful time trying to figure this one out on my own, and have
been scouring the 'net for someone with a similar problem, but can't
find anything.
I'm converting an existing Postfix (2.0.6)/Procmail setup to use
SpamAssassin. I ins
Hi everyone,
I've had an awful time trying to figure this one out on my own, and have
been scouring the 'net for someone with a similar problem, but can't
find anything.
I'm converting an existing Postfix (2.0.6)/Procmail setup to use
SpamAssassin. I installed SpamAssassin via CPAN.
I followed
From: NFN Smith [mailto:[EMAIL PROTECTED]
>
> Following up on my own post. I'm still thrashing, and not
> getting any
> difference in results.
>
> NFN Smith wrote:
> >
> > OK, I've expanded my settings, but I'm still not making any
> > progress.
> >
> >
> >> trusted_networks64.65.1
At 11:58 AM Monday, 9/26/2005, Theo Van Dinter wrote -=>
On Mon, Sep 26, 2005 at 11:10:19AM -0500, sargon wrote:
> I use Theo's excellent handlespam.pl script for reporting spam. Since
> upgrading to SA 3.1 over the weekend, I see this error when I run the
> script:
>
> (razor) Could not report s
Robert Menschel wrote:
SARE's General Subject rules files and the Whitelist rules files have
been updated.
Note that RDJ has not yet been updated for these two new files.
RDJ is now updated. The new ruleset names are: SARE_WHITELIST_SPF and
SARE_WHITELIST_RCVD
Chris Thiele
Following up on my own post. I'm still thrashing, and not getting any
difference in results.
NFN Smith wrote:
You really do HAVE to trust all your own mail relays. Anything else is
just broken.
Agreed.
OK, I've expanded my settings, but I'm still not making any progress.
trusted_
Hello,
this is my first post to the group. Is the first week i work with
Spamassassin, and i think i have a problem with my performance...
I run SA 3.1 (upgraded from 3.0.4) with Sylpheed-Claws 1.9.14. Each
message take around 12 sec. to be processed. I have dissabled DCC,
Razor2 and Pyzor. The s
On Monday, 26-September-2005 13:58, Theo Van Dinter wrote:
> On Mon, Sep 26, 2005 at 11:10:19AM -0500, sargon wrote:
> > I use Theo's excellent handlespam.pl script for reporting spam.
> > Since upgrading to SA 3.1 over the weekend, I see this error when
> > I run the script:
> >
> > (razor) Could
On Mon, Sep 26, 2005 at 11:10:19AM -0500, sargon wrote:
> I use Theo's excellent handlespam.pl script for reporting spam. Since
> upgrading to SA 3.1 over the weekend, I see this error when I run the
> script:
>
> (razor) Could not report spam to Razor et al!
>
> If I check the Razor log, I see
I use Theo's excellent handlespam.pl script for reporting spam. Since
upgrading to SA 3.1 over the weekend, I see this error when I run the
script:
(razor) Could not report spam to Razor et al!
If I check the Razor log, I see this for the most-recent use of the
script:
Sep 26 11:01:52.038064
Rolf <[EMAIL PROTECTED]> wrote on 09/26/2005
09:17:49 AM:
>
> On 26/09/2005, at 3:07 PM, Robert Menschel wrote:
>
> > SARE's General Subject rules files and the Whitelist rules files
have
> > been updated.
> >
>
> I get from --lint:
>
> Failed to run header SpamAssassin tests, skipping some:
I just recently implemented bayes at our site and was wondering how
token expiration works. I thought that since I left the
'bayes_expiry_max_db_size' and 'bayes_auto_expire' to the default
value of 1, that it would automatically expire the tokens. I run
SpamAssassin through amavisd, and found that
> -Original Message-
> From: Rolf [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 26, 2005 9:18 AM
> To: users@spamassassin.apache.org
> Cc: Robert Menschel
> Subject: Re: [SARE] rules update
>
>
> On 26/09/2005, at 3:07 PM, Robert Menschel wrote:
>
> > SARE's General Subject rules
On Montag, 26. September 2005 15:37 Herb Martin wrote:
> 2) Some SMTP servers (but not enough) will check this
> and disallow forged email from those authorized
> servers
Where "some" is becoming bigger each month. I've seen a lot less
joe-jobbing tries with our domains during the
On 26/09/2005, at 3:07 PM, Robert Menschel wrote:
SARE's General Subject rules files and the Whitelist rules files have
been updated.
I get from --lint:
Failed to run header SpamAssassin tests, skipping some: Global symbol
"$C" requires explicit package name at
/etc/spamassassin/70_sare
> On Sonntag, 25. September 2005 08:54 Herb Martin wrote:
> > [detailed description snipped]
> > If a message gets by all this and is spammy then drop it
> into one of
> > two "spam catch accounts" for review.
>
> Seems to me most of this is "hand made" stuff, and quite a
> good concept, BTW. M
> I am new to postfix and spamassassin, but we are already
> using greylist, and I liked a lot what you said here.
>
> How can I greylist messages by means of RBL checking? How
> should I setup Postfix to do that?
>
> Regards,
> Carlos.
I am not a Postfix expert, and cannot really call myself
> Michael Monnerie wrote:
> > On Sonntag, 25. September 2005 01:35 Steve wrote:
> >> Sorry if this is really simple... any advice would be useful.
> >
> > Not a lot, but SPF helps for that scenario. See http://spf.pobox.com
> >
>
>(Pierre replied):
> I agree; SPF is about the only defense. For
On Mon, Sep 26, 2005 at 08:53:41AM -0400, Matthew Yette wrote:
> Over the last week, I've had to repair the bayes_token table twice. Running
> "repair table bayes_token;" works just fine, but why is this occuring?
> There are currently 1,357,428 rows in it, so it's quite large. Should I be
> runnin
On Sonntag, 25. September 2005 08:54 Herb Martin wrote:
> [detailed description snipped]
> If a message gets by all this and is spammy then
> drop it into one of two "spam catch accounts" for review.
Seems to me most of this is "hand made" stuff, and quite a good concept,
BTW. Maybe it would be g
Michael Monnerie wrote:
> On Sonntag, 25. September 2005 01:35 Steve wrote:
>> Sorry if this is really simple... any advice would be useful.
>
> Not a lot, but SPF helps for that scenario. See http://spf.pobox.com
>
I agree; SPF is about the only defense. For the last few days an address in
on
Hey all -
Over the last week, I've had to repair the bayes_token table twice. Running
"repair table bayes_token;" works just fine, but why is this occuring?
There are currently 1,357,428 rows in it, so it's quite large. Should I be
running and expire script on it?
Thanks,
Matt
--
Matthew Yette
Hi !!
I am new to postfix and spamassassin, but we are already using
greylist, and I liked a lot what you said here.
How can I greylist messages by means of RBL checking? How should I
setup Postfix to do that?
Regards,
Carlos.
2005/9/24, Herb Martin <[EMAIL PROTECTED]>:
> > From: Kai Schaetzl [
Hi Bob,
Thanks for this explanation; It solved my problem.
It turned out in /usr/share/spamassassin a translation-file was causing the
problems.
Cheers,
Thijs
> -Oorspronkelijk bericht-
> Van: Robert Menschel [mailto:[EMAIL PROTECTED]
> Verzonden: zondag 25 september 2005 1:46
> Aan: Th
36 matches
Mail list logo
