Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 6:22 PM, Paul B. Gallagher wrote:
> David E. Ross wrote:
> 
>> On 9/12/2016 2:16 PM, Paul B. Gallagher wrote:
>>> But if cookies.sqlite is marked "read-only," how can a site set a
>>> cookie, even if it's an approved site? I mean, the definition of "set a
>>> cookie" includes "modify cookies.sqlite," does it not? Confusinger and
>>> confusinger...
>>>
>>> Do bank sites really work with stale cookies from previous visits?
>>> Sounds like a great way for hackers to impersonate you -- just spoof
>>> your cookie from a previous session.
>>
>> Two profiles, each with its own file named cookies.sqlite:
>>
>> (1)  Profile for general Web surfing --  The file cookies.sqlite is
>> marked "read only".  When a Web server sends a cookie along with the
>> HTML of a Web page, that cookie sits in the the browser's (SeaMonkey or
>> Firefox) memory.  It does not get written to the on-disc file until
>> either the memory space for cookies is filled or (more likely) the
>> browser is terminated.
> 
> Aha! I didn't realize SM could hold cookies in memory without writing 
> them to disk and still have them work.
> 
> I'm still not clear on how they can be written to a read-only file under 
> any conditions (e.g., "when the cookie memory space is filled or the 
> browser is terminated"). AFAIK, "read-only" means "read-only."
> 

That is correct.  For the "read only" cookies.sqlite file, cookies are
NOT written or even updated (although SeaMonkey might attempt a write
operation).  And when they expire, I have to change the file to
"read-write" and use the old Cookie Manager to delete them manually.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Lemuel Johnson wrote:
> On 9/12/2016 12:31 PM, David E. Ross wrote:
>> On 9/12/2016 9:24 AM, Lemuel Johnson wrote:
>>> snipped
>>>
>>> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
>>> evangelist, I have convinced several friends and family members to use
>>> SM as their browser and email client.  They also have Chase accounts.
>>>
>>> The reality is:
>>> 1. They are not changing banks.
>>> 2. They have no idea what a User Agent is or any desire to learn.
>>> 3. They will not use a different browser just to access chase.com
>>> 4. If they move to a different browser they will not be using SeaMonkey
>>> again.
>>>
>>> So, there was a report that chase.com was usable with the default
>>> SeaMonkey user agent.  That would be good, but I cannot replicate.  My
>>> question is more along the lines of "Am I doing something wrong that
>>> prevents (default) SeaMonkey from being accepted at chase.com?"
>>>
>>
>> I had to create a separate SeaMonkey profile for accessing my financial
>> accounts at a bank, two credit unions, and Vanguard mutual funds.  My
>> settings for this profile might give you some idea of what you might
>> need to do.  Where I say "Normally", that reflects the profile where I
>> do most of my Web surfing.
>>
>> Images from all domains (Normally, I block images from "other" domains.)
>>
>> Cookies from 3rd party domains allowed from which there are already
>> existing cookies and the file cookies.sqlite is marked "read-write".
>> (Normally, I allow cookies only from the requested domain; and I mark
>> cookies.sqlite as "read only".)
>>
>> Popups enabled (Normally, I disable popups.)
>>
>> FlashBlock extension and HTML5 Media enabled  (Normally, they are
>> disabled.)
>>
>> AdBlock Plus and Secret Agent extensions not installed.  (They are
>> installed in the profile where I do most of my Web surfing.)
>>
> 
> Browser preferences at default settings:
> Load all images
> Allow all cookies (normally).  cookies.sqlite is RW
> Block unrequested popup windows checked (I believe this is default)
> None of these are installed: FlashBlock, HTML5 Media, AdBlock, Secret
> Agent.  This is such a blatant case of browser sniffing I doubt any
> extension would cause the problem.
> 
> 
> 
Per David Ross's post on 8/30. I added the following to prefs.js

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");

It did not work right away so stopped playing with it. Someone suggested
that any chase cookies be deleted. After I did that, it started working
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Paul B. Gallagher]

David E. Ross wrote:


On 9/12/2016 2:16 PM, Paul B. Gallagher wrote:

But if cookies.sqlite is marked "read-only," how can a site set a
cookie, even if it's an approved site? I mean, the definition of "set a
cookie" includes "modify cookies.sqlite," does it not? Confusinger and
confusinger...

Do bank sites really work with stale cookies from previous visits?
Sounds like a great way for hackers to impersonate you -- just spoof
your cookie from a previous session.


Two profiles, each with its own file named cookies.sqlite:

