[pfx] Re: content_filter on ipv6 ?

Wietse Venema via Postfix-users <[email protected]>
Newsgroups gmane.mail.postfix.user
Message-ID <[email protected]>
lejeczek via Postfix-users:
> glibc-2.39-133.el10
> 
> I do not suppose postfix, messages already queued, would 
> insist to deliver to the filter set prior to change from 
> ipv4 to ipv6 - as oppose to new, those arriving after the 
> change? Because...
> postfix does deliver a ok to ipv6 those "new" messages..

The content_filter value is stored in the queue file. This is how
the Postfix queue manager finds out if, and how, it needs to override
the routing for a recipient address.

> I've a peculiar "broken" amavis - I read somewhere that it 
> might be due to perl module not getting ipv6 soon enough - 
> which does not bind to ipv6 after OS boot, later if 
> re-started/loaded does do bind.
> 
> I'm only able to try to reproduce it, when cluster gets 
> rebooted, thus once in a while.

In that case, when Postfix and Amavis support IPv4, why not leave
the content_filter setting at IPv4?

	Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.