Re: Sites inaccessible via seamonkey

2010-05-14 Thread Ray_Net
David E. Ross wrote: On 5/13/10 12:18 PM, Ray_Net wrote: David E. Ross a écrit : On 5/13/10 5:43 AM, Russ Hunt wrote: On Apr 30, 7:24 pm, Ray_Nettbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps

Re: Sites inaccessible via seamonkey

2010-05-14 Thread David E. Ross
On 5/14/10 8:45 AM, Ray_Net wrote: David E. Ross wrote: On 5/13/10 12:18 PM, Ray_Net wrote: David E. Ross a écrit : On 5/13/10 5:43 AM, Russ Hunt wrote: On Apr 30, 7:24 pm, Ray_Nettbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set

Re: Sites inaccessible via seamonkey

2010-05-13 Thread Russ Hunt
On Apr 30, 7:24 pm, Ray_Net tbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps you.  -JW Hm.  I haven't been able to find out where that is. How do I set that? in SM browser, type the url  

Re: Sites inaccessible via seamonkey

2010-05-13 Thread David E. Ross
On 5/13/10 5:43 AM, Russ Hunt wrote: On Apr 30, 7:24 pm, Ray_Net tbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps you. -JW Hm. I haven't been able to find out where that is. How do I set

Re: Sites inaccessible via seamonkey

2010-05-13 Thread Ray_Net
David E. Ross a écrit : On 5/13/10 5:43 AM, Russ Hunt wrote: On Apr 30, 7:24 pm, Ray_Nettbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps you. -JW Hm. I haven't been able to find out where

Re: Sites inaccessible via seamonkey

2010-05-13 Thread JeffM
Russ Hunt wrote: unless SeaMonkey can be configured so as to avoid this without this pretty obscure individual fix, David E. Ross wrote: The problem is not in SeaMonkey. Yup. sniffing Yup. The proper way to address this problem requires three actions: 2. Contact the owner of Web sites that

Re: Sites inaccessible via seamonkey

2010-05-13 Thread David E. Ross
On 5/13/10 12:18 PM, Ray_Net wrote: David E. Ross a écrit : On 5/13/10 5:43 AM, Russ Hunt wrote: On Apr 30, 7:24 pm, Ray_Nettbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps you. -JW Hm. I

Re: Sites inaccessible via seamonkey

2010-05-13 Thread David E. Ross
On 5/13/10 8:45 AM, David E. Ross wrote: On 5/13/10 5:43 AM, Russ Hunt wrote: On Apr 30, 7:24 pm, Ray_Net tbrraymond.schmit...@tbrscarlet.be wrote: Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps you. -JW Hm. I haven't been able to

Re: Sites inaccessible via seamonkey

2010-05-05 Thread JohnW-Mpls
On Fri, 30 Apr 2010 22:42:30 -0300, Russ Hunt h...@stu.ca wrote: David E. Ross -- Thank you. This is pretty clearly the problem: The webmail.bellaliant.net server is sniffing for Firefox. This is invalid. If sniffing can be justified at all, the site should be sniffing for Gecko. For an

Re: Sites inaccessible via seamonkey

2010-05-01 Thread David E. Ross
On 4/30/10 6:42 PM, Russ Hunt wrote: David E. Ross -- Thank you. This is pretty clearly the problem: The webmail.bellaliant.net server is sniffing for Firefox. This is invalid. If sniffing can be justified at all, the site should be sniffing for Gecko. For an explanation of sniffing,

Re: Sites inaccessible via seamonkey

2010-05-01 Thread Paul B. Gallagher
Russ Hunt wrote: David E. Ross -- Finally, your signature should have the -- (dash-dash-space) on a separate line without any text. I've done my signature like this since about 1988, and I've never had anybody suggest that (or never noticed anyone except yours with the - - on a

Re: Sites inaccessible via seamonkey

2010-04-30 Thread chicagofan
Russ Hunt wrote: I've recent discovered two commercial sites that I cannot access via SEamonkey, though both response when I use Firefox, Internet Explorer, and Chrome. One is this: https://webmail.bellaliant.net/do/login?v=aliantl=en-US I get a message saying: This operation is not currently

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Rubens
chicagofan wrote, on 2010-04-30 14:53: Russ Hunt wrote: I've recent discovered two commercial sites that I cannot access via SEamonkey, though both response when I use Firefox, Internet Explorer, and Chrome. One is this: https://webmail.bellaliant.net/do/login?v=aliantl=en-US I get a message

Re: Sites inaccessible via seamonkey

2010-04-30 Thread J. Weaver Jr.
Russ Hunt wrote: I've recent discovered two commercial sites that I cannot access via SEamonkey, though both response when I use Firefox, Internet Explorer, and Chrome. One is this: https://webmail.bellaliant.net/do/login?v=aliantl=en-US I get a message saying: This operation is not currently

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Russ Hunt
Thanks, Rubens. I get a message saying: This operation is not currently available. Please contact your System Administrator and try again later. We are sorry for this interruption in your service. I don't get that message with any other browser. I got the same... with SM 2.04 and WinXP2.

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Russ Hunt
Well. https://webmail.bellaliant.net/do/login?v=aliantl=en-US That site gives me a Username/Password prompt. Looks normal. That's interesting. I wonder what the difference is. I've tried it from two different machines (both running SM 2.04 and WinXP), and consistently get the error

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Ray_Net
Russ Hunt wrote: Well. I have general.useragent.extra.firefox set to NOT Firefox/3.6. See if that helps you. -JW Hm. I haven't been able to find out where that is. How do I set that? in SM browser, type the url about:config then enter a New string: general.useragent.extra.firefox

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Paul
Russ Hunt wrote: I've recent discovered two commercial sites that I cannot access via SEamonkey, though both response when I use Firefox, Internet Explorer, and Chrome. One is this: https://webmail.bellaliant.net/do/login?v=aliantl=en-US

Re: Sites inaccessible via seamonkey

2010-04-30 Thread David E. Ross
On 4/30/10 1:16 PM, Russ Hunt wrote: Thanks, Rubens. I get a message saying: This operation is not currently available. Please contact your System Administrator and try again later. We are sorry for this interruption in your service. I don't get that message with any other browser. I

Re: Sites inaccessible via seamonkey

2010-04-30 Thread David E. Ross
On 4/30/10 4:55 PM, Paul wrote: Russ Hunt wrote: I've recent discovered two commercial sites that I cannot access via SEamonkey, though both response when I use Firefox, Internet Explorer, and Chrome. One is this: https://webmail.bellaliant.net/do/login?v=aliantl=en-US

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Russ Hunt
David E. Ross -- Thank you. This is pretty clearly the problem: The webmail.bellaliant.net server is sniffing for Firefox. This is invalid. If sniffing can be justified at all, the site should be sniffing for Gecko. For an explanation of sniffing, see my

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Beauregard T. Shagnasty
Russ Hunt wrote: I've done my signature like this since about 1988, and I've never had anybody suggest that (or never noticed anyone except yours with the - - on a separate line. Why? It should be -- (without the quotes of course). See mine below and note the presence of the space. Why?

Re: Sites inaccessible via seamonkey

2010-04-30 Thread Phillip Jones
Russ Hunt wrote: I've recent discovered two commercial sites that I cannot access via SEamonkey, though both response when I use Firefox, Internet Explorer, and Chrome. One is this: https://webmail.bellaliant.net/do/login?v=aliantl=en-US I get a message saying: This operation is not currently