Multi-Line Colored Quoting?

[Phil Gregory]

I really like mutt's ability to color quoted text.  Unfortunately, it
appears to only be able to recognize quotes on a single line.  On some
mailing lists I'm on, people use multiline quoting mechanisims that
mutt doesn't understand.

An example:

 This is the beginning of the quoted text.  It continues for a bit
and wraps onto other lines.  This line doesn't have any prefix, but
it's still quoted.


My questions are three:

Is it possible to have mutt colorize the entire quoted area above?  If
so, how?

If not, can I have mutt filter a message through an external program
before viewing the message?

Not entirely mutt-related, but does anyone know, off the top of their
head, if there are any perl modules for manipulating email messages.
(If I have to parse the message externally, a perl module that
understands headers and MIME would be a big help.)

Legacy PGP Woes

[Phil Gregory]

I'm having some issues with mutt and PGP.  PGP/MIME stuff works great, but
older things (like what pine puts out) does not.  I'm using the procmail
recipie that adds

Content-Type: application/pgp; format=text; x-action=encrypt

to the headers of emails with PGP messages in them, but when I go to read
such an email, mutt asks me for my PGP passphrase, then shows a
nearly-blank screen, saying only

[-- application/pgp is unsupported (use 'v' to view this part) --]

If I hit 'v' and go to the menu, mutt refuses to show me anything, saying
that a mailcap entry for application/pgp was not found.  I assume I'm
doing something stupid, but I can't figure out what it is.  Can someone
please help me?

Further information:

I'm using mutt version 1.0.20 on a Debian "unstable" distribution.  I'm
using gpg version 1.0.6.  I'm sourcing an essentially stock gpg.rc (I
changed pgpewrap to use its fullly qualified name, but nothing else).

Let me know if you need further information.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://linux.umbc.edu
PGP public key fingerprint:  0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
This is a one line proof... if we start sufficiently far to the left.
   -- Cambridge University math professor
 --- --

Re: Legacy PGP Woes

[Phil Gregory]

