Source
Sending API, SMTP & developer experience — found from sitemap — Sweego
Checked for Sweego on 1 Nov 2026
- Page
- https://learn.sweego.io/docs/sending/how_to_send_email_by_smtp
- Checked
- 1 Nov 2026, 09:42 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e0bcb37fb18a68e552837e5e704488f1c78d0d2f3968ec9bb3c7982c3d67f0da
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Smtp sending Report an error
“You can send email by SMTP or API according your needs.”
-
Subdomain mandatory Report an error
“In Sweego, we've decided to make the use of a sub-domain dedicated to emailing mandatory.”
-
Subdomain verification required Report an error
“A subdomain not verified can't send email.”
-
Authentication spf dkim Report an error
“The records created are used for authentication (SPF & DKIM) and bounce management.”
-
Smtp starttls Report an error
“You have to send email with STARTTLS support. (You can use 2525 or 587 port)”
-
Smtp attachments Report an error
“Send an email with attachment”
-
Smtp auth credentials Report an error
“--auth-user "<LOGIN>" --auth-password "<PASSWORD>"”
Scores citing this record
- The Agency Lead Sending API, SMTP & developer experience
- The Agency Lead Message data, retention & security
- The Data Protection Officer Sending API, SMTP & developer experience
- The Shop Operator Sending API, SMTP & developer experience
- The Shop Operator Message data, retention & security
- The Platform Engineer Sending API, SMTP & developer experience
- The Platform Engineer Deliverability & sender reputation
- The Platform Engineer Message data, retention & security
- The SaaS Developer Sending API, SMTP & developer experience
- The SaaS Developer Message data, retention & security
- The Skeptic Sending API, SMTP & developer experience
- The Skeptic Message data, retention & security