iMS POST 2.1.8 beta is now available for download and testing.  This version adds 
loopback protection to the POST Server for
improperly configured MX records.  Here's an example of a domain with an improper MX 
configuration:

Domain: Leading.net

Answer Section:
leading.net, MX, 10, null.leading.net
Authority Records Section:
leading.net, NS, ns1.fdn.com
leading.net, NS, ns2.fdn.com
Additional Records Section:
null.leading.net, A, 127.0.0.100
ns1.fdn.com, A, 216.199.0.131
ns2.fdn.com, A, 216.199.54.11
---

As you can see, their MX points to null.leading.net which, in turn, is defined as a 
loopback address.  For a domain such as this the
POST Server should not attempt to deliver the mail to the designated server as it will 
result in a local loop.

POST Server 2.1.8 addresses this problem and will print out an error in the log file 
for this domain as follows:

13:27:11 [001] WARNING: reject null.leading.net for loopback.

We have this version of the POST Server now running on our main mail server.  Once it 
has been running OK for a day or so we will
remove the "beta" designation an release 2.1.8 officially.  If you would like to apply 
the beta you can download it from:

ftp://ftp.coolfusion.com/pub/ods/ims/beta/post218beta.zip

Regards,

--
Howie Hamlin - inFusion Project Manager
On-Line Data Solutions, Inc. - www.CoolFusion.com  - 631-737-4668 x101
inFusion Mail Server (iMS) - The Intelligent Mail Server
>>> Find out how iMS Stacks up to the competition: 
>http://www.coolfusion.com/imssecomparison.cfm

==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to