similar to: symlink() failure in 1.2 managesieve

Greetings all, I'll skip the details of the setup, except to say that it has a non-standard (and non-templateable) home directory path for virtual users. Ran into the following problem when a debian (possibly from backports) packaged dovecot-1.1.2 was upgraded to a dovecot-1.1.13-2~bpo50+1 (definately from backports): sieve-storage: root directory specified by mail data does not exist:

If I leave the "listen" value as the default in /etc/dovecot.conf I'll get a message similar to the following on each port that it tries to open during startup: # dovecot -F Fatal: listen(::, 143) failed: Address already in use If I set either: listen = * or listen = [::] then it will start up fine. Perhaps it is as though the code tries to open the port twice for both

Hello! A Server running openSUSE 12.3 and dovecot version 2.1.13. In the log I find Oct 19 00:23:23 managesieve(anmeyer at anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/managesieve.sieve). But the link is ok and when I login to roundcube

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha5.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha5.tar.gz.sig It's been a while since alpha4 so I thought I'd release a new one while waiting for Apple's patches.. - mbox fixes. - Lots of Solr fixes - Virtual mailboxes + Solr works now nicely instead of duplicating the indexed data. - Added alias_for setting

Hi, i have 2 dovecot imap server running on solaris 10 The primary server with dovecot 1.0.alpha4 is running with best performance on Sun Sparc E4k5 with 8x 450MHz The secondary with rc10 has ugly performanceproblems on Sun E450 wth 4x 450MHz. Every new imap process takes permanent 25% cpu usage List the folder and fetch message are both slowy! Both servers are configred with ldap backend

Please try if http://dovecot.org/nightly/dovecot-latest.tar.gz (or the CVS directly) works with you. I made a lot of changes to dovecot-auth, so I wouldn't want to make alpha4 release without some more testing in different environments. I'll release alpha4 in a few days, but it'll be basically same as this unless more bugs get fixed. Some of the changes include: - IMAP: We might

Hi, I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious! I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array.

Hi, i don't know. Is normal login_max_processes_count > 1024?? Our environment is about 1700 users (imaps + thunderbird or imaps+horde). The server is RedHat Enterprise Linux 5.2 User logins different in a hour: # cat dovecot.info | grep 'Nov 11 10' | grep "login: Login" | cut -d'<' -f2 | cut -d'>' -f1 | sort | uniq | wc -l 685 Logins in a hour:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, http://hg.rename-it.nl/dovecot-1.2-managesieve/file/tip/README contains the paragraphs (line 47): " mail_location = If, for some inobvious reason, the sieve_storage remains unset, the managesieve daemon uses the specification of the mail_location to find out where to store the sieve files. However, this is provided only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello I'm currently running dovecot-1.0.alpha4-1 on my production system, dovecot-1.0.alpha4-1where I am making use of namespaces. I have downloaded 1.0-beta3 and have installed it on a test system. I have customised the configuration for local use, however when I inserted the namespace settings into my configuration file dovecot refuses to

The actual alpha4 release this time. With a few changes since the pre-release. The important changes again: - Default lock_method changed to flock instead of the old fcntl. Solaris users will need to set it back to fcntl. This makes sure that Dovecot's indexes aren't accidentally used with NFS. - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could

Dear list, I am running dovecot with LDAP. Each account has email in form abc at example.com, and messages are stored at /var/vmail/abc/Maildir. This is an external mail server, and I would like to use a cron job to fetch all messages to an internal server which has slow internet connection. It seems getmail supports multidrop retriever which might fit the bill. However I could not figure out how

Hi, I just installed dovecot 1.1.11 and am having some issues. Mail appears to be delivered to the Maildirs just fine, but when a client (Thunderbird) tries to retrieve them I get this: dovecot: IMAP(info at aedisit.com): maildir_file_do(/var/mail/ > aedisit.com/info/cur/1251566335.V14I27a91M380600.kim): Filename keeps > changing After turning on mail debug mode, I get this: Aug 29

Hello all, I use dovecot11-1.1.7-1.4.1 with OpenSuse 11.1. Everything works fine, except the vacation with managesieve. When i send a mail to an address with vacation, i recieve back a vacation message, but i read an error like this into dovecot-deliver.log: Error: file_dotlock_create(~/.dovecot.lda-dupes) failed: No such file or directory And then the vacation is send any time, without

Howdy, Forgive me if this issue has been more recently addressed in CVS, but a quick scan of the archives didn't turn up any other reports. There appears to be a small typo in src/lib/ioloop-select.c: --- dovecot-1.0.alpha4/src/lib/ioloop-select.c.orig 2005-11-06 22:06:53.000000000 -0800 +++ dovecot-1.0.alpha4/src/lib/ioloop-select.c 2005-11-06 22:07:13.000000000 -0 800 @@ -113,7

On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any. This problem seemed to start happening in alpha3 (and persists in alpha4). When I revert back to alpha2, the messages show up again. It looks like a problem with the dovecot.index*

Hello all, I am struggeling to get my Dovecot SASL to work within postfix. I have used the configuration example listed on the main-site of dovecot and it basically isn't giving me any success at all. I am probably missing something easy, but after spending a few days testing and walking through everything I could think about I thought figured it was better to ask :) Hope someone can point me

Hello, it seems that there is some bug in authentication cache code in dovecot version 1.1.alpha4 - after login attempt with wrong password the correct password also will fail. I can reproduce it very easy: $telnet 10.10.10.30 110 +OK Server. <861.2.46e6c679.jZ8QYpFmU8ZN6XIq7zPhkw==@server2> user testuser +OK pass pass +OK Logged in. quit +OK Logging out. Connection closed by foreign host.

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha4.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha4.tar.gz.sig Note that there are significant changes in this release from alpha3 and I haven't tested everything extensively. Be careful. The next release will hopefully be v1.2.beta1 with a feature freeze. Most importantly shared mailboxes and IMAP ACLs are finally

Hello list, I am not quite sure whether this is a questions for Dovecot or Postfix. I have set up, virtual hosting for one domain (for test purposes) using a passwd-file as passdb and a static userdb (see dovecot -n at the end) along with Postfix in a manner described in [1], i.e. a non-Postfix mail store. Other than that I also do hosting for the canonical domain which is for users with a