similar to: when the user has no home directory

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

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

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.

I tried Dovecot 1.2.beta1 yesterday. I had been using 1.1.11. I started getting "Panic: POP3(xxx): Trying to allocate 0 bytes" There are two kinds of pop3 users. In the attached log.txt file, user u1 is using a pop3 MUA. For users u2, u3, u4 and u5 fetchmail is coming through an ssh tunnel and retrieving their mail. u1 is able to interact normally with dovecot, but the fetchmail users

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:

I am testing the version on FreeBSD 7.3-PRELEASE (I doubt it's the issue) and I am having a problem with pop3. Here is what I see in the log when I attempt to connect to port 110: Feb 22 18:15:03 master: Warning: SIGHUP received - reloading configuration Feb 22 18:15:08 pop3-login: Panic: file login-settings.c: line 216 (login_settings_read): assertion failed: (input.roots[count] == NULL) Feb

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

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

hi All, I have a problem, which makes me headache. I can't find out, what is the problem. I have a mail szerver, which works just fine as expected, TB move messages to trash folder after I delete it, and they are moved. I have an other server. If I delete a message, it doesn't move to the Trash folder. As deleted_to_trash plugin is installed, if I only mark messages as deleted, they

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.

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:

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:

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 had a user telling me that they can't login to the Postfix email server via Webmail (RoundCube) and I decided to see if I could locate this issue in the logs and understand if the user was simply using a wrong password credential and or something more serious. More than likely the person is just using a wrong password but in search of this on my logs, I don't understand why Dovecot

Not sure what to call this - I'm actually working out the details as I type this. I want to have a valid username/password for an account for sending purposes - but when receiving this is an alias that broadcasts to several users. Example: accountspayable at mydomain.com - is an alias for jane at mydomain.com, june at mydomain.com, and john at mydomain.com. However - any mails sent

Hello, Dovecot is logging authentication failures this way: ------ Jul 12 18:07:19 vps0 dovecot: imap-login: Disconnected (auth failed, 22 attempts in 172 secs): user=<info>, method=PLAIN, rip=82.95.148.152, lip=1.2.3.4, TLS, session=<QylMqlLhVwBSX5SY> ------ Fail2ban is trying to catch them with this regex: ------ failregex = .*(?:pop3-login|imap-login):.*(?:Authentication

I'm seeing strings of failed POP3 login attempts with obvious bogus usernames coming from different IP addresses. Today's originated from 216.31.146.19 (which resolves to neovisionlabs.com). This looks like a botnet attack. I got a similar probe a couple days ago. Is anyone else seeing these? The attack involves trying about 20 different names, about 3-4 seconds apart. Here's a

Hello, What does this information mean and how is it relevant? I cannot find documentation other than a brief description in dovecot.conf: %t - number of TOP commands %p - number of bytes sent to client as a result of TOP command %r - number of RETR commands %b - number of bytes sent to client as a result of RETR command Thanks in advance, Cliff