crossposted mail articles not expired?

crossposted mail articles not expired?

[Anil B. Somayaji]

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

Hello!  There's a little "feature" that has been bugging me for a little
while now.  I have lots of nnml groups, and my split rules often
result in crossposts.  This all works fine, and in fact I love it.
Unfortunately, when I have an article expire in one group, it remains
present in the other crossposted groups.  Even worse, the article now
has Xref lines referring to non-existent files (hard links, really).

Here's a real example.  I have a message that was crossposted between my
"adaptive" and "forrest" directories.  In the header, it has:

  Xref: atropos.cs.unm.edu forrest:1000 adaptive:276

However, I had marked the article for expiration in the adaptive
group, and so adaptive:276 no longer exists.  But forrest:1000 does,
with the reference to adaptive:276!

Perhaps it should be an option, but it would be nice if gnus
automatically expired all copies of an article.  Or, maybe when you
manually mark an article for expiration (which is all I do - I'm a
pack rat), there would be a command for "mark to expire this article
and all of its crosspostings."  And, if this is not done, maybe the
bogus Xref should be removed.

I'd be happy to hack on this, if someone can point me to the relevant
functions - I haven't studied the gnus source much.

BTW, I'm running pgnus 0.66.  Thanks!

  --Anil

-- 
Anil Somayaji (soma@cs.unm.edu)
http://www.cs.unm.edu/~soma
+1 505 872 3150

[-- Attachment #2: Type: application/pgp-signature, Size: 284 bytes --]

Re: crossposted mail articles not expired?

[Graham Murray]

soma@cs.unm.edu (Anil B. Somayaji) writes:

> Perhaps it should be an option, but it would be nice if gnus
> automatically expired all copies of an article.  Or, maybe when you
> manually mark an article for expiration (which is all I do - I'm a
> pack rat), there would be a command for "mark to expire this article
> and all of its crosspostings."  And, if this is not done, maybe the
> bogus Xref should be removed.

Or even better, IMHO, would be if crossposted mail were treated in the
same way as news servers handle expiring crossposted news. That is,
the article is not removed until it has expired in *all* the
groups. (Though I do use total-expire in most mail groups, so articles
do not need manual expiry). On the other hand B del should remove the
article immediately in all crossposted groups.

Re: crossposted mail articles not expired?

[Anil B. Somayaji]

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

Graham Murray <graham@barnowl.demon.co.uk> writes:

> On the other hand B del should remove the article immediately in 
> all crossposted groups.

Nope - B del does exactly the same thing as regular expiration.  I
just tried it.  Oh well.

  --Anil

-- 
Anil Somayaji (soma@cs.unm.edu)
http://www.cs.unm.edu/~soma
+1 505 872 3150

[-- Attachment #2: Type: application/pgp-signature, Size: 284 bytes --]

Re: crossposted mail articles not expired?

[Yair Friedman]

soma@cs.unm.edu (Anil B. Somayaji) writes:

> [1  <text/plain; US-ASCII (7bit)>]
> Graham Murray <graham@barnowl.demon.co.uk> writes:
> 
> > On the other hand B del should remove the article immediately in 
> > all crossposted groups.
> 
> Nope - B del does exactly the same thing as regular expiration.  I
> just tried it.  Oh well.

B del does delete articles, but look at nnmail-keep-last-article this
might cause the delays you experiencing.
--
Yair Friedman.

Re: crossposted mail articles not expired?

[Matt Armstrong]

Graham Murray <graham@barnowl.demon.co.uk> writes:

> On the other hand B del should remove the article immediately in all
> crossposted groups.

For what it is worth, I like the way B del works (and each group
having its own copy of the mail in general).

-- 
matta

Re: crossposted mail articles not expired?

[Kai.Grossjohann]

I think there was some discussion on handling expiry a year or so
ago.  The consensus seemed to be that something should be done about
it, and there should be ways of saying:

  - delete this article from this group
  - delete this article from all groups

Here, `delete' means after the expiry wait time, of course.

For the moment, you can do two things:

(1) Use total-expire and gnus-use-cross-reference.
    This means that articles will be removed from all groups when
    marked as read.  Ticking an article means it will stay in that
    group, I think.

(2) Else.
    This means that each copy is treated separately.

kai
-- 
This gubblick contains many nonsklarkish English flutzpahs,
but the overall pluggandisp can be glorked from context. -- David Moser