From: Markus Korber <markus.korber@aphona.net>
Subject: Re: Bogofilter and spam.el
Date: Thu, 20 Nov 2003 15:40:12 +0100 [thread overview]
Message-ID: <86k75v3xyr.fsf@titan.aphona.rbgat.net> (raw)
In-Reply-To: <4ny8uccb4s.fsf@lockgroove.bwh.harvard.edu>
Thus spake Ted Zlatanov:
> On Thu, 13 Nov 2003, markus.korber@aphona.net wrote:
>
>> I've problems using spam.el in connection with bogofilter and IMAP.
>>
>> I get new mail with 'g'. However, even though 'S t' in my INBOX
>> indicates a spamicity value of 1.0, spam is sometimes moved to
>> INBOX/spam and sometimes not. If I press 'g' a second time,
>> however, spam is moved. My setup is as follows:
[Debugging 'spam-check-bogofilter-headers' with (debug header) in it.]
> What I'd like to know is whether the header is the same or different
> with `S t' and from the splitting. With nnimap in particular, this
> is possible.
Interesting behaviour: It seems that in case I press 'g' and have
received a spam mail in my INBOX the function is sometimes not called
at all. However, if I press 'g' a second time, it is called.
prev parent reply other threads:[~2003-11-20 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 12:18 Markus Korber
2003-11-19 21:16 ` Ted Zlatanov
2003-11-20 14:40 ` Markus Korber [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=86k75v3xyr.fsf@titan.aphona.rbgat.net \
--to=markus.korber@aphona.net \
/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).