Re: Browser: unwanted https instead of http

2016-10-11 Thread Paul B. Gallagher 

Rainer Bielefeld wrote:


Hi,

on some (few) web pages I can not reach the linked contents because my
unofficial en-US SeaMonkey 2.49a1  (NT 6.1; WOW64; rv:52.0)
Gecko/20100101 Firefox/52.0 Build 20160930004545  (Default Classic
Theme) on German WIN7 64bit with my normal User Profile automatically
replaces "http" in URL by "https".

Example:
1. In Browser visit 
2. In page contents heading line
ˋclick downloads - Firmwareˊ
Expected:  opens
Actual:    will
  not open because it does not exist. So Error 404.

I see that after a short moment in URL bar "http" becomes replaced by
"https"


Unable to reproduce. I just get the requested directory of downloadable 
files. Waited 13 minutes, no switch to https.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

Re: Seamonkey release?

2016-10-11 Thread sean . nathan 

Stephan Thiele wrote:

Sorry if this is a stupid question, but I don't really understand why
there still is no Seamonkey update after the 2.40 release in March,
almost half a year ago.
I am quite confused that there a nightlies with version numbers
increasing to 2.48 while there is not even a beta.
Seamonkey is my default browser and mail and news program, so I don't
like to take any risk of losing my data and mails by using a buggy
nightly. On the other hand, I see a lot of security updates of Firefox
and Thunderbird which have been published in the meantime and therefore
I'm concerned about unfixed vulnerabilities in Seamonkey.

Any hope?


I'm a dedicated PeppermintOS Linux user... Anyone else find a newer than 
2.40 that works well on Linux Mint based distributions?


sean
--
tagzilla... such memories...



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

Re: Browser: unwanted https instead of http

2016-10-11 Thread Bret Busby 
On 12/10/2016, Rainer Bielefeld  wrote:
> Hi,
>
> on some (few) web pages I can not reach the linked contents because my
> unofficial en-US SeaMonkey 2.49a1  (NT 6.1; WOW64; rv:52.0)
> Gecko/20100101 Firefox/52.0 Build 20160930004545  (Default Classic
> Theme) on German WIN7 64bit with my normal User Profile automatically
> replaces "http" in URL by "https".
>
> Example:
> 1. In Browser visit 
> 2. In page contents heading line
>ˋclick downloads - Firmwareˊ
>Expected:  opens
>Actual:    will
>  not open because it does not exist. So Error 404.
>
> I see that after a short moment in URL bar "http" becomes replaced by
> "https"
>
> This also happens in Safe Mode without add-ons
> No problem in a newly created User Profile.
> So this problem seems to be caused by my preferences, but I can't find
> the responsible one.
>
> Any ideas?
>
> Best Regards
>
> Rainer
> ___
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey
>


Hello.

It is my understanding, and, I accept correction, if I am wrong, that
many web sites have been changed to https, for the sake of web site
security; to try to prevent their web sites from being breached and
malicious material being inserted on their web sites.

From what I understand, the changing to https, has nothing to do with
the web browser being used (although, I have found that some of the
web browsers that I use, have problems with https, or, with some https
web sites), but, is instead, solely the intent of the web site
developers and maintainers.

As I stated, I stand to be corrected, if I am wrong.

-- 

Bret Busby
Armadale
West Australia

..

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992


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

Browser: unwanted https instead of http

2016-10-11 Thread Rainer Bielefeld 
Hi,

on some (few) web pages I can not reach the linked contents because my
unofficial en-US SeaMonkey 2.49a1  (NT 6.1; WOW64; rv:52.0)
Gecko/20100101 Firefox/52.0 Build 20160930004545  (Default Classic
Theme) on German WIN7 64bit with my normal User Profile automatically
replaces "http" in URL by "https".

Example:
1. In Browser visit 
2. In page contents heading line
   ˋclick downloads - Firmwareˊ
   Expected:  opens
   Actual:    will
 not open because it does not exist. So Error 404.

