February 2012 - dovecot

Re: [Dovecot] Problem with Postfix + Dovecot + MySQL + Squirrelmail
by Gustavo 22 Feb '12

22 Feb '12

Ok, I study the wikki and the dovecot works. But when I try to send a mail using squirrel, I get this error on logs: Feb 11 18:41:55 jubileu postfix/smtpd[19522]: connect from localhost.localdomain[127.0.0.1] Feb 11 18:41:55 jubileu postfix/smtpd[19522]: warning: xsasl_cyrus_server_get_mechanism_list: no applicable SASL mechanisms Feb 11 18:41:55 jubileu postfix/smtpd[19522]: fatal: no SASL authentication mechanisms Feb 11 18:41:56 jubileu postfix/master[18383]: warning: process /usr/lib/postfix/smtpd pid 19522 exit status 1 Feb 11 18:41:56 jubileu postfix/master[18383]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling How can I fix this? My conf files seems to be ok: ## Diretorio Base ## base_dir = /var/run/dovecot/ ## Protocolos que ele ira executar ## protocols = imap imaps pop3 pop3s log_timestamp = '%Y-%m-%d %H:%M:%S ' syslog_facility = mail ## Dados do SSL ## ssl_listen = localhost ssl_cert_file = /etc/postfix/mail-cert.pem ssl_key_file = /etc/postfix/mail-key.pem ssl_parameters_regenerate = 168 verbose_ssl = no mail_location = maildir:/var/vmail/%d/%u mail_access_groups = mail mail_debug = no first_valid_uid = 150 last_valid_uid = 150 maildir_copy_with_hardlinks = yes protocol imap { } protocol pop3 { # Login executable location. login_executable = /usr/lib/dovecot/pop3-login mail_executable = /usr/lib/dovecot/pop3 pop3_uidl_format = %08Xu%08Xv } protocol lda { sendmail_path = /usr/lib/sendmail auth_socket_path = /tmp/auth-master } auth_verbose = no auth_debug = no auth default { mechanisms = plain login passdb pam { } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } userdb sql { args = /etc/dovecot/dovecot-sql.conf } socket listen { master { path = /tmp/auth-master mode = 0600 user = vmail group = mail } client { path = /tmp/auth-client mode = 0660 user = vmail group = mail } } } dict { } plugin { } ######################################### And Postfix conf: # SASL Authentication smtpd_sasl_auth_enable = yes smtpd_sasl2_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_path = private/auth smtpd_sasl_application_name = smtpd smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination permit_mynetworks = 127.0.0.0/8, 184.22.103.88/32, 184.22.103.87/32 Thanks!!! > -----Mensagem Original----- From: Timo Sirainen > Sent: Saturday, January 28, 2012 3:51 PM > To: Gustavo > Cc: dovecot(a)dovecot.org > Subject: Re: [Dovecot] Problem with Postfix + Dovecot + MySQL + > Squirrelmail > > On 27.1.2012, at 14.32, Gustavo wrote: > > #service dovecot start >> Starting IMAP/POP3 mail server: dovecotLast died with error (see error >> log for more information): Auth process died too early - shutting down >> > > No need to keep guessing the problem. "See error log for more information" > like it says. http://wiki.dovecot.org/**Logging<http://wiki.dovecot.org/Logging> > > -- Gustavo - clube03(a)gmail.com

2 2

[Dovecot] Where did the message end up?
by Dag Nygren 22 Feb '12

22 Feb '12

Hi all! Just migrated out UW-IMAP installation to Dovecot and so far so good. Had small teething problems though which left me with one question. The scenario was that I have a set of public folders that are only needed by the main company group (gid = company). Then there are some external users as well, not directly in the company group. I set up the public mailbox with permissions 660, owner me and group "company". That is the externals didn't have access to the mail folder. At this point all looked fine, but later there was an email to an external person and this was passed on to deliver by procmail. Procmail logs says all was OK, but there is an entry about the public folder not accessible in the Dovecot log. The email is nowhere to be found. My question: Where is the delivered email? Best Dag

2 5

Re: [Dovecot] Questions still about a uw-imap -> dovecot conversion
by Joseph Tam 22 Feb '12

22 Feb '12

