{"id":1734,"date":"2011-01-05T16:51:44","date_gmt":"2011-01-05T14:51:44","guid":{"rendered":"http:\/\/www.limilabs.com\/blog\/?p=1734"},"modified":"2024-03-11T11:29:43","modified_gmt":"2024-03-11T09:29:43","slug":"i-have-problems-issuing-imap-pop3-smtp-command","status":"publish","type":"post","link":"https:\/\/www.limilabs.com\/blog\/i-have-problems-issuing-imap-pop3-smtp-command","title":{"rendered":"I have problems issuing IMAP, POP3 or SMTP command"},"content":{"rendered":"\n

Mail.dll is a rock solid product<\/a>, however most email servers don’t follow RFC specifications rigorously. In the following few steps we’ll help you gather the information we need to make Mail.dll IMAP and POP3 clients better.<\/p>\n\n\n\n

If you have problems parsing a message please go here<\/a>.<\/p>\n\n\n\n

Prerequisites<\/h2>\n\n\n\n

First please check if you have the latest version<\/strong> installed. You can always download the latest version of Mail.dll email component and release notes<\/a> here.<\/p>\n\n\n\n

Identify command<\/h2>\n\n\n\n

Please identify the command\/set of commands that cause problems.<\/p>\n\n\n\n

Turn on logging<\/h2>\n\n\n\n

Enable logging for Mail.dll clients:<\/p>\n\n\n

\n\/\/ C# version:\n\nLog.Enabled = true;\n\n<\/pre><\/div>\n\n
\n' VB.NET version:\n\nLog.Enabled = True\n\n<\/pre><\/div>\n\n\n
You can observe standard Visual Studio\u2019s trace output window (View\/Output\/Show output from: Debug) or add a custom listener to Trace.Listeners<\/em> collection.<\/p>\n\n\n
\n
\"\"<\/figure><\/div>\n\n\n
You can also enable logging using App.config<\/em> file:<\/p>\n\n\n
\n<?xml version="1.0" encoding="utf-8" ?>\n<configuration>\n    <system.diagnostics>\n      <switches>\n        <add name="Mail.dll" value="True" \/>\n      <\/switches>\n    <\/system.diagnostics>\n<\/configuration>\n\n<\/pre><\/div>\n\n\n
log4net<\/h2>\n\n\n\n
If you are using the latest version of log4net.dll, Mail.dll is going to use log4net instead of Trace<\/em> class. Please refer to log4net manual on how to capture log entries.<\/p>\n\n\n\n
Please remember that even when using log4net, you need to enable logging by setting “Limilabs.Mail.Log.Enabled = True” or be setting Mail.dll<\/em> boolean switch in App.config file.<\/p>\n\n\n\n
Log to file<\/h2>\n\n\n\n
You can create your custom TraceListener <\/em>that writes log to file:<\/p>\n\n\n
\n\/\/ C# version:\n\ninternal class MyListener : TextWriterTraceListener\n{\n    public MyListener(string fileName)\n        : base(fileName)\n    {\n    }\n\n    public override void Write(string message, string category)\n    {\n        if (category == \"Mail.dll\")\n            base.Write(message, category);\n    }\n\n    public override void WriteLine(string message, string category)\n    {\n        if (category == \"Mail.dll\")\n            base.WriteLine(message, category);\n    }\n}\n<\/pre><\/div>\n\n
\n' VB.NET version\n\nFriend Class MyListener\n\tInherits TextWriterTraceListener\n\tPublic Sub New(fileName As String)\n\t\tMyBase.New(fileName)\n\tEnd Sub\n\n\tPublic Overrides Sub Write(message As String, category As String)\n\t\tIf category = \"Mail.dll\" Then\n\t\t\tMyBase.Write(message, category)\n\t\tEnd If\n\tEnd Sub\n\n\tPublic Overrides Sub WriteLine(message As String, category As String)\n\t\tIf category = \"Mail.dll\" Then\n\t\t\tMyBase.WriteLine(message, category)\n\t\tEnd If\n\tEnd Sub\nEnd Class\n<\/pre><\/div>\n\n\n
…then add it to Listeners <\/em>collection:<\/p>\n\n\n
\n\/\/ C# version:\n\nLog.Enabled = true;\nTrace.Listeners.Add(new MyListener(@\"c:\/mail_log.txt\"));\nTrace.AutoFlush = true;\n\n<\/pre><\/div>\n\n
\n' VB.NET version:\n\nLog.Enabled = True\nTrace.Listeners.Add(New MyListener(\"c:\/mail_log.txt\"))\nTrace.AutoFlush = True\n\n<\/pre><\/div>\n\n\n
Log.WriteLine<\/h2>\n\n\n\n
Log<\/em> class exposes WriteLine<\/em> event. You can use that event to subscribe your own logging library:<\/p>\n\n\n
\n\/\/ C#\n\nLog.WriteLine += Console.WriteLine;\n<\/pre><\/div>\n\n
\n' VB.NET\n\nLog.WriteLine += Console.WriteLine\n<\/pre><\/div>\n\n\n
Reproduce the problem<\/h2>\n\n\n\n
Perform the operations that cause problems, and save the log to file.
You can remove username and password, but please do not modify the file<\/strong> extensively. If you do, it may be impossible to reproduce the issue.
In particular do not change new line format nor encoding.<\/p>\n\n\n\n
Additional information<\/h2>\n\n\n\n
Please answer following questions:<\/p>\n\n\n\n