Allow custom domain email addresses for archive email address

Hello,

We have a custom domain at www.smoothtalkersatx.org which we setup to forward to amd.toastmastersclubs.org/

We are using another provider for emails for our domain (we have not setup any MX records for email to toastmasterclubs.org).

I want to be able to add an email address to the "archive" setting which is archive@smoothtalkersatx.org

However I can't because I think forwarding right now assumes both web page and email are always set.

Tried to workaround it by adding a new member, but same issue arises (can't add an email address with same domain name).

Is this something which can be supported/enhanced?

Thanks,

Rahul

1) we do not support domain forwarding, follow the instructions provided or remove the custom domain from the admin console.

2) we do not support any configuration for email except the instructions in the documentation.

support.toastmastersclubs.org/doc/item/dns-settings-overview

Hi Brian,

Sorry i wasn't clear, i am following the instructions on that page except for not adding this record:

domain.ext MX-10 mail.domain.ext (This tells the registrar how to direct email to an email address containing the custom domain name.)

Due to wanting to use a different email provider (gsuites).

When trying to setup Admin Console -> Email/Contact Forms -> Club Archive Email Address to send all email to this email - "archive@smoothtalkersatx.org" it gives the error message:

You have errors in your form below. Please scroll down and correct the following:
Email Settings Tab: You cannot use an email address for Club Email Address that contains toastmastersclubs.org, toastmastersdistricts.org or your custom domain.

Which isn't a problem for us since we arent adding the MX record mentioned above, so some other provider is providing email for our domain.

We do not support that configuration.
Either setup as documented or do not use a custom domain.

We cannot support a custom domain for that archive email address that is the same as the domain you enter. The problem is that it leaves the FTH server vulnerable to potential email loops which causes server crashes. I realize this vulnerability does not apply to your config because you set the MX differently, but frankly we are not going to jump through hoops to support every little advanced tweak clubs use, like MX pointing elsewhere.