Author |
|
WLF2022916 Newbie
Joined: 05 November 2023 Location: United Kingdom
Online Status: Offline Posts: 10
|
Posted: 05 November 2023 at 10:40am | IP Logged
|
|
|
Hello
Before diving into the components please advise current known issues or possible bugs, maybe there are some issues in the list that are unacceptable for me so it will save time, although I've searched and inspected some reviews, advised yours is quite stable and reliable and fairly priced.
Please shed a light on the headquarters as your contact us page does not reveal any information on the physical location of your office(s), your code signing certificate used on component installer indicated the state of Wyoming but am not quite sure because of no Google business profile etc... (need that to pass to the company at the end, not important for me).
These vulnerabilities will not affect our usage, are you aware of similar vulnerabilities affecting mail .net dlls? Thank you in advance.
|
Back to Top |
|
|
WLF2022916 Newbie
Joined: 05 November 2023 Location: United Kingdom
Online Status: Offline Posts: 10
|
Posted: 05 November 2023 at 10:41am | IP Logged
|
|
|
Missed the link
https://www.cvedetails.com/vulnerability-list/vendor_id-6423/Afterlogic.html
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Online Posts: 6104
|
Posted: 05 November 2023 at 9:57pm | IP Logged
|
|
|
Currently we're not aware of any known vulnerabilities or security issues with our components. We treat security very seriously, so when we get such reports we handle them and release fixes on priority basis. I can safely say there were no security issues reported within last couple of years at least. If you have a specific concern, please contact us via HelpDesk.
Quote:
Please shed a light on the headquarters as your contact us page does not reveal any information on the physical location of your office(s), your code signing certificate used on component installer indicated the state of Wyoming but am not quite sure |
|
|
Our primary business office is in Wyoming USA indeed - but our actual research & development office is in Sofia, Bulgaria. You can find contact details at our other website https://afterlogic.works/ focused on custom development projects.
Thanks.
--
Regards,
Igor, Afterlogic Support
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Online Posts: 6104
|
Posted: 05 November 2023 at 10:02pm | IP Logged
|
|
|
Also, regarding the known issues - one thing worth pointing out is this. A couple years ago, Microsoft announced retirement of Basic Authentication for Office 365 service, so OAuth2 is now required. At that time, it wasn't a requirement for SMTP however, in fact they didn't even implement OAuth2 support for non-interactive use of SMTP. So in our guidelines, we've addressed POP3 and IMAP only. However, that has changed relatively recently, they do support OAuth2 non-interactively for Office 365 SMTP now. And we plan a new release of MailBee.NET Objects with samples and documentation updated accordingly - probably, later this year.
--
Regards,
Igor, Afterlogic Support
|
Back to Top |
|
|
WLF2022916 Newbie
Joined: 05 November 2023 Location: United Kingdom
Online Status: Offline Posts: 10
|
Posted: 06 November 2023 at 3:40am | IP Logged
|
|
|
Hello
Thank you for the valuable info, perhaps will need some custom partial development, much better if done by the developers themselves.
I did a quick comparison with other components like GemBox etc, your functions, properties and events are very rich and obviously will make development and debugging easier, the only nightmare is that we already migrated from 2 other components in the past years due to the out-of-business companies.
We also purchased an expensive license of the Indian standard low quality Aspose email component, I bet their source code is the worst project ever done on the globe, we found many critical bugs, broken functions and missing mandatory features, near one year passed and most of them are not fixed yet, another disappointing forced migration which we hope to be the last.
Will definitely need OAuth2, a 2 months time-frame is fine.
|
Back to Top |
|
|