FAQ.txt | FAQ.txt | |||
---|---|---|---|---|
/* ======================================================================== | /* ======================================================================== | |||
* Copyright 1988-2006 University of Washington | * Copyright 1988-2007 University of Washington | |||
* | * | |||
* Licensed under the Apache License, Version 2.0 (the "License"); | * Licensed under the Apache License, Version 2.0 (the "License"); | |||
* you may not use this file except in compliance with the License. | * you may not use this file except in compliance with the License. | |||
* You may obtain a copy of the License at | * You may obtain a copy of the License at | |||
* | * | |||
* http://www.apache.org/licenses/LICENSE-2.0 | * http://www.apache.org/licenses/LICENSE-2.0 | |||
* | * | |||
* | * | |||
* ======================================================================== | * ======================================================================== | |||
*/ | */ | |||
skipping to change at line 452 | skipping to change at line 452 | |||
filesystem to be both a file and a directory; consequently you | filesystem to be both a file and a directory; consequently you | |||
can not have a sub-mailbox within a mailbox that is in one of | can not have a sub-mailbox within a mailbox that is in one of | |||
these formats. | these formats. | |||
This is not a limitation of the software; this is a limitation | This is not a limitation of the software; this is a limitation | |||
of UNIX. For example, there are mailbox formats in which the | of UNIX. For example, there are mailbox formats in which the | |||
name is a directory and each message is a file within that | name is a directory and each message is a file within that | |||
directory; these formats support sub-mailboxes within such | directory; these formats support sub-mailboxes within such | |||
mailboxes. However, for technical reasons, the "flat file" | mailboxes. However, for technical reasons, the "flat file" | |||
formats are generally preferred since they perform better. Read | formats are generally preferred since they perform better. Read | |||
imap-2006/docs/formats.txt for more information on this topic. | imap-2007/docs/formats.txt for more information on this topic. | |||
It is always permissible to create a directory that is not a | It is always permissible to create a directory that is not a | |||
mailbox, and have sub-mailboxes under it. The easiest way to | mailbox, and have sub-mailboxes under it. The easiest way to | |||
create a directory is to create a new mailbox inside a | create a directory is to create a new mailbox inside a | |||
directory that doesn't already exist. For example, if you | directory that doesn't already exist. For example, if you | |||
create "Mail/testbox" on UNIX, the directory "Mail/" will | create "Mail/testbox" on UNIX, the directory "Mail/" will | |||
automatically be created and then the mailbox "testbox" will be | automatically be created and then the mailbox "testbox" will be | |||
created as a sub-mailbox of "Mail/". | created as a sub-mailbox of "Mail/". | |||
It is also possible to create the name "Mail/" directly. Check | It is also possible to create the name "Mail/" directly. Check | |||
skipping to change at line 771 | skipping to change at line 771 | |||
3.4 How do I make the IMAP server look for secondary folders at some | 3.4 How do I make the IMAP server look for secondary folders at some | |||
place other than the user's home directory? | place other than the user's home directory? | |||
Please read the file CONFIG for discussion of this and other | Please read the file CONFIG for discussion of this and other | |||
issues. | issues. | |||
_________________________________________________________________ | _________________________________________________________________ | |||
3.5 How do I configure SSL? | 3.5 How do I configure SSL? | |||
3.6 How do I configure TLS and the STARTTLS facility? | 3.6 How do I configure TLS and the STARTTLS facility? | |||
imap-2006 supports SSL and TLS client functionality on UNIX and | imap-2007 supports SSL and TLS client functionality on UNIX and | |||
32-bit Windows for IMAP, POP3, SMTP, and NNTP; and SSL and TLS | 32-bit Windows for IMAP, POP3, SMTP, and NNTP; and SSL and TLS | |||
server functionality on UNIX for IMAP and POP3. | server functionality on UNIX for IMAP and POP3. | |||
UNIX SSL build requires that a third-party software package, | UNIX SSL build requires that a third-party software package, | |||
OpenSSL, be installed on the system first. Read | OpenSSL, be installed on the system first. Read | |||
imap-2006/docs/SSLBUILD for more information. | imap-2007/docs/SSLBUILD for more information. | |||
SSL is supported via undocumented Microsoft interfaces in | SSL is supported via undocumented Microsoft interfaces in | |||
Windows 9x and NT4; and via standard interfaces in Windows | Windows 9x and NT4; and via standard interfaces in Windows | |||
2000, Windows Millenium, and Windows XP. | 2000, Windows Millenium, and Windows XP. | |||
_________________________________________________________________ | _________________________________________________________________ | |||
3.7 How do I build/install OpenSSL and obtain/create certificates for | 3.7 How do I build/install OpenSSL and obtain/create certificates for | |||
use with SSL? | use with SSL? | |||
If you need help in doing this, try the contacts mentioned in | If you need help in doing this, try the contacts mentioned in | |||
skipping to change at line 804 | skipping to change at line 804 | |||
CRAM-MD5 authentication is enabled in the IMAP and POP3 client | CRAM-MD5 authentication is enabled in the IMAP and POP3 client | |||
code on all platforms. Read md5.txt to learn how to set up | code on all platforms. Read md5.txt to learn how to set up | |||
CRAM-MD5 and APOP authentication on UNIX and NT servers. | CRAM-MD5 and APOP authentication on UNIX and NT servers. | |||
There is no support for APOP client authentication. | There is no support for APOP client authentication. | |||
_________________________________________________________________ | _________________________________________________________________ | |||
3.10 How do I configure Kerberos V5? | 3.10 How do I configure Kerberos V5? | |||
imap-2006 supports client and server functionality on UNIX and | imap-2007 supports client and server functionality on UNIX and | |||
32-bit Windows. | 32-bit Windows. | |||
Kerberos V5 is supported by default in Windows 2000 builds: | Kerberos V5 is supported by default in Windows 2000 builds: | |||
nmake -f makefile.w2k | nmake -f makefile.w2k | |||
Other builds require that a third-party Kerberos package, e.g. | Other builds require that a third-party Kerberos package, e.g. | |||
MIT Kerberos, be installed on the system first. | MIT Kerberos, be installed on the system first. | |||
To build with Kerberos V5 on UNIX, include | To build with Kerberos V5 on UNIX, include | |||
skipping to change at line 2012 | skipping to change at line 2012 | |||
then you have much worse problems then that. | then you have much worse problems then that. | |||
If you absolutely insist upon requiring privileges to create a | If you absolutely insist upon requiring privileges to create a | |||
lock file, external file locking can be done via a setgid mail | lock file, external file locking can be done via a setgid mail | |||
program named /etc/mlock (this is defined by LOCKPGM in the | program named /etc/mlock (this is defined by LOCKPGM in the | |||
c-client Makefile). If the toolkit is unable to create a | c-client Makefile). If the toolkit is unable to create a | |||
<...mailbox...>.lock file in the directory by itself, it will | <...mailbox...>.lock file in the directory by itself, it will | |||
try to call mlock to do it. I do not recommend doing this for | try to call mlock to do it. I do not recommend doing this for | |||
performance reasons. | performance reasons. | |||
A sample mlock program is included as part of imap-2006. We | A sample mlock program is included as part of imap-2007. We | |||
have tried to make this sample program secure, but it has not | have tried to make this sample program secure, but it has not | |||
been thoroughly audited. | been thoroughly audited. | |||
_________________________________________________________________ | _________________________________________________________________ | |||
7.11 What does the message: Mailbox is open by another process, access | 7.11 What does the message: Mailbox is open by another process, access | |||
is readonly mean? How do I fix this? | is readonly mean? How do I fix this? | |||
A problem occurred in applying a lock to a /tmp lock file. | A problem occurred in applying a lock to a /tmp lock file. | |||
Either some other program has the mailbox open and won't | Either some other program has the mailbox open and won't | |||
relenquish it, or something is wrong with the protection of | relenquish it, or something is wrong with the protection of | |||
skipping to change at line 2991 | skipping to change at line 2991 | |||
8.4 Where can I find out more about setting up and administering an | 8.4 Where can I find out more about setting up and administering an | |||
IMAP server? | IMAP server? | |||
We recommend Managing IMAP, by Dianna Mullet & Kevin Mullet, | We recommend Managing IMAP, by Dianna Mullet & Kevin Mullet, | |||
published by O'Reilly, ISBN 0-596-00012-X. | published by O'Reilly, ISBN 0-596-00012-X. | |||
This book also has an excellent comparison of the UW and Cyrus | This book also has an excellent comparison of the UW and Cyrus | |||
IMAP servers. | IMAP servers. | |||
Last Updated: 29 July 2007 | Last Updated: 15 November 2007 | |||
End of changes. 7 change blocks. | ||||
6 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |