Hello,
Hi,
Thank you for writing to Aspose Support team.
We have tested this issue at out end with the latest version of the API and were not able to reproduce the same problem. The API connects to the server without any error. Can you please confirm if the server IP is not behind a firewall? If possible, please share a test account details with us that we can use for investigating the issue further at our end.
Hi Alessandro,
Though it may require a little effort, but can you please test if any other version after 5.3.0 is working fine at your end? The list of changes can be found from our public API Changes section, but it seems difficult to find the exact reason in this case unless we have a test account that we can use to reproduce the problem at our end. We’ll discuss the issue with our Product team for further feedback in this regard and share with you as soon as some information is available. Please share the complete stack trace of the error as well for our analysis.
The last working version is the 5.5.0. From the 5.6.0 onwards there is the problem.
Hi Alessendro,
There have been alot of changes between the transition from 5.5.0 to 5.6.0 and these include major changes to the email communication clients. We are not sure what exactly may have given rise to this issue though. Can you please try the same with a public server such as Office 365 using its SMTP interface and share with us if you face any issue? We are unable to reproduce the problem at our end. We are afraid but without a sample test account, we may not be able to investigate this issue further at our end.
Hi Tim,
We have tested this issue with a public server (GMail in this case - you can get its SMTP IP by Ping it from command prompt using ping [smtp.gmail.com](http://smtp.gmail.com/))
and it didn’t raise any such exception. The email is sent out without any issue. Could you please arrange a test account on your server and share its credentials with us for testing the issue at our end? We’ll use it for reproducing the problem at our end and assist you further.
I’m sorry for the delayed reply - I missed the alert. I think you may be misunderstanding the issue. A public server such as GMail will have reverse DNS available for it (if you use nslookup on the IP address that you discovered, you will see that it yields a host name). If reverse DNS is available, the error does not occur. The error only occurs if reverse DNS is not available for the SMTP server, i.e., nslookup to the IP address does not yield a host name.
Hi Tim,
Could you please share a test account information (IP + Credentials) on your server whose IP you are using to test this issue? Unfortunately, we don’t have any such facility to configure an SMTP server at our end for testing the problem. Or if it is possible, can you please help us in configuring SMTP server on our machine for testing the issue? We’ll look into it for further investigation and assist you accordingly.
Hi Tim,
Kasif,
Hi Tim,
Can you please run your test again? The SMTP server is functioning again and the error still occurs.
Hi Tim,
Our Product team was able to connect earlier to your server using the information you provided and it doesn’t seem seem to be an issue with DNS. As requested, could you please share the complete exception details with us using the latest version of the API? Also, please provide us with the SMTP Activity Logging Information for helping us identify the issue at our end.
I see. It appears that the bug was resolved in the latest version of the API (6.7.0). We were previously using 6.2.0.
Hi Tim,