On Thu, Dec 23, 2010 at 05:15:06PM -0500, Wietse Venema wrote:
> > > Yes, that was precisely what I had overlooked. I think it used to work
> > > differently,
> >
> > This has not changed since at least Postfix 1.0, the design of the
> > queue manager is fundamentally based around transport:nexthop pairs.
> >
> > I would expect that it in fact goes back further, but my life with
> > Postfix started with 1.1 snapshots.
>
> Didn't we change the hop-less filter semantics, and removed the
> "empty nexthop" == myhostname override, for the purpose of
> sender IP address reputation management?
Oops, have not looked at this part of 2.7 too closely yet. I always
specify a fixed nexthop when that's what I want. Indeed the behaviour
changes in 2.7.
20010117
Cleanup: when a content_filter parameter or FILTER command
specifies an empty next-hop destination, the queue manager
now uses the recipient domain instead of $myhostname. Specify
"default_filter_nexthop = $myhostname" for compatibility
with Postfix 2.6 and earlier, or specify a non-empty next-hop
filter destination. Files: *qmgr/qmgr_message.c proto/access,
proto/header_checks, proto/postconf.proto, proto/FILTER_README.
--
Viktor.
