Sending mail to /dev/null without scanning

[Ken A]

Ah, well that's a spam magnet you are engineering! Anyhow, you can 
change RELAY to DISCARD for the desired effect.
Ken
Pacific.Net


Cameron B. Prince wrote:
> Hi Ken,
> 
> Thanks for your reply... This does not do what I need.
> 
> I don't want to send a bounce. I want the sender to have no idea that the
> address isn't good.
> 
> Cameron
> 
>> -----Original Message-----
>> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-
>> bounces at lists.mailscanner.info] On Behalf Of Ken A
>> Sent: Friday, January 27, 2006 6:08 PM
>> To: MailScanner discussion
>> Subject: Re: Sending mail to /dev/null without scanning
>>
>> Put entries in your access table instead.
>>
>> To:bob at mydomain.com     RELAY
>> To:tim at mydomain.com 	RELAY
>> #
>> # Default Entry to Reject all others
>> #
>> To:mydomain.com    ERROR:5.1.1:550 User unknown
>>
>> That way sendmail will reject them for you and mailscanner will never
>> see them. (don't forget to "makemap hash access < access")
>>
>> Ken
>> Pacific.Net
>>
>>
>> Cameron B. Prince wrote:
>>> Hey guys,
>>>
>>> I have been getting a lot of emails coming in with CC's to every-name-
>> known
>>> to-man at mydomain.com. It bothered me that so many of my mail server's
>>> resources and my internet connection were both being used to send
>> bounces
>>> and that this could also be an attempt to determine valid addresses.
>>>
>>> I did some research and came up with creating an alias like this:
>>>
>>> garbage: /dev/null
>>>
>>> Then in my virtusertable I have something like this:
>>>
>>> bob at host.com	bob
>>> tim at host.com	tim
>>> @host.com		garbage
>>>
>>> It works, but now instead of bouncing, the messages are all scanned and
>> then
>>> sent to /dev/null. I need to configure MailScanner so that it doesn't
>> scan
>>> these messages destined for oblivion.
>>>
>>> Jan 27 17:41:00 p2 sendmail[14975]: k0RNeu33014975:
>>> from=<MolliesfDuttonc at netzero.net>, size=1421, class=0, nrcpts=1,
>>> msgid=<aristotelean.combustion at g42Ls1T6.23.com>, proto=SMTP, daemon=MTA,
>>> relay=[221.0.209.135]
>>> Jan 27 17:41:00 p2 MailScanner[14330]: New Batch: Scanning 1 messages,
>> 1883
>>> bytes
>>> Jan 27 17:41:01 p2 MailScanner[14330]: Virus and Content Scanning:
>> Starting
>>> Jan 27 17:41:01 p2 MailScanner[14330]: Uninfected: Delivered 1 messages
>>> Jan 27 17:41:01 p2 MailScanner[14330]: Logging message k0RNeu33014975 to
>> SQL
>>> Jan 27 17:41:01 p2 MailScanner[14294]: k0RNeu33014975: Logged to
>> MailWatch
>>> SQL
>>> Jan 27 17:41:01 p2 sendmail[14980]: k0RNeu33014975: to=/dev/null,
>>> ctladdr=<henderson at mydomain.com> (8/0), delay=00:00:03, xdelay=00:00:00,
>>> mailer=*file*, pri=121421, dsn=2.0.0, stat=Sent
>>>
>>> I setup a ruleset like this in the scan.messages.rules file:
>>>
>>> To:       /dev/null  no
>>> FromOrTo: default    yes
>>>
>>> I have this in the .conf file
>>>
>>> Scan Messages = %rules-dir%/scan.messages.rules
>>>
>>> MailScanner continues to scan the mail even though the to line states "
>>> to=/dev/null"
>>>
>>> Can anyone tell me if this is possible and what I may be doing wrong?
>>>
>>> Thanks,
>>> Cameron
>>>
>> --
>> MailScanner mailing list
>> MailScanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website!
>