On Tuesday, Nov. 10, 2026, email from AnchorPoint Credit Union Association moves to anchorpoint.coop. The change covers every staff address and the newsletters and announcements we send through HubSpot. A few minutes of setup now keeps our messages out of your junk folder.
The Switch
Tuesday, Nov. 10, 2026
name@yourleague.orgname@anchorpoint.coop
- Only the Ending ChangesThe part before the @ stays the same. Mississippi addresses ending in @mscua.com move to @anchorpoint.coop too.
- Old Addresses Still Reach UsMail sent to @yourleague.org and @mscua.com addresses will reach us for at least a year.
- Your Subscriptions StayYou don’t need to sign up again. Your newsletter choices carry over.
What everyone should do For IT teams Watch for impostors Questions
What Everyone Should Do
For anyone at your credit union who gets email from us.
-
Add the staff you work with to your contacts
Save the @anchorpoint.coop address of each staff member you work with, plus news@anchorpoint.coop for our newsletters. Most email filters trust the people in your contacts. Replace any @yourleague.org or @mscua.com entries for us, and check distribution lists, forwarding rules, and saved recipients that include us. Old addresses keep working, so nothing breaks if you miss one.
-
Check your junk folder after Nov. 10
If a message you expected from us lands in junk or spam, make sure the address ends exactly in @anchorpoint.coop, then mark it Not junk (Outlook) or Not spam (Gmail). Each one teaches your filter that you want our mail. Don’t rescue a message you weren’t expecting; call us instead.
-
Send this page to your IT team
Your IT team can allow our domain for everyone at your credit union, with checks that keep impostors out. We don’t ask you to add our whole domain to your own safe senders list: that setting skips the checks that catch forged mail. The section For IT and Email Security Teams has what your IT team needs.
For IT and Email Security Teams
Please make these changes before Nov. 10 if you can.
We sign our mail from anchorpoint.coop with DKIM and publish SPF and DMARC for the domain, so you can allow it on the strength of that authentication. We don’t ask you to exempt us from link or attachment scanning. The domain is new to filters: we registered it on Aug. 31, 2026, and it starts sending mail in November. Expect some filters to treat it with extra suspicion until it builds a sending history.
-
Allow anchorpoint.coop when it passes DMARC
Recommended rule: the header From domain is
anchorpoint.coopand DMARC passes (DKIM signed withd=anchorpoint.coop). Don’t allow on the From address alone. Anyone can forge a From line; the DMARC check stops that.Microsoft 365 (Defender portal and Exchange admin center)
Tenant Allow/Block List, Microsoft’s first-choice method:
- Go to security.microsoft.com/tenantAllowBlockList > Domains & addresses > Add.
- Select Allow, enter
anchorpoint.coop, and set Remove allow entry after to 45 days after last used date. - Select Add.
Mail flow rule, if the Allow/Block List isn’t enough. Use it only if your MX record points to Microsoft 365, or if Enhanced Filtering for Connectors is on for the connector that receives your inbound mail. Otherwise Microsoft 365 can’t see the real DMARC result.
- Go to admin.exchange.microsoft.com, then Mail flow > Rules. Select Add a rule > Create a new rule and name it.
- Apply this rule if: The sender > domain is >
anchorpoint.coop. - Add condition: The message headers > includes any of these words. Header:
Authentication-Results. Word:dmarc=pass. - Do the following: Modify the message properties > set the spam confidence level (SCL) > Bypass spam filtering.
- Add action: Modify the message properties > set a message header. Header:
X-ETR. Value:Bypass spam filtering for authenticated sender anchorpoint.coop. This marks every message the rule touches. - Select Next, leave Rule mode on Enforce, then Next > Finish > Done.
- Turn the rule on. Rules made in the Exchange admin center start disabled: open the rule and use the Enable or disable rule toggle. It can take 30 minutes to apply.
Microsoft warns never to bypass spam filtering on the sender domain alone. The
dmarc=passcondition and theX-ETRheader follow Microsoft’s own example.Other settings to check:
- Impersonation protection (Defender for Office 365): add anchorpoint.coop to trusted senders and domains only if impersonation protection flags our real mail. To catch lookalikes of us, you can add anchorpoint.coop, yourleague.org, and mscua.com as custom protected domains.
- Quarantine: security.microsoft.com/quarantine. Release a message from us only if its
Authentication-Resultsheader showsdmarc=passfor anchorpoint.coop and it’s something you expected. When you release it, check Submit the message to Microsoft to improve detection (false positive).
Google Workspace (Admin console)
- In admin.google.com, go to Apps > Google Workspace > Gmail > Routing. Under Manage address lists, select Add address list and name it.
- Select Add address, enter
anchorpoint.coop, and leave Require sender authentication on. Select Save. - Go to Apps > Google Workspace > Gmail > Spam, Phishing and Malware. Select your top organizational unit, scroll to Spam, and select Configure (or Add another rule).
- Name the setting, check Bypass spam filters for messages from senders or domains in selected lists, select the list from step 1, and select Save.
Changes can take up to 24 hours. Leave the neighboring “hide warnings” options unchecked.
Other gateways (Proofpoint, Mimecast, Barracuda, and others)
Add anchorpoint.coop to your safe or permitted senders policy, with DMARC or DKIM required to pass. If your gateway holds mail from recently registered domains and holds ours, exempt anchorpoint.coop from that one check.
-
Cover both of our sending paths
Staff email and HubSpot email reach you by different routes. A rule that fits one may miss the other.
Staff email Newsletters and announcements From Individual staff, name@anchorpoint.coop Association addresses such as news@anchorpoint.coop Sent through Google Workspace. Exclaimer, our signature service, adds signatures before mail leaves Google, so you’ll see exclaimer.net in the Received headers. HubSpot Envelope sender (Return-Path) anchorpoint.coop A subdomain of hubspotemail.net DKIM d=anchorpoint.coopd=anchorpoint.coop, plus HubSpot’s own signatureHow DMARC passes SPF and DKIM, both aligned DKIM alignment only. A rule that requires aligned SPF will fail this mail. Sending IPs Google’s shared servers HubSpot’s shared servers Please don’t allow either path by IP address. Google’s and HubSpot’s servers send mail for many other organizations, and an IP-based allow skips the authentication checks. If your gateway can only allow by IP, contact us and we’ll help you find another way.
-
Mirror your yourleague.org allow entries
If you allow yourleague.org with a Tenant Allow/Block List entry or a rule that checks authentication, add the same for anchorpoint.coop. Don’t copy IP-based allows or exemptions from link or attachment scanning; we don’t need them.
-
Keep your yourleague.org and mscua.com rules in place
Leave them until we tell you they can go, which will be at least a year. Some of our systems may still send from yourleague.org while we finish the move. We’ll keep both domains registered and protected by DMARC in the meantime.
-
Allow our web addresses if they’re blocked
Some web and DNS filters block recently registered domains. If yours blocks us, allow these hosts by name:
anchorpoint.coopandwww.anchorpoint.coop(our website), andemail.yourleague.org(newsletter images, web versions, click tracking, and subscription preferences). -
Check quarantine after Nov. 10
Release a held message from anchorpoint.coop only if it passed DMARC and you expected it, and report each one to your vendor as not junk. Reports train the vendor’s filters faster than an allow rule alone. Never release a message flagged as malware or high-confidence phishing; contact us instead.
Check our DNS records yourself
dig +short TXT anchorpoint.coop dig +short TXT _dmarc.anchorpoint.coop dig +short TXT google._domainkey.anchorpoint.coop dig +short MX anchorpoint.coop
Mail to anchorpoint.coop is handled by Google Workspace.
Watch for Impostors
Criminals use changes like this one to send convincing fakes. Our staff email addresses end only in @anchorpoint.coop, @yourleague.org, or @mscua.com. Treat a message that claims to be from us but comes from any other domain, even one that looks close, as suspect. A correct address doesn’t prove a message is from us, though: email accounts can be hijacked.
- anchorpoint.coop is our only new domain. We won’t ask you to allow any other domain, install software, or sign in anywhere to keep getting our mail.
- To make sure you’re on this page, type yourleague.org/new-email into your browser instead of following a link.
- If any message asks you to change how you pay us, sign in somewhere, or open an attachment you didn’t expect, call us at 423-899-2425 before you act. Use this number or one you already have, not one from the message.
Questions
Email hello@yourleague.org or call 423-899-2425 and ask for the IT Department. IT teams are welcome to ask for a sample message with full headers.
Prepared by the AnchorPoint IT Department. Updated Oct. 29, 2026.