<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.mozilla.enigmail.general">
    <title>gmane.comp.mozilla.enigmail.general</title>
    <link>http://blog.gmane.org/gmane.comp.mozilla.enigmail.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/17016"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/17007"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16988"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16987"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16986"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16976"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16964"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16958"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16956"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16935"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16927"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16917"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16904"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16902"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16895"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16892"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16888"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16875"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16872"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16867"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/17016">
    <title>Icons in status bar missing</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/17016</link>
    <description>&lt;pre&gt;Hello,

since one of the recent updates, Enigmail does not show any icons (e.g.
key and pencil) in the status bar of the message window anymore. 

Is this normal? Or else, what could be wrong?

&lt;/pre&gt;</description>
    <dc:creator>Patrick Schönbach</dc:creator>
    <dc:date>2012-05-26T13:08:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/17007">
    <title>gpg agent issue with enigmail / tbird 12</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/17007</link>
    <description>&lt;pre&gt;
When attempting to encrypt and/or sign a message, I get:


Key 0x0F2E06CC not found or not valid. The (sub-)key might have expired.

gpg command line and output:
/opt/local/bin/gpg2
Error opening terminal: unknown.
gpg-agent[81149]: command get_passphrase failed: End of file
gpg: problem with the agent: End of file
gpg: skipped "0x0F2E06CC": Operation cancelled
gpg: [stdin]: sign+encrypt failed: Operation cancelled


I can, however, manually encrypt and/or sign stuff using the gpg2
command line.

This seems to happen regardless of whether or not I have a gpg-agent
running.

Suggestions, please?

&lt;/pre&gt;</description>
    <dc:creator>Patrick Spinler</dc:creator>
    <dc:date>2012-05-22T19:27:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16988">
    <title>Bugs</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16988</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----

- -----BEGIN PGP SIGNED MESSAGE-----

Hi All,

There are many bugs within enigmail. With Fedora-16 32 bit there was a general failure to
initialise - it was "fixed" by re-booting the machine. With Fedora 64 bit there was no cure.

There are general failings with LUbuntu 32 bit LXDE running TB 12.1 with enigmail 1.4 - to
wit:

(1) When making a per recipient rule to some one's public key - then enigmail encrypts
with your private key making it impossible for the recipient to read the e-mail.

(2) Passphrases can be input a dozen times or once an hour depending on how dysfunctional
enigmail is.

(3) Worse enigmail gets so dysfunctional that it ceases to operate - it freezes up.

(4) Also if you elect to send your public key with outgoing e-mails and then at a later
date take out the tick mark then enigmail still sends your public key even though there is
no selection to do so.

I reinstalled enigmail from your site. It's the same version that got installed via the
package manager - so it looks like I'm stuck with a dysfunctional enigmail :)

David

- - --
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBT7bcD+Jpqm7flRExAQFekwgAsLnv0y3c+0vvbxHqjiUQdzz45VtneQij
mYldZhwIBYr9i8oNNQcJq1E3N0Gw4rHp6jaKhZ4qLG+WN87i/K0mjokHBemO+wNM
gShKBt3O8dwvCIvY2EqV+XPu2o6o6vQbTV4qbgHX+U3eKt857cBqsXgptnIwE1d6
/qiZ8tJYqm5Ou2eUpLROnfhKjTPzRjd/A1VdOC+Kr/TGT6bbEbwH4EDVHe5DVRhV
us49aYhQFzMQKmqQta06j1CyVWJuk1nVrsb6g6sii/SbZjKjfv72q7CduPMOnYOE
635Y9BtQNMq8CuXCYPJcN8yEqTAKaOqbYtgnQpBLyn3ellS/TVC/gg==
=XZq7
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBT7bd2+Jpqm7flRExAQHGuQf8CfH8OPJKdsU0M8CwONbu58FtEKxWw/Jn
UyflcNZzaiCLlXu8tqej9nzQL+1Z1T3n/vq1Mt7M2/+D/zjHUIg2pG5hXkCyMnWH
SvYKdFJk+Dq4Sag3+/QqOlcyOwPuAvuPl3Yzo8NBm83hj6EMXv28FA6qg24Mn/Rr
e0bHoFxa2OOVZw+sXl5vDvNVKK2BZO+8gqrzoEK5EpZR1JT21o7JPDYip5TE1qsy
1Ja3K86bRhz+njhsKZcX1OY13HGC+E9DqQSl2kgZiegnBeQnJwTiEfkavBcvuK0F
TZQ/ZZXN+szwo5hMrKqvLNOzQI4JGxmUm7Qy0nP/Q9pmOjSWWE5lrQ==
=b/mi
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail&amp;lt; at &amp;gt;mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail
&lt;/pre&gt;</description>
    <dc:creator>david&lt; at &gt;gbenet.com</dc:creator>
    <dc:date>2012-05-18T23:40:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16987">
    <title>Bugs</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16987</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----

