similar to: Can't load private key file

I'm helping a friend setup a small mailserver using dovecot, and I'm finding a strange problem with checkpasswd that I haven't had on my servers. How is the following debug output even possible? Jul 25 12:12:20 company2 dovecot: auth(default): master out: USER 5 joe home=/var/mail/joe.com/joe/Maildir/ uid=1005 gid=1005 Jul 25 12:12:20 company2 dovecot:

Hi there, We recently upgraded to 2.2.12 (the current version in FreeBSD's port tree), and are seeing these errors in our logs (not super frequently, but it happens): May 30 13:20:57 mail1 kernel: pid 15752 (imap), uid 1005: exited on signal 6 May 30 13:20:57 mail1 dovecot: imap(xxx): Fatal: master: service(imap): child 15752 killed with signal 6 (core not dumped - set service imap {

As this is my first message to this ML: Hello! I am using a password-protected SSL key for my dovecot MDA. When I tried to use the ssl_key_password configuration directive as follow: ssl_key_password = </path/to/passfile it did not work as I logged the following: dovecot: imap-login: Error: SSL: Stacked error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt dovecot:

hey friends, I am trying to make postfix run with tls in chroot mode, but I am not able to send the messages with tls on. I am using postfix 2.2.10 on centos 4.0 and I had compiled the postfix from sources with tls & cyrus-sasl support. I copied the certificates from /usr/share/ssl to /etc/postfix. Below are the errors I am getting: May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS

Hello, Thanks for your answer. I read this Wiki tip, but it does not fit, as I serve emails for several domains, each using its iwn (potentioally enciphered) private key. I thus need to use the directive as port of a local_name block. I tried to create 2 blocks in 2 different files automatically loaded from conf.d: ### private.conf ### <-- prevented read permission for other than root:root

I've got a new supermicro server I'm trying to get FreeBSD on. It uses the Intel c602 chipset, and it's my understanding that support for that chipset (c60X) was recently added via the isci driver. Ok, great, that explains why 8.2-R and 9.0-R didn't see the drives. So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, booted it up, and sure enough, as the

We recently upgraded our cluster to 2.1.3, to enable director proxying. Everything appears to be working fine for the most part; the only odd thing is that I'm seeing a lot of entries in the logs like this: Apr 7 02:18:05 mail-out06 dovecot: pop3-login: Fatal: master: service(pop3-login): child 75029 killed with signal 11 (core not dumped - set service pop3-login {

So, to follow up to my previous thread, we just successfully migrated our NFS-based mail cluster from qmail pop, courier imap, and bincimap to dovecot 1.1rc1. Overall the transition was very smooth, the only unexpected adjustment was having to implement ntpd on each box, rather than doing an hourly ntpdate against our local ntpd server, to prevent dovecot from crashing itself from too much

After solving a problem with a sweet little application I discovered (more on that below), I wanted to get some feedback about a potential enhancement for IMAP: standardized, MUA independant, server-side sorting. Currently, there are two basic solutions for sorting: handle it during delivery or handle it in the MUA. However, if you handle it in the MUA, you lose some of the client

We have a checkpassword authentication with mysql pre-fetch for the userdb lookups. When trying to do: doveadm search -u andytest at xecu.net mailbox Trash DELETED I get: doveadm(andytest at xecu.net): Error: user andytest at xecu.net: Auth PASS lookup failed doveadm(andytest at xecu.net): Fatal: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because

v2.1 now saves the base_dir and instance_name to /var/lib/dovecot/instances when starting up. If you have for example two instances with names "backend" and "proxy", you can then use: doveadm -i proxy proxy list instead of something like: doveadm -c /etc/dovecot-proxy/dovecot.conf proxy list The same -i parameter works for all dovecot programs. I also added a couple of new

Hi there, I've been working on rolling out the "deliver" service so we can implement sieve. Dovecot 1.2.11, Postfix 2.6.6, FreeBSD 8, installed by ports. Clustered environment, NFS backend. Everything is working great for the most part, I'm using it to sort a copy of my personal email on a test server. However, I noticed two emails were not properly sorted. I had added a

http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz.sig Looks like it took a bit longer to make this release after RC1 than I thought. I'm now in San Jose area for a few months and still jumping between apartments and trying to adjust to the new timezone. Some of the more important fixes since RC1: - Fixed several race conditions with

http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz.sig Looks like it took a bit longer to make this release after RC1 than I thought. I'm now in San Jose area for a few months and still jumping between apartments and trying to adjust to the new timezone. Some of the more important fixes since RC1: - Fixed several race conditions with

Hi there, After being extremely impressed from implementing it in some customer installations, I've decided to migrate our mail infrastructure to dovecot. Being able to have /bin/checkpassword support across the board for pop, imap, and smtp authentication, as well as being able to ditch stunnel for the SSL layer...where were you in 2001?!? :) I have two concerns, the first is about the

We recently switched to atmail, as well as dovecot. I noticed in atmail the size of the mailboxes was always reported as 0kb. So, I did some debugging, and it boiled down to the fact that the regular expression used by dovecot expected UID before SIZE, but Dovecot returned SIZE before UID. No biggy, I changed the regex, but I was curious if there was a standard. Here's the imap query

I'm in a fairly standard cluster environment: shared storage, bunch of servers each acting as both proxies and backends. We do /bin/checkpassword authentication, allowing a great deal of flexibility...protection against brute force, billing mechanisms, but relevant to this issue, I have it set up to allow users to login with either their username (if they are in one of our default

Hello, I use Dovecot 1.0.12 with Postfix on FreeBSD. It works perfectly, but I have a question. My users are virtual (stocked in a MySQL database). I use SASL Dovecot authentification, and SASL uses my userdb (for POP/IMAP access). However, I would like my users have an other login/password to send email with SMTP/SASL. Or, I don't want my users use the same login/password for POP/IMAP

We're using 2.2.13 with pigeonhole 0.4.3, in a clustered environment (maildir on netapp, dual dovecot instances where each server is both a proxy and a backend). Every now and then (once a month per user, maybe?), users will see a blank email in their inbox. Investigating further, and we will see that the only information recorded in the maildir file for the message is the Return-Path,

I am trying to limit outgoing SMTP traffic to about 14 Mbps and these are the IPFW rules I am using. ${fwcmd} add pipe 1 tcp from 192.168.0.0/24 to any 25 out via dc0 ${fwcmd} pipe 1 config bw 14Mbit/s I've tried multiple tweaks to the pipe rule and I seem to be missing something. I only get about half the bandwidth I specify. Is this normal behavior? Is there something wrong