Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S Sympa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure 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
  • Projets publics
  • Sympa
  • Repository
Switch branch/tag
  • sympa
  • src
  • lib
  • Sympa
  • Robot.pm
Find file BlameHistoryPermalink
  • sikeda's avatar
    [dev] Refactoring: Now S/MIME signing and encryption will be done by bulk.pl. · 6d0d3010
    sikeda authored Aug 13, 2014
    - $message->{shelved}{smime_sign} & $message->{shelved}{smime_encrypt} attributes are set to indicate signing/encryption are required.
    - Messages are checked if encryption is possible on all recipients before they are stored into bulk spool.
    - As a side effect, messages sent by robots will be signed if keys are available.
    
    Known issue: This feature won't be applied to the messages stored into bulk spool before upgrading.
    
    
    git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@11296 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce
    6d0d3010