Hi All,

There are many bugs within enigmail. With Fedora-16 32 bit there was a general failure to
initialise - it was "fixed" by re-booting the machine. With Fedora 64 bit there was no cure.

There are general failings with LUbuntu 32 bit LXDE running TB 12.1 with enigmail 1.4 - to
wit:

(1) When making a per recipient rule to some one's public key - then enigmail encrypts
with your private key making it impossible for the recipient to read the e-mail.

(2) Passphrases can be input a dozen times or once an hour depending on how dysfunctional
enigmail is.

(3) Worse enigmail gets so dysfunctional that it ceases to operate - it freezes up.

(4) Also if you elect to send your public key with outgoing e-mails and then at a later
date take out the tick mark then enigmail still sends your public key even though there is
no selection to do so.

I reinstalled enigmail from your site. It's the same version that got installed via the
package manager - so it looks like I'm stuck with a dysfunctional enigmail :)

David

- -- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBT7bcD+Jpqm7flRExAQFekwgAsLnv0y3c+0vvbxHqjiUQdzz45VtneQij
mYldZhwIBYr9i8oNNQcJq1E3N0Gw4rHp6jaKhZ4qLG+WN87i/K0mjokHBemO+wNM
gShKBt3O8dwvCIvY2EqV+XPu2o6o6vQbTV4qbgHX+U3eKt857cBqsXgptnIwE1d6
/qiZ8tJYqm5Ou2eUpLROnfhKjTPzRjd/A1VdOC+Kr/TGT6bbEbwH4EDVHe5DVRhV
us49aYhQFzMQKmqQta06j1CyVWJuk1nVrsb6g6sii/SbZjKjfv72q7CduPMOnYOE
635Y9BtQNMq8CuXCYPJcN8yEqTAKaOqbYtgnQpBLyn3ellS/TVC/gg==
=XZq7
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail&amp;lt; at &amp;gt;mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail
&lt;/pre&gt;</description>
    <dc:creator>david&lt; at &gt;gbenet.com</dc:creator>
    <dc:date>2012-05-18T23:32:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16986">
    <title>bugs-1</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16986</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----

Oh and when you send an e-mail - to which you have added a per recipient rule and then
write an e-mail - and take out the tick mark to encrypt - it still encrypts!!

I really don't like this!!!!!!!

David

- -- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBT7bdYeJpqm7flRExAQGEggf/eQCmq5yO8ZSqXEQQlbek3zBtrQw4BXv9
RO2DV/2V37/oFLiZHltFGHjNd0zATULOIFk7CpuikKNhFChYjLVRKlFZrE5dt8Kf
3NUIOXoHXr2zhNIW+bZaDBtBTSARzTdAFP/S2oY7M+KxF3PB8rC8VxTLaF9Dq+mK
Uablm276fFrI2XgBbMz82eigUYbqyKbU17QCQpeJxfzm03P1nqKlwnhjh1+2cjJg
xlKi7DiYpD9gGTKEhLMMJAA+3c6DRRVfUVY38gm0TP+btooC/iQwLuD1p1F8hwn+
gAax9iLCr9PbRUMRRyW9KFGQLlcs9YtdEJIQH4Pjxz9lm66ZAOulFA==
=/sCU
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail&amp;lt; at &amp;gt;mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail
&lt;/pre&gt;</description>
    <dc:creator>david&lt; at &gt;gbenet.com</dc:creator>
    <dc:date>2012-05-18T23:38:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16976">
    <title>Decrypting Attachments as created by "Encrypt/sign eachattachment separately ..."</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16976</link>
    <description>&lt;pre&gt;Hi!

A Debian User has discovered that enigmail fails to decrypt attachments 
encrypted by enigmail with the option mentioned in the subject (decryption 
of the main meesage body works fine). This problem is reproducible with the 
latest enigmail version 1.4.1 and icedove (thunderbird) 11. 

