Hi all,
I'm managing a couple of mail servers, on which I have installed Spamdyke with
qmail. Everything works great, but I want to further reduce SPAM I receive.
So I thought, why not implement my own spamtrap? I want to create some e-mail
addresses, that will not be used for communication, wh
Could use a .qmail file for each of those spamtrap addresses which
passes the message off to a script which plucks out the sender's IP
address (from the appropriate Received: header) and appends it to your
ip-blacklist-file.
I'd recommend AGAINST using the sender email address as it could resul
Dossy Shiobara wrote:
> Could use a .qmail file for each of those spamtrap addresses which
> passes the message off to a script which plucks out the sender's IP
> address (from the appropriate Received: header) and appends it to your
> ip-blacklist-file.
Because spammers may send mail from legitim
Angus,
Indeed, the support for spamtrap addresses in Spamdyke could be
interesting - my design for such a feature would be a variation on the
recipient blacklist.
A list of "spamtrap-entry" addresses, if seen as an RCPT TO, will cause
the message to be rejected at the "DATA" step. It is NOT w
>From a technical standpoint, it shouldn't be too hard to implement. When
>triggered, the spamtrap filter would just set the CHILD_QUIT flag in
>smtp_filter(), which would cause middleman() to close its connection to qmail
>(so no more commands would be sent to the real mail server). Each filt
Using something like this would be great, if all of the users used webmail
or IMAP on their clients... Unfortunately, most of mine either use POP3 or
I'm simply filtering their e-mail, so there's not really any folders to
search through...
I've often toyed with the spamtrap honeypot idea, using it
