Skip to content
Snippets Groups Projects
  1. Sep 28, 2024
  2. Feb 22, 2024
  3. Feb 10, 2024
  4. Jan 06, 2024
  5. Dec 27, 2023
  6. Dec 13, 2023
  7. Nov 28, 2023
  8. Oct 21, 2023
  9. Jan 30, 2023
  10. Sep 28, 2022
    • Kristian Klausen's avatar
      Kill the mailman2 server and put the mailman3 server in its place · 893a95f3
      Kristian Klausen authored
      With the final lists migrated to mailman3[1], the mailman2 server can
      finally be killed.
      
      When the mailman3 server was initially setup[2], it was done on a
      separate server because the mailman and mailman3 packages conflicted,
      and the traffic was routed over wireguard (HTTP, LMTP and SMTP).
      
      Instead of installing mailman3 on the original lists.al.org server and
      transferring the data, it was easier just to install the missing pieces
      (basically Postfix and adjusting the Nginx configuration) on the ml3
      server and move the IPs (to keep the IP mail reputation).
      
      So basically the following was done:
      - The IPs for the original lists.al.org was moved to the mailman3.al.org
        server
      - The mailman2 datadir was transferred to mailman3.al.org server, so we
        can keep the pipermail links alive, and import missing mails if needed
      - The original lists.al.org server was decommissioned
      - The mailman3.al.org server was renamed to lists.al.org
      - The missing pieces was added to the mailman3 role (basically Postfix +
        Nginx adjustments)
      - The mailman role was deleted and the mailman3 role renamed to mailman
      
      [1] 75ac7d09 ("mailman: Fourth and final batch of mailman3 migrated lists")
      [2] 9294828f ("Setup mailman3 server")
      
      Fix #59
      Verified
      893a95f3
  11. Sep 10, 2022
  12. Aug 01, 2022
  13. Jun 22, 2022
  14. Jun 08, 2022
  15. May 07, 2022
  16. Jun 02, 2021
  17. May 13, 2021
  18. May 12, 2021
  19. Apr 09, 2021
  20. Feb 14, 2021
    • Kristian Klausen's avatar
      Make ansible-lint happy · 4112bdf9
      Kristian Klausen authored
      yaml: truthy value should be one of [false, true] (truthy)
      yaml: wrong indentation: expected 4 but found 2 (indentation)
      yaml: too few spaces before comment (comments)
      yaml: missing starting space in comment (comments)
      yaml: too many blank lines (1 > 0) (empty-lines)
      yaml: too many spaces after colon (colons)
      yaml: comment not indented like content (comments-indentation)
      yaml: no new line character at the end of file (new-line-at-end-of-file)
      load-failure: Failed to load or parse file
      parser-error: couldn't resolve module/action 'hosts'. This often indicates a misspelling, missing collection, or incorrect module path.
      4112bdf9
  21. Nov 15, 2020
  22. Aug 30, 2020
  23. Jul 08, 2020
  24. May 20, 2020
  25. May 01, 2020
  26. Oct 10, 2019
  27. Sep 12, 2019
  28. Aug 14, 2019
  29. May 06, 2019
  30. Apr 14, 2019
  31. Feb 10, 2019
Loading