- dovecot - dovecot.org

[Dovecot] dovecot sasl auth (pam) + postfix doesn't work...
by marco ghidinelli 08 Mar '07

08 Mar '07

hello, i tried to use the "dovecot sasl" with postfix using pam as backend (actually pam_krb5) but it doesn't work. dovecot runs well as pop3 server authenticating with the pam_krb5 module with the config below, but it doesn't even connect with the kerberos server (a remote AD 2003) when it's called from postfix. --------dovecot.conf--------- protocols = pop3 pop3s imap imaps disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/mail/vhosts/turboden.net/%Ln/ mail_extra_groups = mail protocol imap { } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth_default_realm = MYCORP.LOCAL auth_verbose = yes auth_debug = yes auth default { mechanisms = plain login passdb pam { args = dovecot } userdb static { args = uid=5000 gid=5000 } user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { } -------------------------------- -----/etc/pam.d/dovecot------ auth required pam_krb5.so no_ccache ignore_root debug account required pam_permit.so ----------------------------- from syslog i only get: Mar 8 10:52:38 muletto dovecot: auth(default): client in: AUTH^I1^Iplain^Iservice=smtp^Iresp=<hidden> Mar 8 10:52:38 muletto dovecot: auth(default): passdb(username(a)MYCORP.LOCAL,master): Attempted master login with no master passdbs Mar 8 10:52:39 muletto dovecot: auth(default): client out: FAIL^I1^Iuser=username(a)MYCORP.LOCAL note that it doesn't care about the content of the /etc/pam.d/dovecot when dovecot is called by postfix. does the dovecot-sasl authentication works with the pam backend? maybe i should rename (or copy) the /etc/pam.d/dovecot to another name? let me know. bye.

2 1

[Dovecot] Proposal: RSS-Feed
by hadmut＠danisch.de 08 Mar '07

08 Mar '07

Hi, dovecot provides POP and IMAP services. Proposal: Would be nice if it also could offer an RSS-Feed for a mailbox, giving a summery of sender/subject/date and maybe the first lines of text. regards Hadmut

3 4

[Dovecot] 1.0rc26: ssl_verify_client=yes ?
by Leroy van Logchem 08 Mar '07

08 Mar '07

