From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Agent: delete agentized message?
Date: Tue, 03 Jun 2003 10:35:35 +0200 [thread overview]
Message-ID: <84smqreey0.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
My boss has his nnimap:INBOX under agent control. There are some
very old articles known to the agent, but they are not on the server
anymore. Hitting `B DEL' on them says `cannot delete article 1054'.
Is it normal for Gnus to behave like that?
I did M-x gnus-agent-regenerate-group RET, but that didn't help. (It
did move all those old articles from ancient status to unread status,
though.)
I then marked some of the old spam as expirable and did M-x
gnus-agent-expire-group RET. That did the job.
WIBNI the Agent would delete its copy of a message when people do B
DEL on an article that isn't on the server?
--
This line is not blank.
next reply other threads:[~2003-06-03 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 8:35 Kai Großjohann [this message]
2003-06-03 9:39 ` Niklas Morberg
2003-06-03 13:34 ` Kai Großjohann
2003-06-04 5:51 ` Kevin Greiner
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=84smqreey0.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.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).