I see that after a short moment in URL bar "http" becomes replaced by
"https"

This also happens in Safe Mode without add-ons
No problem in a newly created User Profile.
So this problem seems to be caused by my preferences, but I can't find
the responsible one.

Any ideas?

Best Regards

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

Re: 2.46 updates?

2016-10-11 Thread NoOp 
On 10/11/2016 07:23 PM, NoOp wrote:
> On 10/11/2016 4:42 PM, WaltS48 wrote:
>> On 10/11/2016 07:10 PM, NoOp wrote:
>>> I just received update notices for 2.46 (Windows and linux) on the
>>> system that I have 2.46 running. (Note: I do not get a notice on those
>>> that are still running 2.40). Here is what I get for the upgraded 2.46:
>>> 
>>> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
>>> Firefox/49.0 SeaMonkey/2.46
>>> Build identifier: 20160922144825
>>> 
>>> and
>>> 
>>> User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
>>> Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
>>> Build identifier: 20160922153204
>>> 
>>> Anyone else (that are already running 2.46) get the same?
>>> 
>> 
>> 
>> Nope, but I installed build6 from 
>> 
>> 
>> Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 
>> SeaMonkey/2.46 BuildID: 20161005013219
>> 
> 
> Mine are from:
> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-linux64/
> and I don't see that they're updated beyond 09/22:
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
> Firefox/49.0 SeaMonkey/2.46
> Build identifier: 2016092214482
> 
> Unfortunately I wasn't paying much attention when I updated (baseball
> playoffs & cooking)... but update history from
> 'Help|Troubleshooting|Show Update History' shows on the Win10 shows:
> 
> SeaMonkey 2.46 (20160922153204)
> Security Update
> Installed on: Tuesday, October 11, 2016 3:40:50 PM
> Status: The Update was successfully installed
> 
> and now it is showing (after restart):
> 
> User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
> Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
> Build identifier: 20160922153204
> 
> 
and now on linux:

SeaMonkey 2.46 (20160922144825)
Security Update
Installed on: Tue 11 Oct 2016 P03:33:11 PM PDT
Status: The Update was successfully installed

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160922144825


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

Re: 2.46 updates?

2016-10-11 Thread NoOp 
On 10/11/2016 4:42 PM, WaltS48 wrote:
> On 10/11/2016 07:10 PM, NoOp wrote:
>> I just received update notices for 2.46 (Windows and linux) on the
>> system that I have 2.46 running. (Note: I do not get a notice on those
>> that are still running 2.40). Here is what I get for the upgraded 2.46:
>> 
>> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
>> Firefox/49.0 SeaMonkey/2.46
>> Build identifier: 20160922144825
>> 
>> and
>> 
>> User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
>> Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
>> Build identifier: 20160922153204
>> 
>> Anyone else (that are already running 2.46) get the same?
>> 
> 
> 
> Nope, but I installed build6 from 
> 
> 
> Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 
> SeaMonkey/2.46 BuildID: 20161005013219
> 

Mine are from:
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-linux64/
and I don't see that they're updated beyond 09/22:
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46
Build identifier: 2016092214482

Unfortunately I wasn't paying much attention when I updated (baseball
playoffs & cooking)... but update history from
'Help|Troubleshooting|Show Update History' shows on the Win10 shows:

SeaMonkey 2.46 (20160922153204)
Security Update
Installed on: Tuesday, October 11, 2016 3:40:50 PM
Status: The Update was successfully installed

and now it is showing (after restart):

User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160922153204


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

Re: 2.46 updates?

2016-10-11 Thread WaltS48 

On 10/11/2016 07:10 PM, NoOp wrote:

I just received update notices for 2.46 (Windows and linux) on the
system that I have 2.46 running. (Note: I do not get a notice on those
that are still running 2.40). Here is what I get for the upgraded 2.46:

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160922144825

and

User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160922153204

Anyone else (that are already running 2.46) get the same?