I've put the source (stripped most of the header) of such a message at 

http://wserver.wm1.at/~willi/debian/enigmail/fails_to_decrypt_attachment.txt

Is this a known problem or should I file a bug report? I'd also like to know 
whether other people can reproduce this problem, after all, I always have to 
consider the possibility that I've messed something up in the Debian 
package.

WM
&lt;/pre&gt;</description>
    <dc:creator>Willi Mann</dc:creator>
    <dc:date>2012-05-10T17:06:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16964">
    <title>Enigmail stopped working - loads keys for infinity</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16964</link>
    <description>&lt;pre&gt;Hello,

I am using Enigmail on Fedora 16 x86_64 with Thunderbird. TB version is
12.0.1, Enigmail version is 1.4.1.

Enigmail stopped working completely some days ago, and any attempt to
use it complains that Enigmail
isn't correctly initialized. When I open OpenPGP / Key management, there
is an endlessly  running status
bar at the bottom of the window, saying "Loading keys, please wait ..."
(my translation, the message is in Czech),
and no keys are visible. AFAIK, I have done nothing with my keyring (the
keyset is constant, nothing added...), but
some of them may have expired in that time - I am not sure.

There are some interesting errors in the Thunderbird error console,
generated at the startup of Thunderbird, namely:

subprocess.jsm: got error from stdinWorker: expected type int, got (void 0)

and this repeats once more with a slightly different message:

expected type int, got (void 0)
resource://enigmail/subprocess_worker_unix.js

Can you help me?

Best regards

Marian Kechlibar
&lt;/pre&gt;</description>
    <dc:creator>Marian Kechlibar</dc:creator>
    <dc:date>2012-05-09T10:24:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16958">
    <title>Delay when verifying signatures.</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16958</link>
    <description>&lt;pre&gt;Hi,

when verifying a signed e-mail, whether it is in-line or PGP/MIME,
approximately 30 seconds elapse from issuing the command, to its
completion; using Menu&amp;gt;OpenPGP&amp;gt;Decrypt/Verify, or cliking the 'Decrypt'
icon in the ToolBar.

I know that the required public key is included in my public keyring.
E.G., messages signed by Patrick or by Ludwig.

The process completes successfully, displaying Patrick's or Ludwig's photo.

When the public key required for verifying does not contain a picture
file, verification is instantaneous.


Excerpts from Error Console when verifying a signature with a public key
that contains a photo file.

Timestamp: 5/7/12 9:30:26 AM
Error: enigmail.js: CreateFileStream: Failed to create Desktop Log
Directory/enigcmd.txt


Timestamp: 5/7/12 9:30:58 AM
Error: enigmail.js: WriteFileContents: Failed to write to Desktop Log
Directory/enigerr.txt

I am not suggesting that the photo file is responsible for the delay,
I'm trying to report as completely as I can.
TIA for your attention.

Charly
Mac OS X 10.7.4 (11E52) MacBook Intel C2Duo 2GHz-GnuPG MacGPG2-2.0.17-9
Thunderbird 12.0.1 Enigmail 1.5a1pre (20120506-1748)
&lt;/pre&gt;</description>
    <dc:creator>Charly Avital</dc:creator>
    <dc:date>2012-05-07T13:53:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16956">
    <title>OpenPGP headers</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16956</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

There are options for enabling OpenPGP headers, KEYID and URL to the
key in account settings.  I am just curious, Is this information used
by any email client or Enigmail or is it there just for people who
read headers of emails? I have both enabled.

