Lightweight SMTP client written in Go

According to RFC 5322, it would appear that non-UTF-7 values must be encoded when used in MIME message headers. Hectane does not currently do this, which leads to errors when sending emails with UTF-8 content in an address or subject line.

The relevant functions / types in Go are located here. I will try to get this fixed within the next two to three days.

(issue originally filed here)

I think Reply-To is a pretty common header. It would be a useful addition to the /send API.

Why is it important to me: Wordpress forms plugin uses the wordpress admin email as From:, but the contacter email's as Reply-To. Setting the contacter as From is possible, but increases the odds of the email being classified as spam. Here, it ends up in spam every time unless I create a special rule based on the email's subject.

I'm a great fan of your project and a great fan of docker. Now I was a great fan of Alpine, while it ran all of my apps from a way smaller image. But I found hectane not working in this environment alpine:3.4 or alpine:edge. Do you which library is missing in Alpine Linux? Maybe we can make it run after all..

Heya,

Having some trouble using go mod, because one of the transitive dependencies is using sirupsen/logrus, like the latest Hexane does (3535bbf44c3f32de551c1b8e5f0dab774cfd7e41).

Problem is the latest Hexane release still has the old repo name.

Is there any chance of cutting a new point release, even though it'll mostly be just the updated sirupsen repo name? :smile:

According to this document, Gmail behaves in the following way when displaying received messages:

• If a message was correctly DKIM signed, a 'signed-by' header with the sending domain will appear.
• If a message was SPF authenticated, a 'mailed-by' header with the domain name will appear.
• If no authentication information exists, you'll see a question mark icon next to the sender's name.

Hectane implements neither of these standards and therefore a question mark appears. It would be nice if this could somehow be fixed.

Although Hectane runs without any issues on Windows, the application must be manually started. It would be excellent if the program could be run as a Windows service, simplifying management.

Note: issue #13 may need to be resolved before this can be completed.

There are a lot of functions (especially in the util package) that need to have unit tests written for them. Since a lot of the code is being rewritten and moved around, having tests to ensure that more stuff doesn't get broken is extremely important.

• [x] NonBlockingChan type
• [x] mail utility functions
• [x] Email to Message conversion

The HTTP interface works extremely well for delivering mail to the queue, but adding support for every framework, blog, and web app out there is becoming tedious. It would be nice if Hectane supported SMTP delivery, like Postfix.

Currently, Hectane writes all log output to stderr (with a special hook for the event viewer on Windows). This leads to problems when Hectane is run under init. Output goes absolutely nowhere. Therefore, an option should be provided to redirect log output to a file.

Hectane expects all information to be provided via command-line arguments. It should also be possible to specify a file containing the configuration. Ideally, this would be in JSON format.

Currently, if the html parameter is not supplied, the text content is HTML-escaped and newlines replaced with <br>. It would be nice if anything looking like a URL was also converted to an <a> link.

I'm using https://github.com/hectane/wordpress-hectane to power a contact form on my website.

It's generating emails like the following

Content-Type: text/plain; charset=utf-8

--03188fce48023ba34a4e459e471c59e0ca9deffbdaea8b926ed6e57dacd7
Content-Type: multipart/alternative; boundary=b972600c5117462370a40eeacdb3c0553d2c1ff177e5366b9bf6acb18302

--b972600c5117462370a40eeacdb3c0553d2c1ff177e5366b9bf6acb18302
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8

--- Name ---

testing

--- Email ---

[email protected]

--- Comment or Message ---

testing



Time: 11/29/2020
IP: <ip>
--b972600c5117462370a40eeacdb3c0553d2c1ff177e5366b9bf6acb18302
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

--- Name ---<br><br>testing<br><br>--- Email ---<br><br>[email protected]<br><b=
r>--- Comment or Message ---<br><br>testing<br><br><br><br>Time: 11/29/2020=
<br>IP: <ip>
--b972600c5117462370a40eeacdb3c0553d2c1ff177e5366b9bf6acb18302--

