Summary:

This post describes a tutorial on sending patches by email with git send-email using a USP email account. Because USP email accounts have some restrictions that make the usual Gmail setup impractical, the tutorial presents an alternative workflow based on an OAuth 2.0 email proxy. It explains the problem with standard authentication, introduces the proxy-based approach, and shows how to configure the necessary components so that patches can be sent from the command line with a USP address.

The tutorial is organized around three main steps: running the email proxy with Docker, configuring git send-email through kw send-patch, and testing the setup by sending a sample patch. It also explains the authentication flow used by the proxy, including the browser-based OAuth step and the final verification that the SMTP connection is working correctly.

My experience:

I followed path B from the tutorial. Everything worked as expected overall, but I first had to install Docker because it was not already available on my system.

I also had to run git config --local sendemail.smtpencryption none inside the repository folder to avoid a bug during the setup. After that adjustment, the workflow proceeded normally.