Gnus development mailing list
 help / color / mirror / Atom feed
From: "Kevin Greiner" <kevin.greiner@compsol.cc>
Subject: Re: imap + agent : moved article NOT deleted from source group
Date: Tue, 22 Nov 2005 23:53:32 -0600	[thread overview]
Message-ID: <200511222353.AA36110456@mail.ev1.net> (raw)


Well, that's nice to hear.  I just ran into gnus-fetch-old-headers 
earlier this week.  This variable is used by the nntp backend to 
override the list of requested headers to fetch a subset.  The 
problem that was previously reported was that gnus fetched the 
same headers each time it entered a group because (of course) it 
bypassed the agent.

Now, you've run into a similar problem with nnml.  Hmmm... It 
looks like nnml simulates the nov database with a local file of 
article headers.  Apparently, the 'B m' command fails to update 
this file as a subsequent call to retrieve header with gnus-fetch-
old-headers fetches the article's old header.

Unless someone volunteers, I'll see what can be done with the 'B 
m' command to keep the nnml nov file in sync.

Kevin

---------- Original Message ----------------------------------
From: Danny Siu <dsiu@adobe.com>
Date: Tue, 22 Nov 2005 11:37:38 -0800

>
>I looked into this problem a little more and found that setting
>gnus-fetch-old-headers to 'nil will fix it.  ie: 'B m' will 
delete the moved
>article from the source group.  I think the header fetch is 
bypassing the
>agent code and that results in some inconsistent NOV entries in 
the agent
>cache.
>
>Na Li writes:
>
>  Na> On  8 Apr 2005, Danny Siu wrote:
>  >> I don't know since when this is happening, but when article 
is 'B m'
>  >> from an IMAP source group to a destination group (same IMAP 
server), it
>  >> is NOT removed from the source group and it is marked 
as 'O'.  I seem
>  >> to recall the moved article is immediately removed from the 
source
>  >> group when doing 'B m'.
>  >> 
>  >> This only happens when agent is enabled.  When I remove the 
IMAP server
>  >> from agent, the article is deleted from the source group - 
which should
>  >> be the correct behaviour I expect.
>
>  Na> I've been haunted by this problem for a while and it is 
really
>  Na> annoying. I would probably have to disable agent for now 
but I then
>  Na> can't read/search emails offline.
>
>  Na> Michael
>
>-- 
>Danny Siu
>
>
 

________________________________________________________________
Sent via the EV1 webmail system at mail.ev1.net


 
                   



             reply	other threads:[~2005-11-23  5:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  5:53 Kevin Greiner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-09  2:51 Danny Siu
2005-10-26  5:47 ` Na Li
2005-11-22 19:37   ` Danny Siu

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=200511222353.AA36110456@mail.ev1.net \
    --to=kevin.greiner@compsol.cc \
    /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).