Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • mutt mutt
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mutt Project
  • muttmutt
  • Issues
  • #417
Closed
Open
Created Jun 14, 2022 by janedenone@janedenone

pgp_strict_enc has no effect

Hi,

I recently played around with the various crypto/pgp related configuration parameters, and noticed that the value of pgp_strict_enc does not affect mutt's behaviour. Signed messages are not encoded if the message body contains only ASCII characters, and will be encoded (using quoted-printable) otherwise, even with set pgp_strict_enc = no in .muttrc. Why is that?

Related: Quoted-printable is recommended in the (obsolete) RFC 2015 for signed messages, while its successor, RFC 3156, recommends either quoted-printable or base64. Is it correct to assume that mutt still refers to RFC 2015 with respect to encoding PGP signed messages?

Thanks, Jan

Assignee
Assign to
Time tracking