Possible issue with IMAP and IPv6

So I say this is an issue because errors are logged in the imap4 log file, but it doesn’t seem to break anything.

Here is a snippet of my log file with just the IP address and emails changed:


tcpserver: pid 6794 from 2601:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
tcpserver: ok 6794 server.myserver.com:2607:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:993 :2601::xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx::58652
INFO: Connection, ip=[2601::xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]
vmysql: error creating table 'relay': Table 'relay' already exists
vmysql: sql error[7]: Data too long for column 'ip_addr' at row 1
INFO: LOGIN, [email protected], ip=[2601::xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx], protocol=IMAP

When an IPv4 connects it looks like this:


tcpserver: pid 8727 from xx.xx.xx.xx
tcpserver: ok 8727 server2.justechnology.com:::ffff:yy.yy.yy.yy:993 :::ffff:xx.xx.xx.xx::59326
INFO: Connection, ip=[xx.xx.xx.xx]
INFO: LOGIN, [email protected], ip=[xx.xx.xx.xx], protocol=IMAP

Hi Justin

Good catch, and it would not break anything as it is just logging

I’ll forward the thread to Iw so the database schema can be altered to make the ip-add table accept the correct length for an IPv6 address

Many thanks

John

I see a bug report already submitted for this issue and I’ve brought this to the attention of the development team.