Re: Danger! Danger!

[David Moore <dmoore@UCSD.EDU>]

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> David Moore <dmoore@UCSD.EDU> writes:
> 
> > 	But definitely with 0.70, I'm seeing that if I Gcc myself
> > something and also get the same message via mail, the odds seem high of
> > that thing showing up as 'already read'.  But I think it's also
> > happening with other incoming mail, so it's probably not just a gcc
> > problem.
> 
> Hm.  You're not using duplicate suppression or something like that? 

	I file my detected duplicates into a folder that I clear
manually, currently.  What happens is that if I gcc myself and also get
a copy, that often now, the real copy will arrive via email and be filed
into the correct group (ie, not the duplicate group), but will have the
read mark set (or something).  Maybe I can see if I can make this
reproducable.

	Previous versions would not hide the real copy of message, ie,
both would show up in the summary listing.  Now I do a unix 'from', se I
have the message.  I do 'M-2 g', I watch it file.  Often the unread
counter goes up by the appropriate amount.  I go into the group, and
that message isn't shown to me.  I use nnmail-split-history to get the
article number, use 'j' to go to it.  And it's there, but has been
marked as read for some reason.

	But maybe this is related to some other more generic hiding of
messages, it's hard to tell if I've missed mail or not...which is a bit
disturbing. 

	Maybe something in the code is using the wrong active range to
truncate the unread/ticked/etc lists.  That could explain all of these
problems, although doesn't make it easy to find.


-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | Solo Furnace Creek 508 -- 1996!