jeffs wrote:
Sahil Tandon wrote:
On Mon, 23 Mar 2009, jeffs wrote:
There is the slight potential for abuse by these logged in users that
one or two may figure out a way to send spam through this system by
forging (not login) credentials that the database uses to sort out
outbound email.
This is really shady. Why can't you secure the system?
I'm developing a system that examines the apache logs for a particular
string of characters, which only occasionally are present in the URLs
-- very rarely. Actually, the presence of those strings, is the
mechanism that kicks off a script that sends email to an email
address. Now, it is difficult but not impossible for someone to
calculate what those strings may be. If they guess right, they could
flood my apache logs with those strings and thereby kick off a flurry
of alerts to an email address.
AFAIK, there's no way to do what you want using any type of postfix or
postfix add-on software. A bunch of log hits could just as easily be
real hits for your string as someone playing with you.
What you need is more intelligence in your app, not better mail server
security.
A good place to start would be to model your app after syslogd, which
will report "last message repeated xxxx times", so instead of becoming a
DDOS attack on your intended recipients, they would get a single email
that says "Found string '<your string>" 34,100 times in the last 20 minutes"
In any case, this isn't a postfix problem.
Terry
