Gnus development mailing list
 help / color / mirror / Atom feed
From: shigeki@mediawars.ne.jp (Shigeki Uno)
Cc: ding@gnus.org
Subject: Re: Force Oort to verify sigs?
Date: 18 Mar 2001 04:53:31 +0900	[thread overview]
Message-ID: <8666h8yxxg.fsf@mediawars.ne.jp> (raw)
In-Reply-To: <868zm4yzat.fsf@mediawars.ne.jp>

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

oops, previous email i sent didn't complain of gpg verify and
succeeded in verifying this time (it's for the first time). 

i've never seen such success. ;)

(1) minibffer

  Good signature from 
            'Shigeki Uno (UNO PROJECT) <shigeki@mediawars.ne.jp>'

(2) body  

  [[PGP Signed Part:OK]]

  snip

  [[End of PGP Signed Part]] 
 

# i don't know why i scceed this time. 


shigeki@mediawars.ne.jp (Shigeki Uno) writes:

> Hi, ding users.
> 
> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > Alan Shutko <ats@acm.org> writes:
> > 
> > > Just started using Oort to play with GPG, and I've noticed that it
> > > doesn't automatically verify sigs.  One has to click the button or do
> > > a W s.
> > > 
> > > Any way to get that to happen automatically?  I didn't see a
> > > gnus-treat variable that seemed to be associated.
> > 
> > (setq mm-verify-option 'known)
> 
> as for me, it complains the following error in mini buffer.
> 
>  BAD SIGNATURE claiming to be from 
>              'Shigeki Uno (UNO PROJECT) <shigeki@mediawars.ne.jp>'
> 
> is something wrong with my Gnupg-1.0.4?
> 
> and also, even if i don't set (setq mm-verify-option 'known), my emails
> these are pgp(gpg)'ed always has been shown like this:
>  
>  [[PGP Signed Part:Failed]]
> 
>  snip
> 
>  [[End of PGP Signed Part]]
>   
> am i wrong?
> 
> 
> Gnus/5.090001 (Oort Gnus v0.01)
> emacs 20.7
> Gnupg-1.0.4
> 
> Regards,
> -- 
> Shigeki Uno <mailto:shigeki@mediawars.ne.jp>

- -- 
Shigeki Uno <mailto:shigeki@mediawars.ne.jp>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (NetBSD)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjqzwJoACgkQ28mRkyGnSWmVsACeKrkNgETAQld6XPMmW/fiSYgL
SyYAoOZkO3YQGwgn1Z16+PjlTmjnZouZ
=wSTA
-----END PGP SIGNATURE-----



  reply	other threads:[~2001-03-17 19:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-17 16:44 Alan Shutko
2001-03-17 16:52 ` ShengHuo ZHU
2001-03-17 19:23   ` Shigeki Uno
2001-03-17 19:53     ` Shigeki Uno [this message]
2001-03-18  1:28     ` Daniel Pittman
2001-03-21 22:21       ` Jake Colman
2001-03-22  2:10         ` Colin Marquardt
2001-03-22  3:01         ` Daniel Pittman
2001-03-22 18:19           ` Jake Colman
2001-03-22 20:34             ` Paul Jarc
2001-03-22 21:47               ` Jake Colman
2001-03-22 22:47                 ` Paul Jarc
2001-03-23  1:39               ` Russ Allbery
2001-03-23 15:54                 ` Paul Jarc
2001-03-26 17:20                   ` Jake Colman
2001-03-26 17:56                     ` Josh Huber
2001-03-26 18:58                       ` Jake Colman
2001-03-18  2:07     ` Jack Twilley
2001-03-17 16:52 ` Karl Kleinpaste

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8666h8yxxg.fsf@mediawars.ne.jp \
    --to=shigeki@mediawars.ne.jp \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).