Aren you taking a risk by putting Hexillion in the HELO and MAIL FROM by default?
Yes, but consider the alternatives: • We could use someone else’s domain and email address (as at least one of our competitors does), thus shifting any suspicion to an innocent party • We could leave the defaults blank, forcing our users to enter something before HexValidEmail will work. Our customers are generally not SMTP experts, so they will not expect or understand the need for this information without up-front education. This would lower customer satisfaction, increase our costs, and put us at a competitive disadvantage. The whole point of a component like HexValidEmail is to take the burdens of such details off the shoulders of our customers. • We could try to live a 100% safe life, kill the product, and go home.
