Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nnimap displays wrong article after server move
Date: Fri, 17 Feb 2023 19:23:11 +0100	[thread overview]
Message-ID: <87y1owtals.fsf@dod.no> (raw)
In-Reply-To: <87wn4mheyq.fsf@ericabrahamsen.net>

>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:

> If `gnus-agent-cache' is t, and data is present, Gnus will prefer the
> agent data for that server, even if it's no longer agentized. You'd
> have to shut the agent all the way off (`gnus-agent' -> nil) to ignore
> that data.

Yeah, it's really, really, really, head-thumping-in-table time...

Gnus and gnus agent is not to blame.

dovecot is not to blame.

I and only I am to blame.

Yesterday's email was wiped today, and now I knew for sure I hadn't
deleted anything, even though deleted spam was back... so I looked
again, and my user's crontab on the mailserver had this thing syncing
from the old server (slightly anonymized server name):

0 5 * * * rsync -4 --archive --delete oldserver.mydomain.no:Maildir .

So basically all email received from february 6 (when I switched
servers) and until last midnight is gone, because of --delete.

And heh... the gnus agent that could have helped me, I've also deleted,
since I thought it was to blame.

Oh well! In 100 years' etc. etc.

(And yes. The rsync line has ben scrubbed from my crontab...)



  reply	other threads:[~2023-02-17 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 16:15 "Ghost count" on nnimap group " Steinar Bang
2023-02-10 16:31 ` Steinar Bang
2023-02-11 11:46   ` nnimap displays wrong article after server move (Was: "Ghost count" on nnimap group after server move) Steinar Bang
2023-02-11 11:55     ` nnimap displays wrong article after server move Steinar Bang
2023-02-12 19:16       ` Eric Abrahamsen
2023-02-17 18:23         ` Steinar Bang [this message]
2023-02-18 16:58           ` Eric Abrahamsen
2023-02-19 13:25           ` Eric S Fraga
2023-02-19 16:03             ` Steinar Bang

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=87y1owtals.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.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).