The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Dec 19, 2025 3:24am

Greptile Summary

This PR adds RFC 8058 compliant one-click unsubscribe support for marketing emails. The changes enable email clients to display a native "Unsubscribe" button by adding proper List-Unsubscribe and List-Unsubscribe-Post headers.

• API Endpoint: Modified POST handler to detect application/x-www-form-urlencoded content type and parse email/token from URL query parameters (as required by RFC 8058 for one-click unsubscribe)
• Mailer Refactoring: Extracted unsubscribe header generation into reusable addUnsubscribeData helper function
• Batch Email Support: Added unsubscribe checking and List-Unsubscribe headers to sendBatchWithResend function, which previously lacked this functionality
• Comment Cleanup: Removed unnecessary inline comments from multiple files

Confidence Score: 5/5

• This PR is safe to merge - it correctly implements RFC 8058 one-click unsubscribe with proper token validation and no security regressions.
• The implementation follows RFC 8058 correctly by parsing email/token from URL params for form-encoded requests. The refactoring is clean and adds missing unsubscribe support to batch emails. Existing tests pass and the token verification ensures security.
• No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant EC as Email Client
    participant API as Unsubscribe API
    participant DB as Database
    
    Note over EC,DB: One-Click Unsubscribe Flow (RFC 8058)
    
    EC->>API: POST /unsubscribe (form-urlencoded)<br/>with email and token in URL
    API->>API: Detect form-urlencoded content type
    API->>API: Parse email and token from URL params
    API->>API: Verify unsubscribe token
    API->>DB: Update email preferences
    DB-->>API: Success
    API-->>EC: 200 OK

    Note over EC,DB: Traditional Unsubscribe Flow
    
    EC->>API: POST /unsubscribe (JSON body)
    API->>API: Parse JSON body with email, token, type
    API->>API: Verify unsubscribe token
    API->>DB: Update email preferences
    DB-->>API: Success
    API-->>EC: 200 OK with message

@greptile