I added the ChromeUtils.import which is needed for EDR60 compatibility to 2.53
but won't do this for 2.49.x. Too many prerequisites. Might be all what is
needed for now unless he takes parts out of Enigmail.
FRG
David H. Durgee wrote:
Frank-Rainer Grahl wrote:
I would wait with any hasty decisions. Not sure if they will be able to
put enigmail out with TB 68. Classic add-on support is now more or less
completely trashed in the tree.
FRG
Jonathan N. Little wrote:
David E. Ross wrote:
On 2/8/2019 7:02 PM, Jonathan N. Little wrote:
NoOp wrote:
From the enigmail list:
Subject: [Enigmail] [Ann] Dropped Support for SeaMonkey
<snipped depressing news>
Crap! 20yr+ history with Seamonkey|Mozilla|Communicator and a business
mail account that requires encryption...sigh, Thunderbird...
I create my message in a text, Word, or PDF file and then encrypt it
with PGP. I attached the encrypted file to a plain-text E-mail message
that contains nothing relevant to the real message.
Different application, server generated data...
Great. I just installed Enigmail in October and now they are dropping
support. I trust they are not going to take out SeaMonkey specific
patches that are already in and simply not continue to make further changes.
Would it be possible once the dust has settled for the SeaMonkey support
team to attempt to keep the interface Enigmail uses compatible with them
as opposed to them matching with SM? Given the current situation I know
that is asking quite a bit, but then again I don't know what the future
will hold and what will be needed to do so.
Dave
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
