Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: ham destination bugs
Date: Sat, 27 May 2006 12:17:33 +0200	[thread overview]
Message-ID: <v9r72f6abm.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v964nakssy.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 20 Feb 2006 15:29:01 +0100")

On Mon, Feb 20 2006, Reiner Steib wrote:

> On Tue, Feb 14 2006, Reiner Steib wrote:
>
>>   (ham-process-destination ,rs-imap-train-ham-group
>>                            ,rs-imap-inbox-group)
>
> Another oddity using a slightly changed config (exchanged the order of
> rs-imap-train-ham-group and rs-imap-inbox-group because articles in
> rs-imap-train-ham-group are feed to bogofilter and get deleted
> afterwards by a cron job on the IMAP server, so it's more save for me
> to copy to rs-imap-inbox-group first):
[...]
> "misc.Fi" is a completely unrelated group on "nnml+personal" (possibly
> it's the most recently created group on "nnml+personal").  I'm
> puzzled.

I still see this (the appearance of random unrelated groups in
*Messages*).  Ted, are you listening?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2006-05-27 10:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 20:59 Gnus manual update Chong Yidong
2006-02-06 19:18 ` Ted Zlatanov
2006-02-06 20:19   ` Chong Yidong
2006-02-06 20:31     ` spam manual update for Gnus (was: Gnus manual update) Ted Zlatanov
2006-02-06 22:49       ` spam manual update for Gnus Reiner Steib
2006-02-08 20:20         ` Ted Zlatanov
2006-02-08 20:56           ` Chong Yidong
2006-02-09 15:00           ` spam.el: Bugs, compatibility with v5-10 (was: spam manual update for Gnus) Reiner Steib
2006-02-13 19:04             ` spam.el: Bugs, compatibility with v5-10 Ted Zlatanov
2006-02-13 22:36               ` Emacs 20.7 compatibility in v5-10 (was: spam.el: Bugs, compatibility with v5-10) Reiner Steib
2006-03-20 19:51                 ` Emacs 20.7 compatibility in v5-10 Ted Zlatanov
2006-03-20 20:38                   ` Reiner Steib
2006-02-13 19:15             ` ham destination bugs (was: spam.el: Bugs, compatibility with v5-10) Ted Zlatanov
2006-02-14 15:04               ` ham destination bugs Reiner Steib
2006-02-20 14:29                 ` Reiner Steib
2006-05-27 10:17                   ` Reiner Steib [this message]
2006-05-30 13:55                     ` Ted Zlatanov
2006-06-08 20:54                   ` spam.el spam-summary-prepare-exit rewrite (was: ham destination bugs) Ted Zlatanov
2006-04-19 14:23           ` spam manual update for Gnus Reiner Steib
2006-04-20 18:18             ` Ted Zlatanov
2006-04-20 18:38               ` Chong Yidong
2006-04-20 20:08               ` Reiner Steib
2006-04-20 23:20                 ` Miles Bader
2006-04-20 18:45             ` Ted Zlatanov
2006-02-06 20:25   ` message mode screwy (was: Gnus manual update) Ted Zlatanov
2006-02-08 16:52     ` message mode screwy Reiner Steib
2006-02-09 15:37       ` Ted Zlatanov
2006-02-13 18:58         ` Ted Zlatanov
2006-02-13 22:15           ` Adam Sjøgren
2006-02-13 22:39           ` Reiner Steib

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=v9r72f6abm.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@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).