- dovecot - dovecot.org

[Dovecot] Login Failed
by Aydın Demirel 15 Mar '12

15 Mar '12

Hi; We are using scripts for login successes. Is there a feature for login failed status or can it be developed? Regards -- *Aydın Demirel Endersys Ltd. Sistem Destek Mühendisi/ System Support Engineer* * *<<Endersys is the first Advanced Business Partner of Red Hat in Turkey! http://www.europe.redhat.com/partners/endersys/>> Phone : +90 216 470 9423 | GSM : +90 530 401 8203 Fax : +90 216 470 9508 | Web : http://www.endersys.com <http://www.endersys.com/> Blog : http://blog.endersys.com <http://blog.endersys.com/> Twitter : http://www.twitter.com/endersys LPI : The #1 Linux Certification for IT Professionals LPI (Linux Professional Institute) Turkey http://www.lpi-turkey.com <http://www.lpi-turkey.com/>

2 1

[Dovecot] FTS crash
by Joan Moreau 14 Mar '12

14 Mar '12

Hi Timo, I updated my 2.1 from HG, and now the FTS (Squat) plugin makes a segmentation fault. When I remove the plugin from the dovecot.conf, all works fine. No debug available here, but let me know how can I help you. Joan

2 2

[Dovecot] RECENT status always 0
by Arnaud Abélard 14 Mar '12

14 Mar '12

Hello, we are using dovecot 2.0.13 with maildir++ (we migrated away from courrier just a few months ago) and the RECENT status doesn't seem to be working: . STATUS INBOX (MESSAGES UNSEEN RECENT) * STATUS "INBOX" (MESSAGES 35106 RECENT 0 UNSEEN 10) then 2 minutes later: . STATUS INBOX (MESSAGES UNSEEN RECENT) * STATUS "INBOX" (MESSAGES 35106 RECENT 0 UNSEEN 11) How can the UNSEEN count change without the RECENT count changing accordingly? Thanks in advance, Arnaud -- Arnaud Abélard (jabber: arnaud.abelard(a)univ-nantes.fr) Administrateur Système - Responsable Services Web Direction des Systèmes d'Informations Université de Nantes - ne pas utiliser: trapemail(a)univ-nantes.fr

2 1

[Dovecot] Thunderbird Archive to slower storage - sort of alternate storage
by Marcio Merlone 14 Mar '12

14 Mar '12

Hi people, When a user archives a message from Thunderbird it moves to an IMAP folder "Archives", everyone knows that. I use dovecot 1:1.2.9-1ubuntu6.5 on Ubuntu 10.04 and want to move that folder (and respective IMAP sub-folders) to a slower storage, link it to original location and my first idea for this is find -type d -name .Archives\* -print0 | \ while read -d $'\0' archive; do \ mv "$archive" /dead/Emails/jhon.doe/; \ ln -s "/dead/Emails/jhon.doe/$archive" .; done It works, given that the files are not locked. I could restart dovecot before so it would unlock the files, but there is no guarantee it does not get locked again before the find finishes. I took a look on mailling list archives, but could not find something like that and was wondering what you guys use (if any) for such task and what are the recommendations, best practices, solutions for that? Thanks in advance, best regards. -- *Marcio Merlone*

2 5

Re: [Dovecot] \NoSelect on missing folders in LIST
by Peter Mogensen 14 Mar '12

14 Mar '12

On 2012-03-05 16:36, Timo Sirainen wrote: >> Still curious about if Courier is doing something wrong which the scripts just happened to take advantage of. > > Neither behavior is wrong, just different. :) Ok... I were in doubt if I had missed something from the RFC. However... for testing, I tried to create "INBOX.INBOX" on dovecot. But then dovecot answers NO and complains that the folder already exists. Though it's still not on disk and dovecot still doesn't list it with "*". /Peter

2 1

[Dovecot] No passdbs specified in configuration file with passdb/userdb in protocol sections
by btb＠bitrate.net 13 Mar '12

13 Mar '12

