anything to do with this. If they did, as you say, a regex would
solve the problem.
For starters, what happens when users have the ability to change
addresses, or import new ones in large blocks, via means out of your
programmatic control? If you can't control the inputs...
Besides, users -- especially non-technical middle and senior managers
-- won't often allow themselves to be brought under control. Try, for
example, to tell a senior executive vice-poobah who has had a
membership list for X years -- and has been blissfully ignorant of all
the bounces since they failed silently prior to CF 6 -- that they have
to qualify it all over again with an opt-in. They'll be laughing all
the way to the balcony, and more so as you sail off of it.
The bottom line, imho, is that a robust, properly written cfmail
application ignores whether the inputs have been tested or not. It
tests for failures prior to the xmit, and gracefully catches those
failures so the job can continue. I learned this one the hard way,
personally.
Further, if your circumstances require it, you may have to spell out
in big letters exactly what is wrong with the address so the drooling
slackjaws who let the list get into this shape in the first place can
go fix it. Sadly, thats a business requirement that has bupkis to do
with efficient programming.
--
--Matt Robertson--
MSB Designs, Inc.
mysecretbase.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
