SM locks up from FB and other sites

[Hawker]

SM 2.46 (wonder when there will be a new official release)with a very 
old profile going back to Netscape days.


I'm starting to get a lot of SM lock ups.
The biggest offender is when I am on Face Book.  SM locks up then 
eventually says


> A script on this page may be busy, or it may have stopped responding. 
You can stop the script now, open the script in the debugger, or let the 
script continue.


Only clicking stop brings me back to functioning SM.

The debugger doesn't help me much as I don't know what I am looking at.

How do I debug this? What could be the cause?

I am seeing so many recent issues I wonder if I need to start over with 
a blank profile. I just hate to loose years of tweaks to get SM the way 
I like it.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SEND MESSAGE ERROR: "Sending of the mail failed"`

[David E. Ross]

On 7/17/2017 9:53 AM, Bill Spikowski wrote:
> I'm suddenly getting this message regularly when trying to send emails from 
> my XP computer:
> 
>> Sending of the message failed.
>> The message could not be sent because the connection to Outgoing server 
>> (SMTP) mail.greenviewdata.com timed out. Try again.
> 
> Is there a way I could lengthen the 'time out' period?
> 
> The SM default time-out has always been adequate for me, going back to 
> forever, but maybe not any more!
> 
> I'm having no trouble sending out emails using my gmail account in Seamonkey 
> -- but then they show my gmail address as the sender, which I don't want 
> since I dislike gmail and almost never use it.
> 
> I've also had intermittent problems sending messages from Seamonkey in recent 
> months on my Win7 computers -- but usually I get a password dialog box; if I 
> reenter my password, the message goes out. My new problem on XP might have 
> the same cause, but without the ability to reenter my password to work around 
> it.
> 

The preference variable to control timeouts is mailnews.tcptimeout.  Try
adding the following to your user.js file in your profile:
user_pref("mailnews.tcptimeout", 210);
// set connection timeout to 3.5 minutes because of slow
// response
The "210" is the number of seconds (thus 3.5 minutes) to allow before a
timeout.  You should adjust this as necessary.  The semi-colon (;) at
the end of the first line is necessary.  The second and third lines are
merely a comment to remind you why you did this.

I had a very similar problem, but with submitting messages to a
newsgroup.  In my situation, the NNTP server was timeing-out because it
was not handling IPv6 connections well.  I tried setting
mailnews.tcptimeout to 210, but I still had frequent problems.  I added
the following to my user.js file in my profile:
user_pref("network.dns.disableIPv6", true);
// block use of IP6
This eliminated my need for setting the mailnews.tcptimeout preference
variable, which I then reverted to its default of 100 seconds.

I would not recommend setting network.dns.disableIPv6 for a profile that
is also used by the SeaMonkey browser as the number of Web sites using
IPv6 is increasing.  Instead, you might want to have a separate profile
for mail-news.  In my case, I use SeaMonkey for my browser but
Thunderbird for E-mail and newsgroups; so setting
network.dns.disableIPv6 to "true" only for mail-news was simple.

-- 
David Ross


President Trump now denies there are any tapes that
recorded his conversations with ex-FBI Director Comey.
Between when Trump hinted there might be such tapes
and his denial, there was sufficient time to destroy
any tapes.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: ESR update notification not working?

[chokito]

I check and installs always manually, have no problems.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: ESR update notification not working?

[WaltS48]

On 7/17/17 10:31 AM, chokito wrote:

Version en-US from 2017-05-28

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170528085107
SeaMonkey.exe 52.1.3.6357

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170528045907
SeaMonkey.exe 52.1.3.6357

---

Version en-US from 2017-06-19

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170619200614
SeaMonkey.exe 52.2.1.6379

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170619162041
SeaMonkey.exe 52.2.1.6379



So do Adrian's builds provide an update notification when the user uses;

a) Help > Check for updates

b) Provide a notification when the user has "Automatically check for 
update" enabled in Preferences > Advanced > Software Installation.


c) Update automatically

How did you install Version en-US from 2017-06-19?

--
Go Bucs!
Coexist 
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: ESR update notification not working?

[chokito]

Version en-US from 2017-05-28

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170528085107
SeaMonkey.exe 52.1.3.6357

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170528045907
SeaMonkey.exe 52.1.3.6357

---

Version en-US from 2017-06-19

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170619200614
SeaMonkey.exe 52.2.1.6379

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20170619162041
SeaMonkey.exe 52.2.1.6379
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seeing Photos in eMail Challenge - SM 2.46 on W10 Pro Desktop

[bo1953]

S Slicer wrote:

bo1953 wrote:

Hello all,

My challenge is that I cannot view/see photo's inline at all despite
the fact that I have 'Load All Images' checked in the security settings.

Any ideas or suggestions as to what else I can do in order to view
photos/pictures inline? Maybe something else I have setup and do not
realize.

TIA - bo1953

At the top of the SeaMonkey mail menu:  View -> Display Attachments
Inline; make sure there is a check mark next to that.


S - Thank you for your input, yes that is checked.

I appreciate your time and help.

bo1953
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Demise of Sync - alternatives?

[Andrey ``Bass'' Shcheglov]

Hello,

Using older SeaMonkey versions (e.g.: 2.7), it was possible to change
services.sync.serverURL  from
https://auth.services.mozilla.com/ to
https://pmsync.palemoon.net/sync/index.php/ and easily link SeaMonkey to
an existing Pale Moon sync account (this is how I sync my Debian IceApe
(rebranded SM 2.7) with Pale Moon).

It doesn't seem possible any more with modern SM versions: when I choose
"I already have a SeaMonkey Sync" account, enter the username, password
and recovery key and press "Next" -- nothing happens (no change of the
UI, no error message, no HTTP(S) packets sent to pmsync.palemoon.net).

It still should be possible to set up Sync (v1.1) by setting some extra
preferences in about:config, omitting the Sync UI, but I have had no
success so far.

Regards,
Andrey.

On 15.07.2017 0:15, Frank-Rainer Grahl wrote:
> Sync 1.5 has not been ported yet and with all the crap going on with Fx
> I am not sure it is a good idea anyway. You need a Firefox account and
> everything is tightly coupled to Mozilla. So no for official sync. You
> could probably still set up your own Sync 1.1 server in 2.46 to 2.49 as
> mentioned but the old 1.1 code has been removed by Mozilla from the
> backend too in the latest nightly releases.
> 
> In the long term we need to provide our own sync servers and make
> something work but for now don't hold your breath.
> 
> FRG
> 
> Saptarshi Roy wrote:
>> On Monday, 12 October 2015 19:31:54 UTC+5:30, Bill Spikowski  wrote:
>>> Sync 1.1 no longer works, as Mozilla has shut down their sync server.
>>>
>>> Is updating Seamonkey to use Mozilla's new sync server something
>>> that's in the works and might be expected soon (say, the next month,
>>> rather than next year or not at all)?
>>>
>>> Thomas Rocek recently posted the instructions for setting up a new
>>> Sync 1.1 server, but they're way beyond my tech abilities. Is anyone
>>> aware of a publicly available Sync 1.1 method that Seamonkey users
>>> could rely on for the duration?
>>
>> Is there a way to create a Seamonkey sync account in the latest build?
>>
> 
> ___
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey



smime.p7s
Description: S/MIME Cryptographic Signature
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey