# Security checklist for IMAP setting

https://www.nettescil.com.tr/en/knowledgebase/article/en-3216-imap-setting

## Security checklist for IMAP setting

IMAP setting is a topic that requires Combining IMAP, POP3, SMTP, DNS authentication, quota and delivery records under Email (Mail). This article presents a workable control flow for the purpose of Security check; Do not accept information without an up-to-date panel record and verifiable results as a definitive commitment.

### Security check

It lists authority limit, authentication, backup, log, confidential information and rollback checks before the operation.

### Application order to follow

1. Determine who can access which process and apply the principle of least authority.
2. Do not write passwords, API keys, license secrets and personal data in logs or contents.
3. Rerun access, backup, TLS, log and rollback checks after the change.
4. Take the return point for IMAP setting and note the transaction ID.
5. Recheck the frontend result, logs, permissions and provider response.
6. Do not repeat the same process with unexpected result; Evaluate the rollback plan first.

### checklist

- Has the correct product, service or administrative record been selected for IMAP setting?
- Have it been recorded that the current settings and the rollback backup were verified before the change?
- Have the authorization, license, provider or security conditions been checked from the relevant panel?
- Have the post-processing log, result screen and output visible to the user been re-read?

### Safe limits

Check current records in the Nettescil panel for variable information such as price, SLA, warranty, license scope or provider commitment. Do not exclude an unverified commercial or technical promise from this guide.

### If no results

Note the time of error, the relevant service or transaction number, the error text that appears and the last successful step. Forward the customer data, license key, password or API confidential information to the Nettescil support team without adding it to the support message.