Hi,
on the console:
telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
in the logs:
Sep 30 08:56:23 auth: D
Hi guys,
does nobody has any thoughts on this error?
On 28.09.2014 02:48, Tim wrote:
> Hi guys,
>
> I'm running dovecot/postfix on my Debian Jessie maschine:
>
> # dovecot --version
> 2.2.13
> doveconf -n output: http://p.bastelfreak.de/HsVwS/
>
> today I migrated from maildir(located at /var/vm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Steffen
Thanks very much for the hint. I will give it a try later today.
Michael
Am 30.09.14 08:24, schrieb Steffen Kaiser:
> On Mon, 29 Sep 2014, Reindl Harald wrote:
>
> > Am 29.09.2014 um 15:21 schrieb Michael Wechner:
>
> >> hence I would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
yes, that makes sense. I also did now
doveconf -n > /etc/dovecot/dovecot.conf
but I still do not know why the configuration does not work.
I have now downgraded to
Postfix 2.7.0
Dovecot 1.2.9
also using apt-get install dovecot-postfix
but it a
Hi,
You have broken maildir files with wrong S= in them. Usually produced by
maildrop or courier imap's tools. You can fix them with
http://www.dovecot.org/tools/maildir-size-fix.pl
If you compare ls -la and S= in the files you will see the difference.
Cheers,
Toni
On 30.9.2014 10:05, Tim w
On Mon, Sep 29, 2014 at 10:08:41AM +0200, G??tz Reinicke - IT Koordinator wrote:
> The example wiki shows the passwords {SHA1}, in my password file
> they are {SHA}
You don't need to worry about that part, {SHA} and {SHA1} are aliases that
map to the same behaviour:
src/auth/password-sche
On 30.09.2014 11:24, Toni Mattila wrote:
> Hi,
>
> You have broken maildir files with wrong S= in them. Usually produced
> by maildrop or courier imap's tools. You can fix them with
> http://www.dovecot.org/tools/maildir-size-fix.pl
>
I migrated from maildir to mdbox. Seems like the tool only fixe
Currently I'm using
user_query = SELECT 1000 AS uid, 1000 AS gid, '/srv/vmail/%2.256Hu/%Lu' AS
home, ...
so I'm hashing based on %u (basically). But in my SQL db I have a
"unique_identifier" field, which never changes, even when the user is
changing his/her email address (due to marriage or the l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 30 Sep 2014, Ralf Hildebrandt wrote:
Currently I'm using
user_query = SELECT 1000 AS uid, 1000 AS gid, '/srv/vmail/%2.256Hu/%Lu' AS
home, ...
so I'm hashing based on %u (basically). But in my SQL db I have a
"unique_identifier" field, whic
