Hi.
Tonight, I noticed a strange beaviour with courier MTA on IPv6 enabled
destinations.
I misconfigured courier with a SOURCE_ADDRESS_IPV6 that accidentially was not
configured on the interface, so it was not available.
When sending to a peer that has both, IPv4 and IPv6 addresses and
Bernd Wurst writes:
Hi.
Tonight, I noticed a strange beaviour with courier MTA on IPv6 enabled
destinations.
I misconfigured courier with a SOURCE_ADDRESS_IPV6 that accidentially was not
configured on the interface, so it was not available.
When sending to a peer that has both, IPv4 and
Hi.
Am Dienstag 25 Januar 2011, 12:57:37 schrieb Sam Varshavchik:
So it seems like Courier prefers IPv4 over IPv6 only ONE TIME and then,
on retries, only uses IPv6 without fallback to IPv4.
On manual queue flushes, only IPv4 is used, no IPv6.
No. Courier carries over no preference on
Bernd Wurst writes:
Changing SOURCE_ADDRESS_IPV6 requires a restart, which will kill all active
connection.
I did not change and restart but set the specified address on the interface.
Does not matter. Until Courier gets restarted, it's as if no changes have
been made to the
