[opensuse] Enigmail header problem in Thunderbird on SuSE...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All Was doing a little tweaking of my mail header config in Thunderbird and I have come across some rather quirky behaviour with the 0.95.5 version of enigmail and Thunderbird 2.0.0.9 (SuSE RPM). It has rather distracted me as I thought this was something to do with what I had been doing, which it seems not to be. If I verify the signature the Content-Type: text/plain; charset=ISO-8859-1 part of the header appears in the body of the message on my machine. I have checked the enigmail bugzilla and it has not been reported there. I know the SuSE build is slightly different from the Mozilla release, so it is possibly a SuSE thing. Can anyone else confirm this behaviour. It is not a major issue as far as I can work out, but I have spent rather more time on working out what is going on than I would have preferred. I have no idea when this started happening... I only noticed it with my own mail (somehow the verification settings seem to have changed somewhere along the line so I did not see it in other peoples messages only my own). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHdNwoasN0sSnLmgIRAh78AJ4no+Vcmx5hHoW6we8AhvU60ZqE0gCgyXh4 I7poy+J89IvXvXPcGP7+iVE= =FkuV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote:
Was doing a little tweaking of my mail header config in Thunderbird and I have come across some rather quirky behaviour with the 0.95.5 version of enigmail and Thunderbird 2.0.0.9 (SuSE RPM). It has rather distracted me as I thought this was something to do with what I had been doing, which it seems not to be.
If I verify the signature the
Content-Type: text/plain; charset=ISO-8859-1
Ah. Yes, I have noticed (rather I was told of this) that if my emails go out in English the signature verifies well in Thunderbird, but if they go in Spanish it doesn't verify. The difference is that in the second case the email uses utf-8. A good email goes like this: ... User-Agent: Alpine 0.999999 (LSU 847 2007-12-06) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Status: RO X-Status: X-Keywords: X-UID: 2 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... A bad one goes like this: ... User-Agent: Alpine 0.999999 (LSU 847 2007-12-06) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463809023-467100771-1198265468=:24727" Status: RO X-Status: X-Keywords: X-UID: 3 - ---1463809023-467100771-1198265468=:24727 Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... But I haven't studied the thunderbird part of the problem. I know both kind of signatures verify well using kmail, for instance, so it is not my "fault".
part of the header appears in the body of the message on my machine. I have checked the enigmail bugzilla and it has not been reported there. I know the SuSE build is slightly different from the Mozilla release, so it is possibly a SuSE thing. Can anyone else confirm this behaviour. It is not a major issue as far as I can work out, but I have spent rather more time on working out what is going on than I would have preferred.
Sorry. I have known this for a bit more than a week, but I didn't though of reporting it to bugzilla, not knowing if it is a Novell issue. I commented this to the developper of the gpg filter I use, in the Alpine email list. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHdN//tTMYHG2NR9URAmPtAJ4ofHlMC56tYFzLmF2pH8SwR6L2MACglhMX bNSlKKvsvY9WqbGgkycj40I= =cShd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote:
<snip>
If I verify the signature the
Content-Type: text/plain; charset=ISO-8859-1
Ah.
Yes, I have noticed (rather I was told of this) that if my emails go out in English the signature verifies well in Thunderbird, but if they go in Spanish it doesn't verify. The difference is that in the second case the email uses utf-8.
A good email goes like this:
... User-Agent: Alpine 0.999999 (LSU 847 2007-12-06) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Status: RO X-Status: X-Keywords: X-UID: 2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ...
A bad one goes like this:
... User-Agent: Alpine 0.999999 (LSU 847 2007-12-06) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463809023-467100771-1198265468=:24727" Status: RO X-Status: X-Keywords: X-UID: 3
---1463809023-467100771-1198265468=:24727 Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ...
But I haven't studied the thunderbird part of the problem. I know both kind of signatures verify well using kmail, for instance, so it is not my "fault".
The language/char set thing seems to be a known enigmail extension problem... (noticed references to it in passing while checking to see there were any references to this header problem on the enigmail site). I get the impression there is a work around... As it is, your signature validates fine but this header bit turns up before the signed message part. This seems to suggest the enigmail extension is causing Thunderbird to discard or ignore this part of the header for some reason (One of your earlier messages was immediately available for checking, and as I know you are also not a Thunderbird user it was rather handy for narrowing things down, otherwise I would need to configure Evolution or KMail for signing for further testing :-) ).
part of the header appears in the body of the message on my machine. I have checked the enigmail bugzilla and it has not been reported there. I know the SuSE build is slightly different from the Mozilla release, so it is possibly a SuSE thing. Can anyone else confirm this behaviour. It is not a major issue as far as I can work out, but I have spent rather more time on working out what is going on than I would have preferred.
Sorry. I have known this for a bit more than a week, but I didn't though of reporting it to bugzilla, not knowing if it is a Novell issue. I commented this to the developper of the gpg filter I use, in the Alpine email list.
This is what I am attempting to establish.. if anyone is seeing this on a non SuSE version of Thunderbird or not ... In searching for references about the problem I came across security references associated with Content-Type and I rather wondering whether we are getting some sort of interaction between a Novell specific patch and enigmail... I could test with windows but I am not certain this would be valid as the Windows version of the enigmail extension seems to be a bit less featured (and I would have to configure it).... It is more of a nuisance than anything else...
-- Cheers, Carlos E. R.
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHdPj/asN0sSnLmgIRAkx0AJ9jD0qhd62avDyp50soYZZxw8hzUQCcDgn+ f/3NY1dKQdj1HjM7cE6ELVA= =c2LG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote:
<snip>
A bad one goes like this:
...
<snip>
Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT
I think the second line is the issue for the certificate problem. When it is 7 bit we get the Content-Type line turning up in the main message but the signature is flagged as good. When it is 8 bit (the signature is probably corrupted) and the signature is flagged as bad. (Just got message flagged as having a bad signature and examining headers this is the only common denominator I can see). Now whether these are two different problems or symptoms of the same problem is a moot point...
-- Cheers, Carlos E. R.
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHd3HDasN0sSnLmgIRAqt8AKDW+b7rZUCamYaRQh6PdCDQE1qGgwCg5blK Dd4OlZeisg0xsy84dKtUgcI= =oc5C -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-12-30 at 10:24 -0000, G T Smith wrote:
Carlos E. R. wrote:
The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote:
<snip>
A bad one goes like this:
...
<snip>
Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT
I think the second line is the issue for the certificate problem. When it is 7 bit we get the Content-Type line turning up in the main message but the signature is flagged as good. When it is 8 bit (the signature is probably corrupted) and the signature is flagged as bad. (Just got message flagged as having a bad signature and examining headers this is the only common denominator I can see). Now whether these are two different problems or symptoms of the same problem is a moot point...
In my case the signature is correct, because if I check the same email (the same folder) using other programs, like KMail or Balsa they say it is correct. It is Thunderibird who says it is not. I'll use some local chars to force this one to use utf: áéíóúñ ŕýú This email will not check in thunderbird, I think. I'll tell you later. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHd34VtTMYHG2NR9URAlEdAKCXJeQ78f2LQ4u1FVZQN0y4GYxgHwCeL+L8 fOFwismgursr2BZEAGWCCWI= =Mpk5 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
I'll use some local chars to force this one to use utf: áéíóúñ ŕýú
This email will not check in thunderbird, I think. I'll tell you later.
Using my sent folder (ie, local copy, not altered): Alpine: signature verifies. Balsa: signature verifies. KMail: signature verifies. Thunderbird: signature does not verify. Sea momnkey mail: signature does not verify. So... the msg block and signature is correct, not modified, and the signature verifies; but enigmail fails to verify it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHd4C+tTMYHG2NR9URApxiAJ9N8gcfsbvVbsEZSG+LepyHH3NbzgCfU1My M2WtLM1tDjL2fCIIeCDnTMU= =pujv -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Sunday 2007-12-30 at 10:24 -0000, G T Smith wrote:
Carlos E. R. wrote:
The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote:
<snip>
A bad one goes like this:
...
<snip>
Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT
I think the second line is the issue for the certificate problem. When it is 7 bit we get the Content-Type line turning up in the main message but the signature is flagged as good. When it is 8 bit (the signature is probably corrupted) and the signature is flagged as bad. (Just got message flagged as having a bad signature and examining headers this is the only common denominator I can see). Now whether these are two different problems or symptoms of the same problem is a moot point...
In my case the signature is correct, because if I check the same email (the same folder) using other programs, like KMail or Balsa they say it is correct. It is Thunderibird who says it is not.
I'll use some local chars to force this one to use utf: áéíóúñ Uýú
This email will not check in thunderbird, I think. I'll tell you later.
-- Cheers, Carlos E. R.
No it did not... :-(
Looking at it further in my case I enabled a foreign language work
around for sending. If I am lucky my signature will come across in this
reply as OK.
What we are getting is....
enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -d
gpg: Signature made Sun 30 Dec 2007 11:16:37 GMT using DSA key ID 6D8D47D5
gpg: BAD signature from "Carlos Robinson (Carlos)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <snip>
No it did not... :-(
Looking at it further in my case I enabled a foreign language work around for sending. If I am lucky my signature will come across in this reply as OK....
Ok, that did not work :-( Now to try a build against the SuSE source ... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHd4c/asN0sSnLmgIRAnRfAJ9yw43sssMO0MQGDTLq+47ZoyR9DwCgpt9R eBDv/IAAoWalm84s22fKciw= =LI5V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G T Smith wrote:
<snip>
No it did not... :-(
Looking at it further in my case I enabled a foreign language work around for sending. If I am lucky my signature will come across in this reply as OK....
Ok, that did not work :-( Now to try a build against the SuSE source ...
Which proves not to be necessary. After looking more closely at the files in the SuSE RPM I find enigmail is included and is current (doh!), so a bug report will probably need to be filed with Novell in first instance .... Which is just as well as the documentation suggests it could be the compile from hell :-) - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHd9doasN0sSnLmgIRAjDMAJ9dYVsPAQoFwYy44+Q4tJZ1PAPcfwCfcBMx gixDEL5HjT1ODd1yWG5SGoA= =Vwxk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
G T Smith wrote:
<snip>
No it did not... :-( Looking at it further in my case I enabled a foreign language work around for sending. If I am lucky my signature will come across in this reply as OK.... Ok, that did not work :-( Now to try a build against the SuSE source ...
Which proves not to be necessary. After looking more closely at the files in the SuSE RPM I find enigmail is included and is current (doh!), so a bug report will probably need to be filed with Novell in first instance ....
Which is just as well as the documentation suggests it could be the compile from hell :-)
Feel free to file a descriptive bugreport at the Novell bugzilla. What I couldn't find in this thread is if - Mozilla's Thunderbird (non-RPM) with Enigmail doesn't show this issue - the openSUSE RPM with a downloaded Enigmail extension doesn't show this issue I wouldn't expect a difference but you never know ;-) Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-12-30 at 19:40 +0100, Wolfgang Rosenauer wrote:
Feel free to file a descriptive bugreport at the Novell bugzilla. What I couldn't find in this thread is if - Mozilla's Thunderbird (non-RPM) with Enigmail doesn't show this issue - the openSUSE RPM with a downloaded Enigmail extension doesn't show this issue
I wouldn't expect a difference but you never know ;-)
The only thing I know is that I'm using only opensuse rpms, and they have this problem. I haven't tried external sources of thunderbird or enigmail. To trigger it, I only have to use local chars, and this email will not verify with enigmail: áéíóúẃéŕýṕñ¿?¡! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHeCswtTMYHG2NR9URAqktAJ9AkYMFa+/GAFWiwB/2C7pwOYGbOACgjX8n dTGLtqnr91xDwkc+9ZDaCXE= =w6cY -----END PGP SIGNATURE-----
Carlos E. R. wrote:
[...]
The only thing I know is that I'm using only opensuse rpms, and they have this problem. I haven't tried external sources of thunderbird or enigmail.
To trigger it, I only have to use local chars, and this email will not verify with enigmail: áéíóúéUýUñ¿?¡!
I didn't read the whole thread, but my Thunderbird (with enigmail) certainly tells me that your email has an untrusted good signature. Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas Hertweck wrote:
Carlos E. R. wrote:
[...]
The only thing I know is that I'm using only opensuse rpms, and they have this problem. I haven't tried external sources of thunderbird or enigmail.
To trigger it, I only have to use local chars, and this email will not verify with enigmail: áéíóúéUýUñ¿?¡!
I didn't read the whole thread, but my Thunderbird (with enigmail) certainly tells me that your email has an untrusted good signature.
Th.
Having looked at your header it is indicating UTF8 and 8bit transmission, my defaults are ISO and 7bit... for me the signature is broken... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHeM9MasN0sSnLmgIRAoUGAJ9yNsqOYsVCu+Vafsj/Nr1gACWUWwCfQLi9 EjwYgeuekZ4CFjc4w3l7nEU= =1Tlf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Sunday 2007-12-30 at 19:40 +0100, Wolfgang Rosenauer wrote:
Feel free to file a descriptive bugreport at the Novell bugzilla. What I couldn't find in this thread is if - Mozilla's Thunderbird (non-RPM) with Enigmail doesn't show this issue - the openSUSE RPM with a downloaded Enigmail extension doesn't show this issue
I wouldn't expect a difference but you never know ;-)
The only thing I know is that I'm using only opensuse rpms, and they have this problem. I haven't tried external sources of thunderbird or enigmail.
To trigger it, I only have to use local chars, and this email will not verify with enigmail: áéíóúéUýUñ¿?¡!
-- Cheers, Carlos E. R.
FYI Latest update of enigmail seems to have fixed this issue. Still getting Content header issue.., but that is more of a cosmetic nuisance... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHgk1QasN0sSnLmgIRAg2DAKC/z54mQvZpbMOxu2o90jr1PfWNfwCfUtVd dynhO/+AymqqsOGKEWLJeDc= =80T7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wolfgang Rosenauer wrote:
G T Smith wrote:
G T Smith wrote:
<snip>
No it did not... :-( Looking at it further in my case I enabled a foreign language work around for sending. If I am lucky my signature will come across in this reply as OK.... Ok, that did not work :-( Now to try a build against the SuSE source ...
Which proves not to be necessary. After looking more closely at the files in the SuSE RPM I find enigmail is included and is current (doh!), so a bug report will probably need to be filed with Novell in first instance ....
Which is just as well as the documentation suggests it could be the compile from hell :-)
Feel free to file a descriptive bugreport at the Novell bugzilla. What I couldn't find in this thread is if - Mozilla's Thunderbird (non-RPM) with Enigmail doesn't show this issue - the openSUSE RPM with a downloaded Enigmail extension doesn't show this issue
I wouldn't expect a difference but you never know ;-)
Wolfgang
I will do this. The header of the last message from Carlos does not seem to include any Content-Transfer-Encoding info, and I suspect the problem is something to do with the handling of this info when passing the relevant parts of the message to gpg. But I think I have taken this as far as I can for the moment. The developers of enigmail for quite legitimate reasons do not offer support for distro related builds of Thunderbird. So far no-one has raised this issue with them, or made any comment here to indicate that it is more general. It will be a couple of days before I put a report together into a coherent state, (mainly because I rather hope to be at least partly incoherent this evening :-) ). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHeLwoasN0sSnLmgIRAgj8AJ4/bzypBdVgq4+VmRYaAHuBjul8dwCeIFTV e4gsxxnzWk7sIV+UwL6lnqs= =SiP1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
The header of the last message from Carlos does not seem to include any Content-Transfer-Encoding info, and I suspect the problem is something to do with the handling of this info when passing the relevant parts of the message to gpg. But I think I have taken this as far as I can for the moment.
The developers of enigmail for quite legitimate reasons do not offer support for distro related builds of Thunderbird. So far no-one has raised this issue with them, or made any comment here to indicate that it is more general.
It will be a couple of days before I put a report together into a coherent state, (mainly because I rather hope to be at least partly incoherent this evening :-) ).
My guess is that we hit https://www.mozdev.org/bugs/show_bug.cgi?id=18148 When I got a bit of time, I'll try to compile an enigmail nightly to try it. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wolfgang Rosenauer wrote:
G T Smith wrote:
The header of the last message from Carlos does not seem to include any Content-Transfer-Encoding info, and I suspect the problem is something to do with the handling of this info when passing the relevant parts of the message to gpg. But I think I have taken this as far as I can for the moment.
<snip>
My guess is that we hit https://www.mozdev.org/bugs/show_bug.cgi?id=18148
When I got a bit of time, I'll try to compile an enigmail nightly to try it.
Wolfgang
Didnt look at that one as it is flagged as Windows only.. enigmail on windows is somewhat different... but it looks like it fits... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHeM2LasN0sSnLmgIRAveaAKDBUAAGZqEdfEDaQigueAvSFOCiLwCg1WJI 8zbWcqQ+c8BlaAvS2CTy6k4= =6DhF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
G T Smith -
Thomas Hertweck -
Wolfgang Rosenauer