Advanced Troubleshooting with Socketspy
In order to see what is happening you may need to see the actual data stream passing between Mailtraq and the client.
Socketspy is a simple, safe, diagnostic tool that records data. Its use allows you to resolve problems with installations when there is insufficient information in the Mailtraq Event log.
At a convenient time, set it up as described below and do a test of the type that fails, then examine the log file it forms.
Sending Log Files
If it is necessary to send log files to Mailtraq Support, they should be copy & pasted into MS Notepad (and then Zipped up if very large). Do not paste into Word, as Word's formatting can change line breaks.
Listening from the Mailtraq machine
Working with IMAP
To use it you need to divert the port traffic through Socketspy.
In Mailtraq Console, Options | Services
change Mailtraq's IMAP port (normally 143) to an unused port
- say, 3143, temporarily
and run Socketspy
http://resources.mailtraq.com/files/socketspy.zip (139 KB)
on the Mailtraq machine as follows ...
Local Port [ 143]
Remote Address [ 127.0.0.1 ]
Remote Port [ 3143]
.... then click on Listen. When the client connects, Socketspy opens a log window showing all the protocol interactions in both
directions in real time.
You may need to adjust your fire wall temporarily to allow traffic on that port.
You can save the log to disk for later study via its properties menu (right-click on the window).
It is sometimes necessary to manually start the service after you change the port :
Right-click/All Tasks | Start Service.
And it is recommended that after the session is complete and you return the port settings to their original configuration, you should restart Mailtraq to ensure that all the sockets are correctly assigned.
Working with POP3
The procedure is the same as above, but you are working with the POP3 service and Port 110
In Mailtraq Console, Options | Services
change Mailtraq's POP3 port (normally 110) to an unused port
- say, 3110, temporarily
and run Socketspy
http://resources.mailtraq.com/files/socketspy.zip (139 KB)
on the Mailtraq machine as follows ...
Local Port [ 110]
Remote Address [ 127.0.0.1 ]
Remote Port [ 3110]
Listening from the Client Machine
Sometimes it is necessary to examine the data stream from the client's end of the conversation.
Install Socketspy onto the client machine. The procedure is generally the same as above, except:
POP3
POP3
Local Port [ 110]
Remote Address [ 192.168.1.2] <- The local LAN IP address of the Mailtraq machine
Remote Port [ 110]
And you must change the POP3 server setting in the email client (say, Outlook) to be 127.0.0.1
IMAP
The procedure is generally the same, except:
IMAP
Local Port [ 143]
Remote Address [ 192.168.1.2] <- The local LAN IP address of the Mailtraq machine
Remote Port [ 143]
And you must change the IMAP server setting in the email client (say, Outlook) to be 127.0.0.1
Now, when the client does a send and receive the conversation will be intercepted by Socketspy, which will write the log file, as it transfers the connection to Mailtraq.
Listening to a 'Remote POP3 Collector'
Make sure that Port 5110 is not in use on the Mailtraq machine for any other purpose (if it is, then choose another Port number), and it is not blocked by a local firewall. Then configure Socketspy as shown below.
Local Port: [5110]
Remote Address: [pop3.btmail.com] (substitute your actual ISP account here)
Remote Port: [110]
In Mailtraq, create a new POP3 Collector account, generally as shown.
POP3 Server will be: [127.0.0.1:5110]
The Account and Password settings should be as the actual ISP account.
Click the [Listen] Button in Socketspy
Then, enable this POP3 Collector and Disable (uncheck) the normal one.
Socketspy will now write the 'conversation' between Mailtraq and the ISP mailbox.