Q1) I can't get ssl_verify_client_cert=yes working. The ssl key and cert are signed using our CA. Also the ssl_ca_file has a CRL appended (no revokes yet). Expected behavior: Stop the SSL (the client doesn't have a cert installed) Current behavior: Mail clients accepts SSL and login succeeds. (both Evolution and Thunderbird). My bad? Please advise. Q2) The next step, if dovecot blocks the client because of the verify_client_cert, how to create certs for OE, Evolution and Thunderbird? Thanks, Leroy Server type: Linux Red Hat ES 4.4 (32bit) # ./dovecot -n # /drbd/imap/dovecot-1.0.rc26/etc/dovecot.conf log_path: /drbd/imap/dovecot-1.0.rc26/var/dovecot.log protocols: imaps listen: a.b.c.39:143 ssl_listen: a.b.c.39:993 ssl_ca_file:/drbd/imap/dovecot-1.0.rc26/etc/certs/CA/cacert_with_crl.pem ssl_cert_file:/drbd/imap/dovecot-1.0.rc26/etc/certs/CA/imaps-signedcertificate.pem ssl_key_file:/drbd/imap/dovecot-1.0.rc26/etc/certs/CA/imaps-privatekey.pem ssl_verify_client_cert: yes verbose_ssl: yes login_dir: /drbd/imap/dovecot-1.0.rc26/var/run/dovecot/login login_executable: /drbd/imap/dovecot-1.0.rc26/libexec/dovecot/imap-login verbose_proctitle: yes mail_extra_groups: mail mail_location: mbox:~/:INBOX=/var/mail/%u mmap_disable: yes mbox_write_locks: fcntl dotlock imap_client_workarounds: delay-newmail outlook-idle auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes passdb: driver: passwd-file args: /drbd/imap/dovecot-1.0.rc26/etc/userdb_extra passdb: driver: pam userdb: driver: passwd-file args: /drbd/imap/dovecot-1.0.rc26/etc/userdb_extra userdb: driver: passwd Details (LONG) follow: # cat cacert_with_crl.pem -----BEGIN CERTIFICATE----- MIICxzCCAjCgAwIBAgIBADANBgkqhkiG9w0BAQQFADBSMRwwGgYDVQQKExNXTCBE ZWxmdCBIeWRyYXVsaWNzMQ4wDAYDVQQHEwVEZWxmdDEVMBMGA1UECBMMWnVpZCBI b2xsYW5kMQswCQYDVQQGEwJOTDAeFw0wNzAzMDgxMjE1MzhaFw0xNzAzMDUxMjE1 MzhaMFIxHDAaBgNVBAoTE1dMIERlbGZ0IEh5ZHJhdWxpY3MxDjAMBgNVBAcTBURl bGZ0MRUwEwYDVQQIEwxadWlkIEhvbGxhbmQxCzAJBgNVBAYTAk5MMIGfMA0GCSqG SIb3DQEBAQUAA4GNADCBiQKBgQCp4s55PxpcEgk1KhAJ3DA/DXKHBtUoAE3K273t 1nJzuAujA0mfVtpinDdpreHp53bVGSN5xIDZ+Ljy8wW7lPB5YSwBQFbIoFx/6NkI QPkYeVZ0NrFC1g2tZRD4ObRkqFuApr60+NokY+e3KuInnCdAf0Itb4VVolMvWccz vqdJBQIDAQABo4GsMIGpMAwGA1UdEwQFMAMBAf8wHQYDVR0OBBYEFPynIoyRPF2s UiGO+3RQr2pThXzQMHoGA1UdIwRzMHGAFPynIoyRPF2sUiGO+3RQr2pThXzQoVak VDBSMRwwGgYDVQQKExNXTCBEZWxmdCBIeWRyYXVsaWNzMQ4wDAYDVQQHEwVEZWxm dDEVMBMGA1UECBMMWnVpZCBIb2xsYW5kMQswCQYDVQQGEwJOTIIBADANBgkqhkiG 9w0BAQQFAAOBgQAtRPC7laBPuOMAein4ZXjxSia6l7XjpAI/A2bXFvbV1ulNzbno KYbeqfv6zp1SLWrKvwGeu4DrHLe098ATADqLWANqNqfI5t40nND1rsfGmjGTOJ7v /Q53AaTXEBn2D1ZIqGMUuFOXv0BFi1U2BmPyTt6hlZ1D7wTERxo0UGXFXw== -----END CERTIFICATE----- -----BEGIN X509 CRL----- MIIBFzCBgTANBgkqhkiG9w0BAQQFADBSMRwwGgYDVQQKExNXTCBEZWxmdCBIeWRy YXVsaWNzMQ4wDAYDVQQHEwVEZWxmdDEVMBMGA1UECBMMWnVpZCBIb2xsYW5kMQsw CQYDVQQGEwJOTBcNMDcwMzA4MTIyODE5WhcNMDcwNDA3MTIyODE5WjANBgkqhkiG 9w0BAQQFAAOBgQBnXWqvR9oS674EyNHYoOmv0KeFcVqLOUpR7bVGbMYvCsMc56yy E473NULD0EL0BZFMgGdN05e53KLnOoLiuvFuhCAxZW7o7f72lJC+wegFwROp7OOc aKJ5lumaZ86Xb0uM8N/yJ/5xxCubrt1TYGQYPTjoQo4rJccpFy8aeqNDrA== -----END X509 CRL----- ]# cat imaps-signedcertificate.pem -----BEGIN CERTIFICATE----- MIICHTCCAYYCAQEwDQYJKoZIhvcNAQEEBQAwUjEcMBoGA1UEChMTV0wgRGVsZnQg SHlkcmF1bGljczEOMAwGA1UEBxMFRGVsZnQxFTATBgNVBAgTDFp1aWQgSG9sbGFu ZDELMAkGA1UEBhMCTkwwHhcNMDcwMzA4MTIyMDA2WhcNMDgwMzA3MTIyMDA2WjBc MQswCQYDVQQGEwJOTDEVMBMGA1UECBMMWnVpZCBIb2xsYW5kMRwwGgYDVQQKExNX TCBEZWxmdCBIeWRyYXVsaWNzMRgwFgYDVQQDEw9pbWFwLndsZGVsZnQubmwwgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALlEnCZu2o7LGp1x1rwBY2nZJH49L7by F8GVRpnoi7wnvXV11Iy7JUd0qbyBDWNn6EiBJ2YMemSmceVpXtyxI6wbBqmq0kgn 1VmglFUcYXRx6mkXuMx17OXpqSB9jNU22ldn20h/Xr1yhJ8W/RpohG9u6jebFiF3 qJXdyjXJqPSBAgMBAAEwDQYJKoZIhvcNAQEEBQADgYEAVwOhL3FICQeMJOSxil2S K1TiN+6zjrVDq7L7t7myOkWJA6hrZcPWQZfCV5ZoWaG8nREdesKAQBRvkT6uwmcJ 3pYpc/iBTtmwCpEVjfv0Ki9VwXpWuRo0FcQkrc8MVbclwnkGmtPAJAY7Dz7U/uBf w4N5cj1pfHltVEeD9Jb9tBo= -----END CERTIFICATE----- # cat imaps-privatekey.pem -----BEGIN RSA PRIVATE KEY----- <better not include this :)> -----END RSA PRIVATE KEY-----

