Re: How to print out Passwords from "Saved Logins" Plugin ?

[DoctorBill]

David E. Ross wrote:

On 1/7/2018 7:19 PM, DoctorBill wrote:

I have "Saved Passwords" plugin (?) or extension (?) and can
show all of them onscreen.

I highlighted them Ctrl + C, but apparently it did not go to
the clipboard memory since I cannot Ctrl+V them onto a
word processor page.

Does someone know where the files is saved to ?
It says at the top they are stored on my computer (? where else
would they be stored ?) !

I was able to 'Screensave' the whole thing in three jpg files,
but I'd rather treat them as a wrd file..

DoctorBill



Have you considered Password Exporter?  It can output all of your
passwords together as a csv (comma-separated values) file, which can
then be opened and printed as a spreadsheet with Excel.



Just downloaded it...

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

Re: How to print out Passwords from "Saved Logins" Plugin ?

[David E. Ross]

On 1/7/2018 7:19 PM, DoctorBill wrote:
> I have "Saved Passwords" plugin (?) or extension (?) and can
> show all of them onscreen.
> 
> I highlighted them Ctrl + C, but apparently it did not go to
> the clipboard memory since I cannot Ctrl+V them onto a
> word processor page.
> 
> Does someone know where the files is saved to ?
> It says at the top they are stored on my computer (? where else
> would they be stored ?) !
> 
> I was able to 'Screensave' the whole thing in three jpg files,
> but I'd rather treat them as a wrd file..
> 
> DoctorBill
> 

Have you considered Password Exporter?  It can output all of your
passwords together as a csv (comma-separated values) file, which can
then be opened and printed as a spreadsheet with Excel.

-- 
David E. Ross


President Trump:  Please stop using Twitter.  We need
to hear your voice and see you talking.  We need to know
when your message is really your own and not your attorney's.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: How to print out Passwords from "Saved Logins" Plugin ?

[NoOp]

On 1/7/2018 7:19 PM, DoctorBill wrote:
> I have "Saved Passwords" plugin (?) or extension (?) and can
> show all of them onscreen.
> 
> I highlighted them Ctrl + C, but apparently it did not go to
> the clipboard memory since I cannot Ctrl+V them onto a
> word processor page.
> 
> Does someone know where the files is saved to ?
> It says at the top they are stored on my computer (? where else
> would they be stored ?) !
> 
> I was able to 'Screensave' the whole thing in three jpg files,
> but I'd rather treat them as a wrd file..
> 
> DoctorBill
> 


https://addons.mozilla.org/en-US/thunderbird/addon/password-exporter/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

How to print out Passwords from "Saved Logins" Plugin ?

[DoctorBill]

I have "Saved Passwords" plugin (?) or extension (?) and can
show all of them onscreen.

I highlighted them Ctrl + C, but apparently it did not go to
the clipboard memory since I cannot Ctrl+V them onto a
word processor page.

Does someone know where the files is saved to ?
It says at the top they are stored on my computer (? where else
would they be stored ?) !

I was able to 'Screensave' the whole thing in three jpg files,
but I'd rather treat them as a wrd file..

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

I want to express my appreciation for your help !

[DoctorBill]

I posted the Message titled "E-Mail Providers" and that became one huge 
maggilah !
I am adding THIS just because it would become one tree in a vast forest 
if I posted

it in the original thread.

I understood about 5% of the replies (that is being generous!) due to 
all the Jargon
required to set up the E-Mail "System" in SeaMonkey for other than your 
own ISP.


I tried what was in the replies - as far as I could understand it !
It is amazing just how COMPLEX the world of the Internet is becoming !
There is an old SiFi story called "The Machine Stops".I think it 
applies to our present and

future world.  If the machine stops - God Help us !

Anyway - finally my E-Mail works - but I am afraid to even touch it 
further for

fear of making it stop working..

But - I wanted to express my THANKS to all who tried to help me !
Which one of you helped me is completely obscure, but thanks to ALL of you !

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

Re: Spectre exploit

[Lee]

