Does anyone have any resources on building a mail relay that would limit
the amount of email a single user or ip address can relay over a given
time period?
I have a spam/virus problem that is getting out of hand.
Adi
quote who=Adi Linden
Does anyone have any resources on building a mail relay that would limit
the amount of email a single user or ip address can relay over a given
time period?
relayd for qmail
http://dizzy.roedu.net/relayd/
I'm sure something exists for Sendmail's milter interface.
Might
On Thu, 25 Mar 2004, Adi Linden wrote:
Does anyone have any resources on building a mail relay that would limit
the amount of email a single user or ip address can relay over a given
time period?
http://monkey.org/~jose/software/vthrottle/
It allows you to say you will only take 1 email
On Thu, 25 Mar 2004, Adi Linden wrote:
Does anyone have any resources on building a mail relay that would limit
the amount of email a single user or ip address can relay over a given
time period?
I have a spam/virus problem that is getting out of hand.
Depending on your MTA poison of
Thank you for all the information. It gives me a few choices to maul over.
Right now the single largest issue are compromised PCs that are abused for
sending SPAM and also send viruses. I am seriously considering the idea of
forcing all smtp traffic through a mail relay of some sort.
The
Quoting Adi Linden [EMAIL PROTECTED]:
Is there a way do transparently redirect smtp traffic to a server
elsewhere on the network using Cisco gear? It would be much easier to
implement this solution if smtp traffic is transparently sent through the
dedicated box rather than 'cutting
Everybody who's ever been a road warrior and trapped behind a hotel or ISP that
gratuitously snarfs up port 25 and then mangles your mail knows what I mean...
That's why network guys set up port 587 SMTP support, or ...even
worse... authenticated port-80 SMTP relays on an otherwise idle machine
On Thu, 25 Mar 2004 13:51:13 CST, you said:
of abusive mail. After all, it does take time to read and act upon abuse
reports. By forcing smtp through a specific server at least some proactive
measures are possible such as throttling abusive behaviour.
Forcing it through a server doesn't
On Thu, 25 Mar 2004 14:45:20 EST, Deepak Jain said:
That's why network guys set up port 587 SMTP support, or ...even
worse... authenticated port-80 SMTP relays on an otherwise idle machine
in your NOC. Since its not for general consumption it doesn't need to be
easy or automatic as long as
When you get bored fighting the fire with a leaking bucket of water,
technology exists that automates detection, redirection, posting
information to the end users and eventually re-enabling the subscribers
without any manual intervention. Makes days significantly less dull, but
I might
On 03/25/04, [EMAIL PROTECTED] wrote:
On the other hand, it's probably more effective to find some way of making the
Cisco gear block outbound 25 from abusive machines.
Inbound also. The spammers have been using triangular routing
for a while.
(They dial in
Not to sound like a commercial for Cisco, but their IDS stuff does
rewrite ACL's based upon signatures.
Bil Herd
-Original Message-
From: J.D. Falk [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Redirecting mail (Re: Throttling mail
Ray,
Take a look at IOS server load balancing. You create a virtual server
with your public IP address and bind 1 or more real servers to this
serverfarm.
The nice thing about IOS SLB is that it is part of the IOS image in native
mode on the 65xx and the 72xx series. It runs on a couple of
On Thu, 25 Mar 2004 14:43:33 CST, Adi Linden said:
Where is something like this documented and explained?
If your customer-facing routers/switches are able to generate flow statistics,
it's a Small Matter Of Programming to have something catch said data and do the
analysis. You might need some
14 matches
Mail list logo
