Matthias Andree writes:
Sam Varshavchik <mrs...@courier-mta.com> writes:
Matthias Andree writes:
1.3.8.1 logs like this:
imapd-ssl: Connection, ip=[::ffff:127.0.0.1]
imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1]
imapd-ssl: Connection, ip=[::ffff:192.168.0.1]
imapd-ssl: LOGOUT, ip=[::ffff:192.168.0.1]
1.3.8.2 logs like this (same source IPs in same order). imapd-ssl:
Connection, ip=[::6833:1200:808b:408]
imapd-ssl: LOGOUT, ip=[::6833:1200:808b:408]
Can't reproduce this one, with or without the IPv6 stack loaded. See if this
still happens if the IPv6 stack is not loaded. --
I tried this again, here's what I found (summary first, details below):
With IPv6 loaded:
1.3.8.1 SuSE Linux 7.0 Duron gcc 2.95.2 TCPREMOTEIP OK
1.3.8.2 SuSE Linux 7.0 Duron gcc 2.95.2 TCPREMOTEIP broken
1.3.8.2 SuSE Linux 7.0 Duron gcc 3.0 TCPREMOTEIP broken
1.3.8.2 FreeBSD 4.3 K6-II gcc 2.95.3 TCPREMOTEIP OK, but DNS lookup fails
Compiled and run without IPv6 loaded:
1.3.8.2 SuSE Linux 7.0 Duron gcc 3.0 TCPREMOTEIP OK (IPv6 style)
SuSE Linux 7.0 uses glibc 2.1.3.
Would sending in some config.h files help, and if so, which ones do you
need?
No. This looks like a bug somewhere in the code, and not a configuration
issue. This one needs to be debugged.
I'm going to try some of the boxes on Sourceforge's compile farm, and see if
I can reproduce it...
4 messages in net.sourceforge.lists.courier-users[courier-users] Re: Update Courier-IM...
