From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Apr 3 11:11:53 2015 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B8EE6DD for ; Fri, 3 Apr 2015 11:11:53 +0000 (UTC) Received: from smtp.fdlnet.cz (smtp.fdlnet.cz [IPv6:2a03:1180:0:ffff::25]) by mx1.freebsd.org (Postfix) with ESMTP id C7BCA9C3 for ; Fri, 3 Apr 2015 11:11:52 +0000 (UTC) Received: from kepler.businesshub.cz (unknown [10.1.252.193]) by smtp.fdlnet.cz (Postfix) with ESMTP id 3590999774 for ; Fri, 3 Apr 2015 13:11:50 +0200 (CEST) Message-ID: <551E7576.3030907@email.cz> Date: Fri, 03 Apr 2015 13:11:50 +0200 From: Petr Hejl User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-ports-bugs@freebsd.org Subject: Thunderbird upgrade - Enigmail breaks encryption / signing completely Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 11:11:53 -0000 Hello, sorry if this has already been discussed, I only registered to this mailing list now. After the last Thunderbird upgrade it is no longer possible to encrypt / sign messages with Enigmail enabled. Enigmail doesn't even ask for a password and fails with "encryption command failed" (even though I didn't want to encrypt anything, just sign). To make things even more weird, it is also no longer possible to use Thunderbird native security functions (using trusted CA signed S/MIME keys) as long as Enigmail is enabled. I have to disable Enigmail entirely in order to be able to sign my messages this way. After searching the web I learned that other people are also affected by this issue but found no solution. Should I submit an official bug report? Thanks Petr