If popsneaker uses pop3, there is no way to flag or unflag messages. The
server is automatically doing this for you when popsneaker reads the
message.
Sam
Quoting Louis LeBlanc <[EMAIL PROTECTED]>, who wrote:
> I am not familiar with popsneaker, but it looks like it is flagging
> those messages as read as it checks the headers. Typical behavior,
> really. Check the documentation for popsneaker to see if it can leave
> them marked as new. This is the only thing I can imagine you can do.
> Mutt would have no way to know that a message is new without the
> flags.
>
> Failing that, don't use popsneaker, or change your sort method - maybe
> even define a macro to quickly switch sort orders so you can get a
> message as new, then sort it back into its thread for context.
>
> HTH
>
> L
> On 07/30/01 10:31 PM, Morten Bo Johansen sat at the `puter and typed:
> > This may not be the appropriate place to ask so my pardons in
> > advance...but the latest onslaught of Sircam venom has prompted
> > me to find a way to zap it right at the pop3 server of my ISP,
> > and I have chosen popsneaker for the task. It works really
> > well: popsneaker reads some predefined headers and zaps mails
> > according to rules specified by me.
> >
> > But ... all mails are now seen as read by mutt, i.e. they are
> > nolonger flagged as (N)ew which means that I won't even see
> > them since I prefer to have threads that contain only read
> > messages collapsed.
> >
> > Is there anything to do about this - short of not using popsneaker?
> >
> >
> >
> >
> > Regards,
> >
> > Morten
> >
>
> --
> Louis LeBlanc [EMAIL PROTECTED]
> Fully Funded Hobbyist, KeySlapper Extrordinaire :)
> http://acadia.ne.mediaone.net ԿԬ
>
> Houston, Tranquillity Base here. The Eagle has landed.
> -- Neil Armstrong
>
--
Sam Roberts <[EMAIL PROTECTED]>
