On Mon, Mar 3, 2008 at 8:01 PM, Taco Fleur [EMAIL PROTECTED] wrote:
To me a usenet group is to discuss issues
and to ask for guidance, direction, solutions and the state of issues
... not to actually do something
about it in a collaborative manner.
and to inform interested parties what is
... not to actually do something
about it in a collaborative manner.
and to inform interested parties what is being done and requests for
collaboration
*Difference being requesting to do something and doing something.*
Even if the tool is only used by the applications we roll out, its
Taco Fleur wrote:
There is ALWAYS a solution to a problem. But keep 'm coming, the more
ideas we get out of it ;-)
Here's one:
With our CF-base mail server we can do tricks and one has been to log
all bad IP addresses for machines that try to send bad emails. Most
are easy to detect (not a
Thanks Chris.
On 3/4/08, Chris Velevitch [EMAIL PROTECTED] wrote:
On Tue, Mar 4, 2008 at 11:00 AM, Taco Fleur [EMAIL PROTECTED] wrote:
Difference being requesting to do something and doing something.
You are asking this list, what has been done that seems to be
effective. And
Taco,
That would be a good idea, how would you go about this? In other words, if a
request comes to my site, and I want to check this against that list, what
are your plans of setting up?
Otherwise, a good direction in my opinion.
Andrew Scott
Senior Coldfusion Developer
Aegeon Pty.
Hi Andrew,
I guess there are several ways to integrate or use this list.
1. you could pragmatically read the RSS, import it into a local db and base
your decision that
2. there could be a webservice, but obviously that would be taxing
3. you can import the IPs into IIS with a VBS script and have
On Mon, Mar 03, 2008 at 01:00:17PM +1000, Taco Fleur wrote:
We've been dealing with Spammers, bot infected machines, email harvesters,
etc. a lot in the past couple of months. And its a real pain and costing
lots of money. The big Telco's just don't care, none of our requests to get
to the
Well, I believe these are for email SPAM only, and are lacking
functionality.
I'm talking about a combination of several things.
Bot infected machines is also becoming a serious issue, i.e. we see attacks
coming from more than 20 machines with the same requests, but these people
themselves do not
Perhaps . . . you pass an IP address and some kind of unique identifying key
to his verification URL using URL parameters and he returns an XML packet
with an agreed set of data about the IP? There would also need to be some
kind of registration process using a valid email address to get a key
Yes, those are some good points.
With cooperation of everyone I'm sure some good ideas could be brought to
the table.
I've registered whoisblacklisted.info and will start something in regards to
this. Looking forward to hear from anyone interested in participating in any
way.
I'm looking for
Quick question:
Does anyone on this list spend more than 2 hours a week looking at their
logs and doing somethign about it?
Probably not the right list to ask, as its probably the server guys I need
to ask this question to... ;-)
--~--~-~--~~~---~--~~
You received
11 matches
Mail list logo