(1)  Profile for general Web surfing --  The file cookies.sqlite is
marked "read only".  When a Web server sends a cookie along with the
HTML of a Web page, that cookie sits in the the browser's (SeaMonkey or
Firefox) memory.  It does not get written to the on-disc file until
either the memory space for cookies is filled or (more likely) the
browser is terminated.


Aha! I didn't realize SM could hold cookies in memory without writing 
them to disk and still have them work.


I'm still not clear on how they can be written to a read-only file under 
any conditions (e.g., "when the cookie memory space is filled or the 
browser is terminated"). AFAIK, "read-only" means "read-only."


--
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: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Lemuel Johnson wrote:
> On 9/12/2016 12:31 PM, David E. Ross wrote:
>> On 9/12/2016 9:24 AM, Lemuel Johnson wrote:
>>> snipped
>>>
>>> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
>>> evangelist, I have convinced several friends and family members to use
>>> SM as their browser and email client.  They also have Chase accounts.
>>>
>>> The reality is:
>>> 1. They are not changing banks.
>>> 2. They have no idea what a User Agent is or any desire to learn.
>>> 3. They will not use a different browser just to access chase.com
>>> 4. If they move to a different browser they will not be using SeaMonkey
>>> again.
>>>
>>> So, there was a report that chase.com was usable with the default
>>> SeaMonkey user agent.  That would be good, but I cannot replicate.  My
>>> question is more along the lines of "Am I doing something wrong that
>>> prevents (default) SeaMonkey from being accepted at chase.com?"

I created that report but have since found out that it was not as true
statement. When I use the "Default" profile, Chase is not usable. I did
change the prefs.js but I originally thought that the change made no
difference. However, I now think it did fix the Chase problem. I will go
back and research what I did and let you know. Sorry for the misinformation.
>>
>> I had to create a separate SeaMonkey profile for accessing my financial
>> accounts at a bank, two credit unions, and Vanguard mutual funds.  My
>> settings for this profile might give you some idea of what you might
>> need to do.  Where I say "Normally", that reflects the profile where I
>> do most of my Web surfing.
>>
>> Images from all domains (Normally, I block images from "other" domains.)
>>
>> Cookies from 3rd party domains allowed from which there are already
>> existing cookies and the file cookies.sqlite is marked "read-write".
>> (Normally, I allow cookies only from the requested domain; and I mark
>> cookies.sqlite as "read only".)
>>
>> Popups enabled (Normally, I disable popups.)
>>
>> FlashBlock extension and HTML5 Media enabled  (Normally, they are
>> disabled.)
>>
>> AdBlock Plus and Secret Agent extensions not installed.  (They are
>> installed in the profile where I do most of my Web surfing.)
>>
> 
> Browser preferences at default settings:
> Load all images
> Allow all cookies (normally).  cookies.sqlite is RW
> Block unrequested popup windows checked (I believe this is default)
> None of these are installed: FlashBlock, HTML5 Media, AdBlock, Secret
> Agent.  This is such a blatant case of browser sniffing I doubt any
> extension would cause the problem.
> 
> 
> 

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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 2:16 PM, Paul B. Gallagher wrote:
> David E. Ross wrote:
>> On 9/12/2016 10:37 AM, Paul B. Gallagher wrote:
>>> David E. Ross wrote:
>>>
 I had to create a separate SeaMonkey profile for accessing my
 financial accounts at a bank, two credit unions, and Vanguard mutual
 funds.  My settings for this profile might give you some idea of what
 you might need to do.  Where I say "Normally", that reflects the
 profile where I do most of my Web surfing.

 ...

 Cookies from 3rd party domains allowed from which there are already
 existing cookies and the file cookies.sqlite is marked "read-write".
 (Normally, I allow cookies only from the requested domain; and I
 mark cookies.sqlite as "read only".)
>>>
>>> I'm very curious about how you made this work. Under normal conditions,
>>> you accept first-party cookies but you prevent SM from updating the
>>> cookies file? How can both be true?
>>>
>>
>> I first set the preference to allow ALL cookies.  I then visited the Web
>> sites of the financial institutions.  After that, I changed the
>> preference to "Allow third-party cookies for previously visited websites
>> only".  In that profile, I always had cookies.sqlite marked
>> "read-write".  Only in the profile I use for most of my Web surfing, I
>> marked that file "read only".
> 
> But if cookies.sqlite is marked "read-only," how can a site set a 
> cookie, even if it's an approved site? I mean, the definition of "set a 
> cookie" includes "modify cookies.sqlite," does it not? Confusinger and 
> confusinger...
> 
> Do bank sites really work with stale cookies from previous visits? 
> Sounds like a great way for hackers to impersonate you -- just spoof 
> your cookie from a previous session.
> 

Two profiles, each with its own file named cookies.sqlite:

(1)  Profile for general Web surfing --  The file cookies.sqlite is
marked "read only".  When a Web server sends a cookie along with the
HTML of a Web page, that cookie sits in the the browser's (SeaMonkey or
Firefox) memory.  It does not get written to the on-disc file until
either the memory space for cookies is filled or (more likely) the
browser is terminated.

