On Friday, February 22, 2019 at 9:49:32 AM UTC-6, NFN Smith wrote:
> scientist77...@gmail.com wrote:
> > I have to spoof my useragent to use Yahoo mail with Seamonkey.
> >
> > I use this.
> > Mozilla/5.0 (X11; Linux i686; rv:64.0) Gecko/20100101 Firefox/64.0
> >
> > I can read my mail but can not delete emails.
> >
> >
> > Is there a fix other than using FF?
> >
>
>
> I have more than one account with Yahoo -- on the primary one, I
> normally read through mail and news client, although occasionally, I
> will log in to web mail. No problems there.
>
> I also have an account that I touch rarely, and I just checked in there,
> with web mail. It's been long enough since I interacted with that
> account that I had to initiate a password reset, and once I logged in
> there, Yahoo complained that the new version of their web mail client
> doesn't like my version of Firefox (i.e., Seamonkey 2.49.4 showing
> itself as Firefox 52): "The new Yahoo Mail is no longer supported on
> your browser. Please use a supported browser below or use classic Mail",
> with download links offered for current versions of Chrome and Firefox.
> There is also a link shown for "continue with classic mail", but is
> unresponsive.
>
> I have PrefBar, and when I set Seamonkey to show itself as Firefox 60,
> (specifically, "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0)
> Gecko/20100101 Firefox/60.0" ) I have no problems getting through to the
> new client.
>
> (By the way, if I happen to be spoofing that I'm running Linux, the
> string that I use is "Mozilla/5.0 (X11; Linux x86_64; rv:60.0)
> Gecko/20100101 Firefox/60.0" . For you, one minor niggle would be to
> use an underscore in "x86_64". That may not affect handling any, but a
> valid Linux UA will use the underscore, and the lack of underscore
> indicates that you are spoofing. There are sites out there that will
> reject UA strings that are known to be invalid, in varying degrees of
> aggressiveness.)
>
> Ultimately, the problem is that because Firefox 52 is no longer
> developed/supported, there's an increasing number of web sites that are
> no longer allowing that version. Even before the Firefox ESR shifted
> from 52.x to 60.x, there were sites rejecting older Firefox versions
> (especially ones older than Firefox 57), but with 60.x being the new ESR
> version, rejection of 52.x is accelerating.
>
> A further problem is that the number of Seamonkey users is few enough
> that a lot of site owners don't know about it, or if they do, don't
> care. Or that they don't know that even if Seamonkey 2.49.4 is based on
> Firefox 52, it still has current security updated back ported from
> Firefox 60.x. It's real easy for site owners to simply work under the
> assumption that "Firefox 52 is dead, and we don't want people using it
> to access our site."
>
> In fact, judging from the logs of my own site, the large majority of
> visits from browsers showing Firefox versions older than 60 are bots
> with forged user agent strings. Rejecting those connections is
> considered to be a zero-loss way of blocking a lot of bogus traffic. And
> yes, I'm in the process of adjusting my own filtering rules to be more
> aggressive about rejecting forged traffic, whether from UA strings
> showing really old versions of browsers, as well as browsers showing UA
> strings that have never been valid.
>
> Just yesterday, I posted a comment in a thread that discussed the
> question of a site rejecting *all* versions of Seamonkey (including
> versions that show Seamonkey 2.53/Firefox 60).
>
> This has always been an issue with Seamonkey, that site operators care
> only about "Firefox" (and with the continued growth of Chrome, there's a
> growing number of sites that effectively support Chrome only). It helped
> several years ago when Seamonkey devs adjusted the default UA string to
> show Firefox and Seamonkey, rather than insisting on showing Seamonkey
> only. Before that, there were enough sites that didn't recognize
> Seamonkey, that it was necessary to know how to do browser spoofing.
> Since then, in my own experience, it's been infrequently needed to do
> spoofing, although I have other reasons to do occasional spoofing.
>
> In the meantime, with the end of Firefox 52 ESR, and continued growth of
> Chrome's market share, you should assume that you'll see a corresponding
> growth in the number of sites that reject Seamonkey. Thus, it's a good
> idea to learn how to do spoofing. PrefBar is officially abandoned, and
> it's no longer available from the Seamonkey repository at
> addons.thunderbird.net, but you can still find it at
> https://prefbar.tuxfamily.org/archive.html .
>
> Yes, it's possible to set a Firefox UA as your default via about:config
> (in your prefs.js file), although I recommend against that. Although
> that's fine if you use Seamonkey for only the browser, whatever is in
> that setting also applies to the mail
