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 delivery attempt, five minutes apart,
> is   executed by a completely different process, that has no knowledge of
> what happened in some unrelated process, five minutes earlier.

Courier does not log which desstination IP address is used when a TCP 
connection ailure is logged. But In my excerpt, you can see that there is only 
ONE attempt every five minutes. So there is only one and only try to connect. 
I don't know if Courier even tried to reach the secondary MX.


> A courieresmtp client persists for no longer than a minute, in order to  
> recycle connections. Each delivery attempt you logged was from a
> different   process, each.

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 TCP layer. But only one 
connection failure is logged.



We have 0.65.2 on our production system. When I read the changelog, I stumbled 
upon the following changelog-entry:

2011-01-22  Gordon Messmer <[email protected]>

        * rfc1035/rfc1035mksocket.c (rfc1035_mksocket): Set IPV6_V6ONLY
        socket option to OFF for IPv6 sockets, if the system default is on.


Could it be that this fixes my issues? Is this change included in 0.65.3?

Bernd

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to