Nope, but I installed build6 from 



Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 
SeaMonkey/2.46 BuildID: 20161005013219


--
Visit Pittsburgh 
Ubuntu 16.04.1 LTS
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

2.46 updates?

2016-10-11 Thread NoOp 
I just received update notices for 2.46 (Windows and linux) on the
system that I have 2.46 running. (Note: I do not get a notice on those
that are still running 2.40). Here is what I get for the upgraded 2.46:

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160922144825

and

User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:49.0)
Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
Build identifier: 20160922153204

Anyone else (that are already running 2.46) get the same?

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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread Alexander Yudenitsch 

mozilla-lists.mbou...@spamgourmet.com wrote, on 11 Oct 16 17:30:


Alexander Yudenitsch wrote:


A happy coincidence that you decided to do so, since I already had
the intention of writing you, to ask for details about your migration
of SM from XP to W7 -- but let's leave that for a little later, OK?


I distinctly remember someone on this forum commenting on how he (yes,
it was a 'he', AFAIK) had migrated a profile from XP to W7, and I
thought that was you; well, apparently not...  I did try to find that
message among the hundreds of the 'current' batch but, not remembering
what was the 'nominal' subject, I guess its hopeless.


You can search the archives from this list via Google Groups at
.


Thanks, but I avoid Google Groups if I can; I have signed into them out 
of necessity, but I imagine I'd have to sign onto this group in order to 
do a search, and I prefer not to do that.



A couple of recent threads involving moving profiles around are
titled "If I remplace the directory
C:\Users\RZ\AppData\Roaming\Mozilla\SeaMonkey" and "Installing SM
2.40 and Relations To Different Drive". You may also want to take a
look at .


Thanks, again!  I did look around a little, and had seen those threads 
also (and one of them was the one I was referring to, in the text quoted 
above)



If you have queries about migrating your SeaMonkey profile from one OS
to another, the best thing is to create a new message addressed to this
list / newsgroup with an appropriate subject line. Don't reply to a
message from this thread about a different problem, as some people
ignore threads about things they can't help with or aren't interested
in, so those who might be able to help with that different problem might
not see a reply to a message in this thread.


Of course!  Notice that I did say to Paul: "let's leave that for a 
little later", because I do have the intention of opening another thread 
for that.  I just commented on that because I thought he was the one who 
had written the messages I had seen about the migration, and thought it 
was a coincidence that he was the first one to reply.


In fact, my query has two 'prongs':  Migrating SM from WinXP to Win7, 
and saving information from a previous profile to a new one (which I'm 
sure is a devious and tricky one, since I'm after specific details, and 
not generic advice, and realize there may not be anyone with such advice 
available here when I write).


--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread Alexander Yudenitsch 

mozilla-lists.mbou...@spamgourmet.com wrote, on 11 Oct 16 18:52:


... the main point would be that SM seems to open or show messages
using the 'last-used' text encoding, not the one specified in the
e-mail's properties (which, IMHO, should be considered a bug).


I agree this doesn't seem right. It's been a minor annoyance for me for
a while, and I keep meaning to look into it a bit more and file a bug
report. I've managed to produce a couple of example messages and
reproduce the use of incorrect encodings when opening them, including
corrupting a draft message.

I'm out of time tonight, but hopefully will be able to file a bug report
tomorrow...


From what I've seen in this forum, filing a bug report may be useful 
for SM development, but is unlikely to bring quick results, since the 
devs have so much more, and more important, things to attend to (and I 
do appreciate and thank them all for their efforts and helpfulness).


If that's true, filing a bug report would definitely be a good thing, 
but personally I'll have to concentrate on workarounds (or process 
steps) which will allow me to no longer have this problem in the 
immediate future.


As I said, I'm currently migrating to a XP/7 dual-boot system, so I 
can't concentrate on that, but all the comments and suggestions given 
here so far have indicated several things I can try out without too much 
effort/time; what I'm still unsure of is how I should define all those 
variables in SM/Mail involving text encoding and fonts in a coherent 
manner, adequate to a multi-language mail 'system'...


