From: Jake Colman <colman@ppllc.com>
Cc: <ding@gnus.org>
Subject: Re: How To Switch To Another IMAP Server?
Date: 19 Oct 2001 10:45:29 -0400 [thread overview]
Message-ID: <76lmi7r8mu.fsf@newjersey.ppllc.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110191020520.24329-100000@lie.extundo.com> (Simon Josefsson's message of "Fri, 19 Oct 2001 10:23:06 +0200 (CEST)")
Simon,
Are the gnus tick marks actually stored on the IMAP server? I thought they
were an artificial invention of gnus. I cannot imagine how they night have
copied things over such that all the email arrived but not the associated
marks.
...Jake
>>>>> "SJ" == Simon Josefsson <jas@extundo.com> writes:
SJ> On 18 Oct 2001, Jake Colman wrote:
>> My office has decided to replace our current IMAP Server, truman, with
>> a new IMAP Server, hamilton. For the next few days, both servers will
>> be available to me but next week truman will be taken off-line. The
>> SA's have copied all my mailboxes and folders from truman to hamilton
>> and all new email will be sent to hamilton.
>>
>> So how do I tell gnus that I now want it to access hamilton instead of
>> truman? What I have done in the meantime is to subscribe to new
>> nnimap mailboxes on hamilton giving them the same name as they had on
>> truman. This, of course, gave me two entries for each mailbox, one on
>> each server. I have killed (C-k) many of the truman copies of these
>> mailboxes.
>>
>> Questions:
>>
>> 1) Was there a better way to have done this?
SJ> Can't think of one.
>> 2) Some of the truman mailboxes have ticked articles marked with an
>> exclamation point. How do I get the hamilton copies of the messages
>> ticked the same way.
SJ> How was the messages copied between the servers? The flags should be
SJ> copied as well.
>> 3) I still have references to the killed truman mailboxes in my
>> .newsrc.eld.
>> Is this a problem?
SJ> Shouldn't be, but you can probably remove them by running some
SJ> command to kill "zombies" or "killed" groups, or something like that.
>> 4) I currently have entries for both truman and hamilton in my
>> gnus-secondary-select-methods. When I start gnus, it logs on to both
>> servers, prompting me for passwords for both. Great! If I remove
>> truman, I crap out with a lisp error. Before I delve into this and
>> give you a better report, is there something obvious I missed that
>> would cause a problem, perhaps one of the items mentioned above?
SJ> No, it is a bug. Can you post the entire backtrace?
--
Jake Colman
Principia Partners LLC Phone: (201) 946-0300
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman@ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
next prev parent reply other threads:[~2001-10-19 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 0:54 Jake Colman
2001-10-19 8:23 ` Simon Josefsson
2001-10-19 14:45 ` Jake Colman [this message]
2001-10-19 15:16 ` Simon Josefsson
2001-10-19 15:31 ` Jake Colman
2001-10-19 16:36 ` Kai Großjohann
2001-10-19 16:34 ` Kai Großjohann
2001-10-22 16:58 ` Jake Colman
2001-10-22 20:03 ` Kai Großjohann
2001-10-22 20:06 ` Jake Colman
2001-10-19 9:18 ` Kai Großjohann
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=76lmi7r8mu.fsf@newjersey.ppllc.com \
--to=colman@ppllc.com \
--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).