Skip to main content

Admin Notes: How to debug SMTP task

Sometimes things go wrong.   They just don't work.  For me, it was when someone complained that their emails weren't getting through to a mailbox, from a specific client.

Sure enough all I saw in the mail logs was:
11/18/2010 11:00:27 AM SMTP Server: connected
11/18/2010 11:00:28 AM SMTP Server: disconnected. 0 message[s] received
Yeah.   Really useful.

So, off to find out why.   First step, IBM support site.  And, I found what I was looking for: Domino Router notes.ini debug parameters for SMTP

The basic premise is this:  There are 2 debug parameters that will be useful.

SMTPDebug - This parameter can be set to enable the capture of inbound SMTP protocol conversations. This is for all messages received by the SMTP listener from all clients and servers via the SMTP protocol.
Possible values are:
1. Enable minimal logging of the SMTP listener
2. Enable information logging of data sent and received along with some additional debugging information. This setting indicates commands and responses being received/sent along with the number of bytes being transmitted, but does not include the text that is transmitted.
3. Enable verbose logging of data sent and received. Along with the information recorded at setting 2, this level shows the actual text received/sent via SMTP. Note that this does not include the text body of messages.
4. This is the most verbose you will get for logging (note that this is an undocumented value -- the documentation only lists up to 3, which is strange, as it is documented on the IBM support site...).
I, of course, jumped right to option 4.

SMTPDebugIO - Enables the logging of all data received by the SMTP listener task.
0. No logging
1. Number of bytes sent and received during the SMTP conversation
2. There is no number 2.
3. Logs all data received by the SMTP task
4. RFC822 data (all message data)
Again, I went for option 4.

I set the parameters through the Domino Server Console (You can do it through Domino Administrator, or directly at the server console) using the Set Config command.  In this case:
set config SMTPDebug=4
set config SMTPDebugIO=4
Now, send in test message yourself to see what you should see:

(names changed to protect the innocent)

You have a lot more information now to figure out why the message isn't being received.  Just don't forget to disable the 2 debug settings later using the following commands:
set config SMTPDebug=1
set config SMTPDebugIO=0


Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X