GovOPlaN/govoplan-mail
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases Wiki Activity

Add mail profile folder mapping for standard IMAP folders #15

New Issue
Open
opened 2026-07-14 17:45:09 +02:00 by zemion · 1 comment
zemion commented 2026-07-14 17:45:09 +02:00
Owner
Copy Link

Context

IMAP append was moved out of generic server settings and is now a campaign delivery setting. The old shared server settings UI also exposed a single Sent folder value, but the more durable design is profile/server-level folder mapping for standard IMAP folders.

Scope

Add mail-profile folder mapping in govoplan-mail for standard folders such as Inbox, Sent, Drafts, Trash, Archive, and Junk.

  • Persist mappings per mail profile/server configuration.
  • Reuse the existing IMAP folder listing/detection endpoints where possible.
  • Migrate or round-trip the existing imap.sent_folder value as the Sent mapping.
  • Let campaign IMAP append keep its campaign override, while being able to default from the selected profile mapping later.
  • Keep campaign consumption behind core/mail capabilities rather than direct module-to-module UI imports.

Acceptance Criteria

  • Mail profile settings can save and display standard folder mappings.
  • Existing profiles with imap.sent_folder keep their effective Sent folder.
  • Folder lookup can populate a detected Sent folder and expose available folders for mapping.
  • Campaign append behavior remains backward compatible with the stored campaign override.
  • Backend and WebUI tests cover save/load, migration or compatibility, and the profile editor model.
## Context IMAP append was moved out of generic server settings and is now a campaign delivery setting. The old shared server settings UI also exposed a single Sent folder value, but the more durable design is profile/server-level folder mapping for standard IMAP folders. ## Scope Add mail-profile folder mapping in `govoplan-mail` for standard folders such as Inbox, Sent, Drafts, Trash, Archive, and Junk. - Persist mappings per mail profile/server configuration. - Reuse the existing IMAP folder listing/detection endpoints where possible. - Migrate or round-trip the existing `imap.sent_folder` value as the Sent mapping. - Let campaign IMAP append keep its campaign override, while being able to default from the selected profile mapping later. - Keep campaign consumption behind core/mail capabilities rather than direct module-to-module UI imports. ## Acceptance Criteria - Mail profile settings can save and display standard folder mappings. - Existing profiles with `imap.sent_folder` keep their effective Sent folder. - Folder lookup can populate a detected Sent folder and expose available folders for mapping. - Campaign append behavior remains backward compatible with the stored campaign override. - Backend and WebUI tests cover save/load, migration or compatibility, and the profile editor model.
zemion commented 2026-07-20 14:44:15 +02:00
Author
Owner
Copy Link

Drift note, 2026-07-20: the shared dirty workspace contains an uncommitted fix for quoting IMAP mailbox names. Preserve or isolate that fix when implementing folder mapping, with focused tests for spaces, delimiters, non-ASCII names, and provider-specific quoting.

Drift note, 2026-07-20: the shared dirty workspace contains an uncommitted fix for quoting IMAP mailbox names. Preserve or isolate that fix when implementing folder mapping, with focused tests for spaces, delimiters, non-ASCII names, and provider-specific quoting.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dataflow
GovOPlaN Dataflow module behavior or integration.
module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-mail#15
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?