This content has been marked as final. Show 3 replies
This could be a problem with your Email Settings in the ADDT Control Panel, or maybe a problem with your hosting. Double check your ADDT Email Settings and contact your hosting to see what email settings are required.
I see that you email first inserts a record into your database. I would like to know if you have checked your database to see if in fact the email address was correctly entered into your database before the trigger generated the email send operation.
The reason that I ask is that I am having a similar problem with an enrollment confirmation application that I am building. When I checked the database, I found that instead of a valid text entry being inserted, the "email" field had been encrypted with all numeric characters. This same jumble of numbers was then being applied to the send_email address, and that resulted in my receiving an error message similar to you.
If anyone else has run into this problem and resolved it, please let us know how you were able to stop the encryption. Thank you,
Naj Rellim / firstname.lastname@example.org
ADDT uses an encryption utility, MD5, that converts your email addresses into strings of numeric characters. The problem is that it doesn't decrypt the email addresses before adding them to your database. When your automated mail application draws from your database for email addresses, all it finds are those numbers instead of email addresses. I worked for days trying to first find a way to decrypt the MD5 encryption. When that didn't work, I tried to find the "include" page that contains the encryption. Finally out of frustration, I re-built my registration form without using ADDT and instead using the native dynamic tools of DW-CS3 and the email addresses were correctly entered into the database. The result is that now my mailer function also works.