[tpop3d-discuss] My mods - will they break anything?

[Dom Gallagher]

At 06:00 AM 1/7/2004, tpop3d-discuss-request@lists.beasts.org wrote:
>Date: Wed, 7 Jan 2004 00:56:54 +0000
>From: Chris Lightfoot <chris@ex-parrot.com>
>To: mark@christian.net
>Cc: tpop3d-discuss@lists.beasts.org
>Subject: Re: [tpop3d-discuss] My mods - will they break anything?
>
>On Tue, Jan 06, 2004 at 01:30:03PM -0800, mark@christian.net wrote:
> > I've switched from Qpopper to tpop3d, mainly for the
> > different auth methods and maildir support.  One thing
> > Qpopper does is to rewrite the mailbox adding a Status:
> > to indicate that messages were read, which is useful
> > for us because our webmail app uses this info.
> >
> > So I made some minor mods to tpop3d as follows:
> >
> > - A message stays in 'new' until an actual RETR
> >   command is issued for it.  TOP and other commands
> >   are not sufficient to mark a message as 'read'.
> >
> > - Once retrieved via RETR, a message is moved into
> >   'cur' as before.
> >
> > - The sendmessage function inserts a "Status: R" line
> >   when sending the headers, if the message is in "cur".
> >
> > - The message itself is never actually rewritten.
> >
> > This seems to work just fine, and our webmail app now
> > keeps better track of read vs. unread messages.
> >
> > I'm wondering what side-effects, if any, there might be
> > from this?
>
>The only problem I can think of is that -- unless you've
>changed the STAT responses too -- the sizes reported by
>tpop3d will differ from the true message sizes, because of
>the inserted Status: R headers. This probably isn't a
>problem with typical clients.

This would be a pretty cool config option to have available in the main 
distro; often it'd be useful to be able to use cur/ to identify 'unread' 
email as opposed 'touched' mail as now.

D.
-- 
Dom Gallagher (dgallagher@starnetusa.net)
Development Engineering
StarNet/MegaPOP - http://www.megapop.net
WX is wireless - http://www.starnetwx.net

This message is sent in confidence to the addressees.
It may contain privileged, proprietary, or confidential information.