How do I specify the names of my folders?
You do not need to. OfflineIMAP is smart enough to automati-
cally figure out what folders are present on the IMAP server and
- synchronize them. You can use the folderfilter and foldertrans
+ synchronize them. You can use the folderfilter and nametrans
configuration file options to request certain folders and rename
them as they come in if you like.
from the server and then you can continue using it like normal.
COPYRIGHT
- OfflineIMAP, and this manual, are Copyright (C) 2002, 2003 John
- Goerzen.
+ OfflineIMAP, and this manual, are Copyright 2002, 2003 John Goerzen.
This program is free software; you can redistribute it and/or modify it
- under the terms of the GNU General Public License as published by the
- Free Software Foundation; either version 2 of the License, or (at your
+ under the terms of the GNU General Public License as published by the
+ Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
- This program is distributed in the hope that it will be useful, but
- WITHOUT ANY WARRANTY; without even the implied warranty of MER-
- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
+ This program is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of MER-
+ CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- imaplib.py comes from the Python dev tree and is licensed under the
- GPL-compatible PSF license as stated in the file COPYRIGHT in the
+ imaplib.py comes from the Python dev tree and is licensed under the
+ GPL-compatible PSF license as stated in the file COPYRIGHT in the
OfflineIMAP distribution.
AUTHOR
- OfflineIMAP, its libraries, documentation, and all included files,
+ OfflineIMAP, its libraries, documentation, and all included files,
except where noted, was written by John Goerzen <jgoerzen@complete.org>
and copyright is held as stated in the COPYRIGHT section.
OfflineIMAP may be downloaded, and information found, from its homepage
- via either Gopher <URL:gopher://quux.org/1/devel/offlineimap> or HTTP
+ via either Gopher <URL:gopher://quux.org/1/devel/offlineimap> or HTTP
<URL:http://quux.org/devel/offlineimap>.
OfflineIMAP may also be downloaded using Subversion. Additionally, the
- distributed tar.gz may be updated with a simple "svn update" command;
+ distributed tar.gz may be updated with a simple "svn update" command;
it is ready to go. For information on getting OfflineIMAP with Subver-
- sion, please visit the complete.org Subversion page
+ sion, please visit the complete.org Subversion page
<URL:http://svn.complete.org/>.
SEE ALSO
mutt(1), python(1)
HISTORY
- Detailed history may be found in the file ChangeLog in the OfflineIMAP
- distribution. Feature and bug histories may be found in the file
- debian/changelog which, despite its name, is not really Debian-spe-
+ Detailed history may be found in the file ChangeLog in the OfflineIMAP
+ distribution. Feature and bug histories may be found in the file
+ debian/changelog which, despite its name, is not really Debian-spe-
cific. This section provides a large overview.
- Development on OfflineIMAP began on June 18, 2002. Version 1.0.0 was
- released three days later on June 21, 2002. Point releases followed,
+ Development on OfflineIMAP began on June 18, 2002. Version 1.0.0 was
+ released three days later on June 21, 2002. Point releases followed,
including speed optimizations and some compatibility fixes.
- Version 2.0.0 was released on July 3, 2002, and represented the first
- time the synchronization became multithreaded and, to the best of my
- knowledge, the first multithreaded IMAP syncrhonizing application in
+ Version 2.0.0 was released on July 3, 2002, and represented the first
+ time the synchronization became multithreaded and, to the best of my
+ knowledge, the first multithreaded IMAP syncrhonizing application in
existance. The last 2.0.x release, 2.0.8, was made on July 9.
- Version 3.0.0 was released on July 11, 2002, and introduced modular
+ Version 3.0.0 was released on July 11, 2002, and introduced modular
user interfaces and the first GUI interface for OfflineIMAP. This man-
- ual also was introduced with 3.0.0, along with many command-line
+ ual also was introduced with 3.0.0, along with many command-line
options. Version 3.1.0 was released on July 21, adding the Noninterac-
- tive user interfaces, profiling support, and several bugfixes. 3.2.0
- was released on July 24, adding support for the Blinkenlights GUI
- interface. OfflineIMAP entered maintenance mode for awhile, as it had
+ tive user interfaces, profiling support, and several bugfixes. 3.2.0
+ was released on July 24, adding support for the Blinkenlights GUI
+ interface. OfflineIMAP entered maintenance mode for awhile, as it had
reached a feature-complete milestone in my mind.
- The 3.99.x branch began in on October 7, 2002, to begin work for 4.0.
+ The 3.99.x branch began in on October 7, 2002, to begin work for 4.0.
The Curses.Blinkenlights interface was added in 3.99.6, and many archi-
tectural changes were made.
- 4.0.0 was released on July 18, 2003, including the ability to synchro-
- nize directly between two IMAP servers, the first re-architecting of
- the configuration file to refine the notion of an account, and the new
+ 4.0.0 was released on July 18, 2003, including the ability to synchro-
+ nize directly between two IMAP servers, the first re-architecting of
+ the configuration file to refine the notion of an account, and the new
Curses interface.
-John Goerzen 16 November 2004 OFFLINEIMAP(1)
+John Goerzen 17 June 2005 OFFLINEIMAP(1)