SMTP
SMTP
01 SMTP Components
Message Retrieval
03 Operations
SMTP Server
04 Functionalities and
Security
User Account Naming
05 Conventions
06 Password Guidelines
SMTP
WHAT IS SMTP?
1. SMTP Authentication
- requires the email sender to authenticate (log in) to the SMTP server
using a username and password before sending emails. This prevents
unauthorized users from sending messages through the server,
reducing the risk of spam and email spoofing.
2. TLS (Transport Layer Security)
- TLS provides encryption for the communication between the email
client and the SMTP server. This ensures that the contents of the
email, including the subject, body, and attachments, are encrypted
and cannot be read by anyone intercepting the data.
SMTP Server Functionalities and Security
SMTP Security
1. Standard Format
- Email addresses are usually structured as `[email protected]`.
The `username` is often based on the person’s real name, job title, or
department within the organization. This makes it easier to manage and
identify users.
Example: `[email protected]` or `[email protected]`.
2. Uniqueness
- Each user must have a unique email address within the domain. This
ensures that emails are delivered to the correct individual without any
confusion or overlap.
User Account Naming Conventions
Some general guidelines include:
3. Format Guidelines
- Usernames should avoid special characters, spaces, and non-ASCII
characters to ensure compatibility across different email systems.
- Email addresses are generally case-insensitive, although the domain
portion is always lowercase.
1. Password Length
- A minimum of 8-12 characters is recommended, but longer
passwords (16-20 characters) provide greater security. Password
length increases the time it takes for a brute force attack to
succeed.
2. Complexity
- Passwords should be a mix of uppercase letters, lowercase letters,
numbers, and special characters. This combination makes
passwords harder to guess or crack.
- Example: `D0g$ecure!2024`.
Password Guidelines
3. Password Expiration
- Regularly changing passwords (e.g., every 60-90 days) helps
protect against long-term exposure in the event of a data breach. It
ensures that even if passwords are compromised, they are not
usable for a long time.
5. Avoid Reuse
- Users should not reuse passwords across multiple accounts. This
minimizes the risk of a single compromised account leading to
further breaches.
Password Guidelines