similar to: Apple Mail for 10.4/Shadow/SSL -> Problem.

I'm testing 1.0 beta3 on our mail server, and finding that Apple Mail seems unable to connect to it. I'm running the 1.0b3 on port 997 so we can test it in parallel to 0.91 to compare performance (so far, it's hella faster). I've ensured that the users testing are _not_ connecting in any way to the 0.91 version running on port 993. From the OS X client side (10.4.5 + latest

Hello List! I?ve following problem after updating dovecot... Error: (Empty password returned without nopassword) Jan 21 15:56:15 test-mi dovecot: auth(default): new auth connection: pid=83362 Jan 21 15:56:15 test-mi dovecot: auth(default): client in: AUTH 7 PLAIN service=imap lip=192.168.0.32 rip=192.168.0.86 lport=143 rport=2905 resp=AHRrdWV2NUBnb25lby5jb98AdGVzdHVzZXI1

Hi, I get these errors with dovecot 1.1.13 in my logs: dovecot: Mar 27 12:00:34 Error: auth-worker(default): *** glibc detected *** dovecot-auth: double free or corruption (!prev): 0x00002b30d5a7dd90 *** dovecot: Mar 27 12:00:34 Error: auth(default): worker-server(jan,147.251.48.141): Aborted: Worker process died unexpectedly dovecot: Mar 27 12:00:34 Error: child 21838 (auth-worker) killed with

Hello, I'm trying to configure the dovecot-antispam plugin. Now I've run into a problem: whenever I try to move/copy a message in/from the spam mailbox, Thunderbird (and also Sylpheed, haven't tried anything else) says: The current command did not succeed. The mail server responded: Failed to read mail beginning. and in the logs I get: dovecot: Aug 07 10:41:23 Error:

Hi, We are using dovecot 1.1.11 on Solaris 10u6. Under load, we are experiencing the following errors: Jun 4 18:30:59 ug1s02-zone1 dovecot: [ID 107833 mail.error] auth(default): ldap(0202934816 at ug.smilecoms.com,10.31.3.13): ldap_search() failed (filter (uid=0202934816 at ug.smilecoms.com)): Server is busy We are authenticating against sun directory server yet see no errors in the directory

With following configuration: userdb static { args = uid=10000 gid=10000 home=/home/vmail/domain.tld/%u/./ mail=maildir:~/maildirs } and accompanying passdb passwd-file consisting of only user and password, for example test:{PLAIN}test: dovecot will access home=/home/vmail/domain.tld/test/home/vmail/domain.tld/test/maildirs instead of home=/home/vmail/domain.tld/test/maildirs dovecot

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo at example.com with a password can login with fOO at example.com and fOo at example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had

I'm having the most frustrating issue, and I'm at a loss for what is happening. I'm not even sure it is with Dovecot, but that's why I'm posting this here... if it isn't a dovecot issue, maybe someone can get me headed in the right direction? I've posted relevant dovecot and config info at the bottom of this post. Here's the scenario: We recently migrated our

Recently I've made the post about "double homedir" problem, but I couldn't recreate it later. Here're the exact steps to make it happen (configuration is at the bottom): 1) set configuration as below with passwd-files 2) clean testms dir (not necessary though) 3) reload dovecot (HUP is enough) 4) access the server with any client using testms user (make sure no other

I've followed the instructions ( http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL) to setup Dovecot with MySql and Postfix but cannot receive from (or send mail to) other domains. FYI: email messages are supposed to be stored under /var/mail/mozmonkey.com/<user>/ Directory Permissions: drwxr-xr-x 5 vmail mail 4096 May 10 12:57 mozmonkey.com OS: Linux, Fedora 4 Dovecot

I'm not sure if it's even intended to work in this particular case, but there's a problem when chroot is explicitely defined and rawlogging is used. Rawlog respects chroot point, without being actually chrooted. Consider configurtion as below, with two cases (dovecot.rawlog dir is of course created earlier, with appropriate uid/gid). 1) dovecot.userdb:

Read what I could find on possible upgrade issues and saw only one that might be a problem. I don't think it will but figured it was worth checking. Anything jump out at the more experienced users? dovecot -n (edited to protect the guilty. ie. me) attached. # 1.1.11: /etc/dovecot.conf # OS: Linux 2.6.22.19-vs2.3.0.34.1 i686 CentOS release 5.2 (Final) log_path:

I have Dovecot setup with Postfix and can't seem to connect to to the SMTP server (port 25) unless I'm on the server itself (telnet localhost 25). For example, I cannot use my mail client, Thunderbird, to send mail from my laptop -- it cannot even connect to the server. I checked the logs and nothing shows up for the attempted connection. Dovecot version: 1.0.0 Postfix version: 2.3.6

Originally I've thought that this is related to INBOX field, but it turned out it happens only when you specify mbox. Consider following passwd-file: testms::10000:10000:imap,,,:/home/vmail/ppgk.com.pl/testms/./::userdb_mail=mbox:~/Mail:INBOX=/home/vmail/ppgk.com.pl/%u/inbox or following line from userdb static: args = uid=10000 gid=10000 home=/home/vmail/ppgk.com.pl/%u/./

Hello all! dovecot 1.1.6 Use lazy_expunge plugin call core on connect. Core: bt full #0 lazy_expunge_mail_expunge (_mail=0x2ac06e9b89e8) at lazy-expunge-plugin.c:103 lt = (struct lazy_expunge_transaction *) 0x2ac06e9b86e0 deststorage = <value optimized out> #1 0x000000000041cefc in imap_expunge (box=0x2ac06e988de8, next_search_arg=0x0) at imap-expunge.c:31 ctx =

trying to login squirrelmail using dovecot-1.1.17 on a qmail-server with vpopmail setup has also running your: courier-dovecot-migrate.pl --recursive --convert --overwrite here are the output from dovecot-log: Info: imap-login: Disconnected (no auth attempts): rip=192.168.1.220, lip=192.168.1.220, TLS handshaking: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown

Hi all, I recently upgraded from courier to dovecot 1.1.12 on a Solaris 9 system with about 100 users. We have been testing dovecot for sometime in a mixed Linux/Solaris environment and are aware of the index endianess issue with multiple archs. To solve this, we run with INDEX=MEMORY (as seen in the docs) so that only Linux clients have anything to do with the indexes. We generally have

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if

Hi, I am using dovecot with postfix for authentication. Everything (TLS/SSL, authentication) is working fine, except that when I set: disable_plaintext_auth = yes I still can authenticate with plain text on a no TLS/SSL session: 20 mail2.cs.ait.ac.th ESMTP Postfix (2.6.2) EHLO [192.41.170.57] 250-mail2.cs.ait.ac.th 250-PIPELINING 250-SIZE 10240000 250-VRFY

Hi folks. We're moving users from rc24 and 27 to 1.0.0. On four mailboxes so far we've seen these errors after the move (quick and dirty anonymizing follows): Apr 23 13:22:41 server.umn.edu dovecot: [ID 107833 local6.info] imap-login: Login: user=<USER>, pid=<9046>, method=PLAIN, rip=***.***.***.***, lip=***.***.***.***, TLS Apr 23 13:22:41 server.umn.edu dovecot: [ID