3 4

[Dovecot] Different passwords for different IP-Addresses/protocols?
by hadmut＠danisch.de 08 Mar '07

08 Mar '07

Hi, I'd like to do the following: Have an IMAP server, avaible - at localhost 127.0.0.1 without SSL for local clients and web based applications such as squirrelmail - from outside with SSL for mobile users but - for security reasons - would like to use different passwords on both ports. How could I achieve that? regards Hadmut

2 1

[Dovecot] convert plugin
by FiL ＠ Kpoxa 07 Mar '07

07 Mar '07

Was about to try convert plugin (as opposed to mb2md.pl) and noticed, that it doesn't convert subfolders. I have following structure: ~/ | mail/ | Archive | Help | Sent | Done/ | Cardiology | Childrens | Orkin when I use convert-tool - #convert-tool username /home/username mbox:/home/username/mail/ maildir:/home/username/Maildir/ Error: Mailbox conversion: Couldn't create mailbox Done/Cardiology Error: Internal failure If I try "on the fly" conversion (by putting convert_mail = mbox:%h/mail & convert_skip_broken_mailboxes=yes in dovecot.conf) I get this in the log - Mar 6 12:23:33 enders2 dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Mar 6 12:23:43 enders2 dovecot: IMAP(username): Mailbox conversion: Couldn't create mailbox Done/Cardiology Both methods convert Archive and Logs mailboxes fine. Can anybody confirm? P.S. Linux enders2.tchlab.org 2.6.18-1.2200.fc5smp #1 SMP Sat Oct 14 17:15:35 EDT 2006 i686 i686 i386 GNU/Linux dovecot-1.0.rc22 (I know this is not the latest version, but I didn't see any changes to convert tool/plugin). FiL

2 4

[Dovecot] Config questionsabout various login parms
by Stewart Dean 07 Mar '07

07 Mar '07

I'm currently runing UW-IMAP (compiled vanilla) with procmail and mbox and am making my usual careful crawl (at turtle speed) through figuring out DC config. Some questions: a) I have something like 3-4 root imapd sessions so I presume that the default *login_processes_count* = 3 will be OK. I'm less clear about login_max_processes_count and login_max_connections = 256. A common enough heavy load has something like 275 unique users accessing imap and 600 imapd processes. Suggestions? I'm beginning with no SSL, KISS. b) If I set login_process_per_connection =no, would the number of users accessing imap be the same as the number of imapd sessions? c) login_process_size is confusing/intriguing. If there are 500 processes, the default of 32MB means 16GB (the box has 12GB). OTOH, what about the big players with a 400 MB inbox...will they be able to open their inbox with the default d) login_max_connections ditto...I shouldn't think that an individual user would conceivably have the default of 256, except pathologically....or is this applied to the listening imapd root processes. Thanks in advance for your help and patience......... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 5

[Dovecot] Nokia 6680 and Dovecot
by Boris Ivanov 07 Mar '07

07 Mar '07

