Spanish dictionaries don't appear in mail compose spell check

[Lance Courtland]

Windows 10 Home
SM Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.3


I have downloaded and supposedly successfully installed 3 Spanish 
language dictionaries using Edit/Check Spelling/Language/Download more 
dictionaries, from an email compose window.  They all appear in the 
Add-ons Mangaer Extensions window.


After closing SM and opening again, none of the dictionaries appears in 
the Language drop-down list.


Was there some change in how to use other language dictionaries?

TIA

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

Re: constipated email continues

[WaltS48]

On 8/4/20 1:20 PM, David H. Durgee wrote:

WaltS48 wrote:

On 8/3/20 5:16 PM, David H. Durgee wrote:

I have been having problems with what I refer to as constipated email
since 2.49.4 and it still continues with 2.53.3 at present.  What I am
referring to is that new email for a POP3 account will no longer be
downloaded via periodic POP3 checks.  When I notice that I haven't
received any new email for a long enough period I then click on the "Get
Messages For Account" in the pop-up menu and I then receive the
following pop-up error:


The POP3 mail server (pop.verizon.net) does not support UIDL or XTND
XLST, which are required to implement the ``Leave on Server'', ``Maximum
Message Size'' or ``Fetch Headers Only'' options. To download your mail,
turn off these options in the Server Settings for your mail server in
the Account Settings window.


The only way I have found to correct this problem is to restart
SeaMonkey.  Thankfully I now have the "restart" add-on to do this and in
virtually all cases that solves the problem.  In a rare few cases I get
the same pop-up error again and need to restart a second time.

Perhaps the biggest inconvenience of this whole thing is that the
periodic checks for new messages DO NOT display this pop-up when they
encounter it.  The pop-up error is only displayed for a manual message
retrieval.  Thus it can be hours before I notice that the bug has hit me
again.

Surely there is a way to request that periodic POP3 checks display error
messages when they have a problem.  That would allow me to correct the
situation quickly and thus be able to respond to urgent email in a
timely manner.


At least until the problem can be corrected I would like to be notified
that the problem is occurring again.  It would be even nicer if the log
of the POP3 diagnostics could be saved so that I could provide it to the
developers to allow them to correct the problem.

Dave



Bug 1577548-Intermittent UIDL or XTND XLST Error Messages.



Many support posts.






Thanks for locating this Bugzilla report.  Looking through it sounds as
if a fix should be simple enough, just properly deal with the temporary
error by exiting the current fetch in hope that the problem will be
clear next time.

This clarifies for me why the issue appears to be more frequent lately,
AOL must be having capacity issues that need to be addressed.
Interesting, I do sometimes see temporary errors displayed when
restarting SeaMonkey, so I guess the code path for first and periodic
checks for POP3 mail differ.  This might make the fix even easier, as
the code already exists in the first check path.

Hopefully Frank-Rainer Grahl is keeping an eye on this thread and will
take appropriate action in the next release if it is as simple as it
appears from that Bugzilla report.

Dave



I'd still think there is nothing to fix in the code and the problem is 
with Verizon.


I don't get that message with my Comcast POP3 account and haven't seen 
any reports about similar POP3 account problems with other email providers.


My suggestion would be to use an AOL IMAP account and copy the emails to it.

I think there are instructions somewhere to setup a Verizon IMAP account.

Doesn't really matter since Verizon owns AOL, Yahoo, Huffington Post, 
Mapquest and other properties.


--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
https://give.thunderbird.net/en-US/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.53.3 released!

[Frank-Rainer Grahl]

Steve Wendt wrote:

On 8/4/2020 1:27 PM, Frank-Rainer Grahl wrote:

I've noticed that Lightning complains about being incompatible when trying 
to go from 2.53.x+1 beta to 2.53.x final.


Downlevel was never supported by SeaMonkey or Gecko so the distributed 
lightning is not picked up. It is now a packed extension which makes 
installing it manually pretty easy. Profiles are more or less compatible too 
with latest versions but might change any time.


