Apple. Email account parameters on the device.
All parameters
| Parameter | Purpose and values | Verification and dependencies |
|---|---|---|
| Account signature | Displayed description of the email account. | Check the name in Mail. |
| Account type | IMAP or POP. | Select the protocol of your mail server; storage and synchronization modes differ. |
| Prefix | Mail profile prefix provided by the form. | Ask the mail administrator for the required value. |
| Account name | Displayed name of the owner/account. | Does not replace the authentication login. |
| Email address | Mailbox address. | Compare with the permitted sender. |
| Incoming server: address | DNS name of the IMAP/POP server. | Check DNS and the TLS certificate. |
| Incoming server: port | Port of the selected protocol at the provider. | Do not enter the SMTP port. |
| Incoming server: user | Incoming mail login. | The login format is defined by the provider. |
| Incoming server: authentication | None, Password, NTLM, MD5 Challenge-Response, HTTP MD5 Digest. | Select a method supported by the server; the presence of an option in the form does not mean it is suitable for your server. |
| Incoming server: password | Password or an app password permitted by the provider. | Do not place the secret in examples or shared instructions. |
| Incoming server: SSL | Secure connection for incoming mail. | The port and TLS mode must match the server. |
| Outgoing server: address | DNS name of the SMTP server used for sending. | This is a Mail setting on the device, not the SMTP integration for MDM system emails. |
| Outgoing server: port | Provider SMTP port. | Check the TLS mode. |
| Outgoing server: user | Login for sending email. | Check the right to use the sender address. |
| Outgoing server: authentication | The same authentication method options as for incoming mail. | Check the SMTP AUTH requirements. |
| Outgoing server: password | Secret of the SMTP account. | May differ from the incoming password. |
| Outgoing server: SSL | Secure connection for outgoing mail. | Check actual sending through the required TLS mode. |
| Use incoming password | Reuses the incoming password; the separate outgoing field becomes unavailable. | Enable only if both servers accept the same secret. |
| Prohibit moving messages | By its name, it should restrict moving messages between accounts. | The name of the restriction and the transmitted value differ: the actual direction requires verification. |
| Disable mail synchronization | By its name, it should disable the corresponding synchronization. | The name of the restriction and the transmitted value differ. Do not promise a restriction based on the checkbox alone. |
| Allow sending messages | Permissive sending parameter. | Check sending an email from the device. |
| Use only in the app | Restricts the use of the account to the selected app, as defined by the profile. | Check how the send action is passed from another app. |
| S/MIME signature | Enables digital signing of emails. | A valid signing identity is required; the checkbox does not issue a certificate. |
| Allow changing S/MIME signature | Lets the user change the signature setting. | Check that the switch is available in Mail. |
| Default S/MIME encryption | Sets encryption when an email is composed. | The corresponding certificates and recipient support are required. |
| Allow changing default encryption | Lets the user change the encryption behavior. | Check that the setting is available. |
| Message encryption switch | Shows the encryption choice for an individual message. | Check message composition and the actual S/MIME result. |
Limitations and dependencies
Receiving mail, sending and S/MIME are separate checks. The two restriction switches have a mismatch between the label and the request value; until confirmed on the device, they cannot be used as guaranteed controls.
Creation and assignment
Create a configuration, fill in the parameters and run the preliminary check. After saving, assign recipients. Start with one test device.
Verifying application
In the device card, check the assignment and the latest contact. In client events, find the processing result, then check the feature itself on the device. If the feature has not changed, check the management channel, platform, delivery and compatibility.
Last updated