Jeff Chan wrote:
Turn on SURBL tests. ecamn.com is blacklisted on SURBL.
Ok. According to
http://wiki.apache.org/spamassassin/SURBL
http://www.surbl.org/faq.html#nettest
SA 3.x have SURBL by default and it should be enabled if I'm not starting spamd with
the -L/--local option. My /etc/de
On Mon, Oct 15, 2007 at 11:53:09PM -0600, Chris 'Xenon' Hanson wrote:
> And yet, sometimes the spam that makes it through is startlingly obvious.
> Lots of expletives about male anatomy and the like, in plaintext mails. I
> turned on the X-Spam-Report header to see how things were going. A typica
Quoting Chris 'Xenon' Hanson <[EMAIL PROTECTED]>:
[...]
> X-Spam-Status: Yes, hits=4.4 required=4.0
> X-Spam-Level:
> X-Spam-Report: SA TESTS
>0.1 FORGED_RCVD_HELO Received: contains a forged HELO
>0.1 HTML_40_50 BODY: Message is 40% to 50% HTML
>0.0 HTML_MESSAGE
OS is an old Debian 3.1/Sarge
SpamAssassin version 3.2.3
running on Perl version 5.8.4
MTA is qmail, from qmailrocks
qmail-scanner 2.01 tweaked with q-s-2.01st-20070204.patch
Also using ClamAV
Qmail, qmail-scanner, clamav and Spamassassin are all running, mail is being filtered, all
is good. S
RB> You can do the equivalent (to turn off delivery) by un-subscribing
RB> from the user's list and subscribing to
RB> [EMAIL PROTECTED]
No wonder.
Be sure to document this wherever you document that there is a mailing
list.
Otherwise users spend hours all the way at the ezmlm mail system
source
Michael Scheidell wrote:
> 3.18 is unsupported.
> please update to latest versions.
>
>
Well, it's as supported or unsupported as any other version of
SpamAssassin is. No version of SpamAssassin is "supported" by the SA
team beyond the advice given on this list. (sure, some third parties
offer
3.18 is unsupported.
please update to latest versions.
--
Michael Scheidell, CTO
Office: 561-999-5000 x 1259
Direct: 561-939-7259
Real time security alerts: http://www.secnap.com/news
_
This email has been scanned and c
On Mon, 15 Oct 2007 at 15:26 -0700, [EMAIL PROTECTED] confabulated:
I have recently moved to a new VPS, everything has been setup for me and is
working well except Spamassassin. (I've never had problems with it on my
previous host and I'm a newbie to working with it, so please excuse my
ignoran
MartyG wrote:
> I have recently moved to a new VPS, everything has been setup for me and is
> working well except Spamassassin. (I've never had problems with it on my
> previous host and I'm a newbie to working with it, so please excuse my
> ignorance.).
>
> Hopefully this might help.
>
> Server: A
jidanni wrote:
> Wish this list would use e.g., mailman, where one can turn off delivery.
You can do the equivalent (to turn off delivery) by un-subscribing from the
user's list and subscribing to [EMAIL PROTECTED] .
--
René Berber
On Monday 15 October 2007 23:52:04 Daryl C. W. O'Shea wrote:
> [EMAIL PROTECTED] wrote:
> > BP> comprised of people who know how email works.
> >
> > Wish this list would use e.g., mailman, where one can turn off delivery.
>
> I wish I had an ice cream cone. :)
>
> We use what the ASF provides to u
I have recently moved to a new VPS, everything has been setup for me and is
working well except Spamassassin. (I've never had problems with it on my
previous host and I'm a newbie to working with it, so please excuse my
ignorance.).
Hopefully this might help.
Server: Apache/1.3.37
Spamassassin
[EMAIL PROTECTED] wrote:
BP> comprised of people who know how email works.
Wish this list would use e.g., mailman, where one can turn off delivery.
I wish I had an ice cream cone. :)
We use what the ASF provides to us for free.
Daryl
BP> comprised of people who know how email works.
Wish this list would use e.g., mailman, where one can turn off delivery.
BP> turn to anti-spam tools and their discussion lists to help.
Indeed I use spamassassin to defend against its own list,
score J_SA_MAILING_LIST 55
as I read this list on g
Karsten Bräckelmann wrote:
> Since
> the localized German descriptions *do* use 8 bit chars, using these
> localized descriptions verbatim in headers *will* result in your
> problem. As hinted in my original, full question:
>
> Anyway, even when using the stock X-Spam-Report header with a Germa
Hi all.
I've just installed Fuzzyocr 3.5.1 with SA 3.1.9 on RHEL 5 (Gifsicle 1.48)
and I've noticed some issues with gifsicle.
2007-10-12 00:18:29 [2581] Trouble parsing 'gifsicle --info' output.
Expected 'image #8', found 'image #7', skipping...
2007-10-12 00:18:29 [2581] Trouble parsing 'gifsic
16 matches
Mail list logo
