On 1/9/2015 7:09 PM, Rufus wrote:
Just roll back to 2.26.1...that's what I've done after testing later
releases on a single machine. Haven't seen anything fixed or working
that would make me change from it. Yet.
Security fixes would be the issues. :(
--
He was a musical ant. He was there
On 01/10/2015 02:38 AM, Ed Mullen wrote:
Philip Chee wrote on 1/9/2015 11:48 PM:
On 10/01/2015 01:46, David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab
David H. Durgee wrote:
==snipped==
Next was the problems with chase.com which is
holding me at the 2.30 level in hopes that the next release will
eliminate this problem that makes 2.31 unacceptable. How much longer
can this go on?
Dave
The chase.com problem has been fixed in the next beta:
Rufus wrote:
Ant wrote:
On 1/9/2015 7:09 PM, Rufus wrote:
Just roll back to 2.26.1...that's what I've done after testing later
releases on a single machine. Haven't seen anything fixed or working
that would make me change from it. Yet.
Security fixes would be the issues. :(
Sometimes I
Ant wrote:
On 1/9/2015 7:09 PM, Rufus wrote:
Just roll back to 2.26.1...that's what I've done after testing later
releases on a single machine. Haven't seen anything fixed or working
that would make me change from it. Yet.
Security fixes would be the issues. :(
Sometimes I wonder about
Thee Chicago Wolf [MVP] wrote:
On Fri, 09 Jan 2015 12:46:35 -0500, David H. Durgee m...@privacy.net
wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data
On 01/10/2015 10:16 AM, Rufus wrote:
Ant wrote:
On 1/9/2015 7:09 PM, Rufus wrote:
Just roll back to 2.26.1...that's what I've done after testing later
releases on a single machine. Haven't seen anything fixed or working
that would make me change from it. Yet.
Security fixes would be the
NoOp wrote:
On 01/10/2015 10:16 AM, Rufus wrote:
Ant wrote:
On 1/9/2015 7:09 PM, Rufus wrote:
Just roll back to 2.26.1...that's what I've done after testing later
releases on a single machine. Haven't seen anything fixed or working
that would make me change from it. Yet.
Security fixes
Paul in Houston, TX wrote:
Rufus wrote:
Ant wrote:
On 1/9/2015 7:09 PM, Rufus wrote:
Just roll back to 2.26.1...that's what I've done after testing later
releases on a single machine. Haven't seen anything fixed or working
that would make me change from it. Yet.
Security fixes would be
On 01/09/2015 08:44 PM, Paul in Houston, TX wrote:
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no longer being filled in
WaltS48 wrote:
On 01/09/2015 08:44 PM, Paul in Houston, TX wrote:
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
On 01/09/2015 09:46 AM, David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are
WaltS48 wrote:
On 01/09/2015 08:44 PM, Paul in Houston, TX wrote:
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
On 10/01/2015 01:56, Thee Chicago Wolf [MVP] wrote:
Are you running a different theme by chance? I found zero issues
related to Chase banking for SM but one for FF.
Bug 1094714 - Unable to login at chase.com due to NS_ERROR_FAILURE
(SeaMonkey only)
Philip Chee wrote on 1/9/2015 11:48 PM:
On 10/01/2015 01:46, David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able
On 01/09/2015 07:15 PM, Rufus wrote:
WaltS48 wrote:
On 01/09/2015 08:44 PM, Paul in Houston, TX wrote:
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab
On 10/01/2015 02:04, Jonathan N. Little wrote:
The current firefox user interface is also unacceptable to me. Is there
a way to port the seamonkey user interface in place of the firefox
interface? If so, I might give serious consideration to moving to
firefox and thunderbird in place of
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no longer being filled in
On 10/01/2015 01:46, David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no longer being filled in
On 01/09/2015 12:46 PM, David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no longer being filled in after
2.26.1 was
David H. Durgee wrote:
I am growing more and more tempted to abandon seamonkey due to the
continuing and expanding list of issues. First is the password issue
that forces me to keep a tab open to the data manager in order to be
able to copy/paste passwords that are no longer being filled in
24 matches
Mail list logo
