Note Earl's regression fix for SSL_CTX_clear_options() on older OpenSSL.

[~andy/fetchmail] / design-notes.html

diff --git a/design-notes.html b/design-notes.html
index e95eeb87d0eb0ad6d6f11bbfce6268efa3aed8de..ef2cc07af7068c35ed121b882f87b7032e665acd 100644 (file)
--- a/design-notes.html
+++ b/design-notes.html
@@ -52,7 +52,7 @@ concepts will have to be applied. Random bits are:</p>
 
 <h2>SMTP forwarding</h2>
 
-<p>Fetchmails multidrop and rewrite options will process addresses
+<p>Fetchmail's multidrop and rewrite options will process addresses
 received from remote sites. Special care must be taken so these
 features cannot be abused to relay mail to foreign sites.</p>
 
@@ -73,11 +73,12 @@ suffer. ESR is right in stating that the POP3 UID tracks which messages
 have been read <em>by this client</em> &ndash; and that is exactly what
 we need to do.</p>
 
-<p>If fetchmail is supposed to retrieve all
-mail from a mailbox reliably, without being disturbed by someone
-occasionally using another client on another host, or a webmailer, or
-similar, then <em>client</em>-side tracking of the state is
-indispensable. This is also needed to match behavior to ETRN and ODMR.</p>
+<p>If fetchmail is supposed to retrieve all mail from a mailbox
+reliably, without being disturbed by someone occasionally using another
+client on another host, or a webmailer, or similar, then
+<em>client</em>-side tracking of the state is indispensable. This is
+also needed to match behavior to ETRN and ODMR or to support read-only
+mailboxes in --keep mode.</p>
 
 <h3>Present and future</h3>