periodic archiving of groups?

periodic archiving of groups?

[Anil B. Somayaji]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a friend who gets a lot of email, uses gnus, and wants to
regularly archive her mail.  For example, she'd like messages in
group1 archived every month, group2 archived every year, etc.  When
entering a group, you would just see the un-archived messages by
default, but there should be some easy way to look at the older
archives.

Is there an easy way to do this in gnus?  Right now we're manually
creating new groups and moving old messages into those groups - of
course, this is not very pleasant.  Anyone have any better
suggestions?

Thanks.

  --Anil

- -- 
Anil Somayaji (soma@cs.unm.edu)
http://www.cs.unm.edu/~soma
+1 505 872 3150
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)

iEYEARECAAYFAjpniDkACgkQXOpXEmNZ3SeIBACeJe7J7GD3BuTFXSxhShOSEiqp
3MsAnRq1VSs5poaaRNFnc8EW/LTqMmTL
=Qspw
-----END PGP SIGNATURE-----

Re: periodic archiving of groups?

[ShengHuo ZHU]

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

> I have a friend who gets a lot of email, uses gnus, and wants to
> regularly archive her mail.  For example, she'd like messages in
> group1 archived every month, group2 archived every year, etc.  When
> entering a group, you would just see the un-archived messages by
> default, but there should be some easy way to look at the older
> archives.
> 
> Is there an easy way to do this in gnus?  Right now we're manually
> creating new groups and moving old messages into those groups - of
> course, this is not very pleasant.  Anyone have any better
> suggestions?

Maybe nnmail-expiry-target helps. See info node "Expiring Mail" for
the details.

ShengHuo

Small user interface patch to gpg.el

[Colin Marquardt]

