did some improvements on the server. from
dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-6-amd64 x86_64 Debian 8.11 to # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.8 dovecot is working for days without issues, logging is running to one file /var/log/mail.dovecot In the logfile appears 2019-04-19 18:53:54 imap-login: Info: Login: user=<off...@ourdomain.at>, method=PLAIN, rip=80.75.xx.35, lip=136.xxx.9.172, mpid=28364, TLS, session=<vDTC9uSG2opQS/Yj> All 4 different MUAs Thunderbird are logged in the same way. They are behind a router, so they having the same remote IP. So I cant differentiate, which MUA causes which event. Is there a way, to identify which client raise a special event? Am So., 14. Apr. 2019 um 12:38 Uhr schrieb Reto Brunner via dovecot < dovecot@dovecot.org>: > On Sun, Apr 14, 2019 at 12:04:36PM +0200, Martin Müller via dovecot wrote: > > relay=dovecot, delay=0.13, delays=0.07/0/0/0.06, dsn=4.3.0, > status=deferred > > (temporary failure. Command output: Can't open log file > > /var/log/mail.dovecot-error: Permission denied ) > >[...] > > Here the output of ls -la /var/log/mail.dovecot-error > > -rw-r--r-- 1 root root 21259 Apr 14 11:24 /var/log/mail.dovecot-error > >[...] > > Any hints for me? > > Well, fix the permission errors? > Give write access to the docecot user (or whatever you use) for the log > file. > > Also take care if you use the systemd service, there may be other > restrictions in place (ProtectSystem etc) > -- Martin