Instead of the IP address try the FQDN? E.g. server.mydomain.local
Is the email server on the same domain, not behind a firewall of any sort, can you ping it ok from the vault server?
Hi Neil,
Thanks for your swift reply.
I'm actually setting up the email server using the FQDN as shown as below.
The firewall is disabled too.
Is there any others area that can lead to this error?
Thanks
BR
Wen Tat
Is that definitely the correct port number you've put in there? I'm far from an exchange server expert but isn't the default port number 25? Maybe try port 25 just incase.
Also, which version of Vault are you currently using...? I can see you have PS5 in the email address line, is that a current or old reference to Productstream 5 or just a coincidence?
Hi Neil,
The port number 587 is correct.
Our Microsoft Outlook have no problem to connect it using this port.
We are using Vault Pro 2013 now.
The email is ps5 because we have been are active user since ProductStream5 🙂
BTW, i've capture the email log from ADMS as per attached.
Maybe you can find some hint there?
Again just to try and narrow this down and rule stuff out:
Try changing the "Email From" address to something different, that doesn't actually have to be a valid email account. It has to be in an email format structure, but the actual email address doesn't have to exist so instead of "ps5@vis-dynamics.com" try "vault@vis-dynamics.com" or even "admin@vault.com". The logs are mentioning spam filters so it's worth a try.
Like I mentioned the email from can be from any address, but the address you're sending it too has to be a recognisable internal email address. Perhaps try sending the test email to someone elses internal email address too.
If none of this works, we'll move on to something more technical.
I've just done some basic Googling around and the majority of similar issues have been caused by the port being blocked. It looks like quite a generic error though so it could be a lot of things
I guess you've tried this but make sure if you're using Windows Firewall it's disabled for all 3 network types, also again as a matter of troubleshooting completely disable all anti-virus software on both the Vault server and mail server temporarily to see if it's that causing the blockage.
Hi,
In reviewing the log, it seems like a spam filter is at issue:
The server response was: Sending address not accepted due to spam filter
Has this been investigated? Possibly the sending address needs to be added to a whitelist or spam filter otherwise configured?
Paul