mirror/docker-mailserver.docker-mailserver
1
0
Fork 0
mirror of https://github.com/docker-mailserver/docker-mailserver.git synced 2025-08-03 09:34:33 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

deploy: 59f483f157

Browse source
This commit is contained in:
github-actions[bot] 2023-07-27 00:25:06 +00:00
parent 312ae088d0
commit 459783a1b9
11 changed files with 52 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

2
edge/config/advanced/kubernetes/index.html
View file

@ -1852,7 +1852,7 @@
<span class="w"> </span><span class="nt">ignore-check.kube-linter.io/run-as-non-root</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">&gt;-</span>
<span class="w"> </span><span class="no">&#39;mailserver&#39; needs to run as root</span>
<span class="w"> </span><span class="nt">ignore-check.kube-linter.io/privileged-ports</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">&gt;-</span>
<span class="w"> </span><span class="no">&#39;mailserver&#39; needs privilegdes ports</span>
<span class="w"> </span><span class="no">&#39;mailserver&#39; needs privileged ports</span>
<span class="w"> </span><span class="nt">ignore-check.kube-linter.io/no-read-only-root-fs</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">&gt;-</span>
<span class="w"> </span><span class="no">There are too many files written to make The</span>
<span class="w"> </span><span class="no">root FS read-only</span>

2
edge/config/advanced/mail-fetchmail/index.html
View file

@ -1603,7 +1603,7 @@
<p>To debug your <code>fetchmail.cf</code> configuration run this command:</p>
<div class="highlight"><pre><span></span><code>./setup.sh<span class="w"> </span>debug<span class="w"> </span>fetchmail
</code></pre></div>
<p>For more informations about the configuration script <code>setup.sh</code> <a href="../../setup.sh/">read the corresponding docs</a>.</p>
<p>For more information about the configuration script <code>setup.sh</code> <a href="../../setup.sh/">read the corresponding docs</a>.</p>
<p>Here a sample output of <code>./setup.sh debug fetchmail</code>:</p>
<div class="highlight"><pre><span></span><code><span class="go">fetchmail: 6.3.26 querying outlook.office365.com (protocol POP3) at Mon Aug 29 22:11:09 2016: poll started</span>
<span class="go">Trying to connect to 132.245.48.18/995...connected.</span>

2
edge/config/advanced/mail-forwarding/aws-ses/index.html
View file

@ -1435,7 +1435,7 @@
<h1>AWS SES</h1>
<p><a href="https://aws.amazon.com/ses/">Amazon SES (Simple Email Service)</a> is intended to provide a simple way for cloud based applications to send email and receive email. For the purposes of this project only sending email via SES is supported. Older versions of docker-mailserver used <code>AWS_SES_HOST</code> and <code>AWS_SES_USERPASS</code> to configure sending, this has changed and the setup is mananged through <a href="../relay-hosts/">Configure Relay Hosts</a>.</p>
<p><a href="https://aws.amazon.com/ses/">Amazon SES (Simple Email Service)</a> is intended to provide a simple way for cloud based applications to send email and receive email. For the purposes of this project only sending email via SES is supported. Older versions of docker-mailserver used <code>AWS_SES_HOST</code> and <code>AWS_SES_USERPASS</code> to configure sending, this has changed and the setup is managed through <a href="../relay-hosts/">Configure Relay Hosts</a>.</p>
<p>You will need to create some <a href="https://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html">Amazon SES SMTP credentials</a>. The SMTP credentials you create will be used to populate the <code>RELAY_USER</code> and <code>RELAY_PASSWORD</code> environment variables.</p>
<p>The <code>RELAY_HOST</code> should match your <a href="https://docs.aws.amazon.com/general/latest/gr/ses.html">AWS SES region</a>, the <code>RELAY_PORT</code> will be 587.</p>
<p>If all of your email is being forwarded through AWS SES, <code>DEFAULT_RELAY_HOST</code> should be set accordingly.</p>

2
edge/config/advanced/mail-sieve/index.html
View file

@ -1585,7 +1585,7 @@ If any filter in this filtering chain discards an incoming mail, the delivery pr
<p>All user defined sieve scripts that are managed by ManageSieve are stored in the user's home folder in <code>/var/mail/example.com/user1/home/sieve</code>. Just one Sieve script might be active for a user and is sym-linked to <code>/var/mail/example.com/user1/home/.dovecot.sieve</code> automatically.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>ManageSieve makes sure to not overwrite an existing <code>.dovecot.sieve</code> file. If a user activates a new sieve script the old one is backuped and moved to the <code>sieve</code> folder.</p>
<p>ManageSieve makes sure to not overwrite an existing <code>.dovecot.sieve</code> file. If a user activates a new sieve script the old one is backed up and moved to the <code>sieve</code> folder.</p>
</div>
<p>The extension is known to work with the following ManageSieve clients:</p>
<ul>