Sorry if this is a stupid question, but what's the procedure for "removing" 
the "incompatible" Lightning version and "installing" the "compatible" packed 
version?  I would have expected installing the previous version to fully 
replace the prior / "newer" one, but I'm guessing it's got a version string in 
some configuration file that confuses it?


Ypu can find the xpi in distribution\extensions under the user friedly name 
{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi :)


Just drop it over the browser window and you should get an installation prompt.

The other option is to remove the newer and and reset the distribution key. 
Outlined in the release notes under
Known Issues->Lightning or one of the distributed extensions is not showing up 
or is disabled under Add-ons.


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

Re: SeaMonkey 2.53.3 released!

[Steve Wendt via support-seamonkey]

On 8/4/2020 1:27 PM, Frank-Rainer Grahl wrote:

I've noticed that Lightning complains about being incompatible when 
trying to go from 2.53.x+1 beta to 2.53.x final.


Downlevel was never supported by SeaMonkey or Gecko so the distributed 
lightning is not picked up. It is now a packed extension which makes 
installing it manually pretty easy. Profiles are more or less compatible 
too with latest versions but might change any time.


Sorry if this is a stupid question, but what's the procedure for 
"removing" the "incompatible" Lightning version and "installing" the 
"compatible" packed version?  I would have expected installing the 
previous version to fully replace the prior / "newer" one, but I'm 
guessing it's got a version string in some configuration file that 
confuses it?

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

Re: SeaMonkey 2.53.3 released!

[Frank-Rainer Grahl]

Steve Wendt wrote:

On 8/4/2020 9:05 AM, vij wrote:

A case on pc win7: I try 2.53.3 and it doesn't work on some securised site, 
so I came back to 2.53.2 and Lightning doesn't work at all since...


I've noticed that Lightning complains about being incompatible when trying to 
go from 2.53.x+1 beta to 2.53.x final.


Downlevel was never supported by SeaMonkey or Gecko so the distributed 
lightning is not picked up. It is now a packed extension which makes 
installing it manually pretty easy. Profiles are more or less compatible too 
with latest versions but might change any time.


That said I am not aware of any sites not working in 2.53.3 which worked in 
2.53.2. Probably a different problem maybe with antivirus software.


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

Re: SeaMonkey 2.53.3 released!

[Steve Wendt via support-seamonkey]

On 8/4/2020 9:05 AM, vij wrote:

A case on pc win7: I try 2.53.3 and it doesn't work on some securised 
site, so I came back to 2.53.2 and Lightning doesn't work at all since...


I've noticed that Lightning complains about being incompatible when 
trying to go from 2.53.x+1 beta to 2.53.x final.

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

Re: constipated email continues

[David H. Durgee]

WaltS48 wrote:
> On 8/3/20 5:16 PM, David H. Durgee wrote:
>> I have been having problems with what I refer to as constipated email
>> since 2.49.4 and it still continues with 2.53.3 at present.  What I am
>> referring to is that new email for a POP3 account will no longer be
>> downloaded via periodic POP3 checks.  When I notice that I haven't
>> received any new email for a long enough period I then click on the "Get
>> Messages For Account" in the pop-up menu and I then receive the
>> following pop-up error:
>>
>>
>> The POP3 mail server (pop.verizon.net) does not support UIDL or XTND
>> XLST, which are required to implement the ``Leave on Server'', ``Maximum
>> Message Size'' or ``Fetch Headers Only'' options. To download your mail,
>> turn off these options in the Server Settings for your mail server in
>> the Account Settings window.
>>
>>
>> The only way I have found to correct this problem is to restart
>> SeaMonkey.  Thankfully I now have the "restart" add-on to do this and in
>> virtually all cases that solves the problem.  In a rare few cases I get
>> the same pop-up error again and need to restart a second time.
>>
>> Perhaps the biggest inconvenience of this whole thing is that the
>> periodic checks for new messages DO NOT display this pop-up when they
>> encounter it.  The pop-up error is only displayed for a manual message
>> retrieval.  Thus it can be hours before I notice that the bug has hit me
>> again.
>>
>> Surely there is a way to request that periodic POP3 checks display error
>> messages when they have a problem.  That would allow me to correct the
>> situation quickly and thus be able to respond to urgent email in a
>> timely manner.
>>
>>
>> At least until the problem can be corrected I would like to be notified
>> that the problem is occurring again.  It would be even nicer if the log
>> of the POP3 diagnostics could be saved so that I could provide it to the
>> developers to allow them to correct the problem.
>>
>> Dave
>>
> 
> Bug 1577548-Intermittent UIDL or XTND XLST Error Messages.
> 
> 
> 
> Many support posts.
> 
> 
> 
> 

