similar to: Count breaks socket

This would make my life a lot easier in migrating to Dovecot. And it should be really easy to implement. Here's how linuxconf does it: Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and

OK - here's whay I need to make it work for my Linuxconf compatible authentication system. First - a question: Will this work? I can find docs on "virtualfile. auth virtualfile { mechanisms = plain digest-md5 userdb = passwd-file /etc/vmail/passwd.%d passdb = passwd-file /etc/vmail/shadow.%d user = root } Then - since the dmain name selects the passwd file, if there were a

Hi, I got strange problem with dovecot LDA; in dovecont.conf: mail_chroot = /srv/vmail --- deliver(test at fakedomain.net): Apr 03 07:28:21 Info: auth input: test at fakedomain.net deliver(test at fakedomain.net): Apr 03 07:28:21 Info: auth input: uid=400 deliver(test at fakedomain.net): Apr 03 07:28:21 Info: auth input: gid=400 deliver(test at fakedomain.net): Apr 03 07:28:21 Info: auth

Having a hard time figuring out something that is supposed to be easy. Tryiong to configure Dovecot so that it provides authentication to Exim for outgoing smtp. Tried different things and getting authentication socket protocol error dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 auth default { # Space

I'm using a very old scheme for doing multiple domains using an old Linuxconf based setup. Each domain has it's own passwd/shadow file. It works but I need something new and modern and has a web interface and perhaps a mysql backend or something else good. So - what are people using out there for managing email users and domains? Thanks in advance.

I have an existing email system and I'm trying to addapt dovecot into it. It uses the linuxconf virtual email format. The way it is set up is there there are multiple passwd/shadow files - one for eact domain. They are in standard format. The names of these files are: /etc/vmail/passwd.domain.com /etc/vmail/shadow.domain.com I tried this: auth_userdb = passwd-file /etc/vmail/passwd.%d

I'm using the following authentication passing the full email address user at domain.com auth default { mechanisms = plain # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/vmail/passwd.%d } user = root } But - what I want to

The default_mail_env is very powerful, but .... If you have multiple databases wouldn't it make sense to have a separate mail environment for each database? For example: userdb passwd { default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/vmail/passwd.%d default_mail_env =

OK - trying to migrate to dovecot and I like what I see so far, but having a hard time getting it to work. I decided to go with the 1.0 version because I need to get away from the ~/Mail namespace. I'm trying to port from a Linuxconf virtual WU-IMAP type config. So - I compiled but then decided I wanted mysql so I tried to reconfigure and now getting compile errors. Looks like I'm

Getting an error on POP only - "Authentication Server Isn't Connected" IMAP works fine. This used to work. not sure what changed.

Since my old config had this: protocols = imap imaps pop3 pop3s ssl_cert_file = /usr/share/ssl/certs/imapd.pem ssl_key_file = /usr/share/ssl/certs/imapd.pem then the convert script should have added ssl = yes Just trying to document all the little issues as I find them.

I have apparently done something to mess up my test installation, as deliver's attempts to send messages now fail with the following error: deliver(user at example.com): execv() failed: No such file or directory In these cases, I have sieve rules trying to send messages. It had been working though, and I've tried going through all the changes I made yesterday (related to dictionary

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

Hi all. Intro: Timo has already done great job providing patch which allows postfix to authenticate directly against dovecot (included in latest postfix sorce code/release). Now I'm looking around for one more thing. I want to use dovecot's user db as source for postfix lookup tables. In particular: virtual_mailbox_maps Main reason is - postfix access rules and fighting against spam.

Hi, I'm working on "avelsieve" SqurrelMail plug-in to implement SIEVE "file" back end for dovecot. 1. My be someone my explain me, how to use client auth socket to authenticate against dovecot-auth unix socket. As fas as I understood login must be sent in form "user\0\user\0password" as base64 encoded string. pp code (I'm using socket used by postfix auth):

After upgrading our CentOS 5 box to the latest revisions last week (including Dovecot 1.1), we're seeing the following error message in the log files. Sieve was working fine with Dovecot 1.0. I have yet to turn up anything via Google for this particular error. SELinux is not logging any error messages at the moment, so I'm pretty sure that we've properly allowed all the SELinux

On 2/14/23 08:49, Orion Poplawski wrote: > On 1/29/23 11:24, Orion Poplawski wrote: >> It seems that thunderbird-102.7.1-1.el8 (at least on CentOS Stream) broke >> OAuth authentication with outlook.office365.com.? Downgrading to >> 102.4.0-1.el8 resolved the issue. >> >> Error console reports: >> >> XHR POST

I'd like to make a suggestion. Let's drop the Alpha and come out with an official version 1.0. Here's my reasons. The 0.9x version are obsolete and people should be using the 1.0 Alpha versions which seem to me to do everything the previous versions did and more. It's as full featured and stable as all other IMAP servers and in my opinion is ready to be called 1.0. The

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 # } # } #}

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.