|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] David, <snip> What system are you going to ping to validate the email address? Keep in mind that many (if not most) companies do not point their main domain name to the same system that handles their email. <endsnip> I think I understand what you are saying here. For example we've purchased a division, mountaincable.com. (shortly before telephony tanked :-( ) Anyways, in the next day or so we will have their isp release their mx record to us. These people will have two addresses - a dekko.com address and a mountaincable.com address. Still a ping to mountaincable.com should work, to my best guess. And since I can't truly verify an email without bounce back then testing for the domain might be sufficient. We are dealing primarily with businesses here. How many businesses will have a ping fail with TCP3202, ( not TCP3210) yet still receive email at that domain? I could be in for a rude shock but I'd like an example. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.