Email server profile determines which infrastructure a mailbox will operate on. Robosme supports three profiles.

Exchange

Microsoft Exchange infrastructure is used. The following records are synchronized bidirectionally in this profile:

• Email
• Meeting
• Task
• Contact

Authorization is done through Microsoft's official consent mechanism. User passwords are not entered or stored in Robosme.

For detailed information, Microsoft's official authorization documentation can be reviewed.

Google

Google Workspace (Gmail) infrastructure is used. Similar to the Exchange profile:

• Email
• Calendar (Meeting)
• Task
• Contact

records can be synchronized. Authorization is performed through Google's own OAuth/consent screens. User passwords are not entered or stored in Robosme.

For detailed information, Google's official OAuth and permission documentation can be reviewed.

Custom (POP3 / SMTP)

Used for email servers other than Exchange and Google.

• Incoming emails are received via POP3
• Outgoing emails are sent via SMTP

Meeting, task, or contact synchronization is not performed. Custom profiles are only used for email exchange.

Impact of Server Profile Selection

The selected server profile directly determines which records the mailbox can synchronize:

• Exchange / Google → Email + Calendar + Task + Contact
• Custom → Email only

Therefore, selecting the appropriate server profile is critical for the mailbox behaviors to function correctly.

Synchronization Logic (Brief Information)

Robosme performs bidirectional synchronization at specific intervals for mailboxes with Exchange and Google profiles.
Emails sent through Robosme are transmitted instantly; synchronization period is not waited.