On 1/7/18, Ray_Net  wrote:
> Lee wrote on 07-01-18 22:44:
>> summary: The vuln. mitigation is to install noscript + request policy
>> continued or uMatrix + uBlock Origin or whatever other addon combo
>> that allows javascript from only whitelisted sites.
>>
>> On 1/7/18, Ray_Net  wrote:
>>> WaltS48 wrote on 06-01-18 18:05:
 On 1/6/18 2:36 AM, Ray_Net wrote:
> I have read:
>
> "Disable Javascript until browser company comes out with patch for
> vulnerable Javascript."
>
> So, will SM issue a patch against the Spectre exploit ?
>> Mozilla needs to come up with a patch first.  What they have now only
>> blocks the obvious timing attack methods.
>>
 SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
 doesn't have SharedBufferArray enabled.
 ||
 ||SharedArrayBuffer| is already disabled in Firefox 52 ESR.
 ||
 |REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/

>>> Would it mean that we are protected ?
>> No.
>>
>> Look at the FF advisory
>>The precision of performance.now() has been reduced from 5μs to
>> 20μs, and the SharedArrayBuffer feature has been disabled because it
>> can be used to construct a high-resolution timer.
>>
>> SeaMonkey doesn't implement the SharedArrayBuffer feature but I'm
>> guessing it's performance.now() function still has the 5μs resolution
>> and that will take a patch to fix.
>>
>> But changing the performance.now() resolution is not sufficient.  Take a
>> look at
>> https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/
>>Furthermore, other timing sources and time-fuzzing techniques are
>> being worked on.
>>
>> Which is like saying we've locked the front door so nobody can walk
>> right in anymore but the ground floor windows are still wide open.
>>
>> Follow the "other timing sources and time-fuzzing techniques" link to
>> https://gruss.cc/files/fantastictimers.pdf
>>Abstract. Research showed that microarchitectural attacks like cache
>> attacks can be performed through websites using JavaScript. These
>> timing attacks allow an adversary to spy on users secrets such as
>> their keystrokes,leveraging fine-grained timers. However, the W3C and
>> browser vendors responded to this significant threat by eliminating
>> fine-grained timers from JavaScript. This renders previous
>> high-resolution microarchitectural attacks non-applicable.
>>
>>>>We demonstrate the inefficacy of this mitigation<< by finding and
>> evaluating a wide range of new sources of timing information. We
>> develop measurement methods that exceed the resolution of official
>> timing sources by to orders of magnitude on all major browsers, and
>> even more on Tor browser. Our timing measurements do not only
>> re-enable previous attacks to their full extent but also allow
>> implementing new attacks. We demonstrate a new DRAM-based covert
>> channel between a website and an unprivileged app in a virtual machine
>> without network hardware. Our results emphasize that quick-fix
>> mitigations can establish a dangerous false sense of security.
>>
>>
>> In short, performance.now() and SharedBufferArray are the easy/obvious
>> ways to get a high resolution timer in javascript but they're not the
>> only possible methods.
>>
>> So... what to do?  The exploit mitigation is to install noscript +
>> request policy continued or uMatrix + uBlock Origin or whatever other
>> addon combo that allows javascript from only whitelisted sites.
>>
>> Regards,
>> Lee
> For "Request Policy" we have for all versions:
> This add-on is not compatible with your version of SeaMonkey.

"Request Policy" was the original - you want "RequestPolicy Continued"
which is easier to use:
https://addons.mozilla.org/en-US/firefox/addon/requestpolicy-continued/

which links to
https://addons.mozilla.org/firefox/downloads/file/747484/requestpolicy_continued-1.0.beta13.2-fx+sm.xpi

> For "NoScript Security Suite" we have:
> Only with FireFox.

yeah.. you need to scroll down to 'version history' & click on 'see
all versions'
It looks like 5.1.8.3 is the last one that will work w/ SM
  Works with Firefox 45.0 - 56.0, SeaMonkey 2.42 - *
https://addons.mozilla.org/firefox/downloads/file/806790/noscript_security_suite-5.1.8.3-fx+sm.xpi

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

