From owner-ctm-users@freebsd.org  Fri Sep 11 14:05:48 2015
Return-Path: <owner-ctm-users@freebsd.org>
Delivered-To: ctm-users@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E92299CC14F
 for <ctm-users@mailman.ysv.freebsd.org>; Fri, 11 Sep 2015 14:05:48 +0000 (UTC)
 (envelope-from jhs@berklix.com)
Received: from slim.berklix.org (slim.berklix.org [94.185.90.68])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5D7B41C42
 for <ctm-users@freebsd.org>; Fri, 11 Sep 2015 14:05:46 +0000 (UTC)
 (envelope-from jhs@berklix.com)
Received: from mart.js.berklix.net (pD9FE953E.dip0.t-ipconnect.de
 [217.254.149.62]) (authenticated bits=128)
 by slim.berklix.org (8.14.5/8.14.5) with ESMTP id t8BE59Yn016573;
 Fri, 11 Sep 2015 16:05:09 +0200 (CEST)
 (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41])
 by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id t8BE5fGA043580;
 Fri, 11 Sep 2015 16:05:41 +0200 (CEST)
 (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (localhost [127.0.0.1])
 by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id t8BE5BxE008774;
 Fri, 11 Sep 2015 16:05:29 +0200 (CEST)
 (envelope-from jhs@berklix.com)
Message-Id: <201509111405.t8BE5BxE008774@fire.js.berklix.net>
To: Peter Wemm <peter@wemm.org>
cc: ctm-users@freebsd.org, jvarner@gmail.com
Subject: Re: Future of CTM
From: "Julian H. Stacey" <jhs@berklix.com>
Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany
User-agent: EXMH on FreeBSD http://berklix.com/free/
X-URL: http://www.berklix.com
In-reply-to: Your message "Mon, 31 Aug 2015 19:19:28 -0700."
 <2133149.u1BgRHIO00@overcee.wemm.org>
Date: Fri, 11 Sep 2015 16:05:11 +0200
X-BeenThere: ctm-users@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: CTM User discussions <ctm-users.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/ctm-users>,
 <mailto:ctm-users-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/ctm-users/>
List-Post: <mailto:ctm-users@freebsd.org>
List-Help: <mailto:ctm-users-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/ctm-users>,
 <mailto:ctm-users-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2015 14:05:49 -0000

> From:		Peter Wemm <peter@wemm.org>
> Date:		Mon, 31 Aug 2015 19:19:28 -0700

> I have been trying to find an example of somebody who is actually verifying 
> signatures before piping the messages to to ctm_rmail.  Even the procmailrc 
> files that you publish at http://www.berklix.com/jhs/txt/ctms.html don't do 
> signature checking.   From your own pages:
> # JJLATER add a check for pgp signature, ref.

Thanks to the procmail sample from jvarner, I now apply GPG to all
my incoming CTM streams.  Later I may move gpg verify from procmail
to shells, per new comments marked JJLATER in:

http://www.berklix.org/~jhs/dots/.procmailrc.lists
http://www.berklix.org/~jhs/src/bsd/jhs/bin/local/mail/ctm-freebsd-svn-incoming

Julian
--
Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com
 Reply after previous text, like a play - Not before, which looses context.
 Indent previous text with "> "         Insert new lines before 80 chars.
 Send plain text, Not quoted-printable, Not HTML, Not ms.doc, Not base64.