From: William Kimball, Jr. (popauth3teamdelsol.com)
Date: Wed Jun 09 2004 - 10:16:57 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

You are absolutely right! It's ironic that I figured it out when I was in the shower this morning and your message in
my in-box validated the theory. Only one catch: There *is* a separate mechanism that is triggering "FILTER" for mail
originating outside the LAN, but the routing directive attached to it is null (based on postfix documentation, this is
normal). The syntax of the lookup is:

my-domain.tld FILTER amavisd:

This was working for a looooong time before I started playing with the idea of a second server for content filtering.
My assumption now is that "amavisd:" *without* a routing directive attached to it, like "amavisd:[10,10,10,10]:10024" is
probably triggering the loop-back, being interpreted as something like, "amavisd:my_external_ip_address:25". This has
to be related to inserting the new entries in master.cf and/or the new content_filter entry in main.cf (I normally don't
use this).

I'll toy with this today, but I won't have much time because there's a lot on the stack for me right now. Thanks for
your insight!

--
William Kimball, Jr.
"Programming is an art-form that fights back!"
----- Original Message -----
From: "John Groseclose" <iaincaradoc.org>
To: "William Kimball, Jr." <popauth3teamdelsol.com>
Sent: Wednesday, June 09, 2004 7:07 AM
Subject: Re: 2-server setup for MTA + Content Filtering?

: > I can't do that without restoring the entirety of the "looping"
: >config from yesterday's backup. I'm leery about doing
: > so because, well, it doesn't work. :) If it's _absolutely_
: >necessary that we do this, then I will -- tomorrow (I'm
: > about to pass out, so I'm heading out). If we don't _have_ to
: >revisit this, then I'm ready to try something completely
: > different with a fresh lead on some working documentation for what
: >I'm attempting to accomplish.
:
: I know the feeling. I had to get some sleep too.
:
: The "FILTER" entry in the logs appears to indicate that you've got
: some sort of a lookup that's triggering the filter, not just passing
: everything through it, and I'm betting that there's also a routing
: directive attached to it that's causing the loop.
:
:

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]