Trouble with Email Setup (Exchange 2010)

[Don Thimsen]

I'm doing a major upgrade over the holiday break:

Window 2003 Domain, Exchange 2003, Vault 4.1.4 running MS SQL 2000

to

Windows 2008 R2 Domain controller, Exchange 2010, Vault 5.0.2 running MS SQL 2008 Express

In the new domain, the Vault server is now running on the Domain Controller. Everything seems to be working except I can't get the Email notification working. On the Vault admin Email Settings panel, I get server repsonse 530 5.7.1 Client was not authenticated. Note: When I setup Outlook clients to work with Exchange 2010, I had to enable "Encrypt data between Microsoft Office Outlook and Micosoft Exchange" in the Outlook profile.

Any ideas??

Thanks,
Don

[Beth]

On the previous setup, did you have the encryption enabled also? If that part is different, then you might momentarily turn it off to see if the email notifications work then. That will just help narrow the issue down.

What settings do you have in your email notification setup?

Here is a KB article on email setup that may help: http://support.sourcegear.com/viewtopic ... 455#p50455

[Don Thimsen]

Okay, I've got it working... By default Exchange 2010 servers not running the Edge Transport role will only accept inbound smtp connections from Exchange Users (clients), Exchange Servers (other Exchange 2007/2010 servers) and Exchange Legacy Servers (legacy Exchange 2003 & below servers). To allow annonymous smtp connections for vault notification, I used the Exchange Management Console to add a new Receive Connector for Vault.

Exchange Management Console > Server Configuration > Select the applicable server. There were two entries in the Receive connectors tab: Client and Default. I used the New Receiver Connector... in the Action pane to open the wizard to create an entry for Vault.

Name: Vault
Local IP Address: vault server IP address
Remote IP address: vault server IP address
Authentication: Enabled TLS
Permission Groups: Anonymous

[Beth]

Thank you for the update. This should help other users as well.

[Don Thimsen]

CORRECTION:

At our shop, Exchange and Vault run on the same server. I think the Local IP Address for the connector needs to point to the Exchange server...

Name: Vault
Local IP Address: exchange server IP address
Remote IP address: vault server IP address
Authentication: Enabled TLS
Permission Groups: Anonymous

[Beth]

Thanks again for the update