From: Jonathan Larmour <jifl@jifvik.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: [summaries: [SpamCop summary report]]
Date: Tue, 28 Mar 2006 15:43:00 -0000 [thread overview]
Message-ID: <4429597E.5000701@jifvik.org> (raw)
In-Reply-To: <20060324230906.GE599@redhat.com>
Frank Ch. Eigler wrote:
> Hi -
>
> cgf wrote:
>
>
>>>Is there a class of spamassassin test we're not using yet? DNSBL?
>>>URLDNSBL? DCC/Pyzor/etc.? Can qmail callout-verify MAIL FROM:
>>>senders like exim can?
>>
>>/var/log/maillog reports blocks due to URIBL_* and blocks due to
>>BL_IN_SPAMCOP wouldn't that indicate that both are active?
>
>
> The DCC/Pyzor/Razor2 stuff is worth adding, if it's not there already.
Indeed. I've used Razor2 happily. I haven't tried Pyzor or DCC. Checking
against three different checksums may add up to a fair few resources, but
probably less than letting spams through :).
This may be useful:
http://spamassassinbook.packtpub.com/chapter11_preview.htm
>>qpsmtpd verifies RCPT TO: . I have some from addresses blocked. I
>>don't know what you mean by callout-verify.
>
>
> Exim verifies the MAIL FROM: record, by trying to call out to the MX
> server for the claimed originator domain, to try to deliver a dummy
> message back to the claimed email address. It can dispose of or mark
> email whose originating address was fake. My spam file contains many
> hits of this criterion, which spamassassin can incorporate via bayes
> or direct header-testing clauses.
Sounds expensive for a busy mail hub like sourceware though.
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
prev parent reply other threads:[~2006-03-28 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 15:47 Christopher Faylor
2006-03-24 16:12 ` Frank Ch. Eigler
2006-03-24 17:56 ` Christopher Faylor
2006-03-24 23:09 ` Frank Ch. Eigler
2006-03-28 15:43 ` Jonathan Larmour [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4429597E.5000701@jifvik.org \
--to=jifl@jifvik.org \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).