- dovecot - dovecot.org

[Dovecot] New SSL certificate problem
by Stewart Dean 05 Jan '09

05 Jan '09

Our DC has been using a Verisign certificate. Over the past year, we've been using a Digicert Wildcard Plus certificate for almost all of our machines, and I wanted to switched over our DC mailserver. I used the following command to generate the CSR and key: openssl req -new -newkey rsa:1024 -nodes -out star_bard_edu.csr -keyout star_bard_edu.key -subj "/C=US/ST=NY/L=ourtown/O=Bard College IT/OU=Bard College /CN=*.bard.edu" The resultant CSR verified and I submitted it to digicert and got back our cert, plus their intermediate and Trusted root certs. I killed the root instance of dovecot and waited for all the children to die I put together the intermediate cert (first) and our cert (second) into /usr/ssl/certs/dovecot.pem I put the key star_bard_edu.key in /var/ssl/private/dovecot.pem I restarted dovecot, but the imap login instances didn't appear, so I shifted back to the original combined cert file and key, restarted dovecot and it came up OK I check the syslog and saw these error messages: Jan 5 10:19:49 mercury mail:err|error dovecot: imap-login: Can't load private k ey file /var/ssl/private/dovecot.pem: error:0B080074:x509 certificate routines:X 509_check_private_key:key values mismatch Jan 5 10:19:49 mercury mail:err|error last message repeated 8 times Jan 5 10:19:49 mercury mail:err|error dovecot: child 4051108 (login) returned e rror 89 Jan 5 10:19:49 mercury mail:err|error dovecot: child 4231382 (login) returned e rror 89 I checked my key and it has the same time stamp as my CSR, so I didn't somehow get the wrong key. Both the old and new key are 600; if the old one works based on perms, the new one should too. Would some kind soul tell me what I'm missing? Or is there a problem using wild card certificate with DC? Is there an openssl command to verify the key. Or is it that the key is unencrypted? -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2

[Dovecot] login fails when username has apostrophe
by Karl Latiss 05 Jan '09

05 Jan '09

