Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #294 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

The email-hardening guide explains phishing risks. Add a small offline teaching tool so learners can inspect original synthetic header examples without receiving or sending a phishing message.

Who might enjoy this

  • Community interests: Purple team, Privacy, Tech
  • Skills: python, security, docs
  • Experience: starter; work style: analytical.
  • Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • A standard-library Python CLI reading only explicitly selected synthetic .eml fixtures.
  • Three original fixtures and an answer key distinguishing From, Reply-To, Return-Path and claimed Authentication-Results, including missing/contradictory headers.

Dependencies and decisions

No prerequisite issue is required. Re-read current main and linked MRs before starting.

Acceptance criteria

  • [ ] The CLI extracts the documented fields from folded/Unicode headers and renders missing headers explicitly.
  • [ ] A forged Authentication-Results header is labeled as an unverified assertion; the offline parser never claims to validate SPF/DKIM or prove authenticity.
  • [ ] Opening a fixture causes no URL resolution, attachment execution or email delivery; malformed input has a bounded clear failure.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Parse the supplied synthetic .eml files and compare the displayed identity fields with the answer key.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No real mailboxes/credentials, lure creation or delivery, domain impersonation campaign, attachment execution or reporting real findings.
  • No mail-provider configuration changes or duplication of #72 SOC overview.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:purple-header-triage -->

Relevant files

Hints

No hints yet.

Activity

  • +50 Hugo Zarate earned S bounty Nov 1

Comments

No comments yet. Be the first to weigh in.

↑ Top