Re: Prevent B c/B m from createing dups in target group

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Harry Putnam <reader@newsguy.com> writes:

> My OP was asking for an outline of how to go about starting to create
> that functionality in gnus.  Once finished it could hopefully be
> submitted for consideration as an inclusion.

Oh, right.

In that case, here's how I would do it.

I'd make an option to have mail backends cache the group/message-id
pair somewhere.  Take the nnmail.*cache.* functions as a starting
point.  (They only cache on a message-id basis.)  Then have an option
to refuse entry into the mail backends when you find a
group/message-id pair that matches.

The problem with this approach is that if you move a message out of a
group, you have to remove it from the cache as well.  And what happens
if you delete it outside of Gnus?  You wouldn't then be able to copy a
new copy into the group.

Scratch that.

Perhaps the nn.*-request-accept-article function could have an option
to go through all the messages in the group and see whether the
message is already there.  But that would take a looong time.

> 3) Suppression seems very much like taking pain pills to mask an
>    injury while continuing to grind your body to dust...

On the other hand, if you have a slight headache, a pain killer makes
it all go away and makes you happy and shiny again.

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