Re: SM is not accepted by Chase.com - again!

[Jeffrey Needle]

On Saturday, May 12, 2018 at 2:59:19 PM UTC-7, WaltS48 wrote:
> On 5/12/18 5:32 PM, Jeffrey Needle wrote:
> >>>
> >>>
> >>
> >> You simply need to use a different user agent string when going to
> >> chase.com.  Add this to your prefs.js:
> >>
> >> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
> >> NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");
> > 
> > A favor, please.  I see references to Windows in this entry.  I'm using 
> > Linux, and bank with Chase, and have the same problem.  How would this 
> > entry appear in a Linux box?  Many thanks.
> > 
> 
> I would suggest "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 
> Firefox/60.0". Since that is the latest Firefox release.
> 

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

Re: SM is not accepted by Chase.com - again!

[Lee]

On 5/12/18, WaltS48  wrote:
> On 5/12/18 5:32 PM, Jeffrey Needle wrote:
>>>
>>> You simply need to use a different user agent string when going to
>>> chase.com.  Add this to your prefs.js:
>>>
>>> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
>>> NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");
>>
>> A favor, please.  I see references to Windows in this entry.  I'm using
>> Linux, and bank with Chase, and have the same problem.  How would this
>> entry appear in a Linux box?  Many thanks.
>
> I would suggest "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
> Firefox/60.0". Since that is the latest Firefox release.

Firefox just came out with ESR 52.8 which is a closer match to the
SeaMonkey code base, so I'd suggest pretending you're FF ESR 52 first:
  Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

and if that doesn't work then try 60.0

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

Re: SM is not accepted by Chase.com - again!

[WaltS48]

On 5/12/18 5:32 PM, Jeffrey Needle wrote:





You simply need to use a different user agent string when going to
chase.com.  Add this to your prefs.js:

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


A favor, please.  I see references to Windows in this entry.  I'm using Linux, 
and bank with Chase, and have the same problem.  How would this entry appear in 
a Linux box?  Many thanks.



I would suggest "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 
Firefox/60.0". Since that is the latest Firefox release.


--
GO GOLDEN KNIGHTS!
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[Jeffrey Needle]

> > 
> > 
> 
> You simply need to use a different user agent string when going to 
> chase.com.  Add this to your prefs.js:
> 
> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
> NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");

A favor, please.  I see references to Windows in this entry.  I'm using Linux, 
and bank with Chase, and have the same problem.  How would this entry appear in 
a Linux box?  Many thanks.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[chokito]

My User Agent is "general.useragent.override" "Mozilla/5.0 (Windows NT 6.1; 
WOW64; rv:52.0) Gecko/20100101 Firefox/52.0" and works fine on www.chase.com 
and www.netflix.com with 32-bit and 64-bit versions.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[EE]

cmcadams wrote:

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.



Thank you, I've saved this.

Does anyone know for certain which Windows programs will work to edit 
and save SM config files? And with what settings? Are they ASCII? ANSI? 
I figured that's where I went wrong, trying to edit prefs.js.


Use an ordinary text editor, not a word processor.

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

Re: SM is not accepted by Chase.com - again!

[Ed Mullen]

On 4/1/2018 at 1:05 AM, cmcadams created this epitome of digital genius:

David E. Ross wrote:

On 3/31/2018 6:49 PM, cmcadams wrote:

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I 
suppose.


If an entry into user.js is not recognized by SeaMonkey as being 
valid,

it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.



Thank you, I've saved this.

Does anyone know for certain which Windows programs will work to edit 
and save SM
config files? And with what settings? Are they ASCII? ANSI? I figured 
that's where I

went wrong, trying to edit prefs.js.



The prefs.js file is plain ASCII text.  Unlike Daniel, I prefer always
using Wordpad.  I even set Wordpad as the default appplication for when
I select "Edit" on the context menu for all .js files.


So at least there's no need to worry about that. I can just right-click 
"Open with" and use Notepad or Wordpad depending on size.




If using Wordpad just make sure that you Save As Text. There are other 
formats WP can use that will totally screw up your file.




--
Ed Mullen
https://edmullen.net/
Bureaucracy: a method of turning energy into solid waste.

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

Re: SM is not accepted by Chase.com - again!

[Ed Mullen]

On 3/31/2018 at 2:38 PM, cmcadams created this epitome of digital genius:

WaltS48 wrote:

On 3/30/18 10:25 PM, cmcadams wrote:

Ed Mullen wrote:
On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of 
digital genius:
As of about a week ago, when I log into my Chase accounts account 
using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the 
following page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the 
horizontal span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that 
window still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several 
times, but they refuse to file a report on the problem. Their only 
answer is that Seamonkey is not a supported browser, period. The 
fact that I am still recognized as being logged in is more than 
worrisome.


I am not about to give up on Seamonkey which I have been using 
(under its prior names) for more than 20 years and which is still 
the best browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa




You simply need to use a different user agent string when going to 
chase.com.  Add this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


Since I have a new Chase card I figured I should fix this sooner 
rather than later.


Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and 
DOS Edit, but evidently didn't know the right save options, because 
after running SM the new entry disappeared. Rejected by SM, I suppose.


Cutting to the chase (pun serendipitous): Creating a new entry in 
about:config by manually copying/pasting strings from Ed Mullen's 
example did work.


To create a new entry in about:config you right-click on any entry 
and tell it you want a new string entry. Give it the name 
"general.useragent.override.chase.com" and the value "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0".





Why not ""Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) 
Gecko/20100101 Firefox/59.0"? Which is the current version of Firefox.




I have no preference. I tried Ed Mullen's string and it worked. The 
method remains the same.




The version likely doesn't matter, only that it's a FF UA and reasonably 
recent.


--
Ed Mullen
https://edmullen.net/
I'm a psychic amnesiac. I know in advance what I'm going to forget.

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

Re: SM is not accepted by Chase.com - again!

[Daniel]

cmcadams wrote on 01/04/18 15:27:

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.


This works, I am duly amazed.

With both Notepad and (after toggling value to null) in Wordpad, no 
problems.


Thank you very much.


Alls well that ends well!! Good to hear!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: SM is not accepted by Chase.com - again!

[Ray_Net]

Marisa Ciceran wrote on 30-03-18 16:45:
As of about a week ago, when I log into my Chase accounts account 
using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the 
following page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the 
horizontal span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window 
still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several 
times, but they refuse to file a report on the problem. Their only 
answer is that Seamonkey is not a supported browser, period. The fact 
that I am still recognized as being logged in is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under 
its prior names) for more than 20 years and which is still the best 
browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa


When a site refuse to work with my SM I don't fiddle user.js or other 
fancy specific modification, I just go on the site with FireFox also 
installed on my pc.

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

Re: SM is not accepted by Chase.com - again!

[cmcadams]

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.


This works, I am duly amazed.

With both Notepad and (after toggling value to null) in Wordpad, no problems.

Thank you very much.

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

Re: SM is not accepted by Chase.com - again!

[cmcadams]

David E. Ross wrote:

On 3/31/2018 6:49 PM, cmcadams wrote:

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.



Thank you, I've saved this.

Does anyone know for certain which Windows programs will work to edit and save 
SM
config files? And with what settings? Are they ASCII? ANSI? I figured that's 
where I
went wrong, trying to edit prefs.js.



The prefs.js file is plain ASCII text.  Unlike Daniel, I prefer always
using Wordpad.  I even set Wordpad as the default appplication for when
I select "Edit" on the context menu for all .js files.


So at least there's no need to worry about that. I can just right-click "Open with" 
and use Notepad or Wordpad depending on size.


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

Re: SM is not accepted by Chase.com - again!

[cmcadams]

Daniel wrote:

cmcadams wrote on 01/04/18 11:49:

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.


Thank you, I've saved this.

Does anyone know for certain which Windows programs will work to edit and save SM 
config files? And with what settings? Are they ASCII? ANSI? I figured that's where 
I went wrong, trying to edit prefs.js.


In the past, I'm sure I have used Notepad.exe to edit prefs.js ... and, if I had 
double clicked on a prefs.js that was too big for Notepad.exe to handle, Win7 had 
started Wordpad.exe instead!


Neat. It didn't occur to me to try Wordpad. Says how often I've used it. :/

I loaded prefs.js into Wordpad and thought "Omigosh, lookit all the formatting!" Not 
a problem, there's a save option for that. FC-ing the original with the saved copy 
says identical.


Same same for creating user.js ... which had to be located in the same 
directory/folder as prefs.js to be included into prefs.js.


Ha, I must have found the only reference that DIDN'T say to put it in the profile 
directory. That was that problem then.


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

Re: SM is not accepted by Chase.com - again!

[David E. Ross]

On 3/31/2018 6:49 PM, cmcadams wrote:
> David E. Ross wrote:
>> On 3/31/2018 11:23 AM, EE wrote:
>>> cmcadams wrote:
 Trying a user.js didn't work.

 prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
 DOS Edit, but evidently didn't know the right save options, because
 after running SM the new entry disappeared. Rejected by SM, I suppose.
