similar to: Daemon will not start, invalid argument in stat of base_dir (error within)

Error: stat(/var/run/dovecot) failed: Invalid argument Fatal: Invalid configuration in /etc/dovecot.conf Can someone please help me resolve this issue? I'm willing to pay if required to get this back up! I've been down since 11PM Saturday. Thanks, Frank

Hello, today I run the command "doveadm auth cache flush" for the first time. # doveadm auth cache flush doveadm(root): Error: userdb lookup: connect(/var/run/dovecotauth-master) failed: No such file or directory 0 cache entries flushed # base_dir was the only item contain 'run' and it did not end with a / So I tried to set base_dir to /var/run/dovecot/ and could now rerun

Hi I first let base_dir = with it's default value of /var/dovecot. I changed my mind and now I have doveconf -n # 2.1.17: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.4 amd64 ffs base_dir = /var/run/dovecot/ After a few days, imap clients couldn't login. Here the problem Dec 04 17:03:16 imap-login: Fatal: Corrupted SSL parameters file: /var/dovecot/ssl-parameters.dat Dec 04 17:03:16

I am having problems with dovecot regarding base_dir: I have :: base_dir = /opt/dovecot2/var/run/ For some reason, I have to set permissions to(chmod -R 1777 /opt/dovecot2/var/) for dovecot to run properly, but when I start dovecot, I see this: [root at gw] /opt/dovecot2/etc/dovecot# less /var/log/dovecot/dovecot.log Oct 21 16:15:27 master: Warning: Killed with signal 15 (by pid=72634 uid=0

I can also confirm this, on my own mail server since upgrading to beta1. Dovecot always makes the base_dir world-writable on startup. ----- Forwarded message from Oleg Safiullin <form@pdp-11.org.ru> ----- Date: Fri, 20 Jan 2006 07:09:17 +0600 From: Oleg Safiullin <form@pdp-11.org.ru> To: brad@openbsd.org Subject: dovecot 1.0beta1 Hi. After update dovecot to 1.0beta1 some strange

Hi, I would like to disallow dovecot to read its base_dir (mode 0310). This is currently not possible, because settings_verify() in src/master/master-settings.c will "fix" the directory mode to 0750. The following patch for 1.0rc15 ignores the read bit (0444) when checking the directory permissions. Max -------------- next part -------------- A non-text attachment was scrubbed...

Evening all, I'm running into an issue with lmtp trying to store user mail in 'base_dir' ( same as this ( http://www.dovecot.org/list/dovecot/2011-January/056736.html )) however I'm just using PAM for auth. I've tried with chroot, without chroot and 'chroot'ing lmtp directly in ' service lmtp { } ' which just lead to lots more errors. I've not

Package: xen-hypervisor-4.4-amd64 Version:?4.4.1-9+deb8u3 Severity: important I just upgraded a machine used for hosting a few VM with Xen. The machine was running debian squeeze, so I updated to wheezy and then jessie. Xen is now version 4.4, cpu is 64 bits, dom0 is 32 bits userland with 64 bits kernel?3.16.0-4-amd64. Grub correctly load Xen and dom-0, in fact: # cd /sys/hypervisor/version; cat

Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The

Hi, I have a mailserver(Postfix+MySql) on OpenBSD 4.9 with Dovecot 1.2.16, all works fine. Now i want to do the same but on OpenBSD 5.0. I meet problems using dovecot 2.0.13 on OpenBSD 5.0. Some tests (on the box): telnet 127.0.0.1 110 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. telnet 127.0.0.1 143 Trying 127.0.0.1...

Hello all, I`ve tried to run dovecot many times in my system (Conectiva Linux 9) and was unable to do so. For some reason it gives this message and quits - never runs. My system: Linux ba.gazetaweb.com 2.4.21-28872cl #1 Sex Mar 21 22:02:49 BRT 2003 i686 unknown I`m migrating from UW-IMAPD to dovecot. I've compiled it from sources, using default configurations. Any help

Hello, sorry if the question was asked a couple of times before but I couldn't find any useful hinds to this problem using google and the listman search-engine of the archive of this list. Somehow the ext3 filesystem on one of my machines died an after a reboot grub wouldn't come up again. What I did so far: fsck -y /dev/hda4 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004)

Hi, I am attempting to get dovecot up and running on FreeBSD 4.9..... Tried with the default config file and my own one (below) but when trying to login I get the following: Feb 10 17:59:53 cobain dovecot-auth: passwd(jamie): invalid password field '*' It seems like it is trying to read straight from /etc/passwd? I thought it called getpw(). Is this a common error and could anyone shed

Hi, I've got some trouble here.. i created some sieve rules, but the debug log says that there is a invalid mailbox name error: msgid=<*>: failed to store into mailbox '/home/shared/.automail.Bugtracker/': Invalid mailbox name. ~/.dovecot.sieve if address :is "to" "mantis-admin@<*>" { fileinto

Dear dovecot experts: We are using client certificates to authenthicate against a Dovecot server. Our certificates contain a x500UniqueIdentifier. I'm absolutely sure that the value of the x500UniqueIdentifier was stored into the AUTH_USER when I tested my setup last year. This has somehow changed and now AUTH_USER always contains the username. This has fatal consequences as now every owner

Hi, I am testing dovecot 2.0.13 and 2.0.14 with qmail-ldap and auth_dovecot patch. If i login to dovecot (pop3/imap) with correct user and password. no problem, I can login immediately. but if I try with nonexistant user, dovecot does not immediate answer, wait for a while and says "Waiting for authentication process to respond." auth_dovecot process remains working in the background.

I'm now dealing with issue with some users on mbox getting invalid user settings in /var/adm/messages. /var/log/syslog has: Jul 10 11:21:42 mail2 dovecot: [ID 583609 mail.error] lda(ejames): Error: user ejames: Initialization failed: Namespace '': Mail storage autodetection failed with home=/top/academic/Atmos/people/ejames/home Jul 10 11:21:42 mail2 dovecot: [ID 583609 mail.crit]

http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz.sig This is mainly to fix the 0777 base_dir creation issue, which could be considered a security hole, exploitable by local users. An attacker could for example replace Dovecot's auth socket and log in as other users. Gaining root privileges isn't possible though. This affects only

http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz.sig This is mainly to fix the 0777 base_dir creation issue, which could be considered a security hole, exploitable by local users. An attacker could for example replace Dovecot's auth socket and log in as other users. Gaining root privileges isn't possible though. This affects only

I have recently installed dovecot on a FreeBSD mailserver running postfix. But when I try to login with imap/pop3, I always get an error "stat failed: Not a directory". I guess it is something wrong with the mail format postfix uses to store the message, but I don't seem to find the correct solution. Here's the postfix log with the successful delivery: Feb 17 08:58:24 mailsrv2