Hi Folks,
I run a small website for a membership organization - and I have created an
ASP front end for an access database that allows the board members to manage
their membership roster (names, addresses, membership dues paid, etc)...
Part of the site is an ASP SMTP script that allows members to send emails to
all the people listed in the access database. It's a simple script that
just loops through the database and sends an individual email to everyone in
the database. There are a few drawbacks to this method...
The email gets sent from my server, but the return address listed in the
email is from the individual user that sends it. As a result, a percentacge
of recipients don't get the message, because their mail server does a
reverse check and finds that there is no matching account on the originating
server. It would be impossible for me to give all the users mail accounts
on my server - and it would be a redundant nightmare to manage it.
So, my question is: Is there a solution, like a listserv, which can be
integrated with an existing database of users? Obviously, I don't want to
keep a seperate listserv - the whole idea of the membership database is to
only have one database to update. ie: when a users email changes, I don't
want to update it in two places. Also, it would be nice to be able to
automatically identify obsolete addresses (bounces) and flag the records in
the database. And finally, I'd like to have a solution that solves the
reverse-lookup problem.
I'm grateful for any advice or suggestions.
Best Regards,
Jack Coletti
St. Petersburg, FL