>>>
>>> If an entry into user.js is not recognized by SeaMonkey as being valid,
>>> it will not appear in about:config.  This includes errors in syntax in
>>> the setting, and also settings that are simply not recognized.  The
>>> format for entries in user.js is the same as that for prefs.js.
>>>
>>
>> To check whether SeaMonkey loaded all of user.js into prefs.js
>> successfully, insert
>>  user_pref("00_user.js.loaded", "user.js load failed");
>> as the very first line of user.js and
>>  user_pref("00_user.js.loaded", "yes");
>> as the very last line of user.js, all with SeaMonkey not running.  Note
>> that the semicolon (;) is required.
>>
>> Then, launch SeaMonkey and enter about:config in the address area (URI
>> bar).  You should see
>>  00_user.js.loaded   user set  string  yes
>> if the entire user.js file was okay.  If there was a problem, you will
>> instead see
>>  00_user.js.loaded   user set  string  user.js load failed
>>
>> This also works with Thunderbird and should work (but I have not tested
>> it) with Firefox.
>>
> 
> Thank you, I've saved this.
> 
> Does anyone know for certain which Windows programs will work to edit and 
> save SM 
> config files? And with what settings? Are they ASCII? ANSI? I figured that's 
> where I 
> went wrong, trying to edit prefs.js.
> 

The prefs.js file is plain ASCII text.  Unlike Daniel, I prefer always
using Wordpad.  I even set Wordpad as the default appplication for when
I select "Edit" on the context menu for all .js files.

-- 
David E. Ross


First you say you do, and then you don't.
And then you say you will, but then won't.
You're undecided now, so what're you goin' to do?
From a 1950s song
That should be Donald Trump's theme song.  He obviously
does not understand "commitment", whether it is about
policy or marriage.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[Daniel]

cmcadams wrote on 01/04/18 11:49:

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.


Thank you, I've saved this.

Does anyone know for certain which Windows programs will work to edit 
and save SM config files? And with what settings? Are they ASCII? ANSI? 
I figured that's where I went wrong, trying to edit prefs.js.


In the past, I'm sure I have used Notepad.exe to edit prefs.js ... and, 
if I had double clicked on a prefs.js that was too big for Notepad.exe 
to handle, Win7 had started Wordpad.exe instead!


Same same for creating user.js ... which had to be located in the same 
directory/folder as prefs.js to be included into prefs.js.


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: SM is not accepted by Chase.com - again!

[Daniel]

Stanimir Stamenkov wrote on 31/03/18 23:35:

Sat, 31 Mar 2018 23:45:06 +1100, _Daniel_:

Stanimir, when I look at Marisa's UA String, she *is* showing FF 52, 
the same as you are, but Marisa is also showing her SM after that, so 
that may be the bit that Chase is "seeing" and not supporting!


I'm just suggesting Marisa may better use:

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

that is omitting just the SM part of the original string, instead of:

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 
Firefox/50.0


which Ed has given initially.


Ah!! Roger that! ;-)

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: SM is not accepted by Chase.com - again!

[Daniel]

David E. Ross wrote on 01/04/18 02:03:

On 3/31/2018 5:45 AM, Daniel wrote:

Stanimir Stamenkov wrote on 31/03/18 19:21:

Fri, 30 Mar 2018 19:51:33 -0400, _Marisa Ciceran_:

Ed Mullen wrote:


You simply need to use a different user agent string when going to
chase.com.  Add this to your prefs.js:

user_pref("general.useragent.override.chase.com", "Mozilla/5.0
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


This reply is the only one that worked for me - that is, once I
figured out how to save to DOS in Wordpad that I almost never use.
Thank you!


You may wish to use UA string more closely resembling your current
configuration, and one which reports more recent Fx version:

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

Note, you could also edit this via the  page, and not
having to deal with hidden configuration files on the file system.


Stanimir, when I look at Marisa's UA String, she *is* showing FF 52, the
same as you are, but Marisa is also showing her SM after that, so that
may be the bit that Chase is "seeing" and not supporting!


Yes, I have encountered a few Web sites that accept a Firefox-only UA
string but reject a Firefox+SeaMonkey string.  That is why I use PrefBar
to switch UA strings, where I have both
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
   and
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
SeaMonkey/2.49.2, NOT Firefox/52.0

Also, in PrefBar, I have a checkbox to toggle "Advertise Firefox
compatibility", for which I usually do not have the check mark
(disabling the feature) and for which my user.js turns off in case I
forget I checked the checkbox.

and, David, I've also seen some, posting here, who have SM first 
followed by FF ... which worked sometimes for them and failed sometimes 
as well!


Seems the UA sniffers are getting pretty complex!! ;-P Boo!!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: SM is not accepted by Chase.com - again!

[cmcadams]

David E. Ross wrote:

On 3/31/2018 11:23 AM, EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config.  This includes errors in syntax in
the setting, and also settings that are simply not recognized.  The
format for entries in user.js is the same as that for prefs.js.



To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.



Thank you, I've saved this.

Does anyone know for certain which Windows programs will work to edit and save SM 
config files? And with what settings? Are they ASCII? ANSI? I figured that's where I 
went wrong, trying to edit prefs.js.

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

Re: SM is not accepted by Chase.com - again!

[David E. Ross]

On 3/31/2018 11:23 AM, EE wrote:
> cmcadams wrote:
>> Trying a user.js didn't work.
>>
>> prefs.js didn't wish to be changed...tried both Windows 7 Notepad and 
>> DOS Edit, but evidently didn't know the right save options, because 
>> after running SM the new entry disappeared. Rejected by SM, I suppose.
> 
> If an entry into user.js is not recognized by SeaMonkey as being valid, 
> it will not appear in about:config.  This includes errors in syntax in 
> the setting, and also settings that are simply not recognized.  The 
> format for entries in user.js is the same as that for prefs.js.
> 

To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running.  Note
that the semicolon (;) is required.

Then, launch SeaMonkey and enter about:config in the address area (URI
bar).  You should see
00_user.js.loaded   user set  string  yes
if the entire user.js file was okay.  If there was a problem, you will
instead see
00_user.js.loaded   user set  string  user.js load failed

This also works with Thunderbird and should work (but I have not tested
it) with Firefox.

-- 
David E. Ross


First you say you do, and then you don't.
And then you say you will, but then won't.
You're undecided now, so what're you goin' to do?
From a 1950s song
That should be Donald Trump's theme song.  He obviously
does not understand "commitment", whether it is about
policy or marriage.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[cmcadams]

EE wrote:

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and DOS Edit, but 
evidently didn't know the right save options, because after running SM the new 
entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid, it will not 
appear in about:config.  This includes errors in syntax in the setting, and also 
settings that are simply not recognized.  The format for entries in user.js is the 
same as that for prefs.js.




I just did a copy and paste. I suspect a wrong format for my user.js.

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

Re: SM is not accepted by Chase.com - again!

[cmcadams]

WaltS48 wrote:

On 3/30/18 10:25 PM, cmcadams wrote:

Ed Mullen wrote:

On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of digital genius:
As of about a week ago, when I log into my Chase accounts account using SM 2.49.2 
on my Windows 7 desktop and laptops, it goes to the following page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the horizontal span of 
the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window still 
triggers the "time out" function that logs me out for non-activity. After that, I 
have the option to log back into MOBILE services.


I've tried to report this issue to Chase customer support several times, but they 
refuse to file a report on the problem. Their only answer is that Seamonkey is 
not a supported browser, period. The fact that I am still recognized as being 
logged in is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under its prior 
names) for more than 20 years and which is still the best browser-mail suite on 
the internet. Any suggestions?


Thanks.

Marisa




You simply need to use a different user agent string when going to chase.com.  Add 
this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows NT 10.0; 
Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


Since I have a new Chase card I figured I should fix this sooner rather than 
later.

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and DOS Edit, but 
evidently didn't know the right save options, because after running SM the new 
entry disappeared. Rejected by SM, I suppose.


Cutting to the chase (pun serendipitous): Creating a new entry in about:config by 
manually copying/pasting strings from Ed Mullen's example did work.


To create a new entry in about:config you right-click on any entry and tell it you 
want a new string entry. Give it the name "general.useragent.override.chase.com" 
and the value "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 
Firefox/50.0".





Why not ""Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 
Firefox/59.0"? Which is the current version of Firefox.




I have no preference. I tried Ed Mullen's string and it worked. The method remains 
the same.


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

Re: SM is not accepted by Chase.com - again!

[EE]

cmcadams wrote:

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and 
DOS Edit, but evidently didn't know the right save options, because 
after running SM the new entry disappeared. Rejected by SM, I suppose.


If an entry into user.js is not recognized by SeaMonkey as being valid, 
it will not appear in about:config.  This includes errors in syntax in 
the setting, and also settings that are simply not recognized.  The 
format for entries in user.js is the same as that for prefs.js.


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

