Ok, I would be willing to guess that you have 48 Former Members in your former members list. (I checked.)
The Send Basic Email feature was modeled after the Send Welcome Message feature with some enhancements. This means that, like the Send Welcome Message, the sender was cc'd on every email sent and it sends to each email address *individually* to maintain privacy.
My understanding is that you are saying that your members are saying that they got this same message that was cc'd to the sender a lot of times. I am a bit skeptical of that. I have the email logs and I have looked at them. I do see where your members were sent a *different* email (but not 48 times) regarding your open house with a slightly different subject line--that was sent from an email client. However, the one that was sent to your former members via Send Basic Email was just cc'd to the sender as a confirmation of it being send... I see two email addresses that got those multiple emails (probably 48), one for Kimberly and one I do not recognize.
Since I can see where it would be a problem to be cc'd on a lot of emails, what I have done instead (just now) is to make the function send one confirming email to the original sender containing the list of recipient email addresses instead of cc'ing the sender on each individual send. This confirming email happens *after* all the others have been sent if any successful sends happened. (If no successful sends, then the confirming email does not happen.) The downside to this approach is that you cannot verify that any variable substitution is occurring since the confirming email is sent after the main loop where the variable substitutions happen.
In the future, I may change the confirming email so that it contains all of the individual emails with variable expansions--right now, that is a bit more sophisticated than where FTH is with the email technology.
I am probably going to have to change the send welcome message, also, I can see where this same sort of thing could happen with it.
Last edit: 11 years 3 months ago by SteveTheTechie.
The topic has been locked.