1. 23 Jan, 2020 1 commit
  2. 22 Jan, 2020 1 commit
  3. 20 Jan, 2020 1 commit
  4. 07 Jan, 2020 1 commit
  5. 05 Jan, 2020 3 commits
  6. 04 Jan, 2020 4 commits
  7. 16 Sep, 2019 1 commit
  8. 07 Sep, 2019 1 commit
  9. 22 Aug, 2019 2 commits
  10. 17 Jun, 2019 1 commit
    • ng's avatar
      fix #430 - do not fail on mutt protected headers · 0651daf5
      ng authored
      Although mutt now supports protected headers, the content of a
      message compiled by mutt is just a plain body, without wrapped
      into further mime parts (contrary to other mailers). Also the
      message does not contain a special marked protected headers
      mime part.
      0651daf5
  11. 14 Feb, 2019 2 commits
  12. 03 Feb, 2019 1 commit
    • paz's avatar
      Strip HTML-part if keywords are present to stop leaking them. · f6c4a2f7
      paz authored
      The HTML-part of multipart/alternative-messages also contain the
      keywords. We don't parse them because we don't touch any HTML. In order
      to prevent the keywords from being disclosed to third parties (e.g.
      through resent messages), we strip the HTML-part completely.
      f6c4a2f7
  13. 28 Oct, 2018 1 commit
  14. 07 Oct, 2018 1 commit
  15. 04 Sep, 2018 1 commit
  16. 19 Jul, 2018 2 commits
    • ng's avatar
      Introduce `UNSET-FINGERPRINT` keyword - Implements second part of #260 · 21ca3b3a
      ng authored
      Using the new introduced keyword an admin can now remove the linked
      fingerprint from a subscription. A subscription can only remove
      the fingerprint of themselves.
      
      To unset their own fingerprint admins must additionally pass the
      argument `force`.
      21ca3b3a
    • ng's avatar
      Fix #360 - do not allow setting an empty fingerprint through `SET-FINGERPRINT` · c52b970d
      ng authored
      Check for a valid fingerprint as argument and do not accept an empty
      fingerprint. This will not anymore allow to unset a fingerprint
      through the `SET-FINGERPRINT`. This functionality will be superseeded
      by another keyword.
      
      As part of that fix, wie centralize checking for a valid fingerpint
      and constrain the check to be either 32 (v3) or 40 (v4) characters
      long.
      c52b970d
  17. 16 Jul, 2018 1 commit
  18. 13 Jul, 2018 2 commits
    • ng's avatar
      Improve parsing of keywords - first part of #249 · bc7f412a
      ng authored
      This changes the way how we parse for keywords to the following
      approach:
      
        1. Ignore any empty/pure-whitespace lines at the beginning of
           the first plain_text_part message.
        2. If you match something /^X\-.*/ start matching for plugins,
           else abort.
        3. Once you matched a plugin, but you have a new
           non-empty/pure-whitespace line starting with something
           different than /^X\-.*/ abort looking for plugin names.
      
      This fixes the most common problems with lines starting with `X-`
      further down in the body of an email, while keeping all of the
      existing behavior and functionality.
      
      Any further improvements to the code base and the parsing of
      mails as discussed in #249 is postponed to future work. Tis work
      should go together with work in #359 which will allow to change
      the structure of plugins.
      bc7f412a
    • paz's avatar
      d103f0bb
  19. 10 Jul, 2018 1 commit
  20. 21 Jun, 2018 1 commit
  21. 07 Jun, 2018 2 commits
  22. 28 May, 2018 1 commit
  23. 17 May, 2018 1 commit
  24. 14 May, 2018 1 commit
  25. 30 Apr, 2018 1 commit
  26. 29 Apr, 2018 1 commit
  27. 23 Apr, 2018 1 commit
  28. 19 Apr, 2018 1 commit
  29. 17 Apr, 2018 1 commit
  30. 15 Apr, 2018 1 commit