Re: SM is not accepted by Chase.com - again!

[David E. Ross]

On 3/31/2018 5:45 AM, Daniel wrote:
> Stanimir Stamenkov wrote on 31/03/18 19:21:
>> Fri, 30 Mar 2018 19:51:33 -0400, _Marisa Ciceran_:
>>> Ed Mullen wrote:
>>>
 You simply need to use a different user agent string when going to 
 chase.com.  Add this to your prefs.js:

 user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");
>>>
>>> This reply is the only one that worked for me - that is, once I 
>>> figured out how to save to DOS in Wordpad that I almost never use. 
>>> Thank you!
>>
>> You may wish to use UA string more closely resembling your current 
>> configuration, and one which reports more recent Fx version:
>>
>> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
>>
>> Note, you could also edit this via the  page, and not 
>> having to deal with hidden configuration files on the file system.
>>
> Stanimir, when I look at Marisa's UA String, she *is* showing FF 52, the 
> same as you are, but Marisa is also showing her SM after that, so that 
> may be the bit that Chase is "seeing" and not supporting!
> 

Yes, I have encountered a few Web sites that accept a Firefox-only UA
string but reject a Firefox+SeaMonkey string.  That is why I use PrefBar
to switch UA strings, where I have both
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
  and
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
SeaMonkey/2.49.2, NOT Firefox/52.0

Also, in PrefBar, I have a checkbox to toggle "Advertise Firefox
compatibility", for which I usually do not have the check mark
(disabling the feature) and for which my user.js turns off in case I
forget I checked the checkbox.

-- 
David E. Ross


First you say you do, and then you don't.
And then you say you will, but then won't.
You're undecided now, so what're you goin' to do?
From a 1950s song
That should be Donald Trump's theme song.  He obviously
does not understand "commitment", whether it is about
policy or marriage.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[Lee]

On 3/31/18, WaltS48  wrote:
> On 3/30/18 10:25 PM, cmcadams wrote:
>> Ed Mullen wrote:
>>> On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of
>>> digital genius:
 As of about a week ago, when I log into my Chase accounts account
 using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the
 following page:

 https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails



 The page is blank except for two options that run across the
 horizontal span of the page: 1) No thanks and 2) Call to apply.

 Neither of these buttons links to another page. However, that window
 still triggers the "time out" function that logs me out for
 non-activity. After that, I have the option to log back into MOBILE
 services.

 I've tried to report this issue to Chase customer support several
 times, but they refuse to file a report on the problem. Their only
 answer is that Seamonkey is not a supported browser, period. The
 fact that I am still recognized as being logged in is more than
 worrisome.

 I am not about to give up on Seamonkey which I have been using
 (under its prior names) for more than 20 years and which is still
 the best browser-mail suite on the internet. Any suggestions?

 Thanks.

 Marisa


