Phase 11.7 — Email Retry System (Production-Ready)

[vimal-java-dev]

Context:

• Spring Boot backend (Docker, VPS deployed with blue-green)
• Async email already implemented (ThreadPoolTaskExecutor)
• EmailService using interface + SMTP implementation
• PostgreSQL available
• Redis NOT used
• Goal: Add a retry mechanism with failure tracking

Requirements:

• Store failed emails in DB
• Retry using the scheduler
• Track status (PENDING, FAILED, SENT)
• Clean integration with the existing EmailService
• Production-ready design (no overengineering)

Proceed step-by-step.

[vimal-tech-dev]

Assign me.

[vimal-java-dev]

If any Error at the VPS level, do below 1st,

docker stop vimaltech-contact-api-blue
docker rm vimaltech-contact-api-blue

docker image rm ghcr.io/vimal-java-dev/vimaltech-contact-api:latest

docker pull ghcr.io/vimal-java-dev/vimaltech-contact-api:latest
./deploy.sh

---

👉 Ensure it shows MAIL_HOST (NOT SPRING_MAIL_HOST)

docker exec -it vimaltech-contact-api-green printenv | grep MAIL

MAIL_HOST=smtp.zoho.in
MAIL_PORT=587
MAIL_USERNAME=vimal.patel@vimaltech.dev
MAIL_PASSWORD=xxxxxxxxxxxxxxx
APP_MAIL_FROM=vimal.patel@vimaltech.dev
APP_ADMIN_EMAIL=vimal.patel@vimaltech.dev

---

DEBUG at VPS Level

Run:

docker logs vimaltech-contact-api-green -f

docker logs vimaltech-contact-api-green | grep EmailService

Then hit the API.