--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread Alexander Yudenitsch 

mozilla-lists.mbou...@spamgourmet.com wrote, on 11 Oct 16 17:14:


That also affects opening previously saved drafts. So, for example:
- Start composing a message with UTF-8 encoding (like Paul, that's my
default) and include a character not covered by the standard ASCII set
(in my case, usually "£")  ...


Interesting. What you call "standard ASCII" is what we used to call
"high ASCII."


By "standard ASCII", I meant the first 128 characters. "£" is one of the
extended characters in some charsets. In UTF-8, it's encoded as a
two-byte sequence. Hence when an email containing "£" encoded in UTF-8
is decoded using an extended ASCII charset, it appears as two separate
characters.


The first 128 characters (up to ... xyz{|}~€  in Windows
Character Map) are the most basic, and the last 127 (beginning with
‚ƒ„…†‡ˆ‰Š‹ŒŽ) sometimes cause trouble. The high ASCII set also
includes the accented Western characters mentioned by the OP, such as
àáâãäåæçèéê..., but not Eastern European characters such as ăĺčďů.


The exact characters included in the high/extended ASCII range depend on
the particular character set being used. The one you use may include /
not include those characters, but another might. There's not one single
extended ASCII charset but several, each with an emphasis on particular
languages or regions, including the characters needed for those
languages in its extended range.


At any rate, if high ASCII is causing problems, that suggests that SM is
trying for some reason to make do with a seven-bit encoding instead of
eight bits.


It's not extended characters as such that causes a problem, but emails
being decoded using the wrong character set. The 128 standard ASCII
characters are encoded the same in all extended ASCII-based charsets and
also in UTF-8, so for those of us in Western countries, using the wrong
encoding generally isn't noticeable except for the odd character outside
the standard ASCII ranges.


