Bernd Wurst writes:
Hi.Now, finally, we have a production-ready native IPv6 connection. Sam, you added SOURCE_ADDRESS_IPV6 this June, that was an important feature, thank you.But at the moment, I cannot get it to work.The machine is a server running courier for years, so basic configuration is fine, I am sure to use the correct config file directory and so on.I upgraded to courier-0.65.2, which should contain this change. Logfile states:Dec 18 15:47:09 zucker courierd: Courier 0.65.2 Copyright 1999-2008 Double Precision, Inc.Then, I set in /etc/courier/courierd config file the following lines: SOURCE_ADDRESS="78.46.69.5" SOURCE_ADDRESS_IPV6="2a01:4f8:120:5201::2" As courier always prefers IPv4 (why?), I set a custom route in esmtproutes: mehl.schokokeks.org: [2a01:4f8:121:1ffe::2]Then, I sent a test message to [email protected]. The header of that message, after receipt, contains:Received: from zucker.schokokeks.org ([2a01:4f8:120:5201:1:1102:0:161]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mehl.schokokeks.org with ESMTPS; Sat, 18 Dec 2010 15:45:58 +0100 id 0000000000002416.000000004D0CC926.00000790So the source address was 2a01:4f8:120:5201:1:1102:0:161, not 2a01:4f8:120:5201::2 as I configured.Both addresses are configured on eth0 of that machine. Do you have any clue why this does not work?
The only thing that comes to mind is that this change to courierd requires Courier to be restarted. Did you restart it?
pgpsP0PJZavVk.pgp
Description: PGP signature
------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
