This is kinda depressing to read :(
But thanks for explaining.
I got a good laugh when it mentioned of Lotus Notes, "Run away from it."
Would it be reasonable to stick a link to that article in the submit a patch document? Something like, "If you can't use 'git send-email' for any reason, then please review [link]this article[/link] to understand which clients are capable of sending acceptable patches and how to configure them."
I suspect I'm going to encounter this problem again as I try to make small fixes for more projects, so it might be worth it for me to spend a small amount of time at some point setting up a mail client that I can send git patches with. Or perhaps I can just move the patch(es) onto another machine
(ex: my personal laptop) and send it with 'git send-email' from there,
instead of needing to install a mail client that is outside of my normal
workflow. I am not comfortable with putting smtp login information onto the server that I am using for this work. If anyone has any advice on how to handle this situation, I'd appreciate it. That kernel doc that Peter linked is already pretty helpful, at least.
Thanks!