[PATCH] Expiry-target for nnmh

[PATCH] Expiry-target for nnmh

[janneke]

Hi,

My first patch to Gnus implements expiry-target for the nnmh backend.

    http://appel.lilypond.org/software/gnus-5.8.7.jcn1.diff

Is expiry-target widely used?  I'm new to Gnus; and sometimes a bit
confused about what one would actually use.  The auto-expiry feature
of read articles looks very promising, but it's not exactly what I
want.  Before, using plain mh and scripts, I used to move only mail
that I had answered semi-automatically to my archives, so that my
read-but-unanswered-messages would stay in my inboxes for
manual-archiving.  Can this be easily automated with Gnus?

While this was fine for personal mail, it was maybe not the perfect
solution for mailinglist-mail (answering bug-reports).  With Gnus, it
would be possible to improve on this, by auto-expiring only mail that
has been read, and of which the tread is longer than 1.  This way,
unanswered bug reports/help requests won't expire untill they're
answered by someone.  How do you handle this, or does this require
some more hacking?

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: [PATCH] Expiry-target for nnmh

[Kai Großjohann]

I suspect that most people use `!' (ticked) or `?' (dormant) to mark
messages where something still needs to be done.

I used to have a group where I received a LOT of mail, there I would
do a manual moving of old articles every month or so.  This way, most
of the old mail that I was needing currently could be accessed easily.

Also, it helps to not use total-expire.  Then, entering a group
doesn't need to display as many messages.  Fetching headers is fairly fast.

kai
-- 
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing

Re: [PATCH] Expiry-target for nnmh

[ShengHuo ZHU]

janneke@gnu.org writes:

> Hi,
> 
> My first patch to Gnus implements expiry-target for the nnmh backend.
> 
>     http://appel.lilypond.org/software/gnus-5.8.7.jcn1.diff

I've installed the patch and changed a little.

ShengHuo

Feature request: "Security" feature

[Raja R Harinath]

Hi,

It would be nice if the buttons, introduced in the article buffer by
the "gnus-*-verify-*" functions, had some useful action -- like
showing the output of the underlying program.

Say, you have the button

  [[PGP Verified: OK]]

Clicking on it would produce:

  [[PGP Verified: OK]
  Good Signature from: John Q. Signer <jqs@foo.com>
  No trust path established.
  ]

If we don't pay attention to the status bar while it's verifying, we
lose this information (looking at *Messages* is more painful than
clicking a button in the article).

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash

Re: Feature request: "Security" feature

[ShengHuo ZHU]

Raja R Harinath <harinath@cs.umn.edu> writes:

> Hi,
> 
> It would be nice if the buttons, introduced in the article buffer by
> the "gnus-*-verify-*" functions, had some useful action -- like
> showing the output of the underlying program.
> 
> Say, you have the button
> 
>   [[PGP Verified: OK]]
> 
> Clicking on it would produce:
> 
>   [[PGP Verified: OK]
>   Good Signature from: John Q. Signer <jqs@foo.com>
>   No trust path established.
>   ]
> 
> If we don't pay attention to the status bar while it's verifying, we
> lose this information (looking at *Messages* is more painful than
> clicking a button in the article).

The problem is how to capture those messages from mailcrypt or gpg.el.
Anyone knows?

ShengHuo

Re: Feature request: "Security" feature

[Kevin A. Burton]

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

Raja R Harinath <harinath@cs.umn.edu> writes:

> Hi,
> 
> It would be nice if the buttons, introduced in the article buffer by
> the "gnus-*-verify-*" functions, had some useful action -- like
> showing the output of the underlying program.
<snip>

mailcrypt will throw an error if a signature doesn't match the associated key in
your PGP/GPG keyring.

A while back I noticed a mailing list manager that was inserting a little
message inside my signature and it was causing errors... really cool.  I never
new that it did automatic validation :).  If you pay attention it will remove
the PGP signature info and you see it doing it in *messages*

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
        Cell: 408-910-6145 URL: http://relativity.yi.org ICQ: 73488596 

proprietary == evil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE6JxWkAwM6xb2dfE0RAg+cAJ9UpvXj9Kk4ee3mEYT8qvphhJejWgCgn9CB
loUf0C7vZv9LY/7Y/7t8DmI=
=YXd+
-----END PGP SIGNATURE-----



Semtex Qaddafi Kennedy Clinton $400 million in gold bullion arrangements
Ft. Bragg SEAL Team 6 Rule Psix Nazi North Korea ammunition supercomputer kibo
Soviet

Re: Feature request: "Security" feature

[Michael Welsh Duggan]

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

> Raja R Harinath <harinath@cs.umn.edu> writes:
> 
> > Hi,
> > 
> > It would be nice if the buttons, introduced in the article buffer by
> > the "gnus-*-verify-*" functions, had some useful action -- like
> > showing the output of the underlying program.
> > 
> > Say, you have the button
> > 
> >   [[PGP Verified: OK]]
> > 
> > Clicking on it would produce:
> > 
> >   [[PGP Verified: OK]
> >   Good Signature from: John Q. Signer <jqs@foo.com>
> >   No trust path established.
> >   ]
> > 
> > If we don't pay attention to the status bar while it's verifying, we
> > lose this information (looking at *Messages* is more painful than
> > clicking a button in the article).
> 
> The problem is how to capture those messages from mailcrypt or gpg.el.
> Anyone knows?

I don't know about mailcrypt, but capturing the information from
gpg.el looks quite easy.  In `mml2015-gpg-verify', the `gnus-details'
handle gets set to this information, but only if the signing failed!
If you move the clause:
            (mm-set-handle-multipart-parameter 
             mm-security-handle 'gnus-details 
             (with-current-buffer mml2015-result-buffer
               (buffer-string)))
out of the unless, you should get what you want for free.

-- 
Michael Duggan
(md5i@cs.cmu.edu)

Re: Feature request: "Security" feature

[ShengHuo ZHU]

Michael Welsh Duggan <md5i@cs.cmu.edu> writes:

> I don't know about mailcrypt, but capturing the information from
> gpg.el looks quite easy.  In `mml2015-gpg-verify', the `gnus-details'
> handle gets set to this information, but only if the signing failed!
> If you move the clause:
>             (mm-set-handle-multipart-parameter 
>              mm-security-handle 'gnus-details 
>              (with-current-buffer mml2015-result-buffer
>                (buffer-string)))
> out of the unless, you should get what you want for free.

Done.

ShengHuo