Thanks for locating this Bugzilla report.  Looking through it sounds as
if a fix should be simple enough, just properly deal with the temporary
error by exiting the current fetch in hope that the problem will be
clear next time.

This clarifies for me why the issue appears to be more frequent lately,
AOL must be having capacity issues that need to be addressed.
Interesting, I do sometimes see temporary errors displayed when
restarting SeaMonkey, so I guess the code path for first and periodic
checks for POP3 mail differ.  This might make the fix even easier, as
the code already exists in the first check path.

Hopefully Frank-Rainer Grahl is keeping an eye on this thread and will
take appropriate action in the next release if it is as simple as it
appears from that Bugzilla report.

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

Re: constipated email continues

[WaltS48]

On 8/3/20 5:16 PM, David H. Durgee wrote:

I have been having problems with what I refer to as constipated email
since 2.49.4 and it still continues with 2.53.3 at present.  What I am
referring to is that new email for a POP3 account will no longer be
downloaded via periodic POP3 checks.  When I notice that I haven't
received any new email for a long enough period I then click on the "Get
Messages For Account" in the pop-up menu and I then receive the
following pop-up error:


The POP3 mail server (pop.verizon.net) does not support UIDL or XTND
XLST, which are required to implement the ``Leave on Server'', ``Maximum
Message Size'' or ``Fetch Headers Only'' options. To download your mail,
turn off these options in the Server Settings for your mail server in
the Account Settings window.


The only way I have found to correct this problem is to restart
SeaMonkey.  Thankfully I now have the "restart" add-on to do this and in
virtually all cases that solves the problem.  In a rare few cases I get
the same pop-up error again and need to restart a second time.

Perhaps the biggest inconvenience of this whole thing is that the
periodic checks for new messages DO NOT display this pop-up when they
encounter it.  The pop-up error is only displayed for a manual message
retrieval.  Thus it can be hours before I notice that the bug has hit me
again.

Surely there is a way to request that periodic POP3 checks display error
messages when they have a problem.  That would allow me to correct the
situation quickly and thus be able to respond to urgent email in a
timely manner.


At least until the problem can be corrected I would like to be notified
that the problem is occurring again.  It would be even nicer if the log
of the POP3 diagnostics could be saved so that I could provide it to the
developers to allow them to correct the problem.

Dave



Bug 1577548-Intermittent UIDL or XTND XLST Error Messages.



Many support posts.



--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
https://give.thunderbird.net/en-US/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: constipated email continues

[David H. Durgee]

