Typo and fix incorrect URL and file names.
This commit is contained in:
parent
4468f4169c
commit
4fce081c5f
|
@ -535,7 +535,7 @@ greylisting on them is helpless.
|
|||
|
||||
```
|
||||
# cd /tmp
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/40b98d7dde0178d54498e170c8b5165c0316dc96/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
```
|
||||
|
||||
* Login to MySQL database and import this file:
|
||||
|
@ -654,7 +654,7 @@ greylisting on them is helpless.
|
|||
|
||||
```
|
||||
# cd /tmp
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/40b98d7dde0178d54498e170c8b5165c0316dc96/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
```
|
||||
|
||||
* Login to MySQL database and import this file:
|
||||
|
@ -773,7 +773,7 @@ greylisting on them is helpless.
|
|||
|
||||
```
|
||||
# cd /tmp
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/40b98d7dde0178d54498e170c8b5165c0316dc96/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
```
|
||||
|
||||
* Switch to PostgreSQL daemon user, then execute SQL commands to import it:
|
||||
|
|
|
@ -297,8 +297,9 @@ __Note: this step is required if you're running SOGo on RHEL/CentOS, Debian/Ubun
|
|||
|
||||
SOGo team released new stable version v2.3.0 on Jun 2, it requires system
|
||||
admin to run a shell script to update SQL structure manually if you're currently
|
||||
running an old version of SOGo.
|
||||
http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf
|
||||
running an old version of SOGo. We suggest you read SOGo official upgrade
|
||||
tutorial in `Upgrading` section of
|
||||
[Installation Guide](http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf).
|
||||
|
||||
SOGo-2.3.0 ships this update script, please find it with your package management
|
||||
tool like `yum`, `dpkg`.
|
||||
|
@ -318,23 +319,23 @@ Find the update script shipped in SOGo-2.3.0 and run it:
|
|||
|
||||
```
|
||||
# rpm -ql sogo | grep 'sql-update-2.2.17'
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.1.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.1.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.2.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.2.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
```
|
||||
|
||||
* on Debian/Ubuntu:
|
||||
|
||||
```
|
||||
# dpkg -L sogo | grep 'sql-update-2.2.17'
|
||||
/usr/share/doc/sogo/sql-update-2.1.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo/sql-update-2.1.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
/usr/share/doc/sogo/sql-update-2.2.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo/sql-update-2.2.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
```
|
||||
|
||||
Please pick the one for your SQL server. here we use the one for MySQL
|
||||
backend on CentOS for example:
|
||||
|
||||
```
|
||||
# bash /usr/share/doc/sogo-2.3.0/sql-update-2.1.17_to_2.3.0-mysql.sh
|
||||
# bash /usr/share/doc/sogo-2.3.0/sql-update-2.2.17_to_2.3.0-mysql.sh
|
||||
Username (root): root
|
||||
Hostname (127.0.0.1):
|
||||
Database (root): sogo
|
||||
|
|
|
@ -515,7 +515,7 @@ greylisting on them is helpless.</p>
|
|||
<li>Download SQL template file:</li>
|
||||
</ul>
|
||||
<pre><code># cd /tmp
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/40b98d7dde0178d54498e170c8b5165c0316dc96/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
|
@ -612,7 +612,7 @@ greylisting on them is helpless.</p>
|
|||
<li>Download SQL template file:</li>
|
||||
</ul>
|
||||
<pre><code># cd /tmp
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/40b98d7dde0178d54498e170c8b5165c0316dc96/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
|
@ -709,7 +709,7 @@ greylisting on them is helpless.</p>
|
|||
<li>Download SQL template file:</li>
|
||||
</ul>
|
||||
<pre><code># cd /tmp
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
# wget https://bitbucket.org/zhb/iredmail/raw/40b98d7dde0178d54498e170c8b5165c0316dc96/iRedMail/samples/cluebringer/greylisting-whitelist.sql
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
|
|
|
@ -287,8 +287,9 @@ enable-threads = true
|
|||
<p><strong>Note: this step is required if you're running SOGo on RHEL/CentOS, Debian/Ubuntu.</strong></p>
|
||||
<p>SOGo team released new stable version v2.3.0 on Jun 2, it requires system
|
||||
admin to run a shell script to update SQL structure manually if you're currently
|
||||
running an old version of SOGo.
|
||||
http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf</p>
|
||||
running an old version of SOGo. We suggest you read SOGo official upgrade
|
||||
tutorial in <code>Upgrading</code> section of
|
||||
<a href="http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf">Installation Guide</a>.</p>
|
||||
<p>SOGo-2.3.0 ships this update script, please find it with your package management
|
||||
tool like <code>yum</code>, <code>dpkg</code>.</p>
|
||||
<ul>
|
||||
|
@ -309,21 +310,21 @@ tool like <code>yum</code>, <code>dpkg</code>.</p>
|
|||
<li>on RHEL/CentOS:</li>
|
||||
</ul>
|
||||
<pre><code># rpm -ql sogo | grep 'sql-update-2.2.17'
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.1.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.1.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.2.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo-2.3.0/sql-update-2.2.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>on Debian/Ubuntu:</li>
|
||||
</ul>
|
||||
<pre><code># dpkg -L sogo | grep 'sql-update-2.2.17'
|
||||
/usr/share/doc/sogo/sql-update-2.1.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo/sql-update-2.1.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
/usr/share/doc/sogo/sql-update-2.2.17_to_2.3.0-mysql.sh # <- for MySQL
|
||||
/usr/share/doc/sogo/sql-update-2.2.17_to_2.3.0.sh # <- for PostgreSQL
|
||||
</code></pre>
|
||||
|
||||
<p>Please pick the one for your SQL server. here we use the one for MySQL
|
||||
backend on CentOS for example:</p>
|
||||
<pre><code># bash /usr/share/doc/sogo-2.3.0/sql-update-2.1.17_to_2.3.0-mysql.sh
|
||||
<pre><code># bash /usr/share/doc/sogo-2.3.0/sql-update-2.2.17_to_2.3.0-mysql.sh
|
||||
Username (root): root
|
||||
Hostname (127.0.0.1):
|
||||
Database (root): sogo
|
||||
|
|
Loading…
Reference in New Issue