- -- 
Mika Suomalainen
gpg --keyserver pool.sks-keyservers.net --recv-keys 4DB53CFE82A46728
Key fingerprint = 24BC 1573 B8EE D666 D10A  AA65 4DB5 3CFE 82A4 6728
http://mkaysi.github.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPptlgAAoJEE21PP6CpGcoRW0P/0ghXRYMO8PwliO81NFvVi6b
IKAL8hQKe6hbKcfdGP6zlIOZfSdgXcbtdvDO5cllKjGNqHpUUErIjuS7xfT5bdU/
V6i01pyWm1C7Q83uOEvr4Jt02MOpSXaAsGxNaESywWu1jJyA9byKEm0yv8WCRqYn
5ciDDHvPD6vdO0FQt6fvEWVoCpaxyKtLBcnOzISIAtg+sg7imJ5yX670ex5gdqHG
a8LEp4PPWiXAOHGmUzM3gZR1NfbqrNUIGCl7pXXur/pbDLNouyzQ2ZSNLS55Epo/
B27uCKtTkCQX6vkP3WhiXZVCt22/AhRLc5WHiDU06TorV/1V/RcXANPQ6jIiYHY2
OkmeIJpol/BEP6wlAdo4fcPcHM8QchIf6LXwaYhttZXrBkH8usk6r4Aqz5F9vXuI
rVrzrBEpeH7i/k49IcJyb7aD1cb2GAovBuVVO4srCSgy/fyWIZooEkwsT5/5tqKp
wD1hrfgvPakFXMC2rcTqalpWKHINBWxn+fz7tL8nKks9OtPP8zNfskU8wRzpW1kC
LxumQHANl3ZDaxxMAfsIJmTvd9WZxx3IhPck0+ya38SHVZLOJY02mTjkXaC5Ezru
thNrf/HNiFN3XEdWBGBK9hXEXvvZpFrtnAKeNqrBHY9DFXcQYM4PPcJGIIQhA3YI
WOuw+DLQqoV3NgL75T3G
=lk5c
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Mika Suomalainen</dc:creator>
    <dc:date>2012-05-06T20:04:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16935">
    <title>PGP/MIME signature doesn't get verified by Enigmail on some mailing lists.</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16935</link>
    <description>&lt;pre&gt;Hi,

Why some signature.asc files don't get recognized by Enigmail and they
appear as normal attachments and Enigmail has no idea that they are
signatures?
This has happened at least on gnupg-user, ubuntu-user and
ubuntu-security-announcements mailing lists.

I am thinking of moving back to normal INLINE signatures and include
notice about this weird issue in my signature if this problem isn't
caused by anything which I can do something to.

&lt;/pre&gt;</description>
    <dc:creator>Mika Suomalainen</dc:creator>
    <dc:date>2012-05-02T12:57:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16927">
    <title>PGP/MIME messages?</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16927</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am receiving what I think are PGP/MIME signed messages (I haven't
tested sending myself such messages) and Enigmail doesn't detect the
signature.  Is this an issue with my configuration, or is Enigmail not
really setup to handle this?

Jigme Datse Yli-Rasku
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPndkBAAoJEPTTlG5JFW+7iQYH/jb27nV+OQ509wAcLjtQUxYe
rjlniW+slbM/DnxLnSm+45UKpvVcVLfQAkFAR7LoI7CeJ3zjXb1Q9W6mGOGOm89A
6CZlnyYRVKN8Mr6bbnqQ2OklKAF3ThkDwhdq7btu9ZORtfGAd0/jFME+hGPQisQk
q2sXz4GNivHmwSddvP8/0FLhBrSrzeRp8MgxzX5RFpNHR9+ITtONv+1U21+MLO1t
qvbGQjU9WpS2zIx5htkHWbEpFaiT/mn77GcUolTyZPBzaWTVjPurr/8WFr1KTaoA
rcIGMNMW60yppiNVlkfNa4gWjU1gMNvn4KNcYRVL2l+MbZ2szICBsfPi9sU472E=
=qxeV
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Jigme Datse Yli-Rasku</dc:creator>
    <dc:date>2012-04-30T00:12:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16917">
    <title>First Use</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16917</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello. I am following the manual suggestions for starting up Enigmail
and they suggested I write to you to ensure that my "sign" option is
working. This is coming to you from Weymouth, Nova Scotia where it is
overcast, but warm, at the moment.

Thanks for your help.

Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPmFHlAAoJEK6G+CLT69+jTXcH/1OpYat/jolOFve1/fmb/4oE
5+PQBL5X44lGhrW5j53kG7Pt8VTMtRYfJ5IlEWkBJgs0a3wO1ZIWGZjq+/YFAuvz
Kg8i93paZbnMD9r4YaMMPQZFJN9gbCzfy0shzZkPYkj2R40jsEQccv2AiA4goVDV
Y3UiKDlwBGmMGIkBlgvBHXA2ySfa7kHluu9z0ep7Ei0ov11fKpI3C5ofNu3rFl7/
/cvfm0noHdYz/u2Ms5pe9AUYGgwaPW/YwIincNAXmEp04I0QoKhLJ78WN3DqNxF9
iwG4YS+t3Gx/n2BVwX93GxBoNXbp+668BIF3JRyxeMF56JlfLAwUTRSOQnF3U6M=
=EH/A
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Andy Barnard</dc:creator>
    <dc:date>2012-04-25T19:35:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16904">
    <title>Error decrypting messages</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16904</link>
    <description>&lt;pre&gt;I get the following error on Aurora / Earlybird 14.0a2 (2012-04-25) with
