Marc Perkel wrote:
Not that it is by itself but when combined with other conditions it is
very effective. My theory is that after the message is sent by the virus
sending the quit just takes more time and bandwidth so the spambot just
leaves the connection open on the server side.
But -
Hello Michiel,
Yes, that what I mean. They resolve to 1 IP address. Something like
Apache with virtual domains.
Well, you can't use certs/SSL for virtual hosts sharing the same IP
address in Apache either.
That is bc of catch 22 problem: the requested hostname for vhost is
located in HTTP
Hello Darton,
The best way I've found is to fill out as many free offer and other
advertising gimmick forms as you can find on the web. The sketchier
the company, the better. Google something like multi-level marketing
and you're sure to find some.
I found this one to be the most effective,
W B Hacker wrote:
Marc Perkel wrote:
Not that it is by itself but when combined with other conditions it is
very effective. My theory is that after the message is sent by the virus
sending the quit just takes more time and bandwidth so the spambot just
leaves the connection open on
On Fri, Sep 07, 2007 at 01:06:29PM +0200, [EMAIL PROTECTED] wrote:
Hello Michiel,
Yes, that what I mean. They resolve to 1 IP address. Something like
Apache with virtual domains.
Well, you can't use certs/SSL for virtual hosts sharing the same IP
address in Apache either.
That is bc
Marc Perkel wrote:
Basically most all good email servers are polite and do the quit. Most
all spam bot server don't want to expend the time and bandwidth to be
polite and that can be used in combination with other indicators to
catch spam.
The new 4.68 Exim is a major advancement with
Hello everyone,
So I have this in ACL DATA:
warn set acl_m_sa = ${run {/etc/domeny/testme $message_exim_id $acl_m_user}
{$value} }
log_message = acl_m_user: $acl_m_user
warn continue = {true}
log_message = Testme result for message $message_id: $acl_m_sa
The script is:
