X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=design-notes.html;h=ef2cc07af7068c35ed121b882f87b7032e665acd;hb=2629c4511c68729d98acfd08637c1f00d3807f49;hp=e95eeb87d0eb0ad6d6f11bbfce6268efa3aed8de;hpb=c214bfa7f17bef61eafa5c351fd3c14f8352899e;p=~andy%2Ffetchmail diff --git a/design-notes.html b/design-notes.html index e95eeb87..ef2cc07a 100644 --- a/design-notes.html +++ b/design-notes.html @@ -52,7 +52,7 @@ concepts will have to be applied. Random bits are:

SMTP forwarding

-

Fetchmails multidrop and rewrite options will process addresses +

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.

@@ -73,11 +73,12 @@ suffer. ESR is right in stating that the POP3 UID tracks which messages have been read by this client – and that is exactly what we need to do.

-

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 client-side tracking of the state is -indispensable. This is also needed to match behavior to ETRN and ODMR.

+

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 +client-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.

Present and future