MAILBEE POP3 SMTP WEBMAIL IMAP4 POP IMAP EMAIL COMPONENT VB ASP ACTIVEX COM VBA OCX NET .NET C# VB.NET ASP.NET DOWNLOAD QUEUE SSL SECURITY CENSOR ACCESS PARSER C++ DLL CONTROL LIBRARY MIME INTERFACE

MailBee.NET POP3

AfterLogic Forum : MailBee.NET POP3

Topic: Login failure due to Capa error

Author

Message

<< Prev Topic | Next Topic >>

dshirah
Newbie
Newbie

Joined: 20 January 2008
Location: United States
Online Status: Offline
Posts: 2

Posted: 20 January 2008 at 4:48pm \| IP Logged

First, so far I'm loving this component.

Second, when trying to connect to my client's email account hosted by Hostdepartment.com I get the following exception:

"The particular item of the response data cannot be parsed. The response string: .."

I telnetted to the server and tried a Capa and received back only a "."

So it appears Capa is not supported.

My next step was to try every single one of the authentication methods with the option set to try only that one. The same exception was received across the board. Since Outlook connects up nice and easy, I know it can be done. Obviously I'm missing a step somewhere.

Any thoughts?

Thanks

Don

Andrew
AfterLogic Support

Joined: 28 April 2006
Location: United States
Online Status: Offline
Posts: 1189

Posted: 21 January 2008 at 2:14am \| IP Logged

We've just tried to telnet Hostdepartment.com and got the following result:

Code:

+OK <53557.1200908994@mail.hostdepartment.com>

CAPA

-ERR authorization first

+OK

This means CAPA is not supported by the POP3 server at all. Also, we tried to connect to the same POP3 server via MailBee.NET Objects using random credentials (just to get the exception, not to log in) and got the following log file:

Code:

[12:50:29.85] [INFO] Assembly version: 3.0.0.65.

[12:50:29.80] [INFO] Will resolve host "Hostdepartment.com".

[12:50:29.97] [INFO] Host "Hostdepartment.com" resolved to IP address(es) 65.19.185.222.

[12:50:29.97] [INFO] Will connect to host "Hostdepartment.com" on port 110.

[12:50:30.49] [INFO] Socket connected to IP address 65.19.185.222 on port 110.

[12:50:30.91] [RECV] +OK <53281.1200908868@mail.hostdepartment.com>\r\n

[12:50:30.93] [INFO] Connected to mail service at host "Hostdepartment.com" on port 110 and ready.

[12:50:30.94] [INFO] Get the list of POP3 capabilities via CAPA command.

[12:50:30.96] [SEND] CAPA\r\n

[12:50:31.39] [RECV] -ERR authorization first\r\n

[12:50:31.42] [INFO] Warning: The server does not support CAPA command. POP3 pipelining will not be available. The server responded: -ERR authorization first.

[12:50:31.42] [INFO] Get the list of advertized SASL authentication methods via AUTH command.

[12:50:31.44] [SEND] AUTH\r\n

[12:50:31.88] [RECV] -ERR authorization first\r\n

[12:50:31.88] [INFO] Warning: The server does not support AUTH command. SASL authentication will not be available. The server responded: -ERR authorization first.

[12:50:31.89] [INFO] Will login as "jdoe".

[12:50:31.89] [INFO] Will try APOP authentication.

[12:50:31.91] [SEND] APOP jdoe a3ca45f73f9c21cdb98c90bb9252b0e3\r\n

[12:50:32.34] [RECV] -ERR authorization failed\r\n

[12:50:32.44] [INFO] Error: The server has responded with negative reply. The server responded: -ERR authorization failed.

[12:50:32.44] [INFO] Warning: Socket connection was aborted by remote host.

[12:50:32.45] [INFO] Will disconnect from host "Hostdepartment.com".

[12:50:32.45] [INFO] Disconnected from host "Hostdepartment.com".

The log doesn't indicate that APOP authentication type is not supported. However, it also doesn't indicate that it's supported. The only way to check it is using valid credentials.

