Multi-User Mails Redundancy

[InternalLoss]

In the PHP implementation, if multiple recipients are specified, then the scripts simply just create the mail multiple times, wasting a lot of database space.

Example:

2017/11/26 15:50:57 MAIL FROM: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 RCPT TO: [email protected]
2017/11/26 15:50:57 DATA
2017/11/26 15:50:57 Date: 26 Nov 2017 21:39:16 -0000
2017/11/26 15:50:57 From: [email protected]
2017/11/26 15:50:57 To: [email protected],
2017/11/26 15:50:57  [email protected],
2017/11/26 15:50:57  [email protected],
2017/11/26 15:50:57  [email protected],
2017/11/26 15:50:57  [email protected],
2017/11/26 15:50:57  [email protected],
2017/11/26 15:50:57  [email protected],
2017/11/26 15:50:57  [email protected]

Would create 8 separate mail entries in the database, wasting space.
Tying in with #5, we could parse the mail and then have recipient ids in an indexable format where the database could select mails the user has not yet received, however once they have received it remove their Wii ID from the recipient list (for the sake of semantics you'd want to simply set them as sent so that the original mail contents are not edited but, to be honest, missing out all recipients except the ones that haven't yet got the mail shouldn't be an issue, it's not a security flaw).

[InternalLoss]

@spotlightishere has this been solved in Mail-Go? This is a very old issue, I'm assuming it is.

[spotlightishere]

As far as I can tell, this has not been dealt with in either implementation.