0 votes
by (120 points)
edited
C:\Program Files\Rebex Components 2012 R2\samples\bin>pop3download  unsecure 58.
68.254.103 -username postmaster@del-illumination.com -password h2i9b9z8
Connecting Unsecure to 58.68.254.103:110...
Authorizing as postmaster@del-illumination.com...
Error occured: bad login (-17)

Rebex.Net.Pop3Exception: bad login (-17)
   at Rebex.Net.Pop3.1zLrkA(Boolean , Boolean , String& )
   at Rebex.Net.Pop3.2Dt7i1Z(String , Boolean , Boolean )
   at Rebex.Net.Pop3.1toiKt(String , String , Pop3Authentication , GssApiProvide
r )
   at Rebex.Net.Pop3.Login(String userName, String password, Pop3Authentication
method)
   at Rebex.Net.Pop3.Login(String userName, String password)
   at Rebex.Samples.PopDownload.Program.Main(String[] args)
Disconnecting...

C:\Program Files\Rebex Components 2012 R2\samples\bin>

use outlook or foxmail soft is ok!

Applies to: Rebex Secure Mail

1 Answer

0 votes
by (134k points)
edited

It looks like this server's implementation of CRAM-MD5 authentication is broken. Both Outlook and FoxMail try classic cleartext authentication instead and this works in Rebex POP3 as well. You just need to explicitly specify the authentication method in the Login method call. In the Pop3Download sample's source code, find the following line:

    client.Login(config.User, config.Password);

And add Pop3Authentication.ClearText argument:

    client.Login(config.User, config.Password, Pop3Authentication.ClearText);

This should solve the issue. We will add a workaround for it to the next release. Thanks for reporting this!

Update: The workaround is available in Rebex Secure Mail 2012 R3. With this release, it's no longer necessary to explicitly specify Pop3Authentication.ClearText.

...