I need to whitelist an ipv6 address in fail2ban, however when I just add them to the ignoreip statement in my jail.conf they get blocked anyways.
This is what I have in /etc/fail2ban/jail.conf
[DEFAULT]
ignoreip = 192.168.100.0/24 , 2a02:2020:2020::1,
Any one knows how to white list an IPv6 addess in fail2ban?
Im trying to setup a 'whitelist' DNS server for a small school network to prevent the kids accessing inappropriate sites (ie. students should only be able to access a pre-selected list of sites) and be forwarded to an access-denied page if they try accessing such a page.
Im aware this can be done using Squid3 but in this specific case its not a viable option.
I read the man named page as well as a number of tech sites and Im not having much luck. If any one could give me nudge in the right direction, I'd really appreciate it.
-Cheers
The question I have may be more of principle than anything else, but here's my dilemma.
I manage an email system for a small company (about 20 email users). We own a plain-letter .com domain name through Network Solutions. Our email service is hosted by Google Apps.
Recently (Feb. 2011) we've been having customers report that they aren't getting our emails. Upon further investigation it seems that the failed emails are all to a common (well known) domain. We have not received any bounce messages for the emails. We've also contacted a few of the intended recipients, who have reported that the messages are not in their spam box; they simply did not receive anything. In these cases we re-sent the same email to an alternate address on another domain, which was successful received.
One customer contacted their email provider about the issue. The provider recommended that we submit a form to be white-listed by their domain.
Here's where my problem begins. I feel like this is heading down a slippery slope. Doesn't this undermine the very principle of email? If this is the appropriate action to take in these situations where will it end? In theory (following this model) it could be argued that eventually one will first need to "whitelist" (or more appropriately termed "authenticate") themselves with an email host before actually sending any messages. More to this point, what keeps the "bad" spammers from doing the same thing...? We've just gone full circle.
I know avoiding anti-spam measures is a big cat-and-mouse game, but I think this is the wrong way of "patching" the problem. Email standards say that messages should not just disappear silently. I have a problem supporting a model that says "you must do < this > to make sure your emails aren't ignored".
I have a notion to call the provider and voice my complaint, although I have a feeling it will probably fall on deaf ears. Am I missing something here? Is this an acceptable approach to email spam problems? What should I do?
What are some good links.articles on how to white list, with flexibility, IPs connecting to MS SQL server. (using win server 2008 r2, if it matters) Thnkas
EDIT:
I want to be able to whitelist IPs conecting to MS SQL Server via the firewall. I need the method to be "Flexible" so that i can change the list frequently. why? because i noticed recently in the database logs that there was an extreme number of failed login attempts from people just trying to brute their way in.
So any information on how to do this would be great. So far in the firewall i know know how to whitelist or blacklist single IPs per rule not entire lists. furthermore i would like to know if this will accomplish what i want. Again Thanks in advance
I just bought a custom domain that I'm trying to use as my primary email address. However at the moment many of my emails are landing in people's SPAM accounts. Are there any cheap ways around this problem (no-spam lists at internet providers or that sort of thing)? I'm not a spammer, I'm a fourth year college student.