问题描述
当同时运行组件SMTP和POP时，OpenSSL库中也出现了AV，因为我在Google上发现了一些对此的抱怨，因此我将使用OpenSSL的替代方法.
When running component SMTP and POP too, am getting AV in OpenSSL library, as I found several complaints about this on Google, I would use an alternative to OpenSSL.
我确定Indy的组件没有错误，因为Remy Lebeau是主要角色，但我需要替代方法.我是否必须离开印地那美丽的作品?
I'm sure that the component of Indy has no error because Remy Lebeau is the master, but I need an alternative. Will I have to leave this beautiful work which is the component of Indy?
推荐答案
Indy的OpenSSL用法经过了很好的测试，并被许多人毫无问题地使用.如果您使用的是AV，那么在怀疑Indy有问题之前，我会怀疑您自己的代码中存在错误.当然，这并不是说Indy完美无瑕.因此，如果您怀疑Indy或OpenSSL错误，则需要提供特定的详细信息，代码段等来进行验证，否则没有人可以帮助您.如果您还看到其他投诉，请提供指向它们的链接.
Indy's OpenSSL usage is fairly well tested, and used by many people without problem. If you are having AVs with it, I would suspect a bug in your own code before I suspect a problem with Indy. That's not to say that Indy is perfect and bug free, of course. So if you suspect an Indy or OpenSSL bug, you need to provide specific details, code snippets, etc to verify it, otherwise no one can help you. If you have seen other complaints, provide links to them.
对于您的实际问题，可以使用第三方替代方法，例如 EldoS SecureBlackbox ，其中包括针对Indy的TIdIOHandler SSL实现.
As for your actual question, there are third-party alternatives available, such as EldoS SecureBlackbox, which includes an TIdIOHandler SSL implementation for Indy.
这篇关于Indy SMTP组件中的OpenSSL替代的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！