Hacker News new | ask | show | jobs
by MaxBarraclough 979 days ago
They said they found it difficult to configure, not that they found it difficult to use afterwards.
1 comments
tlamponi 979 days ago
If your system cannot relay mail correctly already, as most office setups are easy to configure to be able to provide that without extra config, at least for Linux setups, then the set up means having something like the following in their gitconfig:

    cat .gitconfig
    # snip
    [sendemail]
     to = default@list.example.com
     annotate = yes
     suppresscc = self
     smtpencryption=tls
     smtpserver=imap.example.com
     smtpserverport=587
     smtpuser=foo.bar@example.com
(only the ones starting with "smtp" are relevant for mail, the other ones are just there for convenience)

And that has to be done once, iow., in essence it's as hard a setting up an email fat client like thunderbird.

link
earthboundkid 979 days ago
FWIW, I haven't done that kind of setup for years because modern iOS/macOS does email server discovery, where you enter "bob@example.com" and then it does discovery and figures out the right imap.example.com:587 etc for you by looking at DNS.
link
tlamponi 979 days ago
Yes, such things are nice. The well-known URI [0] system is also sometimes used for this, at least there's one entry for Thunderbird under the "autoconfig/mail" subdirectory. Having some of those auto-config methods available for git send-mail could be nice, as it would lower the barrier a bit further, even if most devs are probably able to check their SMTP endpoint and port.

[0]: https://en.wikipedia.org/wiki/Well-known_URI

link