>>>
>>> You simply need to use a different user agent string when going to
>>> chase.com.  Add this to your prefs.js:
>>>
>>> user_pref("general.useragent.override.chase.com", "Mozilla/5.0
>>> (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");
>>
>> Since I have a new Chase card I figured I should fix this sooner
>> rather than later.
>>
>> Trying a user.js didn't work.
>>
>> prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
>> DOS Edit, but evidently didn't know the right save options, because
>> after running SM the new entry disappeared. Rejected by SM, I suppose.
>>
>> Cutting to the chase (pun serendipitous): Creating a new entry in
>> about:config by manually copying/pasting strings from Ed Mullen's
>> example did work.
>>
>> To create a new entry in about:config you right-click on any entry and
>> tell it you want a new string entry. Give it the name
>> "general.useragent.override.chase.com" and the value "Mozilla/5.0
>> (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0".
>>
>>
>
> Why not ""Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0)
> Gecko/20100101 Firefox/59.0"? Which is the current version of Firefox.

Because SeaMonkey 2.49.2 is based on Firefox ESR 52 (extended support
release?), so you've got a better chance of things working correctly
if you pretend to have the latest version of Firefox ESR.

& if Chase had competent web developers this wouldn't be an issue in
the first place, but it is so you probably should have the rv:XXX
number match the Firefox/XXX number:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

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

Re: SM is not accepted by Chase.com - again!

[WaltS48]

On 3/30/18 10:25 PM, cmcadams wrote:

Ed Mullen wrote:
On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of 
digital genius:
As of about a week ago, when I log into my Chase accounts account 
using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the 
following page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the 
horizontal span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window 
still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several 
times, but they refuse to file a report on the problem. Their only 
answer is that Seamonkey is not a supported browser, period. The 
fact that I am still recognized as being logged in is more than 
worrisome.


I am not about to give up on Seamonkey which I have been using 
(under its prior names) for more than 20 years and which is still 
the best browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa




You simply need to use a different user agent string when going to 
chase.com.  Add this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


Since I have a new Chase card I figured I should fix this sooner 
rather than later.


Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and 
DOS Edit, but evidently didn't know the right save options, because 
after running SM the new entry disappeared. Rejected by SM, I suppose.


Cutting to the chase (pun serendipitous): Creating a new entry in 
about:config by manually copying/pasting strings from Ed Mullen's 
example did work.


To create a new entry in about:config you right-click on any entry and 
tell it you want a new string entry. Give it the name 
"general.useragent.override.chase.com" and the value "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0".





Why not ""Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) 
Gecko/20100101 Firefox/59.0"? Which is the current version of Firefox.


--
Best name ever! Cadet Bone Spurs
NRA = Newly Recruited Activists
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop

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

Re: SM is not accepted by Chase.com - again!

[Stanimir Stamenkov via support-seamonkey]

Sat, 31 Mar 2018 23:45:06 +1100, _Daniel_:

Stanimir, when I look at Marisa's UA String, she *is* showing FF 52, the 
same as you are, but Marisa is also showing her SM after that, so that 
may be the bit that Chase is "seeing" and not supporting!


I'm just suggesting Marisa may better use:

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

that is omitting just the SM part of the original string, instead of:

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 
Firefox/50.0


which Ed has given initially.

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

Re: SM is not accepted by Chase.com - again!

[Daniel]

Stanimir Stamenkov wrote on 31/03/18 19:21:

Fri, 30 Mar 2018 19:51:33 -0400, _Marisa Ciceran_:

Ed Mullen wrote:

You simply need to use a different user agent string when going to 
chase.com.  Add this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


This reply is the only one that worked for me - that is, once I 
figured out how to save to DOS in Wordpad that I almost never use. 
Thank you!


You may wish to use UA string more closely resembling your current 
configuration, and one which reports more recent Fx version:


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

Note, you could also edit this via the  page, and not 
having to deal with hidden configuration files on the file system.


Stanimir, when I look at Marisa's UA String, she *is* showing FF 52, the 
same as you are, but Marisa is also showing her SM after that, so that 
may be the bit that Chase is "seeing" and not supporting!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: SM is not accepted by Chase.com - again!

[Stanimir Stamenkov via support-seamonkey]

Fri, 30 Mar 2018 19:51:33 -0400, _Marisa Ciceran_:

Ed Mullen wrote:

You simply need to use a different user agent string when going to 
chase.com.  Add this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


This reply is the only one that worked for me - that is, once I figured 
out how to save to DOS in Wordpad that I almost never use. Thank you!


You may wish to use UA string more closely resembling your current 
configuration, and one which reports more recent Fx version:


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

Note, you could also edit this via the  page, and not 
having to deal with hidden configuration files on the file system.


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

Re: SM is not accepted by Chase.com - again!

[Hartmut Figge]

NoOp:

>https://pasteboard.co/HeoYl92.png

I'm getting the sane with
Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/2018010400 SeaMonkey/2.56a1-h
without advertising FF compatibility.

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

Re: SM is not accepted by Chase.com - again!

[NoOp]

On 03/30/2018 10:33 PM, NoOp wrote:
> On 03/30/2018 07:45 AM, Marisa Ciceran wrote:
>> As of about a week ago, when I log into my Chase accounts account using 
>> SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following 
>> page:
>> 
>> https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails
>> 
>> The page is blank except for two options that run across the horizontal 
>> span of the page: 1) No thanks and 2) Call to apply.

> 
> Works for me.
> 
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
> Firefox/52.0 SeaMonkey/2.49.2
> Build identifier: 20180205032337
> 
> User agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101
> Firefox/52.0 SeaMonkey/2.49.2
> Build identifier: 20180205075051
> 
> 

Screenshot:
https://pasteboard.co/HeoYl92.png
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[NoOp]

