Just to keep up with listing the spam gangs; coolestrxever. com
belongs to the taiwantelco/taiwanmedial group. (and is one of their fake
Beverly Hills 90210/90211 addresses). BTW. The latest registrations have
moved back to Turkey (where they started), but use a Pakistani cellular
phone a
Sorry if you see a double post ... it was my bad to forget to
remove the ** spam ** flags in the subject.
Original Message
Subject: Re: SpamAssassin 3.0.2 flags messages from
users@spamassassin.apache.org
Date: Tue, 10 May 2005 16:58:00 -0400
From: Martin G. Diehl <[EM
Sorry if you see a double post ... it was my bad to forget to
remove the ** spam ** flags in the subject.
Original Message
Subject: Re: *SPAM* SpamAssassin 3.0.2 flags messages from
users@spamassassin.apache.org
Date: Tue, 10 May 2005 16:58:00 -0400
From: Martin G. Diehl
Thomas Cameron wrote:
so I whitelist on: List-Id:
Do you mind posting the exact syntax in your local.cf to do this?
All that I was able to find out is that it locally coding and is part
of the user login.
Thanks!
Thomas
--
Martin G. Diehl
ontent-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcVS0HY4PWTqQht5TSKWb96NwD4Y8QAH9gAg
In-Reply-To: <[EMAIL PROTECTED]>
X-Virus-Scanned: by AMaViS - amavis-milter (http://www.amavis.org/)
X-
From: Loren Wilton [mailto:[EMAIL PROTECTED]
>
> Of course, the better way to do this is not let the list mail get to SA in
> the first place.
I let SA mark all my mail. Mail from this list gets sorted out before I
sort out the spam. That way I still have the SA markup in case I want to
look at
On Sun 8 May 05 18:46, "Thomas Cameron" <[EMAIL PROTECTED]>
wrote:
> > so I whitelist on:
> > List-Id:
>
> Do you mind posting the exact syntax in your local.cf to do this?
Well, I think Loren answered it, but I tend to use other filtering tools
to deal with that, so in procmail, I'd do somethi
> > so I whitelist on:
> > List-Id:
>
> Do you mind posting the exact syntax in your local.cf to do this?
Don't know about the OP's, but mine is
header WHITELIST_SA List-Id =~
/(?:dev|users)\.spamassassin\.apache\.org/i
describe WHITELIST_SA SA List
score WHITELIST_SA -100
You can simpl
so I whitelist on:
List-Id:
Do you mind posting the exact syntax in your local.cf to do this?
Thanks!
Thomas
Sorry it took a while ...
On Sat 7 May 05 16:23, "Martin G. Diehl" <[EMAIL PROTECTED]> wrote:
> Joshua Tinnin wrote:
>
> [thanks for your response]
>
> > On Sat 7 May 05 07:01, "Martin G. Diehl" <[EMAIL PROTECTED]> wrote:
> >>Greetings,
> >>
> >>I am seeing some SpamAssassin eMail messages fla
-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcVS0HY4PWTqQht5TSKWb96NwD4Y8QAH9gAg
In-Reply-T
crisppy fernandes wrote:
Dev community,
This is to know from developers community is spamassassin wrked for
anyone just after upgrade or install.
It worked for me, but I had a very simple 2.x install. No Bayes or
anything. I think I had to update Net::DNS and a couple other Perl
modules, but I
It worked well for us, actually, better. To give some light on the
subject, specificly the SURBLS made a HUGE difference in our case. For
the users with not enough spam on their servers, pop a website on goggle
for indexing that contains one of their e-mail addresses and they'll
have plenty :-
Dev community,
This is to know from developers community is spamassassin wrked for
anyone just after upgrade or install.
Everyday one or other new user complaints abt this behaviour that
spamassassin after upgrade to 3.0.x version not seems to wrk.
After checking the man documents or wiki we come
...
>Its part of a larger quote, to the effect that someone with one clock is
>sure of the time, someone withe two clocks isn't and I forget what is
>supposed to happen as you get more clocks. Maybe you get back closer to the
>assurance you had with a single cheap windup clock. I originally came
>...
>From: "List Mail User" <[EMAIL PROTECTED]>
>
>> > ...The person with two clocks is never really sure of
>> > the current time.
>>
>> OT, but... above - *not* a good quote, but it sounds nice)
>> To be `sure' of the time, you need at least three clocks (look at the
>> documentat
> > ...The person with two clocks is never really sure of
> > the current time.
>
> OT, but... above - *not* a good quote, but it sounds nice)
> To be `sure' of the time, you need at least three clocks (look at the
> documentation for ntp/ntpd).
Its part of a larger quote, to the eff
From: "List Mail User" <[EMAIL PROTECTED]>
> > ...The person with two clocks is never really sure of
> > the current time.
>
> OT, but... above - *not* a good quote, but it sounds nice)
> To be `sure' of the time, you need at least three clocks (look at the
> documentation for ntp/n
> ...The person with two clocks is never really sure of
> the current time.
OT, but... above - *not* a good quote, but it sounds nice)
To be `sure' of the time, you need at least three clocks (look at the
documentation for ntp/ntpd).
>
> ...
...
Paul Shupak
> Jens Ahlin wrote:
>> When trying to build rpm using rpmbuild -tb
>> Mail-SpamAssassin-3.0.2.tar.gz
>> fails with
>> error: Failed build dependencies:
>> perl(Digest::SHA1) is needed by spamassassin-3.0.2-1
>> perl(HTML::Parser) is nee
Bob Proulx wrote:
Jens Ahlin wrote:
When trying to build rpm using rpmbuild -tb Mail-SpamAssassin-3.0.2.tar.gz
fails with
error: Failed build dependencies:
perl(Digest::SHA1) is needed by spamassassin-3.0.2-1
perl(HTML::Parser) is needed by spamassassin-3.0.2-1
After installing
Jens Ahlin wrote:
> When trying to build rpm using rpmbuild -tb Mail-SpamAssassin-3.0.2.tar.gz
> fails with
> error: Failed build dependencies:
> perl(Digest::SHA1) is needed by spamassassin-3.0.2-1
> perl(HTML::Parser) is needed by spamassassin-3.0.2-1
>
> A
Hi,
When trying to build rpm using rpmbuild -tb Mail-SpamAssassin-3.0.2.tar.gz
fails with
error: Failed build dependencies:
perl(Digest::SHA1) is needed by spamassassin-3.0.2-1
perl(HTML::Parser) is needed by spamassassin-3.0.2-1
After installing these modules using CPAN rpmbuild
thank you! thank you! thank you!
it works - oh thank you!
:-))
-prash.
On Mon, 28 Feb 2005 21:27:41 -0800, Tom Q. Citizen
<[EMAIL PROTECTED]> wrote:
> Tom Q. Citizen wrote:
>
> > Theo Van Dinter wrote:
> >
> >> On Mon, Feb 28, 2005 at 08:22:01PM -0800, Tom Q. Citizen wrote:
> >>
> >>
> >>> Than
Tom Q. Citizen wrote:
Theo Van Dinter wrote:
On Mon, Feb 28, 2005 at 08:22:01PM -0800, Tom Q. Citizen wrote:
Thanks, I had tried that earlier with no luck. Are there any
guidelines on what kinds of characters are allowed in the rewrite
string? I did notice I had embedded spaces between the p
Theo Van Dinter wrote:
On Mon, Feb 28, 2005 at 08:22:01PM -0800, Tom Q. Citizen wrote:
Thanks, I had tried that earlier with no luck. Are there any guidelines
on what kinds of characters are allowed in the rewrite string? I did
notice I had embedded spaces between the parens and asterisks wh
Theo Van Dinter wrote:
On Mon, Feb 28, 2005 at 08:22:01PM -0800, Tom Q. Citizen wrote:
Thanks, I had tried that earlier with no luck. Are there any guidelines
on what kinds of characters are allowed in the rewrite string? I did
notice I had embedded spaces between the parens and asterisks wh
On Mon, Feb 28, 2005 at 08:22:01PM -0800, Tom Q. Citizen wrote:
> Thanks, I had tried that earlier with no luck. Are there any guidelines
> on what kinds of characters are allowed in the rewrite string? I did
> notice I had embedded spaces between the parens and asterisks which I've
> removed
users@spamassassin.apache.org
Subject: Help needed with rewrite_header and Spamassassin 3.0.2 on Linux
Hi! Ok, I'm running Spamassassin 3.0.2 on a RedHat 9 based Linux box w/
perl 5.8.2 (multi-threaded), netqmail 1.05, and vpopmail 5.4.9. I've
got qmail-scanner 1.25 installed and clamav .083.
Here you go...
http://wiki.apache.org/spamassassin/SubjectRewrite
-Original Message-
From: Tom Q. Citizen [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 10:53 PM
To: users@spamassassin.apache.org
Subject: Help needed with rewrite_header and Spamassassin 3.0.2 on Linux
Hi
Hi! Ok, I'm running Spamassassin 3.0.2 on a RedHat 9 based Linux box w/
perl 5.8.2 (multi-threaded), netqmail 1.05, and vpopmail 5.4.9. I've
got qmail-scanner 1.25 installed and clamav .083. All seems to be
working well except for rewrite_header doesn't seem to be working.
On Tuesday 08 February 2005 07:58 pm, John Andersen wrote:
> On Monday 07 February 2005 08:08 am, Timothy Richter wrote:
> > Good Morning,
> >
> > Recently, we upgraded from Spamassassin 2.61 to 3.0.2. Guinevere is on
> > version 2.17. Our threshold had been 4.9, and we typically blocked 60% of
> >
On Monday 07 February 2005 08:08 am, Timothy Richter wrote:
> Good Morning,
>
> Recently, we upgraded from Spamassassin 2.61 to 3.0.2. Guinevere is on
> version 2.17. Our threshold had been 4.9, and we typically blocked 60% of
> our mail as being spam.
>
> Since the upgrade, we are blocking less th
> Recently, we upgraded from Spamassassin 2.61 to 3.0.2.
> Guinevere is on version 2.17. Our threshold had been 4.9, and
> we typically blocked 60% of our mail as being spam.
>
> Since the upgrade, we are blocking less than have of our
> email as being spam. I have taught the Bayesian filter
>
Good Morning,
Recently, we upgraded from Spamassassin 2.61 to 3.0.2. Guinevere is on version
2.17. Our threshold had been 4.9, and we typically blocked 60% of our mail as
being spam.
Since the upgrade, we are blocking less than have of our email as being spam. I
have taught the Bayesian filter
francois.baert wrote:
> Hello,
>
> Spamassassin-3.0.2 running on redhat9.0
> spamassassin --lint gives a list of warning like this:
> warning: description for REMOVE_PAGE is over 50 chars
> warning: description for FROM_WEBMAIL_END_NUMS6 is over 50 chars
> ...ie
> l
Hello,
Spamassassin-3.0.2 running on redhat9.0
spamassassin --lint gives a list of warning like this:
warning: description for REMOVE_PAGE is over 50 chars
warning: description for FROM_WEBMAIL_END_NUMS6 is over 50 chars
...ie
lint: 171 issues detected.
What does it mean?
Thanks for help
Hello,
I have problem with timeouts on FreeBSD 5.2 with milter-spamc-0.25
(spamass-milter-0.2.0_5 same problem too), p5-Mail-SpamAssassin-3.0.2 .
When I get spam with "X-SpamDetected:1" in header, I get following error
in my maillog :
milter-spamc[585]:timeout before input from SP
What about running a mail through SA on the command line, does that work?
>
> I run spamassassin --lint and didnt got any issue.
> It happens this, when using spamassassin-3.0.0 all goes fine, after i
> intall spamassassin-3.0.2 spammail stops being treated as spam.
>
> Other weird b
At 06:58 AM 1/20/2005, Thomas Kinghorn [MTNNS -Rosebank] wrote:
Is there a way to limit spamd child processes?
# ps -ef | grep spam
root 602 1 0 13:28 ?00:00:12 /usr/bin/spamd -d -c -m5 -H
xadmin 649 602 0 13:29 ?00:00:09 spamd child
xadmin 650 602 0 13:29 ?
Title: Spamassassin 3.0.2 child processes
Hi List.
Is there a way to limit spamd child processes?
# ps -ef | grep spam
root 602 1 0 13:28 ? 00:00:12 /usr/bin/spamd -d -c -m5 -H
xadmin 649 602 0 13:29 ? 00:00:09 spamd child
xadmin 650 602 0 13:29
ing spamassassin-3.0.0 all goes fine, after i intall
spamassassin-3.0.2 spammail stops being treated as spam.
Other weird behaviour is that now with spamassassin-3.0.2 the email that comes
from hotmail (throught the Hotway is a POP3-HTTPMail gateway daemon), and the
email that comes normally to my PO
ing spamassassin-3.0.0 all goes fine, after i intall
spamassassin-3.0.2 spammail stops being treated as spam.
At 10:54 AM 1/15/2005, Zé wrote:
I use mandrake with kde-3.3.2.
After i installed spamassassin-spamc-3.0.2-1mdk stoped classifing spam emails.
No more spam mails were recognized.
Have you checked that SA is working at all by running spamassassin --lint?
It should run silently. If it complains, you
I use mandrake with kde-3.3.2.
After i installed spamassassin-spamc-3.0.2-1mdk stoped classifing spam emails.
No more spam mails were recognized.
Any help?
Thanks Rainer,
> > Well that certainly forced the use of /etc/mail/spamassassin/local.cf,
> > however now I get no mail filtering what so ever. Its like it
> doesn't know
> > about the rules files.
>
> You may run "spamassassin -D --siteconfigpath=/etc/mail/spamassassin <
> /dev/null 2>&1 | grep
On Sun, Jan 09, 2005 at 12:13:12PM +1100, Paul Grenda wrote:
> > use the "--siteconfigpath=/etc/mail/spamassassin" parameter.
> Well that certainly forced the use of /etc/mail/spamassassin/local.cf,
> however now I get no mail filtering what so ever. Its like it doesn't know
> about the rules fi
> -Original Message-
> From: Rainer Sokoll [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 8 January 2005 8:18 PM
> To: users@spamassassin.apache.org
> Subject: Re: SpamAssassin 3.0.2 Path Problems
>
>
> On Sat, Jan 08, 2005 at 12:18:48PM +1100, Paul Grenda wrote:
>
On Sat, Jan 08, 2005 at 12:18:48PM +1100, Paul Grenda wrote:
> After trying to install Spamassasasin 3.0.2 using the rpmbuild withour
> success, I have managed to install it using perl Makefile.PL, make, make
> install and it seems to have been largely sucessful except it no longer
> seems to be a
> no longer seems to be able to find my local.cf (see another thread on this
> forum).
local.cf seems to have moved around in various installs on various platforms.
Search around and see if there is a default local.cf in some other directory,
perhaps
/etc/mail/spamassassin.
Your problem with t
After trying to install Spamassasasin 3.0.2 using the rpmbuild withour
success, I have managed to install it using perl Makefile.PL, make, make
install and it seems to have been largely sucessful except it no longer
seems to be able to find my local.cf (see another thread on this forum).
Now I thi
Loren Wilton wrote:
> > We upgraded from 2.64 to 3.0.2 and now all of a sudden we are getting
> > mails with blank lines in the headers, eg
> Certainly doesn't happen normally.
> The last time someone reported this happening it turned out to be a
> broken version of the integration tool they were
> We upgraded from 2.64 to 3.0.2 and now all of a sudden we are getting
> mails with blank lines in the headers, eg
Certainly doesn't happen normally.
The last time someone reported this happening it turned out to be a broken
version of the integration tool they were using, as best I recall. I th
We upgraded from 2.64 to 3.0.2 and now all of a sudden we are getting
mails with blank lines in the headers, eg
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.com
X-Spam-Level:
X-Spam-Status: No, score=0.4 required=4.0 tests=NO_REAL_NAME,UPPERCASE_25_50
autolearn=no
> Geoff Soper wrote:
>> I run SpamAssassin on my web host's machine. I install it in my directory
>> using:
>>
>> perl Makefile.PL PREFIX=$HOME
>> make
>> make install
>>
>> My problem is that my host doesn't have the Digest::SHA1 module installed.
>> I don't have the ability to install Perl module
Geoff Soper wrote:
I run SpamAssassin on my web host's machine. I install it in my directory
using:
perl Makefile.PL PREFIX=$HOME
make
make install
My problem is that my host doesn't have the Digest::SHA1 module installed.
I don't have the ability to install Perl modules centrally but I can
install
> -Original Message-
> From: Geoff Soper [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 01, 2005 3:49 PM
>
> Unfortunately that's not an option. I have installed the module without
> issue in my space, I don't see a problem with getting SpamAssassin to call
> that module. I just want
users@spamassassin.apache.org
> Subject: Problem installing SpamAssassin 3.0.2
>
>
>
> I run SpamAssassin on my web host's machine. I install it in my directory
> using:
>
> perl Makefile.PL PREFIX=$HOME
> make
> make install
>
> My problem is that my host doesn
Title: Problem installing SpamAssassin 3.0.2
New host?
Your ISP shouldn't have any problems
installing modules like that.
Gary
From: Geoff Soper
[mailto:[EMAIL PROTECTED]Sent: Sat 1/1/2005 10:50
AMTo: users@spamassassin.apache.orgSubject: Problem
installing SpamAssassin 3.0
I run SpamAssassin on my web host's machine. I install it in my directory
using:
perl Makefile.PL PREFIX=$HOME
make
make install
My problem is that my host doesn't have the Digest::SHA1 module installed.
I don't have the ability to install Perl modules centrally but I can
install the module local
SpamAssassin 3.0.2 is released! 3.0.2 contains some important
bugfixes, and is recommended.
Highlights:
- Detect legitimate SMTP AUTH submission, to avoid false positives on
Dynablock-style rules
- Fix URIDNSBL plugin to honor uridnsbl_max_domains config option
- Various documentation
61 matches
Mail list logo
