Compose and reply to personal mail on Android
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Read the prerequisites (#95 and #112), then inspect SendMailRequest and MailboxHandler.Send in internal/web/handler/mailbox.go. Trace the Android mail entry points and existing mailbox tests before defining the integration boundaries. Done means validated compose and reply flows, per-account drafts, safe pending-send handling, and tests for each listed acceptance case.
Written by the indexing model from the issue text.
Description
Roadmap: #76
Goal
Send plain-body mail through the existing personal mailbox contract.
Acceptance criteria
- Compose recipients, subject, and body with validation matching
SendMailRequest. - Reply with the correct parent entry ID and server-supported sender identity.
- Preserve an unsent draft per account; require an explicit send action.
- Prevent repeated pending sends and explain ambiguous timeouts without automatically duplicating delivery.
- Test accepted send, invalid recipient, denied relay, expired session, and reply-thread behavior.
Start: SendMailRequest and MailboxHandler.Send in internal/web/handler/mailbox.go. Attachment transport is a separate contract.
Prerequisites: #95, #112.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 6h 25m
- Merged PRs (30d)
- 18
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wavefnd/wave-platform
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#139 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#137 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wavefnd/wave-platform#136 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 94/100
wavefnd/wave-platform#135 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
wavefnd/wave-platform#133 ·
Maintainers usually reply within 1 day
All issues in wavefnd/wave-platform
Similar issues
-
area: global bug dx priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
grafana/mcp-grafana#1267 ·
Maintainers usually reply within 1 day
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
coverage-gap good-first-pattern help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
GoogleCloudPlatform/k8s-aibom#114 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
txn2/mcp-data-platform#1984 ·
Maintainers usually reply within 1 day