On 03/30/2018 07:45 AM, Marisa Ciceran wrote:
> As of about a week ago, when I log into my Chase accounts account using 
> SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following 
> page:
> 
> https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails
> 
> The page is blank except for two options that run across the horizontal 
> span of the page: 1) No thanks and 2) Call to apply.
> 
> Neither of these buttons links to another page. However, that window 
> still triggers the "time out" function that logs me out for 
> non-activity. After that, I have the option to log back into MOBILE 
> services.
> 
> I've tried to report this issue to Chase customer support several times, 
> but they refuse to file a report on the problem. Their only answer is 
> that Seamonkey is not a supported browser, period. The fact that I am 
> still recognized as being logged in is more than worrisome.
> 
> I am not about to give up on Seamonkey which I have been using (under 
> its prior names) for more than 20 years and which is still the best 
> browser-mail suite on the internet. Any suggestions?
> 
> Thanks.
> 
> Marisa
> 
> 

Works for me.

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Firefox/52.0 SeaMonkey/2.49.2
Build identifier: 20180205032337

User agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101
Firefox/52.0 SeaMonkey/2.49.2
Build identifier: 20180205075051


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

Re: SM is not accepted by Chase.com - again!

[cmcadams]

Ed Mullen wrote:

On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of digital genius:
As of about a week ago, when I log into my Chase accounts account using SM 2.49.2 
on my Windows 7 desktop and laptops, it goes to the following page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the horizontal span of the 
page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window still triggers 
the "time out" function that logs me out for non-activity. After that, I have the 
option to log back into MOBILE services.


I've tried to report this issue to Chase customer support several times, but they 
refuse to file a report on the problem. Their only answer is that Seamonkey is not 
a supported browser, period. The fact that I am still recognized as being logged in 
is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under its prior 
names) for more than 20 years and which is still the best browser-mail suite on the 
internet. Any suggestions?


Thanks.

Marisa




You simply need to use a different user agent string when going to chase.com.  Add 
this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows NT 10.0; 
Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


Since I have a new Chase card I figured I should fix this sooner rather than 
later.

Trying a user.js didn't work.

prefs.js didn't wish to be changed...tried both Windows 7 Notepad and DOS Edit, but 
evidently didn't know the right save options, because after running SM the new entry 
disappeared. Rejected by SM, I suppose.


Cutting to the chase (pun serendipitous): Creating a new entry in about:config by 
manually copying/pasting strings from Ed Mullen's example did work.


To create a new entry in about:config you right-click on any entry and tell it you 
want a new string entry. Give it the name "general.useragent.override.chase.com" and 
the value "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 
Firefox/50.0".



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

Re: SM is not accepted by Chase.com - again!

[Marisa Ciceran]

Ed,

This reply is the only one that worked for me - that is, once I figured 
out how to save to DOS in Wordpad that I almost never use. Thank you!


I also appreciate the other suggestions to change my primary bank are 
not viable for me for the simple reason that the Chase branch bank that 
I have been using for 48 years (through it's many predecessor name 
permutations) is less than a minute's walk away from my apartment.


Thanks, all!

Marisa


Ed Mullen wrote:
On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of 
digital genius:
As of about a week ago, when I log into my Chase accounts account 
using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the 
following page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the 
horizontal span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window 
still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several 
times, but they refuse to file a report on the problem. Their only 
answer is that Seamonkey is not a supported browser, period. The fact 
that I am still recognized as being logged in is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under 
its prior names) for more than 20 years and which is still the best 
browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa




You simply need to use a different user agent string when going to 
chase.com.  Add this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
(Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");






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

Re: prefs.js is not for user manipulation (was: SM is not accepted by Chase.com - again!)

[Felix Miata]

Ed Mullen composed on 2018-03-30 11:32 (UTC-0400):

> You simply need to use a different user agent string when going to 
> chase.com.  Add this to your prefs.js:

> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
> NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");

Never add anything to prefs.js if you're not 200% certain you know what you are
doing and how to undo the damage from a mistake. Either include it in user.js,
or include via about:config. User.js is an optional file that SM will only read,
never write.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[EE]

Marisa Ciceran wrote:
As of about a week ago, when I log into my Chase accounts account using 
SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following 
page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the horizontal 
span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window 
still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several times, 
but they refuse to file a report on the problem. Their only answer is 
that Seamonkey is not a supported browser, period. The fact that I am 
still recognized as being logged in is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under 
its prior names) for more than 20 years and which is still the best 
browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa



There must be other banks.  Why not switch banks?

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

Re: SM is not accepted by Chase.com - again!

[David E. Ross]

