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

[Feature] Add low-priority POP3 legacy download support #8

New Issue
Closed
opened 2026-07-09 12:47:29 +02:00 by zemion · 2 comments
zemion commented 2026-07-09 12:47:29 +02:00
Owner
Copy Link
Copy Source

Objective

Evaluate and optionally implement POP3 support as low-priority legacy mailbox download support.

POP3 is not a general mailbox browsing protocol for GovOPlaN. It should be added only for deployments that must download mail from legacy servers without IMAP or JMAP.

Scope

  • Owning repository: govoplan-mail.
  • Priority: low.
  • First slice, if implemented: explicit download/import workflow from a POP3 mailbox into managed mail records or a review queue.
  • Out of scope: normal folder browsing, server-side search, multi-folder state, and replacing IMAP/JMAP mailbox UX.

Expected behavior

  • Keep POP3 disabled unless explicitly configured by an admin policy/profile.
  • Provide profile test diagnostics for connection, auth, TLS mode, and message count where available.
  • Support safe preview/list of downloadable messages without exposing credentials.
  • Download messages into a governed local representation with audit evidence.
  • Make deletion-from-server an explicit, separately governed option; default should be non-destructive.

Acceptance criteria

  • POP3 does not appear as a default or recommended mailbox option while IMAP/JMAP are available.
  • A POP3 profile can be tested and can download messages in a controlled workflow when explicitly enabled.
  • UI copy makes the legacy/non-folder semantics clear.
  • Tests cover TLS/auth failures, non-destructive download, optional delete behavior, duplicate prevention, audit evidence, and disabled-by-policy behavior.

Origin

Split out from the closed combined protocol placeholder govoplan-mail#4.

## Objective Evaluate and optionally implement POP3 support as low-priority legacy mailbox download support. POP3 is not a general mailbox browsing protocol for GovOPlaN. It should be added only for deployments that must download mail from legacy servers without IMAP or JMAP. ## Scope - Owning repository: `govoplan-mail`. - Priority: low. - First slice, if implemented: explicit download/import workflow from a POP3 mailbox into managed mail records or a review queue. - Out of scope: normal folder browsing, server-side search, multi-folder state, and replacing IMAP/JMAP mailbox UX. ## Expected behavior - Keep POP3 disabled unless explicitly configured by an admin policy/profile. - Provide profile test diagnostics for connection, auth, TLS mode, and message count where available. - Support safe preview/list of downloadable messages without exposing credentials. - Download messages into a governed local representation with audit evidence. - Make deletion-from-server an explicit, separately governed option; default should be non-destructive. ## Acceptance criteria - POP3 does not appear as a default or recommended mailbox option while IMAP/JMAP are available. - A POP3 profile can be tested and can download messages in a controlled workflow when explicitly enabled. - UI copy makes the legacy/non-folder semantics clear. - Tests cover TLS/auth failures, non-destructive download, optional delete behavior, duplicate prevention, audit evidence, and disabled-by-policy behavior. ## Origin Split out from the closed combined protocol placeholder `govoplan-mail#4`.
zemion added the area/apicodex/readymodule/mail
priority
p3
status
ready
type
feature
 labels 2026-07-29 14:15:12 +02:00
zemion commented 2026-08-22 04:19:06 +02:00
Author
Owner
Copy Link
Copy Source

Starting the autonomous implementation. Scope: an explicitly enabled legacy POP3 endpoint/profile, safe connection diagnostics and message preview, governed non-destructive import with duplicate prevention and audit evidence, and separately controlled delete-after-import behavior. I will use protocol mocks for TLS/auth/error and provider-effect coverage; no live mailbox credentials are required.

Starting the autonomous implementation. Scope: an explicitly enabled legacy POP3 endpoint/profile, safe connection diagnostics and message preview, governed non-destructive import with duplicate prevention and audit evidence, and separately controlled delete-after-import behavior. I will use protocol mocks for TLS/auth/error and provider-effect coverage; no live mailbox credentials are required.
zemion added
status
in-progress
 and removed
status
ready
 labels 2026-08-22 04:19:07 +02:00
zemion commented 2026-08-22 05:16:57 +02:00
Author
Owner
Copy Link
Copy Source

Implemented, verified, released, and catalogued as v0.1.20.

