Migrating to FTH4

Your club admin received the instructions to update their admin password to access FTH4. (FTH3 admin passwords will NOT work in FTH4). Follow the instructions in the email and use 'Member sign in' in the top right corner to access the Club Admin account.

If you are not sure who the club admin is, in your member account; look at 'Club Officers and Members' > "Club Email addresses". The LAST item in this list is the person who is currently listed as your club admin.

If this is not correct, please complete and submit this form to change your club admin:
www.toastmastersclubs.org/welcome/change-admin/

Admin email removal event warrants some backup notice?

  • davem
  • davem's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 38
  • Thanks: 0

Re: Admin email removal event warrants some backup notice?

3 years 3 days ago
#91374
You don't know where this stuff is going to come from, I report about a dozen different spammers a day to my personal mailboxes, via SpamCop, but someone figured out you don't reject contact@...
Here is a snippet from the header:

Received: from mail0.invaldomain.com (mail.atasu-refinery-kz.com [80.89.239.82])
by toastmastersclubs.org (8.14.4/8.14.4) with ESMTP id 38BD5ONe002865
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
for <contact@merrimack-toastmasters.org>; Mon, 11 Sep 2023 13:05:25 GMT
(Merrimack Toastmasters #508 www.merrimack-toastmasters.org )
The topic has been locked.
  • Brian
  • Brian's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 13589
  • Thanks: 4107

Re: Admin email removal event warrants some backup notice?

3 years 7 hours ago
#91389
You can still add the email to you club black list and that will help block them next time.
Thank you,

Brian McDonald DTM
Silver and Wiser Online Toastmasters Club #777940

Technical Support Consultant for FreeToastHost
The topic has been locked.
  • davem
  • davem's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 38
  • Thanks: 0

Re: Admin email removal event warrants some backup notice?

1 year 1 month ago
#95612
And it happened again, took me 2 weeks to notice.

[Wed, 16 Jul 2025 06:18:00 UTC, FreeToastHost System Warning]

Emails sent to the email address [ dave@mitton.com ] have bounced too many times and exceeded the FreeToastHost limit for returned emails. The error information for the last bounced email is as follows:

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

Recipient Email Address: dave@mitton.com
Email Subject: =?utf-8?q?Re-Validation?=
Date Sent: Wed, 16 Jul 2025 06:17:20 GMT

Diagnostic Code: 550 5.7.1 Message contains spam or virus. [1752646673-724450]
Delivery Status: 5.7.1 securityerror
Date Last Attempted: Wed, 16 Jul 2025 06:17:55 GMT
....
Sigh.
(Merrimack Toastmasters #508 www.merrimack-toastmasters.org )
The topic has been locked.
  • RichardT
  • RichardT's Avatar
  • Offline
  • FreeToastHost Ambassador
  • FreeToastHost Ambassador
  • Posts: 1508
  • Thanks: 301

Re: Admin email removal event warrants some backup notice?

1 year 1 month ago
#95619
This is why it's possible for each club to disable their contact@ address and each officer has the ability to disable their public addresses.

A potential mitigation for you to consider; set up a club archive email address (e.g. yourclubname@gmail.com) and use that as the public address where you currently use contact-508@. This way you have full control over an email account to filter spam and and organize legit club business messages. If desired, you can set up filter criteria to forward various legit messages to your personal email and they're not confined to the FTH email alias requirements.

See "Club archive email address + login info" in this doc;

support.toastmastersclubs.org/doc/item/email-settings
Richard Taylor
TM Club #7045
The topic has been locked.
Moderators: Brian, Pam, RichardT, NotLiable, NSB, jgavin, Lcala305, Heni, peterb323, DebbieT
Time to create page: 0.217 seconds