bug? 39/40 w/ demon

bug? 39/40 w/ demon

[Erik Selberg]

I've been experimenting with the demon in attempts to have my mail
automatically incorporated.

I was using the following in my .gnus.el:

(setq gnus-use-demon t)
(gnus-demon-add-scanmail)

What happened is that I incorporated a bunch of mail (mostly in two
mailing lists, so not that importmant). It seems to have been split
into the appropriate groups. However, the group .overview files don't
indicate that they're present, nor are the files phyically there. The
active file does indicate that they're present though.

When I tried copying the Incoming file to spool and re-incing, nothing
happened. I assume that somewhere is a hashtable of message id's, and
gnus is just not re-processing message id's it has seen before? I
tried changing the message id on one piece, and it was processed
(although the rest weren't), which seems to validate this hypothesis.

Has anyone else had problems with the demon doing this kind of thing
before? Any ideas here? Seems far to vague for a real bug report, but
it's definitely weird.

-eri


-- 
				Erik Selberg
"I get by with a little help	selberg@cs.washington.edu
 from my friends."		http://www.cs.washington.edu/homes/selberg

Re: bug? 39/40 w/ demon

[Lars Magne Ingebrigtsen]

Erik Selberg <selberg@cs.washington.edu> writes:

> What happened is that I incorporated a bunch of mail (mostly in two
> mailing lists, so not that importmant). It seems to have been split
> into the appropriate groups. However, the group .overview files don't
> indicate that they're present, nor are the files phyically there. The
> active file does indicate that they're present though.

Hm...  I haven't heard of this bug before.  I have no idea what could
be causing the .overview files not to be updated, really.

> When I tried copying the Incoming file to spool and re-incing, nothing
> happened. I assume that somewhere is a hashtable of message id's, and
> gnus is just not re-processing message id's it has seen before? I
> tried changing the message id on one piece, and it was processed
> (although the rest weren't), which seems to validate this hypothesis.

If you have `nnmail-treat-duplicates' set to `delete', all duplicates
will be deleted.

-- 
(domestic pets only, the antidote for overdose, milk.)
  lmi@gnus.org * Lars Magne Ingebrigtsen

Re: bug? 39/40 w/ demon

[Erik Selberg]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > When I tried copying the Incoming file to spool and re-incing, nothing
> > happened. I assume that somewhere is a hashtable of message id's, and
> > gnus is just not re-processing message id's it has seen before? I
> > tried changing the message id on one piece, and it was processed
> > (although the rest weren't), which seems to validate this hypothesis.
> 
> If you have `nnmail-treat-duplicates' set to `delete', all duplicates
> will be deleted.

right. course, this assumes that the original wasn't... :)
-- 
				Erik Selberg
"I get by with a little help	selberg@cs.washington.edu
 from my friends."		http://www.cs.washington.edu/homes/selberg