I’ve already tested and reproduced this problem using Aspose.Email for .NET 17.7.
I use Windows 7 Enterprise.
Steps to reproduce:
- Enable FIPS Compliant Algorithms:
1.1. In Control Panel, click Administrative Tools, and then double-click Local Security Policy.
1.2. In Security Settings, expand Local Policies, and then click Security Options.
1.3. Under Policy in the right pane, double-click System cryptography: Use FIPS compliant algorithms for encryption,
hashing, and signing, and then click Enabled.
- Please use the following code for reproducing problem:
Pop3Client client = new Pop3Client();
client.Host = popHost;
client.Port = 110;
client.Username = username;
client.Password = password;
client.SecurityOptions = SecurityOptions.Auto;
int messageCount = client.GetMessageCount();
for (int i = 1; i <= messageCount; i++)
string msgId = client.GetMessageUniqueId(i);
MailMessage msg = client.FetchMessage(msgId);
FetchMessage always throws AsposeException starting with Aspose.Email for .NET 17.5 when using FIPS compliant environment .
image.jpg (97.9 KB)
I’ve provided sample for POP3 protocol but this problem also occurs for other protocols.