hi- i have a configuration in which i'm using different passdb/userdb settings for each of imap, lmtp and smtp [without getting too far off on a tangent, this is so ldap group membership can be used to independently control authorization for receiving [lmtp], retrieving [imap], and sending [smtp/postfix] of email. each passdb/userdb uses a different search filter.] when i use this as my config: # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-15-generic-pae i686 Ubuntu 11.10 auth_debug = yes first_valid_gid = 2000 first_valid_uid = 2000 log_timestamp = "%d.%m.%Y %H.%M.%S " login_greeting = dovecot ready mail_debug = yes protocols = " imap lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 10026 } } ssl_cert = </etc/dovecot/pki/mra.example.com-cert.pem ssl_key = </etc/dovecot/pki/mra.example.com-key.pem verbose_proctitle = yes protocol imap { mail_max_userip_connections = 20 passdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } } protocol lmtp { userdb { args = /etc/dovecot/dovecot-ldap-lmtp.conf.ext driver = ldap } } protocol smtp { passdb { args = /etc/dovecot/dovecot-ldap-smsp.conf.ext driver = ldap } } dovecot complains: dovecot: auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism needs one which is a little confusing, since there are multiple passdbs specified, in the various protocol sections. i found that adding another "global" passdb to the config allows dovecot to work - e.g.: # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-15-generic-pae i686 Ubuntu 11.10 auth_debug = yes first_valid_gid = 2000 first_valid_uid = 2000 log_timestamp = "%d.%m.%Y %H.%M.%S " login_greeting = dovecot ready mail_debug = yes passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 10026 } } ssl_cert = </etc/dovecot/pki/mra.example.com-cert.pem ssl_key = </etc/dovecot/pki/mra.example.com-key.pem verbose_proctitle = yes protocol imap { mail_max_userip_connections = 20 passdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } } protocol lmtp { userdb { args = /etc/dovecot/dovecot-ldap-lmtp.conf.ext driver = ldap } } protocol smtp { passdb { args = /etc/dovecot/dovecot-ldap-smsp.conf.ext driver = ldap } } the problem with this is that while each of the passdb/userdb configs for the various protocols does indeed work, if a result is not found in one of them, the global passdb appears to then function as a catch-all. how can i tell dovecot it doesn't need a global passdb? each of the protocols' passdb/userdb configs is functioning as desired, but having dovecot look elsewhere upon failure ends up defeating the purpose. thanks -ben

2 2

[Dovecot] invalid mailbox name
by Vincent Schut 13 Mar '12

13 Mar '12

Hi, while migrating all mail from our old to our new server (using offlineimap, imap -> imap), I get the following error for one of my user's mailboxes: ERROR: Folder 'Organisations.RS Env & IJRS'[local_hoekman] could not be created. Server responded: ('NO', ['Invalid mailbox name: Organisations.RS Env & IJRS']) I suppose this is because of the ampersand in the mailbox name? Because other folder with spaces in it go just fine... Is this a fixed thing? Why was my user able to create the folder once? And why is dovecot 1.2.15 refusing to create the folder now? Migration is from dovecot 1.1.11 to 1.2.15. Thanks, Vincent.

2 5

[Dovecot] upgrade convert omissions
by Nick Edwards 13 Mar '12

13 Mar '12

It did not convert over some things: protocol imap { listen = *:143 mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle ssl_listen = *:993 } protocol pop3 { pop3_uidl_format = %f mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { mail_plugins = quota cmusieve quota_full_tempfail = no log_path = /var/log/dovecot/deliver.log deliver_log_format = msgid=%m: from=%f: %$ auth_socket_path = /var/run/dovecot/auth-master } I ended up with service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 } It looks like service-foobar is replacing stuff inside protocol {} but protocol still exists in examples, kind of confusing. Oh what about service-pop3, different than examples and service-imap, where's pop3s ? I guess I'll just copy the service pop3 section from an example file. Does all this mean the protocol section is not needed? or everything inside of them I had is no longer valid? No LDA specific logging converted, it did not include the quota stuff in where it is needed (mail_plugins went MIA), but did inside converted plugin section. I did note the conversion warned that workarounds = outlook-idle is no longer needed, but nothing about the other stuff. Just concerns me if it ignored some needed stuff, what else did it ignore. Nik (who is rather reluctant to use series 2 and break everything and stay with 1.2) Below is the new conf file: auth_cache_negative_ttl = 0 auth_cache_ttl = 5 mins auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no first_valid_uid = 95 last_valid_uid = 95 listen = *,:: log_path = /var/log/dovecot/pop3.log login_log_format_elements = user=<%u> method=%m rip=%r %c mail_location = maildir:/vmail/%d/%n/Maildir mail_nfs_index = yes mail_nfs_storage = yes maildir_very_dirty_syncs = yes mmap_disable = yes passdb { args = /etc/dovecot-sql.conf driver = sql } plugin { quota = maildir quota_rule = *:storage=1000M quota_rule2 = Trash:storage=100M quota_rule3 = Junk:ignore quota_rule4 = Spam:ignore quota_warning = storage=90%% /usr/local/bin/quotawarn-90.sh quota_warning2 = storage=75%% /usr/local/bin/quotawarn-75.sh } pop3_lock_session = yes protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = vmail } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 } shutdown_clients = no ssl_cert = </etc/ssl/certs/mail.crt ssl_key = </etc/ssl/certs/mail.key userdb { args = /etc/dovecot-sql.conf driver = sql }

2 2

[Dovecot] Trouble adding sasl support via dovecot
by Richard Troy 12 Mar '12

12 Mar '12