*** /tmp/gpg.el~	Thu Jan 18 17:47:08 2001
--- /tmp/gpg.el	Thu Jan 18 17:47:08 2001
***************
*** 632,638 ****
        ;; temporary file resides in a world-writable directory.
        (unless (or (memq system-type '(windows-nt cygwin32 win32 w32 mswindows))
  		  (eq (file-modes gpg-temp-directory) 448)) ; mode 0700
! 	(error "Directory for temporary files must have mode 0700."))
        (setq name (make-temp-name name))
        (let ((mode (default-file-modes)))
  	(unwind-protect
--- 632,638 ----
        ;; temporary file resides in a world-writable directory.
        (unless (or (memq system-type '(windows-nt cygwin32 win32 w32 mswindows))
  		  (eq (file-modes gpg-temp-directory) 448)) ; mode 0700
! 	(error "Directory for temporary files (%s) must have mode 0700." gpg-temp-directory))
        (setq name (make-temp-name name))
        (let ((mode (default-file-modes)))
  	(unwind-protect

Re: Small user interface patch to gpg.el

[ShengHuo ZHU]

Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:

> *** /tmp/gpg.el~	Thu Jan 18 17:47:08 2001
> --- /tmp/gpg.el	Thu Jan 18 17:47:08 2001
> ***************
> *** 632,638 ****
>         ;; temporary file resides in a world-writable directory.
>         (unless (or (memq system-type '(windows-nt cygwin32 win32 w32 mswindows))
>   		  (eq (file-modes gpg-temp-directory) 448)) ; mode 0700
> ! 	(error "Directory for temporary files must have mode 0700."))
>         (setq name (make-temp-name name))
>         (let ((mode (default-file-modes)))
>   	(unwind-protect
> --- 632,638 ----
>         ;; temporary file resides in a world-writable directory.
>         (unless (or (memq system-type '(windows-nt cygwin32 win32 w32 mswindows))
>   		  (eq (file-modes gpg-temp-directory) 448)) ; mode 0700
> ! 	(error "Directory for temporary files (%s) must have mode 0700." gpg-temp-directory))
>         (setq name (make-temp-name name))
>         (let ((mode (default-file-modes)))
>   	(unwind-protect

Committed.

ShengHuo

Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el)

[Colin Marquardt]

I just noticed that all my mails and postings have an X-Draft-From:
header (this one too I guess, since I will not manually remove it).

| To: ding@gnus.org
| Date: 18 Jan 2001 17:48:01 -0800
| X-Draft-From: ("nnimap+nsmail:INBOX" 9422)

I am running the gnus-CURRENT-20010116 snapshot, and I generate the
headers when starting to compose the message (it escapes me ATM what
the variable to tweak that is). I can see the header linger up
there, soon to be sent out with the rest of the message. See? Here it
goe

Re: Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el)

[Kai Großjohann]

The X-Draft-From header is used by Gnus to note state for saving
drafts.  It is used to apply the right posting style even if you start
a message, then save it as a draft (using `C-c C-d'), then send it
later on.

kai
-- 
Be indiscrete.  Do it continuously.

Re: Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el)

[Karl Kleinpaste]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> The X-Draft-From header is used by Gnus to note state for saving
> drafts.

Yes, but it's supposed to be left only in a Gcc'd copy, and never sent
out on the wire.  Weirdly, Colin's mail still has it in what gets sent
out.  That's a problem, but I don't share it (X-D-F is gone from what
goes out the wire for me), so I don't know how he would fix it.

Re: Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el)

[Kai Großjohann]

On 19 Jan 2001, Karl Kleinpaste wrote:

> Yes, but it's supposed to be left only in a Gcc'd copy, and never
> sent out on the wire.

Hm.  See message-ignored-mail-headers and
message-ignored-news-headers.  Maybe Colin has frobbed these?

kai
-- 
Be indiscrete.  Do it continuously.

Re: Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el)

[Colin Marquardt]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> On 19 Jan 2001, Karl Kleinpaste wrote:
> 
> > Yes, but it's supposed to be left only in a Gcc'd copy, and never
> > sent out on the wire.
> 
> Hm.  See message-ignored-mail-headers and
> message-ignored-news-headers.  Maybe Colin has frobbed these?


Ah, indeed, in both their property lists I see:

  standard-value: ("^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|X-Draft-From:")
  saved-value:    ("^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Complaints-To:")

so I must have changed it somehow/somewhen, thanks.

BTW, it looks to me that "X-Draft-From:" should also have the
beginning-of-line in front of its regexp part. A small bug?

Colin

Re: Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el)

[Simon Josefsson]

Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:

> BTW, it looks to me that "X-Draft-From:" should also have the
> beginning-of-line in front of its regexp part. A small bug?

Fixed.

S/MIME buttons

[Colin Marquardt]

Hi,

I'm not sure how well my gnus-CURRENT-20010116 snapshot is supposed
to treat S/MIME signatures, but when opening a posting, the buttons
look like this:


[[S/MIME Signed Part:Undecided]]
[...]
[2. S/MIME Cryptographic Signature --- application/x-pkcs7-signature; smime.p7s]...

[[End of S/MIME Signed Part]]


Now, when I press button-2 on the first button, nothing happens,
except that the "[2. S/MIME Cryptographic Signature ..." becomes a
"[4. S/MIME Cryptographic Signature ...". This number increases by 2
every time I press the first button.
If you need the raw posting, I can provide it.

If S/MIME is not (yet) supported, can it say so in the echo area?

Cheers,
  Colin

Re: S/MIME buttons

[Simon Josefsson]

Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:

> Now, when I press button-2 on the first button, nothing happens,
> except that the "[2. S/MIME Cryptographic Signature ..." becomes a
> "[4. S/MIME Cryptographic Signature ...". This number increases by 2
> every time I press the first button.

No error?  Do `W s' from the summary buffer behave the same?

I commited a bug fix to be able to button-2 on the button rather than
using `W s'.

Do you have "openssl" (OpenSSL 0.9.6) in your path?

I remember seeing the increasing-mime-part-number problem before, but
I thought it was fixed for long now.

> If you need the raw posting, I can provide it.

Forward it to me and I'll have a look.  But it's probably some other
problem.

Re: S/MIME buttons

[ShengHuo ZHU]

Simon Josefsson <sj@extundo.com> writes:

> Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:
> 
> > Now, when I press button-2 on the first button, nothing happens,
> > except that the "[2. S/MIME Cryptographic Signature ..." becomes a
> > "[4. S/MIME Cryptographic Signature ...". This number increases by 2
> > every time I press the first button.

I think we should hide the signature.

> No error?  Do `W s' from the summary buffer behave the same?
> 
> I commited a bug fix to be able to button-2 on the button rather than
> using `W s'.
> 
> Do you have "openssl" (OpenSSL 0.9.6) in your path?
> 
> I remember seeing the increasing-mime-part-number problem before, but
> I thought it was fixed for long now.

Because the part is reparsed, the part number increases, one for the
text part, one for signature.  It is not easy to fix.

ShengHuo

Re: S/MIME buttons

[Colin Marquardt]

Simon Josefsson <sj@extundo.com> writes:

> Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:
> 
> > Now, when I press button-2 on the first button, nothing happens,
> > except that the "[2. S/MIME Cryptographic Signature ..." becomes a
> > "[4. S/MIME Cryptographic Signature ...". This number increases by 2
> > every time I press the first button.
> 
> No error?  Do `W s' from the summary buffer behave the same?

No error with `W s' too. I explicitly looked into the 
" *Message-Log*" buffer (this is XEmacs 21.1.9).

> Do you have "openssl" (OpenSSL 0.9.6) in your path?

Uhm, no, and I cannot compile it (some problem in my environment that
I cannot fix).

Could it give an error message if openssl is not available (or is
this what you expect to see?).

> > If you need the raw posting, I can provide it.
> 
> Forward it to me and I'll have a look.  But it's probably some other
> problem.

Will do.

Thanks,
  Colin

Re: periodic archiving of groups?

[Alan Shutko]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Maybe nnmail-expiry-target helps. See info node "Expiring Mail" for
> the details.

Thanks!  I don't know if it helps the original poster, but it's just
what _I've_ been looking for.

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
Spelling is a lossed art.

Re: periodic archiving of groups?

[Alan Shutko]

Alan Shutko <ats@acm.org> writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > Maybe nnmail-expiry-target helps. See info node "Expiring Mail" for
> > the details.
> 
> Thanks!  I don't know if it helps the original poster, but it's just
> what _I've_ been looking for.

Actually, I've realized I'm looking for something slightly different.
I ideally want two levels of expiry.  I'd like to be able to mark
articles E and have them go away (in seven days or whatever) and then
have pretty much everything get archived after 30.  Hmmmm....

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
Calm down, it's *only* ones and zeroes.

Re: periodic archiving of groups?

[Oystein Viggen]

Alan Shutko wrote: 

> Actually, I've realized I'm looking for something slightly different.
> I ideally want two levels of expiry.  I'd like to be able to mark
> articles E and have them go away (in seven days or whatever) and then
> have pretty much everything get archived after 30.  Hmmmm....

Couldn't you use group names that end in something like -year-month, so
that new groups are created every month?  A friend of mine uses a system 
like this and is very happy with it.

Oystein
-- 
If it ain't broke, don't break it.

Re: periodic archiving of groups?

[Alan Shutko]

Oystein Viggen <oysteivi@tihlde.org> writes:

> Couldn't you use group names that end in something like -year-month, so
> that new groups are created every month?  A friend of mine uses a system 
> like this and is very happy with it.

I do, but I'd like some things to get deleted, not archived.  For
example, some spam does find its way into my inbox, and a lot of my
work email is of only short-term interest.

I can do an explicit B DEL to delete messages, but it would be nice if
things I marked as E would be deleted after some time, but everything
alive after a longer amount of time got archived.  Sort of a
"total-archive".

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
Nothing is ever a total loss; it can always serve as a bad example.

Re: periodic archiving of groups?

[Oystein Viggen]

Alan Shutko wrote: 

> I can do an explicit B DEL to delete messages, but it would be nice if
> things I marked as E would be deleted after some time, but everything

You of course know of gnus-group-expire-all-groups?

Oystein
-- 
If it ain't broke, don't break it.

Re: periodic archiving of groups?

[Alan Shutko]

Oystein Viggen <oysteivi@tihlde.org> writes:

> You of course know of gnus-group-expire-all-groups?

Yes.  But it doesn't help.  That's because I want expiration to do two
different things in the same group.

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
It's clever, but is it art?

Re: periodic archiving of groups?

[Rob Browning]

Oystein Viggen <oysteivi@tihlde.org> writes:

> Couldn't you use group names that end in something like -year-month,
> so that new groups are created every month?  A friend of mine uses a
> system like this and is very happy with it.

For me, this wouldn't be optimal.  I don't want a new group to get
created at the beginning of every month.  When that happens, all
of a sudden, I've got an empty group with no context for the current
incoming messages.

What I'd like to be able to say is "every month, archive the messages
from the month that's 6 months ago into a new group".

I wouldn't mind having to do this manually, though it'd be really nice
to have an automated way to handle it.

I might be interested in writing the elisp for this if someone could
get me pointed in the right direction (I'd want to base the splitting
on the actual message date, not the article numbers...)

-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930

Re: periodic archiving of groups?

[Harry Putnam]

Rob Browning <rlb@cs.utexas.edu> writes:

> I wouldn't mind having to do this manually, though it'd be really nice
> to have an automated way to handle it.
> 
> I might be interested in writing the elisp for this if someone could
> get me pointed in the right direction (I'd want to base the splitting
> on the actual message date, not the article numbers...)

The elisp for most of it is already written.  You seem to be talking
of nnml groups here (judging from previous post).  You can do this by
writing a separtate set of split rules and keeping them in a separate
file.  When you want to do this archiving you would load that file
which would override the split in .gnus.  Then enter the subject
group with C-u <RET> mark all but the last mnths messages by using the
limit `/ t' features then respool them according to your newly loaded
rules.

The new rules will look like:
(setq nnmail-split-methods 
  '(("SOMEGROUP_FEB-00" "^Date:.*Feb.*2000") 
     ("SOMEGROUP_MAR-00" "^Date:.*Mar.*2000")
etc etc
When done have gnus reread ~/.gnus or restart, to reload the original
split urules then back to business as usual.

You'll probably need to run `nnml-generate-nov-databases' since some
groups will have been severely truncated.  


etc etc

Re: periodic archiving of groups?

[Kai Großjohann]

With the right backend and the right settings, you might not have to
move articles to a different group at all.  For example,

(setq gnus-fetch-old-headers 500)

and using nnml should get you by.  The old articles will be there,
marked as read, but they won't be displayed by default.

kai
-- 
Be indiscrete.  Do it continuously.

Re: periodic archiving of groups?

[Rob Browning]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> and using nnml should get you by.  The old articles will be there,
> marked as read, but they won't be displayed by default.

But this falls down once you get over about 10000 articles, at least
on linux, using nnml and ext2...

It's painfully slow at that point.

-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930