[Pkg-xen-devel] [PATCH 00/19] Fixing cross-compilation, some script work, revised

[Ian Campbell]

On Fri, 2020-12-04 at 22:11 -0800, Elliott Mitchell wrote:
> On Sat, Dec 05, 2020 at 03:12:15AM +0100, Marek Marczykowski-G??recki wrote:
> > On Fri, Dec 04, 2020 at 05:48:37PM -0800, Elliott Mitchell wrote:
> > > The host on which I do development and has the appropriate repositories
> > > doesn't handle this e-mail address.  As such `git send-email` is
> > > *completely* incompatible with this setup.
> > 
> > I'm fairly sure your setup isn't that special to be incompatible with
> > `git send-email`. For example you can setup `git send-email` to use
> > arbitrary SMTP server, see here:
> > https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Setting_up_git_send-email
> > 
> 
> Which assumes one's git repositories are located directly on the Internet
> (one of the most secure places, really!) and nothing filtering port 25...

Look in `git-sendemail(1)` for the `--smtp-server-port` option which
can configure git-sendemail to use a smart host (Mail Submission
Agent), encrypted (TLS or STARTTLS) and authenticated on port 465 or
587 i.e. the same thing you feed into e.g. Thunderbird or any other
mail client to send email from them.

You can also/instead use e.g. ssmtp or msmtp to provide a
dumb/outgoing-only/lite version of /usr/lib/sendmail which does nothing
but forward outgoing mail to your smarthost in a similar way.

In neither case do you need port 25 to be open, you need outgoing port
465 or 587 and no incoming ports at all.

If you do not have that option for some reason (perhaps your isp is
especially draconian and filters 465 and 587 without providing you with
a relay machine or you dont want use their relay for some reason) you
can:
   1. Run `git format-patches` in your git repo.
   2. Copy (scp, rsync, sneakernet) `*.patch` to a machine with outgoing
      email access and the git tools (but not any git repo)
   3. Run `git send-email *.patch` on the host with access to outgoing
      email.

Which can't be all that different to how you are doing things now,
except for step 3 uses `git sendemail` instead of whatever you are
doing now.

Ian.