similar to: "correct" permissions for login dir

Hello, Dovecot auth protocol 1.0 defines differend command sets for client and master. How can a daemon distinguish a master connection from a client connection? Clients do send CPID and master does not. I have following auth configuration: auth external { socket connect { master { path = /var/state/dovecot/login/master-auth } } } I try to learn my authentication daemon to

Hi Kirill, Thanks for your reply. Such a simple flat file approach would be perfect, and I don't mind at all to require app specific usernames *and* passwords. However, I am unsure how to combine your recipe below with our regular AD userdb/passdb. Perhaps someone can give me some pointers in that direction? MJ On 07/20/2017 06:50 PM, Kirill Miazine wrote: > I'm not familiar

Hello, POP users often keep fetched mail on server, by checking for "leave mail on server" or similar option in their client. What would be the best way to disallow them using such approach. That is, what is the best way to force deletion of messages that have been RETRieved in a POP session at the end of that POP session? RETRieved messages will be marked as \Seen, but since users

Just a notice to those of you who use Dovecot authentication with Exim. In Dovecot 2.0 authentication server will send a new keyword, COOKIE. This will cause Exim to abort it's authentication request. I submitted a bug and patch to Exim to fix this, the patch is here: http://km.krot.org/code/exim-dovecot-1.1.diff BR, Kirill

Hi all, im doing some tests with the test56 release and im seeing some problems with APPEND (may be related to something else, I just see it with APPEND). When I ask someone to move some emails from one mailbox to another, after some messages (seemingly random), the client experiences a 'hang'. When tracing the process what seems to happen is that dovecot doesnt send a final OK after

Hi, mj * mj [2017-07-20 13:29]: > Hi, > > Further to the other thread about password guessing activities against our > dovecot, I would like to implement application specific passwords on our > dovecot. [...] > > Is there anone here with some additional notes, ideas, tips, trics on > setting up application specific passwords with dovecot with virtual users? > We are

2017-09-07 15:04 GMT+02:00 Sami Ketola <sami.ketola at dovecot.fi>: > > > On 7 Sep 2017, at 16.03, Antoine Nguyen <ngu.antoine at gmail.com> wrote: > > > > 2017-09-07 14:29 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > > > >> > >> > >> On 07.09.2017 15:26, Antoine Nguyen wrote: > >>> Hi all, > >>>

Hi, Further to the other thread about password guessing activities against our dovecot, I would like to implement application specific passwords on our dovecot. Googling results in some documents, but they are all a bit older: > https://www.happyassassin.net/2014/08/26/adding-application-specific-passwords-to-dovecot-when-using-system-user-accounts/ >

* Antoine Nguyen [2017-09-07 15:13]: > 2017-09-07 15:04 GMT+02:00 Sami Ketola <sami.ketola at dovecot.fi>: > > > > > > On 7 Sep 2017, at 16.03, Antoine Nguyen <ngu.antoine at gmail.com> wrote: > > > > > > 2017-09-07 14:29 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > > > > > >> > > >> > > >>

Hi, I would like to know if the pop3-login process would be create more than one while a user connection is established. http://wiki.dovecot.org/RunningDovecot ------------------------------------ imap-login and pop3-login processes handle new IMAP and POP3 connections until user has logged in. ------------------------------------ I'm sorry to ask you this kind of question... Regards,

Greetings, Can Dovecot can handle separate authentication for receiving mail (IMAPS) and sending mail (SMTPS)? In the past, we used Dovecot IMAP for the receiving part and Cyrus SASL for the sending part. This allowed us to use two passwords with mail. Cyrus has grown too old and isn't useful anymore. Can Dovecot give us this functionality: two passwords, one for IMAP

> On 08 January 2019 at 19:39 Rupert Gallagher via dovecot <dovecot at dovecot.org> wrote: > > > Hello, > > I am mosty done with the upgrade, but there is a problem that keeps me awake at night: file ownership and permissions. > > It would be most helpful to have the following from Aki's live system: > > ls -halFR /var/run/dovecot My live config uses

> http://hg.dovecot.org/dovecot-2.2/rev/64c73e6bd397 ==> /var/log/dovecot/dovecot.log <== Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: net_connect_unix(/var/run/dovecot/imap-hibernate) failed: Permission denied Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: Couldn't hibernate imap client: Couldn't export state: Virtual mailboxes have no GUIDs

Did some additional testing with these results. * Configured a new Dovecot host (copied over existing config from 1 of the replicated hosts. * Verified permissions on new host drwxr-xr-x 3 root root 4096 Aug 26 00:05 /etc/dovecot/ drwxr-xr-x 5 root dovecot 800 Aug 26 02:50 /var/run/dovecot/ Made sure address matches new host: service lmtp { user = vmail inet_listener lmtp { address =

Using rpms and converted dovecot.conf with doveconf. Need assistance to determine how to resolve 'auth-worker' and userdb complaint. logging into mysql from commandline with mail admin acct and using dovecot sql query is successful but the following fails: doveadm auth -x service=imap -x lip=127.0.0.1 john Password: passdb: john auth failed extra fields: temp doveadm(root): Fatal:

I notice that the nologin parameter for the AUTH command is gone in version 1.1 of Dovecot Authentication Protocol. nologin was added in 1.1, so that authentication client could indicate that there will be no subsequent master requests to retrieve user info. Could we have nologin back please? Kirill

Hello! doveconf --version 2.2.36 I want to move to a new server with dovecot but get an error Error: service(quota-status): listen(*, 12340) failed: Permission denied when I define service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 } private]# ll insgesamt 0 srw-rw-rw-. 1 postfix postfix 0 14. Apr 15:05 anvil

I?m running Dovecot 2.3.4 on FreeBSD 11.2 with qmail. In my mail log, I see messages like this on every delivery Jan 8 10:30:02 v1 qmail: 1546961402.314222 delivery 533: success: lda(matt,)Error:_net_connect_unix(/var/run/dovecot/stats-writer)_failed:_Permission_denied/did_0+0+1/ Searching for this error, I found a message on a support forum for a different server that suggested adding this to

I have an issue that surfaced when I tried to start using the new metrics service, but it looks like it may be a more generic issue. When I enabled stats and started dovecot, I got the following error in the log: Error: stats: open(/var/run/dovecot/stats-mail) failed: Permission denied /var/run/dovecot/stats-mail did not exist. /var/run/dovecot/ existed, owned by root, which apparently was

Greetings, I'm setting up replication and am getting this error from the server where the replicated mails are being initially created: Aug 27 11:03:53 molecular dovecot: dsync-server(user at domain.org): Error: Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory Can anyone shed some light on this? Here's the Replicator config of the