Steve Campbell <campbell(a)cnpapers.com> writes: > > This was piped into a script that Email'd users about the changes > > that was going to happen, what they would expect to see, and a > > FAQ on how to set up a mail client correctly. > > Here, I'm not sure what should be done. The users with the secondary > folders that are not in ~/mail can't seem to get the client configured. "Great artists steal". Google around for a good set of instructions on how to set up IMAP prefix's for various mail clients, and refer your users to that. I also referred them to our webmail (with the correct mail prefix) as a reference to a list of mailboxes they ought to see. If they don't match, then that's a symptom of a bad prefix. > I've tried this and modified the .mailboxlist, but I'm thinking Dovecot > is ignoring this and I'm not sure what it's looking at to determine the > imap folders. > > > - .subscription files were moved into the mail folder > > (don't have to edit prefixes since the aliasing > > will take care of that). > > And when would these .subscription files be created? The first time the > folders would be accessed, or when? This seems to be part of my fix that > I'm getting lost on. Sorry, as Timo intimated, dovecot uses .subscription, which can be adjusted back to .mailboxlist, which uw-imapd uses. You shouldn't have to edit it if you set up namespace aliasing. Just move it from the top-level into your user's mail directory during cutover: (if you use dovecot's default subscription filename) mv $USER/.mailboxlist $USER/mail/.subscription If your IMAP client is still ignoring subscriptions, it usually means the client was configured that way. > > - your setup is fairly close to mine, so you may also run into > > the problem of user having mailboxes with group ownership that > > users are not part of (for example, group "mail" for INBOX set > > by your LDA or personal mailboxes with groups the user is no > > longer a member of) *and* with group permission not mode=0. > > Sendmail sort of requires the "mail" group, does it not? I'll take a > look and see if all users are part of this or not. A crazy solution > would be in order here? I think sendmail works fine if you set your mail spool mode=1777 (like /tmp), but have each inbox mode=0600. This setting will persist. It's sendmail LDA mail.local that's the problem: it autocreates new inboxes with permissions user:mail/660 and unless the user is in group "mail", chaos will ensue. You can maybe do a cron script or some other hack, or better yet, use dovecot LDA, which sets up the perms correctly (and keeps indexes updated). A one time "chmod go-rwx" during cutover is all that is required then. The log entry that points this problem out looks like dovecot: imap(smith): Error: chown(/dc-cache/smith/.imap/xx, group=6(mail)) failed: Operation not permitted (egid=5678(goodgroup), group based on /home/smith/mail/xx - see http://wiki2.dovecot.org/Errors/ChgrpNoPerm) dovecot: imap(smith): Error: mkdir(/dc-cache/smith/.imap/xx) failed: Not owner Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] dsync, hard-links and refcounts
by Christoph Bußenius 21 Feb '12

21 Feb '12

Hi, when creating a copy of a mail, dovecot provides a feature that will store its contents only once. In maildir, this is done by means of hard links, while mdbox has some special refcounting mechanism. My question is, how can we convert mails from maildir to mdbox without duplicating these copies? It seems that dsync does not detect the hard links. Even if the hard-linked mails have the same GUID listed in dovecot-uidlist, dsync creates multiple instances of the text. - Is there some way to make dsync notice the hard links? (I used dovecot 2.0.17) - Alternatively, is there some tool to deduplicate the mdbox after it has been converted from maildir? - NB: I am not talking about single-instance storage for attachments. Thank you very much, Christoph -- Christoph Bußenius Rechnerbetriebsgruppe der Fakultäten Informatik und Mathematik Technische Universität München +49 89-289-18519 <> Raum 00.05.055 <> Boltzmannstr. 3 <> Garching

2 10

[Dovecot] Managesieve AUTHENTICATE with IDN using UTF-8 or encode into ACE?
by Christian Rohmann 21 Feb '12

21 Feb '12

Hey dovecot-users, clients that speak telnet based protocols like http, smtp usually encode IDN (International Domain Names) containing UTF-8 characters into ACE (ASCII Compatible Encoding) punycode. I am wondering what the case was with managesieve (RFC 5804). For example if I was using a username like "user(a)xn--4ca0br.example.com" with the AUTHENTICATE command. Would that need to be encoded into ACE or be left in UTF-8? Reading section "2.1. AUTHENTICATE Command" or "4. Formal Syntax" suggests that quoted or literal UTF-8 is correct. Thanks Christian

2 1

[Dovecot] Some trouble with dovecot 2.1 and SASL
by Alessio Cecchi 21 Feb '12

21 Feb '12

Hi, I'm testing dovecot 2.1.0, on Debian 6.0, with "passdb driver = imap" and SASL for postfix's SMTP-Auth, like explained ih this howto: http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL Authentications over IMAP (local dovecot -> remote dovecot) works fine, and it's great. Also smtp-auth on postfix (over SASL) works fine. But in the dovecot log I found this error: Feb 19 11:11:42 demo-vpop dovecot: auth: Fatal: master: service(auth): child 30506 killed with signal 11 (core dumps disabled) even though all works fine. This is my dovecot configuration: # 2.1.0: dovecot.conf-imapc # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.4 auth_mechanisms = plain login default_login_user = nobody imapc_host = 10.0.0.1 mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_uid = imapproxy passdb { args = host=10.0.0.1 default_fields = userdb_imapc_user=%u userdb_imapc_password=%w driver = imap } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl = no userdb { driver = prefetch } But if instead of "unix_listener /var/spool/postfix/private/auth" I use: service auth { unix_listener auth-userdb { } inet_listener { port = 12345 } } no errors appears in the log. In both cases all works fine. Is there any errors in my dovecot's configuration? -- Alessio Cecchi is: on LinkedIn -> http://www.linkedin.com/in/alessice Assistenza Sistemi Linux -> http://www.cecchi.biz/ Hosting Linux -> http://www.hosting-linux.it @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it

3 4

Re: [Dovecot] Questions still about a uw-imap -> dovecot conversion
by Steve Campbell 21 Feb '12

21 Feb '12

On 2/20/2012 4:58 PM, Jim Lawson wrote: > On 2/20/12 3:36 PM, Steve Campbell wrote: >> >> Thanks for that input. I still think I'm missing something since I >> too used the compatibility link that you pointed to. Only thing is >> that proceeding those namespaces, I used the first example of: >> >> namespace { >> type = private >> separator = / >> prefix = "#mbox/" >> location = mbox:~/mail:INBOX=/var/mail/%u >> inbox = yes >> hidden = yes >> list = no >> } >> namespace { >> type = private >> separator = / >> prefix = >> location = maildir:~/mail >> } >> >> This seemed to get the ball rolling so that users could access >> anything at all. I still have the problem of client imap folders >> being different from webmail imap folders. That's pretty much why I'm >> thinking of using mbox as the INBOX and all other imap folders in the >> ~/mail directory in maildir format. > You ought to be able to get webmail to see the same folders as the > imap clients. > >> >> Should I remove the first two namespaces, in your opinion? Right now, >> the whole thing is kind of fragile. >> > > From your added namespaces, it looks like you are trying to support > mbox and maildir and ~/mail at the same time. Do you already have > maildir folders to support? If not, I would try to get things working > well with mbox first before I started a conversion to maildir. I > would also ask why you're thinking of moving to maildir. Yes, there > are caching benefits, but when you add the Dovecot indexing on top of > mbox, it's pretty much a wash. If you are using file-level backup, > rather than some sort of snapshot technology, maildir will be much, > much slower to back up. Your system will spend all its time walking > directories, opening and closing files. If you don't have many users > to worry about it might be OK, but make sure it's worth it. A lot of > sites went to maildir in the 1998-2004 era and have regretted the > decision as their systems get overloaded with files and they can't > back them up. No, I've got all mbox formats. Previous posts probably suggested that I wanted to move to maildir, but all of the replies I've received have convinced me that I do not want to do that. The folders in ~ and ~/mail are mboxes, so I need to see what damage I've done with a maildir namespace. The maildir reference could be part of the problems I'm seeing. I'm still not sure whether I should be seeing .subscriptions or mail/subscriptions anywhere and whether Dovecot will use the .mailboxlist that exists. The wiki suggests that I need to recompile Dovecot to continue using .mailboxlist. This is something I don't want to do. > >> Horde/Imp updates are probably out of the question until I can get a >> server to install the upgrade on. > For Dovecot and IMP both, you should set up an alternate server to > test out your config changes on before you put them into production. > If you are running on a bare metal single server, set up another > Dovecot instance on a different set of ports (I commonly use 20143 > (imap), 20993 (imaps), 20110 (pop3)) which you can fiddle with > freely. Once you are satisfied with the result in your various > clients, put it into production. You can do the same with Horde/IMP > by putting an installation in a different location on your webserver. > > Jim I've got a second server that is totally independent of the one I'm messing with. I've done the horde/imp alternate port/config. It all went well. The downside is that I didn't realize those secondary folders in ~/mail were being hidden. Kinda late to switch back, but the secondary server supports another domain, so I have it to test with. Again, the damage I've caused to those secondary imap folders needs to be determined to get this fixed properly. Most users are seing the secondary folders and can use them. It's just those users who have folders in ~ that are seeing problems as far as I can tell. Thanks steve > >

2 1

Re: [Dovecot] Questions still about a uw-imap -> dovecot conversion
by Joseph Tam 21 Feb '12

21 Feb '12

Steve Campbell wrote: > The more I read about all of this, the more I'm thinking about moving to > maildir format. My switchover this weekend is full of holes due to the > way user's imap folders were laid out. Some had folders in their home > directory and others might have folders in their /home/mail directory. I had the same problem, and handled it more or less the same way as the later poster (Jim Lawson <jtl+dovecot(a)uvm.edu>) handled his site. I retained use of mbox format as well. I planned the migration like this - scan user home directories for mailboxes (especially "Trash", "Drafts", "Sent", etc.) looking for "From " as the first 5 bytes. This was piped into a script that Email'd users about the changes that was going to happen, what they would expect to see, and a FAQ on how to set up a mail client correctly. - during the cutover, - mailboxes left on the home directory were moved to ~/mail, or renamed (e.g. "Sent" -> "00Sent" to avoid name collision for users that had a mixture of correct and blank prefixes. (I think I deleted "Trash", "Junk", etc. anyways). - Namespace aliasing was used so that prefixes "", "mail", "~/mail", and whatever darn fool settings my users used, would map to the same directory. - .subscription files were moved into the mail folder (don't have to edit prefixes since the aliasing will take care of that). - depending on what POP3 client you used (I used qpopper), you may need to configure pop3_reuse_xuidl = yes to avoid a massive re-downloading from POP3 clients after cutover. - the mail clients I control centrally (e.g. webmail, public server mail clients, etc). shouldn't need updating since they ought to have been set up properly in the first place. - after cutover, a second notification was sent for users that didn't move their mailboxes the first time around, and was it done for them during migration. And of course, test like crazy and watch the logs like a hawk. Other gotcha's: - your setup is fairly close to mine, so you may also run into the problem of user having mailboxes with group ownership that users are not part of (for example, group "mail" for INBOX set by your LDA or personal mailboxes with groups the user is no longer a member of) *and* with group permission not mode=0. You'll have to treat these (set mode=0, or change the group to something the user is part of), or the dovecot index creation will fail and they won't be able to access their mailboxes. I think my migration went pretty smoothly. Less than a handful of wazzup' Email problem reports. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Recalculate quota when quota=dict ?
by Jacek Osiecki 21 Feb '12

21 Feb '12

Hi, My current setting for quota is: plugin { #quota = dirsize:User quota #quota = maildir:User quota quota = dict:User quota::proxy::quota #quota = fs:User quota } I have used mb2md.pl and copied result files manually to a desired mail folder - but quota was not recalculated. And it seems, that no matter what I do - the quota usage remains the same. I tried uncommenting line with: quota = maildir:User quota but it did not help. Any other idea how to recalculate quota? Greetings, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

4 6

[Dovecot] passwd-file - lower limit for username?
by Oon-Ee Ng 21 Feb '12

21 Feb '12

Hi, previously I could use the following in my passwd-file:- AB:{plain}password I'm not sure when it stopped working, its not an account I access with any regularity, but today it would not work (2.1.0, 64-bit Arch Linux), with an 'unknown user' error in the logs. Is there some new lower limit for username length?

2 3