Skip to content

Update smtp wording #313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MichalSalon merged 1 commit into from
Jan 31, 2026
Merged

Update smtp wording #313

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions apps/docs/content/references/smtp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ Port 25, in particular, is frequently exploited for spam distribution across clo
- Professional IP reputation management
- Automated bounce handling

This strict policy stems from a crucial understanding: poor IP reputation from email abuse can cascade across an entire infrastructure. The impact extends beyond email services to affect:
This strict policy protects platform integrity. Poor IP reputation from email abuse can cascade across an entire infrastructure. The impact extends beyond email services to affect:

- Legitimate web applications
- Platform response times
Expand Down Expand Up @@ -203,4 +203,4 @@ When implementing email functionality in your applications:
- Implement proper error handling and retry logic
- Use queue systems for bulk sending to prevent rate limits
- Monitor delivery status and bounce rates
- Keep SMTP libraries and configurations up to date
- Keep SMTP libraries and configurations up to date