From: Christopher Faylor <me@cgf.cx>
To: "Frank Ch. Eigler" <fche@redhat.com>, overseers@sourceware.org
Subject: Re: [summaries: [SpamCop summary report]]
Date: Fri, 24 Mar 2006 17:56:00 -0000 [thread overview]
Message-ID: <20060324175647.GA27534@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20060324161230.GC599@redhat.com>
On Fri, Mar 24, 2006 at 11:12:30AM -0500, Frank Ch. Eigler wrote:
>Hi -
>
>> [...] Anyone have any insight? The web site isn't very informative
>> about what's going on. [...]
>
>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?
qpsmtpd verifies RCPT TO: . I have some from addresses blocked. I
don't know what you mean by callout-verify.
cgf
next prev parent reply other threads:[~2006-03-24 17:56 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 [this message]
2006-03-24 23:09 ` Frank Ch. Eigler
2006-03-28 15:43 ` Jonathan Larmour
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=20060324175647.GA27534@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--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).