The entire message is (or can be) compressed before transmission (eg. When IMAP has DEFLATE enabled).
Just because an intermediate encoding step expands binary to make it text safe doesn’t mean it has to stay uncompressed during the entire existence of that MIMe message.
I’m not arguing for Outlook. I wouldn’t touch that POS unless I was forced to.
But maybe it’s just easier to not have to teach an astronaut to use another app. If they are using Outlook in space, it’s probably the same app and server they use on the ground.
Of course FTP or RSYNC or whatever would be slightly more efficient for the transfer or more capable or retrying / resuming. I’m not arguing that either.
Sometimes it’s more important that the astronaut doesn’t have to learn another app instead/ system.
Sometimes it’s better to choose a less efficient system that is less prone to accidental destructive. It’s not like anybody ever screwed up a sync command and accidentally wiped a directory or anything.[1]
[1] https://www.reddit.com/r/linuxquestions/comments/1kawpyu/rsy...
I’ll wait.
There's no way that outlook is the best tool for the job though, and it's no surprise at all that they're having problems with it. It's a complete mess with insane amounts of overhead and bloat if all you want to do is send text. Even the message headers it sends/mangles are trash. It's a pain to work with on the end user side too. I can't imagine that they couldn't have written a basic email client that would do the job better with far fewer problems/resources or used/built off of any number of decades old open source projects.