Don Spam's Reckless Son wrote:
> David H. Durgee wrote:
>> I have been having problems with what I refer to as constipated email
>> since 2.49.4 and it still continues with 2.53.3 at present.  What I am
>> referring to is that new email for a POP3 account will no longer be
>> downloaded via periodic POP3 checks.  When I notice that I haven't
>> received any new email for a long enough period I then click on the "Get
>> Messages For Account" in the pop-up menu and I then receive the
>> following pop-up error:
>>
>>
>> The POP3 mail server (pop.verizon.net) does not support UIDL or XTND
>> XLST, which are required to implement the ``Leave on Server'', ``Maximum
>> Message Size'' or ``Fetch Headers Only'' options. To download your mail,
>> turn off these options in the Server Settings for your mail server in
>> the Account Settings window.
>>
>>
>> The only way I have found to correct this problem is to restart
>> SeaMonkey.  Thankfully I now have the "restart" add-on to do this and in
>> virtually all cases that solves the problem.  In a rare few cases I get
>> the same pop-up error again and need to restart a second time.
>>
>> Perhaps the biggest inconvenience of this whole thing is that the
>> periodic checks for new messages DO NOT display this pop-up when they
>> encounter it.  The pop-up error is only displayed for a manual message
>> retrieval.  Thus it can be hours before I notice that the bug has hit me
>> again.
>>
>> Surely there is a way to request that periodic POP3 checks display error
>> messages when they have a problem.  That would allow me to correct the
>> situation quickly and thus be able to respond to urgent email in a
>> timely manner.
>>
>>
>> At least until the problem can be corrected I would like to be notified
>> that the problem is occurring again.  It would be even nicer if the log
>> of the POP3 diagnostics could be saved so that I could provide it to the
>> developers to allow them to correct the problem.
>>
>> Dave
>>
> 
> Reverting back to this thread, a question:
> Did this behaviour start with 2.49.4 or did your usage of Seamonkey
> change when that level was current?  Specifically, your tendency to keep
> the program running for days at a time.
> Obviously, I'm wondering if this bug was introduced at around that time
> or if it was there all along.  I suppose you would then need to work out
> what level you were using before 2.49.4.
> 

I have tended to keep SeaMonkey open for long periods for a long time,
so I suspect that the bug was introduced at that time or very shortly
before.  It it is a little difficult to be sure, as the periodic POP3
mail checks fail silently with this bug.  It is only when I suspect a
problem and do a manual check for mail that I am sure the bug has hit again.

I maintain SeaMonkey here via Ubuntuzilla, so whatever releases are
available there would reflect my my prior versions in use.

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

Re: SeaMonkey 2.53.3 released!

[vij]

Mike C a écrit :

Under SeaMonkey 2.53.3 release notes (in RED):
https://www.seamonkey-project.org/releases/

This version of SeaMonkey makes changes to your profile that can't be 
reverted in the case where you want to go back to an earlier version. 
You MUST absolutely do a full backup of your profile before using this 
application.


I never saw anything like this on previous versions.
Is it something to be REALLY concerned with?



A case on pc win7: I try 2.53.3 and it doesn't work on some securised 
site, so I came back to 2.53.2 and Lightning doesn't work at all since...

On macOS all is fine.





Edmund Wong wrote:

Greetings,

The SeaMonkey Project is pleased to announce the release of SeaMonkey
2.53.3.

So please check out [1] or [2].

Updates are still not available via Check-for-updates unfortunately.  I
am *still* working on it.

Thanks to all involved.

Edmund

Links:
[1] - http://www.seamonkey-project.org/releases/2.53.3
[2] - http://www.seamonkey-project.org/releases/seamonkey2.53.3/








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

Re: constipated email on occasion

[David H. Durgee]

Frank-Rainer Grahl wrote:
> 
> 
> Don Spam's Reckless Son wrote:
>> David H. Durgee wrote:
>>> Frank-Rainer Grahl wrote:
 David H. Durgee wrote:
> Don Spam's Reckless Son wrote:
>
> At least one developer, Frank-Rainer Grahl, monitors this newsgroup.
> Perhaps he can look at this post and let me know if it merits a bug
> report.  It might be a known problem or one impossible to fix for some
> reason.  As it is infrequent I can live with it if necessary.
>
> Dave
>

 If it is not easily reproducable a fix in the near future is unlikely.
 Filing a bug in this case would only be good so that others who have
 the
 same problem can find it and so can help track it down. With the
 current
 state of affairs I just wouldn't just hold my breath for this to
 happen.
 Bugs are cheap so your decision. Just don't be discouraged when nothing
 happens with it.

 FRG
