Gnus development mailing list
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org
Subject: Re: Issue with nnml backend and gnus-group-get-new-news()
Date: Tue, 1 Dec 2009 13:13:54 +0100	[thread overview]
Message-ID: <38b2ab8a0912010413k7dd402actfda0b1b7352b27af@mail.gmail.com> (raw)
In-Reply-To: <878wdnuigm.fsf@thinkpad.tsdh.de>

Hello Tassilo

Thank you for your time.

On Tue, Dec 1, 2009 at 10:55 AM, Tassilo Horn <tassilo@member.fsf.org> wrote:
> Francis Moreau <francis.moro@gmail.com> writes:
>
> Hi Francis,
>
>> So in my case I pass 2 as argument (C-u 2 g) and all mails from group
>> whose level is 1 or 2 are fetched but no splitted (they're stuck in
>> Incoming files).
>
> Hm, now I was able to receive mails from POP3 accounts into my nnml
> groups.  Those groups are all level 5.  I fetched mail with `5 g', and 2
> new mails were received, stored as Incoming files, split and delivered
> into the right groups.
>
> So at least with my Gnus version (Emacs CVS from yesterday), it seems to
> work.  So either it's a strange misconfiguration on your side, or
> "normal" mail splitting is broken (I use fancy mail splitting), or a bug
> in an older emacs version that's fixed in the meantime.

I'm using Gnus from Emacs CVS which I updated 2 months ago.

>
> Hm, what does M-x nnmail-split-history RET say?

So I tried different values for the prefix and here are the ouptut of
M-x nnmail-split-history for each values. For each values, a mail was
previously sent and should reach my 'Inbox' group.

'g'    Ok -> Inbox:2599
'1 g' Ok -> Inbox:2600

'2 g' Ko -> Inbox:17
'3 g' Ko -> Inbox:18
'4 g' Ko -> Inbox:19
'5 g' Ko -> Inbox:20

'g'    Ok -> Inbox:2601

Ok means that the mail finally was delivered to the right group
('Inbox'), otherwise Ko, the mail is stuck in the 'Incoming' stage.

As you can see the sequence number after "Inbox::" seems to have been
reset in the non working case.

Hope that helps.
-- 
Francis



  reply	other threads:[~2009-12-01 12:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30  9:36 Francis Moreau
2009-11-30  9:53 ` Tassilo Horn
2009-11-30 10:33   ` Francis Moreau
2009-11-30 12:26     ` Tassilo Horn
2009-11-30 13:16       ` Francis Moreau
2009-11-30 13:38         ` Tassilo Horn
2009-11-30 13:48           ` Francis Moreau
2009-12-01  9:55             ` Tassilo Horn
2009-12-01 12:13               ` Francis Moreau [this message]
2009-12-01 20:17                 ` Tassilo Horn
2009-12-02 13:57                   ` Francis Moreau
2009-12-02 23:57                 ` Dan Christensen
2009-12-03  9:11                   ` Francis Moreau
2009-12-03 14:09                     ` Dan Christensen
2009-12-03 21:42                       ` Francis Moreau
2009-12-03 22:10                         ` Dan Christensen
2009-12-08 12:05                           ` Francis Moreau
2009-12-08 14:06                             ` Dan Christensen
2009-12-08 15:17                               ` Francis Moreau
2009-12-09 10:26                               ` Francis Moreau

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=38b2ab8a0912010413k7dd402actfda0b1b7352b27af@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=ding@gnus.org \
    --cc=tassilo@member.fsf.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 NNTP newsgroup(s).