|
We had the exact same issue with Comcast. No change was done on our i5. It had something to do with NAT or Network Address Translation. Apparently when you send email from your i5 and it goes through your router it will get NATed from an internal address (sample 10.10.1.12) to an external address. That address may be any one of a series that it picks from a pool. For example anything in the range of 208.202.42.1 through 208.202.42.20. Now, when this address gets to Comcast and they try to do a rDNS lookup it may fail. I forget what our router guy did. But it might have had something to do with either making sure that the rDNS worked for all, or, that every time the i5 goes through the router it picks the same address. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.