>>>
>>> I just had this bite me again today.  Annoying.
>>>
>>> Is there a way to get pop-up notification when the POP mail request
>>> fails in this manner?  Perhaps some config setting or a setting
>>> somewhere in mail configuration I have missed?
>>>
>>> Right now the only way I find out is if I right-click on the mail
>>> account and select "get messages for account", as that WILL result in a
>>> pop-up when there is an error.  If I am otherwise occupied I may not
>>> notice for hours that I have a problem, which happened to me today.
>>>
>>> Dave
>>>
>>
>> If this is happening in Thunderbird as well - and WaltS48 seems to
>> think it is - then a bug report against Thunderbird would be the best
>> chance for a long term solution.
>> Maybe there is such a bug-report already, then it would need votes?
>>
> 
> These bugs are the hardest to track down. We are always trying to get
> general fixes in so that we have a chance to do a catch up later but I
> didn't notice a fix or bug for this yet. If it exists then yes is
> probably in the shared mailnews component.
> 
> 
> FRG

As I noted in my post restating the problem, I believe it would be
helpful if this error resulted in a pop-up when encountered by a
periodic POP3 check for new mail as opposed to silently failing.  It
would be even more helpful if there were a way to provide you with
diagnostic logs when this failure happens.  This need not be default
behavior, I would be happy to set some configuration flags that either
exist already or might be added in a later build to accomplish this.

I don't know why, but this occurring more frequently now than in the
past.  I am sometimes having to restart SeaMonkey more than once per day
to address this problem.  I also find it interesting that it appears the
behavior is a bit different with Thunderbird, as in the restated thread
someone noted that the problem would clear itself the next time around
where that does not appear to be the case with SeaMonkey.

Thank you again for your work in support of SeaMonkey.  I am happy to do
whatever I can to assist you in resolving issues with the package.  May
you find the time and perhaps additional helpers to assist with support
of SeaMonkey.

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

Re: constipated email continues

