feat: Frappe Mail Connector

[s-aga-r]

Integrates Frappe Mail with the Email Account DocType, enabling seamless sending and receiving of emails via the Frappe Mail API.

• Connect to Frappe Mail

  • Basic (API Key and Secret)

    basic.auth.mp4

  • OAuth

    oauth.mp4

• Validate on Save

  When saving the Email Account, the API credentials and mailbox (for inbound and outbound emails) are validated with the Frappe Mail site.

  

• Outbound

  The framework's Email Queue sends an HTTP request to the Frappe Mail API (outbound/send) with a JSON object containing the sender, recipient(s), and raw message. Frappe Mail parses the raw message, signs it with the mailbox domain's DKIM signature, and pushes it to an agent for delivery.

  

• Inbound

  Inbound email handling varies based on the protocol:

  • POP: The pulled email is removed to prevent duplicate pulls.
  • IMAP: Unique Identifiers (UIDs) ensure only new emails are pulled. The maximum UID is maintained in the system and updated with each pull.

  Frappe Mail uses Mail Sync History to keep track of pulled emails, ensuring that each pull retrieves the next set of emails.

  • Handling Multiple Sites/Devices
    The Mail Sync History includes a Source field to differentiate between devices. When making a pull request to Frappe Mail, an X-Site header can be passed to identify the requesting device or source. The default source is the request IP if the X-Site header is not provided.

  • Failed while parsing/processing the raw message
    The EmailAccount.last_synced_at timestamp is passed when requesting emails from Frappe Mail. This timestamp is only updated when the pull request is completed, ensuring no emails are skipped.