Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
We have customers which require the use of the NTLM protocol for email notifications. Currently, Vault Professional only support SMTP protocol for this feature.
Our Anti-spam filter is flagging Vault emails as spoofed, presumably because it can't verify that the email is coming from a valid user in our domain even though I have set up a domain user to represent the Vault with it's own mailbox.
I posted this comment under another idea about ECO email notification but thought it warranted reposting here:
There is also a problem with the notification service stopping if it doesn't get a response from the email server it is sending through. We have been having some communication dropouts with Exchange and Outlook. I am told by Autodesk support after reviewing our logs that Vault does not get responses from our SMTP server and therefore quits. I have to issue an 'iisreset' on the Vault server to re-enable email notifications.
I would like to see the Vault server keep trying to send the emails in its queue, retrying after a configurable amount of time. Email servers do this, building up their queue until communication is restored. Let's see Vault do this, please.
Most externally hosted Email providers like Office 365 or Gmail require SSL or TLS encryption. The Vault Pro email notification for engineering change orders does not support these encryption technoligies yet.
Please support TLS/ SSL encryption to allow Vault email notifications without the need to set up an internally hosted email server.
Wir wollten unser Änderungsmanagement über EMAIL verwalten. Da wir mit OFFICE365 agieren war die Aussage von AUTODESK, dass dies nicht funktioniert, da VAULT die Verschlüsselung nicht anbietet. Wir konnten dies nicht glauben und haben bei unterschiedlichen Stellen nachgefragt. Mit dem Ergebnis es ist kaum zu glauben aber wahr.
Since SSL was mentioned as an option for accessing the mobile app, it seems like it would be a good time to implement support for emails for those that will turn it on now.
As noted by someone else, more companies are going to cloud servers for e-mail. It would be good if other protocols were supported so these could be utilized. With more people working remotely, notifications go a long way to help communication. I would think this is needed now more than ever.
The email settings on the ADMS seem to only work in an active directory environment and for self-owned SMTP servers.
However, many of our customers are using third-party email services and have no active directory environment, the SMTP servers are on the cloud, usually require TLS/SSL connections. I have encountered many cases requiring a setup for these SMTP servers, none of them is working with Vault, even if the server requires no TLS/SSL connections.
From a programming perspective, it's utterly simple to send an email with those SMTP servers. It's as simple as requiring only 3 lines of Powershell code, as follows:
$smtpClient = [System.Net.Mail.SmtpClient]::new('smtp.some_email_provider.com', 25)
$smtpClient.Credentials = [System.Net.NetworkCredential]::new('myname@mycompany.com', 'password')
$smtpClient.Send('myname@mycompany.com', 'anothername@mycompany.com', 'Subject', 'This is a simple test.')
This is working wonderfully! I have tried it with various email service providers, with no problem.
It's unbelievable that these SMTP servers cannot work with Vault. When setting up email settings in ADMS with these SMTP servers, it always says "authentication is required".
Please remove these unnecessary limitations from Vault.
Also here, the support is needed. Is there anything known about when we can expect this and in what versions?
The fact, that it was already accepted in 2013 indicates, that the current solution is really old fashioned. In any up to date IT environment the Support for NTLM Protocol is mandatory. Otherwise unfortunately this feature in Vault cannot be used.