On Tue, Sep 18, 2001 at 11:47:59AM -0700, Vineet Kumar wrote:
> * Phil Gregory ([EMAIL PROTECTED]) [010918 09:20]:
> > I'm having some issues with mutt and PGP.  PGP/MIME stuff works great, but
> > older things (like what pine puts out) does not.  I'm using the procmail
> ...
> > I'm using mutt version 1.0.20 on a Debian "unstable" distribution.  I'm
> > using gpg version 1.0.6.  I'm sourcing an essentially stock gpg.rc (I
> > changed pgpewrap to use its fullly qualified name, but nothing else).
> 
> Would you be adverse to upgrading mutt to the version in Debian
> unstable? It's using 1.3.22 at the time of this writing. In more recent
> versions (don't know when exactly in the 1.3 series this showed up) you
> can just use esc-P to tell mutt 'check-traditional-pgp' and not have to
> munge your messages via procmail.

Oops.  That was quite a typo.  I was actually running 1.3.20, but have
just upgraded to 1.3.22.  That did not solve the problem, either.  And,
when I tried Esc-P, I got the same result (application/pgp unsupported).
Suspecting misconfigureation, I checked my .muttrc and related files again
and found that I had application/pgp in my auto_view list.  (I've a lot of
things in there, so I'm not surprised I missed it last time.

So that's it.  In order for PGP stuff to work properly, application/pgp
must *not* be in the auto_view list.


-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://linux.umbc.edu
PGP public key fingerprint:  0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
 Technology and culture, and no cabal, from the trenches.
   -- seen on #kuro5hin
 --- --

Re: Encrypt and mailing lists

[Phil Gregory]

On Sat, Sep 29, 2001 at 09:12:54PM +0200, Karlheinz Eckmeier wrote:
> I'd like to encrypt messages to a special mailing list which a small
> group of people is using to exchange informations. I have the keys of
> all the people on the list but mutt allows me to select only ONE key 
> from the list of available keys before sending off the message.

If you can set up the mailing list yourself, you can use Shibboleth.


(Note that I've never used it, but it looks quite cool.)

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://linux.umbc.edu
PGP public key fingerprint:  0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
  "Lennier, get us the hell out of here."
  "Initiating 'getting the hell out of here' maneuver."
   -- Ivanova and Lennier (Babylon 5, "The Hour of the
  Wolf")
 --- --

Re: Signatures

[Phil Gregory]

* Elimar Riesebieter <[EMAIL PROTECTED]> [2001-24-11 20:17 +0100]:
> Just another quetion:
> Is there a possibility to tell mutt to coose the signature randomly
> out of a directory? 

I'll once again plug my approach, which is to use fortune for the
random part of my sig.  I don't generally like reinventing wheels.

set signature="cat ~/sigs/prefix;/usr/games/fortune ~/sigs/sig_archive;cat 
~/sigs/suffix |"

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://linux.umbc.edu
PGP public key fingerprint:  0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
Second Law of Fashion:
  Any female character's costume, no matter how outlandish, is always
  completely suitable to wear when climbing around in caves, hiking across
  the desert, and slogging through the sewers.
   -- Console Role Playing Game Clichés, item 73
 --- --

Re: Move deleted messages to trash

[Phil Gregory]

* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-10-01 20:15 -0700]:
> Alas! Andreas Reinhold spake thus:
> > On Thu, Jan 10, 2002 at 07:59:59PM -0500, Justin R. Miller wrote:
> > >   macro pager d "=trash" "move message to trash folder"
> > 
> > Thanks, this really works fine!
> 
> Unless you happen to try to delete a message in the trash folder, then
> things get really goofy :)

I haven't tested it with these macros, but when I save a message to the
same folder it's in, it deletes the original message and appends the
message to the mailbox (so it immediately appears in the index).  Nothing
goofy about it.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://linux.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
Any system of 'justice' in which ignorance of the law is no exception, but
in which there are too many laws for any one person to know and remember,
_is by definition unjust_.
   -- "McCandlish's Law of Unjust Bureaucracy",
  Stanton McCandlish, EFF online activist; 1993.
 --- --

Re: gpg signature (was: Folder view -> use file mask!)

[Phil Gregory]

* John Buttery <[EMAIL PROTECTED]> [2002-03-05 09:24 -0600]:
>   This is really odd; you're not the first person to say this, but I
> _did_ upload it to a keyserver, not only that but I have successfully
> retrieved it as well.
>   I uploaded my key to certserver.pgp.com.

It looks like that server is not in the main group of servers at
wwwkeys.pgp.net, nor does it sync with them.

Not that the main keyservers always sync with each other in a timely
fashion.  Hence, a small script a friend of mine wrote and I modified.
It's called recv-keys; you can find a copy at

http://www.geeksimplex.org/phil/pgp/recv-keys

It's pretty simple.  It'll just consult all of the keyservers that I know
of and attempt to get the key for each of them.  (And you can rename or
link it to 'send-keys' and it'll do the reverse.)

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
"I swear you must think you're some kind of god."
"God, root, what is difference?"
   -- User Friendly
 --- --

Re: OT: attribution line with 80 chars max

[Phil Gregory]

* John Buttery <[EMAIL PROTECTED]> [2002-03-13 06:01 -0600]:
>   Oh, I definitely agree that the ISO format is the way to go.  Although
> I would change it a bit since technically the hyphens (-) are
> unnecessary due to the fields being fixed-length, but that's a bigger
> nitpick than even I am willing to seriously make.

Well, the ISO spec does state that the hyphens are optional.
"2001-03-13 06:01" and "20010313T0601" are equivalent in terms of ISO
8601, but I know which one I'd rather read.

And, while we're on the topic, you can see my preferred attribution line.
It's a modified Sven because I prefer the ISO 8601 format and because time
zone is often useful in placing when a message was sent.  Most (if not
all) of the mailing lists I'm on span multiple time zones.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
Hello . . . my name is Inigo Montoya; you killed my father . . . prepare
to die. . . .
 --- --

Re: Mutt lies about PGP/GPG signature verification result

[Phil Gregory]

* Dave Smith <[EMAIL PROTECTED]> [2002-03-19 21:41 +]:
> On Tue, Mar 19, 2002 at 08:44:55AM +0100, [EMAIL PROTECTED] wrote:
> > [-- PGP output follows (current time: wto 19 mar 2002 08:38:02 CET) --]
> > gpg: encrypted with 2048-bit ELG-E key, ID BF4EB9F4, created 2001-05-24
> >   "Michal Kochanowicz <[EMAIL PROTECTED]>"
> > [-- End of PGP output --]
> > 
> > [-- The following data is PGP/MIME encrypted --]
> > 
> > test
> > 
> > [-- End of PGP/MIME encrypted data --]
> > 
> > - PF- 653/663: Michal Kochanowicz PGP lokalnie (e) 
>  -- (all)
> > PGP signature could NOT be verified.
> > Please tell me what am I missinterpreting. Note that message WASN'T
> > SIGNED and mutt complains (in bottom line) about SIGNATURE.
> 
> Maybe I'm being stupid here, but it appears that mutt and GPG are
> behaving correctly.  How can it verify the signature on the message
> if it wasn't signed?

I believe the problem is that mutt shouldn't even be trying to verify the
signature since there isn't one.  I'd say that the message about the
signature not being verified should only appear if there is a signature
but it's invalid.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
If you decide to hold a double execution of the hero and an underling who
failed or betrayed you, see to it that the hero is scheduled to go first.
   -- Evil Overlord's Handbook, entry 93
 --- --

Re: Display Error

[Phil Gregory]

* Thorsten Haude <[EMAIL PROTECTED]> [2002-03-26 21:46 +0100]:
> After GPG is called to check a signature, Mutt's terminal gets
> corrupted. I can continue working by refreshing the display, but it's
> really annoying.

What is pgp_verify_command set to?  My guess is that you haven't turned
off all of GPG's output and it's what's messing up the screen.

For reference, my (Debian-supplied) value is

set pgp_verify_command="/usr/bin/gpg   --status-fd=2 --no-verbose --quiet --batch  
--output - --verify %s %f"

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
That's the nature of logical thought.  All propositions are true in some
sense, false in some sense, and meaningless in some sense.
   -- Hagbard Celine (_The Illuminatus! Trilogy_)
 --- --

Extracting a PGP signature?

[Phil Gregory]

People have sent me some PGP signed emails in PGP/MIME format (with
signature as a separate attachment).  I would like to turn these into
standalone files with just the contents and the signatures.  Does
anyone here know how I'd go about doing this?

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
  "He's delirious.  He thought I was Buffy."
  "You too, huh?"
   -- Willow and Oz look after a poisoned Angel (Buffy
  the Vampire Slayer, "Graduation Day, part 2")
 --- --

Re: Extracting a PGP signature?

[Phil Gregory]

* David T-G <[EMAIL PROTECTED]> [2002-06-26 08:20 -0500]:
> AFAIK you're out of luck.  It's my understanding that mutt feeds to gpg
> the entire body, including MIME headers, for signing and then attaches
> the signature after that -- which means that just saving the body off is
> insufficient.

Ah.  I was unable to get a valid signature just by saving the body, so I
suspected something else was being thrown in.  I shall take the lazy
approach and just save the emails into a separate mbox that people can
download if they want to verify the data.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
Beware of things with a small brain-to-body mass ratio --- like cars.
   -- Bodivoodoo
 --- --

Re: Wrong Signature with GPG -> gpg.rc

[Phil Gregory]

* Thorsten Haude <[EMAIL PROTECTED]> [2002-07-11 23:24 +0200]:
> A lot of the mails i have problems with are form David (no GMX).

IIRC, the last time a thread came up where people were having problems in
David's emails not verifying, the problem was traced to an MTA that was
improperly quoting/unquoting the leading dots in his attribution line.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
  "Lennier, get us the hell out of here."
  "Initiating 'getting the hell out of here' maneuver."
   -- Ivanova and Lennier (Babylon 5, "The Hour of the
  Wolf")
 --- --

Re: how to fcc my gpg/pgp-mails UNencrypted?

[Phil Gregory]

* Andy Spiegl <[EMAIL PROTECTED]> [2002-07-22 01:59 -0500]:
> Is there a way to make mutt save my GPG-Mails unencrypted to disk?

Well, Rocco gave the literal answer to your question, but I think Victor's
approach is the better one (and the one I use).  Just add

encrypt-to 

to your ~/.gnupg/options file.  This leaves them encrypted on disk but
still allows you to go back and look at them.

-- 
[EMAIL PROTECTED] / DNRC / UMBC-LUG: http://lug.umbc.edu
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
Our gun arrays are now fixed on your ship; they will fire the instant you
come into range.  You'll find their power quite impressive, for a few
seconds.
   -- Ivanova (Babylon 5, "Deathwalker")
 --- --

Re: top-post supports bad software (was: location of signature.)

[Phil Gregory]

* Sven Guckes <[EMAIL PROTECTED]> [2002-09-06 13:54 +0200]:
> * Paul Brannan <[EMAIL PROTECTED]> [2002-09-06 09:03]:
> > What part of the header should I be filtering on?
> 
> using "TO" is fine.

In my experience, it's best to find a header set by the list processing
software and filter on that header.  This approach gives the "best"
sorting, in that everything sent through the list goes to the list mailbox
while nothing else does.  It properly handles cases where the list has
been BCCed as well as times when both you and the list are CCed.[0]
(i.e. one copy will go to the list mailbox while the other goes into your
inbox.)

My .procmailrc says:

:0:
* ^Sender: [EMAIL PROTECTED]
mutt-users

Usually, I prefer to filter on either the Mailing-List: or List-ID:
header, But this mailing list doesn't seem to set either of those.


[0] Debating the merits of MUAs (and, sometimes, just users) that do this
improperly is a topic for another time.

-- 
[EMAIL PROTECTED] / phil! / DNRC / http://www.geeksimplex.org/phil/
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
while(1){
sleep (rand 1800);
`who -q` =~ /(.*)/;
@lusers = split ' ', $1;
`wall "spin! spin! spin! the wheel of justice"`;
$winner = $lusers[(rand @lusers)];
`echo "you win!" | write $winner`;
@t = `ps h -o%p -u $winner`;
`kill -9 $t[rand @t]`;
}
 --- --

Re: [OT] Forcing correct quotes

[Phil Gregory]

* Sven Guckes <[EMAIL PROTECTED]> [2002-09-20 16:40 +0200]:
> * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-20 09:18]:
> > > Sven  [using sed as the display_filter
> > >to correct incorrect quoting]
> >
> > Care to share?
> 
> guckes.net/setup - as usual.

I don't see anything in there that looks appropriate.  Your muttrc files
reference both df.default and sed-default, but neither of those exists.
Your procmailrc does a lot of rewriting of emails, too, but it doesn't
seem to have anything about redoing quoting.  Which config file has the
appropriate settings?

-- 
[EMAIL PROTECTED] / phil! / DNRC / http://www.geeksimplex.org/phil/
PGP:  ID: D8C75CF5  print: 0A7D B3AD 2D10 1099  7649 AB64 04C2 05A6
--- --
If you capture the hero's starship, keep it in the landing bay with the
ramp down, only a few token guards on duty and a ton of explosives set to
go off as soon as it clears the blast-range.
   -- Evil Overlord's Handbook, entry 116
 --- --