Re: Spectre exploit

[Mason83]

On 07/01/2018 23:48, Ray_Net wrote:
> Lee wrote on 07-01-18 22:44:
>> summary: The vuln. mitigation is to install noscript + request policy
>> continued or uMatrix + uBlock Origin or whatever other addon combo
>> that allows javascript from only whitelisted sites.
>>
>> On 1/7/18, Ray_Net  wrote:
>>> WaltS48 wrote on 06-01-18 18:05:
 On 1/6/18 2:36 AM, Ray_Net wrote:
> I have read:
>
> "Disable Javascript until browser company comes out with patch for
> vulnerable Javascript."
>
> So, will SM issue a patch against the Spectre exploit ?
>> Mozilla needs to come up with a patch first.  What they have now only
>> blocks the obvious timing attack methods.
>>
 SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
 doesn't have SharedBufferArray enabled.
 ||
 ||SharedArrayBuffer| is already disabled in Firefox 52 ESR.
 ||
 |REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/

>>> Would it mean that we are protected ?
>> No.
>>
>> Look at the FF advisory
>>The precision of performance.now() has been reduced from 5μs to
>> 20μs, and the SharedArrayBuffer feature has been disabled because it
>> can be used to construct a high-resolution timer.
>>
>> SeaMonkey doesn't implement the SharedArrayBuffer feature but I'm
>> guessing it's performance.now() function still has the 5μs resolution
>> and that will take a patch to fix.
>>
>> But changing the performance.now() resolution is not sufficient.  Take a 
>> look at
>> https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/
>>Furthermore, other timing sources and time-fuzzing techniques are
>> being worked on.
>>
>> Which is like saying we've locked the front door so nobody can walk
>> right in anymore but the ground floor windows are still wide open.
>>
>> Follow the "other timing sources and time-fuzzing techniques" link to
>> https://gruss.cc/files/fantastictimers.pdf
>>Abstract. Research showed that microarchitectural attacks like cache
>> attacks can be performed through websites using JavaScript. These
>> timing attacks allow an adversary to spy on users secrets such as
>> their keystrokes,leveraging fine-grained timers. However, the W3C and
>> browser vendors responded to this significant threat by eliminating
>> fine-grained timers from JavaScript. This renders previous
>> high-resolution microarchitectural attacks non-applicable.
>>
>>>>We demonstrate the inefficacy of this mitigation<< by finding and
>> evaluating a wide range of new sources of timing information. We
>> develop measurement methods that exceed the resolution of official
>> timing sources by to orders of magnitude on all major browsers, and
>> even more on Tor browser. Our timing measurements do not only
>> re-enable previous attacks to their full extent but also allow
>> implementing new attacks. We demonstrate a new DRAM-based covert
>> channel between a website and an unprivileged app in a virtual machine
>> without network hardware. Our results emphasize that quick-fix
>> mitigations can establish a dangerous false sense of security.
>>
>>
>> In short, performance.now() and SharedBufferArray are the easy/obvious
>> ways to get a high resolution timer in javascript but they're not the
>> only possible methods.
>>
>> So... what to do?  The exploit mitigation is to install noscript +
>> request policy continued or uMatrix + uBlock Origin or whatever other
>> addon combo that allows javascript from only whitelisted sites.
>>
>> Regards,
>> Lee
> For "Request Policy" we have for all versions:
> This add-on is not compatible with your version of SeaMonkey.
> 
> For "NoScript Security Suite" we have:
> Only with FireFox.

NoScript >10.x will only work with FF >= 57 (because that version
is a webextension, not XUL add-on).

