Re: [Enigmail] Cross-compiling on Linux for Windows [was: Compiling Enigmail: makemake - what???]

Am 30.01.2014 15:45, schrieb Patrick Brunschwig: I fixed a number of things earlier this week to support cross-compiling. If you pull the current trunk, you should be able to get a working XPI for Windows. +1 yes, I can confirm this! I

Re: [Enigmail] signing broken, sometimes

Yes PGP/MIME appears to work just fine. Also, if I change the account settings to only send plain text the thunderbird only uses the plaintext composition style and this puts line breaks as you type. So apparently there is an issue with the HTML-plaintext conversion and enigmail. I'm okay with usin

Re: [Enigmail] Cross-compiling on Linux for Windows [was: Compiling Enigmail: makemake - what???]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30.01.14 01:59, Thomas Gries wrote: > Am 27.01.2014 17:55, schrieb Patrick Brunschwig: building trunk? See >> >> >> >> >> make distclean ; ./co

Re: [Enigmail] Process details about fixing bugs and adding new features

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30.01.14 14:55, Nicolai Josuttis wrote: > Thanks Patrick, making it standalone is a HUGE step. For what it's > worth: I just compiled successfully enigmail with cygwin on my Win > 7 system and could load the resulting xpi into my Thunderbird. Goo

Re: [Enigmail] signing broken, sometimes

On 01/30/2014 09:08 AM, Nathan Andrew Fain wrote: > it appears the enigmail has issues when the text of lines will get > wrapped. What I believe is happening is that the signature is made > before the text is converted to its unformatted version and > line-wrapped. So, the signature is created on t

Re: [Enigmail] per recipient rules not in menu

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/01/14 13:57, Nicolai Josuttis wrote: > I still suggest to have this option entry enabled even without the > expert mode enabled ;-) > And I could easily push a fix/patch ;-) that would be great. It can get complex when rules clash but I don't

Re: [Enigmail] signing broken, sometimes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it appears the enigmail has issues when the text of lines will get wrapped. What I believe is happening is that the signature is made before the text is converted to its unformatted version and line-wrapped. So, the signature is created on this email b

Re: [Enigmail] per recipient rules not in menu

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I still suggest to have this option entry enabled even without the expert mode enabled ;-) And I could easily push a fix/patch ;-) Am 30.01.2014 14:29, Anna Morris schrieb/wrote: > > > On 30/01/14 13:06, Philip Jackson wrote: >> Did you check the

[Enigmail] Process details about fixing bugs and adding new features

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks Patrick, making it standalone is a HUGE step. For what it's worth: I just compiled successfully enigmail with cygwin on my Win 7 system and could load the resulting xpi into my Thunderbird. Before I start to help to fix/add issues now directl

Re: [Enigmail] per recipient rules not in menu

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/01/14 13:06, Philip Jackson wrote: > Did you check the OpenPGP/preferences in Thunderbird ? If 'Display Expert > Settings' is not selected in preferences, Thunderbird does not display the > OpenPGP/Edit per recipient rules (and others are misi

Re: [Enigmail] per recipient rules not in menu

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Did you check the OpenPGP/preferences in Thunderbird ? If 'Display Expert Settings' is not selected in preferences, Thunderbird does not display the OpenPGP/Edit per recipient rules (and others are misiing too). This is the behaviour of Thunderbird /

[Enigmail] per recipient rules not in menu

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, on my desktop the OpenPGP menu's (in Thunderbird) are a bit odd (compared to my laptop) for example "per recipient rules" is totally absent. Can't find it anywhere, the only way to access this seems to be to right-click on the email address withi

[Enigmail] signing broken, sometimes

I have a critical bug that is difficult to reproduce. Many times when I write a message and sign it the signature shows up as invalid. I copy+paste the block and check the signature with gpg from the command line and this confirms that the signature is bad for some reason. However, if I then make a