--On Tuesday, April 30, 2002 7:42 PM -0400 James Ralston <[EMAIL PROTECTED]> wrote:
> For recent versions of sendmail, you can use the spamfriend/spamhater > hooks in the accessdb to implement either one of these policies: > > 1. Incoming mail from RBL-listed sites is rejected, except for > spamfriend users. > > 2. Incoming mail from RBL-listed sites is rejected only for > spamhater users. > > You'll need to design a method for users to indicate their choice, > though. > > Solutions probably exist for other versions of sendmail, and other > MTAs. Seen Many Solutions, Fortunatly a Aware Administrator can determine where the spam comes from. Because more times then not, the spammer tries to send the mail directly to you. Avoiding any and all relays, but then there are those that are getting smarter. > I'm not the person to whom you addressed this question, but I'll > answer it anyway: > > Because the receiving MTA is the only entity which knows the IP > address of the relay. Once the receiving MTA hands off the message to > another MTA, that information is lost. > > Trying to determine the IP address of the relay by screen-scraping the > receiving MTA's Received headers is an ugly, disgusting, error-prone, > shameful hack. It does not belong in Sieve; it does not belong in > anything. > > If you want to accept/block mail based on the relay it comes from, do > it at the MTA. Don't tag at the MTA. Don't file at the MTA. Either > accept or reject, period. Provide a way for individual users to > control the accept/reject behavior for mail destined to them. > > If you want to filter mail based on content, do it at the local > (final) delivery agent. Tag or file based on the content, but don't > reject it. Provide a way for individual users to customize the > filters and their actions. I dont think I could have said it better myself, in fact i know i couldnt. I'm just glad it was said. Thank you! Sincerely, Scott M Likens
