Galae is a MailCow fork managed by the Algoo company.
It was created with two guiding principles:
- Implement missing functionalities mandatory for the Galae service launch (see below for a complete list)
- Build a scalable production ready stack.
Here is a list of Galae customizations submitted to Mailcow but not yet implemented, with their corresponding issues and PR both on Galae and MailCow sides. Note that since initial Galae implementation, subsequent commits were made when merging from upstream (MailCow to Galae).
MailCow issues and PR states are represent with the following emoji:
- ⏳️ Still open
- ❌ Closed as staled
- 👥 Closed as duplicate
- ⛔️ Closed as refused
- ☑️ Closed with no implementation
- ✅ Closed as completed
| Functionality | Galae Issues | Corresponding MailCow Issues / PR |
|---|---|---|
| DB : allow to use external server | #1, #9 | ⛔️ mailcow#190, ✅ mailcow#456, 👥 mailcow#1539, 👥 mailcow#1774, ⛔️ mailcow#5395, 👥 mailcow#5437, ⏳️ mailcow#5869 |
| Allow "0" as local_part (eg "[email protected]") | #7 | ✅ mailcow#5190, ⛔️ mailcow#5563 with PR ⛔️ mailcow#5565 and ❌ mailcow#5619 |
| Wildcard email alias | #3, #13, #16 | ❌ mailcow#1787, ☑️ mailcow#2077 with PR ❌ mailcow#5881, ❌ mailcow#2507 with PR ⏳️ mailcow#4015 |
The wildcard aliases support introduced in PR #5 requires a database schema update for existing mailcow installations. For the moment, this need to be done manually. Below is a (very) succinct explanation:
- connect to the MySQL mailcow database
- run the following SQL commands:
ALTER TABLE alias ADD COLUMN is_wildcard tinyint(1) NOT NULL DEFAULT '0' AFTER public_comment;
ALTER TABLE domain ADD COLUMN allow_wildcard_aliases tinyint(1) NOT NULL DEFAULT '0' AFTER relay_unknown_only;