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

Cover the untested mail server and report surfaces

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend, testing-qa

Research direction

Start with the TLS report views in services/email/mta/views.py and their tls_report_list.html and tls_report_detail.html templates, then inspect the server entry points in services/email/msa/server.py, services/email/mta/server.py, and msa/management/commands/mta.py. Run the existing test suite to learn its conventions, then cover the listed task, model, parser, handler, and no-current-org branches. Done means tests reach the named production paths and pass.

Written by the indexing model from the issue text.

Description

side quest test

Four untested areas run in production without a test that reaches them. They are one theme, so they are filed together, not as six separate issues.

Deferred findings from the getting started page work. testJoe reported four untested areas during the sweep, and builderJoe hit two of them again.

The findings are:

side quest: services/email/mta/views.py:135-171 TLS report list/detail views and their templates tls_report_list.html, tls_report_detail.html (0%). Outside the diff; untested in the mta selection. [services/email/mta]
side quest: services/email/msa/server.py:85-147 and services/email/mta/server.py:3-88 server entry points, plus msa/management/commands/mta.py. Outside the diff; untested. [services/email/msa, services/email/mta]
side quest: services/email/msa/tasks.py:264-265,344-358; services/email/mta/models.py:222-231,280,295,402; mta/parser.py:29,37-38; mta/handlers.py:114-129. Outside the diff; untested branches. [services/email/msa, services/email/mta]
side quest: services/email/dashboard/context_processors.py:8 no-current-org branch. Outside the diff; not covered by this selection, may be hit by public-page tests elsewhere. [services/email/dashboard]
  • Repo: codingjoe/relay
  • Work reference: branch codingjoe-getting-started-page, git diff origin/main...HEAD, flagged by testJoe during the sweep of that pull request.
  • Why it is deferred: none of it is in that diff. The repo also states that the test suite is planned rather than complete, so these gaps are known backlog and not new regressions.

What to do: cover the TLS report views and the server entry points first. They run in production without a test that reaches them. The task and parser branches come next.

Dominant language
Python
Stars
4
Forks
0
Avg merge
2h 40m
Merged PRs (30d)
163

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 codingjoe/relay

All issues in codingjoe/relay

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.