similar to: Stable Version

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 =

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

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

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

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:

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

ok - if I'm using a password/shadow file arrangement, what auth mechanisms besides "plain" should I turn on? -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

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

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 =

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

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

I like this unofficial survey of hardware but wondering what MTA and spam filtering everyone is using. I do front end spam filtering for other servers as well. (junkemailfilter.com) I'm using Exim 4.61 SpamAssassin 3.11 Some version of DSpam that I'm experimenting with Most of my spam filtering happens on the Exim level. My mail spam filter server is: AMD 3800 Dual Core Athlon 2 100gb

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

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

Hope to get some attention about this idea to reduce hacking passwords. Here is a list of about 700,000 IP addresses that are hacking passwords through SMTP AUTH http://ipadmin.junkemailfilter.com/auth-hack.txt This is a list of IP addresses that attempted to authenticate against my fake AUTH advertizing on servers with no authentication. We do front end spam filtering for thousands of