[Mimedefang] Ignoring sendmail aliases

[Les Mikesell]

Kelly Jones wrote:
> I just realized I never mentioned my real problem in my original
> message (aside from being scatterbrained, apparently).
> 
> The problem: sendmail rejects the "RCPT TO:" with a user unknown. It
> then (known bug) passes it along to mimedefang, where I OK it, but
> it's too late:
> 
> == CUT HERE ==
> 
> Oct 27 22:46:46 devmx sm-mta[17796]: m9RMkjoM017796: <-- RCPT
> TO:<foo at xyz.com>
> 
> Oct 27 22:46:46 devmx sm-mta[17796]: m9RMkjoM017796: --- 550 5.1.1
> <foo at xyz.com>... User unknown
> 
> Oct 27 22:46:46 devmx sm-mta[17796]: m9RMkjoM017796:
> <foo at xyz.com>... User unknown
> 
> Oct 27 22:46:46 devmx sm-mta[17796]: m9RMkjoM017796:
> milter=mimedefang, action=rcpt, continue
> 
> Oct 27 22:46:46 devmx sm-mta[17796]: m9RMkjoM017796: Milter: rcpts:
> <foo at xyz.com>
> 
> == CUT HERE ==
> 
> How do I tell sendmail to stay out of the validating-recipients business?


define(`MAIL_HUB', `esmtp:othermachine.yourdomain.com')
But unless you want them sent there, be sure to redirect or reject 
everything.


> I'm pulling both the valid recipients and their "true" delivery
> addresses from LDAP. I realize sendmail can do this directly, but
> there's a lot of potential in having mimedefang do it (eg, one-use
> addresses, expiring addresses, addresses that only work after you've
> validated on a website, etc)

Wouldn't it be just as easy to update the aliases db on the fly?

-- 
   Les Mikesell
    les at futuresource.com