Re: USPS website will soon no longer support SeaMonkey

[WaltS48]

On 6/13/18 4:15 PM, Richard Owlett wrote:

On 06/13/2018 09:21 AM, David H. Durgee wrote:

Mozilla User wrote:
First YouTube, then YahooMail, now I will soon no longer be able to 
track my packages through USPS using SeaMonkey.


When on the USPS using SeaMonkey, I get this message:
Alert: As of April 30, USPS.com will no longer support outdated 
browsers. To continue access, you may need to upgrade your browser. 
Read more ›


:(

I guess years of using the Mozilla Browser, and then SeaMonkey are 
about to come to an end. I loved the idea of it and have been a loyal 
user for about 15 years, but now I guess I need to switch to FireFox. 
It's just a pain in the neck to keep switching between browsers for 
certain websites. I like having one browser for everything.




Just wanted to let the group know that I found myself totally unable 
to complete a customs form on the USPS website on Monday.  I wound up 
having to physically fill one out at the local post office to get my 
package sent.


This is impacting more that SeaMonkey, I was unable to do so with the 
CURRENT FireFox and Google Chrome either here on my linux mint 18.3 
x64 system!  I can only assume that their snooping is not happy with 
linux browsers.


I assume that at some point I could spoof a user agent string that 
will make USPS happy, but this is getting ridiculous when current 
releases of major browsers are not being supported simply because they 
are linux releases.


Dave


Does USPS know there is a problem?
IOW have *YOU* told the Postmaster General that there is a problem?

About 50 years ago I observed USPS vehicles driven in an 
improper/illegal manner. I complained to local Postmaster. I was 
effectively told "Go jump in the lake!" After all I WAS a college 
student and Cayuga Lake was convenient. Email not having been invented, 
I sent a "snail mail" letter to the Postmaster General. It got a prompt 
response from state/regional/local administrators. The local postmaster 
then stated "there was no problem" BUT "he would meet with me at *MY* 
personal convenience. I declined as I had observed USPS drivers no 
longer doing "bad things".


Depends on the vehicle, but my mailman drives a mail vehicle with the 
steering wheel on the right hand side of the vehicle, so he can drive 
down streets in the correct lane and put the mail in street side mailboxes.


Maybe the one you saw was driving in an improper/illegal manner because 
they had to put the mail in mailboxes on the opposite side of the street 
and his steering wheel was on the left.


Thank you for notifying the Postmaster General that there is a problem 
with using the SeaMonkey browser on their website and being part of the 
solution. 



--
CPU: 3.2 Ghz AMD Athlon(tm) II X3 455 Processor
RAM: 8 GiB
Graphics: GeForce GT 630/PCIe/SSE2
OS: Ubuntu Linux 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Testing Marking Cross-posts as read in SeaMonkey

[WaltS48]

On 6/13/18 3:36 PM, Balaco ocalaB wrote:

Em 13-06-2018 14:43, David E. Ross escreveu:

On 6/12/2018 10:14 PM, Daniel wrote:

I do a fair bit of reading of posts on UseNet which are often
cross-posted, but the cross-posts are not getting marked as read.

I know this did function, long ago, in Netscape Navigator, got broken
(was that in Mozilla Suite??) and still doesn't work in SeaMonkey and, I
guess, in Thunderbird.

So I'm cross-posting this to three groups on the news.mozilla.org server
so I can have a bit of a look ... and play!!

The way I figure, there must be information in the message headers which
is common to all the cross-posts but different to any other posts in any
of the mentioned groups.

If you're not interested, please killfile this thread in the three news
groups.



This is bug #43278, reported 18 years ago.  The problem is in the
MailNews Core component, whiich means it affects both SeaMonkey and
Thunderbird.  This worked in Netscape Communicator 4, which means that
this could be fixed.

See .



 From that page:

- Importance: major
- Status: NEW
- Reported: 18 years ago (as you said)
- Modified: a year ago

An opinion: it is just silly to only write a sentence about when things 
were written, instead of saying the actual date. A year ago may be a 
year and 11 months ago - in other words, a year ago may be in 2016! 18 
years ago may be in the first half of 1999!





An opinion: learn how things work.

If you hover your mouse over "18 years ago" you see a tooltip (you know 
what those are, right) with the date 2000-06-21 01:03 PDT.


The same for "a year ago" 2017-03-17 06:51 PDT

The last comment was made "2 years ago" 2016-12-24 11:24 PST.

--
CPU: 3.2 Ghz AMD Athlon(tm) II X3 455 Processor
RAM: 8 GiB
Graphics: GeForce GT 630/PCIe/SSE2
OS: Ubuntu Linux 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: USPS website will soon no longer support SeaMonkey

[Richard Owlett]

On 06/13/2018 09:21 AM, David H. Durgee wrote:

Mozilla User wrote:
First YouTube, then YahooMail, now I will soon no longer be able to 
track my packages through USPS using SeaMonkey.


When on the USPS using SeaMonkey, I get this message:
Alert: As of April 30, USPS.com will no longer support outdated 
browsers. To continue access, you may need to upgrade your browser. 
Read more ›


:(

I guess years of using the Mozilla Browser, and then SeaMonkey are 
about to come to an end. I loved the idea of it and have been a loyal 
user for about 15 years, but now I guess I need to switch to FireFox. 
It's just a pain in the neck to keep switching between browsers for 
certain websites. I like having one browser for everything.




Just wanted to let the group know that I found myself totally unable to 
complete a customs form on the USPS website on Monday.  I wound up 
having to physically fill one out at the local post office to get my 
package sent.


This is impacting more that SeaMonkey, I was unable to do so with the 
CURRENT FireFox and Google Chrome either here on my linux mint 18.3 x64 
system!  I can only assume that their snooping is not happy with linux 
browsers.


I assume that at some point I could spoof a user agent string that will 
make USPS happy, but this is getting ridiculous when current releases of 
major browsers are not being supported simply because they are linux 
releases.


Dave


Does USPS know there is a problem?
IOW have *YOU* told the Postmaster General that there is a problem?

About 50 years ago I observed USPS vehicles driven in an 
improper/illegal manner. I complained to local Postmaster. I was 
effectively told "Go jump in the lake!" After all I WAS a college 
student and Cayuga Lake was convenient. Email not having been invented, 
I sent a "snail mail" letter to the Postmaster General. It got a prompt 
response from state/regional/local administrators. The local postmaster 
then stated "there was no problem" BUT "he would meet with me at *MY* 
personal convenience. I declined as I had observed USPS drivers no 
longer doing "bad things".


IN OTHER WORDS
"If you are not part of the solution, you are part of the problem!"



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

Re: Testing Marking Cross-posts as read in SeaMonkey

[Balaco ocalaB]

Em 13-06-2018 14:43, David E. Ross escreveu:

On 6/12/2018 10:14 PM, Daniel wrote:

I do a fair bit of reading of posts on UseNet which are often
cross-posted, but the cross-posts are not getting marked as read.

I know this did function, long ago, in Netscape Navigator, got broken
(was that in Mozilla Suite??) and still doesn't work in SeaMonkey and, I
guess, in Thunderbird.

So I'm cross-posting this to three groups on the news.mozilla.org server
so I can have a bit of a look ... and play!!

The way I figure, there must be information in the message headers which
is common to all the cross-posts but different to any other posts in any
of the mentioned groups.

If you're not interested, please killfile this thread in the three news
groups.



This is bug #43278, reported 18 years ago.  The problem is in the
MailNews Core component, whiich means it affects both SeaMonkey and
Thunderbird.  This worked in Netscape Communicator 4, which means that
this could be fixed.

See .



From that page:

- Importance: major
- Status: NEW
- Reported: 18 years ago (as you said)
- Modified: a year ago

An opinion: it is just silly to only write a sentence about when things 
were written, instead of saying the actual date. A year ago may be a 
year and 11 months ago - in other words, a year ago may be in 2016! 18 
years ago may be in the first half of 1999!



--
=
  1.a. Você quer fazer um comentário, mas não quer mostrar
   quem você é?
  1.b. Do you want to make a comment for me, but do not want
   to show who you are?

  2.a. Você pode fazê-lo aqui:
  2.b. You may do it here:

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

Re: Testing Marking Cross-posts as read in SeaMonkey

[David E. Ross]

On 6/12/2018 10:14 PM, Daniel wrote:
> I do a fair bit of reading of posts on UseNet which are often 
> cross-posted, but the cross-posts are not getting marked as read.
> 
> I know this did function, long ago, in Netscape Navigator, got broken 
> (was that in Mozilla Suite??) and still doesn't work in SeaMonkey and, I 
> guess, in Thunderbird.
> 
> So I'm cross-posting this to three groups on the news.mozilla.org server 
> so I can have a bit of a look ... and play!!
> 
> The way I figure, there must be information in the message headers which 
> is common to all the cross-posts but different to any other posts in any 
> of the mentioned groups.
> 
> If you're not interested, please killfile this thread in the three news 
> groups.
> 

This is bug #43278, reported 18 years ago.  The problem is in the
MailNews Core component, whiich means it affects both SeaMonkey and
Thunderbird.  This worked in Netscape Communicator 4, which means that
this could be fixed.

See .

-- 
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: ebay and SeaMonkey Browser Support

[NFN Smith]

TCW wrote:

On 6/12/2018 11:58 PM, Daniel wrote:

TCW wrote on 12/06/18 23:17:


But be aware that even with the "Advertise Firefox" setting set, some 
sites still act up. Seems some now only work if Firefox is the only 
Browser mentioned so kick up a stink if SeaMonkey and Firefox are 
mentioned  or if Firefox and SeaMonkey are mentioned.


Some, hereabouts, have suggested creating a UserAgent pref that would 
apply to the specific, troublesome, site.


I don't think it will completely not load. I mean, come on. Do you know 
how many people that would affect? It's like pointing a gun in someone's 
face and saying they *have* to use this browser or else. Doesn't work 
that way. They'll lose money and issue a mea culpa.


A lot depends on how a site is built. The most common way of browser 
handling is via scripting that checks the presented User Agent string. 
Some sites may simply grumble about an unsupported browser, others may 
not allow additional access. And if you block scripting with something 
such as NoScript, you may not see complaints at all.


There's also non-scripting ways of forcing compliance.  On the web site 
I maintain, I have several rules in place that reject connections by 
certain browser IDs.  In my case, I use those for forged UAs, because I 
know that the access is malicious.  There's one operation that shows 
browser access as "Firefox 40.1" (a version which was never valid). If 
somebody goes to this site with a browser that's showing that, the 
connection will be rejected with a 403 error (and it's something I've 
tested with a spoofed UA string.)


Mostly, browser sniffing is simply looking for an acceptable version 
level.  Thus, as noted elsewhere in this thread, sites are increasingly 
complaining about UA strings that show Firefox 52, not knowing (or 
caring) that Firefox 52.x ESR (and other Mozilla derivatives that are 
based on that) are valid browsers, with current support.  I think a lot 
of the complaints that are coming from sites that have decided that 
anything that's before 57.0 and Quantum should not be used.


On the other hand, there are sites that will object if they see anything 
other than a valid Firefox UA string.  That would be one that has all 
the appropriate Firefox data but also shows the current Seamonkey 
version (which is what you get if you use "Advertise Firefox".  I know 
that chase.com has a reputation of problems there, but personally, I've 
never had problems there if I set the UA string to stock Firefox 
(without advertising compatibility). I've never bothered to check to see 
if other browsers that do similar compatibility advertising have 
problems at Chase.  That would include things like PaleMoon, or Opera (a 
Chromium derivative), which shows a Chrome UA, and then notes 
Opera-specific version info.


There's a variety of reasons that a site may object to Seamonkey (or an 
ESR version of Firefox);


- Security. It's not unreasonable to expect a reasonably current version 
that's updated on security patches.  I don't maintain our corporate web 
site, but I do know that there's a minimum version of Firefox that's 
considered to be acceptable.


- Support. For consumer-facing sites (especially financial sites), it's 
really common for the support people to demand a limited number of 
browsers, and I think this is the issue at Chase. Management decides "we 
only support browsers X, Y and Z", and if they find you're running 
anything else and you need their help, they'll end the conversation. 
Ultimately, this is the same attitude as from 20 years ago, when sites 
were supporting IE only.  They simply didn't want to bother with any 
variations.  Thus, even though Seamonkey is derived from Firefox, and 
runs the same Gecko engine (and has all the same capacities), a 
difference as simple as getting to configs by going to Hamburger Menu -> 
Options, and a tab-centric interface in Firefox, as opposed to 
Seamonkey's Edit -> Preferences, and a tree-oriented UI is more than 
they want to bother with. From a support standpoint, they want to *know* 
what the user is seeing, and not have to guess at UI variants.


- Indifference/laziness: Some devs don't know (or care to know) about 
derivative projcts, and why people may want to use them.  On their part, 
"one size fits all" is a whole lot easier for them.  But that's not 
really much different than software developers that set their installers 
to default to all _their_ preferred options, with the expectation that 
most users won't bother to change the defaults.


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

Re: ebay and SeaMonkey Browser Support

[WaltS48]

On 6/13/18 12:57 AM, Henrik37 wrote:

NFN Smith wrote:

Snip


Big Jim wrote:

If you have things set so that Firefox Compatibility is enabled, 
Seamonkey 2.49.x identifies itself as Firefox 52.0  For most sites 
that are complaining about outdated browsers, it's likely that most of 
them are keying that off seeing Firefox 52 (and devs/admins that don't 
know/care about the Firefox ESR branch).  It also seems that given the 
scope of improvements that came with Firefox 57, a growing number of 
sites are now designating Firefox 57.0 as the minimum browser version.



Snip


Smith


For someone who has never heard about a 'Firefox Compatibility' feature 
before, can you direct me on how to enable it?





Already enabled according to your User Agent in the message header.

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


--
CPU: 3.2 Ghz AMD Athlon(tm) II X3 455 Processor
RAM: 8 GiB
Graphics: GeForce GT 630/PCIe/SSE2
OS: Ubuntu Linux 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: USPS website will soon no longer support SeaMonkey

[David H. Durgee]

Mozilla User wrote:
First YouTube, then YahooMail, now I will soon no longer be able to 
track my packages through USPS using SeaMonkey.


When on the USPS using SeaMonkey, I get this message:
Alert: As of April 30, USPS.com will no longer support outdated 
browsers. To continue access, you may need to upgrade your browser. Read 
more ›


:(

I guess years of using the Mozilla Browser, and then SeaMonkey are about 
to come to an end. I loved the idea of it and have been a loyal user for 
about 15 years, but now I guess I need to switch to FireFox. It's just a 
pain in the neck to keep switching between browsers for certain 
websites. I like having one browser for everything.




Just wanted to let the group know that I found myself totally unable to 
complete a customs form on the USPS website on Monday.  I wound up 
having to physically fill one out at the local post office to get my 
package sent.


This is impacting more that SeaMonkey, I was unable to do so with the 
CURRENT FireFox and Google Chrome either here on my linux mint 18.3 x64 
system!  I can only assume that their snooping is not happy with linux 
browsers.


I assume that at some point I could spoof a user agent string that will 
make USPS happy, but this is getting ridiculous when current releases of 
major browsers are not being supported simply because they are linux 
releases.


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

Re: ebay and SeaMonkey Browser Support

[Daniel]

TCW wrote on 13/06/18 23:01:

On 6/12/2018 11:58 PM, Daniel wrote:

TCW wrote on 12/06/18 23:17:

On 6/11/2018 8:07 PM, Big Jim wrote:
As of June 19th, ebay states that they will no longer support the 
SeaMonkey browser because it is outdated and unsafe.  A paste of the 
message I received is below...


eBay

Oh No!

We noticed that you’re on an outdated web browser that may 
compromise your security as you shop online.


As of June 19, 2018 you will no longer be able to check out on eBay 
with your current browser.

Update to the latest version now so you can continue
to check out safely and securely.

Why must we continually put up with this!


Meh, not likely to do anything. Just make sure that at least Edit > 
Preferences > Advanced > HTTP Networking > Advertise Firefox 
Compatibility is enabled. Or just do: 
http://ficara.altervista.org/?p=2528


I'm using FRG's build of SM 2.53 and eBay hasn't complained to me 
about anything.


But be aware that even with the "Advertise Firefox" setting set, some 
sites still act up. Seems some now only work if Firefox is the only 
Browser mentioned so kick up a stink if SeaMonkey and Firefox are 
mentioned  or if Firefox and SeaMonkey are mentioned.


Some, hereabouts, have suggested creating a UserAgent pref that would 
apply to the specific, troublesome, site.


I don't think it will completely not load. I mean, come on. Do you know 
how many people that would affect? It's like pointing a gun in someone's 
face and saying they *have* to use this browser or else. Doesn't work 
that way. They'll lose money and issue a mea culpa.


Hey, you're preaching to the converted here, I'm just reporting what 
others have reported here, before.

--
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: ebay and SeaMonkey Browser Support

[TCW]

On 6/12/2018 11:58 PM, Daniel wrote:

TCW wrote on 12/06/18 23:17:

On 6/11/2018 8:07 PM, Big Jim wrote:
As of June 19th, ebay states that they will no longer support the 
SeaMonkey browser because it is outdated and unsafe.  A paste of the 
message I received is below...


eBay

Oh No!

We noticed that you’re on an outdated web browser that may compromise 
your security as you shop online.


As of June 19, 2018 you will no longer be able to check out on eBay 
with your current browser.

Update to the latest version now so you can continue
to check out safely and securely.

Why must we continually put up with this!


Meh, not likely to do anything. Just make sure that at least Edit > 
Preferences > Advanced > HTTP Networking > Advertise Firefox 
Compatibility is enabled. Or just do: 
http://ficara.altervista.org/?p=2528


I'm using FRG's build of SM 2.53 and eBay hasn't complained to me 
about anything.


But be aware that even with the "Advertise Firefox" setting set, some 
sites still act up. Seems some now only work if Firefox is the only 
Browser mentioned so kick up a stink if SeaMonkey and Firefox are 
mentioned  or if Firefox and SeaMonkey are mentioned.


Some, hereabouts, have suggested creating a UserAgent pref that would 
apply to the specific, troublesome, site.


I don't think it will completely not load. I mean, come on. Do you know 
how many people that would affect? It's like pointing a gun in someone's 
face and saying they *have* to use this browser or else. Doesn't work 
that way. They'll lose money and issue a mea culpa.

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

Re: Testing Marking Cross-posts as read in SeaMonkey

[Mason83]

On 13/06/2018 07:14, Daniel wrote:

> The way I figure, there must be information in the message headers which 
> is common to all the cross-posts but different to any other posts in any 
> of the mentioned groups.

Yes: the Message-ID.

That of your initial message is 

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