Op 10/26/2017 om 1:32 PM schreef Marc Weustink:
> Hi,
>
> I've enabled client certificate authentication for imap and
> managesieve. When I use Thunderbird with the sieve plugin it tries to
> login, but times out.
>
> Initially I reported this to the sieve plugin, but we came to the
> conclusion th
On 28.10.2017 12:24, Alex JOST wrote:
Am 28.10.2017 um 08:30 schrieb Admin Beckspaced:
On 27.10.2017 20:35, Aki Tuomi wrote:
On October 27, 2017 at 6:00 PM Admin Beckspaced
wrote:
Hello dovecot community,
...
If someone could shed some light on this I would be more than
grateful ;)
T
> On October 28, 2017 at 1:41 PM Tobi wrote:
>
>
> Hello list
>
> I saw the response from Vlad in my queue (as dovecot was broken there
> has been no delivery to mailbox) but after fix and queue flush Vlads
> message does not show up in my mailbox.
>
> > Check the systemd unit for ProtectHome
Hello list
I saw the response from Vlad in my queue (as dovecot was broken there
has been no delivery to mailbox) but after fix and queue flush Vlads
message does not show up in my mailbox.
> Check the systemd unit for ProtectHome, and make sure that is turned
> off.
Found these lines in unit fi
Am 28.10.2017 um 08:30 schrieb Admin Beckspaced:
On 27.10.2017 20:35, Aki Tuomi wrote:
On October 27, 2017 at 6:00 PM Admin Beckspaced
wrote:
Hello dovecot community,
...
If someone could shed some light on this I would be more than
grateful ;)
Thanks & greetings
Becki
We actually disc
> On October 28, 2017 at 1:12 PM "Vlad K." wrote:
>
>
> On 2017-10-28 11:51, Tobi wrote:
> >
> > Does anyone have an idea why dovecot suddenly behaves like that?
> >
>
> Since that's CentOS 7, I've heard SystemD tends to go mad (madder than
> usual) and mount the service with readonly paths
On 2017-10-28 11:51, Tobi wrote:
Does anyone have an idea why dovecot suddenly behaves like that?
Since that's CentOS 7, I've heard SystemD tends to go mad (madder than
usual) and mount the service with readonly paths...
--
Vlad K.
:2017-10-28T11:51:Tobi:
> Oct 28 11:39:50 mbox1 dovecot: lmtp(tobs...@brain-force.ch): Error:
> ssY/MGZQ9FnoLgAAC4IaJw:2: sieve: failed to open logfile (LOGGING TO
> STDERR): open(/home/vmail/brain-force.ch/tobster/.dovecot.sieve.log)
> failed: Read-only file system
>
> But a test at cli shows th
Hi list
I have to dovecot instances running which host my mailboxes on Centos7
dovecot.x86_64 1:2.2.26.0-2.el7.centos
installed
dovecot-debuginfo.x86_641:2.2.26.0-2.el7.centos
installed
dovecot-mysql.x86_641:2.2.26.0-2.el7.centos
installed
dovecot-
Thanks, I've tried it.
Unfortunately it didn't help. The error message stays the same.
Am 28.10.2017 um 11:43 schrieb Aki Tuomi:
Try adding
service quota-warning {
chroot =
}
It won't chroot it then, but I'm not sure if that has a huge security impact.
Aki
On October 28, 2017 at 12:13
Try adding
service quota-warning {
chroot =
}
It won't chroot it then, but I'm not sure if that has a huge security impact.
Aki
> On October 28, 2017 at 12:13 PM Michael Härtl wrote:
>
>
> I'm running dovecot 2.2.27 in a alpine based docker container and want
> to log to /dev/stdout. I th
> On October 28, 2017 at 11:37 AM Jerry wrote:
>
>
> On Fri, 27 Oct 2017 21:35:16 +0300 (EEST), Aki Tuomi stated:
>
> >We actually discovered that Android has a bug with DIGEST-MD5, which Google
> >refuses to fix. Also DIGEST-MD5/CRAM-MD5 etc are not really good idea with
> >SSL anyways
>
> C
I'm running dovecot 2.2.27 in a alpine based docker container and want
to log to /dev/stdout. I therefore added this setting:
log_path = /dev/stdout
Logging works fine so far.
Now I've added a quota-warning script. With the log_path setting above
the script creates warnings like:
Oct 28
On Fri, 27 Oct 2017 21:35:16 +0300 (EEST), Aki Tuomi stated:
>We actually discovered that Android has a bug with DIGEST-MD5, which Google
>refuses to fix. Also DIGEST-MD5/CRAM-MD5 etc are not really good idea with
>SSL anyways
Could you actually describe what that bug is? I actually know someone
14 matches
Mail list logo
