-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Daniel,
>> Enigmail dose not read the gpg.conf file > Is there a reason for that? Yes! If we read it, we would have to write back to it, too. And we do not want to fiddle with a user's GnuPG config. > Wouldn't it make sense for Enigmail to read such settings? So users don't > have to configure it in gpg.conf AND enigmail preferences? Only "experts" will know at all what gpg.conf is. These experts will know how to handle things. For the average/typical "user", this doesn't make sense. And we don't have the ressources to maintain such "expert" code. There already is a lot of it ... > Bytheway, do you prefer future bugreports (okay, this one wasn't a > bugreport as it turns out...) on this list or on sourceforge? Ideally, you would check using list/forum first to make sure it IS a bug and to provide all necessary information when reporting it, and then report it. Well, we still may have some nice dreams, ey? Olav - -- The Enigmail Project - OpenPGP Email Security For Mozilla Applications -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/ iQGcBAEBCAAGBQJVGpnIAAoJEKGX32tq4e9WqqYMAJWKuPhfWdtjURRd73Hq40JB MlspGxh8WAIco6Fl7QO30BujZ0pR190Rxy7ifN2L3KKpYVbYd+CYMIWPK86v6OPb arLdRb+pf4V/9S/Y6e2lwy8n+IyO7pNjK+FCIz1A08zAZyiWJpS0WmuRlX7S/2KT S8VctMpTdjqx+h1zQ7HwV81OBh92tT5Izdrg0wtV8hoXVGcJKVH28IUMG151dAEw GKGrFGZddZipyXILG2drSz7+0uA7zb8Jc/RMKdBsucdhW49UY40ZfI7Th314c2L8 JiauDdeamxKERFF0CXcoGEIYZ36JyR/pMZb1Ok4JmogX6b0cJtX1ffdmx+SEzED1 8eCQoglUa/MHiwt35qrXYjOQAu8B0VEo+bzffmgkjpgfG/Frz+b4U/PzubxiUR0A YRRYZgOK207+oQjxnyhT649f5Hxew+48Ru9OX8T5X4+1tGXwO5LRuyJjvGNVa/sm JrEvaa7KqbXJFvNFdhkZc46MKRVNKRMYA0d6Mww9eg== =Gll6 -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