[Don Spam's Reckless Son]

David H. Durgee wrote:

I have been having problems with what I refer to as constipated email
since 2.49.4 and it still continues with 2.53.3 at present.  What I am
referring to is that new email for a POP3 account will no longer be
downloaded via periodic POP3 checks.  When I notice that I haven't
received any new email for a long enough period I then click on the "Get
Messages For Account" in the pop-up menu and I then receive the
following pop-up error:


The POP3 mail server (pop.verizon.net) does not support UIDL or XTND
XLST, which are required to implement the ``Leave on Server'', ``Maximum
Message Size'' or ``Fetch Headers Only'' options. To download your mail,
turn off these options in the Server Settings for your mail server in
the Account Settings window.


The only way I have found to correct this problem is to restart
SeaMonkey.  Thankfully I now have the "restart" add-on to do this and in
virtually all cases that solves the problem.  In a rare few cases I get
the same pop-up error again and need to restart a second time.

Perhaps the biggest inconvenience of this whole thing is that the
periodic checks for new messages DO NOT display this pop-up when they
encounter it.  The pop-up error is only displayed for a manual message
retrieval.  Thus it can be hours before I notice that the bug has hit me
again.

Surely there is a way to request that periodic POP3 checks display error
messages when they have a problem.  That would allow me to correct the
situation quickly and thus be able to respond to urgent email in a
timely manner.


At least until the problem can be corrected I would like to be notified
that the problem is occurring again.  It would be even nicer if the log
of the POP3 diagnostics could be saved so that I could provide it to the
developers to allow them to correct the problem.

Dave



Reverting back to this thread, a question:
Did this behaviour start with 2.49.4 or did your usage of Seamonkey 
change when that level was current?  Specifically, your tendency to keep 
the program running for days at a time.
Obviously, I'm wondering if this bug was introduced at around that time 
or if it was there all along.  I suppose you would then need to work out 
what level you were using before 2.49.4.


--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: constipated email on occasion

[Frank-Rainer Grahl]

Don Spam's Reckless Son wrote:

David H. Durgee wrote:

Frank-Rainer Grahl wrote:

David H. Durgee wrote:

Don Spam's Reckless Son wrote:

At least one developer, Frank-Rainer Grahl, monitors this newsgroup.
Perhaps he can look at this post and let me know if it merits a bug
report.  It might be a known problem or one impossible to fix for some
reason.  As it is infrequent I can live with it if necessary.

Dave



If it is not easily reproducable a fix in the near future is unlikely.
Filing a bug in this case would only be good so that others who have the
same problem can find it and so can help track it down. With the current
state of affairs I just wouldn't just hold my breath for this to happen.
Bugs are cheap so your decision. Just don't be discouraged when nothing
happens with it.

FRG


I just had this bite me again today.  Annoying.

Is there a way to get pop-up notification when the POP mail request
fails in this manner?  Perhaps some config setting or a setting
somewhere in mail configuration I have missed?

Right now the only way I find out is if I right-click on the mail
account and select "get messages for account", as that WILL result in a
pop-up when there is an error.  If I am otherwise occupied I may not
notice for hours that I have a problem, which happened to me today.

Dave



If this is happening in Thunderbird as well - and WaltS48 seems to think it is 
- then a bug report against Thunderbird would be the best chance for a long 
term solution.

Maybe there is such a bug-report already, then it would need votes?



These bugs are the hardest to track down. We are always trying to get general 
fixes in so that we have a chance to do a catch up later but I didn't notice a 
fix or bug for this yet. If it exists then yes is probably in the shared 
mailnews component.



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

Re: constipated email on occasion - Frank-Rainer Grahl pls read this post

[Don Spam's Reckless Son]

David H. Durgee wrote:

Frank-Rainer Grahl wrote:

David H. Durgee wrote:

Don Spam's Reckless Son wrote:

At least one developer, Frank-Rainer Grahl, monitors this newsgroup.
Perhaps he can look at this post and let me know if it merits a bug
report.  It might be a known problem or one impossible to fix for some
reason.  As it is infrequent I can live with it if necessary.

Dave



If it is not easily reproducable a fix in the near future is unlikely.
Filing a bug in this case would only be good so that others who have the
same problem can find it and so can help track it down. With the current
state of affairs I just wouldn't just hold my breath for this to happen.
Bugs are cheap so your decision. Just don't be discouraged when nothing
happens with it.

FRG


I just had this bite me again today.  Annoying.

Is there a way to get pop-up notification when the POP mail request
fails in this manner?  Perhaps some config setting or a setting
somewhere in mail configuration I have missed?

Right now the only way I find out is if I right-click on the mail
account and select "get messages for account", as that WILL result in a
pop-up when there is an error.  If I am otherwise occupied I may not
notice for hours that I have a problem, which happened to me today.

Dave



If this is happening in Thunderbird as well - and WaltS48 seems to think 
it is - then a bug report against Thunderbird would be the best chance 
for a long term solution.

Maybe there is such a bug-report already, then it would need votes?

--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Access Denied - CarMax.com

[Daniel]

Danny Kile wrote on 4/08/2020 5:58 AM:

Daniel wrote:

Danny Kile wrote on 2/08/2020 12:53 PM:

Don Spam's Reckless Son wrote:

Danny Kile wrote:

Going to carmax.com I get the following error:

Access Denied
You don't have permission to access "http://www.carmax.com/; on 
this server.


Reference #18.2d891ab8.1596029342.1765be0e

I works just fine with Chrome.

What is my solution? Thank you!


This is a Seamonkey forum and your user-agent claims you are using 
Firefox 63.0.3, no trace of Seamonkey at all.
btw, I can also access that site with my geriatric version of 
Seamonkey.




I have tried several user-agents strings and none seem to make a 
deference. Right now I am using the following:


Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
Firefox/60.0 SeaMonkey/2.53.3


Danny, are you sure you are using that UA, because in your message 
that I am replying to, your UA is showing as ...


Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
SeaMonkey/2.53.3


Note NO mention of Firefox!!


And it dose the same thing Access Denied.

I have tried a different user profile and that seem to work. However 
I am not willing to switch user profile to get one site to work. I 
would like to get this one working.


Thank you to all that have replied to this message. Ant other 
suggestions.


Thank you,
Danny


That because I have change it as per recommendation in this forum.


Ah!! O.K., just checking!!
--
Daniel

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


Linux 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