Hi I've added the apostrophe character to auth_username_chars however authentication still fails. I'm using LDAP with the following details: dovecot version 1.1.7 openldap client library 2.4.11 With auth_verbose = yes and auth_debug = yes set I see the following in the logs. Note the initial escaped apostrophe and the subsequent escaped escape in the filter! ----- start log ----- Jan 5 16:15:05 www-example1 dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=10.1.1.180 rip=10.3.96.60 lport=143 rport=48733 resp=<hidden> Jan 5 16:15:05 www-example1 dovecot: auth(default): ldap(julie.o \'reilly(a)example.com,10.3.96.60) pass search: base=dc=example, dc=com scope=subtree filter=(&(objectClass=qmailUser)(uid=julie.o\\'reilly)) field s=mail,userPassword Jan 5 16:15:05 www-example1 dovecot: auth(default): ldap(julie.o \'reilly(a)example.com,10.3.96.60) unknown user Jan 5 16:15:07 www-example1 dovecot: auth(default): client out: FAIL 1 user=julie.o\'reilly(a)example.com failed, 1 attempts): user=<julie.o\'reilly(a)example.com>, method=PLAIN, rip=10.3.96.60, lip=10.1.1.180 ----- end log ----- Users without apostrophes can authenticate successfully. If I've missed anything please let me know. # dovecot -n # 1.1.7: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.0-RELEASE amd64 ufs protocols: imap listen: 10.1.1.180 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes first_valid_uid: 999 first_valid_gid: 999 mail_privileged_group: mail mail_uid: 999 mail_gid: 999 mail_location: maildir:/usr/home/vmail/%Ld/%Ln imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@' username_format: %Lu passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail # grep -v '^ *$#.*$\?$' dovecot-ldap.conf uris = ldap://www-example1:389 dn = uid=xxxx,dc=example,dc=com dnpass = xxxx sasl_bind = no tls = no auth_bind = no ldap_version = 3 base = dc=example, dc=com user_attrs = homeDirectory=home=/usr/home/vmail/%L $,mailMessageStore=mail=maildir:/usr/home/vmail/%L$,=uid=999,=gid=999 user_filter = (&(objectClass=qmailUser)(uid=%n)) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=qmailUser)(uid=%n)) default_pass_scheme = PLAIN -- Karl Latiss <klatiss(a)nextdigital.com> Next Digital

1 0

[Dovecot] Permission to distribute Dovecot run file
by Rick Widmer 05 Jan '09

05 Jan '09

I am working on updating the Shupp toaster, http://shupp.org/toaster/ a set of files and instructions for installing qmail, vpopmail, qmailadmin and squirrelmail. Two of my most important goals are switching the imap program from courier to Dovecot, and closer integration with OpenSuSE. (Which I run my mail servers on.) To follow the style of the toaster I need a place where I can obtain the init.d script from http://wiki.dovecot.org/DovecotInit I would prefer to have permission to host the file myself so I don't have to worry about creating patches if there is ever a need for my run file to be different from yours. If that is not acceptable, would you please either provide a URL where I can download just the run file, or include it in the distribution. Thanks, Rick

3 2

[Dovecot] Warnings compiling on OpenBSD 4.4 i386
by Peter Lindgren 04 Jan '09

04 Jan '09

Hi, probably just nothing to worry about, but I get the following warnings when building 1.1.7 on OpenBSD 4.4 on i386. If I remove the --with-bsdauth config option, they all disappear. I won't use it anyway, but maybe there are others. $ dmesg OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008 deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Xeon(R) CPU 3040 @ 1.86GHz ("GenuineIntel" 686-class) 1.87 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR real mem = 1071788032 (1022MB) avail mem = 1027936256 (980MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd460, SMBIOS rev. 2.4 @ 0xdc010 (48 entries) bios0: vendor HP version "O10" date 07/20/2007 bios0: HP ProLiant ML110 G4 $ ./configure --without-pop3d --with-deliver --with-passwd --with-passwd-file --with-bsdauth --without-ldap --sysconfdir=/etc --localstatedir=/var --sharedstatedir=/var mail-index-map.c: In function `mail_index_map_ext_hdr_check': mail-index-map.c:171: warning: comparison between signed and unsigned mail-index-map.c: In function `mail_index_map_clone': mail-index-map.c:1112: warning: comparison between signed and unsigned mail-index-sync-update.c: In function `sync_header_update': mail-index-sync-update.c:419: warning: comparison between signed and unsigned mail-transaction-log-file.c: In function `log_file_track_mailbox_sync_offset_hdr': mail-transaction-log-file.c:682: warning: comparison between signed and unsigned passdb-bsdauth.c: In function `bsdauth_preinit': passdb-bsdauth.c:59: warning: implicit declaration of function `auth_cache_parse_key' passdb-bsdauth.c:60: warning: assignment makes pointer from integer without a cast /Peter -- Peter Lindgren http://www.norrskenkonsult.com

2 1

[Dovecot] convert non-standard mbox to maildir
by Maarten Bezemer 04 Jan '09

04 Jan '09

Hi, Let me start with wishing you all the best for this new year, and I hope we'll see a lot of new features and not so much new bugs ;-) I'm trying to convert a number of PSTs to maildir. Just plain drag&drop in Outlook doesn't work (gives a very cryptic error message in a certain folder, but that folder is perfectly all right), and using the import option also barfs when it's not even half-way through the PST. So, I took aid4mail and it converted the PST to mbox wihtout any problem. But now, I have a directory structure, filled with mbox mailboxes. Like: INBOX INBOX/mailbox INBOX/subfolder INBOX/subfolder/mailbox INBOX/subfolder/subsubfolder INBOX/subfolder/subsubfolder/mailbox INBOX/subfolder2 INBOX/subfolder2/mailbox etc. This differs from normal mbox setup, but given the fact that there are both folders AND messages below inbox, this is indeed the only useful way to do it. But now I cannot convert this to maildir using either dovecot or mb2md, since it's not the usual mbox setup. Any suggestions would be greatly appreciated! Thanks in advance, Maarten

2 3

[Dovecot] deliver looking into root directory for sieve configuration ?
by Guillaume Hilt 03 Jan '09

03 Jan '09

Hi, I'm using dovecot (+sieve), dspam, clamav and postfix with wirtual users and domains. When the server receive an email, I get this error : Jan 2 14:48:52 mail postfix/qmgr[13573]: 89DE1276C42B: from=<postmaster(a)shadowprojects.org>, size=926, nrcpt=1 (queue active) Jan 2 14:48:52 mail deliver(postmaster(a)adomain.fr): chdir(/root) failed: Permission denied Jan 2 14:48:52 mail deliver(postmaster(a)adomain.fr): stat(/root/.dovecot.sieve) failed: Permission denied Jan 2 14:48:52 mail deliver(postmaster(a)adomain.fr): msgid=<495E1B33.5020009(a)shadowprojects.org>: saved mail to INBOX Jan 2 14:48:52 mail postfix/lmtp[13584]: 89DE1276C42B: to=<postmaster(a)adomain.fr>, relay=mail.mydomain.com[/var/run/dspam/dspam.sock], delay=0.07, delays=0.05/0/0/0.01, dsn=2.6.0, status=sent (250 2.6.0 <postmaster@adomain> Message accepted for delivery) Why does it look inside the /root folder for sieve configuration ? All virtual mailboxes are in /home/vmail/DOMAIN/USER/.maildir (owned by postfix:postfix; dspam has been put in the postfix group) I uploaded the following config files in http://hiltg.pastebin.com/ : - main.cf - master.cf - dovecot.conf - dspam.conf (mails are supposed to be delivered to the mailbox by dovecot, which is called by dspam) Any idea please ? Thanks and happy new year to you all, -- Guillaume Hilt

4 17

[Dovecot] Per-namespace proxying?
by VanL 03 Jan '09

03 Jan '09

Hello, Searching in the archives, I saw the following posting from Timo Sirainen: [Dovecot] Roadmap to future (06 Dec 2007): [...] > Proxying > -------- > > - These could be implemented to v1.2. - Log in normally (no proxying) > if destination IP is the server itself. > > - Support for per-namespace proxying: > > namespace public { > prefix = Public/ > location = proxy:public.example.org > } > > There are two choices for this: Dummy IMAP proxying or handling it with > a mail storage backend. Dummy IMAP proxying would just let the remote server > whose mailbox is currently selected handle most of the commands and their > replies. I'm just afraid that this will become problematic in future. > ... (continues) Was this feature ever implemented? Is it in the 1.2 alphas? On a related note, were virtual mailboxes implemented? Thanks, Van

2 1

[Dovecot] Unkillable imap process?
by Johan Persson 03 Jan '09

03 Jan '09

Hi, Not sure if this is relevant but having been running dovecot 1.1.4 for a long time (without any problem) I recently upgraded to 1.1.7 when I switched to SuSE 11.1 This is just running on my home server and it's a fairly standard fetchmail-procmail-dovecot setup. However I recently had an incident which I cannot quite explain. I suspect it could be a possible disk problem but I did run a SMART check and the disks and HW seems ok. The mail store is mounted on a separate partition using ext3 fs What happened was that I noticed that the load on my server went through the roof and that the imap process was hogging 100% of the CPU and it had been running so for over an hour. Before this happened I had just setup a new laptop with Thunderbird as the mail client and had just done a off-line sync of my whole mail store (~1.5GB). So for a short time the dovecot server would have been under maximum load. I tried to recover by gracefully shutting down dovecot and when that didn't stop the imap process I first tried to be nice by sending it the TERM signal and when that didn't do it, the KILL signal. However, I was not able to stop the imap process. I then decided to recycle the server and initiated a shutdown. However, not even that was able to complete (since the shutdown process seemed to be hanging on not being able to stop the imap process). In the end I was (for the first time in over 6 years) forced to use the hard reset button on the server. I do realize that this is almost impossible to diagnose, but does anyone now in general what could possible cause the imap process to so completely be locked up that it is impossible to even shut it down? The dovecot -n output is 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.7-9-pae i686 openSUSE 11.1 (i586) ext3 log_path: /var/log/dovecot.err info_log_path: /var/log/dovecot.info login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 2 login_max_processes_count: 2 login_max_connections: 5 max_mail_processes: 32 mail_max_userip_connections: 8 mail_location: maildir:/srv/mail/%u mailbox_idle_check_interval: 15 fsync_disable: yes auth default: passdb: driver: pam userdb: driver: passwd Cheers Johan

3 2

[Dovecot] Possible to log IMAP connections to MySQL Table?
by Corey Shaw 03 Jan '09

03 Jan '09

Is it currently possible to log all IMAP connection attempts to a MySQL table? Thanks. _____________________ Corey

8 13

[Dovecot] NFS, IDLE, and index locking
by Jack Stewart 31 Dec '08

31 Dec '08

Hi, I'll try to keep short. My primary question is what, in people's experience, are the best configuration settings for to avoid potential NFS cache locking issues in an interesting heterogeneous environment? We appear to have a workaround for some locking issues we have seen, which is turning off IDLE. Upgrading our version of dovecot from 1.1.4 is likely to address some core issues, but I want to get the system setup in tune first. There are some things in our setup that seem dumb, and I would like to make sure they are dumb. As far as our environment goes, it isn't unusual for our users to connect with multiple different clients from multiple locations. Some of these clients behave well, and some not so well. In addition we have multiple distributed servers with multiple instances. Generally the connection from one of their clients/desktops goes to the same server but their different desktops may connect to different servers. If anyone has a similar enough environment, do you find it better to have the hard link setting off or is it better for you to turn it on? The attribute cache is the default (60 seconds) which works well enough in a polling setting but may be a problem with IDLE (30 second check). Do you find it better to bump up the IDLE check interval or drop the attribute cache? Our cache and maildir are on separate NFS volumes so we can change one without changing the other. Our tcp timeout setting is too long (it is the default). Do you find 180-300 seconds more reasonable? ---Jack To give some context, we have a handful of users with intermittent caching locking where the dovecot.index.cache file would simply not update. One of our internal people managed to get this problem when he was using pine (non-IDLE) with gnubiff (IDLE) from the same desktop. We haven't had any alarms since taking the brute force approach of turning off IDLE. Unfortunately other projects are inhibiting my capacity for additional debugging at this time. Also, it isn't clear to me that we will learn anything useful since the servers do not appear to be tuned and they are only running dovecot 1.1.4. Just for reference, below is our dovecot configutation. disable_plaintext_auth = yes base_dir = /var/run/dovecot/imap-server-its/ protocols = imap imaps syslog_facility = local4 shutdown_clients = yes ssl_cert_file = xxx.pem ssl_key_file = yyy.key ssl_ca_file = zzz.pem mail_location = maildir:/var/spool/maildir/%1Ln/%Ln:INDEX=/var/spool/dovecot/indexes/%1Ln/%Ln login_greeting_capability = no verbose_proctitle = yes mail_debug = yes imap_capability = "IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1" # MAILDIR Performance settings maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no # Handling web logins & imap traffic login_processes_count = 16 login_max_processes_count = 2048 max_mail_processes = 4096 mail_max_userip_connections = 2000 # NFS settings mmap_disable = yes fsync_disable = no mail_nfs_index = yes mail_nfs_storage = yes dotlock_use_excl = yes lock_method =fcntl protocol imap { listen = *:10143 ssl_listen = *:10993 imap_client_workarounds = delay-newmail outlook-idle netscape-eoh } ## Authentication processes namespace private { separator = . prefix = Mail. inbox = yes } auth_verbose = yes auth default { mechanisms = plain login passdb ldap { args = /etc/dovecot.conf-ldap } userdb static { args = uid=vmail gid=mail home=/var/spool/maildir/%1Ln/%Ln } socket listen { master { path = /var/run/dovecot/imap-server-its/auth-master user = vmail group = mail } user = root }

2 2