Of course I meant that when asked, you would create the rule - or had you and yet Outpost asked again?
Anyway, I don’t pretty understand why be so strict to guard every connection to/from localhost. It’s all programs you are already running on your pc, some of them communicate with them selves via network (localhost) and other perhaps communicate by other means you know nothing about from your firewall. Localhost address is not accessible from anyother computer than yours.
But I’m happy to hear that it could be solved by configuring the firewall.
Good day.
Lukas.
U might have found the DNS cache plugin bug, a lot of folk asked about this at the outpost forum & it was recommended to disable it, i had probs with it myself till i disabled it.
Hmm, I think I’ll be better uninstalling the whole think quickly
Yee, when prompted i created a rule for it that included the 12110 that it asked for & allowed it, but in the network activity pane i could see both the localhost rule for mailwasher & OE was being blocked for some reason despite it being allowed, i was only prompted for port 12110 & even tried creating a rule with no ports soecified which should have allowed it access to any port/ports it needed.
The reason i have the global allow localhost rule unticked is it is advised to do so in the faq for creating a secure config at the outpost forums, if U use any kind of proxy, then it can be a security risk, the thread is located here http://www.outpostfirewall.com/forum/showthread.php?t=9858
When configured right, it is a very powerfull firewall, the default config for it can be a bit sparse, but then they have to make a default for non technical users
Hmm, I think I'll be better uninstalling the whole think quickly :P
LOL, give it a try, U never know U might like it, the DNS cache plugin is just a bit flakey,but once disabled there no probs
