On 01/08/2018 01:01 AM, Daniel wrote:
> I dual boot this HP 6730b Laptop with both Windows 7 and Mageia Linux,
> as shown i8n my sig file, and share the one SeaMonkey 2.49.1 profile
> which is situated on one of my Win7 partitions. Recently I have added
> Lightning (getting old ... memory
I upgraded SeaMonkey to 2.49.1 yesterday. Now I am getting the
following message:
"Inbox is protected. Please enter a Document Open Password."
I have never established such a password on any system that I have ever
owned. How do I fix this problem?
Windows 10
Frog
Lee wrote on 08-01-18 23:19:
On 1/8/18, Ray_Net wrote:
Lee wrote on 08-01-18 01:06:
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
On 08.01.2018 22:46, mozilla-lists.mbou...@spamgourmet.com wrote:
In short, I think the problem is with neither the OS nor SeaMonkey, but
with your configuration (attempting to share a single profile between
the two OSs).
Right! Special care is needed if it comes to use one profile
On 1/8/18, Ray_Net wrote:
> Lee wrote on 08-01-18 01:06:
>> 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 +
Paul B. Gallagher wrote:
Jonathan N. Little wrote:
Paul B. Gallagher wrote:
Jonathan N. Little wrote:
Because Windows defaults to using *localtime* for the system's
realtime clock and Linux uses UTC. Getting Windows to use UTC is a
bit of a pain, so it is much easier to adjust Linux.
Not
Daniel wrote:
I dual boot this HP 6730b Laptop with both Windows 7 and Mageia Linux,
as shown i8n my sig file, and share the one SeaMonkey 2.49.1 profile
which is situated on one of my Win7 partitions. Recently I have added
Lightning (getting old ... memory failing ;-( or is my life getting
Jonathan N. Little wrote:
Paul B. Gallagher wrote:
Jonathan N. Little wrote:
Because Windows defaults to using *localtime* for the system's
realtime clock and Linux uses UTC. Getting Windows to use UTC is a
bit of a pain, so it is much easier to adjust Linux.
Not much of a pain here on
Daniel wrote:
Paul B. Gallagher wrote:
Because such an invalid time stamp is proof that the message is spam.
Real people don't keep their computer date and time so far off from
reality.
Well, just at the moment, Paul, you might pick me, as I'm swapping
between Linux and Win7. My clock varies
Paul B. Gallagher wrote:
Jonathan N. Little wrote:
Because Windows defaults to using *localtime* for the system's
realtime clock and Linux uses UTC. Getting Windows to use UTC is a bit
of a pain, so it is much easier to adjust Linux.
Not much of a pain here on Windows 7. Right-click the
Jonathan N. Little wrote:
Because Windows defaults to using *localtime* for the system's realtime
clock and Linux uses UTC. Getting Windows to use UTC is a bit of a pain,
so it is much easier to adjust Linux.
Not much of a pain here on Windows 7. Right-click the clock at lower
right corner
Daniel wrote:
Paul B. Gallagher wrote:
Daniel wrote:
A Williams wrote:
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.
Why?? You could always find out the "real" posting time if
On 1/8/2018 at 5:57 AM, Daniel created this epitome of digital genius:
Paul B. Gallagher wrote:
Daniel wrote:
A Williams wrote:
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.
chokito wrote:
Add scrolling="no" and frameborder="0" to the end of line iframe.
http://api.wetmet.net/client-content/PlayerFrame.php?CAMERA=186-04-01CFVER=WMWIDTH=100%HEIGHT=100%;
width="100%" height="100%" scrolling="no" frameborder="0">
Thanks, that did get rid of the scroll bars. Some of
Add scrolling="no" and frameborder="0" to the end of line iframe.
http://api.wetmet.net/client-content/PlayerFrame.php?CAMERA=186-04-01CFVER=WMWIDTH=100%HEIGHT=100%;
width="100%" height="100%" scrolling="no" frameborder="0">
___
support-seamonkey
Paul B. Gallagher wrote:
Daniel wrote:
A Williams wrote:
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.
Why?? You could always find out the "real" posting time if you needed
it!
Daniel wrote:
A Williams wrote:
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.
Why?? You could always find out the "real" posting time if you needed
it!
Because such an invalid
I dual boot this HP 6730b Laptop with both Windows 7 and Mageia Linux,
as shown i8n my sig file, and share the one SeaMonkey 2.49.1 profile
which is situated on one of my Win7 partitions. Recently I have added
Lightning (getting old ... memory failing ;-( or is my life getting
busier?? ;-) )
Lee wrote on 08-01-18 01:06:
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
A Williams wrote:
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
20 matches
Mail list logo