Do you have an antivirus/firewall/antispam system installed on the workstation you're trying MailBee.NET Objects from? If so, please try to temporarily disable it for testing purpose. Some applications of such type act as POP3 proxies that may cause various problems in communicating between POP3 server and client.

Could you please enable logging POP3 session into a file, reproduce the issue and provide us with the log file for examination? You can enable logging as follows:

[C#]

Code:

Smtp pop = new Pop3();

pop.Log.Enabled = true;

pop.Log.Filename = @"C:\log.txt";

[Visual Basic]

Code:

Dim pop As New Pop3

pop.Log.Enabled = True

pop.Log.Filename = "C:\log.txt"

Please make sure the application has permission to write into the specified location.

You can send us the log via Request Support Form.

It would be also very helpful if you provide us with a test account on Hostdepartment.com server the issue can be reproduced on.

Best regards,
Andrew

dshirah
Newbie
Newbie

Joined: 20 January 2008
Location: United States
Online Status: Offline
Posts: 2

Posted: 23 January 2008 at 12:20pm \| IP Logged

Thanks. I have submitted a support request with and included a test account. As we figure this out, I update this thread in case anyone outside wants to follow along.

Don

Andrew
AfterLogic Support

Joined: 28 April 2006
Location: United States
Online Status: Offline
Posts: 1189

Posted: 24 January 2008 at 4:19am \| IP Logged

We've reproduced the issue and are going to fix it in future releases of MailBee.NET Objects.

MailBee.NET Objects sends "CAPA" command to determine what transmission and authentication mode should be used.

To avoid requesting "CAPA" command, application should not use pipelining and should use a predefined authentication method.

As a quick workaround, please try to use the following code lines for connecting and logging to your POP3 server:

[C# code]

Code:

pop.Connect("***removed***", 110, false);

pop.Login("***removed***", "MailBee", AuthenticationMethods.Regular);

[VB.NET code]

Code:

pop.Connect("***removed***", 110, False)

pop.Login("***removed***", "MailBee", AuthenticationMethods.Regular)

We implemented a similar sample which successfully connected to the account you provided, CAPA was not requested and there was no exception thrown.

Best regards,
Andrew

Alex
AfterLogic Support

Joined: 19 November 2003
Online Status: Offline
Posts: 2206

Posted: 24 January 2008 at 9:57am \| IP Logged

Further investigation has shown that the problem is probably not connected with MailBee.NET Objects.

We tried to connect to your server and got the following log:

Code:

[20:52:37.65] [INFO] Assembly version: 3.0.2.79.

[20:52:37.64] [INFO] Will resolve host "mail.myghiaccount.com".

[20:52:37.65] [INFO] Host "mail.myghiaccount.com" resolved to IP address(es) 66.160.178.160.

[20:52:37.65] [INFO] Will connect to host "mail.myghiaccount.com" on port 110.

[20:52:37.94] [INFO] Socket connected to IP address 66.160.178.160 on port 110.

[20:52:38.20] [RECV] +OK  <11501.1201196977@massachusetts.worldispnetwork.com>\r \n

[20:52:38.21] [INFO] Connected to mail service at host "mail.myghiaccount.com" on port 110 and ready.

[20:52:38.21] [INFO] Get the list of POP3 capabilities via CAPA command.

[20:52:38.21] [SEND] CAPA\r\n

[20:52:38.48] [RECV] +OK capability list follows\r\n.\r\n

I.e. CAPA is working correctly.

However, the log you sent us (which is not working) contains "+OK AVG POP3 Proxy Server" greeting from the mail server.

This means your have some software on your computer installed (AVG) which intercepts POP3 traffic but contains some bugs in it and does not correctly process CAPA command. You should disable such software if you want to take advantage of all features of MailBee.NET Objects.

The scenario above is quite common since many third-party utilities support only those POP3 commands which are used by Outlook and Thunderbird. Other commands can be not supported or badly supported.

Regards,
Alex

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

Printable version

Forum Jump

.NET Components

ActiveX Components

Web scripts

Solutions

MailBee.NET POP3