(2)  Profile for accessing financial accounts -- The file cookies.sqlite
is marked "read-write".

As for stale cookies, the cookies in profile #2 above are sent back to
the Web server when I request a Web page.  The server returns those
cookies with updated content.  The content might identify my browser and
PC.  If I blocked cookies in this profile, the Web server would require
me to go through several additional steps to login because the server
does not recognize my configuration as belonging to an authentic user.
The server might also not use my preferred settings for my account
because those settings are in my cookies.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/12/2016 12:31 PM, David E. Ross wrote:

On 9/12/2016 9:24 AM, Lemuel Johnson wrote:

snipped

I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"



I had to create a separate SeaMonkey profile for accessing my financial
accounts at a bank, two credit unions, and Vanguard mutual funds.  My
settings for this profile might give you some idea of what you might
need to do.  Where I say "Normally", that reflects the profile where I
do most of my Web surfing.

Images from all domains (Normally, I block images from "other" domains.)

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I mark
cookies.sqlite as "read only".)

Popups enabled (Normally, I disable popups.)

FlashBlock extension and HTML5 Media enabled  (Normally, they are
disabled.)

AdBlock Plus and Secret Agent extensions not installed.  (They are
installed in the profile where I do most of my Web surfing.)



Browser preferences at default settings:
Load all images
Allow all cookies (normally).  cookies.sqlite is RW
Block unrequested popup windows checked (I believe this is default)
None of these are installed: FlashBlock, HTML5 Media, AdBlock, Secret 
Agent.  This is such a blatant case of browser sniffing I doubt any 
extension would cause the problem.




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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/12/2016 12:04 PM, Ed Mullen wrote:

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired
off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What message
does the site give you?

I just went there and tried to log in with fake info and the site
dutifully directed me to an error page.




After a successful login, I am re-directed to
https://www.chase.com/services/browser-upgrade,

where the first sentence is:
"You need to upgrade your browser to access your accounts and statements."

Then they provide links to Internet Explorer, Firefox, Chrome and Safari.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Paul B. Gallagher]

David E. Ross wrote:

On 9/12/2016 10:37 AM, Paul B. Gallagher wrote:

David E. Ross wrote:


I had to create a separate SeaMonkey profile for accessing my
financial accounts at a bank, two credit unions, and Vanguard mutual
funds.  My settings for this profile might give you some idea of what
you might need to do.  Where I say "Normally", that reflects the
profile where I do most of my Web surfing.

...

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I
mark cookies.sqlite as "read only".)


I'm very curious about how you made this work. Under normal conditions,
you accept first-party cookies but you prevent SM from updating the
cookies file? How can both be true?



I first set the preference to allow ALL cookies.  I then visited the Web
sites of the financial institutions.  After that, I changed the
preference to "Allow third-party cookies for previously visited websites
only".  In that profile, I always had cookies.sqlite marked
"read-write".  Only in the profile I use for most of my Web surfing, I
marked that file "read only".


But if cookies.sqlite is marked "read-only," how can a site set a 
cookie, even if it's an approved site? I mean, the definition of "set a 
cookie" includes "modify cookies.sqlite," does it not? Confusinger and 
confusinger...


Do bank sites really work with stale cookies from previous visits? 
Sounds like a great way for hackers to impersonate you -- just spoof 
your cookie from a previous session.


--
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: Duplicate Address Book Entries

[Rick Merrill]

On 8/2/2016 4:46 PM, Frosted Flake wrote:

I currently have only two address books in Seamonkey: "Collected
Addresses" and "Personal Address Book"

Each of those have many duplicated entries for people.

Under "Personal Address Book" I have created a number of Mailing Lists
that I want to use to organize my contacts.

That raises a few questions

1) When an entry is dragged to a mailing list under the "Personal
Address Book", where does it get taken from?  Wherever it comes from,
that real email address has to remain there in order to remain in the
mailing list.

2) Can that email address be used in multiple mailing lists?

3) In either "Collected Addresses" or "Personal Address Book", there are
many duplicated entries.  What is the simplest way to remove duplicates
before filling the contacts into the mailing lists?

