Bug 163781

Enigmail launches gpg-agent via "wrappers/gpg-agent-wrapper.sh" script, and this script is expected to be beneath user's profile directory. But our port installs enigmail into /usr/local/lib/xpi/ which ends up with the error when enigmail cannot launch gpg-agent.

Fix: Enigmail was changed not to look into user profile directory only, it's going to be released with the next version ( > 1.3.4 ):
http://www.mozdev.org/source/browse/enigmail/src/package/enigmail.js?rev=1.311

Enigmail looks for its directory by its extension ID, the latter one is changed by our port from "{847b3a00-7ab1-11d4-8f02-006008948af5}" to "${GECKO}@mozilla-enigmail.org", but such change is done only in install.rdf file while other constants in enigmail's code still refer to original ID.

So, the question is just ID changing in all other files. Patch example is attached.

Patch attached with submission follows:
How-To-Repeat: 1. Make sure you have enigmail installed not into your thunderbird profile directly, probably file system needs additional manual checking to make sure there are no any non-deleted old files in your profile.
2. Check that gpg-agent is not running or stop it.
3. Run thunderbird and try to use enigmail, e.g. "Main menu > OpenPGP > Key Management". As a result you should get similar error message:
  "Could not start the gpg-agent program which is needed for your GnuPG version 2.0.18."

As long as it's not related to particular MUA, the same steps seem to be correct for enigmail-seamonkey and enigmail-thunderbird3.