[Mimedefang] Blocking Dictionary Attacks

[renaud.pascal at atosorigin.com]

On Fri, 5 Jun 2009 13:19:42 -0500
afo cliff <afocliff at gmail.com> wrote:

> Paul:
> 
> I am intrigued by your mention of using filter_recipient.  I did a
> grep on that and can't find it.  Is that part of mimedefang?


 then you mimedefang-filter manpage is b0rken ;-)

# man -P more mimedefang-filter | grep -c filter_recipient
26

 just check this:
-------
# man -P cat mimedefang-filter 2>/dev/null | grep -C 4 filter_recipient | head



FILTERING BY RECIPIENT
       You can define a function called filter_recipient in your filter.  This
       lets  you  reject  messages  to certain recipients, rather than waiting
       until the whole message has been sent.  Note that  for  this  check  to
       take place, you must use the -t flag with mimedefang.


-------

> 
> Thanks for everyone's help.  I was able to get it to work.  I already
> could make it work with access table, but this method does not produce
> rejection notices.  The undocumented exclamation point is the key.
> How I did it:
> 
> access: empty
> 
> aliases:
> bitbucket /dev/null
> 
> local-host-names:
> mydomain.com
> 
> mailertable:
> mydomain.com esmtp:final.mailserver.com
> 
> sendmail.mc:
> 
> define(`SMART_HOST', `final.mailserver.com')dnl
> ...
> define(`MAIL_HUB', `final.mailserver.com')dnl
> FEATURE(`stickyhost')dnl
> define(`_VIRTUSER_STOP_ONE_LEVEL_RECURSION_')dnl
> 
> relay-domains: empty
> 
> virtusertable:
> user1 at mydomain.com !
> @mydomain.com bitbucket
> 
> 
> I added define(`_VIRTUSER_STOP_ONE_LEVEL_RECURSION_')dnl to
> sendmail.mc as a precaution.  Everything worked without it.
> _______________________________________________
> NOTE: If there is a disclaimer or other legal boilerplate in the above
> message, it is NULL AND VOID.  You may ignore it.
> 
> Visit http://www.mimedefang.org and http://www.roaringpenguin.com
> MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
> http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
>