• How to fix missing (standard) headers in reported spam?

    From Andrzej Adam Filip@21:1/5 to All on Fri Mar 4 07:37:15 2022
    I reports spam received in my personal mailboxes at mail servers not
    under my control. I report received spam e.g. via spamcop.net.
    One server uses custom X-* header for recording envelope sender instead
    of pretty standard Return-Path: header.

    How should I mark Return-Path: header generated by "email-client"?
    Could you suggest something better than the example below?

    1: Custom header to mark end of email-client generated headers

    Return-Path: <user@example.com>
    X-Email-Client-Headers: The End
    <all original email client headers>


    2: Custom Received: headers to mark end of email-client generated headers

    Return-Path: <user@example.com>
    Received: from pop3.demon.co.uk
    by localhost with POP3 (fetchmail-6.2.5)
    for user@example.com; Thu, 30 Jun 2005 00:14:08 +0100 (BST)
    <all original email client headers>

    --
    A. Filip

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)