Am 12.06.2018 um 01:01 schrieb @lbutlr:
I created a sieve_default to move any spam-tagged messages into the Junk
mailbox automatically, but it doesn’t appear to be working (though the other
imapsieve_mailbox… scripts are working).
From doveconf -n
plugin {
imapsieve_mailbox1_before = file
Hi all,
I can't login.
This is a dovecot server for a small inhouse network, and I doon't use
any encryption, and just want to login using the
standard Linux login
dovecot status gives me the following error messages:
un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 12 Jun 2018, Walter Ulmke wrote:
un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't be
supported with given passdbs
Config error.
"Fatal" sounds fatal ;-)
stats: open(old-stats-user) failed: Permission denied
Likew
On 2018-06-12 13:14, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 12 Jun 2018, Walter Ulmke wrote:
un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't
be supported with given passdbs
Config error.
"Fatal" sounds fatal ;-)
stats: open(old-s
On 22 April, 2018 - Tomas Forsman wrote:
> On 21 March, 2018 - Aki Tuomi wrote:
>
> > Thank you for your thorough report, we'll look into it.
>
> Has anyone managed to reproduce this (using my transcript for example)?
Anyone? I would guess more people are affected..
/Tomas
--
Tomas Forsman, s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 12 Jun 2018, Walter Ulmke wrote:
Date: Tue, 12 Jun 2018 14:23:30 +0200
From: Walter Ulmke
To: dovecot@dovecot.org
Subject: Re: cant login to Dovecot
On 2018-06-12 13:14, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just upgraded from 2.2.34 to 2.3.1:
Jun 12 16:06:38
lmtp(exam...@example.name)<46176><8JrHEW7TH1tgtAAAd9aEAw>: Info:
msgid=:
save failed to INBOX: The email account that you tried to reach is over
quota (Mailbox is full).
Jun 12 16:06:38
lmtp(exam...@example.name)<46176><8JrHEW7TH1tgtAAAd9aE
On 2018-06-12 15:18, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 12 Jun 2018, Walter Ulmke wrote:
Date: Tue, 12 Jun 2018 14:23:30 +0200
From: Walter Ulmke
To: dovecot@dovecot.org
Subject: Re: cant login to Dovecot
On 2018-06-12 13:14, Steffen Kaiser wrote:
--
Am 12.06.2018 um 17:10 schrieb Walter Ulmke:
PAM war mir immer schon suspekt.
Ich habe den Bereich auskommentiert und erhalte nun:
auth: Error: stats: open(old-stats-user) failed: Permission denied
Jun 12 17:04:44 ulmke2 dovecot[6883]: auth: Fatal: No passdbs specified
> On 12 June 2018 at 17:27 Tom Sommer wrote:
>
>
> Just upgraded from 2.2.34 to 2.3.1:
>
> Jun 12 16:06:38
> lmtp(exam...@example.name)<46176><8JrHEW7TH1tgtAAAd9aEAw>: Info:
> msgid=:
>
> save failed to INBOX: The email account that you tried to reach is over
> quota (Mailbox is full).
>
Dovecot 2.2.36 + Pigeonhole 0.4.24
Is this an intended behavior?
```
# service dovecot status
dovecot is stopped
# doveconf mail_plugins
mail_plugins = stats
# ls foo.*
foo.sieve
# sievec foo.sieve
sievec(root): Error: stats: open(/var/run/dovecot/stats-mail) failed: No such
device or address
#
On Tue, 12 Jun 2018, Walter Ulmke wrote:
... and just want to login using the standard Linux login
Depends on what you which "standard" you mean but I'll just assume
you're using PAM, as suggested by your config.
auth_mechanisms = plain login digest-md5 cram-md5 ntlm rpa apop anonymous
Loo
12 matches
Mail list logo