Kompx.com or Compmiscellanea.com

Imapsync IMAP migration under Windows

Operating systems : Windows

Migrating an IMAP e-mail box from one IMAP server to another under Windows [ 1 ] [ 2 ] by means of imapsync:

  • Copying an e-mail box with all its contents and keeping its folder structure;
  • The e-mail box is hosted at a web hosting company's server and transfered to a common Yandex Mail (not Yandex Mail for Domain);
  • Both IMAP servers support SSL.
  • The process is done in three steps: test run, migrating folder structure, migrating e-mails.

Test run

Content of imapsync-test.bat:


.\imapsync.exe ^
	--host1 imap.domain.ru --user1 email1@domain.ru --password1 "password1" ^
	--host2 imap.yandex.ru --user2 email2@yandex.ru --password2 "password2" ^
	--ssl1 --ssl2 --sslargs1 SSL_verify_mode=0 --sslargs2 SSL_verify_mode=1 ^
	--skipheader "^(?!Message-Id)" ^
	--automap ^
	--regextrans2 "s/^INBOX\.(.+)/$1/" ^
	--addheader ^
	--justfolders ^
	--dry
@PAUSE

Note: the caret character ( ^ ) at the end of line means "this command continues on the next line". It allows to break long command with many options into several parts to put them in several lines for better readability.

This step is meant for testing if imapsync may be run at all, if it can connect to both e-mail boxes and can read the basic structure of the first one. Imapsync runs without actually doing anything, just printing what would have been done without the --dry option. Adding --justfolders is to make testing faster, as imapsync does its job only for folders then.

A log file with full details for each run is placed into the LOG_imapsync folder.

Migrating folder structure

Content of imapsync-folders.bat:


.\imapsync.exe ^
	--host1 imap.domain.ru --user1 email1@domain.ru --password1 "password1" ^
	--host2 imap.yandex.ru --user2 email2@yandex.ru --password2 "password2" ^
	--ssl1 --ssl2 --sslargs1 SSL_verify_mode=0 --sslargs2 SSL_verify_mode=1 ^
	--skipheader "^(?!Message-Id)" ^
	--automap ^
	--regextrans2 "s/^INBOX\.(.+)/$1/" ^
	--addheader ^
	--justfolders
@PAUSE

This step reproduces the folder structure of the e-mail box being migrated in the one it is being migrated to.

Migrating e-mails

Content of imapsync-emails.bat:


.\imapsync.exe ^
	--host1 imap.domain.ru --user1 email1@domain.ru --password1 "password1" ^
	--host2 imap.yandex.ru --user2 email2@yandex.ru --password2 "password2" ^
	--ssl1 --ssl2 --sslargs1 SSL_verify_mode=0 --sslargs2 SSL_verify_mode=1 ^
	--skipheader "^(?!Message-Id)" ^
	--automap ^
	--regextrans2 "s/^INBOX\.(.+)/$1/" ^
	--addheader
@PAUSE

Now e-mails are being copied. If the size of an e-mail with attachment(s) is larger than it is allowed (for Yandex Mail it is not more than 30 megabytes - source), then this particular message is not going to be migrated and there is to be an error mentioned in the log file.


[ 1 ]

Tested under Windows 7.

[ 2 ]

Imapsync IMAP migration under Linux: Imapsync. IMAP migration.


Aliosque subditos et thema

 

Windows console applications. Multimedia

 

