similar to: Quotas once again

Is there anything that can be done so that when users IMAP to their inbox and have reached their filesystem quota, that they can still DELETE their mail? They can login, but when they go to delete/expunge this is the error I get in syslog. I have tried mail_read_mmaped to yes and no, and same result. Mar 25 14:54:27 penguin1 imap(bob): file_set_size() failed with index data file

Hi, i have a problem with dovecot and quotas, when a user has over-quota he can't access the mail account to download mails and solve the quota problem. I'm using debian sarge (stable) and quota v1 (vfsold), i have installed dovecot in debian way apt-get install dovecot dovecot-common dovecot-pop3d users only can access via pop3 to their mails. This is the error i get when i try to access

Hi, Thank you for pointing me about -xc99 flag, I have compiled and installed dovecot inplace of version 1.0.5 without any special actions on the upgrade. And after starting it immediately got in it's log file messages like: --- dovecot: Oct 16 23:10:18 Error: IMAP(seriv): file_set_size() failed with index cache file /var/spool/imap/seriv/.imap/.git-altlinux-ru/dovecot.index.cache: Invalid

Hi, on a clustered Dovecot server installation that was recently moved from a shared GPFS filesystem to GFS2, occasional corruptions in the users' INBOXes started appearing, where a new incoming message would be appended directly after a block of NUL bytes, and be scanned by dovecot as being glued to the preceding message. I traced this to the file extension operation performed in

FreeBSD 6.1 STABLE Postfix version 2.4-20060806 Dovecot v1.0.rc2 I have the following in the postfix main.cf file: mailbox_command = /usr/local/libexec/dovecot/deliver This is from the dovecot.conf file: default_mail_env = mbox:/var/mail/%u However, mail is never delivered with this configuration. This is an excerpt from the 'dovecot.log' file: deliver(gerard): Error:

Hi, compiled perfectly, so the patch of course work ;), but seems that I had the conf a bit broken, because he doesn't read the new messages in /var/mail/user, does the line: #default_mail_env = mbox:~/Mail:INBOX=/var/mail/username look good?, I also tryed with %h instead of username, the rest of the conf is pretty standard, I can create folders and so on. Regards Alvaro

I recently had a system crash and my inbox became inaccessible via IMAP. ls -ld /var/spool/mail drwxrwxr-x 2 root mail 4096 Sep 1 07:54 /var/spool/mail ls -l /var/spool/mail/ignacio -rw-rw---- 1 ignacio mail 7222021 Sep 1 07:54 /var/spool/mail/ignacio /usr/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED

Hello I am migrate FC1 to FC2, in FC1 i use ipop3d, but in the migration to FC2 this programa is obsolete, i decide migrate to dovecot, but i have problems with the old mail i have the mail stored into /var/spool/mail/USER and this error appears with examine the mail with Oulook Express: Jun 6 23:24:10 dakota pop3(dakota): open(/var/spool/mail/dakota.lock) failed: Permission denied Jun 6

Oct 5 22:51:59 ns6 dovecot: POP3(aewhale): file_lock_dotlock() failed with mbox file /var/spool/mail/aewhale: Permission denied Any suggestions? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ------------------------------------------------------------------------ ABS Computer Technology, Inc. <http://www.ABS-CompTech.com> - Email,

Jun 8 23:14:09 dakota pop3(dakota): open(/var/spool/mail/dakota.lock) failed: P ermission denied Jun 8 23:14:09 dakota pop3(dakota): file_lock_dotlock() failed with mbox file / var/spool/mail/dakota: Permission denied Jun 8 23:14:09 dakota pop3(dakota): open(/var/spool/mail/dakota.lock) failed: P ermission denied Jun 8 23:14:09 dakota pop3(dakota): file_lock_dotlock() failed with mbox file /

Hi, Can sameone explain me why my logs are full of such errors: Jul 11 12:07:32 mxhost deliver(user1): pwrite() failed: File too large Jul 11 12:07:32 mxhost deliver(user1): file_set_size() failed with index cache file /mail/user1/Maildir/.parser/dovecot.index.cache: File too large mxhost# ls -lh /mail/user1/Maildir/.parser/dovecot.index.cache -rw------- 1 user1 emails 64M Jul 11 10:01

Hi, AIX's implementation of posix_fallocate is a little bit, let me say, peculiar. Attached is a patch to "fix" (=work around) this. Without you'll see this in the logs: Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): posix_fallocate() failed: File exists Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): file_set_size() failed with mbox file

Hi I am trying to install 1.0 stable from source on a test server running 0.99 on FC3. i did basic ./configure etc and get this result Jul 13 17:24:26 proteus4 dovecot: Dovecot v1.0-stable starting up Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): open(/var/spool/mail/.temp.proteus4.4485.e3eec7b26a559bac) failed: Permission denied Jul 13 17:24:35 proteus4 dovecot: POP3(obantec):

dovecot: Oct 05 16:03:07 Info: imap-login: Login: user=<kartagis>, method=plain, rip=212.98.201.1, lip=192.168.1.2 dovecot: Oct 05 16:03:07 Error: IMAP(kartagis): open(/var/mail/.temp.kunduz.org.14095.855b9feb950c2c78) failed: Permission denied dovecot: Oct 05 16:03:07 Error: IMAP(kartagis): file_lock_dotlock() failed with mbox file /var/mail/kartagis: Permission denied Hi, I get these

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the

well, now that I have moved to dovecot, I'm not getting any spam... in fact, I'm not getting e-mail at all. default_mail_env =mbox:~/IMap2/:INBOX=/var/spool/mail/%u when I first tried to access my inbox, I was told I had permission problems: Aug 14 17:47:22 harvee imap(esj): open(/var/spool/mail/esj.lock) failed: Permission denied Aug 14 17:47:22 harvee imap(esj): file_lock_dotlock()

Hi all: I have a problem running my dovecot server. I get the following error message when trying to get mail from my account with INBOX in /var/spool/mail/tanim (username tanim). Nov 22 19:23:00 phobos imap(tanim): file_lock_dotlock() failed with mbox file /var/spool/mail/tanim: Permission denied What permissions should I set for the mailbox? I am running dovecot-0.99.11-1.1. Tanim --

Hello, I'm trying to set up dovecot as the delivery agent for postfix. I configured postfix with: mailbox_command = = /usr/local/libexec/dovecot/deliver In the logs I see the following error: Sep 20 17:19:26 zalm deliver: open(/var/mail/.temp.zalm.8045.65c09c28953ea20c) failed: Permission denied Sep 20 17:19:26 zalm deliver: file_lock_dotlock() failed with mbox file