Evidence:

  • Mail commit: 218fef11f1
  • Annotated release tag: v0.1.20 (peels to the Mail commit above)
  • Workspace release-catalog commit: 9fe7ad2cb4ca559d4b91207e96e4478e954a0b53
  • POP3 is disabled by default and explicitly positioned as legacy migration support, not the normal mailbox path.
  • Added TLS/STARTTLS/plain transport handling, sanitized connection/auth diagnostics, bounded message-count and preview operations, governed local import, stable-UIDL duplicate prevention, encrypted raw-message storage, and explicit separately-authorized provider deletion.
  • Preview/import are non-destructive by default. Provider deletion requires both mail:pop3:delete and endpoint policy; ambiguous QUIT results are retained as outcome_unknown evidence.
  • Added tenant/profile visibility boundaries, audit evidence, provider-state diagnostics, DSAR-safe metadata, migration coverage, administrator/user documentation, and a shared-pattern WebUI workflow.

Checks passed:

  • 150 Mail backend tests
  • Mail UI contract suite
  • manifest-shape, lint, compile, focused transport/API tests
  • complete workspace focused gate, including 59 WebUI module permutations and 8 browser conformance tests

No decision or manual verification is required to close this implementation issue. A staging smoke test against a deliberately provisioned legacy POP3 account is still a useful deployment check when credentials are available, but is not needed for implementation correctness because protocol behavior and failure modes are covered by controlled tests.

Implemented, verified, released, and catalogued as v0.1.20. Evidence: - Mail commit: 218fef11f1b9879bdd708c136f1967fde8289735 - Annotated release tag: v0.1.20 (peels to the Mail commit above) - Workspace release-catalog commit: 9fe7ad2cb4ca559d4b91207e96e4478e954a0b53 - POP3 is disabled by default and explicitly positioned as legacy migration support, not the normal mailbox path. - Added TLS/STARTTLS/plain transport handling, sanitized connection/auth diagnostics, bounded message-count and preview operations, governed local import, stable-UIDL duplicate prevention, encrypted raw-message storage, and explicit separately-authorized provider deletion. - Preview/import are non-destructive by default. Provider deletion requires both mail:pop3:delete and endpoint policy; ambiguous QUIT results are retained as outcome_unknown evidence. - Added tenant/profile visibility boundaries, audit evidence, provider-state diagnostics, DSAR-safe metadata, migration coverage, administrator/user documentation, and a shared-pattern WebUI workflow. Checks passed: - 150 Mail backend tests - Mail UI contract suite - manifest-shape, lint, compile, focused transport/API tests - complete workspace focused gate, including 59 WebUI module permutations and 8 browser conformance tests No decision or manual verification is required to close this implementation issue. A staging smoke test against a deliberately provisioned legacy POP3 account is still a useful deployment check when credentials are available, but is not needed for implementation correctness because protocol behavior and failure modes are covered by controlled tests.
zemion removed the
status
in-progress
codex/ready labels 2026-08-22 05:16:59 +02:00
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/approvals
GovOPlaN Approvals 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/committee
GovOPlaN Committee module behavior or integration.
 module/connectors
GovOPlaN Connectors module behavior or integration.
 module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
 module/dashboard
GovOPlaN Dashboard module behavior or integration.
 module/dataflow
GovOPlaN Dataflow module behavior or integration.
 module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
 module/decisions
GovOPlaN formal Decisions module behavior or integration.
 module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
 module/dms
GovOPlaN Dms module behavior or integration.
 module/docs
GovOPlaN Docs module behavior or integration.
 module/encryption
GovOPlaN Encryption key custody, cryptographic policy, and E2EE 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/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
 module/helpdesk
GovOPlaN Helpdesk 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/mandates
GovOPlaN Mandates, jurisdiction, responsibility, and authority 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/parties
GovOPlaN procedure Parties, representation, and delivery-authority 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/projects
GovOPlaN Projects module behavior or integration.
 module/quick-access
GovOPlaN configurable task-local Quick Access behavior and integrations.
 module/records
GovOPlaN Records and eAkte lifecycle 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/services
GovOPlaN versioned institutional Services 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/tickets
GovOPlaN Tickets module behavior or integration.
 module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
 module/voting
GovOPlaN Voting module behavior or integration.
 module/wiki
GovOPlaN Wiki module behavior or integration.
 module/workflow
GovOPlaN Workflow module behavior or integration.
 module/workflow-engine
GovOPlaN Workflow Engine runtime, persistence, 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 labels area/api module/mail
priority
p3
type
feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
govoplan-package-publisher zemion (Albrecht Degering)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-mail#8