With SM 2.49 (FF 52) install NoScript 5.1.8.3
https://addons.mozilla.org/firefox/downloads/file/806790/noscript_security_suite-5.1.8.3-fx+sm.xpi?src=version-history
(It says "fx+sm", I think that's FF and SM)

AFAICT, the latest RequestPolicy extension should work...
https://addons.mozilla.org/firefox/downloads/file/223479/requestpolicy-0.5.28-sm+fx.xpi?src=version-history
(In fact, there is no WebExtension version, so no FF 57 support)

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

Re: Spectre exploit

[Ray_Net]

Lee wrote on 07-01-18 22:44:

summary: The vuln. mitigation is to install noscript + request policy
continued or uMatrix + uBlock Origin or whatever other addon combo
that allows javascript from only whitelisted sites.

On 1/7/18, Ray_Net  wrote:

WaltS48 wrote on 06-01-18 18:05:

On 1/6/18 2:36 AM, Ray_Net wrote:

I have read:

"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."

So, will SM issue a patch against the Spectre exploit ?

Mozilla needs to come up with a patch first.  What they have now only
blocks the obvious timing attack methods.


SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
doesn't have SharedBufferArray enabled.
||
||SharedArrayBuffer| is already disabled in Firefox 52 ESR.
||
|REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/


Would it mean that we are protected ?

No.

Look at the FF advisory
   The precision of performance.now() has been reduced from 5μs to
20μs, and the SharedArrayBuffer feature has been disabled because it
can be used to construct a high-resolution timer.

SeaMonkey doesn't implement the SharedArrayBuffer feature but I'm
guessing it's performance.now() function still has the 5μs resolution
and that will take a patch to fix.

But changing the performance.now() resolution is not sufficient.  Take a look at
https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/
   Furthermore, other timing sources and time-fuzzing techniques are
being worked on.

Which is like saying we've locked the front door so nobody can walk
right in anymore but the ground floor windows are still wide open.

Follow the "other timing sources and time-fuzzing techniques" link to
https://gruss.cc/files/fantastictimers.pdf
   Abstract. Research showed that microarchitectural attacks like cache
attacks can be performed through websites using JavaScript. These
timing attacks allow an adversary to spy on users secrets such as
their keystrokes,leveraging fine-grained timers. However, the W3C and
browser vendors responded to this significant threat by eliminating
fine-grained timers from JavaScript. This renders previous
high-resolution microarchitectural attacks non-applicable.

   >>We demonstrate the inefficacy of this mitigation<< by finding and
evaluating a wide range of new sources of timing information. We
develop measurement methods that exceed the resolution of official
timing sources by to orders of magnitude on all major browsers, and
even more on Tor browser. Our timing measurements do not only
re-enable previous attacks to their full extent but also allow
implementing new attacks. We demonstrate a new DRAM-based covert
channel between a website and an unprivileged app in a virtual machine
without network hardware. Our results emphasize that quick-fix
mitigations can establish a dangerous false sense of security.


In short, performance.now() and SharedBufferArray are the easy/obvious
ways to get a high resolution timer in javascript but they're not the
only possible methods.

So... what to do?  The exploit mitigation is to install noscript +
request policy continued or uMatrix + uBlock Origin or whatever other
addon combo that allows javascript from only whitelisted sites.

Regards,
Lee

For "Request Policy" we have for all versions:
This add-on is not compatible with your version of SeaMonkey.

For "NoScript Security Suite" we have:
Only with FireFox.


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

Re: E-Mail Providers

[Jonathan N. Little]

DoctorBill wrote:

WaltS48 wrote:

On 1/1/18 11:32 AM, Ed Mullen wrote:
On 12/31/2017 at 4:54 PM, DoctorBill created this epitome of digital 




Use Gmail's SMTP server:  smtp.gmail.com


First he has to add it to SeaMonkey.

Could you post the steps to achieve that, have the Gmail account use 
it and not use the Default Frontier server.



Right !



I have more than once in this thread!!!

1) Edit > Mail & Newsgroups Account Settings

2) Scroll down in left panel to Outgoing Server (SMTP)

3) Click the Add... button

4) In fields enter:
Description: GMail
Server Name: smtp.gmail.com
Port: 587
Connection Security: STARTTLS
Authentication method: Password transmitted insecurely *
User Name: 
* This is really Normal Password, because of STARTTLS encrypted 
communication to server is already established before password is sent. 
(This is legacy way which I *know* works because I am currently using 
it, but I noticed there is now option for OAuth2. I will convert my to 
that option and update results)


