On Wed, Sep 19, 2001 at 11:03:42PM +0200, [EMAIL PROTECTED] 
wrote:
> Charles Cazabon ([EMAIL PROTECTED]) wrote:
> > [EMAIL PROTECTED] 
><[EMAIL PROTECTED]> wrote:
> 
> [snip]
> 
> > > The catch is that I still want to POP them out, just not see them as
> > > marked NEW.
> > 
> > I think you're screwed, then.  You want your POP3 daemon to
> > transparently know (and inform the POP3 client) that another process,
> > totally unrelated to POP3, has gone into the Maildir and read some
> > files.  See the problem?
> 
> I see the logic that would explain that what I try to do is indeed
> problematic. However, if I understood correctly, I could not get the
> result wanted by having two POP client access the mailbox with the first
> one leaving the mail on the server. When I would POP with the second
> one, I would still see the mails I have already read as new.

Does anyone know of a POP server that exhibits this behaviour OOTB? I
know Qpopper does not, nor does (obviously) qmail-pop3d. I don't recall
ever having this work transparently, with any combination of clients or
servers (and I've run quite a few combinations of both in my time...)
Anytime, anywhere, multiple clients accessing the same mailbox seem to
treat a message read by the other client as new and unread.

-- 
Greg White

Reply via email to