Using the imapsync utility according to your how-to. yum installed with dependencies successfully. All parameters on command line OK. Getting the following error after the "will try" and "From & To" lines: "Can not open imap connection on [host1 ip] with user [username@host1] : IO::Socket::INET: connect: Connection timed out" NOTE: host1 substituted for the actual ip addr. username@host1 substituted for the actual email user. The server on host1 has been operating correctly for almost 4 years. Just doing a migration to a different host. Server is Fedora 8 X64 with Apache, Postfix/Dovecot/Amavis/Clamav/SpamAssassin running on an AMD Athlon 64X2 2.4GHz 4GB. Any help with this error appreciated. SeaHawkJa
netstat -tap output [root@ws1 /]# netstat -tap Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:imaps *:* LISTEN 2192/dovecot tcp 0 0 *op3s *:* LISTEN 2192/dovecot tcp 0 0 *:43907 *:* LISTEN 1858/rpc.statd tcp 0 0 localhost.localdomain:10024 *:* LISTEN 2217/amavisd (maste tcp 0 0 localhost.localdomain:10025 *:* LISTEN 2273/master tcp 0 0 *:mysql *:* LISTEN 2164/mysqld tcp 0 0 *op3 *:* LISTEN 2192/dovecot tcp 0 0 *:imap *:* LISTEN 2192/dovecot tcp 0 0 *:sunrpc *:* LISTEN 1839/rpcbind tcp 0 0 ws1.somename.net:http *:* LISTEN 2301/httpd tcp 0 0 *:ftp *:* LISTEN 2075/vsftpd tcp 0 0 localhost.localdomain:ipp *:* LISTEN 2424/cupsd tcp 0 0 *:smtp *:* LISTEN 2273/master tcp 1 16 ws1.somename.net:smtp sub-228ip138.mio.an:38739 CLOSING - tcp 0 0 ws1.somename.netop3 192.168.0.33:4206 TIME_WAIT - tcp 0 0 *:ssh *:* LISTEN 2049/sshd tcp 0 0 *:https *:* LISTEN 2301/httpd tcp 0 2368 ws1.somename.net:ssh c-my-ip-adr-here.hsd1:cvmmon ESTABLISHED 24242/0
Can do using LAN IP addr Nothing in the firewall blocking imap - I think it is in the server config. As I was using SSH to access the server previously, I decided to go in to the client and try imapsync directly on the server - same timeout result! Tried the quick imap telnet check to server.net 143 and that was a no go. Decided to use server's IP since I was at the site and ...voila - she speaks. So re-ran the imapsync from another station using SSH and the server's IP and off it went. Anyway, since the email migration is the priority now, I am proceeding with that. I still need to check on the server's config to see what's up with the imap 143 blocking for future reference if I have to do this on another server. Thanks for those who took the time to check in on this, and also Falko for your input. SeaHawkJa