5) Click OK

6) Back in  Mail & Newsgroups Account Settings window in left pane click 
on your GMail account and in right hand panel under Outgoing Server 
(SMTP) droplist select GMail server just defined above.


7) Click OK

8) In your gmail account compose new email and try to send it, should 
get password prompt to set and save password and now you should be able 
to send email from SeaMonkey via gmail.


Now if you ant to use gmail's OAuth2

1) In the Outgoing Server (SMTP) section select the GMail server 
previously defined.


2) Click the Edit button

3) Change Authentication method: from Password transmitted insecurely to 
OAuth2


4) Click OK and then OK again to close setting dialogs

5) Compose a new test email on your gmail account to set the new 
security protocol


6) When you click sent you will get a popup window stating from Google 
that "Thunderbird" is trying to access your account. Put your gmail 
address in the box and click Next


7) You will be prompted for your gmail password enter that and click Next

8) You will be asked to allow "Thunderbird" access to your account so 
click Allow and that is it.


Now you will *send* Gmail using Gmail's SMTP server and not Frontier

--
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Webcam Shuts Off

[Tom Pamin]

Tom Pamin wrote:

Tom Pamin wrote:

chokito wrote:

Copy text below in a text editor and save it as example as WebCam.txt.
Then rename the file to WebCam.htm or WebCam.html and open it with the
browser.



  
Webcam


  
  
http://api.wetmet.net/client-content/PlayerFrame.php?CAMERA=186-04-01&CFVER=WM&WIDTH=100%&HEIGHT=100%";

width="100%" height="100%">
  Your browser does not support iframes.

  



I renamed it to an html file, but the file type still shows as txt, and
opens still in Notepad, not SM?

Got it changed to html. I'll test it later today. Thanks!


One more thing on this. It is working fine, but I do have 2 scroll bars 
on the right side using my 15" laptop. If I choose View-Fullscreen on 
the top, the scroll bar gets closer to fullscreen, but not totally.


Checking the original web site, that view is total fullscreen with no 
scroll bars. Is there any way to adjust your new file to show a real 
fullscreen with no scroll bars. I did try changing the height and width 
%'s in your file, but can't get it right.



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

Re: Spectre exploit

[Lee]

summary: The vuln. mitigation is to install noscript + request policy
continued or uMatrix + uBlock Origin or whatever other addon combo
that allows javascript from only whitelisted sites.

On 1/7/18, Ray_Net  wrote:
> WaltS48 wrote on 06-01-18 18:05:
>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>> I have read:
>>>
>>> "Disable Javascript until browser company comes out with patch for
>>> vulnerable Javascript."
>>>
>>> So, will SM issue a patch against the Spectre exploit ?

Mozilla needs to come up with a patch first.  What they have now only
blocks the obvious timing attack methods.

>> SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
>> doesn't have SharedBufferArray enabled.
>> ||
>> ||SharedArrayBuffer| is already disabled in Firefox 52 ESR.
>> ||
>> |REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/
>>
> Would it mean that we are protected ?

No.

Look at the FF advisory
  The precision of performance.now() has been reduced from 5μs to
20μs, and the SharedArrayBuffer feature has been disabled because it
can be used to construct a high-resolution timer.

SeaMonkey doesn't implement the SharedArrayBuffer feature but I'm
guessing it's performance.now() function still has the 5μs resolution
and that will take a patch to fix.

But changing the performance.now() resolution is not sufficient.  Take a look at
https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/
  Furthermore, other timing sources and time-fuzzing techniques are
being worked on.

Which is like saying we've locked the front door so nobody can walk
right in anymore but the ground floor windows are still wide open.

Follow the "other timing sources and time-fuzzing techniques" link to
https://gruss.cc/files/fantastictimers.pdf
  Abstract. Research showed that microarchitectural attacks like cache
