TOPIC:

I set up a new group GoDaddy email address and added the appropriate officers using their generic FTH emails (e.g. This email address is being protected from spambots. You need JavaScript enabled to view it.). However, the test emails were returned saying undeliverable and said something about BCC not allowed. I can send emails directly to the FTH generic club officer emails. Is there something unique about using GoDaddy that cannot send to the FTH club officers?

FTH does not allow BCC due spammers using it
You need to put the correct email address in the To:

I realize that FTH does not allow BCC. I verified with GoDaddy Support that they do not send in BCC but only in TO and CC. I earlier mentioned the BCC because that is what was stated in the reply received since the send failed. Thus, I am trying to determine what could cause the failed send since I did cut-and-paste of the FTH officer emails, and, I can individually send to those FTH officer emails. Somehow, somewhere, the handshake between GoDaddy and FTH may have some issue that I hope to discover "the cure".

What is the email address you are sending from?

I tried two different email accounts to send from. One is my Toastmasters email: This email address is being protected from spambots. You need JavaScript enabled to view it.. I sent to the new GoDaddy This email address is being protected from spambots. You need JavaScript enabled to view it. which should re-route in GoDaddy to three officers' generic FTH emails: president, vpm and vppr all at -7361@toastmastersclubs.org. The message received back is:
Your message has not been delivered to any of the original recipients because it has a destination club
email address (This email address is being protected from spambots. You need JavaScript enabled to view it.) 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.
In other Failed Delivery emails it stated one of the other officer emails.

I will need to see the full email header to dig deeper.

Not sure why you are doing this, there is already a list with all the officers-nnnnnn
Also you can create custom groups in FTH.

FTH is seeing the gmail as duplicates
FAILURE (Duplicate Message ID: <004201d71f48$658db0d0$30a91270$@gmail.com>) Mon 2021/03/22 18:29:46 UTC Club:[] From:[This email address is being protected from spambots. You need JavaScript enabled to view it.] To:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] CC:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] Subject:[This is a Test Email to See if You Receive it] ALL To:[] ALL CC:[]
FAILURE (Duplicate Message ID: <004201d71f48$658db0d0$30a91270$@gmail.com>) Mon 2021/03/22 18:29:46 UTC Club:[] From:[This email address is being protected from spambots. You need JavaScript enabled to view it.] To:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] CC:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] Subject:[This is a Test Email to See if You Receive it] ALL To:[] ALL CC:[]
FAILURE (Duplicate Message ID: <004201d71f48$658db0d0$30a91270$@gmail.com>) Mon 2021/03/22 18:30:54 UTC Club:[] From:[This email address is being protected from spambots. You need JavaScript enabled to view it.] To:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] CC:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] Subject:[This is a Test Email to See if You Receive it] ALL To:[] ALL CC:[]
FAILURE (Duplicate Message ID: <001201d71f4b$ba293530$2e7b9f90$@gmail.com>) Mon 2021/03/22 18:46:57 UTC Club:[] From:[This email address is being protected from spambots. You need JavaScript enabled to view it.] To:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] CC:[] Subject:[Test Email for BJ PR] ALL To:[] ALL CC:[]
FAILURE (Duplicate Message ID: <001201d71f4b$ba293530$2e7b9f90$@gmail.com>) Mon 2021/03/22 18:46:57 UTC Club:[] From:[This email address is being protected from spambots. You need JavaScript enabled to view it.] To:[<This email address is being protected from spambots. You need JavaScript enabled to view it.>] CC:[] Subject:[Test Email for BJ PR] ALL To:[] ALL CC:[]

Explicit BCC is not necessary. An email header with a buried recipient address will also trigger the bounce since some BCCs are sent that way without an explicit BCC address. Also, forwarded emails have that, but forwards have other info in the email headers that we detect for the major email systems like Gmail, MS, and Yahoo. If Godaddy is essentially sending as a forwarding email, maybe we are not detecting that so it would look like BCC in that case.

Need to see the email header.

Here are the headers for the one I sent and the one I got back"
==========================================================
FROM THE EMAIL I SENT:
Return-Path: <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Received: from WIN10Lar (2603-8090-0406-5524-3828-00c3-da98-c4b2.res6.spectrum.com. [2603:8090:406:5524:3828:c3:da98:c4b2])
by smtp.gmail.com with ESMTPSA id a6sm3700371otq.79.2021.03.22.17.46.38
for <This email address is being protected from spambots. You need JavaScript enabled to view it.>
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Mon, 22 Mar 2021 17:46:39 -0700 (PDT)
From: <This email address is being protected from spambots. You need JavaScript enabled to view it.>
To: <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Subject: Another Test Email thru GoDaddy thru FTH to Three Club Officers
Date: Mon, 22 Mar 2021 19:46:37 -0500
Message-ID: <000301d71f7d$fbfeecc0$f3fcc640$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0004_01D71F54.132B55C0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdcffelXtIyUFGKzRD+ywiCNqtz4jg==
Content-Language: en-us