That was educational (or memory-stirring, since I had read about all 
that a long time ago) for me:  It seems that the problem might lie in 
the extended ASCII characters used for pt-BR text, which (since SM 
doesn't have any place to specify that particular language) might mean 
it tries to use an inappropriate one (if that's what you meant by 
"There's not one single extended ASCII charset but several, each with an 
emphasis on particular languages or regions, including the characters 
needed for those languages in its extended range.")


It might also answer another query I raised recently in this thread:


"Western" characters -- but what's that:  Is that an euphemism for
"English"?  Portuguese, Spanish, French, all use "Western
characters", IMHO; but I suspect the former (ie, "Western")
actually means "English"...


I had thought that, in SM/Mail, there were basically 3 text encoding 
options: English (called "Western"); Unicode; and 'other languages'. 
For many years, I used 'Western' but, as it seemed more and more 
messages used Unicode, switched to it (this was at the same time as the 
'drafts gibberish' problem started to become more annoying), thinking 
that Unicode (is that the same as UTF-8?), at least, should be 
"universal"...


Discounting the cases where one opens a message with the wrong encoding 
(which is easy to identify since, in such cases, re-opening the message 
with the correct encoding makes the problem go away), it seems this 
problem (which I described with the Drafts) only appears when a message 
mixes extended ASCII characters with lots of standard ASCII ones (would 
you say that's a correct way of putting it?).



--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread mozilla-lists . mbourne 

Alexander Yudenitsch wrote:

mozilla-lists.mbou...@spamgourmet.com wrote, on 10 Oct 16 15:48:


Paul B. Gallagher wrote:

I have noticed that sometimes SM will guess wrong when I select a
message in a mail folder, but if I navigate away and then return it'll
guess right. I don't know why that is -- it seems to be sticking to the
encoding it used for the previous message that I just deleted.


I've noticed that too, and it may be the root of Alexandre's problem. It
seems that SeaMonkey correctly detects the encoding when opening
messages in the "message pane", but doesn't actually use that encoding
until the next message is opened, and doesn't detect the encoding at all
when opening them in a separate window (just using the last-detected
encoding from the message pane).

That also affects opening previously saved drafts. So, for example:
- Start composing a message with UTF-8 encoding (like Paul, that's my
default) and include a character not covered by the standard ASCII set
(in my case, usually "£")
- Save as draft and close that message.
- View, in the message pane (View > Layout > Message Pane or press F8),
another email which uses a different encoding (e.g. us-ascii)
- Re-open the draft
- The "£" now appears as "£" (it just happens that in this case the
second character is the same as the original single character, but
that's not necessarily the case for all characters)

No amount of closing and re-opening the draft seems to fix that. However:
- Select the draft in the thread pane
- Open the message pane (View > Layout > Message Pane or press F8)
- It looks wrong there too, and saving the draft again at this point
will compound the problem. However...
- Close the message pane
- Open the message pane
- It now looks correct, and double-clicking to open the message for
further editing is now also correct.

To be honest, I've got to the point where I barely notice this and just
automatically tap F8 a couple of times when a message isn't displayed
correctly. That it's become an automatic reaction isn't a particularly
good sign, but that may be a workaround until the problem is fixed
properly.

I think this has come up on this list before, but not sure it's reported
on Bugzilla.


Sounds like potentially good news, and thanks!

Since I never use the 'message pane', but always open e-mails (including
drafts) in their own windows, I think the problem may be a little more
'widespread' than that


That's possible. I've been able to reliably reproduce by toggling the 
message pane, but I can believe there may be other ways leading to the 
wrong encodings being used. Maybe when messages are deleted, or perhaps 
when a new message is displayed in the same window (using next/previous)...



-- but the main point would be that SM seems to
open or show messages using the 'last-used' text encoding, not the one
specified in the e-mail's properties (which, IMHO, should be considered
a bug).


I agree this doesn't seem right. It's been a minor annoyance for me for 
a while, and I keep meaning to look into it a bit more and file a bug 
report. I've managed to produce a couple of example messages and 
reproduce the use of incorrect encodings when opening them, including 
corrupting a draft message.


I'm out of time tonight, but hopefully will be able to file a bug report 
tomorrow...


--
Mark.

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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread mozilla-lists . mbourne 

Alexander Yudenitsch wrote:

BTW, before I forget:  It's been a few years since SM started opening
that 'message pane' when you classify a message as "Junk"; it wasn't
that way earlier, and I don't see any way to turn that behavior off!
Does anyone know some way to do that?


That one looks like bug 986874 
. I don't think 
it's an intentional behaviour which would be turned off by an option.


--
Mark.

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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread mozilla-lists . mbourne 

Alexander Yudenitsch wrote:

Paul B. Gallagher wrote, on 10 out 16 17:49:


Alexander Yudenitsch wrote:


A happy coincidence that you decided to do so, since I already had
the intention of writing you, to ask for details about your migration
of SM from XP to W7 -- but let's leave that for a little later, OK?


I can't promise to remember the details of what I did so long ago...

IIRC, I upgraded the OS from XP to Win2000 while SM was already
installed, and it just ran without further action on my part. And then I
did the same thing again when going from Win2000 to Win7.

But don't quote me -- it's been over a decade, and I can't swear that
I'm reembering correctly.


I distinctly remember someone on this forum commenting on how he (yes,
it was a 'he', AFAIK) had migrated a profile from XP to W7, and I
thought that was you; well, apparently not...  I did try to find that
message among the hundreds of the 'current' batch but, not remembering
what was the 'nominal' subject, I guess its hopeless.


You can search the archives from this list via Google Groups at 
. A couple of 
recent threads involving moving profiles around are titled "If I 
remplace the directory C:\Users\RZ\AppData\Roaming\Mozilla\SeaMonkey" 
and "Installing SM 2.40 and Relations To Different Drive". You may also 
want to take a look at 
.


If you have queries about migrating your SeaMonkey profile from one OS 
to another, the best thing is to create a new message addressed to this 
list / newsgroup with an appropriate subject line. Don't reply to a 
message from this thread about a different problem, as some people 
ignore threads about things they can't help with or aren't interested 
in, so those who might be able to help with that different problem might 
not see a reply to a message in this thread.


--
Mark.

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

Re: View Selection Source Fails in SeaMonkey 2.40

2016-10-11 Thread EE 

Ray_Net wrote:

What happens about a possible solution for :
"View Selection Source Fails in SeaMonkey 2.40"

I had a very bad idea coming from 2.38 to 2.40 :-(

Now I am at:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40


That is fixed in SeaMonkey 2.45 and 2.46.  I have been using Tinderbox 
comm-release builds for awhile because I got tired of waiting for the 
next official release to come out.


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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread mozilla-lists . mbourne 

Paul B. Gallagher wrote:

mozilla-lists.mbou...@spamgourmet.com wrote:


Paul B. Gallagher wrote:

I have noticed that sometimes SM will guess wrong when I select a
message in a mail folder, but if I navigate away and then return it'll
guess right. I don't know why that is -- it seems to be sticking to the
encoding it used for the previous message that I just deleted.


I've noticed that too, and it may be the root of Alexandre's problem. It
seems that SeaMonkey correctly detects the encoding when opening
messages in the "message pane", but doesn't actually use that encoding
until the next message is opened, and doesn't detect the encoding at all
when opening them in a separate window (just using the last-detected
encoding from the message pane).

That also affects opening previously saved drafts. So, for example:
- Start composing a message with UTF-8 encoding (like Paul, that's my
default) and include a character not covered by the standard ASCII set
(in my case, usually "£")  ...


Interesting. What you call "standard ASCII" is what we used to call
"high ASCII."


By "standard ASCII", I meant the first 128 characters. "£" is one of the 
extended characters in some charsets. In UTF-8, it's encoded as a 
two-byte sequence. Hence when an email containing "£" encoded in UTF-8 
is decoded using an extended ASCII charset, it appears as two separate 
characters.



The first 128 characters (up to ... xyz{|}~€  in Windows
Character Map) are the most basic, and the last 127 (beginning with
‚ƒ„…†‡ˆ‰Š‹ŒŽ) sometimes cause trouble. The high ASCII set also
includes the accented Western characters mentioned by the OP, such as
àáâãäåæçèéê..., but not Eastern European characters such as ăĺčďů.


The exact characters included in the high/extended ASCII range depend on 
the particular character set being used. The one you use may include / 
not include those characters, but another might. There's not one single 
extended ASCII charset but several, each with an emphasis on particular 
languages or regions, including the characters needed for those 
languages in its extended range.



At any rate, if high ASCII is causing problems, that suggests that SM is
trying for some reason to make do with a seven-bit encoding instead of
eight bits.


It's not extended characters as such that causes a problem, but emails 
being decoded using the wrong character set. The 128 standard ASCII 
characters are encoded the same in all extended ASCII-based charsets and 
also in UTF-8, so for those of us in Western countries, using the wrong 
encoding generally isn't noticeable except for the odd character outside 
the standard ASCII ranges.


--
Mark.

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

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread Alexander Yudenitsch 

Paul B. Gallagher wrote, on 11 Oct 16 04:10:


If I were only getting 20 messages a day, I might try your way. As it
happens, I routinely get over a hundred, sometimes 200, so filtering to
appropriate folders is a great time saver. If messages 3, 28, 47, and 96
relate to the same topic, it's much easier to see all four in the same
folder and read them together than to try to keep several dozen threads
in my head all at the same time as I work through an unsorted inbox.

I also get client requests referring to old jobs, some of them a year or
two old, and I have to be able to find the old correspondence quickly
and easily. I probably have a hundred thousand old messages going back
to the late 90s, and the only way I can cope is with a good filing system.


Yeah, "You can't really understand another person's experience until 
you've walked a mile in their shoes" (and, by then, you're a mile away, 
and you have their shoes...  :-))


I guess that, on average, I must get 50 messages a day, but most of them 
are very quickly and easily taken care of every day using an e-mails 
folders structure adequate to my needs and SM's spam/junk filters and 
Boolean search (which, BTW, is unparalleled, at least for me:  I've 
never seen any e-mail client with search capabilities even close to 
these!); I imagine that, if I got 100-200/day, maybe I'd start using 
folder filtering, too...


BTW, I just remembered that I do use folder filtering, but on my e-mail 
service (fastmail.fm):  Many years ago, I wrote a filtering script so 
that e-mails sent to that address would be sent to my SM client, with a 
copy in their 'junk' files, and those sent to an alternate address, on 
another service, would be automatically retrieved and go to a specific 
folder there, keeping the original on that other service -- but it has 
been so long that that's all I remember, and probably I wouldn't be able 
to even understand that script if I wanted to change it, these days.


Finally, a 'kindred soul':  I also keep many messages since the '90s 
(starting with a few from CompuServe!), and am only able to do that 
because of the aforementioned e-mails folders structure and SM's Boolean 
search capabilities.  Most people I know delete 99% of their e-mails 
soon after reading them (or even before that  :-)); besides sometimes 
having a need to get back to earlier info and texts, one of my intents 
is being able to  avoid 'reinventing the wheel':  If I already wrote 
extensively about something I have to write again today, why not re-use 
the previous text, with adequate changes?


--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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

Re: Installing SM 2.40 and Relations To Different Drive.... *Resolved*

2016-10-11 Thread Ray_Net 

SamuelS wrote on 11/10/2016 01:20:

Ray_Net wrote:

SamuelS wrote on 09/10/2016 14:04:

SamuelS wrote:
Hello all, just received my new system, suffice it to say the 
company that made it for me, did what they wanted to do and not 
what I requested...


I had my SM program on W10 pro on drive e: I have tried to 
re-install on drive e: and the message:


Your Seamonkey profile cannot be loaded. It cannot be found or is 
corrupted. (or something to this effect)


Thoughts on what my issue is on this?

TIA - bo1953

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Hello all,

Dumb me, last night tried to re-install SM 2.40 on my W10 machine as 
desired c: drive and I receive the same message as above...


Now this is very confounding. I have tried installing as Admin, etc...

So SM is not installing at all on any drive, so far.

I only transferred my SSD's and HD's to the new system. I expected 
some re-installation but nothing like this, so far. My focal point 
is getting SM installed and getting emails then the rest to follow.



You give us NO DETAILS ... this is my details:
The SeaMonkey profile is for my windows7 pc at:
C:\Users\RZ\AppData\Roaming\Mozilla\SeaMonkey\
where I can see:
- The "profile.ini" file
- The "Crash Reports" directory
- The "Profiles" directory
-- under the "profiles" directory I can see:
  - The "ey8r9gln.default" directory who contains all the profile.

I then just have a new pc With Windows 10 Pro 64 bits.
I just copy C:\Users\RZ\AppData\Roaming\Mozilla\SeaMonkey\*.*
From my C: Drive of my Windows7 pc
AS C:\Users\RAY\AppData\Roaming\Mozilla\SeaMonkey\*.*
To my C: Drive of my new Windows10 pc

RZ is my pc-username of my Windows7 pc
and RAY is my pc-username of my Windows10 pc

THEN I install SM on my Windows10 pc
And all goes well 

SM was and is installed on W7 and on W10 at default locations.

Hello all,

I found it to be more time efficient to create new profiles.

I could not even get MozBackup to work on the new system, S, 
instead of fighting it, I just kissed it all good bye and started from 
scratch...


Thank you all for your input and thoughts on this.

Warmest regards,

bo1953

You don't need MozBackup, you can just copy the profile to your new 
machine then install SM as I explained you.

So simple like that :-)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread Paul B. Gallagher 

