similar to: mechanisms?

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

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

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 =

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

You forgot to cc the list. ssl_ca is used only for validating client certificates. ---Aki TuomiDovecot oy -------- Original message --------From: Marc Perkel <marc at perkel.com> Date: 21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi <aki.tuomi at dovecot.fi> Subject: Re: SSL error after upgrading to 2.31 On 05/21/2018 07:54 AM, Aki Tuomi wrote:

I've never used namespaces and don't quite know what they do. If I add a namespace then do things like shared folders magically appear to users? Also - I wonder if this is possible. I'd like to create a write only shared folder. I know this is unusual but I have a reason. I'd like to have a folder that people can drag spam into to report missed spam. I want to write only so

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

Trying this and it doesn't work: passdb = passwd-file /etc/vmail/test.%d Apparently it doesn't expand the %d according to the log file. -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

Is there a way to change the name of the .subscriptions file that dovecot looks for to .mailboxlist to be compatible with WU-IMAP? It would be handy for testing and conversion if you had that. BTW - I'm a new user and your software is very well designed. -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

I'm very new to Dovecot - still testing it - and planing to convert in the futire. I see a lot of rapid development here which I like. But I'm wondering if there is any kind of schedule for blessing 1.0 as official - or - what the custom is for a stable release. Just trying to think about when to jump in. I'm fairly brave, but the feature I need we just added today. -- Marc

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 =

I created a testimonials page. Feel free to add to this. http://wiki.dovecot.org/moin.cgi/Testimonials -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

Trying to use the deliver utility and getting this error: error: net_connect(/var/run/dovecot/auth-master) failed: No such file or directory -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

If its too hard for them to setup the pop3 catch all, we can probably put some mapping in place to smtp froward mail to their server. This is more complex on our part so would prefer not to do it that way, but its an option and will require not setup on their part other than make sure their server does not accept mail for anyone other than our server. dovecot-request@dovecot.org wrote: >

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

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

Not directly Dovecot, but a configuration problem. We have a working set-up with Dovecot+Procmail+Sendmail, using POP-before-SMTP. We want to be able to offer email accounts to some local schools, using SquirrelMail (keeps their costs & maintenance down). The whole arrangement is working, but we don't want to have to have 300+ School children as users of our Red Hat Enterprise server,

After upgrading to 2.31 I'm getting this error. Not sure what I'm doing wrong. No (No signatures could be verified because the chain contains only one certificate and it is not self signed.) ssl = yes ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt local mail.ctyme.com { ? protocol imap { ??? ssl_cert =