Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Define the mailbox attachment contract needed by Android

Open
  • Is something wrong?
#114 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, go
Domain
api, mobile, security

Research direction

Start by reading internal/web/handler/mailbox.go, internal/mail/repository.go, and the internal/identity/ entry points, then review prerequisites #88 and MIME parsing work in #14. Document the attachment contract, including the Android lifecycle and synthetic MIME fixtures, and clearly separate server retrieval, upload, and Android UI tasks when the contract is complete.

Written by the indexing model from the issue text.

Description

android difficulty: advanced enhancement help wanted mail

Roadmap: #76

Goal

Specify attachment support before adding file controls to the Android mailbox. Current SendMailRequest and message views do not expose an attachment contract.

Acceptance criteria

  • Document how incoming MIME parts become stable attachment identifiers and public metadata within an authenticated message view.
  • Specify authorized download/upload behavior, size limits, supported content handling, and retention.
  • Define safe filenames, content types, and account ownership checks with synthetic MIME fixtures.
  • Specify Android file-picker and temporary-file lifecycle requirements without broad storage access.
  • Record the contract and identify separate server retrieval, upload, and Android UI implementation tasks.

Start: internal/web/handler/mailbox.go, internal/mail/repository.go, and internal/identity/. Coordinate with #14 for MIME parsing; do not duplicate that bug fix.

Prerequisites: #88.

Dominant language
Go
Stars
1
Forks
7
Avg merge
1h 45m
Merged PRs (30d)
16

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.