<div>
Gareth - I completely agree regarding setting up restrictions on the firewall. &nbsp;That was my first option which I'm still looking into.<br />
<br />
Thanks,<br />
RealTimer
</div>


Gareth - I completely agree regarding setting up restrictions on the firewall.  That was my first option which I'm still looking into.

Thanks,
RealTimer

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
We have recently deployed a Windows 2012R2 server running Exchange Server 2013 Standard. <br />
<br />
We use a 3rd party spam filter (Appriver). &nbsp;We want to ensure that Exchange 2013 only allows inbound email from the Appriver IP addresses.<br />
<br />
Could you please furnish the appropriate manner in which to accomplish this.<br />
<br />
Thanks in advance.<br />
<br />
Regards,<br />
RealTimer
</div>
</div>


Hello,

We have recently deployed a Windows 2012R2 server running Exchange Server 2013 Standard. 

We use a 3rd party spam filter (Appriver).  We want to ensure that Exchange 2013 only allows inbound email from the Appriver IP addresses.

Could you please furnish the appropriate manner in which to accomplish this.

Thanks in advance.

Regards,
RealTimer

Exchange 2013 - limiting SMTP traffic to allow only specific range.

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.