On Sunday, September 21, 2014 at 9:30:23 PM UTC+2, EE wrote:
Why is it that with SeaMonkey 2.29, the new .jsonlz4 bookmark backups
will not restore, and the manual .json backups will now not restore
either? Why change things so that backups are not restorable?
Today (10 Jan 2015) I updated
Thee Chicago Wolf (MVP) schrieb:
On Thu, 08 Jan 2015 17:56:13 -0800, NoOp gl...@sbcglobal.net.invalid
wrote:
On 01/08/2015 05:07 PM, NoOp wrote:
On 01/08/2015 10:43 AM, George wrote:
The SeaMonkey Project is pleased to announce the release of SeaMonkey
2.32b3. Please give it a spin.
https://bugzilla.mozilla.org/show_bug.cgi?id=1120067
/Philipp
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
David E. Ross wrote:
On 1/9/2015 11:58 AM, Bill Spikowski wrote:
I wonder if anyone else is experiencing trouble recently while
zooming Google Maps in Seamonkey.
In recent months I've noticed erratic zooming in Google Maps with
various browsers, but only in Seamonkey is it so pronounced as to
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
Has anyone on this list using SM successfully set up the e-mail portion of SM
with Verizon FiOS?
As I read Verizon's instructions, they specify:
Server settings:
Server Type: POP Mail Server
Server Name: pop.verizon.net Port: 995 Default 995
User Name: just your name(leave off @verizon.net)
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:
Bill Spikowski wrote:
David E. Ross wrote:
On 1/9/2015 11:58 AM, Bill Spikowski wrote:
I wonder if anyone else is experiencing trouble recently while
zooming Google Maps in Seamonkey.
In recent months I've noticed erratic zooming in Google Maps with
various browsers, but only in Seamonkey is
HenriK wrote:
Has anyone on this list using SM successfully set up the e-mail portion
of SM with Verizon FiOS?
As I read Verizon's instructions, they specify:
Server settings:
Server Type: POP Mail Server
Server Name: pop.verizon.net Port: 995 Default 995
User Name: just your name(leave off
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
Paul B. Gallagher wrote:
HenriK wrote:
Has anyone on this list using SM successfully set up the e-mail portion
of SM with Verizon FiOS?
As I read Verizon's instructions, they specify:
Server settings:
Server Type: POP Mail Server
Server Name: pop.verizon.net Port: 995 Default 995
User Name:
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
Bill Spikowski wrote:
David E. Ross wrote:
On 1/9/2015 11:58 AM, Bill Spikowski wrote:
I wonder if anyone else is experiencing trouble recently while
zooming Google Maps in Seamonkey.
In recent months I've noticed erratic zooming in Google Maps with
various browsers, but only in Seamonkey is
Jonathan N. Little wrote:
Paul B. Gallagher wrote:
The settings you describe work fine for me. They're not as secure
as they might be (other possibilities might also exist), but they
do work.
Why not as secure as they might be? Because of the normal password?
You don't need an encrypted
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
Paul B. Gallagher wrote:
Jonathan N. Little wrote:
Paul B. Gallagher wrote:
The settings you describe work fine for me. They're not as secure
as they might be (other possibilities might also exist), but they
do work.
Why not as secure as they might be? Because of the normal password?
You
On 1/9/2015 1:58 PM, Bill Spikowski wrote:
I wonder if anyone else is experiencing trouble recently while zooming
Google Maps in Seamonkey.
In recent months I've noticed erratic zooming in Google Maps with
various browsers, but only in Seamonkey is it so pronounced as to make
Google Maps
On 1/10/2015 3:13 PM, HenriK wrote:
Has anyone on this list using SM successfully set up the e-mail portion of SM
with Verizon FiOS?
As I read Verizon's instructions, they specify:
Server settings:
Server Type: POP Mail Server
Server Name: pop.verizon.net Port: 995 Default 995
User
Ed wrote:
Looks good to me. That's the way I'm set up for on FiOS.
I can offer no suggestions.
And DSL
--
Take care,
Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
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 1/9/2015 5:38 PM, David E. Ross wrote:
On 1/9/2015 11:58 AM, Bill Spikowski wrote:
I wonder if anyone else is experiencing trouble recently while
zooming Google Maps in Seamonkey.
In recent months I've noticed erratic zooming in Google Maps with
various browsers, but only in Seamonkey is
24 matches
Mail list logo
