Whatever email client you are using is breaking up the email into distinct copies and generating distinct Message ID's for each copy:
Code:
Jan 5 17:56:35 toastmastersclubs sendmail[22019]: 105HuZoD022019: from=<adayers@freshayers.com>, size=8413, class=0, nrcpts=1, msgid=<202101051756.105HuXKC028965@jax4mhob08.registeredsite.com>, proto=ESMTP, daemon=MTA, relay=jax4mhob08.myregisteredsite.com [64.69.218.88]
Jan 5 17:56:35 toastmastersclubs sendmail[22018]: 105HuZD4022018: from=<adayers@freshayers.com>, size=8412, class=0, nrcpts=1, msgid=<202101051756.105HuXXR027956@jax4mhob09.registeredsite.com>, proto=ESMTP, daemon=MTA, relay=jax4mhob09.myregisteredsite.com [64.69.218.89]
Jan 5 17:56:35 toastmastersclubs sendmail[22017]: 105HuZgB022017: from=<adayers@freshayers.com>, size=8419, class=0, nrcpts=1, msgid=<202101051756.105HuXsk017619@jax4mhob07.registeredsite.com>, proto=ESMTP, daemon=MTA, relay=jax4mhob07.myregisteredsite.com [64.69.218.87]
Jan 5 17:56:36 toastmastersclubs sendmail[22016]: 105HuZtv022016: from=<adayers@freshayers.com>, size=8415, class=0, nrcpts=1, msgid=<202101051756.105HuX8W028698@jax4mhob10.registeredsite.com>, proto=ESMTP, daemon=MTA, relay=jax4mhob10.myregisteredsite.com [64.69.218.90]
Our email code relies heavily on the Message IDs to determine whether multiple received emails (received by the server) are actually just re-sends of the same email from an email client. In this case, because the incoming Message IDs are distinct and different, our email code cannot know that they are actually just re-sends of the same email.
