Member Cannot Receive FTH Emails

Hi,

One of our club members is missing the FTH email announcements. He can log onto the site with no issue, and I can see that is email is correct, but for some reason whenever I send an announcement, it does not show up for him.

Our club number is 2466 (District 52)
Email address is eric.kong@ngc.com

Any ideas?

Thanks,
Anthony

The Bounce Count for Email Address [eric.kong@ngc.com] has been reset to zero.
His email provider is blocking email from FTH he will have to contact his email provider

Your email message to eric.kong@ngc.com could not be delivered
and was returned to the FreeToastHost server. Details are as follows:

Recipient Email Address: eric.kong@ngc.com
Email Subject: Toastmasters Club 2466 Meeting Agenda for August 11, 2020
Date Sent: Tue, 11 Aug 2020 16:53:23 +0000

Diagnostic Code: 550 Too many invalid recipients
Delivery Status: 5.5.0

Thanks Brian for the quick response!

I sent him a test email, but he did not receive it. Is the block counter still going up? I have the same email provider (as well as several other members) and have no issues receiving messages from FTH, so it's odd that Eric is having issues. But if the counter is going up, I can talk with our IT to try and see what's going on.

bounce count is not going up, it is still at zero.
He has a secondary yahoo.com email but he has not selected the option to send to both emails in his profile.
I sent him an email and it went through.

SUCCESS (Form Email) Tue 2020/09/08 15:21:50 UTC Club:[2466] From:["Toastmasters Club 2466 on behalf of Admin" <server@toastmastersclubs.org>] To:[eric.kong@ngc.com] CC:[] Subject:[checking]
Sep 8 15:21:52 toastmastersclubs sendmail[13281]: 088FLoPT013275: to=<eric.kong@ngc.com>, ctladdr= (501/502), delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=121177, relay=mx2.ngc.iphmx.com. [207.54.95.251], dsn=2.0.0, stat=Sent (ok: Message 9446781 accepted)

Cool! I think it is working now. I sent some more test emails to Eric and he received them, so I think we are all good now. Thank you again so much Brian.