I "upgraded" to Debian testing with courier-mta 0.65.0 on one server
about 6 months ago and courier stopped working with strange network
errors so I moved that mail host to another non-Debian box. Today I
finally found a solution after seeing this and some more googling...
# strace testmxlookup debian.org
[...]
sendto(3, "IC\1\0\0\1\0\0\0\0\0\0\6debian\3org\0\0\17\0\1", 28, 0,
{sa_family=AF_INET6, sin6_port=htons(53), inet_pton(AF_INET6,
"::ffff:127.0.0.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
ENETUNREACH (Network is unreachable)
[...]
edit /etc/sysctl.d/bindv6only.conf
change net.ipv6.bindv6only = 1 to 0
invoke-rc.d procps restart
This setting only affected courier, all other services seemed to
work just fine.
My question is how to configure courier-mta to work with the above
default net.ipv6.bindv6only = 1 setting for when Debian testing
becomes stable and I go to upgrade other servers?
--markc
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
