So let me give you some background context on this bounce logging and tracking that we started doing in the last 6 mos.
The crux of what you are observing is that some people are (or were) members of more than one club and their email address may show up in the FTH database for multiple clubs.
So if Frank was in 3 clubs, for example, and only one of those clubs is sending emails to that bad email address, the question then becomes what to do about the other 2 clubs when we delete/deactivate the email address *everywhere* in our database. We are not going to dance around these bad email addresses anymore... if they are deleted or deactivated, it is done *globally* in our database.
What I chose to do for the other "2 clubs" in this scenario was to do a login based notification message even for the clubs that may not be actively using the email address. My reason: Better to over-notify than to not notify at all, particularly if we are automatically deleting data that your club entered.
So... bottom line is that you may get these types of notifications for email addresses that you are not using if the relevant person's email address is associated with more than one club. (In other words, some other club tried to use the same email address, the email bounced back to the FTH server for the 4th time, and that is what triggered the notification to *every club* that has the email address in their db records and content.)
Last edit: 6 years 6 months ago by SteveTheTechie.
The topic has been locked.