From owner-freebsd-gnome@FreeBSD.ORG Sun Mar 27 19:00:50 2005 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B93516A4CE; Sun, 27 Mar 2005 19:00:50 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6606943D41; Sun, 27 Mar 2005 19:00:49 +0000 (GMT) (envelope-from dougb@freebsd.org) Received: from [192.168.0.3] (c-24-130-110-32.hsd1.ca.comcast.net[24.130.110.32]) by comcast.net (sccrmhc13) with ESMTP id <20050327190047016002lq32e>; Sun, 27 Mar 2005 19:00:48 +0000 Message-ID: <424702DE.5080205@FreeBSD.org> Date: Sun, 27 Mar 2005 11:00:46 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jose M Rodriguez References: <20050326181940.W65159@qbhto.arg> <42461C19.3080103@ahze.net> <200503271017.36162.freebsd@redesjm.local> In-Reply-To: <200503271017.36162.freebsd@redesjm.local> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: gnome@freebsd.org cc: freebsd-ports@freebsd.org cc: ale@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: enigmail-thunderbird doesn't work with latest thunderbird X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 19:00:50 -0000 Jose M Rodriguez wrote: > You can't use enigmail with thunderbird right now. Jose, I'm not sure what your motivations are with these posts, but you are quite simply 100% wrong here. As I posted last night, it works fine if you follow the instructions in the pkg-message file that prints after 'make install'. > If you're trying this, you must tweak the enigmail build system to get a > new extension compatible .xpi (I think this target is allready defined > and documented). I agree that this would be a nice goal, where are your patches to implement it? -- This .signature sanitized for your protection