Enigmail 1.5a1pre nightly (2012-04-22) when trying to decrypt a message:

Timestamp: 25-4-2012 17:25:20
Error: enigmailMessengerOverlay.js: messageDecryptCb: caught exception:
TypeError
Message: 'Cc[NS_IPCBUFFER_CONTRACTID] is undefined'
File:
file:///C:/Users/OEEkker.AMC/AppData/Roaming/Thunderbird/Profiles/k4l90cvh.default/extensions/%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D/components/enigmail.js
Line:    2307
Stack:
&amp;lt; at &amp;gt;file:///C:/Users/OEEkker.AMC/AppData/Roaming/Thunderbird/Profiles/k4l90cvh.default/extensions/%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D/components/enigmail.js:2307
&amp;lt; at &amp;gt;chrome://enigmail/content/enigmailMessengerOverlay.js:909
&amp;lt; at &amp;gt;chrome://enigmail/content/enigmailMessengerOverlay.js:832
&amp;lt; at &amp;gt;chrome://enigmail/content/enigmailMessengerOverlay.js:743
&amp;lt; at &amp;gt;chrome://enigmail/content/enigmailMessengerOverlay.js:504
&amp;lt; at &amp;gt;resource://enigmail/enigmailCommon.jsm:1214
_______________________________________________
Enigmail mailing list
Enigmail&amp;lt; at &amp;gt;mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail
&lt;/pre&gt;</description>
    <dc:creator>Onno Ekker</dc:creator>
    <dc:date>2012-04-25T15:28:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16902">
    <title>enigmail-nightly-comm-central-win-lin.xpi (build date: 2012-04-24, version: 1.5a1pre)</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16902</link>
    <description>&lt;pre&gt;Patrick,

The Enigmail package labeled:

for Thunderbird &amp;amp; SeaMonkey "comm-central"
enigmail-nightly-comm-central-win-lin.xpi (build date: 2012-04-24, 
version: 1.5a1pre)

is not compatible with the Daily labeled:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120425 
Thunderbird/15.0a1

with a build config of:

about:buildconfig
Build Machine

momo-vm-win2k3-02
Source

Built from http://hg.mozilla.org/mozilla-central/rev/75c7378c87b6
Build platform
target
i686-pc-mingw32
Build tools
Compiler Version Compiler flags
d;D:\mozilla-build\msys\mozilla-build\python25\python2.5.exe -O 
e;D:\mozilla-build\msys\buildbot\win32-comm-central-nightly\build\mozilla\build\cl.py 
cl 14.00.50727.762 -TC -nologo -W3 -Gy -Fdgenerated.pdb -we4553 
-DNDEBUG -DTRIMMED -Zi -UDEBUG -DNDEBUG -O1 -Oy
d;D:\mozilla-build\msys\mozilla-build\python25\python2.5.exe -O 
e;D:\mozilla-build\msys\buildbot\win32-comm-central-nightly\build\mozilla\build\cl.py 
cl 14.00.50727.762 -TP -nologo -W3 -Gy -Fdgenerated.pdb -wd4800 
-we4553 -DNDEBUG -DTRIMMED -Zi -UDEBUG -DNDEBUG -O1 -Oy
Configure arguments

--enable-application=mail --enable-update-channel=nightly 
--enable-update-packaging --disable-debug --enable-optimize 
--enable-tests --enable-jemalloc --enable-application=mail 
--enable-update-channel=nightly --enable-update-packaging 
--disable-debug --enable-optimize --enable-tests --enable-jemalloc 
--enable-application=../mail --disable-official-branding 
--with-branding=../mail/branding/nightly --cache-file=.././config.cache 
--srcdir=/e/buildbot/win32-comm-central-nightly/build/mozilla
&lt;/pre&gt;</description>
    <dc:creator>David</dc:creator>
    <dc:date>2012-04-25T12:53:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16895">
    <title>OpenPGP Options</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16895</link>
    <description>&lt;pre&gt;Hello.  Am I correct in saying that I cannot save a pending message as an 
