Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.software.seamonkey    |    Not a bad little Mozilla fork    |    9,710 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,277 of 9,710    |
|    NFN Smith to Mark Bourne    |
|    Re: Problematic popup for imap.mail.yaho    |
|    09 Oct 25 09:21:34    |
      From: worldoff9908@gmail.com              Mark Bourne wrote:              >>>       >>> Dave       >>       >> The error console shows [ABE} errors relating to this. How do I fix       >> that?       >>       >> Dave       >       > I don't know if it might have other meanings, but to me "ABE" is       > NoScript's "Application Boundaries Enforcer" that restricts which       > domains can load Javascript and other resources from which other       > domains. It could be that the Yahoo login page is trying to load       > Javascript from another Yahoo domain, and maybe you've configured ABE       > rules that prevent that. As far as I recall ABE isn't enabled by       > default in NoScript, and has very few restrictions by default even if       > enabled. So if that is the problem, hopefully you'd know you've enabled       > ABE at some point and that's enough of a clue to work out how to adjust       > whatever rules you've set up.       >       > Or it could be "ABE" has a completely different meaning in this context...!       >              I'm a NoScript user, but have never interacted with ABE.              If NoScript is active, then it can be disruptive to mail connections. At       the very least, you need to make sure that all of the scripting hosts       that Yahoo mail uses have been whitelisted. A good place to start would       be to make sure you have whitelisted the Yahoo sites that mail.yahoo.com       uses for web access. That would include yahoo.com, yahoo.net, oath.com       and yimg.com. The web client also uses googletagmanager, which may be       necessary for use there, but probably isn't necessary for POP/IMAP/SMTP       from the Seamonkey mail client. I would also whitelist yahooapis.com              I know that with Microsoft servers and OAuth2, I found that all of the       authentication processes that they use take a little bit of effort to       find all the necessary servers to whitelist, but I do have that working.       But Yahoo's processes are far less complex than what Microsoft is       imposing on its users.              Smith              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca