IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Could they be "clever" on the back-end?
I switched the Evo setup to use IPs, and starting moving mail. Everything looks good. Then I updated the DNS and sent a test, and it went to the new inbox. Still good.

Then I went to move the last couple of folders, and it started getting flaky. Not always pulling up the message bodies, but not always failing either. I saw a message flash past in the status bar about problems reading 'imap.cooklikeyourgrandmother.com', but the Evo setup isn't using the subdomain any more.

Is it possible I'm hitting it via IP, but the server is redirecting based on DNS?
--

Drew
New It would be very difficult.
It is possible for some of the authentication mechanisms to use the 'name' the client is using to connect, but this would be an unofficial extension. IMAP doesn't otherwise use the hostname the client is using as part of the communication.

There's no also no redirection mechanism. The best it can do it say "no such mailbox" along with an IMAP 'comment' requesting you use a different server. Exchange's IMAP connector does this if you connect to the wrong mailstore, but I don't know of a client that can read this and 'fix' the account. Any workable 'redirection' mechanism would require the server you connect to to proxy the protocol to another server, so you wouldn't notice anyway.

I'd be inclined to think Evolution is making some guesses that it maybe shouldn't be doing. Shut it down - and it's client backend - and give it another go. It is extremely unlikely to lose email in this sort of malfunction as the protocol makes this difficult.

Wade.

Q:Is it proper to eat cheeseburgers with your fingers?
A:No, the fingers should be eaten separately.
New Yep, IMAP seems pretty durable
It looks like Evo was choking on my large mailbox and slow connection. After several restarts I finally got everything. Or at least close enough to everything that I haven't noticed any problems yet.

I took this opportunity to clear out a bunch of old stuff that I was keeping "just in case". I need to start doing what the real-estate company I worked for did: File everything by "keep until" date. If that date comes and something is still in the file, toss it.
--

Drew
     Anyone got a good "how to move email" howto? - (drook) - (21)
         Re: Anyone got a good "how to move email" howto? - (folkert) - (14)
             Only one problem ... well maybe more than one - (drook) - (13)
                 A hosts file is fine. - (static) - (12)
                     But both servers think they serve the same domain - (drook) - (11)
                         IMAP doesn't care. - (static) - (10)
                             Yup, churning away now - (drook) - (6)
                                 IMAP Keeps what the Clients sets. - (folkert) - (5)
                                     Don't have access to the source - (drook) - (1)
                                         Re: Don't have access to the source - (folkert)
                                     No, IMAP-to-IMAP transfer is safer. - (static) - (2)
                                         Re: No, IMAP-to-IMAP transfer is safer. - (folkert) - (1)
                                             If I cared about fast or efficient, sure - (drook)
                             Could they be "clever" on the back-end? - (drook) - (2)
                                 It would be very difficult. - (static) - (1)
                                     Yep, IMAP seems pretty durable - (drook)
         What Greg said. - (static) - (1)
             Evolution will be fine with thousands of messages. - (pwhysall)
         That was my tech-career ender - (mhuber) - (2)
             Good thing he said "we" -NT - (drook) - (1)
                 "we" didn't get fired. -NT - (mhuber)
         Why did I wait so long to do this? - (drook)

(to borrow Ashton's excellent phrase)
68 ms