Message Not Delivered Error

Our club uses GoDaddy.com that forwards e-mails sent to our domain name. For example, all our members can send an email to a member without knowing their personal e-mail address; e.g., Joe Smith is JoeS@example.org. We've had instances where members send e-mails to officers using this system; e.g., vpe@example.org which was nonexistent.

Therefore, I entered the actual TM address in GoDaddy.com to forward these e-mails; e.g., an e-mail sent to vpe@example.org should now forward to the vpe-xxxx@toastmastersclubs.org. Note: I entered xxxx instead of our actual TM club #.

However I get the following error message. How can I get around this problem so that members, guests, and others can use either e-mail address?

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Your message has not been delivered to any of the original recipients because it has a destination club email address (vpm-xxxx@toastmastersclubs.org) that is not part of the To or CC fields.

Please note: We do not support the use of BCC. If you are sending to an email address on this server using BCC please re-address using To or CC and try again.

All Depend on if you have anything in the CC: or BCC: Please post the full email including email headers.

Thank you for replying. I did not have anything in the CC or BCC lines.

I was using the GoDaddy.com forwarding service to redirect e-mails sent to our @bluejackettm.org address to the equivalent xxxx-7361@toastmastersclubs.org. For example, e-mails sent to vpe@bluejackettm.org would be redirected to vpe-7361@toastmastersclubs.org.

I included the FreeToastHost e-mail and attachment.

I guess you cannot do that. We only support where the custom domain email mx points to the FTH server.
We are not staffed to figure out your particular hack.

You are getting the bounce because the server cannot definitively determine whether this is a "creative BCC" approach or a forwarded email (they can look similar in the headers) so the former is presumed and the email is rejected as a result. We do support some types of forwarded emails, but only those whose headers look like emails forwarded via Gmail, Hotmail/Outlook, or Yahoo! email. Those email services put specific headers in forwarded emails that we can detect to allow the code to verify they are forwarded emails and not a "creative BCC" approach.