attacks can be performed through websites using JavaScript. These
timing attacks allow an adversary to spy on users secrets such as
their keystrokes,leveraging fine-grained timers. However, the W3C and
browser vendors responded to this significant threat by eliminating
fine-grained timers from JavaScript. This renders previous
high-resolution microarchitectural attacks non-applicable.

  >>We demonstrate the inefficacy of this mitigation<< by finding and
evaluating a wide range of new sources of timing information. We
develop measurement methods that exceed the resolution of official
timing sources by to orders of magnitude on all major browsers, and
even more on Tor browser. Our timing measurements do not only
re-enable previous attacks to their full extent but also allow
implementing new attacks. We demonstrate a new DRAM-based covert
channel between a website and an unprivileged app in a virtual machine
without network hardware. Our results emphasize that quick-fix
mitigations can establish a dangerous false sense of security.


In short, performance.now() and SharedBufferArray are the easy/obvious
ways to get a high resolution timer in javascript but they're not the
only possible methods.

So... what to do?  The exploit mitigation is to install noscript +
request policy continued or uMatrix + uBlock Origin or whatever other
addon combo that allows javascript from only whitelisted sites.

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

Re: E-Mail Providers

[DoctorBill]

Chris Ilias wrote:

On 2018-01-01 10:06 AM, WaltS48 wrote:

On 12/31/17 4:54 PM, DoctorBill wrote:

Jonathan N. Little wrote:

DoctorBill wrote:


I have several gmail accounts, but gmail does not handle Pictures
(photo files) very well.  There is no "In Line Photos" like SeaMonkey
has - just "attachments".

Can anyone recommend a good E-Mail service that allows photos to be 
embedded in the message like SM did ?  INSERT |  IMAGE etc.
What are you talking about? You know you can access gmail with the 
*client* part of SeaMonkey. I have a gmail account and I can embed 
images inline, just setup your gmail account for access with Mail 
and Newsgroups.


 I have tried to do this, but run into an error message when I try to 
send an E-Mail.


"Outgoing server (SMTP) mail.frontier.com is unknown. The server may 
be incorrectly configured. Please verify that your Outgoing server 
(SMTP) settings are correct and try again."


I get this when I try to send e-mail from any of the gmail accounts. 
Somehow, the frontier

account is getting mixed up with the gmail accounts - ? ? ? ? ? ?

I don't know enough on how to address this "error" !



Use Thunderbird. It automatically sets up email accounts for you and 
you won't have these problems.


People post in support forums because they don't want to switch 
products. Telling them to use a different product is not helpful and 
off-topic.



Right !
Like telling someone with questions about how our government works to 
move to Afghanistan.


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

Re: E-Mail Providers

[DoctorBill]

WaltS48 wrote:

On 1/1/18 11:32 AM, Ed Mullen wrote:
On 12/31/2017 at 4:54 PM, DoctorBill created this epitome of digital 
genius:

Jonathan N. Little wrote:

DoctorBill wrote:


I have several gmail accounts, but gmail does not handle Pictures
(photo files) very well.  There is no "In Line Photos" like SeaMonkey
has - just "attachments".

Can anyone recommend a good E-Mail service that allows photos to be 
embedded in the message like SM did ?  INSERT |  IMAGE   etc.
What are you talking about? You know you can access gmail with the 
*client* part of SeaMonkey. I have a gmail account and I can embed 
images inline, just setup your gmail account for access with Mail 
and Newsgroups.


  I have tried to do this, but run into an error message when I try 
to send an E-Mail.


"Outgoing server (SMTP) mail.frontier.com is unknown. The server may 
be incorrectly configured. Please verify that your Outgoing server 
(SMTP) settings are correct and try again."


I get this when I try to send e-mail from any of the gmail accounts. 
Somehow, the frontier

account is getting mixed up with the gmail accounts - ? ? ? ? ? ?

I don't know enough on how to address this "error" !


Use Gmail's SMTP server:  smtp.gmail.com


First he has to add it to SeaMonkey.

Could you post the steps to achieve that, have the Gmail account use it 
and not use the Default Frontier server.



Right !

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

Re: Spectre exploit

