[exim-dev] [Bug 1342] New: Submission mode should repair bro…

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Phil Pennock
Date:  
À: exim-dev
Nouveaux-sujets: [exim-dev] [Bug 1342] Submission mode should repair broken Message-Id, [exim-dev] [Bug 1342] Submission mode should repair broken Message-Id, [exim-dev] [Bug 1342] Submission mode should repair broken Message-Id, [exim-dev] [Bug 1342] Submission mode should repair broken Message-Id
Sujet: [exim-dev] [Bug 1342] New: Submission mode should repair broken Message-Id
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1342
           Summary: Submission mode should repair broken Message-Id
           Product: Exim
           Version: 4.80.1
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: General execution
        AssignedTo: pdp@???
        ReportedBy: pdp@???
                CC: exim-dev@???



If a message is received in Submission mode and the Message-Id: header is
broken, then we should be fixing it.

Submission mode means we're taking responsibility. DKIM verification is
already out, because we add other headers which DKIM might have asserted the
non-existence of.

My HP printer can send scans directly via email. It can authenticate and
connect on port 465 (not STARTTLS, but SSL-on-connect). A sample header is:

    Message-ID: <-1879363435-1362596707@>


Oww. If my mail-system has taken responsibility, and will sign it, then this
should be repaired.

Am not inclined to make it an option beyond "being in submission mode":
submission means fix up this junk.

Open question is how to log the transformation and where.


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email