Migration Tool?

[ayjayef]

Thanks heaps Ben. I'm glad it works for you!

Firstly, I don't have the directory
Program Files\Mail Enable\CONFIG\Migrate

and I was previously selecting
Capture and create new mailbox where login is valid on remote server and not locally

so it was creating a
Program Files\Mail Enable\CONFIG\Auth\username@domain.txt

...but only if I had the migration tool set to

Configure remote server
POP3
xxx.xxx.xxx.xxx
110


If I set the migration tool to:

Configure remote server
IMAP
xxx.xxx.xxx.xxx
143

It does nothing.


I just did exactly the same as you suggested and when trying the telnet to the POP I got:

+OK Welcome to MailEnable POP3 Server
USER test1@green.com.au
+OK
PASS fred
-ERR Unable to log on

I just downloaded Eurora to the same destination server, installed it, configured a IMAP client and it worked fine reading mail from the source server.


So to recap...
if I set the migration utility to use POP3 it creates the account fine but doesnt pull the mail from the source.

if I set the migration utility to use IMAP it doesnt authenticate.

Any ideas?


edit:

I just tried a command line IMAP from the destination server to the source server and it authenticates fine.

Code: Select all

* OK IMAP4rev1 server ready at 03/06/09 16:33:45
1 LOGIN test1@green.com.au fred
1 OK LOGIN completed
1 LIST " " "%"
* LIST (\HasNoChildren) "/" "Deleted Items"
* LIST (\HasNoChildren) "/" Drafts
* LIST (\HasChildren) "/" INBOX
* LIST (\HasNoChildren) "/" "Sent Items"
* LIST (\HasNoChildren) "/" test1dir
* LIST (\HasNoChildren) "/" test2dir
* LIST (\HasNoChildren) "/" Trash
* LIST (\HasNoChildren) "/" " /Public"
1 OK LIST completed

[ayjayef]

After spending days on this I now have no hair, fingers are bleeding and I think I've been divorced... oh, and I have industrial deafness from the noise in the server room. Apart from that I had great long weekend thanks.

Ok, enough sooking.

So I have since removed ME Enterprise as it was a 3.53 install with a 3.61 upgrade. I guessed if I totally removed it, reinstalled the current version, applied our license key that we are at least starting at a "known good" platform.

Of course, I'm posting this here so that didnt fix it.

I then installed Wireshark to see the traffic.

destination server asks the source server...

Code: Select all

1s CAPABILITY\r\n

source server replies with...

Code: Select all

* OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] source.server.com IMAP4rev1 2001.315rh at Tue, 10 Mar 2009 19:43:00 +1100 (EST)\r\n

destination server asks the source server...

Code: Select all

01ME AUTHENTICATE LOGIN\r\n

source server replies with...

Code: Select all

+ VYNlciBOYW1lAA==\r\n

destination server says to the source server...

Code: Select all

YX5keUBKQwAAAAAAAAAAAAAAAAAAAAAA\r\n

source server replies with...

Code: Select all

+ UHFzc3dvcmQA\r\n

destination server says to the source server...

Code: Select all

PXthd2FaOT0AAAAAAAAAAAAAAAAAAAAAAAA=\r\n

source server replies with Pi55off...

Code: Select all

01ME NO AUTHENTICATE LOGIN failed\r\n

Still awake?

The summary is that the two IMAP servers "meet and sniff bums" fine, its only at the authentication part of the process that it all goes pear-shaped.

from the command line on the destination server I can send...

1 LOGIN user@domain.tld password

...and it works fine.

These two servers are next to each other in the (noisy) server room and I'm happy to pass plain text passwords between them.

I should also note that this is the sercond source server I have tried, 1st one was a registered MailEnable Pro v2.?, the 2nd one is a *nix Readhat server and both have the same results/issue/problem.

Is there a way to turn-off the "01ME AUTHENTICATE LOGIN" part of the Mailenable handshake so it just does a plain text logon?


HELP PLEASE ANYONE
after a week and a half of this I'm going insane.

**insert insane smiley here**
**and another one for the voice in my head here **

[ayjayef]

...another half a week and I can see a sliver of light.

The problem with the migration tool was the two source servers, not the new destination server! Who would have thought that. I (very wrongly) assumed that if I tried to migrate from two different IMAP servers on two different platforms and it didnt work then the problem would be the migration tool.

To help others that end-up in this migration hell...

Source server #1 was a ME Pro v2.x and the fix was to upgrade it to ME Pro v2.53. IT WORKS!

Source server #2 is a "RedHat Release 9 (Shrike)" running IMAP via xinet.d and it is still having grief with the migration.

At least now I can assume its a problem with the linux IMAP and start to troubleshoot that. (wish me LOTS of luck)