Accounts, mail and synchronisation, and what 'synced' actually means

Why this matters

Adding a mail account to a phone is the single most common configuration task in end-user support, and it is one of the few places where a technician is expected to know actual field values rather than a concept. The exam asks for them.

The deeper reason it matters is that "synchronised" is a word users and technicians use to mean different things. To a user it means "my stuff is on both". To the protocol it means "one of these two copies is authoritative and the other reflects it", and which one is authoritative decides what happens when something is deleted. Most of the distressing support calls in this area are that misunderstanding arriving at a bad moment.

This lesson also introduces corporate device policy, which is the first time in this course that connecting a personal device has consequences the user did not expect.

The lesson

Adding an account: the fields a mail client needs and where each comes from

A manually configured mail account needs, at minimum:

• The email address and password, or a modern token obtained by signing in.
• Incoming server name and protocol, with a port and a security setting.
• Outgoing server name, with a port and a security setting.
• Whether the outgoing server requires authentication, which is almost always yes and is the field most often left unset.

The port numbers are worth committing to memory because the exam asks for them directly and because a wrong port is the most common manual-setup error:

• IMAP 143 plain, 993 with TLS.
• POP3 110 plain, 995 with TLS.
• SMTP 25 for server-to-server, 587 for submission with authentication, and 465 for implicit TLS submission.

The plain ports exist and should not be used. If a scenario presents a choice between an encrypted and an unencrypted port for the same protocol, the encrypted one is the answer.

Most providers now publish automatic discovery records so a client needs only the address and password. When automatic setup fails, the fallback is manual entry with the values above, and the provider's own support page is the correct source for the server names — not memory.

IMAP against POP3, and why one leaves mail on the server and one does not

This is the examinable distinction in this objective, and it is about where the authoritative copy lives.

• POP3 downloads mail to the device and, by default, deletes it from the server. The device holds the only copy. Folders, read status and deletions are local and are not reflected anywhere else. There is a "leave a copy on the server" option, which helps but does not synchronise state.
• IMAP keeps mail on the server and the device shows a view of it. Folders, read and unread status, flags and deletions all synchronise. Every device sees the same mailbox.

The practical consequences, which are what scenarios describe:

• A user with mail on their phone and nothing on their laptop is usually running POP3 on the phone.
• A user who deleted mail on one device and finds it gone everywhere is running IMAP, and it is working correctly.
• A user who wants the same mailbox on three devices needs IMAP; there is no configuration of POP3 that achieves it properly.
• A user whose mailbox is full at the provider is running IMAP, because POP3 would have emptied it.

Corporate mail commonly uses a vendor synchronisation protocol rather than either, which behaves like IMAP for mail and also carries calendar, contacts and policy.

Corporate mail, device policies and what accepting one actually grants

When a personal device is enrolled for corporate mail, the acceptance prompt is doing more than the user reads. Depending on what the organisation has configured, it may grant the ability to:

• Require a device passcode of a stated complexity and a screen lock timeout.
• Require device encryption.
• Block or allow specific device features.
• Remotely wipe the device — and depending on the configuration, that may mean the whole device rather than only the corporate data.

That last point is the one worth stating to every user before they tap accept, because the support call that follows a remote wipe of a personal phone is the worst one in this job. Where a choice exists, a containerised or work-profile arrangement separates corporate data from personal data so that a wipe removes only the former.

For a technician, the examinable points are that mobile device management enforces policy rather than suggesting it, that enrolment is a consent step with real consequences, and that removing the account is what removes the policy. A device that will not let a user set a four-digit passcode is usually under a policy and not faulty.

Synchronising contacts, calendars and photos, and what happens on deletion

Modern accounts synchronise far more than mail, and each data type has its own toggle. That is why a user can have working mail and missing contacts from the same account — a single switch, not a fault.

The behaviours to know:

• Contacts and calendars synchronise bidirectionally. A contact deleted on the phone is deleted at the provider, and therefore on every other device.
• Photos typically synchronise to a provider's library. Deleting from the device deletes from the library, subject to a recovery period of around thirty days in most services.
• Multiple accounts on one device each carry their own contacts and calendars, and the device merges them for display. A contact that "cannot be deleted" is often in a read-only account view.
• Storage limits stop synchronisation silently in some services, which presents as "my new photos are not appearing on my laptop".

The support habit that prevents the worst outcomes is to ask which copy the user considers to be the real one before changing anything, and to make sure there is a second copy before removing an account. Removing an account from a device generally removes its synchronised data from that device.

Diagnosing an account that receives but does not send, or syncs one folder only

These two symptoms are precise, and each points at a small set of causes.

Receives but does not send. The incoming configuration is correct, so the credentials and the account are fine. The fault is on the outgoing side:

• Outgoing authentication not enabled — the most common cause by a wide margin.
• Wrong outgoing port or security setting.
• The network blocking the submission port, which is why sending works on cellular and fails on a particular office network.
• A provider limit reached, such as a daily send cap.

Syncs one folder only. Almost always an IMAP folder subscription issue: the client is subscribed to the inbox and not to the others. Some clients also limit synchronisation by age or by folder for battery reasons, which produces "my old mail is missing" rather than "my mail is missing".

Nothing syncs at all is a different shape: check whether the account shows an authentication error, whether the device has connectivity on the interface it is trying to use, and whether background data is restricted for that application — which ties directly back to lesson 5.