[David E. Ross]

On 1/7/2018 2:48 AM, Ray_Net wrote:
> WaltS48 wrote on 06-01-18 18:05:
>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>> I have read:
>>>
>>> "Disable Javascript until browser company comes out with patch for 
>>> vulnerable Javascript."
>>>
>>>
>>> So, will SM issue a patch against the Spectre exploit ?
>>
>> SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR 
>> doesn't have SharedBufferArray enabled.
>>
>> ||
>>
>>> ||SharedArrayBuffer| is already disabled in Firefox 52 ESR.|
>> ||
>>
>> |REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/|
>>
>> ||
>> ||
>>
>> |
>> |
>>
> Would it mean that we are protected ?
> 

That would mean SeaMonkey is protected.  You must also update Windows
itself AFTER you verify that your anti-virus application is compatible
with the Windows patch.

-- 
David E. Ross


President Trump:  Please stop using Twitter.  We need
to hear your voice and see you talking.  We need to know
when your message is really your own and not your attorney's.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Spectre exploit

[WaltS48]

On 1/7/18 5:48 AM, Ray_Net wrote:

WaltS48 wrote on 06-01-18 18:05:

On 1/6/18 2:36 AM, Ray_Net wrote:

I have read:

"Disable Javascript until browser company comes out with patch for 
vulnerable Javascript."



So, will SM issue a patch against the Spectre exploit ?


SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR 
doesn't have SharedBufferArray enabled.


||


||SharedArrayBuffer| is already disabled in Firefox 52 ESR.|

||

|REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/|

||
||

|
|


Would it mean that we are protected ?



Well, the advisory does say "the |SharedArrayBuffer| feature has been 
disabled because it can be used to construct a high-resolution timer".


If it isn't enabled in the ESR that SeaMonkey is based on, then I would 
expect users are protected.



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

Re: Is this group moderated?

[A Williams]

Daniel wrote:

Paul in Houston, TX wrote:

rickman wrote:

Paul B. Gallagher wrote on 12/14/2017 2:30 PM:

WaltS48 wrote:

On 12/14/17 11:46 AM, Paul B. Gallagher wrote:

David E. Ross wrote:

On 12/13/2017 3:45 PM, Richard Owlett wrote:

If so, *WHY*?

I ask because I follow a similar group following a different
fork of
Netscape.

On that group the moderator chastised a poster for suggesting
conformance to courtesy/productivity issues.

YMMV



Mozilla newsgroups are listed at
.  Those newgroups
that are
moderated are indicated as such.  There is no indication of
moderation
for mozilla.support.seamonkey.


True enough. But in practice, Chris Ilias removes messages that
violate
his criteria and issues warnings both public and private. If you
want to
call that moderation, there it is.



You have received warnings about off-topic, or other unacceptable
posts to
this specific newsgroup?


I have. I didn't always agree with the assessment, but what could I do?

And it's not like he's fining me or firing me or putting me in jail.
At most
it's an annoyance when it happens to me, and a pleasure when it
happens to
real bad guys like the Italian spammer. ;-)


Do any spammers get the ax?  I have seen no indication of that.


Except for the ones in Italian I see zero spam or drama in this group.


Neither have I recently!! After I got the filter working correctly.

I'm guessing they only make it here because they come via Google groups
... and nobody dares upset them!!



Why would blocking a spammer upset Google?
Speaking strictly for myself, there are two categories I'd like to see 
blocked - the other one being posts where the date is more than 24 hours 
in the future.

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

Re: Spectre exploit

[Ray_Net]

WaltS48 wrote on 06-01-18 18:05:

On 1/6/18 2:36 AM, Ray_Net wrote:

I have read:

"Disable Javascript until browser company comes out with patch for 
vulnerable Javascript."



So, will SM issue a patch against the Spectre exploit ?


SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR 
doesn't have SharedBufferArray enabled.


||


||SharedArrayBuffer| is already disabled in Firefox 52 ESR.|

||

|REF: https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/|

||
||

|
|


Would it mean that we are protected ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey