commit
4f4a60e21b
|
@ -240,7 +240,7 @@ $(document).ready(function() {
|
||||||
"paging": {
|
"paging": {
|
||||||
"enabled": true,
|
"enabled": true,
|
||||||
"limit": 5,
|
"limit": 5,
|
||||||
"size": 5
|
"size": pagination_size
|
||||||
},
|
},
|
||||||
"filtering": {
|
"filtering": {
|
||||||
"enabled": true,
|
"enabled": true,
|
||||||
|
|
|
@ -49,8 +49,10 @@ The database will be initialized right after a connection to MySQL can be establ
|
||||||
|
|
||||||
## Update mailcow
|
## Update mailcow
|
||||||
|
|
||||||
There is no update routine. You need to refresh your pulled repository clone and apply your local changes (if any). Actually there are many ways to merge local changes. Here is one to
|
There is no update routine. You need to refresh your pulled repository clone and apply your local changes (if any). Actually there are many ways to merge local changes.
|
||||||
stash all local changes, pull changes from the remote master branch and apply your stash on top of it. You will most likely see warnings about non-commited changes; you can ignore them:
|
|
||||||
|
### Step 1, method 1
|
||||||
|
Stash all local changes, pull changes from the remote master branch and apply your stash on top of it. You will most likely see warnings about non-commited changes; you can ignore them:
|
||||||
|
|
||||||
```
|
```
|
||||||
# Stash local changes
|
# Stash local changes
|
||||||
|
@ -61,6 +63,49 @@ git pull
|
||||||
git stash pop
|
git stash pop
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Step 1, method 2
|
||||||
|
Fetch new data from GitHub, commit changes and merge remote repository:
|
||||||
|
|
||||||
|
```
|
||||||
|
# Get updates/changes
|
||||||
|
git fetch
|
||||||
|
# Add all changed files to local clone
|
||||||
|
git add -A
|
||||||
|
# Commit changes, ignore git complaining about username and mail address
|
||||||
|
git commit -m "Local config aat $(date)"
|
||||||
|
# Merge changes
|
||||||
|
git merge
|
||||||
|
```
|
||||||
|
|
||||||
|
If git complains about conflicts, solve them! Example:
|
||||||
|
```
|
||||||
|
CONFLICT (content): Merge conflict in data/web/index.php
|
||||||
|
```
|
||||||
|
|
||||||
|
Open `data/web/index.php`, solve the conflict, close the file and run `git add -A` + `git commit -m "Solved conflict"`.
|
||||||
|
|
||||||
|
### Step 1, method 3
|
||||||
|
|
||||||
|
Thanks to fabreg @ GitHub!
|
||||||
|
|
||||||
|
In case both methods do not work (for many reason like you're unable to fix the CONFLICTS or any other reasons) you can simply start all over again.
|
||||||
|
|
||||||
|
Keep in mind that all local changes _to configuration files_ will be lost. However, your volumes will not be removed.
|
||||||
|
|
||||||
|
- Copy mailcow.conf somewhere outside the mailcow-dockerized directory
|
||||||
|
- Stop and remove mailcow containers: `docker-compose down`
|
||||||
|
- Delete the directory or rename it
|
||||||
|
- Clone the remote repository again (`git clone https://github.com/andryyy/mailcow-dockerized && cd mailcow-dockerized`). **Pay attention** to this step - the folder must have the same name of the previous one!
|
||||||
|
- Copy back your previous `mailcow.conf` into the mailcow-dockerizd folder
|
||||||
|
|
||||||
|
If you forgot to stop Docker before deleting the cloned directoy, you can use the following commands:
|
||||||
|
```
|
||||||
|
docker stop $(docker ps -a -q)
|
||||||
|
docker rm $(docker ps -a -q)
|
||||||
|
```
|
||||||
|
|
||||||
|
### Step 2
|
||||||
|
|
||||||
Pull new images (if any) and recreate changed containers:
|
Pull new images (if any) and recreate changed containers:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
@ -68,6 +113,7 @@ docker-compose pull
|
||||||
docker-compose up -d --remove-orphans
|
docker-compose up -d --remove-orphans
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Step 3
|
||||||
Clean-up dangling (unused) images and volumes:
|
Clean-up dangling (unused) images and volumes:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
|
@ -69,20 +69,20 @@ docker-compose up -d
|
||||||
|
|
||||||
This option is not best-practice and should only be implemented when there is no other option available to archive whatever you are trying to do.
|
This option is not best-practice and should only be implemented when there is no other option available to archive whatever you are trying to do.
|
||||||
|
|
||||||
Simply create a file `data/conf/postfix/check_sender_access` and enter the following content:
|
Simply create a file `data/conf/postfix/check_sasl_access` and enter the following content. This user must exist in your installation and needs to authenticate before sending mail.
|
||||||
```
|
```
|
||||||
user-to-allow-everything@example.com OK
|
user-to-allow-everything@example.com OK
|
||||||
```
|
```
|
||||||
|
|
||||||
Open `data/conf/postfix/main.cf` and find `smtpd_sender_restrictions`. Prepend `check_sasl_access hash:/opt/postfix/conf/check_sender_access` like this:
|
Open `data/conf/postfix/main.cf` and find `smtpd_sender_restrictions`. Prepend `check_sasl_access hash:/opt/postfix/conf/check_sasl_access` like this:
|
||||||
```
|
```
|
||||||
smtpd_sender_restrictions = check_sasl_access hash:/opt/postfix/conf/check_sender_access reject_authenticated_sender [...]
|
smtpd_sender_restrictions = check_sasl_access hash:/opt/postfix/conf/check_sasl_access reject_authenticated_sender_login_mismatch [...]
|
||||||
```
|
```
|
||||||
|
|
||||||
Run postmap on check_sender_access:
|
Run postmap on check_sasl_access:
|
||||||
|
|
||||||
```
|
```
|
||||||
docker-compose exec postfix-mailcow postmap /opt/postfix/conf/check_sender_access
|
docker-compose exec postfix-mailcow postmap /opt/postfix/conf/check_sasl_access
|
||||||
```
|
```
|
||||||
|
|
||||||
Restart the Postfix container.
|
Restart the Postfix container.
|
||||||
|
@ -215,7 +215,7 @@ Open `data/conf/nginx/site.conf` and add a new "catch-all" site at the top of th
|
||||||
```
|
```
|
||||||
server {
|
server {
|
||||||
listen 80 default_server;
|
listen 80 default_server;
|
||||||
server_name _;
|
include /etc/nginx/conf.d/server_name.active;
|
||||||
return 301 https://$host$request_uri;
|
return 301 https://$host$request_uri;
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in New Issue