go-smtp
go-smtp copied to clipboard
emersion
📤 An SMTP client & server library written in Go
List of all extensions: https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml#mail-parameters-2 | Extension | RFC | Client | Server | |-----------------------|--------|--------|--------| | ESMTP | [5321] | ✓ | ✓ | | LMTP | [2033] | ✓...
Right now clients always wait for the server reply for a command before sending the next one. This causes some unnecessary latency due to roundtrips. Possible extended API to allow...
In an environment like kubernetes hosted on AWS, the server needs to handle health checks from load balancers. A TCP health check only checks that a connection can be established,...
Use-case: provide a different hostname over the TLS connection. Ref https://github.com/emersion/go-smtp/pull/184#discussion_r863123368
Resolves https://github.com/emersion/go-smtp/issues/245 Also fixes possible problem with sending only `elho` after `StartTLS` ignoring `helo`
Currently conn.go does not support HELP SMTP command and throws a 502. This presents a problem because many clients, like curl, request HELP upon connection. ``` curl -v "smtp://$SMTP_SERVER_HOST:$SMTP_SERVER_PORT" *...
- [ ] Tests - [ ] Docs - [ ] Consider introducing `LMTPDataCommand` as well - [ ] Consider splitting `Close` and waiting for server reply? Not sure it's...
The usefulness of this package is questionable: it should be pretty trivial for a library user to wrap a backend instead of using this.
Currently, go-smtp starts a new session for every EHLO command it receives. So, any user information, e.g. from AUTH LOGIN, gets lost. [RFC 5321](https://datatracker.ietf.org/doc/html/rfc5321#section-4.1.4) states: > An EHLO command MAY...
These changes allows the smtp server to advertise XOORG capability and extract it into the options. There is a simple test case added and it is tested against Exchange Online...
