Re: Chase bank access bug fixed in SM 2.32

2015-01-19 Thread NFN Smith
Ken Rudolph wrote: Using the PrefBar Customize, I get the User Agent Extlist box. But I'm not sure how to go from there. I tried putting in the Firefox user agent above in the Value box opposite Real UA and applying that. But it didn't affect the browser message at Chase.com. I know I'm

Re: Chase bank access bug fixed in SM 2.32

2015-01-17 Thread Ken Rudolph
NFN Smith wrote: Ken Rudolph wrote: Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. I missed responding

Re: Chase bank access bug fixed in SM 2.32

2015-01-16 Thread Daniel
On 16/01/15 12:27, NFN Smith wrote: Snip See above. Yes, you can change your user agent in prefs.js, but that hard-codes things, and you have to update every time that Mozilla does another update cycle. One minor glitch that I've discovered with spoofing in Seamonkey is that it affects your

Re: Chase bank access bug fixed in SM 2.32

2015-01-16 Thread NFN Smith
Daniel wrote: Smithy, why use an extension (dispMUA) to display a message's User-Agent: header when all you need do is set the pref mailnews.headers.showUserAgent to false and the User-Agent line will be displayed in the Subject area of the message pane. Partially personal preference and

Re: Chase bank access bug fixed in SM 2.32

2015-01-16 Thread NFN Smith
Ken Rudolph wrote: Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. I missed responding to this

Re: Chase bank access bug fixed in SM 2.32

2015-01-16 Thread Daniel
On 17/01/15 05:20, NFN Smith wrote: Daniel wrote: Smithy, why use an extension (dispMUA) to display a message's User-Agent: header when all you need do is set the pref mailnews.headers.showUserAgent to false and the User-Agent line will be displayed in the Subject area of the message pane.

Re: Chase bank access bug fixed in SM 2.32

2015-01-15 Thread Zeb Carter
David H. Durgee wrote: Ken Rudolph wrote: David H. Durgee wrote: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser

Re: Chase bank access bug fixed in SM 2.32

2015-01-15 Thread NFN Smith
Following up several responses in a single post... Zeb Carter wrote: David H. Durgee wrote: Ken Rudolph wrote: David H. Durgee wrot e: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still

Re: Chase bank access bug fixed in SM 2.32

2015-01-15 Thread Philip Chee
On 15/01/2015 11:20, PhillipJones wrote: With latest SeaMonkey Version; now Discover also does this. The Wheels at top of SeaMonkey(or Mozilla) are not not educating these financial institutions. In the early days of Mozilla/Firefox they had a tech evang volunteer team who would bombard

Re: Chase bank access bug fixed in SM 2.32

2015-01-15 Thread David H. Durgee
Ken Rudolph wrote: David H. Durgee wrote: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread David H. Durgee
Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We

Chase bank access bug fixed in SM 2.32

2015-01-14 Thread Ken Rudolph
Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread WaltS48
On 01/14/2015 07:44 PM, Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread PhillipJones
Paul B. Gallagher wrote: PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I know you're capable

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread PhillipJones
PhillipJones wrote: Paul B. Gallagher wrote: PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread PhillipJones
Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread Paul B. Gallagher
PhillipJones wrote: Paul B. Gallagher wrote: PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread Ken Rudolph
David H. Durgee wrote: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when

Re: Chase bank access bug fixed in SM 2.32

2015-01-14 Thread Paul B. Gallagher
PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I know you're capable of it, but the last