2016-01-08 04:13:14 nimap: edd authentication failure using internet password
2016-01-08 04:13:16 nimap: easter authentication failure using internet password
2016-01-08 04:13:19 nimap: felicity authentication failure using internet password
The IP should appear between the brackets . Can any one confirm that they can see the connecting IMAP client’s IP in their server’s console? Or could this be a bug that needs to be reported to IBM?
As I mentioned earlier, these debug settings are filling the log with an excessive amount of data for every little connection.
Unfortunately that’s not practical at all to leave this setting on all the time, e.g. for collecting statistics about incoming connections.
I will report this to IBM as a bug in the IMAP server, because the behaviour seems to be incorrect (the IP is missing) and because I have tried in many ways to solve it but couldn’t.
The settings you suggested didn’t make a difference. The IMAP task still behaves the same, logs the same.
I’ve also tried these:
Log_MailRouting=40
IMAPDebugIO=4
The debug option gave a lot of information, including the IP of the client, but it also filled the log with too much data for every quick connection.
I was hoping to make the IMAP task report the IP just like how SMTP does (directly on the console, and appropriately in an event handler linked to an agent, for example).
I am actually trying to capture the data by an event handler. But without success so far.
With POP, I have the same difficulty. If I were asked to provide statistics, I would use the debug parameters, and simply grep the results in the console.log to get the IPs of the connecting clients.