record sending status
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Perl
- Stars
- 1.3k
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
Idea from user via email
Optionally write a summary of the transaction. Rough first pass:
Attempt time: ....
Remote: [ foo.example.com | |pipe | /path/to/socket ]
Attempted: 1@example.com,2@example.com,3@example.com
Success: 1@example.com
Permanent Failure: 2@example.com
Temporary Failure: 3@example.com
This could optionally be sent to console or logged for later processing
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no files, tests, or entry points. Start by clarifying the transaction summary's scope and the console or logging destination; done should include an optional report containing the attempted recipients and their success, permanent-failure, or temporary-failure status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100