Hello Folks, I've been the admin of a site that uses Postfix with Dovecot on RedHat since, oh, gosh, maybe 1996? It's been a long time. I've never built it from source, though, just used the rpms (and I wonder if maybe that's my problem now). It just works, is reliable, and lets me be a very-part-time administrator. Repeatedly over the last few years I've been asked to have our mail system "join the modern age" and provide mail sending capabilities for clients that aren't on our internal network - via their smart-phones, from home, etc. OK... Well, way back when the site was set up, smtp servers didn't do any kind of "auth", but along the way to solving this problem (trying to configure pop-before-smtp, someone mentioned that Postfix now has an auth mechanism that uses Dovecot and I should use that instead! Great! ... Except that I've spent between 16 and 20 hours on this with no joy, and while I hate having to ask for help, it's time to ask what things that are obvious to the less ignorant that I must be doing wrong... Certainly, given the solid history of Postfix and Dovecot, I must be the problem! My problem statement is simply, "it should be working", but doesn't, and I don't get any announcement of "auth" when testing connections to Postfix as per directions here: http://www.postfix.org/SASL_README.html#server_test At least I haven't broken the normal functionality! I'm building a new server on the latest Fedora Core (16), but it's lacking in some hardware and won't be ready for a while, so I'm working with FC 14, running Postfix 2.5.6, and Dovecot 1.2.8. It uses the "cram-md5" auth scheme (which works fine and I'd hate to change it if I don't have to). The system has been up and functional on these versions for a couple of years, and quite stable, we just can't send if we're not local. When I do "postconf-a" it indicates cyrus and dovecot, so I take it that means Postfix has been built with sasl support. (I presume this means I don't have to compile it from source.) First Dovecot. Its set up to provide all protocols, but only imaps and pop3s have ports forwarded through the firewall. Plain-text auth is disabled, ssl is set to yes, ssl_listen is not specified, and the cert and key files are in the default locations - and work. No cipher list is used. Dovecot's chrooted. The protocol sections imap and pop3 take ALL the defaults, as does lda (I've ignored sendmail_path = /usr/lib/sendmail) as I don't think it matters. "auth default {" has mechanisms set to cram-md5, digest-md5, plain, and login, with passdb passwd-file pointing to a file in /etc where the cram data goes. It's not using pam, and there's an OLD comment in the config: # Experience says we need an empty passdb - passwd group: which is followed by passdb passwd{}. Later, there's "userdb passwd {}. All of that was configured long ago and has been functional. The changes I've made to add sasl support primarily pertain to the "socket listen section of "auth default". There, the master section remains commented out while the client section has been uncommented, the path set to /var/spool/postfix/private/auth, mode set to 0660, and the user and group have been set to postfix. ...This is all as described here: http://www.postfix.org/SASL_README.html and http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL That's it for Dovecot. Now, to Postfix itself. >From the working environ, only listening on port 25, I simply added the following (as per directions already cited above): smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_security_options = noanonymous, noplaintext smtp_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous smtp_sasl_tls_security_options = noanonymous And, of course, permit_sasl_authenticated was added to smtpd_recipient_restrictions. I got the impression from the baove sources that Postfix will then use Dovecot's authentication mechanism via a socket it finds in its private/auth subdirectory. NOT documented in any of those places, someone suggested I must turn on TLS. OK... The documentation found here: http://www.postfix.org/TLS_README.html claims (intimates) that it's not possible to run a site on a self-signed certificate, however, there's ZERO budget for a signed certificate, so unless I can get one for ten bucks somewhere, that could be a deal-breaker here. However, we've been using self-signed certificates for a while now and wonder why an "exception" mechanism wouldn't exist. As that web page talks about "Netscape" I suspect it's very old and may no longer apply. In any event, I tried this, too (after trying without). On the good side, an available Android phone, previously reading fine, but unable to send, no longer complained when the setup was changed to the imap username and password, same server address, TLS security type, and the server port of 25. HOWEVER, no mail has passed through it successfully, it just gives no error whatsoever, so far, while the server's log reports "Relay access denied." Notably, when setting up TLS, Postfix complained when the smtpd_tls_key_file was incorrect, but did not complain when it was provided properly, suggesting it's reading and accepting my self-signed certificate and private key. Ideas, please?! And, by the way, what's port 465 all about? Some clients propose that's what should be used to send... Thanks in advance for your help, Richard

2 2

[Dovecot] mdbox + gzip and rsync
by Jean-Daniel Beaubien 12 Mar '12

12 Mar '12

Hi, After reading the following paragraph from the dovecot doc, I've been wondering how it would affect rsync (when combined with gzip): "Expunging a message only decreases the message's refcount. The space is later freed in "purge" step. This is typically done in a nightly cronjob when there's less disk I/O activity. The purging first finds all files that have refcount=0 mails. Then it goes through each file and copies the refcount>0 mails to other mdbox files (to the same files as where newly saved messages would also go), updates the map index and finally deletes the original file. So there is never any overwriting or file truncation." How will the mailbox files (m.X) files be modified when I move or delete emails using mdbox+gzip. Will the resulting gzipped mdbox files be rsync-able or will they need a full re-upload? If I plan on using rsync for backups, am I better off not using the gzip feature (if i can spare the extra storage)??? Thanks, -JD

3 3