MPlayer : FFmpeg Media players appeared long ago, but their heyday began with the mass spread of personal computers powerful enough to play video files. This coincided with the mass spread of operating systems and other software with graphical user interface. However, a program with a graphical user interface is dualistic in its nature: there is a code responsible for graphical user interface, for the appearance and there is a code - for performing the task the given application has been created for in the first place. Both code complexes consume system resources, their response time to user actions makes up certain amount of waiting time. And in cases or concepts when appearance is taken as less important - less important to the point of sparing or almost sparing to employ it - console applications, among others, appear. Moreover, the segmentation of the GUI and of the engine makes it easier to change the graphical user interface or perform complex automated operations. The scheme is implemented for media players for Windows as well. MPlayer, for instance, in its usual form is a console application, starting up quickly, having fast response to user actions, consuming system resources almost entirely for its immediate task. And on this basis if desired, one or another graphical interface may be added for creating, all in all, a new application. MPlayer - / home page / Console media player for Windows. Basis for SMPlayer and UMPlayer. There are versions for Linux, FreeBSD, NetBSD, OpenBSD, Apple Darwin, Mac OS X, QNX, OpenSolaris/Solaris, Irix, HP-UX, AIX, some other *nix system, BeOS, Syllable, AmigaOS, AROS, MorphOS, DOS, Windows. Supported video, audio formats, static images, subtitles, etc. ( List and More extensive list of video and audio codecs ). MPlayer: "Dead Man" MPlayer: "Sky Captain and the World of Tomorrow" MPlayer: "10,000 BC" MPlayer: "13 Tzameti" MPlayer: "The Draughtsman's Contract" MPlayer: "Balzaminov's Marriage" FFmpeg - / home page / Pack of utilities and libraries for work with video and audio files. Created in and for Linux, but there is a Windows variant. Source code may be compiled for some other operating systems. Supported file formats and codecs: ( List ). Also, VLC media player can be run in text mode, ncurses using.

Arachne web browser. Installing and setting up for internet connection via Ethernet

 

A : Installing Arachne web browser on a disk created in RAM - Arachne runs the fastest this way. RAM size should allow for a RAM disk of 6 MB or more. In order to install and set up Arachne web browser for internet connection via Ethernet, there have to be several programs at hand: 1. Arachne web browser [ Download ] 2. If Arachne web browser is to be used for surfing web pages with character encoding other than Latin for West European languages, visit www.glennmcc.org/apm/ to find available character set packages and download the necessary one. 3. Mouse driver, mouse.com for instance [ Download ] 4. Packet driver for Ethernet network card: http://www.crynwr.com/drivers/ http://www.georgpotthast.de/sioux/packet.htm 5. Microsoft Network Client 3.0 [ Download ] 6. NDIS 2.0 driver for Ethernet network card. For example: Realtek RTL8029AS [ Download ]. Drivers for other network cards may be found, for instance, on web sites of Ethernet cards manufacturers. 7. Archivers. For example, PKZIP [ Download ] and PKUNZIP [ Download ] 8. If it is not MS-DOS 6.0+ to be used, QEMM97 [ Download ] 9. If it is not MS-DOS 6.0+ to be used, TDSK [ Download ] Installing and setting up Arachne web browser, step by step: 1. Create a RAM disk. Which drive letter will be assigned to it comes from the assumption that A: and B: go to floppy drives (even if there is only one, both letters will be reserved anyway), C: goes to the first active primary MS-DOS partition on the first physical hard disk. If there are more disks, then there will be as many letters used consecutively as to name them all. Unless there are no devices installed using DRIVER.SYS or similar drivers, the next drive letter will be assigned to the RAM disk. In order to be sure, after having the relevant string for making RAM disk added to CONFIG.SYS (See below), computer could be restarted and what letter is assigned to the RAM disk checked by experiment. In this case, it is E: Depending on RAM size it needs to be decided how many megabytes can be reserved for RAM disk. Basically, the more the better. Since, for instance, web browser cache is going to swell during prolonged and intensive use within a session. In this example the RAM disk is 12 000 KB. The maximum size for RAMDRIVE.SYS MS-DOS driver is 32 767 KB, the one of TDSK - 64 MB. In order to create such a disk, the string has to be added somewhere in the middle of CONFIG.SYS as follows: DEVICE=C:\DOS\RAMDRIVE.SYS 12000 512 512 /E 2. Create a folder, for example C:\DRIVERS\. Put there: a mouse driver, for instance mouse.com, a packet driver for Ethernet network card and a NDIS 2.0 driver for Ethernet network card. 3. Add a string starting mouse driver to AUTOEXEC.BAT. Specify there the full path to the driver, may be any: LH C:\DRIVERS\MOUSE.COM 4. Prepare installation floppies of Microsoft Network Client 3.0: DSK3-1.EXE -d A: DSK3-2.EXE -d A: 5. Start setup.exe from the first floppy and begin Microsoft Network Client 3.0 installation. Installation is starting. Press Enter to continue Select folder for Microsoft Network Client 3.0 to be installed to. It may be any or the suggestion of the installer may be left as it is - in the case discussed it is left as it is.