Re: [Enigmail] What about PGP/Header support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 03/15/2014 10:10 AM, Patrick Brunschwig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15.03.14 16:41, Egbert van der Wal wrote: I recently set up my mailserver to use DKIM signing and I think the solution for embedding the DKIM signature is really elegant: adding a DKIM-Signature header. Since mail clients that do not understand this header just ignore it, it is basically invisible to people inexperienced with mail and/or DKIM. It is still embedded in the message. I then started looking for any possibilities to use this and came across someone who wrote about this same idea: http://beza1e1.tuxen.de/articles/pgp_header.html It is important to be clear about the nature of the problem so as to address it properly. The problem is part social and part technical. First, as to the social, I have been signing my emails for many years now, and I find some people are disturbed when they can't do anything with the attachment. I explain, sometimes they don't understand, but the important thing for them is to just ignore the attachment, and eventually they get that. Life goes on. Next is the technical. This divides into two problems. First is that the current methods of signing have been in use for quite a long period of time. Enigmail is far from the only piece of software involved. Compatibility is an issue. But I believe this is what the RFC process is for. The other issue is the question of what to sign/encrypt. I'm not seeing this as a problem. Just sign/encrypt the entire body, including attachments and leave it to the sender, as we already have been doing for years, to make obvious which bits are from previous messages. This does seem to me to be 'clean' and 'elegant'. It also seems to me that it would address another problem previously reported on this list in which a signed attachment could lead a receiver to believe that the entire message had been signed. It's important to remember here what a signature is supposed to mean: strictly that I sent this. It means nothing more. And it strikes me that the practice of encrypting pieces of a message and leaving other pieces unencrypted is dubious, that leaving portions unencrypted might offer clues as to the encrypted content. - -- David Benfell see https://parts-unknown.org/node/2 if you don't understand the attachment -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJTJLpxAAoJEBV64x4SNmArnN4P/iUxhalEbYElYO9S2nAV/kQ7 9Hd5PjM0cA2zOccGh5kWF69ftO44A0UMT2wAprLrOgfKFkXZLIKhb591lGjgpqAf vVeEQUshIHp4kioJBq+VMxh6tDDP8ZDttJQF5a7rHrPV7F7gGnc6IztcbA6bwmGo 5tdRAWH3Xc72R/6kfRWEHAoyaNH2BRdrVZx+T/MsGTdIk/dul020pzjHe7Uk7LUd QtpFrGBCtHfN9xM+RvkmVky1e+5UNj7yR/XATeqzKYoVAbj5zoDdIScR25YnewfM TDE6Qe1oGcQFKitNhmji7eq/CbwVT5kG0rfW25PLRLS7CH0nM7Y/bqK+w6Uxnn0Q 3dF2WqztrRa0ugFnF5ZY2b2SKXcSJCAN3dcHSc1HTpC7HI2L+zo7AKOceOMHQU3X SU+uucEUhJ1p+mUu5lxoBLsTNWe+iNcBhd0ydk8mfc0Zt6HSRRamCVYLJlsoksG2 rEBChvYQ8zPM0N+ZgDwC8MzCD1HJVCPy8b5vuT12MdOPUng3E8A8RphKSapPrQHI sgJbBLY3lMsVzbtKoPy6ksmF8YyIHci5uKu+cjOH60ygX1LpZupsU2Ft8vrxnVtF xWF/XtBy7qkuK62ZesYdvYVskNnSHbeziqQGE4tVdOWCcWshiLksd/q4RR4Fs6fw PA5YXrl8Yu33GBuVA8p7 =I6/e -END PGP SIGNATURE- attachment: benfell.vcf___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] Integration with Namecoin identities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-02-19 23:12, Robert J. Hansen wrote: It's not necessary that it become official. After all, the HKP keyserver protocol isn't documented in RFC4880. It's just necessary that it become a de-facto standard way of querying for keys. If/when it becomes a de-facto standard, GnuPG will quickly add support for it as a keyserver protocol, and Enigmail will follow suit. I'm not a developer either. That said, when I look at namecoin, I see a mess that is a long ways from widespread support. The bitcoin protocol (upon which namecoin is based) apparently has problems, which I *don't think* impact namecoin, but suggest that bitcoin itself needs to mature a bit (which has implications for all of its derivatives). All that said, I'm a bit confused by this. GnuPG *does* support the HKP protocol with the keyserver option. -BEGIN PGP SIGNATURE- Version: OpenPGP.js v.1.20131017 Comment: http://openpgpjs.org wsFcBAEBCAAQBQJTBa//CRAVeuMeEjZgKwAA888P/jE5vYBfBURV4FwvUSnI jVZrSCtHnzg0uVxTfzb6wHWcFuMwEPHAWFOenPozxmIO7qrDviPoBTREShpa 5f7H8x6u5d0JYNxX0omVYthTcsijZmUx+e7xy5Kg7hV4XCZPNCx21lMzq17u qGMXH4njNxjzBNJleeXNz4Wn7q+dAuNOI5Pm+GDySIbCSV3OhcWNZZu9l4SC 1BKYfxGf0mZRVv9VhyLNeMzYes5btRgAtnm5rviTn/5MfJ2+chVKomMxe6BP R9MakW1i4Re4XUzBxDPxbZpDbyQjqCLSR3MiNEt5P+Q2mf88iX9WYGUk2pKh APdLItjXXvR+Ha0yGjH26lHa1RDzOdRopF+IQCdATT4rNrHthtYup1qRjVTo /znVTqbpWnAanGWSw0oRRVAqfseQA3enfpPIiVCVIBIIUweMmHsZNyt9Bewd aGGL0keWnrkThqvuTB0CQAJPhBk6CqTaFfn8Z4sj+4iM+QoeCkBoUnwPuYc+ koQABsDP9gRKg1CPb9rqzcVI2A9Vr3bCjew/MkM1/jiRgtAYtJJTQKZGJZ/e hmGoYPZ4q0ynOKE3hDvm89hlUSk5e5qZRGsh/yyMuAP90TipzdjEg0ZWPQYy hUjC0AQlgbpdUxAHVDQWziNDVJifrhm8JPVwMqLVGbQjMB29qfhAlBUe6Pic LFQ6 =sRQQ -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] enigmail picks invalid key ID
On Mon, 2013-11-11 at 14:32 -0500, Daniel Kahn Gillmor wrote:
One way to work around this is to remove the old key from your gpg
keyring entirely.
There is also a configuration option in gpg.conf to select a default
key. I believe the parameters that should be set are:
default-key ${new-key-id}
encrypt-to ${new-key-id}
--
David Benfell benf...@parts-unknown.org
If an attachment to this email baffles you, please see
https://parts-unknown.org/node/2
signature.asc
Description: This is a digitally signed message part
___
enigmail-users mailing list
enigmail-users@enigmail.net
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] (no subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/19/2013 11:10 AM, Anthony Papillion wrote: In order to use encryption, BOTH sides must be using it or it doesn't work. Right. In order to encrypt a message to someone, you must have their public key and in order for them to decrypt it, they must have the corresponding private key. - -- David Benfell / benf...@parts-unknown.org Please see https://parts-unknown.org/node/2 for GnuPG information (or the attachment you don't understand) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR6fPVAAoJELJhbl/uPb4S4ZYP/RSYpChIBt4MA74xnYam+DTb SXhKU9+z6PijakfsB5684ZCOutd0nLb4/k+uRyTf6CCoMUiAwx+hFx21Uk7FKzUR lK2N169UgZfO/A7C7OBilU1WA3CCsXqlLpoYJgBnTkehzgrUJuq3hLn/TjQLD+z7 Vm9NlB52tzBA9sCUMzSSGIvEAEziQjCyLGjfMh+5rq992xKL5kW24CSGbW4s8w2n aLge1bESw7iDG4uzoOeOvpFVs9Le2P0s1ET2bgOKHLX7U0v5HblMGUoQyyADl7C4 bMnD1BV8gZxvImF5vlJ+XMLHGIX2rs9oIDUE1mbdfUJta3zKKCPyC1yv1U3+ZwiR CZS0Mx6UpR6gHolpxD3unCx6XSS91HwIVgE7byK3/BJVQC0vF0XOflN4W5fT1/Rn xKmNteUbCb8+pcklesPBuyU4OCDTA75Vl+jXp5ozgiU1oUezoJcBS5NfFQPp5UI/ 2BUJvUf0XzhCouHZCVE0Mg1A1Vhg1sf8yCk+0iGnRyD2nftDeSkdnd0qyBNfaMcR E+dq8v+eMwzfCJ+jz6A6CFHRD4uyS+re+BSWlCo9BlDxBp6JRDWoAvsXLYzklSVF 3czyzaA467ZWN0p9z3UTozzxiJdjPw7HVEvSy5uZRXS5QBVTDcX5Lc+jO6DQfNm7 bfkkvR2pmyFEmcagmnHs =4lpA -END PGP SIGNATURE- attachment: benfell.vcf___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] APPARENTLY SOLVED: Re: signing problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2013 09:39 AM, David Benfell wrote: A test email appears to have been signed correctly. So now the email to the list was signed incorrectly. If this is just a front-end for gnupg, did someone perhaps take a wrong turn writing this plugin? Why is it this fussy? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRM45AAAoJELJhbl/uPb4SC6MP/0RFhgy4ZoC32a8AYXJ16yGQ eaZY7S3Q0NJhYaU4c1XAIpGgRqTqquzd7TjA7YXdL50ij1tOEb1hlt3qy8y0Z/gg h6lBP/1HAlLr3b/pZGxjReGwYhbFaMLWeHM9Sb3czcPcKR0oc5u2/Wb9osQ6ILUz vB7eNhUyyCmNHHROHphTOyk7Fyuq/KerkgloDZ9VFXCHeUtUJDQaBG/8jv9dEAu6 pNoUEa0Djlx0N+uCVRlfaZg4lH5GJjQhmYqD5iBpE6sOxNJh04/Bo+cAr9qa2sfI PoSc5sfjJYZbO+PNF4qrR9SWx5zrQr5U0jWctnnf8jYC/yc2NXYjxZwXBJZ8GrMu zFlj56RSJNJfxtBS3HUhxBS7E/76MylfM4Nm9R0xtV9lKJ3Ok0TuWaFJYSMJqq2h r6qiHuX7qAfFoUycCTHBPAyiswOFXZ0evGGb/0ujbHbusco5DgWo4c9nuqfdEr8p N+x3gv2bYQeRksK68Xry58QUzb2e/iuUDf6UmLRJqFDzCoKupS5rHxfiW9nM5HF9 OYkQOU0Ivm2fcYXV8LnKEZSAQtb4U+ypQrIOv/RwRrgcFRfasPHY/QVc8iBlwrSK 5RaAP3IwZMBxND/VVob6bzDIcC/4k0F0V2s6b47wgX5s/fvaBsMysMMaMp/epRc5 Lc2S8euz4fmgpWJ96GQt =wlmQ -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] APPARENTLY SOLVED: Re: signing problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2013 12:51 PM, Grant Olson wrote: No, you're right. Enigmail defaults to inline PGP. You can use PGP/Mime if you want your signatures sent as MIME attachments. Inline PGP is just text so it's compatible with all mailers. PGP/Mime isn't as ugly for non-pgp enabled browsers, and signs and encrypts attachments, which Inline PGP does not. (Mentioning the pros and cons of each of course means we'll have another six hundred email thread about which format is better...) Thanks, Grant. I'll leave it be for now. But my apologies if I provoke a flame war. I'm new here and that was definitely not my intention. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRNAU2AAoJELJhbl/uPb4SAV8QAL2igKCQ0pwcripzYoYAjiFZ n6FxxHOVSk1veTBDbGXLgpL1pcb+U/fBin2A9obtE2/ADE6AVjb4vxfsw3LFMB5q D3tUvldL+tJiLXtK5pCY3QlkgUYOl1P+pYcvp7SFbSTd6HbmqqZllj9WhjV8CkX7 j46rjI0lQK23/2DNcMGXuZlGM5RNvSgrHg+pO/LdNVQvLu6V7epk9YLTKstjoHUJ z4ivY0hiK6wNv1HwHRTK5pygfVKkY3qofUMEcMh06255f0rIQ1LeILSdNwa4I+OF uPUgUxVocwjxyYkJJ3p8dlUnL6XHbMxM/rXXacVRi/8TixzThogXnNhg47gtYTug 3mgqpaNMbnoMeBT97TpUNAnlTUVtxZUWg9MppUpGXCXlqqhfKNYPWD110RK+OJvo k1ScopTJBdpMlED66HgWSdZs7al9SLErVVSsdSYtaoHnTxNCJmrt3m8Q/mmsF5K9 16BBRQEMX7V6j/TCUFqFMPHoXDJG4H60reu6N8Q/CoCabjOHIWB4Vy4yTh0ev0w+ rpR+d28A/RM/SGavipnrDhGgvdxtvQxV+qmbDTmQdxTEAzKPAxeOT6ZPdpqdQwi3 BMKS5jsGcFE2j+f62XiIyt3pzq9FCYBVllsJ9508QJ7dHDjQLHLGW60PeOCMCnvr FlBEmDu5E6kQnKn3Aawf =FdUF -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
[Enigmail] signing problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I am running thunderbird with enigmail in three instances: 1) Linux Mint Debian Edition (gpg1 backend) 2) Windows 7 (gpg2 backend) 3) Arch (gpg2 backend) I am using the same key on all three instances. The first two of these seem to work fine. But when I sign an email on the third, enigmail complains that it cannot verify the signature. I'm sure that's not enough information. What more information should I obtain and how do I obtain it? Thanks! - -- David Benfell benf...@parts-unknown.org dbenf...@saybrook.edu See https://parts-unknown.org/node/2 for GnuPG (the attachment you don't understand) information. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRMpg4AAoJELJhbl/uPb4SJtoP/06YCElHpd9WWVk8z7oBmeZK TYC1WoRlENRDCV1arT+ze7fDJMJTkvmhcYum5LRk/DycEcs7cDf8nB2ccCRDQgIk gppbx8vqEE9l3hg4F46rkKWRQ4ncNY4gL9I5UuNAgjpC7Uxv5dnXZFEOOblW/A3s 3jrZyocoeUxX87rqiR0dS7BZeBFUVOHh29Frq+xGfsOtVUG/ZX/HvlzHpoxAWfVp WwhqS+O285lf9ArK2Kk5GYgrFqszRzXJ0OkohGa2Rt8nEprz8HpjiliFv01+uBPh aVZLfUDc9z06cJ3q7rIBUTBldOiI4C50kdoExXw3JEpxe0v/dJmxSwT6V9lczqMN 3YRbH5BQis3qjG91Pnzk5s9tzyeQsWb9CtqnhR3ocSK0b+NEpf4cV1D84Sb9GXYA JlLfsVGe+ZSMxRgh9ou8hg+VPmZoZHDA93X3e0sjoz8gc4uUF81bmy9vh/OEz4kX +wKBbHiGP19sVQ8NR6gEcUe9QI1baRMOOHojBHL+U/+bYrfidKkxx0N/58ZvgW6L rJnkl2yY1e/AA+9KLYvzrdGEG7F9vThOn75sBSKjIBlrXRidbn6t2Hy1gO5SILbl aOSGxR0YWGRX3V/vvuH0KQEy3GujPJ2bvy161I8Sm5UUkbjq3tG0m+AY4XvmzS0P CfORdqrv8Lz8jcjHyvy1 =f1Zn -END PGP SIGNATURE- attachment: benfell.vcf___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] signing problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/2013 04:43 PM, Doug Barton wrote: On 03/02/2013 08:37 AM, David Benfell wrote: | To demonstrate the problem, here is a message from the afflicted | instance--actually on the same hardware (it is dual-boot). Looks like a whitespace problem. Are you by any chance mixing and matching thunderbird and enigmail from your distro's packages and the mozilla sites? If so, don't do that. :) Make sure that you have all of one, or all of the other. Yup. I didn't know any better. I will clean this up presently. Thanks! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRMqg1AAoJELJhbl/uPb4SXCEP/R5Gz0cB9EHPLNZWK3C96qZ9 N/jBxbH5z1bhPJ1qCb9UiV/mEbI7hfx8mYbcoqmNJzyYgzCHa1bgLM7m7HVMNrIG khO41r+LUrFaodaHVZV1pPY99rCcEj0TtISqLBW7DupgUontfv3ZSWrtsc4aMXYG 59AlSnbWGdX+I55n9mWySABNfhEeDrMoNB3fyqEtplC9yXblp9wtwCh8fvmGUhan nElYbKYEZVN/fmJhwAV5Tb60mcbcZHsogdocfkQWmbc7AEaMMjU1Yvxw8BZZVTva Q0ydWYz3OYcW9rsT+I0TAoxduZhMflZMGbiEQt6GWe1dYOAAJEOUSWMAIidqCGIK 1sgh1vbMzUIzaSYYYQ1OgS0YVF5+swlGmf9Q49dxFJdJmnc0jAelYoTXWSjnkO6f J//NrMt3USjd1Mnylp6XgnJEpWzfkgvAXNeMFQsjK3HdjycHW5vKRxnr6U9X9P1u SyO+ssNWv8vbx0b3IN4C2h1mpYL/IX5Atop+3K9Vs2vnU4VgH/m0p2GkNXiKFFfM mRufINQG3fCtkVtXj1VO8xTEqdBc2fLjPRe5Hk04mnvhZfsXYvbeCdutW7SHnZ3d 5yd2aPbLwgW7EmXvLc7HO39fW8FsuuUvkbU7m2vHIA7wGklpxf9E8Ot/ihjPu1AZ P+/qr9uWDi9iYmGMW9lI =Ls8y -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] signing problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/2013 04:43 PM, Doug Barton wrote: Are you by any chance mixing and matching thunderbird and enigmail from your distro's packages and the mozilla sites? If so, don't do that. :) Make sure that you have all of one, or all of the other. The situation on Arch is *not* *nice*. enigmail is a community-supported package. The most popular Arch User Repository package for enigmail seeks and now fails to download the source for Thunderbird 16.0.1. Presumably it means to rebuild it to eliminate any possibility of this problem. I went with the second most popular package. We'll see if it worked -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRMqpjAAoJELJhbl/uPb4S6v8QAIDKWrVqZMvOUgTPNfvUmjQD pCuH2aBE/B25p+G5XvjC0wJ51Dns5TMTbtJwj1nV7Q1hqoYDc9jP7oLuDSxIDe0H xWX9ZyJ4i2IGxanKcUAzghbcRBMJM7zfvUUU834bM9BIIeSB89G/JkMpoHrwFqNb 25wxji2vsGgDhpvTS8vlKjs9b2z+Cdy4M4bnFsppQfRIB+uzfX1MWW7GcAE3LCZh d3BYh5Z5kzC9DfRn3RI5sLUIOLauri3oaQ7W//O3SpZ4rQLFtseWKQSISjuFX+OY OzHiRqVuYOYm1fcYUBMeqeOP7cfUmt5bLOmMt94nwpF0x3HI+dlvB7AQCSF2v9NU h4MRdtxmFhyjF2bl2UxzQuNfuAhCETxw9wNQTsqbFWTqLaUT2KEDNK452u09zDz3 5ZE0AsGOR7i2rQLPLOwTUbAWq+pGrknG1FlDHP9UnsEJ7OhqURaknB31gT69Wruc HQ4hGRAUOCuSt9R1a82X6ivCTorVYwQJyXOluY+kHK2Rqx3RDN5Fzs5Q0zt1w22f pIAY/elwKjEX5ZOvOPOY/99ay/V4PT6yn7ouJsSMP69q1xc8W/XYkXnvrq6Qwqva mnPso+mQZfV1wNgovESrJHkwg0gZaHpkPaovleF6m7sgmLLIQIDqsHZDLjtrBZip k5nt2AWpUBQJL64pUDPY =0tyA -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] signing problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/2013 05:41 PM, David Benfell wrote: The situation on Arch is *not* *nice*. enigmail is a community-supported package. The most popular Arch User Repository package for enigmail seeks and now fails to download the source for Thunderbird 16.0.1. Presumably it means to rebuild it to eliminate any possibility of this problem. I went with the second most popular package. We'll see if it worked That of course landed me right back where I was. I don't think I'm going to be able to fix this. Thunderbird downloaded from mozilla's site blows up with some weird XPCOMGlueLoad error which seems to point to dependency hell (circular dependencies, shades of very bad old RPM days) within AUR for xcb packages. Thanks anyway! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRMrEcAAoJELJhbl/uPb4SIw8QAIlHi6h8i67x/bxm5oA0cz57 1ksX9bePi0o6CJIsMydkn7mJtmVhWcbqJtz6cd6YQ3sMLHfirCAey73eyPw813ER dP34PNAo/yAUAvjQr20Genkd1RhpWUdXpFHbVtxQuVMt+x4uddvvl2J0T4AL+Nez palOZftoo+IHfY8QdDZMt0L7e8KaYSQGtJUB4thBcwrld7MkPf/NUh+/sihsHYKi 4lYpjNuWWQrMeUnZJv+OKD52/NYpLCCWCzBYbKb9qcMVwHFxQxtok/nOjLMRN/mn br8tBY6XE5Q9gWkudkgjbmL1Y8A2NC9q1FP6/Nk7NeGx/39YSXt7WZWC5lHGhyeC a8qMXvqK4BREXhDr/+gIAVtVHexwi3oLRiHzOagynLnlsxTu115Gd6HNY+0jQFeM jKEhGRxRwpz9sgrG0ahqw7oEuy5Xjw7lJByU6oqtPTThUMvbqg3g7C/07fSsn8Ox KUncYaVqDTO55p//2x5Xqu3r3hkWAMAVqum32o1js0YZbZQcn8Hoc4cT5r9tpuIC Cw5EMCpc7MKsyDPAKvV8EoNAZxJ1MP8YPBd6q8MNrbraeSZqJ8zZFaY7rM8NLfBh 0ukQAL7Q8KkJ3J9uG+P0ODV4B7hKjSnZbYFZttnEN57zcIgjwW6IIq4aFzjKAWMQ K/+pZ1zL7Gl+xCMDPoKQ =jIHW -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
