Tony,
Thanks for the comments.
+--<srv1>--+
| | MDA
| messages |
| | server-side message store (inbox)
+----------+
| POP (usually)
+--<pc1>---+
| |
| messages | client-side message store
| |
+----------+
Messages are retained on pc1 and not on srv1.
TF> My annotations above apply to this scenario. In this case the client may
TF> use sieve to direct POPped messages to different mailboxes.
Sieve is used between what 2 entities? It sounds as if it is inside
pc1, so I'm not sure how that uses a protocol standard like sieve,
unless you have the sieve result in multiple pop sessions, one for
each mailbox.
From your next comments, it sounds as if one use of sieve is inside
pc1 and the other is the more usual interaction between pc1 and srv1
(mda).
d/
--
Dave Crocker <mailto:dcrocker(_at_)brandenburg(_dot_)com>
Brandenburg InternetWorking <http://www.brandenburg.com>
Sunnyvale, CA USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>