Re: PGP/MIME integration

On Sat, Nov 22, 2003 at 01:42:13AM +0100, Urs Janßen wrote:
| [your message did not make it to tin-users as this is a closed list
| and your address is not on the subscription list]

Oops.  My bad.  I was subscribed as "dman+tin", but sent the message
as "dman".  I've now switched the subscription address.

I also tried posting via NNTP, but I don't think the newsgroup accepts
posts.  (seems kinda odd that I can't get newreader help via news)

BTW, the "subscribe" link on the web site points to the wrong address.
It looks like an older mailman address, but that only invokes a bot
telling me to email majordomo instead.  (not the end of the world, but
would probably be an improvement)

| > Is my tin setup just poor, or does tin have really poor PGP/MIME
| > support?
| 
| sort of the later, this has several reasons:
| a) pgp-signing of messages (either in the old way that tin currently
|    proudces or via MIME-sections like it's done in mutt) isn't very
|    welcome in most groups on usenet and thus it's usualy not done at
|    all
[...]
| as multipart messages are usualy not very welcome on usenet we didn't
| implement that (yet). the "old-style" pgp-support was written before
| the MIME-section stuff came up.

I see.  Come to think of it, the groups where I usually see signatures
are the gmane-hosted mirrors of "techie" mailling lists.  I had pretty
much just assumed the rest of the messages were sent by people who
didn't care to sign them or with software that didn't automate it.

| > tin automatically sign messages, rather than manually requesting it
| > for each and every message?  Additionally, can tin automatically
| 
| sort of: via header signing by using tinews.pl (included in the
| source-tarball in the tools-dir) as (built-in) inews replacement.

Ooh, I wasn't thinking of that.  If I get a properly set up inews
program, and then front-end that with a script, then that could work.
The "inews" program can't get input from the terminal, though, can it?
I think that would be necessary for gpg to unlock the private key ...

(it doesn't sound like tinews.pl does what I want, but the
architecture looks like a possible fit)

| > What about preprocessing messages before displaying them in the pager?
| 
| currently there is no way to do that (a few years ago some announced
| perl-hooks for tin, but I never saw his beta code. I guess he gave
| up. perl-hooks for certain actions are on my TODO-list, but with a
| very very low priority).

Hmm.  Maybe if I'm bored some day and don't have enough
responsibilities and commitments to keep me more than busy I'll code
it myself then.  I think a parallel to mutt's "display_filter" it
would be very useful.


On Sat, Nov 22, 2003 at 02:44:08AM +0100, Urs Janßen wrote:
| > > for each and every message?  Additionally, can tin automatically
| > > verify PGP/MIME signatures when reading messages?
|
| if you have set up your mail.cap file accordingly and the mime-part
| is propper announced and you use metamail_prog (--internal or
| metamutt) and have ask_for_metamail=OFF then autoverify should work.

Oh, ok.  I'll check on the --internal option there (that would still
use the internal pager, I presume) and hooking pgpverify into the
mailcap.  That could be the solution I was looking for.  Thus far
metamail has been more annoying than not, since I haven't come across
any "attachments" other than PGP signatures (and metamail currently
just dumps then through 'less') and the message body that goes with it
(which loses all its color, headers, and ability to jump to the next
message when metamail displays it with less).  I do realize that those
aren't tin's fault, apart from the situation not arising if tin
handled the pgp internally :-).


I was thinking of using tin, with gmane, instead of mutt for some
high-volume mailing lists I have been on.  I like tin's flagging by
age (the <2days vs. older marks) and the auto-expiring of old
messages.  It seems less likely that cruft would build up so much that
way :-).  Currently I sometimes "lose" messages if I don't read them
right away and then they build up on disk until I take the time to
clean them out.  Perhaps I should just make an automated system for
purging old messages in mailboxes :-).


Thanks for your explanation.  It keeps me from wondering, and gives me
some ideas to follow up with.

-D

-- 
\begin{humor}
Disclaimer:
If I receive a message from you, you are agreeing that:
   1. I am by definition, "the intended recipient"
   2. All information in the email is mine to do with as I see fit and make
        such financial profit, political mileage, or good joke as it lends
        itself to. In particular, I may quote it on USENET or the WWW.
   3. I may take the contents as representing the views of your company.
   4. This overrides any disclaimer or statement of confidentiality that may
        be included on your message
\end{humor}
.
www: http://dman13.dyndns.org/~dman/            jabber: [email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/vuWwiB6vp1xAVUARAuy+AJ47x/4NPjxXIqoJZXuhzVYp4i/TxACeJPDn
hDf+o2dxtxHhbSqzyFpRqqk=
=f6A4
-----END PGP SIGNATURE-----