On 3/30/2018 7:45 AM, Marisa Ciceran wrote:
> As of about a week ago, when I log into my Chase accounts account using 
> SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following 
> page:
> 
> https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails
> 
> The page is blank except for two options that run across the horizontal 
> span of the page: 1) No thanks and 2) Call to apply.
> 
> Neither of these buttons links to another page. However, that window 
> still triggers the "time out" function that logs me out for 
> non-activity. After that, I have the option to log back into MOBILE 
> services.
> 
> I've tried to report this issue to Chase customer support several times, 
> but they refuse to file a report on the problem. Their only answer is 
> that Seamonkey is not a supported browser, period. The fact that I am 
> still recognized as being logged in is more than worrisome.
> 
> I am not about to give up on Seamonkey which I have been using (under 
> its prior names) for more than 20 years and which is still the best 
> browser-mail suite on the internet. Any suggestions?
> 
> Thanks.
> 
> Marisa
> 
> 

I created a separate SeaMonkey profile just for use with those financial
institutions where I have accounts:  a medium-size regional bank, two
credit unions, the issuer of my wife's Master Card, and Vanguard Group.
Among the settings in that profile that are different from those in my
general-use profile are:
*  popups are enabled
*  images from all sources are enabled
*  Flash and HTML5 media are enabled
*  new and updated cookies from domains that have already set cookies
are accepted
*  the cookies.sqlite file is marked "read-write" (but is marked "read
only" in all my other profiles)
*  an anti-tracking extension is not installed (but is installed in my
general-use profile)

For a long time, I also forced the user agent (UA) to spoof Firefox.
Later, I changed that to enable "Advertise Firefox compatibility".
After much hounding by me, all five institutions now accept all my
logins and transactions with "Advertise Firefox compatibility" disabled,
with one exception.  The exception is the occasional Webcast from
Vanguard, which still requires me to spoof Firefox.

Part of all this supports the suggestion expressed by others for using a
small, local bank instead of a mega-bank.  You have more leverage in
getting a small bank to accommodate you than with a large bank.

-- 
David E. Ross


First you say you do, and then you don't.
And then you say you will, but then won't.
You're undecided now, so what're you goin' to do?
From a 1950s song
That should be Donald Trump's theme song.  He obviously
does not understand "commitment", whether it is about
policy or marriage.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM is not accepted by Chase.com - again!

[Ed Mullen]

On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of digital 
genius:
As of about a week ago, when I log into my Chase accounts account using 
SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following 
page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails 



The page is blank except for two options that run across the horizontal 
span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window 
still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several times, 
but they refuse to file a report on the problem. Their only answer is 
that Seamonkey is not a supported browser, period. The fact that I am 
still recognized as being logged in is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under 
its prior names) for more than 20 years and which is still the best 
browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa




You simply need to use a different user agent string when going to 
chase.com.  Add this to your prefs.js:


user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");




--
Ed Mullen
https://edmullen.net/
A fool-proof method for sculpting an elephant: First, get a huge block 
of marble; then chip away everything that doesn't look like an elephant.


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

Re: SM is not accepted by Chase.com - again!

[WaltS48]

On 3/30/18 10:45 AM, Marisa Ciceran wrote:


I am not about to give up on Seamonkey which I have been using (under 
its prior names) for more than 20 years and which is still the best 
browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa



See all the previous posts about this troublesome bank here.

https://groups.google.com/forum/?fromgroups#!searchin/mozilla.support.seamonkey/Chase;context-place=forum/mozilla.support.seamonkey

If I used SeaMonkey, I'd change banks.

--
Best name ever! Cadet Bone Spurs
NRA = Newly Recruited Activists
National Popular Vote
Ubuntu 16.04LTS - Unity Desktop

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

Re: SM is not accepted by Chase.com - again!

[Frank-Rainer Grahl]

> . Any suggestions?

Give up on Chase or use a user agent switcher.

FRG

Marisa Ciceran wrote:

. Any suggestions?

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

SM is not accepted by Chase.com - again!

[Marisa Ciceran]

As of about a week ago, when I log into my Chase accounts account using 
SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following 
page:


https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails

The page is blank except for two options that run across the horizontal 
span of the page: 1) No thanks and 2) Call to apply.


Neither of these buttons links to another page. However, that window 
still triggers the "time out" function that logs me out for 
non-activity. After that, I have the option to log back into MOBILE 
services.


I've tried to report this issue to Chase customer support several times, 
but they refuse to file a report on the problem. Their only answer is 
that Seamonkey is not a supported browser, period. The fact that I am 
still recognized as being logged in is more than worrisome.


I am not about to give up on Seamonkey which I have been using (under 
its prior names) for more than 20 years and which is still the best 
browser-mail suite on the internet. Any suggestions?


Thanks.

Marisa


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