similar to: Why dovecot does not want to read my acl file?

Hi, I have the following problem: My structure is stored in LDAP that way: dc=example,dc=com + ou=groups | + cn=Account Operators | + ... + ou=machines | + uid=workstation1$ | + uid=workstation2$ | + ... + ou=users + ou=int | + uid=user1 | + uid=user2 | + ... + ou=ext + uid=user3 + uid=user4 + ... ... Only internal

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:

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

Hi Johanners Berg, I put the antispam plugin to work (some days ago) and now my imap daemon dies with segfault. I don't have nothing (wrong) in logs, just a lot of segfaults... Dec 10 15:37:21 curie kernel: printk: 22 messages suppressed. Dec 10 15:37:21 curie kernel: imap[4774]: segfault at 8 rip 2afe7fe7d7ff rsp 7fff2b9bdab0 error 6 Dec 10 15:37:21 curie kernel: imap[4779]: segfault at 8

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, always when my server is on high load I saw this errors on logs: curie:~# uptime 10:22:38 up 19 days, 19:19, 2 users, load average: 207.01, 169.27, 94.41 Sep 15 17:00:26 curie dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x00000000009f8560 *** Sep 15 17:00:26 curie dovecot: child 24012 (login) killed with signal 6 Sep 15 18:48:36 curie dovecot:

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

Hi All, Relatively new to Dovecot - converting from courier-imap. So far, I've got it working with virtual users (postfixadmin tables), and it seems to be working. I'm trying to get sieve working. It's not, so I tried turning up the logging, and putting it into a separate log file to get it out of the syslog for now. I can get the main dovecot to log, but I cannot get any log

Hello I got this error yesterday dovecot: Feb 11 16:07:27 Error: IMAP(dumontj): FETCH for mailbox Sent UID 7139 got too little data: 11112 vs 11160 dovecot: Feb 11 16:07:27 Error: IMAP(dumontj): Corrupted index cache file /user/dumontj/.imap/Sent/dovecot.index.cache: Broken virtual size for mail UID 7139 Does remove the cache will cure the problem ? Thanks

Hi. Just got this error (1.1.rc4), is it something to worry about? Corrupted index cache file /.../Maildir/.Sent/dovecot.index.cache: used_file_size too large This is a shared mailbox with concurrent access. In general, can that usage pattern mess up the index? I am guessing "no", which is why I worry slightly about the warning. Cheers, Anders.

I've been simultaneously learning about dovecot and experimenting with the 1.2.alpha4. To start I built an rpm under CentOS 5.2 from: dovecot-1.2.alpha4.tar.gz dovecot-1.2-managesieve-0.11.2.tar.gz dovecot-1.2.alpha4-managesieve-0.11.2.diff.gz dovecot-1.2.alpha4.tar.gz dovecot-1.2-sieve-0.1.2.tar.gz and then setup with mysql to use virtual users. Mail-wise, it all works. :)

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

Can dovecot-1.1 deliver work with static userdb? I'm currently running dovecot-1.0.12 and postfix-2.4.6, with virtual users' maildirs all owned by vmail and mail_location = maildir:/var/mail/%Lu. The following definition of the dovecot transport in postfix/master.conf works fine with dovecot-1.0: dovecot unix - n n - 1 pipe flags=DRh

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 successfully configured dovecot using virtual users (and LDAP/AD). deliver is the LDA and verifies if the user exists (as recommended in the WIKI). However, the howtos in the Wiki say *nothing* about the case that the recipients should be verified *before* receiving the messages (prevent backscatter, ...). All configurations in the dovecot-Wiki (postfix and exim) just accept the mails

Hello again. I am trying to use a master user. The login works. However, a LIST command gives me only the INBOX. Is this to be expected? When logging in normally, I do get the full list of folders. (using Dovecot 1.1 rc3.) Anders.

I had recently upgraded from Dovecot 1.0.14 to 1.1.0, and then to 1.1.1. Ever since the upgrade to 1.1.0, I noticed that "plus addressing" has failed. In case I'm using a foreign phrase, this is the concept of sending an e-mail to "user+spam at domain.com", and having dovecot (dovecot LDA, specifically), deliver this to the "spam" submailbox to

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not