similar to: Panic in dovecot 1.2.beta1

Since upgrading from Dovecot 2.0.beta4 + patches http://hg.dovecot.org/dovecot-2.0/rev/96496e1d3d12 and http://hg.dovecot.org/dovecot-2.0/rev/aefa279e2c70 to Dovecot 2.0.beta 5, I have started to see the subject error from Dovecot for SASL authentications. It doesn't happen every time, but it happens more often than not. It doesn't seem to affect Postfix's acceptance of the message.

Just an FYI, I have been running 2.2.beta1 for a few days now with no problems, but I'm not using any of the new features ;) -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

The initial problem I was seeing after upgrade from 2.0beta5 to 2.0beta6 was error messages from my Android phone K9 client that dovecot was reporting -1 messages in various mailboxes. These mailboxes do have the special "Mail System Internal Data" message in them. In trying to get more information for debugging, I tried toenable rawlog using the same configuration I used successfully

I have just upgraded from 1.2.beta1 to 1.2.beta2. My configuration is: [root at sbh16 ~]# dovecot -n # 1.2.beta2: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/postfix/sbh16-cert.pem ssl_key_file: /etc/postfix/sbh16-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default):

Since upgrading from dovecot-2.1.rc1 to dovecot-2.1.rc3, some clients are showing a .subscriptions file in the user's mbox path as a folder. Some clients such as T'bird on Mac OS X create this file listing subscribed mbox files. Other clients such as T'bird on Windows XP show this file as a folder in the folder list even though it cannot be accessed as a folder (dovecot returns CANNOT

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

I just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic:

The log messages are attached. The core dump is at <https://www.dropbox.com/s/9i80ms7xkyxoqj7/core.26450?dl=0> The server is $ uname -a Linux sbh16.songbird.com 2.6.18-8.1.14.el5 #1 SMP Thu Sep 27 18:58:54 EDT 2007 i686 i686 i386 GNU/Linux -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Background. A while back I upgraded my phone to one currently using Android 4.1.2 and K9 mail 4.409. This phone/MUA combination seems at times to go crazy making IMAP connections. At first, I had mail_max_userip_connections = 30 (my largest imap account has 19 folders). The issue I had at that time was multiple errors like Oct 14 17:45:16 sbh16 dovecot: imap-login: Maximum number of connections

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

Saw the following in the log after shutting down my client. Feb 22 20:44:47 sbh16 dovecot: imap(mark): Disconnected: Logged out bytes=1755/9765 Feb 22 20:44:47 sbh16 dovecot: imap(mark): Panic: file istream-raw-mbox.c: line503 (istream_raw_mbox_get_start_offset): assertion failed: (rstream->seeked) Feb 22 20:44:47 sbh16 dovecot: imap(mark): Raw backtrace:

It appears that there is some version of the Dovecot LDA that is sending an RFC 3798 MDN rather than an RFC 3464 DSN to report non-delivery to a user who is over quota. See <https://bugs.launchpad.net/mailman/+bug/693134> for a discussion of this and <https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/Automatically%20rejected%20mail.msg> for the actual MDN

I have recently upgraded from Dovecot 1.2.10 to 2.0.beta3. I have Postfix 2.3.3 and use Dovecot to provide SASL auth for Postfix. # dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

I just looked over my logs and noticed the following error: Mar 9 19:07:34 apple dovecot: Panic: POP3(april): Trying to allocate 0 bytes Mar 9 19:07:34 apple dovecot: POP3(april): Raw backtrace: pop3 [0x492952] -> pop3 [0x4929d3] -> pop3 [0x4920e6] -> pop3 [0x49cb8d] -> pop3(client_create+0x452) [0x41aef2] -> pop3(main+0x393) [0x41c9e3] ->

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

The February archive indexes of this list haven't been updating since Feb 8. The text file at <http://dovecot.org/pipermail/dovecot/2013-February.txt> appears to be up to date with all posts, but the index pages at <http://dovecot.org/pipermail/dovecot/2013-February/thread.html>, <http://dovecot.org/pipermail/dovecot/2013-February/subject.html>,

I don't know if this is significant or not, but it is at least unusual here. First we see this: > Oct 9 10:10:03 sbh16 dovecot: imap(mark): Error: Sync failed for mbox file /var/spool/mail/mark: seq=393 uid=201517 uid_broken=0 originally needed 0 bytes, now needs 66 bytes which has apparently added 66 bytes to UID 201517 Then, later we see: > Oct 9 11:26:19 sbh16 dovecot:

I have been running dovecot 1.2.10 without problems. I am trying to install 2.0.beta3. I have I think translated all my configuration customizations correctly, but I have problems. I can start dovecot, but I can't login, at least not with SSL. Here's my dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms

some senders on this maillist use a version of thunderbird that adds more then one references header and this imho breaks threading :( -- xpoint