encrypted one unless the "From" field has an Identity with a user that has 
been configured already to use Enigmail OpenPGP support? I ask because I 
thought I should be able to encrypt without signing for any recipient 
regardless of the sender's ID, but that appears not to be the case. After 
all, encryption is based on the recipient, not on the sender. So, apparently 
I cannot have an on-the-fly "From" header for a message and save it, even 
temporarily, as encrypted, although it would also seem to me that this might 
be allowed if my configuration options included encrypting to self.  Am I 
missing something? Thanks. 
&lt;/pre&gt;</description>
    <dc:creator>Papo</dc:creator>
    <dc:date>2012-04-25T03:43:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16892">
    <title>Thunderbird 12.0</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16892</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

from &amp;lt;http://enigmail.mozdev.org/download/nightly.php.html&amp;gt;



As I indicated in a previous posting, I am running TB 12.0, which does
not seem to be beta anymore, but stable.

Maybe I'm getting a wrong rendition of the above page, because of some
browser problem.

FYI.
Charly
Mac OS X 10.7.4 (11E52) MacBook Intel C2Duo 2GHz-GnuPG MacGPG2-2.0.17
Thunderbird 12.0 Enigmail 1.5a1pre (20120424-2038)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GnuPG for Privacy
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCgAGBQJPlxaTAAoJEPDKqP3/J6K0a80IALcfN05v/xdMU1WwXYv/Yrjy
8kKV46wn77Wetb2sVct3VND3M+O2/oS0T0TB2m98X7dITIAX4SgNNI/Ouyu+BmVV
YJ4Z9Q9eCYhbxkYfxexttyp1ds29uBtAcsyenxQypgcUEz3ClCqznUKqFXyoQHLa
UH2TK+nAO1SXC3S8+jg70bBWGffWFcPcIXGmCkP0JYuAS0qQxMKxAJrgB4CNX1af
k07oknvFU/MhlQb2TcvJhlyoImOfgOXQugD71Hq72KIfk3yW9Rpz76cPcuUVvDuT
Gw5A1cALb4NZLw0CXOFn/3PmKZEVWY7zG4dTcpY+qLrCUgffSprdxyIZUlf/UWQ=
=3EwJ
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Charly Avital</dc:creator>
    <dc:date>2012-04-24T21:09:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16888">
    <title>Fwd: Re:  Character Set disclosures</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16888</link>
    <description>&lt;pre&gt;Mozdev was bouncing my regular MTAs last night, Earthlink &amp;amp; Roadrunner.
This never got through. Trying one last time with Google.

-------- Original Message --------
Subject: Re: [Enigmail] Character Set disclosures
Date: Sun, 22 Apr 2012 00:18:14 -0500
From: John Clizbe &amp;lt;John&amp;lt; at &amp;gt;enigmail.net&amp;gt;
Reply-To: Enigmail user discussion list &amp;lt;enigmail&amp;lt; at &amp;gt;mozdev.org&amp;gt;
Organization: Mozilla &amp;amp; Mozdev Enigmail Team
To: Enigmail user discussion list &amp;lt;enigmail&amp;lt; at &amp;gt;mozdev.org&amp;gt;

Papo wrote:

In the beginning, there was 7-bit ASCII and and it was deemed adequate for all
could communicate (albeit, it was a hassle if you weren't writing English). And
then the users, being a proud lot, said. "Behold! Notice there is an used 8th
bit, we can use it to map the rest of our characters." And soon a plethora of
character sets were released unto the Internet and messages began to look like:
[
  Catalan:   Per una versiA3 en CatalA  dâ?Taquest missatge, enviA_ un correu
             electrA²nic amb lâ?Tassumpte â?oHELP CAâ?? a lâ?TadreA§a &amp;lt;pubaddr&amp;gt;
  German:    FA¼r eine deutschsprachige Fassung dieses Textes senden Sie
             eine Mail mit dem Betreff "HELP DE" an die folgende Adresse
             &amp;lt;pubaddr&amp;gt;.
  English:   For an English version of this message, send an e-mail with
             a subject line of "HELP EN" to &amp;lt;pubaddr&amp;gt;.
  Spanish:   Para una versiA3n en EspaA±ol de este mensaje, envA-e un e-mail
             con el asunto "HELP ES" a la direcciA3n &amp;lt;pubaddr&amp;gt;
]
instead of
[
  Catalan:   Per una versió en Català d’aquest missatge, enviï un correu
             electrònic amb l’assumpte “HELP CA” a l’adreça &amp;lt;pubaddr&amp;gt;
  German:    Für eine deutschsprachige Fassung dieses Textes senden Sie
             eine Mail mit dem Betreff "HELP DE" an die folgende Adresse
             &amp;lt;pubaddr&amp;gt;.
  English:   For an English version of this message, send an e-mail with
             a subject line of "HELP EN" to &amp;lt;pubaddr&amp;gt;.
  Spanish:   Para una versión en Español de este mensaje, envíe un e-mail
             con el asunto "HELP ES" a la dirección &amp;lt;pubaddr&amp;gt;
]

and the users were displeased and the Standards Bodies were in a kerfluffle.

Which is why we see so many different values for CharSet. Unicode (UTF-8 and
UTF-16) is a standard to lead us from the confusion of multiple character set
mappings back to one common mapping.
Unicode FAQ: https://www.cl.cam.ac.uk/~mgk25/unicode.html

The MUA (in most case for this list Thunderbird or Seamonkey) sets the character
set encoding, based on your global composition options. You may change it, but I
don't think you can disable it. Enigmail then picks up the setting for setting
the message's armor header. Disabling it for encrypted OpenPGP traffic would be
a disaster. OpenPGP only knows bit and bytes, it has ZERO idea of characters.
The Charset: header in OpenPGP tells the application how to map the bytes it has
decrypted back into text for you to read.

It's a "Good Thing™" please let it do its job.

-John
&lt;/pre&gt;</description>
    <dc:creator>John Clizbe</dc:creator>
    <dc:date>2012-04-22T22:11:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16875">
    <title>Character Set disclosures</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16875</link>
    <description>&lt;pre&gt;Hello. At the top of the encrypted text by Enigmail on Windows OS, I see 
information about the apparent character set used in the unencrypted 
message. I do not see this information with gpg and other front-end 
programs, and I am not sure what setting in Enigmail causes it. Is there a 
way to turn off this feature? I am not sure that it helps anything or adds 
any value. Any ideas? This is what it looks like:

-----BEGIN PGP MESSAGE-----
Charset: ISO-8859-1
Version: GnuPG v2.0.17 (MingW32)
&lt;/pre&gt;</description>
    <dc:creator>Papo</dc:creator>
    <dc:date>2012-04-22T02:47:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16872">
    <title>symmetric encryption</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16872</link>
    <description>&lt;pre&gt;Hello. Nothing I found with Google indicated that Enigmail is capable of 
symmetric encryption/decryption. Before I spend more time on the search, I 
want to confirm it here? Can it? Thanks. 
&lt;/pre&gt;</description>
    <dc:creator>Papo</dc:creator>
    <dc:date>2012-04-20T21:58:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16867">
    <title>using encryption to self</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16867</link>
    <description>&lt;pre&gt;Hello. I have Enigmail 1.4 in Thunderbird 11.0.1 on Windows OS.  I would 
like to have Enigmail configured so that whenever I encrypt a message to 
send, it also encrypts it to a key of mine so that I can later decrypt and 
read the messages I have saved. I would like to have it encrypt to a key of 
mine which I would not normally use for any other purpose. I do not want 
this key ID to be sent along with the message for others to find. So using 
some sort of hidden encryption to self option would work well for me, and I 
can create a special key if need be.  My question is how would I configure 
this to occur within Enigmail? I am not sure, but I was thinking that I 
might use the field in OpenPGP Preferences&amp;gt; Advanced, where it is labeled 
"Additional parameters for GnuPG"?  Any ideas about how to do this would be 
welcome.  Thanks. 
&lt;/pre&gt;</description>
    <dc:creator>Papo</dc:creator>
    <dc:date>2012-04-20T07:40:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16865">
    <title>UBUNTU GnuPG not found</title>
    <link>http://comments.gmane.org/gmane.comp.mozilla.enigmail.general/16865</link>
    <description>&lt;pre&gt;I'm trying to setup Enigmail on an UBUNTU system and it gives me GnuPG:
Not Found
override ?  ( browse )

what do ti give it?  I found gpg in the /usr directory and I can run GPG
commands from the Terminal window so GPG is clearly available.

&lt;/pre&gt;</description>
    <dc:creator>Mike Acker</dc:creator>
    <dc:date>2012-04-18T15:17:14</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.mozilla.enigmail.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.mozilla.enigmail.general</link>
  </textinput>
</rdf:RDF>

