[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IMAP server-to-server replication?
- To: Simon Josefsson <jas@pdc.kth.se>
- Subject: Re: IMAP server-to-server replication?
- From: Kai.Grossjohann@CS.Uni-Dortmund.DE
- Date: 15 Feb 1999 17:23:12 +0100
- Cc: nnimap@extundo.com
- In-Reply-To: Simon Josefsson's message of "15 Feb 1999 17:00:21 +0100"
- References: <86n22hvqhd.fsf@slowfox.frob.org> <Douglas.K.Eldred-1502990819560001@dkemac.arh.cdc.com> <vafu2wn20sa.fsf@ramses.cs.uni-dortmund.de> <ilu3e471wtm.fsf@squid.pdc.kth.se>
- User-Agent: Gnus/5.070074 (Pterodactyl Gnus v0.74) Emacs/20.3
Simon Josefsson <jas@pdc.kth.se> writes:
> The problem with offline moving of articles with Gnus is that Gnus
> insists on having `nnfoo-request-accept-article' return the article
> number that the article was stored as, and we can't possibly know that
> in disconnected mode. I'm not sure how much of a trouble that would
> be. I'm also not sure if Gnus does anything with the article number
> (hopefully not).
I had a quick peek in the pgnus-0.74 sources. Here's what I found
out:
gnus-msg.el:989:
Here, it is only important whether or not nil was returned.
gnus-sum.el:7187:
Here, the value is used for modifying the Xref header.
nndraft.el:157:
Here, the value is used to associate a file with a new draft
message.
Apparently, only the second one causes problems. Hm. Do you see a
way around this? What does Gnus use the Xref header for; can it be
done without? If the Xref header is needed, can we maybe just adjust
it later, when going online?
Yet another possibility would be to store a copied or moved message in
the nndraft:queue group and have nnagent do its thing when `sending'
the drafts.
kai
--
I like _b_o_t_h kinds of music.