At 05:29 PM 9/7/2007, Mark Martinec wrote:
> > Of additional note, when I add a little more debugging code to
> > amavisd in the penpals sections, it seems regardless if a domain is
> > local or not (or even in cases where @local_domain_maps is undefined
> > i find the following:
> >
> > lookup(0,
Nate,
> Of additional note, when I add a little more debugging code to
> amavisd in the penpals sections, it seems regardless if a domain is
> local or not (or even in cases where @local_domain_maps is undefined
> i find the following:
>
> lookup(0,$sender,@{ca('local_domains_maps')}) ALWAYS retu
Nate,
> In this setup, there are thousands of domains being scanned, and
> amavis as well as postfix utilize a mysql db to determine where
> to forward the email after it's scanned via a postfix transport
> table. With this setup, I typically leave @mynetworks and
> @local_domains_maps undefined
Of additional note, when I add a little more debugging code to
amavisd in the penpals sections, it seems regardless if a domain is
local or not (or even in cases where @local_domain_maps is undefined
i find the following:
lookup(0,$sender,@{ca('local_domains_maps')}) ALWAYS returns Y
This is
I know this must be something I've overlooked as it just seem so
silly that penpals would work in reverse order.
All outbound email from my location sends through a SMTP server which
forwards to the AMAVIS filtering server before leaving the
network. Inbound email comes into the AMAVIS server,
