Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack

2011-03-09 Thread Sam Varshavchik
Bernd Wurst writes: Hi Sam. It's ridiculous. I'm not a native english speaker, perhaps this is the reason that you are not willing to understand the key point. Am Mittwoch, 9. März 2011, um 00:12:49 schrieb Sam Varshavchik: Bernd Wurst writes: in this case, is blocked via greylisting by

Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack

2011-03-09 Thread Bernd Wurst
Hi Sam. Am Mittwoch, 9. März 2011, um 13:05:34 schrieb Sam Varshavchik: First try CAN establish a TCP connection and then is blocked by greylisting. All further tries run into a timeout because IPv6 is broken. There is no further try on the IPv4 address. I don't know what to tell you. Each

Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack

2011-03-09 Thread Sam Varshavchik
Bernd Wurst writes: Okay. Which component cares about connecting to the secondary MX (or any other available IP address) when TCP connection to the primary fails? As I understood, the connection to the secondary MX should take place immediately after the second try on the first MX fails on