diff options
Diffstat (limited to 'imap/docs')
| -rw-r--r-- | imap/docs/FAQ.html | 16 | ||||
| -rw-r--r-- | imap/docs/RELNOTES | 8 | ||||
| -rw-r--r-- | imap/docs/bugs.txt | 2 | ||||
| -rw-r--r-- | imap/docs/calendar.txt | 8 | ||||
| -rw-r--r-- | imap/docs/commndmt.txt | 2 | ||||
| -rw-r--r-- | imap/docs/drivers.txt | 12 | ||||
| -rw-r--r-- | imap/docs/formats.txt | 6 | ||||
| -rw-r--r-- | imap/docs/imaprc.txt | 6 | ||||
| -rw-r--r-- | imap/docs/internal.txt | 20 | ||||
| -rw-r--r-- | imap/docs/locking.txt | 4 | ||||
| -rw-r--r-- | imap/docs/md5.txt | 2 | ||||
| -rw-r--r-- | imap/docs/mixfmt.txt | 4 |
12 files changed, 45 insertions, 45 deletions
diff --git a/imap/docs/FAQ.html b/imap/docs/FAQ.html index 27d42aa4..f2496b99 100644 --- a/imap/docs/FAQ.html +++ b/imap/docs/FAQ.html @@ -322,7 +322,7 @@ <ul> <li><a href="#5.1">5.1 I see that the IMAP server allows access to - arbitary files on the system, including /etc/passwd! How do I disable + arbitrary files on the system, including /etc/passwd! How do I disable this?</a></li> <li><a href="#5.2">5.2 I've heard that IMAP servers are insecure. Is @@ -1411,7 +1411,7 @@ <p>SSL is supported via undocumented Microsoft interfaces in Windows 9x and NT4; and via standard interfaces in Windows 2000, Windows - Millenium, and Windows XP.</p> + Millennium, and Windows XP.</p> </dd> </dl> @@ -1468,7 +1468,7 @@ make lnp EXTRAAUTHENTICATORS=gss </pre> - <p>To build with Kerberos V5 on Windows 9x, Windows Millenium, and NT4, + <p>To build with Kerberos V5 on Windows 9x, Windows Millennium, and NT4, use the "makefile.ntk" file instead of "makefile.nt":</p> <pre> @@ -2061,7 +2061,7 @@ mtest.c:515: the `gets' function is dangerous and should not be used. <hr> <p><a name="5.1"><strong>5.1 I see that the IMAP server allows access to - arbitary files on the system, including /etc/passwd! How do I disable + arbitrary files on the system, including /etc/passwd! How do I disable this?</strong></a></p> <dl> @@ -2251,7 +2251,7 @@ for better performance. <p>Coaxing software that uses autoconfig to build properly on platforms which were not specifically considered by that software wastes an inordinate amount of time. When (not if) autoconfig fails to do the - right thing, the result is an inpenetrable morass to untangle in order + right thing, the result is an impenetrable morass to untangle in order to find the problem and fix it.</p> <p>The concept behind autoconfig is good, but the execution is flawed. @@ -3162,7 +3162,7 @@ looking something like: <pre> dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU </pre>The only thing that is variable is the "ssss" field, it can be as many -digits as needed. All other fields (inluding the "dd") are fixed width. So, +digits as needed. All other fields (including the "dd") are fixed width. So, the easiest thing to do is to look forward in the file for the next internal header, and delete everything from the error point to that internal header. @@ -3520,7 +3520,7 @@ his home directory. <dl> <dd> - There are two common occurances of this problem: + There are two common occurrences of this problem: <ul> <li>You are running a system (e.g. certain versions of Linux) which @@ -4147,7 +4147,7 @@ that the text part in a 334 response be a BASE64 encoded string; in other words, it is a protocol syntax error. <p>In the case of AUTH=PLAIN, RFC 4422 (page 7) requires that the - encoded string have no data. In other words, the appropropiate + encoded string have no data. In other words, the appropriate standards-compliant server response is "334" followed by a SPACE and a CRLF.</p> diff --git a/imap/docs/RELNOTES b/imap/docs/RELNOTES index 80e17967..28069698 100644 --- a/imap/docs/RELNOTES +++ b/imap/docs/RELNOTES @@ -335,7 +335,7 @@ broken servers use the SSLv23 server method, and this flag works around that problem. WARNING: use of this flag will cause TLS negotiation to fail with a server which uses the proper TLSv1 server method. Additionally, there are known security risks in SSLv2; so users should be suspicious if this switch -suddenly becomes necesary. +suddenly becomes necessary. The silly mailbox flag combination /ssl/tls is now rejected as an invalid remote specification. Previous versions tried to negotiate TLS over an SSL @@ -595,7 +595,7 @@ no longer builds on those platforms. Updated: 7 January 2003 -imap-2002b is a maintenace release, released concurrently with Pine 4.52, +imap-2002b is a maintenance release, released concurrently with Pine 4.52, and contains only bugfixes. Programs written for imap-2002 will build with this version without modification. @@ -631,7 +631,7 @@ you will be asked to confirm to continue the build. ORDEREDSUBJECT threading has been changed in accordance with draft 12 of the IMAP threading specification. Previously, each non-root message in an -ORDEREDSUBJECT thread has been a child of the message immediately preceeding +ORDEREDSUBJECT thread has been a child of the message immediately preceding it in the thread. Draft 12 changes this so that the second message in the thread is the child of the first (root) message, and all subsequent messages are siblings of the first message. This is significant in MUAs which display @@ -810,7 +810,7 @@ by the /ssl switch in the mailbox name. With SSL connections, the server certificate is validated by the client code on UNIX, and Windows 2000 unless /novalidate-cert is specified. Server -certificates are currently is not validated on Windows 9x, Windows Millenium, +certificates are currently is not validated on Windows 9x, Windows Millennium, or Windows NT 4; this is an artifact of the operating system and not the port (e.g. client code using the NT port will validate certificates if running on Windows 2000). On UNIX, the server certificate must be signed by a trusted diff --git a/imap/docs/bugs.txt b/imap/docs/bugs.txt index 5f87b3ef..d8daa1a2 100644 --- a/imap/docs/bugs.txt +++ b/imap/docs/bugs.txt @@ -46,7 +46,7 @@ The following are known problems/deficiencies in the imap-2007 toolkit: DNS and/or the server's host table. A workaround exists (see the top-level Makefile for details) but is not recommended and can not be used at all with Kerberos. - . At the insistance of the security gurus, SSL certification validation + . At the insistence of the security gurus, SSL certification validation is now on by default. This means that you must now use the new /novalidate-cert switch if establishing an SSL connection to a server with a self-signed certificate; i.e. if "imap.example.com" has a diff --git a/imap/docs/calendar.txt b/imap/docs/calendar.txt index c1009078..63aaa68b 100644 --- a/imap/docs/calendar.txt +++ b/imap/docs/calendar.txt @@ -66,7 +66,7 @@ Caesar). Months in the Julian calendar were 30 or 31 days in length and every fourth year was made a leap year (having 366 days) by adding a day -to the end of the year. This leap year rule was not consistantly +to the end of the year. This leap year rule was not consistently applied until 8 CE. The year-ending month of February, never a popular month, was presently shortened so that Julius Caesar and Emperor Augustus could each have long months named after them. @@ -124,7 +124,7 @@ calendar. This suggestion was adopted over the next 500 years and subsequently followed in the Gregorian calendar. For the benefit of those who seek religious significance to the -calendar millenium, note that year 1 is too late by at least 4 years. +calendar millennium, note that year 1 is too late by at least 4 years. Herod the Great, named in the Christian Bible as having all children in Bethlehem put to death in an attempt to kill the infant Jesus, died in 4 BCE. @@ -190,7 +190,7 @@ centuries yet. There is code in c-client to support the modified Gregorian calendar, although it is currently disabled. Sometime in the next 2000 years, someone will need to enable this code so that c-client is -Y4K compiliant. Then, 18,000 years from now, someone will have to +Y4K compliant. Then, 18,000 years from now, someone will have to tear into c-client's code to fix the Y20K bug. @@ -237,7 +237,7 @@ adjustments will be necessary at that time. Hence my use of "or so" in predicting the years that the calendar will fall behind. The actual point may be anywhere from decades (in the -case of Y3.3K) to millenia (in the case of Y40K) off from these predictions. +case of Y3.3K) to millennia (in the case of Y40K) off from these predictions. MEANINGS OF DAY NAMES diff --git a/imap/docs/commndmt.txt b/imap/docs/commndmt.txt index 7fd9707b..ee387311 100644 --- a/imap/docs/commndmt.txt +++ b/imap/docs/commndmt.txt @@ -92,7 +92,7 @@ they are such. 10. Thou shalt use the LIST "*" wildcard only with great care. If thou doth not fully comprehend the danger of "*", thou shalt use only -"%" and forget about the existance of "*". +"%" and forget about the existence of "*". Honor these commandments, and keep them holy in thy heart, so that thy users shalt maximize their pleasure, and the server administrators diff --git a/imap/docs/drivers.txt b/imap/docs/drivers.txt index de91aa53..0d4c77c9 100644 --- a/imap/docs/drivers.txt +++ b/imap/docs/drivers.txt @@ -114,14 +114,14 @@ prefix of the mailbox name. On UNIX, the following rules apply: Prefix Interpretation of Suffix ------ ------------------------ -/ [black box] preceeds a user name; "/foo/bar" means +/ [black box] precedes a user name; "/foo/bar" means "black box user foo's mailbox bar" - [not black box] preceeds an absolute path name. -~ [not black box] preceeds a user name; "~foo/bar" means + [not black box] precedes an absolute path name. +~ [not black box] precedes a user name; "~foo/bar" means "UNIX user foo's mailbox bar" -#ftp/ preceeds UNIX user ftp's mailbox name -#public/ preceeds UNIX user imappublic's mailbox name -#shared/ preceeds UNIX user imapshared's mailbox name +#ftp/ precedes UNIX user ftp's mailbox name +#public/ precedes UNIX user imappublic's mailbox name +#shared/ precedes UNIX user imapshared's mailbox name All other names are interpreted in the context of the UNIX user's home directory (not black box), the black box user's black box directory diff --git a/imap/docs/formats.txt b/imap/docs/formats.txt index 8dfb9dae..d1e3b353 100644 --- a/imap/docs/formats.txt +++ b/imap/docs/formats.txt @@ -17,7 +17,7 @@ When a mailbox storage technology uses local files and -directories directly, the file(s) and directories are layed out in a +directories directly, the file(s) and directories are laid out in a mailbox format. I. Flat-File Formats @@ -166,7 +166,7 @@ Soapbox on File/Message Formats too much effort into file/message formats, you are correct. There's a general reason why file/message formats are a bad idea. -Just about every filesystem in existance serializes file creation and +Just about every filesystem in existence serializes file creation and deletions because these manipulate the free space map. This turns out to be an enormous problem when you start creating/deleting more than a few messages per second; you spend all your time thrashing in the @@ -209,7 +209,7 @@ So what does this all mean? A database (such as used by Exchange) is really a much better approach if you want to move away from flat files. mx and especially -Cyrus take a tenative step in that direction; mx failed mostly because +Cyrus take a tentative step in that direction; mx failed mostly because it didn't go anywhere near far enough. Cyrus goes much further, and scores remarkable benefits from doing so. diff --git a/imap/docs/imaprc.txt b/imap/docs/imaprc.txt index cda153a6..82c7daa2 100644 --- a/imap/docs/imaprc.txt +++ b/imap/docs/imaprc.txt @@ -30,7 +30,7 @@ set keywords. * config file whether or not there is any need for one. * * * * This information is subject to change without notice. Commands * -* may be added, removed, or altered. The behavior of comamnds may * +* may be added, removed, or altered. The behavior of commands may * * change. Do not use any of this information without consulting me * * first. c-client's defaults have been carefully chosen to be right * * for general-purpose and most special-purpose configurations. If * @@ -469,7 +469,7 @@ matter. Unrecognized commands are ignored. 30) set disable-automatic-shared-namespaces <number> Never look up the "ftp", "imappublic", and "imapshared" users as - posssible home directories for the #ftp, #public, and #shared + possible home directories for the #ftp, #public, and #shared namespaces. On some systems (reportedly including AIX 4.3.3) getpwnam() of an unknown user name is horrendously slow. @@ -510,7 +510,7 @@ matter. Unrecognized commands are ignored. By default, the servers (ipop[23]d and imapd) will do gethostbyaddr() on the local and remote sockets so that imapd can identify itself properly (this is important when the same CPU hosts multiple virtual - hosts on different IP addresss) and also includes the client's name + hosts on different IP address) and also includes the client's name when it writes to the syslog. There are also client gethostbyaddr() calls, used primarily by authentication mechanisms. diff --git a/imap/docs/internal.txt b/imap/docs/internal.txt index 203688e8..98d66ab6 100644 --- a/imap/docs/internal.txt +++ b/imap/docs/internal.txt @@ -626,7 +626,7 @@ void INIT (STRING *s,STRINGDRIVER *d,void *data,unsigned long size); data pointer to driver-dependent data, from which the driver can determine string data size size of the string - This call initializes the string stucture. + This call initializes the string structure. unsigned long SIZE (STRING *s); @@ -723,7 +723,7 @@ char mail_string_next (STRING *s); void mail_string_setpos (STRING *s,unsigned long i); These three functions are the init, next, and setpos string -structure access methods for the build-in mail_string string driver. +structure access methods for the built-in mail_string string driver. mail_string is a basic string driver for a char* string. See the documentation below on "String Structures" for more information. @@ -742,7 +742,7 @@ statement #include "linkage.c" which will include the "system standard driver linkage" defined when c-client was built. By using linkage.c instead of explicit mail_link() -calls, you are guaranteed that you will have a consistant linkage among +calls, you are guaranteed that you will have a consistent linkage among all software built on this system. @@ -925,7 +925,7 @@ fetch an operational parameter and SET_xxx to set the parameter: bit. Defaults to non-NIL, since this is usually bad news. GET_LISTMAXLEVEL / SET_LISTMAXLEVEL - The maximum depth of recusion that LIST will go on a * + The maximum depth of recursion that LIST will go on a * wildcard. Defaults to 20. GET_ANONYMOUSHOME / SET_ANONYMOUSHOME @@ -1143,7 +1143,7 @@ long mail_rename (MAILSTREAM *stream,char *old,char *newname); It returns T if successful, NIL if unsuccessful. If unsuccessful, an error message is returned via the mm_log() callback. - It is an error to reanme a mailbox that does not exist, or rename + It is an error to rename a mailbox that does not exist, or rename a mailbox to a name that already exists. It is permitted to rename INBOX; a new empty INBOX is created in its place. @@ -1609,7 +1609,7 @@ unsigned int seen : 1; message read unsigned int unseen : 1; message not read - The following auxillary structures are used by search programs: + The following auxiliary structures are used by search programs: SEARCHHEADER: header line searching char *line; header line field name char *text; text header line @@ -1725,7 +1725,7 @@ and end of the expunge to ensure synchronization. The status of the expunge is passed to the application via the mm_log() facility. Note that the decrementing of msgno's for subsequent messages -happens immediately; for example, if three consequtive messages starting +happens immediately; for example, if three consecutive messages starting at msgno 5 are expunged, mm_expunged() will be called with a msgno of 5 three times. @@ -2709,7 +2709,7 @@ possibly shown to the user. ERROR An error event. This event should be displayed to the user, or at least logged someplace. This is a - serious error condition occured that aborted the + serious error condition occurred that aborted the requested operation and possibly also aborted the mail stream. This ranges from normal error conditions such as "Can't open mailbox", "too many login failures, go @@ -2793,7 +2793,7 @@ function has to output its own. Driver interface When writing a new driver for the c-client, you must provide a -DRIVER stucture giving a dispatch vector between MAIL and the driver. +DRIVER structure giving a dispatch vector between MAIL and the driver. The DRIVER dispatch vector is described in mail.h. char *name; @@ -2974,7 +2974,7 @@ void mail_lock (MAILSTREAM *stream); lock if the stream is already locked. This is mainly used to catch errors due to a callback function -(e.g. mm_exists) inadvertantly recursing back to the MAIL routines and +(e.g. mm_exists) inadvertently recursing back to the MAIL routines and establishing an infinite recursion. Normally, drivers will set the lock prior to calling one of the callback functions above or, more likely, in the beginning of the driver's non-reentrant "do operation" section. In the diff --git a/imap/docs/locking.txt b/imap/docs/locking.txt index 32ff6c66..eb165647 100644 --- a/imap/docs/locking.txt +++ b/imap/docs/locking.txt @@ -61,7 +61,7 @@ writeable memory between such processes. A means of communicating this is by use of a file with a mutually agreed upon name. A binary semaphore can be passed by means of the -existance or non-existance of that file, provided that there is an +existence or non-existance of that file, provided that there is an atomic means to create a file if and only if that file does not exist. In C terms: @@ -245,7 +245,7 @@ BEZERK AND MMDF Locking in the traditional UNIX formats was largely dictated by the status quo in other applications; however, additional protection -is added against inadvertantly running multiple instances of a +is added against inadvertently running multiple instances of a c-client application on the same mail file. (1) c-client attempts to create a .lock file (mail file name with diff --git a/imap/docs/md5.txt b/imap/docs/md5.txt index c43f1023..f589c9ca 100644 --- a/imap/docs/md5.txt +++ b/imap/docs/md5.txt @@ -25,7 +25,7 @@ RFC 1939, the standard document for the POP3 protocol. challenge; the client responds with an MD5 checksum of the challenge plus the password; the server in compares the client's response with its own calculated value of the checksum. If the client's response -matches the server's calulated value, the client is authenticated. +matches the server's calculated value, the client is authenticated. Unlike plaintext passwords, this form of authentication is believed to be secure against the session being monitored; "sniffing" diff --git a/imap/docs/mixfmt.txt b/imap/docs/mixfmt.txt index afe3f940..68d75836 100644 --- a/imap/docs/mixfmt.txt +++ b/imap/docs/mixfmt.txt @@ -136,7 +136,7 @@ A file number is set to the current modseq when it is created. If a copy or append causes the file to exceed the compiled-in file size limit, a new file is started and the metadata is updated accordingly. -Preceeding each message is per-message record with the following format: +Preceding each message is per-message record with the following format: Key Payload --- ------- ;; per-message record @@ -225,7 +225,7 @@ Then the index and status files are closed. Shared expunge presents a problem due to the requirements of the IMAP protocol. You can't "burp" away a message until you are certain that no sharers have a pointer to any longer. Consequently, for the nonce -"burping" out expunged data be defered to an exclusive expunge as in +"burping" out expunged data be deferred to an exclusive expunge as in mbx format. If shared burping is ever implemented, then care will be needed not to |