Alexander Yudenitsch wrote:


Paul B. Gallagher wrote, on 11 Oct 16 00:35:


In the same way, I do want SM to move junk messages to the Junk
folder, which then lights up in bold to remind me to check them. In
most cases, I can take one look at the subject line and agree that
it's junk -- if I've just inherited $23 million from some Nigerian
prince, or gained the opportunity to improve my size and
performance, I don't have to open it.


Once more, I think our intents are the same, but we go about them in
different ways: The "one look" you described is the same I take to
decide if something should be (there is no "is", here, just a "should
be", IMHO) classified as junk/spam, bank/personal/etc. and so on --
only I prefer to do that, several times a day, in the Inbox (which,
with this procedure, never has more than 20 items in it at any given
time), and you let SM place the messages in folders, and then look at
them there (we both use the 'bold=unread' feature, too.


If I were only getting 20 messages a day, I might try your way. As it 
happens, I routinely get over a hundred, sometimes 200, so filtering to 
appropriate folders is a great time saver. If messages 3, 28, 47, and 96 
relate to the same topic, it's much easier to see all four in the same 
folder and read them together than to try to keep several dozen threads 
in my head all at the same time as I work through an unsorted inbox.


I also get client requests referring to old jobs, some of them a year or 
two old, and I have to be able to find the old correspondence quickly 
and easily. I probably have a hundred thousand old messages going back 
to the late 90s, and the only way I can cope is with a good filing system.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Mail and text encoding

2016-10-11 Thread Alexander Yudenitsch 

Paul B. Gallagher wrote, on 11 Oct 16 00:35:


The usual point of filters (not the same as Junk Mail Control) is...


I used "filtering' in a general sense:  After all, analyzing a message 
and deciding it's junk/spam and/or from your brother is, basically the 
same function.  I _am_ familiar with the idea of filters...:



... to move incoming messages to appropriate folders. So messages
from my bank go in my bank's folder, messages from my accountant go
in my accountant's folder, messages from my brother go in my Personal
folder, etc. I don't clog up my Inbox by letting everything stay
there and moving it manually. And I can see at a glance where the new
messages are because any folder name with unread messages is shown in
bold.

In the same way, I do want SM to move junk messages to the Junk folder,
which then lights up in bold to remind me to check them. In most cases,
I can take one look at the subject line and agree that it's junk -- if
I've just inherited $23 million from some Nigerian prince, or gained the
opportunity to improve my size and performance, I don't have to open it.


Once more, I think our intents are the same, but we go about them in 
different ways: The "one look" you described is the same I take to 
decide if something should be (there is no "is", here, just a "should 
be", IMHO) classified as junk/spam, bank/personal/etc. and so on -- only 
I prefer to do that, several times a day, in the Inbox (which, with this 
procedure, never has more than 20 items in it at any given time), and 
you let SM place the messages in folders, and then look at them there 
(we both use the 'bold=unread' feature, too.



But for those that I do want to inspect, I open them with one crucial
setting:
 Edit | Preferences | Mail & Newsgroups | Message Display
 ...
 [x] Block images and other content from remote sources.

This way, the message doesn't "phone home" for a web beacon to notify
the spammer that I've opened the message.


I do have that set, but I still prefer to examine the 5% or so 
'suspicious' messages by looking at the source, since I imagine here 
might be some new technique whereby a hacker can circumvent this setting 
-- and learning about it after some dastardly deed has been done is 
small comfort.



Of course, you'll also want to set SM not to run scripts and plugins in
mail messages:
 Edit | Preferences | Advanced | Scripts & Plugins
 Enable plugins for [ ] Mail & Newsgroups
(JavaScript is disabled by default for the "Mail & Newsgroups"
component, for security reason.)


Yes, that's set too.  As I said, I think we have similar strategies, but 
differ in some tactics...


--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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