Email queue orphaned job detection uses wall clock — vulnerable to clock drift

[hman38705]

Labels: reliability, email

Priority: Medium

Description

src/email/queue.rs uses SystemTime::now() to detect stale/orphaned jobs. If the system clock is adjusted (NTP step, daylight saving, clock skew between instances), jobs can be falsely detected as orphaned or miss the detection window entirely.

Acceptance Criteria

• Replace SystemTime with a monotonic duration tracked from job creation (store job enqueue timestamp in the Redis value, compare against UTC now from the database or a trusted NTP source)
• Add a configurable EMAIL_ORPHAN_THRESHOLD_SECS variable (default 300)
• Add a test that simulates clock skew and verifies orphan detection is not affected

[harryjupiter148]

@harryjupiter148 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, Maintainer. Please, I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @harryjupiter148 to this issue.

[dhareymu]

@dhareymu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer,

Please, I would love to work on this project to fix the issues for you. I promise to work on it swiftly and create a PR for it in no time.

I look forward to working with you. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dhareymu to this issue.

[solidsole]

@solidsole has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to claim this issue. I have reviewed the details and can begin working on a fix right away. Please assign it to me if it's still available. Thanks!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @solidsole to this issue.

[obedojukwu50-stack]

@obedojukwu50-stack has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I will like to work on this issue, I know exactly what to do and will deliver efficiently.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @obedojukwu50-stack to this issue.

[Mirabel64]

@Mirabel64 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I'm a fullStack developer with years of experience, I have worked on several projects, can I please work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mirabel64 to this issue.

[edwarddavid929-png]

@edwarddavid929-png has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would like to work on this project

ℹ️ Repo Maintainers: To accept this application, review their application or assign @edwarddavid929-png to this issue.

[Caneryy]

@Caneryy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello! Can I work on this issue please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Caneryy to this issue.

[drips-wave]

Congratulations, @edwarddavid929-png! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @edwarddavid929-png: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