Tor-Einar Jarnbjo wrote:
Is there any particular reason for that? The way IP addresses are
handled by the Java API, James must have been implemented on purpose
to only support IPv4 if it is not supporting IPv6. Actually, I've been
running James on an IPv6 enabled server for the last year or so, but
there might very well not yet have been any incoming traffic over the
IPv6 interface.
I had to try this and the only problem I found was, that the JDBC stores
are using varchar(20) for the remote_addr columns in spool and inbox,
which of course is not enough for an IPv6 address. After modifying the
tables, my James installation seems to at least accept SMTP over IPv6:
received: from 2001:a60:XXXX:0:0:0:0:1 ([2001:a60:XXXX:0:0:0:0:1]) by XX
(JAMES SMTP Server 2.3.0) with SMTP ID 427 for <[EMAIL PROTECTED]>; Sat, 5 Jan 2008
12:46:40 +0100 (CET)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
