I have a question that has as of yet remained unanswered.
Is it possible to filter or forward mail based on envelope sender and/or 
sender IP.

things I know:
1. I know you can block sender IPs with tcpserver, but that rejects the 
connection, I need to set up an auto-response.
2. I know I can use my own rbl database w/ rblsmtpd, once again, that returns 
error codes, I need to collect some of this bad mail
3. I have seen several anti-spam patches.  see the stuff about error codes -^
4. this would be modestly easy with procmail or similar, but all mail would 
have to be "delivered" to procmail for processing, then back to qmail for 
remote sending.  I don't want the extra load, these are not large machines.
5. qmail offers about 9 million features for filtering by recipient, all I 
need is one or two to filter by sender to make this work.
6. these are relay machines (PRIVATE, spam bad, duh) recipients are not 
local, this is handled in the smtproutes control file.
7. I can't figure out how to use aliases to direct mail based on anything 
about the sender, though it may be painfully simple.


things I need:
1. the ability to not just smtp reject this bad mail, (based primarily on 
envelope sender, but perhaps also sender IP), but to essentially process it 
and dump it to a dummy account with an autoresponder.
2. I DON'T NEED AN AUTORESPONDER, thanks anyway

WHY:
We had been the victim of spammer abuse of our mailserver until I got here, 
because the last admin left it wide open.  OK, I fixed the relaying. Now, we 
are constantly bombarded with spam destined to numerous legitimate internal 
accounts.  RBL you say? No, My company services ~75000 active end-users.  
There are literally thousands of domains that queries/support mails come 
from.  Most of us know that often the server that the mail comes from is 
often not the originator of the mail itself.  As a company, we simply cannot 
arbitrarily block a quantity of mail servers that may end up being the source 
of legitimate mails from our customers (our services are EXTREMELY time 
dependant, and a single mail can be "worth" quite a bit of money to a user). 
So, I am left needing a method to block mail, but still offer an immediate, 
very clear method to tell a sender that their mail did not go through. I do 
not expect all of our users to decipher an smtp error message, I have to 
assume the lowest common denominator.  

Mega thanks in advance to all who read through this damn sob story ;)
and thanks again to those who went through my last few, I love this list.

Mike Culbertson
[EMAIL PROTECTED]

Reply via email to