We have SharePoint 2013 Foundation running on an IIS 8 VM. The server is Windows Server 2012 Data Center. My company uses a hosted Exchange service (Exchange 2010). I have the SMTP FQDN and TCP port used for relay that the Exchange hosting company gave me.
Essentially the hosting company requires relay.hostingco.com (this is made up of course) on TCP port 2525 and no authentication. I have this set up in IIS in the SMTP properties for the SharePoint - 80 site.
I then have SharePoint set up to send email to my IIS host (call it intranet.mycompany.com). It's set this way because SharePoint can't be configured to use unique TCP ports or authentication as you know.
None of this works. I've called the hosting company and they say I have everything right although I don't think they're SharePoint experts.
Is that the only config you made? If so, it's not going to work.
More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.
Pimping Sharepoint 2007 without Server-Side Code
One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in…
In SharePoint 2010 it is easy to create custom color themes to jazz up a site. Theme colors can also be created in PowerPoint 2010 with a few clicks. But how do the chosen colors actually look in the SharePoint site? The attached PowerPoint…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail. The methods are covered in more detail in o…