Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: New issue: emails get stuck in Mail/Incoming* files
Date: Fri, 30 Oct 2009 01:40:09 -0700 (PDT)	[thread overview]
Message-ID: <22d0703e-7419-48a0-822d-2cd7b7585f44@g23g2000yqh.googlegroups.com> (raw)
In-Reply-To: <mailman.9725.1256886321.2239.info-gnus-english@gnu.org>

Hello Tassilo,

On Oct 30, 8:04 am, Tassilo Horn <tass...@member.fsf.org> wrote:
> Francis Moreau <francis.m...@gmail.com> writes:
>
> Hm, to see where the splitting process delivered a mail, you can use
> this.
>
> ,----[ (info "(gnus)Splitting Mail") ]
> |    If you wish to see where the previous mail split put the messages,
> | you can use the `M-x nnmail-split-history' command.
> `----
>
> But most probably this doesn't show anything, because you said that they
> don't show up in any inbox.

No this doesn't help since the emails seem not going through the split
process and stay at the 'Incoming' stage.

>
> I had a similar thing when upgrading from dovecot 1.1 to 1.2 (that's my
> local imap server).  In 1.1, the dot was used as separator while in 1.2
> it is a /.  So the old foo.bar group didn't get any new messages.  Then,
> I found out that I had to enter the server buffer and subscribe to
> foo/bar and friends, which contained all the new and the old mails.
>

I took a look to the server buffer, but nothing wrong I can notice
unfortunately.

> But I guess you use nnml or nnmaildir, right?

yes I use nnml.

So I guess I need to debug this with a debuger, but I was wondering if
you or someone else have any hints since I'm going to have hard time
to find out what's going on...

Thanks

  parent reply	other threads:[~2009-10-30  8:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 10:41 Francis Moreau
2009-10-29 18:53 ` Tassilo Horn
     [not found] ` <mailman.9692.1256842434.2239.info-gnus-english@gnu.org>
2009-10-29 21:28   ` Francis Moreau
2009-10-30  7:04     ` Tassilo Horn
     [not found]     ` <mailman.9725.1256886321.2239.info-gnus-english@gnu.org>
2009-10-30  8:40       ` Francis Moreau [this message]
2009-10-30 11:49         ` Francis Moreau
2009-10-30 22:32           ` Tassilo Horn
     [not found]           ` <mailman.9758.1256941987.2239.info-gnus-english@gnu.org>
2009-10-31  6:46             ` Francis Moreau
2009-10-31  8:37               ` Tassilo Horn
     [not found]               ` <mailman.9779.1256978304.2239.info-gnus-english@gnu.org>
2009-11-02  8:58                 ` Francis Moreau
2009-11-04 16:33                 ` Francis Moreau
2009-11-05 14:01                   ` Tassilo Horn
     [not found]                   ` <mailman.10125.1257429708.2239.info-gnus-english@gnu.org>
2009-11-06 16:09                     ` Francis Moreau
2009-11-06 22:52                       ` Tassilo Horn
     [not found]                       ` <mailman.10198.1257547993.2239.info-gnus-english@gnu.org>
2009-11-12 20:55                         ` Francis Moreau
2009-10-30 14:17         ` Tassilo Horn
     [not found]         ` <mailman.9732.1256912260.2239.info-gnus-english@gnu.org>
2009-10-30 14:27           ` 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=22d0703e-7419-48a0-822d-2cd7b7585f44@g23g2000yqh.googlegroups.com \
    --to=francis.moro@gmail.com \
    --cc=info-gnus-english@gnu.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).