4) Which of the two "Collected Addresses" or "Personal Address Book")
should be the source for the mailing lists under "Personal Address Book"?

5) If it is the "Personal Address Book", can I safely empty all the
email address in "Collected Addresses" after moving the ones of interest
into the "Personal Address Book"?

Questions above are in no particular order or priority.

My thought is to move all appropriate email address from "Collected
Addresses" to "Personal Address Book".  Then eliminate all duplicates
from that list.  Finally, populate the individual mailing lists from the
"Personal Address Book".  Hopefully keeping only one copy of the actual
contact entry in the "Personal Address Book".

Does this even make any sense?  :)


Yes, it makes sense as we have all encountered similar issues at one 
time or another. "Collected" has those to whom you have sent email, 
including "reply all". I regularly go through those and remove the 
"abuse..." and similar items.


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

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 10:37 AM, Paul B. Gallagher wrote:
> David E. Ross wrote:
> 
>> I had to create a separate SeaMonkey profile for accessing my
>> financial accounts at a bank, two credit unions, and Vanguard mutual
>> funds.  My settings for this profile might give you some idea of what
>> you might need to do.  Where I say "Normally", that reflects the
>> profile where I do most of my Web surfing.
>>
>> ...
>>
>> Cookies from 3rd party domains allowed from which there are already
>> existing cookies and the file cookies.sqlite is marked "read-write".
>> (Normally, I allow cookies only from the requested domain; and I
>> mark cookies.sqlite as "read only".)
> 
> I'm very curious about how you made this work. Under normal conditions, 
> you accept first-party cookies but you prevent SM from updating the 
> cookies file? How can both be true?
> 

I first set the preference to allow ALL cookies.  I then visited the Web
sites of the financial institutions.  After that, I changed the
preference to "Allow third-party cookies for previously visited websites
only".  In that profile, I always had cookies.sqlite marked
"read-write".  Only in the profile I use for most of my Web surfing, I
marked that file "read only".

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: RETR Problem with e-mail

[Arnie Goetchius]

Henrik37 wrote:
> Arnie Goetchius wrote:
>> Henrik37 wrote:
>>> In trying to download a large number of e-mails that have stacked up on
>>> an e-mail server, I receive the following error message:
>>>
>>> "The RETR command did not succeed. Error retrieving a message. Mail
>>> server mail..net responded: messages are counted from 1"
>>>
>>> I am not certain what I am being told or how to fix the problem.
>>>
>>> All suggestions, help and/or advice will be gratefully accepted.
>>>
>>> The PC involved is running SM v2.39 under Win XP SP3
>> If I don't download for a while (days, weeks) and there are lots of
>> unread messages on the server, I get that message whether XP SP3, Win7
>> or Win10. I just restart the "Get msgs" and after a number of restarts,
>> all messages on the server are downloaded. I don't know what the magic
>> number of "unread" messages is to cause this to happen but it does
>> happen to me, often :-(
>>
> Interesting observation.  Do you just hit the 'Get msgs' button
> repeatedly or do you back completely out of SM e-mail and re-enter the
> PW, etc.?
I don't back out but I do give it a minute or so before I het the "Get
Msgs" button again
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Paul B. Gallagher]

David E. Ross wrote:


I had to create a separate SeaMonkey profile for accessing my
financial accounts at a bank, two credit unions, and Vanguard mutual
funds.  My settings for this profile might give you some idea of what
you might need to do.  Where I say "Normally", that reflects the
profile where I do most of my Web surfing.

...

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I
mark cookies.sqlite as "read only".)


I'm very curious about how you made this work. Under normal conditions, 
you accept first-party cookies but you prevent SM from updating the 
cookies file? How can both be true?


--
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: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 9:24 AM, Lemuel Johnson wrote:
> On 9/11/2016 8:19 PM, Ed Mullen wrote:
>> On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:
>>> On 9/10/2016 12:28 PM, Ed Mullen wrote:
 On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:
> On 9/2/2016 1:56 PM, Arnie Goetchius wrote:
>> snipped<
>> As of today, I can now log into the Chase website with the default
>> User
>> Agent for Seamonkey. This is what my UA shows:
>>
>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>> Firefox/43.0 SeaMonkey/2.40
>>
>
> Chase is still not allowing me access.
>
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
> Firefox/43.0
> SeaMonkey/2.40
>
> I also tried spoofing "Windows NT 10.0" without success.

 Try clearing out any Chase cookies and make sure you allow them.