==========================================================
FROM THE FAILED DELIVERY EMAIL I RECEIVED:
Delivered-To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Received: by 2002:a50:f294:0:0:0:0:0 with SMTP id f20csp4094793edm;
Mon, 22 Mar 2021 17:46:42 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJymW3MIx9rzUHFuVm/g9eLn7VtPRg5IwWC3UBcMpLNgDx7Cv/F9rgabDYN8GoQljbNY3+Y+
X-Received: by 2002:a05:620a:981:: with SMTP id x1mr2847981qkx.501.1616460402604;
Mon, 22 Mar 2021 17:46:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1616460402; cv=none;
d=google.com; s=arc-20160816;
b=Hi6qoldz3sPhGGg0yeDK2EJWtA1r8P5ze8rw86hoJRzvJnUJIBUbkRL8/5AY+hCYOH
I1RXB9TJF85+IQbwtO+gUA/plRC3U1ZW7P781maMyhGHa8eNhs5VkuciF+qZcHPxkAd/
Poq0bGNs7UeAgWblmCeOy6Ky/e1CPwDYosHafVpqlYRTaEI4zDv1kiY/CYrDYaseR2mv
Fl+L9I8VYS/Z1RNyZQ41Oan+2QBuu9u4whci6NWve8owMSY2wV1PY597B9MOUE0jk9mJ
t9ESy+9DjraJT+YBXT1Fzj2rPt7pxhbs3IAK22aSc0Xs4+Z5WdTdxA675S1tqERQj+XP
XNMw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=dkim-signature:content-transfer-encoding:from:subject:to
:mime-version:date:message-id;
bh=a1+AkHjeCxlgji6p2u04FrZHGsqOth0wEogjsheR/jg=;
b=aOji4gJK2N88SEg+A4REs0OSX5gSMPmwy0pPEGGOmpXhLYsYwhApwGin6hcZbB64Sz
DjCbitnqV/yxV6XSvG8Ufbrp7Iqe2FCa8bCS4Uo8I64GIE0MZ8ygATIVagBBkSzWjz8A
uEnqCx6Xt0kTmSkTs+zg74MSCbHXg8JAWmkRCBnFlHepISCdwY/N4Cs3E6p7yWMmYqmm
p+94b3dbPebemumQ/jr8/lBBvGpiDc8LGtPV3zAfy4qOHeN9arKWv0GahDTuyg8qPudJ
uKZA8FsCa/svYGzIyJ9p/e27D7NtAeWUXI8saPtZMQY3KDPsUGTiiS1K4Amt74GlFFBt
A1Jg==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@toastmastersclubs.org header.s=default header.b=IrZANF9p;
spf=pass (google.com: domain of This email address is being protected from spambots. You need JavaScript enabled to view it. designates 50.19.253.65 as permitted sender) smtp.mailfrom=server@toastmastersclubs.org;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=toastmastersclubs.org
Return-Path: <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Received: from toastmastersclubs.org (toastmastersclubs.org. [50.19.253.65])
by mx.google.com with ESMTPS id z28si8090749qkj.166.2021.03.22.17.46.42
for <This email address is being protected from spambots. You need JavaScript enabled to view it.>
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Mon, 22 Mar 2021 17:46:42 -0700 (PDT)
Received-SPF: pass (google.com: domain of This email address is being protected from spambots. You need JavaScript enabled to view it. designates 50.19.253.65 as permitted sender) client-ip=50.19.253.65;
Authentication-Results: mx.google.com;
dkim=pass header.i=@toastmastersclubs.org header.s=default header.b=IrZANF9p;
spf=pass (google.com: domain of This email address is being protected from spambots. You need JavaScript enabled to view it. designates 50.19.253.65 as permitted sender) smtp.mailfrom=server@toastmastersclubs.org;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=toastmastersclubs.org
Received: from localhost.localdomain (toastmastersclubs.org [127.0.0.1])
by toastmastersclubs.org (8.14.4/8.14.4) with ESMTP id 12N0kgME018584
for <This email address is being protected from spambots. You need JavaScript enabled to view it.>; Tue, 23 Mar 2021 00:46:42 GMT
Message-Id: <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Tue, 23 Mar 2021 00:46:42 +0000
MIME-Version: 1.0
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Subject: [FreeToastHost] Message Not Delivered: Another Test Email thru
GoDaddy thru FTH to Three Club Officers
From: "FreeToastHost Server" <This email address is being protected from spambots. You need JavaScript enabled to view it.>
X-Loop: freetoasthost
Content-Transfer-Encoding: 7bit
Content-Type: multipart/mixed; boundary="16164604020.DA9eEcD6B.18575"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=toastmastersclubs.org;
h=content-transfer-encoding:content-type:date:from:mime-version
:subject:to; s=default; bh=h6OKcuNmV1o0D3onImOJ5Erc0ivIIragWVz+c
0Lsrio=; b=IrZANF9pl0/eVOZ6gnqifqq1JjAQYxvNqFoScJHITTcG7O5AHN4wH
BBwFlUnDqxHVofiCjnyw/XqOaIEFZByz3GM/JO/Th65IjlV/sNoDU2thknaDJkp7
cdK0TA8EKy3IC4vWEwun+WW4QSnTUGPCRxfBily/yTcj1St7uK63z0=

larryfth:

Could you send the email again? I know it will not go through yet, but I need to try to capture some information from the BCC logic.

The part that is triggering the bounce is the following. However, it should not generate a bounce in this case because this address is in the TO, so it is really not "buried" for our purposes.
Please let me know when you have sent it, so I can check if I have the information I need.

Just resent it at 9:05 pm CDT

Let me see what I got

Ok, from my test log file:
Ok, this legitimately fails the BCC test.
Reason: The buried email address, This email address is being protected from spambots. You need JavaScript enabled to view it., does not match any email address in the "TO".

Unless the code found something that would identify this email as being forwarded, we could not pass this because spammers sometimes use a buried email address as another way to bcc people.

This also seems to be different than the headers you posted earlier. Do you have the headers for what you just sent?

Headers attached

Something is fishy. Your headers don't show the vppr address that my test code caught.

Please do me a favor and re-send it, but this time put the following at the very beginning of your email subject line (before the rest of the subject)... you will need something other than this debugging tag in the subject, since the tag gets stripped out.

The above will save a copy of the email as received by the server and will save a trace of the email logic. You will also receive this information back as an email with attachments.

Unfortunately, I have to get going on other things, so may have to come back to this.