https://github.com/roylee0704/go-mail
mail client, written in GO
https://github.com/roylee0704/go-mail
Last synced: 2 months ago
JSON representation
mail client, written in GO
- Host: GitHub
- URL: https://github.com/roylee0704/go-mail
- Owner: roylee0704
- Created: 2016-05-20T10:27:45.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2016-05-20T11:01:15.000Z (almost 9 years ago)
- Last Synced: 2024-12-27T23:09:17.649Z (4 months ago)
- Homepage:
- Size: 1000 Bytes
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# go-mail
mail client in GO
Email is fantastic as it actually represents a whole batch of computer Science
converging in an interesting ways. The level of emails we dealing: **2.8mil emails/sec**.
### Required Parameters
- Server/Port.
- User/Password.
- TSL Enabled.
To send an email.
### How Email Messages Work
There's a standard which splits email up: header/body.
```html
HEADER is what the computer processes, all the fields:
- from: tom@... \n
- to: bob@... \n
- date: \n
- id: \n
\n
\n
BODY is the message that you've read.
\eof
```
All the fields you see, `from`, `to`, `date`, `id`.
Parsing is the way computer looks for specific special ones and special symbols.
So when it stumbles upon `from:` and `to:`, that's gonna be email addresses.
And that simplicity makes it very very fast.
The above has posed as standard to process email.
How do you bold a text? How do you send an image? How may you send an attachment
using this? Computer Science does an awful a lot of work called abstractions and
extension.
```html
HEADER is what the computer processes, all the fields:
- from: tom@... \n
- to: bob@... \n
- date: \n
- id: \n
- mime: \n
\n
\n
BODY is the message that you've read.
/eof
```
It turns out that the body part can be processed by computer as well.