>>>
>>> Did that first, also cleared cache.  Still no go:
>>> "You need to upgrade your browser to access your accounts and
>>> statements."
>>
>> Change banks.
>>
>>
> 
> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even 
> evangelist, I have convinced several friends and family members to use 
> SM as their browser and email client.  They also have Chase accounts.
> 
> The reality is:
> 1. They are not changing banks.
> 2. They have no idea what a User Agent is or any desire to learn.
> 3. They will not use a different browser just to access chase.com
> 4. If they move to a different browser they will not be using SeaMonkey 
> again.
> 
> So, there was a report that chase.com was usable with the default 
> SeaMonkey user agent.  That would be good, but I cannot replicate.  My 
> question is more along the lines of "Am I doing something wrong that 
> prevents (default) SeaMonkey from being accepted at chase.com?"
> 

I had to create a separate SeaMonkey profile for accessing my financial
accounts at a bank, two credit unions, and Vanguard mutual funds.  My
settings for this profile might give you some idea of what you might
need to do.  Where I say "Normally", that reflects the profile where I
do most of my Web surfing.

Images from all domains (Normally, I block images from "other" domains.)

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I mark
cookies.sqlite as "read only".)

Popups enabled (Normally, I disable popups.)

FlashBlock extension and HTML5 Media enabled  (Normally, they are
disabled.)

AdBlock Plus and Secret Agent extensions not installed.  (They are
installed in the profile where I do most of my Web surfing.)

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ed Mullen]

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What message 
does the site give you?


I just went there and tried to log in with fake info and the site 
dutifully directed me to an error page.



--
Ed Mullen
http://edmullen.net/
Have you ever imagined a world with no hypothetical situations?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: RETR Problem with e-mail

[Henrik37]

Arnie Goetchius wrote:

Henrik37 wrote:

In trying to download a large number of e-mails that have stacked up on
an e-mail server, I receive the following error message:

"The RETR command did not succeed. Error retrieving a message. Mail
server mail..net responded: messages are counted from 1"

I am not certain what I am being told or how to fix the problem.

All suggestions, help and/or advice will be gratefully accepted.

The PC involved is running SM v2.39 under Win XP SP3

If I don't download for a while (days, weeks) and there are lots of
unread messages on the server, I get that message whether XP SP3, Win7
or Win10. I just restart the "Get msgs" and after a number of restarts,
all messages on the server are downloaded. I don't know what the magic
number of "unread" messages is to cause this to happen but it does
happen to me, often :-(

Interesting observation.  Do you just hit the 'Get msgs' button 
repeatedly or do you back completely out of SM e-mail and re-enter the 
PW, etc.?

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

Re: RETR Problem with e-mail

[Henrik37]

Pete wrote:

Have you had email running on this PC before using the software that you
are currently using?

Peter


Yes, two other accounts are up and working.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even 
evangelist, I have convinced several friends and family members to use 
SM as their browser and email client.  They also have Chase accounts.


The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey 
again.


So, there was a report that chase.com was usable with the default 
SeaMonkey user agent.  That would be good, but I cannot replicate.  My 
question is more along the lines of "Am I doing something wrong that 
prevents (default) SeaMonkey from being accepted at chase.com?"

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

Re: Seamonkey release?

[Stephan Thiele]

Hi, Edmund,

thanks a lot for your explanations. I think I understood it’s pretty much 
to do and it’s difficult enough to merely adapt the changes in basic 
codebase and infrastructure.
Thank you for all the work that you as volunteers put into the project, and 
hope on ..


Stephan


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

Re: RETR Problem with e-mail

[Arnie Goetchius]

Henrik37 wrote:
> In trying to download a large number of e-mails that have stacked up on
> an e-mail server, I receive the following error message:
> 
> "The RETR command did not succeed. Error retrieving a message. Mail
> server mail..net responded: messages are counted from 1"
> 
> I am not certain what I am being told or how to fix the problem.
> 
> All suggestions, help and/or advice will be gratefully accepted.
> 
> The PC involved is running SM v2.39 under Win XP SP3
If I don't download for a while (days, weeks) and there are lots of
unread messages on the server, I get that message whether XP SP3, Win7
or Win10. I just restart the "Get msgs" and after a number of restarts,
all messages on the server are downloaded. I don't know what the magic
number of "unread" messages is to cause this to happen but it does
happen to me, often :-(
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[WaltS48]

On 09/11/2016 04:31 PM, Lemuel Johnson wrote:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default 
User

Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
Firefox/43.0

SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and 
statements."



Change browsers. I'll bet Firefox works, and you could use it just for 
Chase.



--
Visit Pittsburgh 
Ubuntu 16.04.1 LTS

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

Re: RETR Problem with e-mail

[Pete]

Have you had email running on this PC before using the software that you 
are currently using?


Peter

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