similar to: Newbie: unable to access mailbox more than once

hello dovecot at dovecot.org: I want to see the contents of dovecot.index.cache . Is there any command can make it become visible character displayed ? the command idxview can displayed doveoct.index and logview can dispalyed dovecot.index.log but it seems no command to displays dovecot.index.cache for us. thanks amandy

Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) So the binaries are: 1) These probably belong to bin/ or sbin/ or both: - authtest - dovecotpw - doveadm 2) Binaries that you might want to call from mail_executable setting: - rawlog - gdbhelper 3) Index file dumping

http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz.sig Still a bit more fixes. My coding TODO list is again empty. Unless something special happens in the next few weeks, I'll still make rc29 with the documentation included and v1.0 will be released April 13. * deliver + userdb static: Verify the user's existence from passdb,

http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz.sig Still a bit more fixes. My coding TODO list is again empty. Unless something special happens in the next few weeks, I'll still make rc29 with the documentation included and v1.0 will be released April 13. * deliver + userdb static: Verify the user's existence from passdb,

Playing with the new idxview I got this error running against my INBOX dovecot.index.cache file. What exactly does it mean? Full output: # /usr/libexec/dovecot/idxview dovecot.index.cache -- INDEX: dovecot.index.cache version = 1.8 base header size = 0 header size = 1170103198 record size = 1170103283 compat flags = 7 index id = 0 flags = 26512 uid validity = 0 next uid = 2460778624 messages

"M. Balridge" <dovecot at r.paypc.com> writes: > I assume it's a rarely seen issue because few Dovecot users compile the > software in caves on computers powered by horse-pulled generator > wheels. I resemble that remark. >> Warning: Transaction log file /home/luser/mail/.imap/INBOX/dovecot.index.log >> was locked for 95 seconds (rotating while syncing)

A mail user reported that he filled up his INBOX (despite reminders he was approaching his filesystem quota), and furthermore, he could not fix the situation because he couldn't expunge message he marked for deletion. The dovecot logs revealed the cause dovecot: imap(user): Error: open(/var/mail/user.lock) failed: Disc quota exceeded This created an impasse where a user cannot free

mail_extra_groups=mail setting is often used insecurely to give Dovecot access to create dotlocks to /var/mail directory. If you don't use mboxes in /var/mail, make sure this setting is cleared. If you do use /var/mail mboxes and Dovecot gives permission errors without it, do one of the following (in the preferred order): a) Upgrade to v1.0.11 and use the new mail_privileged_group setting

mail_extra_groups=mail setting is often used insecurely to give Dovecot access to create dotlocks to /var/mail directory. If you don't use mboxes in /var/mail, make sure this setting is cleared. If you do use /var/mail mboxes and Dovecot gives permission errors without it, do one of the following (in the preferred order): a) Upgrade to v1.0.11 and use the new mail_privileged_group setting

Greetings to all. It's my first post to the list. We just completed a migration from qpopper to dovecot for our IMAP and POP3 services. We have a rather large mail environment (we are the biggest provider in Greece). So, here are the details: - Keep getting errors like these in our production environment Jul 22 00:18:21 pop01 dovecot: master: Error: service(pop3): child 4078 killed with

I've tried turning on mbox_very_dirty_syncs for myself (and a few other brave souls running 1.0-alpha3 rather than 1.0-stable) again to see what perfomance gain it gives (see thread http://www.dovecot.org/list/dovecot/2005-July/007956.html). Now we aren't running UW-IMAP at all, how safe is mbox_very_dirty_syncs assuming the only other process writing to mailboxes is our MTA (exim) which

http://dovecot.org/releases/dovecot-1.0.rc32.tar.gz http://dovecot.org/releases/dovecot-1.0.rc32.tar.gz.sig Pretty late for changes if v1.0 is supposed to come out tomorrow, but I can't really leave these LDAP bugs unfixed. They shouldn't anyway break anything, so here's one more day for you people to find out about any bugs. One thing that I'm a bit concerned about is the

Hi All! Just noticed a strange behavior of the FS quota plugin on delivery stage. We use group FS quotas via NFS. And quota-tool says: --- Disk quotas for group #5751796 (gid 5751796): Filesystem blocks quota limit grace nfse:/export 1276 10240 10240 --- I run: --- cat ./test.eml | /usr/local/libexec/dovecot/deliver -e -n -d xxxx at xxxxx.xxxx --- and get: --- Quota

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've set up a namespace to share some mailboxes. When I try to select them, I get an internal error: Client-server chat: * OK Dovecot ready. 1 login dvtest2 x 1 OK Logged in. 2 list "" * * LIST (\HasNoChildren) "." "Trash" * LIST (\HasChildren) "." "test" * LIST (\HasNoChildren)

Im still finding a number of control directories that have the wrong permission: Jun 26 00:02:34 userimap13.xs4all.nl dovecot: IMAP(xxx): file_dotlock_create(/var/spool/mail/dovecot-control/g/gl/xxx/INBOX/.Apple Mail To Do/dovecot-uidlist) failed: Permission denied userimap1# ls -al "/var/spool/mail/dovecot-control/g/gl/xxx/INBOX/.Apple Mail To Do" total 8 drw------- 2 xxx user 4096

Hello everyone, I am testing Dovecot 1.1.3 at the moment to see if I can migrate from UW-Imap(mbox) to Dovecot(maildir). Because I dont' want to influence the production server I installed Dovecot on an ununsed computer with some dummy-testusers using ssl and maildir. Installation was without any problems and everything works fine with one exception: I cannot download some attachments.

Hi, I just found these useful tools :) they were installed in libexec dir :) -- Xueron Nee http://www.xueron.com

Hi, currently I have one new user with a problem. When she logs in to dovecot with pop3 from her apple mail, dovecot tells problems with the +w permission. Error: open(/var/mail/******) failed: Permission denied (euid=3462(******) egid=548(dozenten) missing +w perm: /var/mail) /var/mail is rw by root.mail I cant see why just this particular user has that problem/gets that messages. AFAIK no

I am wondering if I really need to use dovecot quota functions or not. Assume for the moment, that, each system user has a quota defined using Linux quotas, and that the Maildir is within their quota limited directory. So, any mail (or files created by the user etc) that would exceed the quota obviously can't be created.? In such an environment, is there any advantage to implementing the same

I installed dovecot 1.1 on our system yesterday, and found a few bugs so far. Here is the list: BUG #1: can't access some folders Details: a select "RSS.A List Apart" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $$$INDEXED###) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $$$INDEXED### \*)] Flags permitted. * 52 EXISTS * 0 RECENT * OK [UNSEEN 50] First unseen.