In the fork, @mathlete2 informed me:
While there may well be a ready-made solution somewhere within those search results, the post that contains the solution is not identifiable at a glance…
Sorry, I had intended my link to make things reasonably easy, though requiring a little effort of reading some pre-existing posts. If this had been Stack Exchange, I would have been expected to just “close as duplicate”, since the question is already answered somewhere else, but I think that’s harsh; but maybe my expecting someone to search the forum is also too harsh. (I guess even SE’s close-as-duplicate link to the original; it’s apparently time for me to stop just giving people the keywords to search for and instead just finding the exact post myself.)
is not identifiable at a glance.
I thought that the post that the preview shows as “Let’s call the script MailMerge.py” would be easily noticed by looking through those results… but I guess not.
9ffaa2ae-482b-4d13-9c78-6c3c8b46a508-image.png
So here is the post I was intending for @Claudio-Raphael or anyone else to find – it presents a fully-working PythonScript solution; for those who don’t know how to make use of a solution using the PythonScript plugin, this FAQ explains the steps needed.
Sometimes these scripts for the PythonScript plugin get multiple versions, depending on customizations that people request; I don’t remember whether MailMerge has been customized one or more times in other of the search results; so if the one I linked to is not exactly the solution desired, checking out some of the other posts in that search might find alternate versions of the script which will work better in your circumstances.
TL;DR
The MailMerge.py script is here – sorry for any confusion.