similar to: Debugging sieve-options

Last night Dovecot stopped, and the last message in the log was: Fatal: write() failed to info log: Interrupted system call Would you please advise? *** # dovecot -n # 1.1.6: /usr/local/etc/dovecot.conf Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead # OS: FreeBSD 6.4-PRERELEASE i386 log_path:

Hello! Always reproducible pine vs dovecot-imap-mbox.gz scene has weird errors. - Initial message is OK: [Folder "SAVE.gz" opened with 211 messages READONLY] - Some mails at the end are listed correctly, others are listed with empty sender/size/subject (just numbering). - All mails have no bodies. Full header command produces total blank screen. Even before any error message.

I have just upgraded from 1.0.7 to 1.0.13. I read the comments in the example .conf file and it seemed what I needed to enable dotlock access to mailboxes in /var/spool/mail (writable by 'mail' group) was "mail_privileged_group = mail" so I removed the "mail_extra_groups = mail" that I had in 1.0.7 and added "mail_privileged_group = mail", but I got errors

"Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead" I use the following: mail_extra_groups = mail nogroup Because I have the real and virtual accounts. What's the correct way to replace the above line? It seems that mail_privileged_group only accepts one group, but I need two. Any

Greetings, I recently upgraded our server from Dovecot 1.0.14 to 1.1.1. I am building using the FreeBSD ports system, so nothing is custom aside from the flags set there. dovecot fell down a few days after the update with: pid 1823 (imap), uid 1000: exited on signal 11 the mail log shows: Jul 4 14:36:07 hostname dovecot: IMAP(username): Corrupted index cache file

http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz.sig * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. - mbox: Dropped some of the physical size

http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.11.tar.gz.sig * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. - mbox: Dropped some of the physical size

Hello, I am trying to configure my dovecot folowing this guide: http://www.w3style.co.uk/virtual-domains-with-exim-and-dovecot I append the output of dovecot -n below. I created /etc/vmail/my-domain.de/user containing: test-user:{PLAIN}test:1002:100::/home/test-user:: No I try to login: telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK This

Howdy, Today I installed the new version of Apple OSX 10.6. Besides that it deleted the dovecot user, things went quite smooth. As far as I can tell it is running as it used to. However, I can't login to my account. It used to work fine with PAM taking the username and password from my osx installation. Now it doesn't allow me to login anymore. I have read on a website that apple

Hi Guys, I've been trying to get this to work for 3 days now, but no luck. I have Dovecot set with an Active Directory back-end. Everything is working properly but I can't get user specific quotas.I tried with both 1.0.13 and 1.0-rc7. All users have the same quota which is set in dovecot.conf dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf Warning: mail_extra_groups setting was often

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz.sig Changes since rc1: * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. + Expire plugin

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz.sig Changes since rc1: * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. + Expire plugin

Getting the followng error when managesieve is enabled. Any other post I've read says this problem is because the service hasn't restarted after upgrade. I've restarted dovecot & postfix many times, reboot machine too. Still get the error. Racking my brains on this!! May 7 13:21:19 drizzle dovecot: dovecot: Created login processes successfully, unstalling May 7 13:21:20 drizzle

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

Hi, i have a big problem with dovecot... PAM auth problem i guess, but don't know how to sort it out... Down the log and the dovecot.conf. Please soemone can tell me what's broken there? Thanks a lot ************************* HERE log ************************* Jun 9 14:49:46 vps dovecot: pop3-login: Can't connect to auth server at default: Resource temporarily unavailable Jun 9

On Thu, Jul 31, 2008 at 5:21 PM, Kacper Wysocki <kacperw at online.no> wrote: > I'm using dovecot 1.0.13 as the IMAPS frontend for a vpopmail/qmail > virtual domain setup. Dovecot is set up as follows: > passdb vpopmail{ > } > userdb vpopmail{ > } > > I've added a domain alias for the main domain with vaddaliasdomain and > email to post at aliasdomain is

Hi, I do hope this hasn't been covered. I googled and looked in the archives but didn't see anything related, so hopefully I am not covering old ground. I recently upgraded from 1.0.10 to 1.1rc5. I am seeing this error from clients: May 25 11:01:54 finity dovecot: Panic: IMAP(xxx at here.org): file mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node): assertion failed:

Hi folks, I'm using dovecot 1.0.13 as the IMAPS frontend for a vpopmail/qmail virtual domain setup. Dovecot is set up as follows: passdb vpopmail{ } userdb vpopmail{ } I've added a domain alias for the main domain with vaddaliasdomain and email to post at aliasdomain is delivered to post at maindomain and can be checked with pop. However, when I try to check IMAP through the account post

This is with respect to an error that I am facing in dovecot. The error is that is seen in logs is "Feb 23 00:04:46 mailblade1 dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist: Duplicate file entry at line 7: 1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 -> 97805)" This error is seen for multiple users. Once this error occurs for a user, the