b1a294d364
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 5.0.2 to 5.0.4.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](
|
||
|---|---|---|
| .github | ||
| assets | ||
| LICENSES | ||
| log | ||
| smtp | ||
| testdata | ||
| .gitignore | ||
| .golangci.toml | ||
| auth.go | ||
| auth_test.go | ||
| b64linebreaker.go | ||
| b64linebreaker_test.go | ||
| client.go | ||
| client_119.go | ||
| client_120.go | ||
| client_121_test.go | ||
| client_test.go | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CONTRIBUTING.md | ||
| doc.go | ||
| doc_test.go | ||
| eml.go | ||
| eml_test.go | ||
| encoding.go | ||
| encoding_test.go | ||
| file.go | ||
| file_test.go | ||
| go.mod | ||
| go.sum | ||
| go.sum.license | ||
| header.go | ||
| header_test.go | ||
| LICENSE | ||
| msg.go | ||
| msg_test.go | ||
| msg_totmpfile.go | ||
| msg_totmpfile_116.go | ||
| msg_unix_test.go | ||
| msgwriter.go | ||
| msgwriter_test.go | ||
| part.go | ||
| part_test.go | ||
| quicksend.go | ||
| quicksend_test.go | ||
| random.go | ||
| random_test.go | ||
| reader.go | ||
| reader_test.go | ||
| README.md | ||
| REUSE.toml | ||
| SECURITY.md | ||
| senderror.go | ||
| senderror_test.go | ||
| sonar-project.properties | ||
| tls.go | ||
| tls_test.go | ||
go-mail - Easy to use, yet comprehensive library for sending mails with Go
The main idea of this library was to provide a simple interface for sending mails to my JS-Mailer project. It quickly evolved into a full-fledged mail library.
go-mail follows idiomatic Go style and best practice. It has a small dependency footprint by mainly relying on the Go Standard Library and the Go extended packages. It combines a lot of functionality from the standard library to give easy and convenient access to mail and SMTP related tasks.
In the early days, parts of this library (especially some parts of msgwriter.go) had been forked/ported from go-mail/mail and respectively go-gomail/gomail. Today most of the ported code has been refactored.
The smtp package of go-mail has been forked from the original Go stdlib's net/smtp package and has then been extended
by the go-mail team to fit the packages needs (more SMTP Auth methods, logging, concurrency-safety, etc.).
Features
Here are some highlights of go-mail's featureset:
- Very small dependency footprint (mainly Go Stdlib and Go extended packages)
- Modern, idiomatic Go
- Sane and secure defaults
- Implicit SSL/TLS support
- Explicit STARTTLS support with different policies
- Makes use of contexts for a better control flow and timeout/cancelation handling
- SMTP Auth support
- CRAM-MD5
- LOGIN
- PLAIN
- SCRAM-SHA-1/SCRAM-SHA-1-PLUS
- SCRAM-SHA-256/SCRAM-SHA-256-PLUS
- XOAUTH2
- RFC5322 compliant mail address validation
- Support for common mail header field generation (Message-ID, Date, Bulk-Precedence, Priority, etc.)
- Concurrency-safe reusing the same SMTP connection to send multiple mails
- Support for attachments and inline embeds (from file system,
io.Reader,embed.FSorfs.FS) - Support for different encodings
- Middleware support for 3rd-party libraries to alter mail messages
- Support sending mails via a local sendmail command
- Support for requestng MDNs (RFC 8098) and DSNs (RFC 1891)
- DKIM signature support via go-mail-middlware
- Message object satisfies
io.WriterToandio.Readerinterfaces - Support for Go's
html/templateandtext/template(as message body, alternative part or attachment/emebed) - Output to file support which allows storing mail messages as e. g.
.emlfiles to disk to open them in a MUA - Debug logging of SMTP traffic
- Custom error types for delivery errors
- Custom dial-context functions for more control over the connection (proxing, DNS hooking, etc.)
- Output a go-mail message as EML file and parse EML file into a go-mail message
go-mail works like a programatic email client and provides lots of methods and functionalities you would consider standard in a MUA.
Documentation
We aim for good GoDoc documenation in our library which gives you a full API reference. We also provide a more in-depth documentation website at go-mail.dev
Compatibility
Go is growing fast and providing great features with every new release. While we'd love to adopt the latest Go features into our code, we realize that not everybody using this package can run the latest Go versions. Therefore we try to implement alternative solutions for Go versions that do not support these features. Yet, the work needed to maintain the separate versions is not to be underestimated. For that reason, we might retire that code at some point. We guarantee that go-mail will always support the last four releases of Go. With two Go releases per year, this gives the user a timeframe of two years to update to the next or even the latest version of Go.
Support
We have a support and general discussion channel on Discord. Find us at: #go-mail alternatively find us on the Gophers Slack in #go-mail
Middleware
The goal of go-mail is to keep it free from 3rd party dependencies and only focus on things a mail library should
fulfill. Yet, since version v0.2.8 we've added support for middleware on the Msg object, allowing 3rd parties to
alter a given mail message to their needs without relying on go-mail to support their specific need.
To get our users started with message middleware, we've created a collection of useful middlewares. It can be found in a seperate repository: go-mail-middlware.
Merch
Thanks to our wonderful friends at HelloTux we can offer great go-mail merchandising. All merch articles are embroidery to provide the best and most long-lasting quality possible.
If you want to support the open source community and represent your favourite Go mail library with some cool drip, check out our merch shop at: https://www.hellotux.com/go-mail.
Examples
We provide example code in both our GoDocs as well as on our official Website (see Documentation). For a quick start into go-mail check out our Getting started guide.
Authors/Contributors
go-mail was initially created and developed by Winni Neessen, but over time a lot of amazing people contributed ot the project. Big thanks to all of them for improving the go-mail project (be it writing code, testing code, reviewing code, writing documenation or helping to translate the website):
A huge thank you also goes to Maria Letta for designing our super cool go-mail logo!
Sponsors
We sincerely thank our amazing sponsors for their generous support! Your contributions do not go unnoticed and helps keeping up the project!