--03188fce48023ba34a4e459e471c59e0ca9deffbdaea8b926ed6e57dacd7--

03188fce48023ba34a4e459e471c59e0ca9deffbdaea8b926ed6e57dacd7 isn't mentioned anywhere else in the headers. Based on https://github.com/hectane/hectane/blob/master/email/email.go#L40, the Content-Type is supposed to be multipart/mixed, likely mentioning the extra boundary. How can I figure out where the Content-Type header is being dropped?

I learned about hectane from https://github.com/docker-library/wordpress/issues/30#issuecomment-145320414.

I installed the WordPress plugin, and have the following service in my docker-compose.yml:

    mail:
        image: hectane/hectane:0.3.1
        environment:
            LOGFILE: /dev/stderr
            DEBUG: 1
        volumes:
            - mail:/data
        networks:
            - external

WordPress successfully queues mail with hectane:

$ ls -la $(docker volume inspect website_mail --format {{.Mountpoint}})
total 12
drwxr-xr-x 3 root root 4096 Sep 12 00:40 .
drwxr-xr-x 3 root root 4096 Sep 12 00:39 ..
drwx------ 2 root root 4096 Sep 12 00:40 6708342d-b706-499a-b51e-69dca2499388

But hectane cannot connect to the SMTP servers:

$ docker logs $(docker container ls --filter name=mail --format {{.Names}})
time="2019-09-12T00:51:45Z" level=info msg="loaded 1 message(s) from /data" context=Queue 
time="2019-09-12T00:51:45Z" level=info msg="message received in queue" context=<my domain>
time="2019-09-12T00:51:45Z" level=debug msg="connecting to mail server" context=<my domain>
time="2019-09-12T00:51:45Z" level=debug msg="unable to connect to gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:51:47Z" level=debug msg="unable to connect to alt1.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:51:48Z" level=debug msg="unable to connect to alt2.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:51:48Z" level=debug msg="unable to connect to alt3.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:51:49Z" level=debug msg="unable to connect to alt4.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:51:49Z" level=error msg="unable to connect to a mail server" context=<my domain>
time="2019-09-12T00:53:49Z" level=debug msg="connecting to mail server" context=<my domain>
time="2019-09-12T00:53:49Z" level=debug msg="unable to connect to gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:53:51Z" level=debug msg="unable to connect to alt1.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:53:52Z" level=debug msg="unable to connect to alt2.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:53:52Z" level=debug msg="unable to connect to alt3.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:53:53Z" level=debug msg="unable to connect to alt4.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:53:53Z" level=error msg="unable to connect to a mail server" context=<my domain>
time="2019-09-12T00:57:53Z" level=debug msg="connecting to mail server" context=<my domain>
time="2019-09-12T00:57:53Z" level=debug msg="unable to connect to gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:57:55Z" level=debug msg="unable to connect to alt1.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:57:56Z" level=debug msg="unable to connect to alt2.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:57:56Z" level=debug msg="unable to connect to alt3.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:57:57Z" level=debug msg="unable to connect to alt4.gmr-smtp-in.l.google.com" context=<my domain>
time="2019-09-12T00:57:57Z" level=error msg="unable to connect to a mail server" context=<my domain>

What other setup is necessary to get hectane working?

Reading through the docs, I'm not sure what happens to emails in the queue that are rejected. Say the following happens:

1. I start up hectane as a service.
2. A client sends an email via POST /v1/send and gets an empty response back (success).
3. Hectane sees the recipient's server is down and queues the mail.
4. The recipient's mail server never comes back OR it comes back and rejects the email.
5. ???

How can the client find out what happened to the email? The GET /v1/status call doesn't seem to offer a way to check on an email - and there's no real ID we can use to do so.

How can I use this library to send email using Microsoft Outlook SMTP settings? Outlook SMTP settings: Server name: smtp.office365.com Port: 587 Encryption method: STARTTLS

Error relocating /lib/ld-musl-armhf.so.1: RELRO protection failed: Invalid argument
Error relocating /usr/local/bin/hectane: RELRO protection failed: Invalid argument