similar to: Feature Request - Authentication Scheme - Linuxconf

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

I'd like a separate feature for setting umask for index and cache files differently from email files. The reason is that I'm putting indexes in a separate location and I need group create rights in directories. Otherwise what happens is that the first user creates the directories, but the second user for the domain that has a different UID gets an error. default_mail_env =

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 - I thought this was going to be easy. Maybe it is. I'm just not that good at reading directions. Trying to use dsync. Getting this error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) Currently using maildir. The setup is as follows: mail_uid = mail mail_gid = mail mail_location =

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

Hi, We are currently moving from linuxconf/dovecot to a dovecot setup with sql support, the problem we currently facing is having a message sent to a aliase delivered to the user email inbox with dovecot-lda, i have created cedrict at mail.vdl and a alias test at mail.vdl, when i send to cedrict at mail.vdl the message is included in the user inbox file, but when i send to test at mail.vdl

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>

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

Hi, just subscribed after successfully (?) migrating from a somewhat old linuxconf/vimap config. dovecot-1.1.7, x86 A few issues: The index files seem to be created with the wrong permissions. I get numerous ``Dec 24 15:36:29 mail dovecot: POP3(user at domain): stat(/var/run/dovecot/imap-index/domain/user/.imap/INBOX) failed: Permission denied (euid=60107 egid=231 missing +x perm:

I'm running rsync version 3.0.6 in order to migrate a set of objects from an old server to a new one. The set of object to migrate is basically composed of mail dirs which follow a well-defined name pattern, such that I believe it should be easily handled by the --filter option. I'm infact attempting to use the following rsync command in the new server: rsync -auEAXDSvz --delete-after

Did a quick-n-dirty install of 1.1.alpha2 on a Fedora Core 6 server... am getting the following message in the maillog, though there seems to be no problem accessing mail. Error seems to be consistent for all users. Running 1.0.3 on the system previously. Aug 8 22:49:26 stage2 dovecot: IMAP(testuser): mkdir(/var/spool/vmail/192.168.0.199/.imap/testuser) failed: Permission denied This is what

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

Trying to figure out how to convert an existing mbox system to maildir Below is my dovecot.conf file. Tried adding this at the bottom of the file and nothing happens. plugin { convert_mail = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX convert_skip_broken_mailboxes=yes } What am I doing wrong? ## Dovecot 1.0 configuration file # '#' character and everything after it is

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

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

Or you can implement a policy server yourself. :)The protocol is not complicated, json over http. See?https://wiki.dovecot.org/Auth/Policy ---Aki TuomiDovecot oy -------- Original message --------From: Aki Tuomi <aki.tuomi at dovecot.fi> Date: 21/05/2018 19:13 (GMT+02:00) To: Marc Perkel <marc at perkel.com>, dovecot at dovecot.org Subject: Re: Dovecot blacklist?

What would cause this? dovecot: Jul 31 19:31:17 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

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

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

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *