DSR mailbox
Read a mailbox where data subjects send their requests, so that each email starts the GDPR request workflow.
A data subject request (DSR: a person asking
to see, correct, delete or move the personal data you hold about them) often
arrives as an ordinary email. The DSR mailbox connector points Aegis at one
dedicated mailbox, such as privacy@yourcompany.com, over IMAP (the
standard protocol mail programs use to read a mailbox). Aegis reads new emails,
sorts out which ones are requests, and opens a pending request for each one it
recognises, so the legal deadline starts from the day the email arrived.
At a glance
| Direction | Into Aegis. |
|---|---|
| What it brings in |
New (unread) emails in one IMAP mailbox folder (INBOX
by default), up to 50 per run.
|
| Where it lands | Each email is stored and classified by AI. An email recognised with high confidence as a data subject request becomes a pending request, with its acknowledgement and response deadlines started, and an AI draft response; a person reviews it before anything is sent (see GDPR). |
| Credentials and permissions | The IMAP server, port (993 by default), username and password of the mailbox, with TLS on by default. |
| Owner of imported records | A request created from an email is unassigned until someone assigns it. |
| When it runs |
Every 15 minutes, on plans with GDPR automation, and only while the
connector reads
Connected (its last connection test succeeded). With AI
switched off, emails are still collected but not classified.
|
| Set it up |
/connectors/dsr-mailbox, under the GDPR module rather
than a connector module, by a Manager or Admin, on a plan that
includes the connector.
|
Who uses it
- Admin and Manager open the page, save the IMAP settings, test the connection and disconnect the mailbox. Both also receive the notifications the connector sends when it opens a request or finds an email it is unsure about.
- Contributor and Viewer cannot open the page; Aegis redirects them to the access-denied page. They work with the resulting requests in GDPR as their role allows.
Saving and testing also need the GDPR module switched on for your organisation.
On the
Connectors overview, the DSR Mailbox tile is
greyed out with a Premium label when your plan does not include
GDPR automation; without it the mailbox is never read, even if settings are
saved.
What's on this screen
No screenshot of this page was captured for this edition of the guide; the
description below follows the page as it is built. From top to bottom,
/connectors/dsr-mailbox shows:
-
Breadcrumb and header.
Connectors / DSR Mailbox, then the titleDSR Mailbox Setupwith a one-line description of what the mailbox does. -
IMAP Configuration card. The settings form:
IMAP Server,Port,Use TLS(Yes (recommended)orNo),Username,PasswordandMailbox Folder, each with a short hint underneath, and theSave Configurationbutton at the bottom. -
Connection Status card. A status badge (
Not Tested,Testing...,ConnectedorConnection Failed), the last recorded error with its time when there is one, and theTest Connectionbutton. After a successful test a green box headedConnected to IMAP serverlists the host and port, the folder being watched and the total number of folders the account can see. -
Disconnect connector card. Shown only once a configuration
is saved, with a red
Disconnectbutton. - Setup Instructions and How It Works. Two reference cards at the foot of the page: six numbered setup steps, and four short points on what the mailbox does.
Prepare the mailbox
- Create a dedicated address for requests, separate from general inboxes, and publish it as the privacy contact in your privacy notice.
- Switch on IMAP access for that account. In Microsoft 365 this is a mailbox setting; in Google Workspace it is a Gmail setting.
- If the account uses two-factor sign-in, create an app-specific password for Aegis. Many providers reject the ordinary account password over IMAP.
Connect the mailbox
-
Go to
Connectorsand select theDSR Mailboxtile. The setup page opens with theIMAP Configurationcard at the top and the status badge readingNot Tested. -
Enter the
IMAP Serverhost name (for exampleimap.example.com). LeavePortat993andUse TLSatYes (recommended)unless your provider says otherwise; the hint names143for a connection without TLS. -
Enter the
Username(usually the email address) and thePassword. TheSave Configurationbutton stays disabled until both the server and the username are filled in. -
Change
Mailbox Folderonly if requests are filed into a subfolder; it defaults toINBOX. -
Select
Save Configuration. The button readsSaving..., then the settings are stored with the password encrypted. The save is recorded in the audit log. An invalid port or a missing field shows an error above the form and nothing is saved. -
Select
Test Connection. The badge readsTesting...while Aegis signs in and lists the account's folders; it does not read or move any email. On success the badge turns toConnectedand the green box shows the host, folder and folder count. Reading starts at the next 15-minute run.
Saving alone does not start reading the mailbox. Aegis reads it only while
the connector is
Connected, and that state comes from a successful
Test Connection.
When the test fails
A failed test turns the badge to Connection Failed and shows a
short reason. The reason is also kept on the page as the last recorded error,
with the time it was recorded, so it is still there after a reload.
-
IMAP connection test failed: Aegis could not reach or sign in to the server. Check the host, port and TLS setting, and the password (an app-specific password if the account uses two-factor sign-in). The message deliberately leaves out network detail. -
Mailbox "…" not found: the sign-in worked but the folder inMailbox Folderdoes not exist under that name. Correct the folder name, save, and test again. -
DSR Mailbox connector not configured. Save settings first.: you tested before saving. Save, then test.
Every test, passed or failed, is written to the audit log with its outcome.
Change or rotate the settings
-
Open the page. The form shows the saved values; the
Passwordfield is empty and its hint readsLeave blank to keep current. -
Change what you need and select
Save Configuration. To rotate the password, type the new one; leaving it blank keeps the stored one. -
Select
Test Connectionagain. Any change to the saved settings sets the connector back to not connected, so reading pauses until this test succeeds.
A stored password stays tied to the server, port and TLS setting it was entered
for. If you change the IMAP Server or the Port, or
switch Use TLS to No, enter the password again in the
same save; Aegis refuses to carry the old one over, and records the refusal in
the audit log.
Disconnect the mailbox
-
In the
Disconnect connectorcard, selectDisconnect. A confirmation dialog explains that the configuration and credentials are deleted and reading stops. -
Confirm. Aegis deletes the stored settings and password, records the change
in the audit log and returns you to the
Connectorsoverview. Requests already created from emails stay in GDPR. You can configure the mailbox again later.
The AI assist
Each new email is classified by AI as a request or not, and by type (access, erasure, portability and so on). What happens next depends on how confident the classification is:
| Confidence | What Aegis does |
|---|---|
| 70% or more | Opens a pending request with the deadlines started and a note naming the email subject and confidence, then looks up what data you hold on the person and prepares a draft response. Admins and Managers are notified to review and confirm it. |
| 30% to 70% | Opens no request. Admins and Managers are notified that the email needs a person to look at it. |
| Below 30% | Treats the email as not a request and takes no action. |
The AI never acts on its own: a person confirms each request, reviews and edits the draft, and sends the acknowledgement and the response from the request in GDPR. Each classification is an AI action metered against your organisation's AI credits. When AI is switched off for the organisation, or the credits run out, emails are still collected but are left unclassified for the privacy team to handle by hand.
Tips and limits
- Each email is stored once, by its Message-ID, so a mailbox read twice does not duplicate requests.
- Aegis reads only unread emails and marks each one as read once it has stored it. An email someone opens in a mail program before the next run is therefore skipped; keep people out of this mailbox, or mark an email as unread again to have it picked up.
-
If a scheduled run cannot reach the mailbox, the connector switches to
Connection Failedand reading pauses until aTest Connectionsucceeds again. - There is no list of the collected emails in Aegis. Emails in the 30% to 70% band, and emails collected while AI was off, reach a person through the notification or not at all; check the mailbox itself for anything that did not become a request.
-
The
How It Workscard on the page mentions acknowledgement emails. These are sent when a person acknowledges the request in GDPR, not automatically on arrival. - Your organisation has one DSR mailbox; you cannot connect a second one.
Where this connects
Requests are handled in GDPR; the end-to-end flow is in Handle a data subject request. The other connectors and their shared lifecycle are in Connectors, and outgoing email is set up in SMTP.