1 OFFLINEIMAP(1) OfflineIMAP Manual OFFLINEIMAP(1)
6 OfflineIMAP - Powerful IMAP/Maildir synchronization and reader support
9 offlineimap [ -1 ] [ -P profiledir ] [ -a accountlist ] [ -c configfile
10 ] [ -d debugtype[,...] ] [ -l filename ] [ -o ] [ -u interface ]
13 offlineimap -h | --help
17 OfflineIMAP is a tool to simplify your e-mail reading. With
18 OfflineIMAP, you can read the same mailbox from multiple computers.
19 You get a current copy of your messages on each computer, and changes
20 you make one place will be visible on all other systems. For instance,
21 you can delete a message on your home computer, and it will appear
22 deleted on your work computer as well. OfflineIMAP is also useful if
23 you want to use a mail reader that does not have IMAP support, has poor
24 IMAP support, or does not provide disconnected operation.
26 OfflineIMAP is FAST; it synchronizes my two accounts with over 50 fold-
27 ers in 3 seconds. Other similar tools might take over a minute, and
28 achieve a less-reliable result. Some mail readers can take over 10
29 minutes to do the same thing, and some don't even support it at all.
30 Unlike other mail tools, OfflineIMAP features a multi-threaded synchro-
31 nization algorithm that can dramatically speed up performance in many
32 situations by synchronizing several different things simultaneously.
34 OfflineIMAP is FLEXIBLE; you can customize which folders are synced via
35 regular expressions, lists, or Python expressions; a versatile and com-
36 prehensive configuration file is used to control behavior; two user
37 interfaces are built-in; fine-tuning of synchronization performance is
38 possible; internal or external automation is supported; SSL and PREAUTH
39 tunnels are both supported; offline (or "unplugged") reading is sup-
40 ported; and esoteric IMAP features are supported to ensure compatibil-
41 ity with the widest variety of IMAP servers.
43 OfflineIMAP is SAFE; it uses an algorithm designed to prevent mail loss
44 at all costs. Because of the design of this algorithm, even program-
45 ming errors should not result in loss of mail. I am so confident in
46 the algorithm that I use my own personal and work accounts for testing
47 of OfflineIMAP pre-release, development, and beta releases. Of course,
48 legally speaking, OfflineIMAP comes with no warranty, so I am not
49 responsible if this turns out to be wrong.
52 OfflineIMAP traditionally operates by maintaining a hierarchy of mail
53 folders in Maildir format locally. Your own mail reader will read mail
54 from this tree, and need never know that the mail comes from IMAP.
55 OfflineIMAP will detect changes to the mail folders on your IMAP server
56 and your own computer and bi-directionally synchronize them, copying,
57 marking, and deleting messages as necessary.
59 With OfflineIMAP 4.0, a powerful new ability has been introduced -- the
60 program can now synchronize two IMAP servers with each other, with no
61 need to have a Maildir layer in-between. Many people use this if they
62 use a mail reader on their local machine that does not support
63 Maildirs. People may install an IMAP server on their local machine,
64 and point both OfflineIMAP and their mail reader of choice at it. This
65 is often preferable to the mail reader's own IMAP support since
66 OfflineIMAP supports many features (offline reading, for one) that most
67 IMAP-aware readers don't. However, this feature is not as time-tested
68 as traditional syncing, so my advice is to stick with normal methods of
69 operation for the time being.
72 If you have already installed OfflineIMAP system-wide, or your system
73 administrator has done that for you, your task for setting up
74 OfflineIMAP for the first time is quite simple. You just need to set
75 up your configuration file, make your folder directory, and run it!
77 You can quickly set up your configuration file. The distribution
78 includes a file offlineimap.conf.minimal (Debian users may find this at
79 /usr/share/doc/offlineimap/examples/offlineimap.conf.minimal) that is a
80 basic example of setting of OfflineIMAP. You can simply copy this file
81 into your home directory and name it .offlineimaprc (note the leading
82 period). A command such as cp offlineimap.conf.minimal
83 ~/.offlineimaprc will do it. Or, if you prefer, you can just copy this
84 text to ~/.offlineimaprc:
90 localrepository = Local
91 remoterepository = Remote
99 remotehost = examplehost
100 remoteuser = jgoerzen
102 Now, edit the ~/.offlineimaprc file with your favorite editor. All you
103 have to do is specify a directory for your folders to be in (on the
104 localfolders line), the host name of your IMAP server (on the remote-
105 host line), and your login name on the remote (on the remoteuser line).
108 To run OfflineIMAP, you just have to say offlineimap -- it will fire
109 up, ask you for a login password if necessary, synchronize your fold-
110 ers, and exit. See? You can just throw away the rest of this finely-
111 crafted, perfectly-honed manual! Of course, if you want to see how you
112 can make OfflineIMAP FIVE TIMES FASTER FOR JUST $19.95 (err, well, $0),
116 If you are reading this document via the "man" command, it is likely
117 that you have no installation tasks to perform; your system administra-
118 tor has already installed it. If you need to install it yourself, you
119 have three options: a system-wide installation with Debian, system-wide
120 installation with other systems, and a single-user installation. You
121 can download the latest version of OfflineIMAP from the OfflineIMAP
122 website <URL:http://quux.org/devel/offlineimap/>.
125 In order to use OfflineIMAP, you need to have these conditions satis-
128 o Your mail server must support IMAP. Most Internet Service Providers
129 and corporate networks do, and most operating systems have an IMAP
130 implementation readily available.
132 o You must have Python version 2.2.1 or above installed. If you are
133 running on Debian GNU/Linux, this requirement will automatically be
134 taken care of for you. If you do not have Python already, check with
135 your system administrator or operating system vendor; or, download it
136 from the Python website <URL:http://www.python.org/>. If you intend
137 to use the Tk interface, you must have Tkinter (python-tk) installed.
138 If you intend to use the SSL interface, your Python must have been
139 built with SSL support.
141 o Have a mail reader that supports the Maildir mailbox format. Most
142 modern mail readers have this support built-in, so you can choose
143 from a wide variety of mail servers. This format is also known as
144 the "qmail" format, so any mail reader compatible with it will work
145 with OfflineIMAP. If you do not have a mail reader that supports
146 Maildir, you can often install a local IMAP server and point both
147 OfflineIMAP and your mail reader at it.
149 SYSTEM-WIDE INSTALLATION, DEBIAN
150 If you are tracking Debian unstable, you may install OfflineIMAP by
151 simply running the following command as root:
153 apt-get install offlineimap
155 If you are not tracking Debian unstable, download the Debian .deb pack-
156 age from the OfflineIMAP website
157 <URL:http://quux.org/devel/offlineimap/> and then run dpkg -i to
158 install the downloaded package. Then, skip to [XRef to CONFIGURATION]
159 below. You will type offlineimap to invoke the program.
161 SYSTEM-WIDE INSTALLATION, OTHER
162 Download the tar.gz version of the package from the website
163 <URL:http://quux.org/devel/offlineimap/>. Then run these commands,
164 making sure that you are the "root" user first:
166 tar -zxvf offlineimap_x.y.z.tar.gz
168 python2.2 setup.py install
170 On some systems, you will need to use python instead of python2.2.
171 Next, proceed to [XRef to CONFIGURATION] below. You will type
172 offlineimap to invoke the program.
174 SINGLE-ACCOUNT INSTALLATION
175 Download the tar.gz version of the package from the website
176 <URL:http://quux.org/devel/offlineimap/>. Then run these commands:
178 tar -zxvf offlineimap_x.y.z.tar.gz
181 When you want to run OfflineIMAP, you will issue the cd command as
182 above and then type ./offlineimap.py; there is no installation step
186 OfflineIMAP is regulated by a configuration file that is normally
187 stored in ~/.offlineimaprc. OfflineIMAP ships with a file named
188 offlineimap.conf that you should copy to that location and then edit.
189 This file is vital to proper operation of the system; it sets every-
190 thing you need to run OfflineIMAP. Full documentation for the configu-
191 ration file is included within the sample file.
193 OfflineIMAP also ships a file named offlineimap.conf.minimal that you
194 can also try. It's useful if you want to get started with the most
195 basic feature set, and you can read about other features later with
199 Most configuration is done via the configuration file. Nevertheless,
200 there are a few command-line options that you may set for OfflineIMAP.
202 -1 Disable most multithreading operations and use solely a single-
203 connection sync. This effectively sets the maxsyncaccounts and
204 all maxconnections configuration file variables to 1.
207 Sets OfflineIMAP into profile mode. The program will create
208 profiledir (it must not already exist). As it runs, Python pro-
209 filing information about each thread is logged into profiledir.
210 Please note: This option is present for debugging and optimiza-
211 tion only, and should NOT be used unless you have a specific
212 reason to do so. It will significantly slow program perfor-
213 mance, may reduce reliability, and can generate huge amounts of
214 data. You must use the -1 option when you use -P.
217 Overrides the accounts option in the general section of the con-
218 figuration file. You might use this to exclude certain
219 accounts, or to sync some accounts that you normally prefer not
220 to. Separate the accounts by commas, and use no embedded
224 Specifies a configuration file to use in lieu of the default,
228 Enables debugging for OfflineIMAP. This is useful if you are
229 trying to track down a malfunction or figure out what is going
230 on under the hood. I suggest that you use this with -1 to make
231 the results more sensible.
233 -d requires one or more debugtypes, separated by commas. These
234 define what exactly will be debugged, and include three options:
235 imap, maildir, and thread. The imap option will enable IMAP
236 protocol stream and parsing debugging. Note that the output may
237 contain passwords, so take care to remove that from the debug-
238 ging output before sending it to anyone else. The maildir
239 option will enable debugging for certain Maildir operations.
240 And thread will debug the threading model.
243 Enables logging to filename. This will log everything that goes
244 to the screen to the specified file. Additionally, if any
245 debugging is specified with -d, then debug messages will not go
246 to the screen, but instead to the logfile only.
248 -o Run only once, ignoring all autorefresh settings in the configu-
253 --help Show summary of options.
256 Specifies an alternative user interface module to use. This
257 overrides the default specified in the configuration file. The
258 pre-defined options are listed in the User Interfaces section.
261 OfflineIMAP has a pluggable user interface system that lets you choose
262 how the program communicates information to you. There are two graphi-
263 cal interfaces, two terminal interfaces, and two noninteractive inter-
264 faces suitable for scripting or logging purposes. The ui option in the
265 configuration file specifies user interface preferences. The -u com-
266 mand-line option can override the configuration file setting. The
267 available values for the configuration file or command-line are
268 described in this section.
271 Tk.Blinkenlights is an interface designed to be sleek, fun to watch,
272 and informative of the overall picture of what OfflineIMAP is doing. I
273 consider it to be the best general-purpose interface in OfflineIMAP.
275 Tk.Blinkenlights contains, by default, a small window with a row of
276 LEDs, a small log, and a row of command buttons. The total size of the
277 window is very small, so it uses little desktop space, yet it is quite
278 functional. The optional, toggleable, log shows more detail about what
279 is happening and is color-coded to match the color of the lights.
281 Tk.Blinkenlights is the only user interface that has configurable
282 parameters; see the example offlineimap.conf for more details.
284 Each light in the Blinkenlights interface represents a thread of execu-
285 tion -- that is, a particular task that OfflineIMAP is performing right
286 now. The colors indicate what task the particular thread is perform-
287 ing, and are as follows:
289 Black indicates that this light's thread has terminated; it will light
290 up again later when new threads start up. So, black indicates
294 is the color of the main program's thread, which basically does
295 nothing but monitor the others. It might remind you of HAL 9000
298 Gray indicates that the thread is establishing a new connection to
301 Purple is the color of an account synchronization thread that is moni-
302 toring the progress of the folders in that account (not generat-
305 Cyan indicates that the thread is syncing a folder.
307 Green means that a folder's message list is being loaded.
309 Blue is the color of a message synchronization controller thread.
311 Orange indicates that an actual message is being copied. (We use fuch-
312 sia for fake messages.)
315 indicates that a message is being deleted.
317 Yellow / bright orange
318 indicates that message flags are being added.
321 indicates that message flags are being removed.
324 corresponds to the countdown timer that runs between synchro-
327 The name of this interfaces derives from a bit of computer history.
328 Eric Raymond's Jargon File defines blinkenlights, in part, as:
331 Front-panel diagnostic lights on a computer, esp. a dinosaur.
332 Now that dinosaurs are rare, this term usually refers to status
333 lights on a modem, network hub, or the like.
335 This term derives from the last word of the famous blackletter-
336 Gothic sign in mangled pseudo-German that once graced about half
337 the computer rooms in the English-speaking world. One version
338 ran in its entirety as follows:
340 ACHTUNG! ALLES LOOKENSPEEPERS!
342 Das computermachine ist nicht fuer gefingerpoken und mitten-
343 grabben. Ist easy schnappen der springenwerk, blowenfusen und
344 poppencorken mit spitzensparken. Ist nicht fuer gewerken bei
345 das dumpkopfen. Das rubbernecken sichtseeren keepen das cotten-
346 pickenen hans in das pockets muss; relaxen und watchen das
350 Curses.Blinkenlights is an interface very similar to Tk.Blinkenlights,
351 but is designed to be run in a console window (an xterm, Linux virtual
352 terminal, etc.) Since it doesn't have access to graphics, it isn't
353 quite as pretty, but it still gets the job done.
355 Please see the Tk.Blinkenlights section above for more information
356 about the colors used in this interface.
359 Tk.VerboseUI (formerly known as Tk.TkUI) is a graphical interface that
360 presents a variable-sized window. In the window, each currently-exe-
361 cuting thread has a section where its name and current status are dis-
362 played. This interface is best suited to people running on slower con-
363 nections, as you get a lot of detail, but for fast connections, the
364 detail may go by too quickly to be useful. People with fast connec-
365 tions may wish to use Tk.Blinkenlights instead.
368 TTY.TTYUI interface is for people running in basic, non-color termi-
369 nals. It prints out basic status messages and is generally friendly to
370 use on a console or xterm.
373 Noninteractive.Basic is designed for situations in which OfflineIMAP
374 will be run non-attended and the status of its execution will be
375 logged. You might use it, for instance, to have the system run auto-
376 matically and e-mail you the results of the synchronization. This user
377 interface is not capable of reading a password from the keyboard;
378 account passwords must be specified using one of the configuration file
382 Noninteractive.Quiet is designed for non-attended running in situations
383 where normal status messages are not desired. It will output nothing
384 except errors and serious warnings. Like Noninteractive.Basic, this
385 user interface is not capable of reading a password from the keyboard;
386 account passwords must be specified using one of the configuration file
390 Here are some example configurations for various situations. Please e-
391 mail any other examples you have that may be useful to me.
393 MULTIPLE ACCOUNTS WITH MUTT
394 This example shows you how to set up OfflineIMAP to synchronize multi-
395 ple accounts with the mutt mail reader.
397 Start by creating a directory to hold your folders by running mkdir
398 ~/Mail. Then, in your ~/.offlineimaprc, specify:
400 accounts = Personal, Work
402 Make sure that you have both an [Account Personal] and an [Account
403 Work] section. The local repository for each account must have differ-
404 ent localfolder path names. Also, make sure to enable [mbnames].
406 In each local repository section, write something like this:
408 localfolders = ~/Mail/Personal
410 Finally, add these lines to your ~/.muttrc:
412 source ~/path-to-mbnames-muttrc-mailboxes
413 folder-hook Personal set from="youremail@personal.com"
414 folder-hook Work set from="youremail@work.com"
415 set mbox_type=Maildir
416 set folder=$HOME/Mail
417 spoolfile=+Personal/INBOX
421 UW-IMAPD AND REFERENCES
422 Some users with a UW-IMAPD server need to use OfflineIMAP's "reference"
423 feature to get at their mailboxes, specifying a reference of "~/Mail"
424 or "#mh/" depending on the configuration. The below configuration from
425 (originally from docwhat@gerf.org) shows using a reference of Mail, a
426 nametrans that strips the leading Mail/ off incoming folder names, and
427 a folderfilter that limits the folders synced to just three.
430 localrepository = GerfLocal
431 remoterepository = GerfRemote
433 [Repository GerfLocal]
435 localfolders = ~/Mail
437 [Repository GerfRemote]
439 remotehost = gerf.org
443 # Trims off the preceeding Mail on all the folder names.
444 nametrans = lambda foldername: \
445 re.sub('^Mail/', '', foldername)
446 # Yeah, you have to mention the Mail dir, even though it
447 # would seem intuitive that reference would trim it.
448 folderfilter = lambda foldername: foldername in [
450 'Mail/list/zaurus-general',
451 'Mail/list/zaurus-dev',
454 holdconnectionopen = no
456 PYTHONFILE CONFIGURATION FILE OPTION
457 You can have OfflineIMAP load up a Python file before evaluating the
458 configuration file options that are Python expressions. This example
459 is based on one supplied by Tommi Virtanen for this feature.
461 In ~/.offlineimap.rc, he adds these options:
464 pythonfile=~/.offlineimap.py
468 Then, the ~/.offlineimap.py file will contain:
470 prioritized = ['INBOX', 'personal', 'announce', 'list']
473 for prefix in prioritized:
474 xsw = x.startswith(prefix)
475 ysw = y.startswith(prefix)
486 folders=os.listdir(os.path.expanduser('~/data/mail/tv@hq.yok.utu.fi'))
490 This code snippet illustrates how the foldersort option can be cus-
491 tomized with a Python function from the pythonfile to always synchro-
492 nize certain folders first.
495 If you get one of some frequently-encountered or confusing errors,
496 please check this section.
498 UID VALIDITY PROBLEM FOR FOLDER
499 IMAP servers use a unique ID (UID) to refer to a specific message.
500 This number is guaranteed to be unique to a particular message forever.
501 No other message in the same folder will ever get the same UID. UIDs
502 are an integral part of OfflineIMAP's synchronization scheme; they are
503 used to match up messages on your computer to messages on the server.
505 Sometimes, the UIDs on the server might get reset. Usually this will
506 happen if you delete and then recreate a folder. When you create a
507 folder, the server will often start the UID back from 1. But
508 OfflineIMAP might still have the UIDs from the previous folder by the
509 same name stored. OfflineIMAP will detect this condition and skip the
510 folder. This is GOOD, because it prevents data loss.
512 You can fix it by removing your local folder and cache data. For
513 instance, if your folders are under ~/Folders and the folder with the
514 problem is INBOX, you'd type this:
516 rm -r ~/Folders/INBOX
517 rm -r ~/.offlineimap/Account-AccountName
518 rm -r ~/.offlineimap/Repository-RepositoryName
520 (Of course, replace AccountName and RepositoryName with the names as
521 specified in ~/.offlineimaprc).
523 Next time you run OfflineIMAP, it will re-download the folder with the
524 new UIDs. Note that the procedure specified above will lose any local
525 changes made to the folder.
527 Some IMAP servers are broken and do not support UIDs properly. If you
528 continue to get this error for all your folders even after performing
529 the above procedure, it is likely that your IMAP server falls into this
530 category. OfflineIMAP is incompatible with such servers. Using
531 OfflineIMAP with them will not destroy any mail, but at the same time,
532 it will not actually synchronize it either. (OfflineIMAP will detect
533 this condition and abort prior to synchronization.)
535 This question comes up frequently on the OfflineIMAP mailing list
536 <URL:http://lists.complete.org/offlineimap@complete.org/>. You can
537 find a detailed discussion <URL:http://lists.com-
538 plete.org/offlineimap@complete.org/2003/04/msg00012.html.gz> of the
541 USE WITH MS EXCHANGE SERVER
542 Several users have reported problems with Microsoft Exchange servers in
543 conjunction with OfflineIMAP. This generally seems to be related to
544 the Exchange servers not properly following the IMAP standards.
546 Mark Biggers has posted some information <URL:http://lists.com-
547 plete.org/offlineimap@complete.org/2005/09/msg00011.html.gz> to the
548 OfflineIMAP mailing list about how he made it work.
550 Other users have indicated that older (5.5) releases of Exchange are so
551 bad that they will likely not work at all.
553 I do not have access to Exchange servers for testing, so any problems
554 with it, if they can even be solved at all, will require help from
555 OfflineIMAP users to find and fix.
557 OTHER FREQUENTLY ASKED QUESTIONS
558 There are some other FAQs that might not fit into another section of
559 the document, so they are discussed here.
561 What platforms does OfflineIMAP run on?
562 It should run on most platforms supported by Python, which are
563 quite a few. I do not support Windows myself, but some have
564 made it work there; see the FAQ entry for that platform.
566 I'm using Mutt. Other IMAP sync programs require me to use "set
567 maildir_trash=yes". Do I need to do that with OfflineIMAP?
568 No. OfflineIMAP is smart enough to figure out message deletion
569 without this extra crutch. You'll get the best results if you
570 don't use this setting, in fact.
572 I've upgraded and now OfflineIMAP crashes when I start it up! Why?
573 You need to upgrade your configuration file. See [XRef to
574 UPGRADING.4.0] at the end of this manual.
576 How do I specify the names of my folders?
577 You do not need to. OfflineIMAP is smart enough to automati-
578 cally figure out what folders are present on the IMAP server and
579 synchronize them. You can use the folderfilter and nametrans
580 configuration file options to request certain folders and rename
581 them as they come in if you like.
583 How can I prevent certain folders from being synced?
584 Use the folderfilter option in the configuration file.
586 How can I add or delete a folder?
587 OfflineIMAP does not currently provide this feature, but if you
588 create a new folder on the IMAP server, it will be created
589 locally automatically.
591 Are there any other warnings that I should be aware of?
592 Yes; see the Notes section below.
594 What is the mailbox name recorder (mbnames) for?
595 Some mail readers, such as Mutt, are not capable of automati-
596 cally determining the names of your mailboxes. OfflineIMAP can
597 help these programs by writing the names of the folders in a
598 format you specify. See the example offlineimap.conf for
601 Can I synchronize multiple accounts with OfflineIMAP?
602 Sure. Just name them all in the accounts line in the general
603 section of the configuration file, and add a per-account section
606 Does OfflineIMAP support POP?
607 No. POP is not robust enough to do a completely reliable multi-
608 machine synchronization like OfflineIMAP can do. OfflineIMAP
611 Does OfflineIMAP support mailbox formats other than Maildir?
612 Not at present. There is no technical reason not to; just no
613 demand yet. Maildir is a superior format anyway. However,
614 OfflineIMAP can sync between two IMAP servers, and some IMAP
615 servers support other formats. You could install an IMAP server
616 on your local machine and have OfflineIMAP sync to that.
618 [technical] Why are your Maildir message filenames so huge?
619 OfflineIMAP has two relevant principles: 1) never modifying your
620 messages in any way and 2) ensuring 100% reliable synchroniza-
621 tions. In order to do a reliable sync, OfflineIMAP must have a
622 way to uniquely identify each e-mail. Three pieces of informa-
623 tion are required to do this: your account name, the folder
624 name, and the message UID. The account name can be calculated
625 from the path in which your messages are. The folder name can
626 usually be as well, BUT some mail clients move messages between
627 folders by simply moving the file, leaving the name intact.
629 So, OfflineIMAP must store both a UID folder ID. The folder ID
630 is necessary so OfflineIMAP can detect a message moved to a dif-
631 ferent folder. OfflineIMAP stores the UID (U= number) and an
632 md5sum of the foldername (FMD5= number) to facilitate this.
634 What is the speed of OfflineIMAP's sync?
635 OfflineIMAP versions 2.0 and above contain a multithreaded sys-
636 tem. A good way to experiment is by setting maxsyncaccounts to
637 3 and maxconnections to 3 in each account clause.
639 This lets OfflineIMAP open up multiple connections simultane-
640 ously. That will let it process multiple folders and messages
641 at once. In most cases, this will increase performance of the
644 Don't set the number too high. If you do that, things might
645 actually slow down as your link gets saturated. Also, too many
646 connections can cause mail servers to have excessive load.
647 Administrators might take unkindly to this, and the server might
648 bog down. There are many variables in the optimal setting;
649 experimentation may help.
651 An informal benchmark yields these results for my setup:
653 o 10 minutes with MacOS X Mail.app "manual cache"
655 o 5 minutes with GNUS agent sync
657 o 20 seconds with OfflineIMAP 1.x
659 o 9 seconds with OfflineIMAP 2.x
661 o 3 seconds with OfflineIMAP 3.x "cold start"
663 o 2 seconds with OfflineIMAP 3.x "held connection"
665 Can I use OfflineIMAP on Windows?
666 These answers have been reported by OfflineIMAP users. I do not
667 run OfflineIMAP on Windows myself, so I can't directly address
670 The basic answer is that it's possible and doesn't require hack-
671 ing OfflineIMAP source code. However, it's not necessarily
672 trivial. The information below is based in instructions submit-
675 First, you must run OfflineIMAP in the Cygwin
676 <URL:http://www.cygwin.com/> environment.
678 Next, you'll need to mount your Maildir directory in a special
679 way. There is information for doing that at
680 <URL:http://barnson.org/node/view/295>. That site gives this
683 mount -f -s -b -o managed "d:/tmp/mail" "/home/of/mail"
686 That URL also has more details on making OfflineIMAP work with
690 o Internet Message Access Protocol version 4rev1 (IMAP 4rev1) as speci-
691 fied in RFC2060 and RFC3501
693 o CRAM-MD5 as specified in RFC2195
695 o Maildir as specified in the Maildir manpage
696 <URL:http://www.qmail.org/qmail-manual-html/man5/maildir.html> and
697 the qmail website <URL:http://cr.yp.to/proto/maildir.html>.
699 o Standard Python 2.2.1 as implemented on POSIX-compliant systems.
702 DELETING LOCAL FOLDERS
703 OfflineIMAP does a two-way synchronization. That is, if you make a
704 change to the mail on the server, it will be propagated to your local
705 copy, and vise-versa. Some people might think that it would be wise to
706 just delete all their local mail folders periodically. If you do this
707 with OfflineIMAP, remember to also remove your local status cache
708 (~/.offlineimap by default). Otherwise, OfflineIMAP will take this as
709 an intentional deletion of many messages and will interpret your action
710 as requesting them to be deleted from the server as well. (If you
711 don't understand this, don't worry; you probably won't encounter this
715 OfflineIMAP is not designed to have several instances (for instance, a
716 cron job and an interactive invocation) run over the same mailbox
717 simultaneously. It will perform a check on startup and abort if
718 another OfflineIMAP is already running. If you need to schedule syn-
719 chronizations, please use the autorefresh settings rather than cron.
720 Alternatively, you can set a separate metadata directory for each
723 COPYING MESSAGES BETWEEN FOLDERS
724 Normally, when you copy a message between folders or add a new message
725 to a folder locally, OfflineIMAP will just do the right thing. How-
726 ever, sometimes this can be tricky -- if your IMAP server does not pro-
727 vide the SEARCH command, or does not return something useful,
728 OfflineIMAP cannot determine the new UID of the message. So, in these
729 rare instances, OfflineIMAP will upload the message to the IMAP server
730 and delete it from your local folder. Then, on your next sync, the
731 message will be re-downloaded with the proper UID. OfflineIMAP makes
732 sure that the message was properly uploaded before deleting it, so
733 there should be no risk of data loss.
736 OfflineIMAP can work with Evolution. To do so, first configure your
737 OfflineIMAP account to have sep = / in its configuration. Then, con-
738 figure Evolution with the "Maildir-format mail directories" server
739 type. For the path, you will need to specify the name of the top-level
740 folder inside your OfflineIMAP storage location. You're now set!
743 At this time, I believe that OfflineIMAP with Maildirs is not compati-
744 ble with KMail. KMail cannot work in any mode other than to move all
745 messages out of all folders immediately, which (besides being annoying
746 and fundamentally broken) is incompatible with OfflineIMAP.
748 However, I have made KMail version 3 work well with OfflineIMAP by
749 installing an IMAP server on my local machine, having OfflineIMAP sync
750 to that, and pointing KMail at the same server.
753 There is an OfflineIMAP mailing list available. To subscribe, send the
754 text "Subscribe" in the subject of a mail to offlineimap-request@com-
755 plete.org. To post, send the message to offlineimap@complete.org.
756 Archives are available at
757 <URL:http://lists.complete.org/offlineimap@complete.org/>.
760 Reports of bugs should be sent via e-mail to the OfflineIMAP mailing
761 list at offlineimap at complete dot org. Debian users are encouraged
762 to instead use the Debian bug-tracking system.
765 If you are upgrading from a version of OfflineIMAP prior to 3.99.12,
766 you will find that you will get errors when OfflineIMAP starts up
767 (relating to ConfigParser or AccountHashGenerator) and the configura-
768 tion file. This is because the config file format had to change to
769 accommodate new features in 4.0. Fortunately, it's not difficult to
772 First thing you need to do is stop any running OfflineIMAP instance,
773 making sure first that it's synced all your mail. Then, modify your
774 ~/.offlineimaprc file. You'll need to split up each account section
775 (make sure that it now starts with "Account ") into two Repository sec-
776 tions (one for the local side and another for the remote side.) See
777 the files offlineimap.conf.minimal and offlineimap.conf in the distri-
778 bution if you need more assistance.
780 OfflineIMAP's status directory area has also changed. Therefore, you
781 should delete everything in ~/.offlineimap as well as your local mail
784 When you start up OfflineIMAP 4.0, it will re-download all your mail
785 from the server and then you can continue using it like normal.
788 OfflineIMAP, and this manual, are Copyright (C) 2002, 2003 John
791 This program is free software; you can redistribute it and/or modify it
792 under the terms of the GNU General Public License as published by the
793 Free Software Foundation; either version 2 of the License, or (at your
794 option) any later version.
796 This program is distributed in the hope that it will be useful, but
797 WITHOUT ANY WARRANTY; without even the implied warranty of MER-
798 CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
799 Public License for more details.
801 You should have received a copy of the GNU General Public License along
802 with this program; if not, write to the Free Software Foundation, Inc.,
803 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
805 imaplib.py comes from the Python dev tree and is licensed under the
806 GPL-compatible PSF license as stated in the file COPYRIGHT in the
807 OfflineIMAP distribution.
810 OfflineIMAP, its libraries, documentation, and all included files,
811 except where noted, was written by John Goerzen <jgoerzen@complete.org>
812 and copyright is held as stated in the COPYRIGHT section.
814 OfflineIMAP may be downloaded, and information found, from its homepage
815 via either Gopher <URL:gopher://quux.org/1/devel/offlineimap> or HTTP
816 <URL:http://quux.org/devel/offlineimap>.
818 OfflineIMAP may also be downloaded using Subversion. Additionally, the
819 distributed tar.gz may be updated with a simple "svn update" command;
820 it is ready to go. For information on getting OfflineIMAP with Subver-
821 sion, please visit the complete.org Subversion page
822 <URL:http://svn.complete.org/>.
828 Detailed history may be found in the file ChangeLog in the OfflineIMAP
829 distribution. Feature and bug histories may be found in the file
830 debian/changelog which, despite its name, is not really Debian-spe-
831 cific. This section provides a large overview.
833 Development on OfflineIMAP began on June 18, 2002. Version 1.0.0 was
834 released three days later on June 21, 2002. Point releases followed,
835 including speed optimizations and some compatibility fixes.
837 Version 2.0.0 was released on July 3, 2002, and represented the first
838 time the synchronization became multithreaded and, to the best of my
839 knowledge, the first multithreaded IMAP syncrhonizing application in
840 existance. The last 2.0.x release, 2.0.8, was made on July 9.
842 Version 3.0.0 was released on July 11, 2002, and introduced modular
843 user interfaces and the first GUI interface for OfflineIMAP. This man-
844 ual also was introduced with 3.0.0, along with many command-line
845 options. Version 3.1.0 was released on July 21, adding the Noninterac-
846 tive user interfaces, profiling support, and several bugfixes. 3.2.0
847 was released on July 24, adding support for the Blinkenlights GUI
848 interface. OfflineIMAP entered maintenance mode for awhile, as it had
849 reached a feature-complete milestone in my mind.
851 The 3.99.x branch began in on October 7, 2002, to begin work for 4.0.
852 The Curses.Blinkenlights interface was added in 3.99.6, and many archi-
853 tectural changes were made.
855 4.0.0 was released on July 18, 2003, including the ability to synchro-
856 nize directly between two IMAP servers, the first re-architecting of
857 the configuration file to refine the notion of an account, and the new
862 John Goerzen 28 September 2005 OFFLINEIMAP(1)