similar to: Master Login

Trying to get the master password to work. What am I doing wrong? Trying this test: /etc/dovecot.masterusers master:{plain}test auth_master_user_separator=* auth default_with_listener { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes #pass =yes } passdb passwd-file { # Path for

I want to set up a Master Password that will authenticate to any account. How would I do that? (Don't need to hear about why I shouldn't so don't waste my time replying with a security lecture)

Here's what I'd like. Limited master users, where someone can be a master users for some domains but not others. I think I could do what I want with the right kinds of variable passing that doesn't yet exist. Let me see if I can explain clearly. From the example in the wiki: auth_master_user_separator = * passdb { driver = sql args = /etc/dovecot/dovecot-sql-master.conf.ext

I guess Dovecot has an LDA called deliver. What is it and how do I use it? Or is it ready to be used. can't find any docs on it. -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

Can't figure out why the login is slow. I telnet to port 143 on localhost. I type: 0 login user password Takes about 10 seconds and it lets me in. I'm using MYSQL and it's a small indexed database on a fast server so it's not the mysql query that's slowing it down. At least I don't think it is. But - kind of stumped. Just wondering if there's something obvious

Help... Dovecot 1.0alpha1 hung up today with nothing working and the following spewing to my syslog: pipe() failed: Too many open files My setup: Solaris 9, just using imap, mbox format. The various "max" settings in dovecot.conf use the defaults. Suggestions on what to change in fovecot.conf to keep this from happening? Jeff Earickson Colby College

I tried activating this code in the example config file and it failed to create the socket. You might want to look inti this. Running alpha1. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

> On July 11, 2017 at 11:50 AM azurit at pobox.sk wrote: > > > > Cit?t azurit at pobox.sk: > > > Cit?t Aki Tuomi <aki.tuomi at dovecot.fi>: > > > >>> On July 10, 2017 at 1:45 PM azurit at pobox.sk wrote: > >>> > >>> > >>> > >>> Cit?t Aki Tuomi <aki.tuomi at dovecot.fi>: > >>> >

Running rc24 and with one user in particular they are getting "(auth) killed with signal 11" when trying to pop email. IMAP works. What causes this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://dovecot.org/pipermail/dovecot/attachments/20070224/195f61be/attachment-0002.html>

Works great with all the beta versions. I installed RC1 and get massive authentication failures. auth_debug_passwords = yes auth_master_user_separator=* auth default_with_listener { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes #pass =yes } passdb passwd-file { # Path for passwd-file

This might require adding some new code to Dovecot to pull this off. But it would be extremely powerful if I could get this to work. Here's the situation. Having a master password is great for helping users and doing tech support. But - suppose I'm hosting many domains and I want to create master passwords for each domain separately so that the owners of the domain can log in as any

Greetings all... We are thinking about using the master DB, so a few admins can impersonate an ordinary user. So, we want to define one master for a set of users. And this administrator cannot be master of the other users? Can this be done somehow? Reading the docs, it seems that if a user is defined as master, it can login as everyone. Thanks for any hint.

Hi Timo, Been trying to track this problem down further. The problem seems to be related to verifying the master user failing. My passdb looks like this: passdb { driver = sql args = /etc/dovecot/dovecot-domain-owner-sql.conf master = yes pass = yes } dovecot-domain-owner-sql.conf contains: user_query = SELECT user_name, domain_name FROM users WHERE user_name = '%n' AND

I'm somewhat confused. I need to use a master socket for the dovecot lda but I also need to have a client socket for authenticating through Exim for outgoing smtp. The auth section doesn't allow for two sockets. How do I do this? Thanks in advance.

Hello all. I just wanted to tell you that poprelayd is now compatible with Dovecot. I have just created a parser for the Dovecot server. This might be interesting either for you or your future customers. Maybe you will want to make some advertisement for it ? I remind that poprelayd is a service that allows a POP user to use the SMTP server of the same machine to send e-mails (making relays)

Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP

> On 15 Feb 2018, at 22.16, Travis Dolan <travis.dolan at gmail.com> wrote: > > It would look as though the changes have now negatively affected a "normal" user from logging in. > > > telnet host 143 > > a login username password > > > a NO [AUTHENTICATIONFAILED] Authentication failed. > > > telnet host 143 > > 1 login

Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary.

So Timo, Have you considered the idea of storing all the email in a MySQL database? Seems to me that MySQL could somplify all the backend stuff that everyone struggles with and with replication one could create very massive and reliable systems. What would it take to use MySQL that way?

Just throwing out some thoughts here. I know Timo has high standards and is trying to make 1.0 bug free before calling it 1.0. But I want to argue for an earlier less perfect 1.0. Dovecot is already way past the quality of most 1.0 releases. So it is good enough by common standards. No one really expects a 1.0 release to be perfect. But - some people don't consider a product ripe until it