Hi Guys Im using Nokia 6680 to connect to dovecot (dovecot-1.0.b7_1 from FreeBSD ports) Where ever it trying to login it failed despite it works well with PC clients. * OK [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1 CAPABILITY * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN 1 OK Capability completed. 2 LOGIN sj sj 2 NO Authentication failed. I relized that problem is 1 character message tag - 1,2. Is it bug in phone or in dovecot? -- Yours Boris

2 2

[Dovecot] Newbie questions: Load-balanced Dovecot with NFS storage
by Mike Brudenell 07 Mar '07

07 Mar '07

Hi, I experimented with Dovecot a while back and our site is now taking the plunge to switch to it from the UW IMAP server when we rejig the topology of our mail store and IMAP servers. Currently we have a farm of 5 IMAP servers running the UW server. Each has locally attached disk used to store people's mailboxes. Each user is allocated to one of these five servers and can only access their mail via that server. Our aim is to remove this restriction to provide resilience in the event of a server failing. Our thoughts... * We are envisaging having a farm of N (to be determined) servers running Dovecot. These will be closed systems: users do not have shell- access, and can only reach their mail via IMAP. * A single mailstore common to all N servers will be hosted on our NetApp filer and NFS-mounted on each server. Each server would be running Solaris 10. If we use all-new kit it will be x86-based, or we may have to redeploy some of our existing SPARC boxes to the new service. * We will be converting user mailboxes to be in Maildir format. * Our hardware load balancer, which supports persistent sessions, will be used to distribute users between the servers. This could either direct a user to any one of the N servers, or could be set to 'prefer' a given server for a particular user (only failing over to one of the others if their 'usual' server was unavailable). More on this in my questions below. :-) I have been scouring the Dovecot list, archives and Wiki and think I have come up with a set of issues we need to be aware of and things we have to do in order to make this work reliably. Please would you let me know if I have missed or misunderstood anything? Issues To Watch For ------------------- * For timestamp integrity our servers will be synched with NTP to our local time server. * Because sessions could be on different servers memory mapping of index files doesn't work well with NFS, so set mmap_disable=yes in dovecot.conf. * Dovecot relies on the mtime timestamp of mailbox files so the NFS-mounted mailstore needs to be mounted with these options on each server: actimeo=0 (Are there any other mount options we should use too?) * We will be using filesystem quotas on users mailboxes. We understand that Dovecot's index files are best on no-quota filestores so will store these separately. Questions --------- Q1. Would it be better to store the index files on NFS-shared filestore and direct users to any of the IMAP server machines? Or to store the index files on local disk and direct each user to their 'preferred' IMAP server machine? Q2. Does Dovecot (or "something") clean out old index files that haven't been accessed for a while? Eg, when a user has temporarily come through on a different IMAP server to normal. Or do the index files sit there untouched for evermore? Q3. Storing the index files on the NetApp filer would give us the ability to share them between servers and grow their volume as need be, but at the cost of performance. How big do the index files get? Are they typically a few kBytes per message? Per mailbox? Per user? Or more? Q4. We will be using Exim as the MTA, which can deliver direct to Maildir mailboxes. However I understand that Dovecot's "deliver" LDA adds the benefit of updating the index files as each message is delivered. Is this a significant gain? Or is there little difference in actual use? Q5. We have around 20,000 mail accounts and will therefore be seeing lots of concurrent IMAP sessions, usually secure (SSL) ones. I have seen mention that this can give rise to "Too many open files" errors under Solaris. How do we avoid this when we are likely to have several thousand concurrent IMAP sessions per server machine? With many thanks for your time and advice... Cheers, Mike Brudenell -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

5 9

[Dovecot] Time moving backwards error
by Emmett Pate 07 Mar '07

07 Mar '07

I'm running dovecot on an OpenBSD 3.7 server and after upgrading to RC25, the daemon started exiting with: Fatal: Time just moved backwards (1173221579 -> 1173221578)! This might cause a lot of problems, so I'll just kill myself now. After upgrading to RC26, I've gotten the error: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. Occasionally, however, it's followed by: Fatal: Sleep interrupted, byebye. The server is running NTP, but I can't find any reason why it would have to roll the clock back a second so often. Until I get this figured out, I've gone back to RC19. Any ideas? Thanks. -- Emmett "Buddy" Pate Chief Technology Officer William E. Wood and Associates, Realtors epate(a)williamewood.com

3 2

[Dovecot] dovecot-ldap.conf - Active directory
by Cristian Salan 07 Mar '07

07 Mar '07

Hello, I have a configuration with dovecot-ldap working with openldap (on FreebSD 5.4 Release). Now I'm trying to do the same thing with an Active Directory (win2k3). I have installed an properly configured SFU. Via nss_ldap-pam_ldap is working fine (FreeBSD 6.2 Release). Because nss_ldap is reported broken with dovecot I'm trying to use dovecot-ldap for both passdb and userdb. My guessed filters/attributes follows: user_filter = (&(objectClass=user)(msSFU30Name=%u)) user_attrs = homeDirectory=msSFU30HomeDirectory, uidNumber=msSFU30UidNumber, gidNumber=msSFU30GidNumber pass_attrs = msSFU30Name,msSFU30Password pass_filter = (&(objectClass=user)(msSFU30Name=%u)) But it doesn't work. Any advice? Cristian Salan

2 1