Babyl Updating..

Babyl Updating..

[Patrick Audley]

	I _love_ the sgnus support for reading mail, but I share my
mail box with VM sometimes.  Is there anyway to have gnus update the
unseen status (and perhaps even flag expired messages as deleted ala
Rmail).

	Secondly, my mail file seems to bloat to 2M and stay steadily
there..  I am expiring all my read mail and have the expiry days set
to one, what am I doing wrong?

					Thanks.

-- 
... I Still miss my ex-wife.....BUT, My aim is improving!
/*----------------------------------------------------------------.
| The Crystal Wind is The Storm,      Patrick Audley              |
|    The Storm is The Data,     ______/\/\/\/\/\/\/\_______       |
|      The Data is Life.        InterNet: paudley@portal.ca       |
`----------------------------------------------------------------*/

Re: Babyl Updating..

[Kai Grossjohann]

>>>>> On Tue, 28 Nov 95 23:59:25 -0800, Patrick Audley <paudley@portal.ca> said:

  Patrick> Secondly, my mail file seems to bloat to 2M and stay
  Patrick> steadily there..  I am expiring all my read mail and have
  Patrick> the expiry days set to one, what am I doing wrong?

There are a number of things:  First, messages must be explicitly
marked for expiry (E, I think) to be expirable unless the total-expire
parameter is set for the particular group (then, read messages are
expirable, too).  Secondly, no expirable message is deleted from disk
unless you call the expire function (C-M-c from the *Group* buffer or
something).

hth,
        \kai{}
--
Have you hugged your signature today?

Re: Babyl Updating..

[Lars Magne Ingebrigtsen]

Patrick Audley <paudley@portal.ca> writes:

> 	I _love_ the sgnus support for reading mail, but I share my
> mail box with VM sometimes.  Is there anyway to have gnus update the
> unseen status (and perhaps even flag expired messages as deleted ala
> Rmail).

This is on the todo list, but it might take a while.

-- 
Home is where the cat is.

Re: Babyl Updating..

[Steven L. Baur]

>>>>> "Kai" == Kai Grossjohann <grossjoh@dusty.informatik.uni-dortmund.de> writes:
    Kai> There are a number of things: First, messages must be
    Kai> explicitly marked for expiry (E, I think) to be expirable
    Kai> unless the total-expire parameter is set for the particular
    Kai> group (then, read messages are expirable, too).  Secondly, no
    Kai> expirable message is deleted from disk unless you call the
    Kai> expire function (C-M-c from the *Group* buffer or something).

This isn't true of all backends.  Expiration is performed automatically
on quit out of *Summary* buffer if any articles are marked for expire
in nnml groups, for example.

-- 
steve@miranova.com baur