-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rocco, et al --
...and then Rocco Rutte said... % % Hi, Hello! % % * David T-G [04/22/02 18:44:05 CEST] wrote: % > Rocck -- % % Creative, I must say. ;-) Whoops. That is clue number one ... % % > ...and then Rocco Rutte said... % % > % This only happens if a mail was former "text/plain" and is now % > % "application/pgp; ...". To find if this - in my case - is the % > % reason, I'll remove those rules and see what happens. % % > Here's a test message back to you, then. Let's see if mutt says it's % > verified. % % Of course it's verified. You have 'multipart/signed' which is % a signal for procmail to not touch the mail. ... and here's clue number two. Must have been way too early for me. Sorry! So *now* what do you get? TIA^^2 & HAND :-D - -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8xHQHGb7uCXufRwARArxkAJ0do0jvBDm3WzfRdRSBctoNScMZLQCeODzS QMT5NGUzvn3EMzudUKC2ieI= =1SF+ -----END PGP SIGNATURE-----
