-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/11 14:43, Wietse Venema wrote:
> This should be possible with one Postfix
> {SNIP}
> No firewalling needed.
To bring closure to this thread and perhaps benefit others in the future:
As part of a defense-in-depth security strategy a strict IP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/11 13:52, Vick Khera wrote:
> What if you do this: eliminate the ability of your mail server to send
> SMTP over IPv4, possibly by removing any IPv4 address from it, or
> firewalling that ability away.
>
> Set up fallback_relay on this host s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/11 13:24, Jeroen Geilman wrote:
> But that is not what you have DONE.
Yes, because evidently the two are mutually exclusive. A relayhost cannot be
defined for only IPv4 traffic nor can it be configured to not effect IPv6
capable traffic.
Es
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/11 13:19, Jeroen Geilman wrote:
> Consider why you have set a global relayhost; apparently, you want ALL mail
> delivered via this one host.
Negative, I want all IPv4-only, non-IPv6 transit capable, mail delivered via
this host.
- --
- -ev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/11 13:02, Wietse Venema wrote:
> The Postfix documentation only describes the features that are
> implemented. Therefore if you can't find something then you can
> safely assume that it is not supported.
Dr. Venema, thank you for your reply.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, I may have a somewhat unique situation regarding an IPv4 relayhost on an
IPv4 and IPv6 enabled Postfix MTA; it seems that even for an IPv6 capable
recipient MTA the IPv4 relayhost is used. Is there a way to bind/enforce the
relayhost to be IPv4