This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Jan 14, 2016, 11:34 AM
21 Posts

IMAP task does not output the client's IP address

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: imap ip
  • Replies: 5

Hi

In my 64-bit Domino 9.0.1 installation on Windows 2008 R2 64-bit the IMAP task does not display the IP address of the connecting client.

Searching the web, I couldn't find enough information about anything relevant. Also, there don't seem to exit any setting about this.

I even created an event handler which runs an agent that receives all the event's data and details. The details didn't include an IP address.

(The details of the event's data can be seen here: http://i.stack.imgur.com/UkGwf.png )

Here's what appears in the server log/console:

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?

 

Thanks in advance

Jan 14, 2016, 1:02 PM
122 Posts
Re: IMAP task does not output the client's IP address
Hello Sam!

Could you try to add the parameters below on NOTES.INI:
log_mailrouting=20
log_sessions=1

The router task must be restarted to take effects.

I hope it helps.

Best Regards!
Rodrigo San Vicente

Jan 15, 2016, 4:28 PM
21 Posts
No luck, yet

Thank you, Rodrigo..

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.

Jan 18, 2016, 8:57 AM
33 Posts
IMAPDebug

set conf IMAPDebug=3          [0,1,2,3,4]
set conf IMAPDebugIO=2      [0,1,2,3,4]

Jan 22, 2016, 2:48 AM
21 Posts
Same thing

Thanks Bryant!

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.

Thanks

Aug 9, 2016, 8:54 PM
196 Posts
POP is much the same issue

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.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal