30 points tonymet | 8 comments | | HN request time: 0.901s | source | bottom
1. ceuk ◴[] No.44385212[source]
You know something is a good idea when you're surprised it hasn't already been invented. This is one of those (assuming it actually hasn't I guess).

Really handy little tool. Nice one

replies(2): >>44385588 #>>44388312 #
2. JdeBP ◴[] No.44385588[source]
I would be surprised if has not. There have been lots of tools over the years where the idea was to present a command-line interface compatible with Sendmail's message submission mode, and hand the mail over to a smart host, possibly not using anything like SMTP.

I predict that someone will be asking for the -t option to be supported here. (-:

replies(1): >>44388698 #
3. mmh0000 ◴[] No.44385944[source]
See also:

https://wiki.archlinux.org/title/SSMTP

replies(1): >>44388329 #
4. tonymet ◴[] No.44388312[source]
I felt the same way . The idea came when I tried to submit patches to sourcehut using my gmail account and the gmail smtp gateway didn’t work (connections, formatting).

A quick proof of concept with the REST API and I thought – why don’t we all use this for patches?

5. tonymet ◴[] No.44388329[source]
i got the idea because gmail smtp didn’t format patches properly. It uses mime and rich formatting which breaks patches.

REST apis preserve the original message .

replies(1): >>44388530 #
6. tonymet ◴[] No.44388530{3}[source]
*gmail's smtp gateway . obviously smtp protocol is high-fidelity
7. tonymet ◴[] No.44388698{3}[source]
it works implicitly . gmail api reads the headers for BCC / to: etc. I'll see about improving the command line args and usage