From: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: bogofilter behavior
Date: Thu, 05 Aug 2004 18:45:03 +0200 [thread overview]
Message-ID: <m3fz71zg8g.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <m34qnhlwhb.fsf@newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> Matthias Andree <matthias.andree@gmx.de> writes:
>
>> Check bogofilter -vvv what it thinks and what token make that message
>> "spammy" - and what the counts were.
>
> Thanks for your response. And I saw your test appear on bogofilter
> group on gmane.
>
> For the record. What I was talking about in my gnu.emacs.gnus post
> was that I had attempted a post on gmane. Got the auto responder and
> responded. Then got a notice that it was a subscribe only list.
Yes indeed it is, to catch the (still only a few messages a day) spam.
> Went to website and subbed.
The subscription needs to be acknowledged before it becomes effective -
but David or I should have seen your post held for moderation and have
then the choice to reject, approve, discard -- and both David and I look
at the posts before deciding.
I'll Bcc: David on this post so he knows what's going on.
> I can't find evidence of any of this on my spools now. I'm not sure
> what went wrong but it seems my messags never got there or something,
> but then why would I get the auto response from gmane...
>
> Maybe I crashed the browser while subbing or something.
>
> Anyway, you've fully answered my questions for now. So I think I'll
> go subscribe again.
I have seen the notification that you are subscribed; if you prefer to
read via GMANE, you can go to the listinfo site (where you have
subscribed) and change your options to "nomail" -- to post, you'd still
send to bogofilter@bogofilter.org.
Followup-To: poster - please answer by mail if there is further need for
discussion.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
prev parent reply other threads:[~2004-08-05 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 10:06 Harry Putnam
[not found] ` <v9zn5cv3hd.fsf@marauder.physik.uni-ulm.de>
2004-08-03 16:19 ` Harry Putnam
[not found] ` <v9d628p0ei.fsf@marauder.physik.uni-ulm.de>
2004-08-03 21:39 ` Harry Putnam
[not found] ` <4nekmmaokh.fsf@lifelogs.com>
[not found] ` <m3oelqt4or.fsf@merlin.emma.line.org>
[not found] ` <4nd625cjag.fsf@lifelogs.com>
2004-08-09 2:00 ` Matthias Andree
[not found] ` <4nvffs6vfs.fsf@lifelogs.com>
[not found] ` <m3fz6v7u7l.fsf@merlin.emma.line.org>
2004-08-10 14:59 ` Ted Zlatanov
[not found] ` <656wo2y8.fsf@blue.sea.net>
[not found] ` <4nvfdzmync.fsf@lifelogs.com>
[not found] ` <v98yavbncv.fsf@marauder.physik.uni-ulm.de>
[not found] ` <4nfz5231ea.fsf@lifelogs.com>
[not found] ` <v9hdpijfgx.fsf@marauder.physik.uni-ulm.de>
[not found] ` <4nd605axsa.fsf@lifelogs.com>
[not found] ` <v9hdpgrb4l.fsf@marauder.physik.uni-ulm.de>
2004-09-30 15:15 ` Ted Zlatanov
2004-10-02 17:11 ` Harry Putnam
2004-10-03 15:45 ` Reiner Steib
[not found] ` <m31ximuk0r.fsf@merlin.emma.line.org>
[not found] ` <m34qnhlwhb.fsf@newsguy.com>
2004-08-05 16:45 ` Matthias Andree [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=m3fz71zg8g.fsf@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
/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 NNTP newsgroup(s).