Mail will be deployed to a VM, per T1475.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 2 2023
Zammad 6 has been released in June.
Apr 15 2023
Mar 13 2023
Twitter support discontinuation
Feb 17 2020
Zammad - T1105 - looks better nowadays and a better fit for modern ticketing desk.
A new version 3.2.0 has been released 2019-12-03 and contains an interesting part:
Dec 16 2019
we're at the +18 months moment and Zammad is still in active development, with a new release this December.
Dec 6 2019
Woodscloud is a better fit.
Nov 15 2018
Oct 30 2018
Not maintained anymore at Flockport level. At this stage, we can use as a base template to provision a standalone mail server ourself through Salt.
Nov 9 2017
Oct 28 2017
[ Prioritized as low, as currently, noone received a virus to our installation. Feel free to switch this to normal for a sporadic mail, to high if you're flooded non stop. ]
Oct 23 2017
We are dephasing lxc.
Apr 28 2017
Apr 27 2017
Apr 22 2017
Jan 27 2017
A temporary caretakers lists has been created as aliases in vma, should be deleted and recreated properly in Sympa.
Jan 22 2017
Jan 21 2017
Jan 20 2017
Next configure nginx and run wwsympa-wrapper.fcgi at user 116 (sympa)
Steps 2 and 3 have been done this Thursday.
Jan 18 2017
Sympa software in installed in /var/lib/sympa.
- Install sympa on the mailserver lxc container
- Define two virtual maps in Postfix with virtual_alias_maps, one for our users domains (managed by vma.nasqueron.org), one for our mailing lists domains (managed by Sympa)
- Follow https://tribut.de/blog/sympa-and-postfix/ per T232#6384
- Configure a test@lists.nasqueron.org list
- Configure a second test@lists.ook.space list to determine multidomain works
Jan 17 2017
For the autodiscover format used by Outlook and Android, we can also include in Protocol blocks this information:
Jan 16 2017
DNS configuration
Autoconfig document are published, so step 1 is done.
Done, to test.
Configured on port 587 on mail.nasqueron.org.
There is something we can do for better user experience: use https://tools.ietf.org/html/rfc6186 to provide DNS records about configuration