December 2012 - dovecot

[Dovecot] Possible bug not sure on which end
by joshua.trier＠hostrocket.com 17 Dec '12

17 Dec '12

Hello Serveral of our clients are running into a problem relating to Gmails change in their "Check mail from other accounts (using POP3):". It seems related to the response dovecot sends back on a connection. Gmail is checking for a +OK in the header, however dovecot is sending OK without a prefix of +. Here is the response from Gmail webmail "Missing +OK response upon connecting to the server: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready." Here is dovecot header on a pop3-ssl connection * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. Who's end is this problem on? Google's, dovecots? Anyway to enable the response to include a +? Thanks Josh

3 2

Re: [Dovecot] Non-dovecot user looking for feedback
by Joseph Tam 17 Dec '12

17 Dec '12

On Mon, 17 Dec 2012, Chris Ross wrote: > I've been using UW-IMAPd for neigh on forever (at least since 2001). > But, as it's basically stalled, and I'm about to update the hardware > that is my mail server, I thought it was time to review existing > open-source IMAP servers. Dovecot is the top three in my looking. I converted a few years ago and never looked back. > So, am I right that dovecot supports only the "one big full file" mbox > format, and the maildir format? And if so, is it known to allow > multiple simultaneous IMAP clients to access and monitor and/or modify > the same folder simultaneously? I still run using mbox, and have not had a problem with corruption, however, this is probably owing to our modest IMAP demand and careful coordination of file locks among all the different MUAs. You're better off with Maildir and other formats, that are better designed for simultaneous access. There are other good reasons to switch formats. Dovecot also supports its own mdbox/sdbox for high performance: its a hybrid that tries to incorporate the best of both words. More info http://wiki2.dovecot.org/MailboxFormat > After those questions, it's just a "what do you think the pros and cons > of each are?" I can't speak to the other software you are looking at, but two factors I found to be particularly good: - flexibility: you can get almost every oddball setup to work. Migration from uw-imapd is fairly easy, but then again, uw-imapd didn't have a lot of knobs to turn. Plugins are available that extends its functionality. - support: this mailing list is great, and Timo is an absolute wizard in getting bugs fixed. (Note: I am shamelessly buttering him up so that he fixes the outstanding bug I reported!) Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] more than one password_query
by goffer 16 Dec '12

16 Dec '12

Hello, I use dovecot + postfix with postfix sasl authentication by dovecot auth service. I have one question. Is it possible to have separate password_query only for auth service. I have two fields in database, one permits login to imap pop, second I want to use to permit login to smtp. Please explain how to set this (if it is possible) or give me some direction and sorry my English. -- View this message in context: http://dovecot.2317879.n4.nabble.com/more-than-one-password-query-tp39282.h… Sent from the Dovecot mailing list archive at Nabble.com.

1 1

[Dovecot] need help with dovecot-lda
by Andreas Meyer 16 Dec '12

16 Dec '12

Hello all! Some month ago I upgraded our dovecot installation from version 1.0.5 to version 2.1.7 without having any trouble. Postfix is delivering email directly per virtual transport to the maildirs and mailboxes of the users in /var/spool/vhosts/domains/.... Now I want to use dovecot-lda and created a new entry in the master.cf of postfix. dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} It is not clear to me, how the dovecot-lda is started bei dovecot and you it finds the socket dovecot postfix created. The dovecot.conf looks like this; # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.22.5-31-bigsmp i686 openSUSE 10.3 (i586) ext3 auth_verbose = yes disable_plaintext_auth = no log_path = /var/log/dovecot1 mail_location = mbox:/var/spool/vhosts/%d/dovecotprivate/%n:INBOX=/var/spool/vhosts/%d/%n !include /etc/dovecot/conf.d/*.conf passdb { args = /etc/dovecot/passwd driver = passwd-file } userdb { args = /etc/dovecot/passwd driver = passwd-file } ssl_cert = < /etc/dovecot/ssl/hostcert.pem ssl_key = < /etc/dovecot/ssl/hostkey.pem #verbose_ssl = yes plugin { quota = maildir:User quota quota_rule = *:storage=500MB # 10% of 1GB = 100MB quota_rule2 = Trash:storage=+10%% # 20% of 1GB = 200MB # quota_rule3 = Spam:storage=+20%% autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent } I set soft_bounce = yes in main.cf of postfix and delivery of mail fails with Dec 14 16:13:34 delta postfix/virtual[14082]: BBC0F1B31294: to=<xyz(a)anup.de>, relay=virtual, delay=395, delays=395/0.01/0/0.13, dsn=4.1.1, status=SOFTBOUNCE (unknown user: "xyz(a)anup.de") This is the relevant part of the main.cf: dovecot_destination_recipient_limit = 1 virtual_mailbox_domains = anup.de bit-corner.de bitcorner.de baubetreuung-meyer.de saxelektro.de virtual_mailbox_base = /var/spool/vhosts #virtual_mailbox_maps = hash:/etc/postfix/vmailbox #virtual_minimum_uid = 100 #virtual_uid_maps = static:5000 #virtual_gid_maps = static:5000 virtual_mailbox_limit = 524288000 virtual_transport = dovecot I don't get it right. As far as I understand postfix uses virtual_transport = dovecot and hands the mail over to the socket dovecot. But how does dovecot know where to look for the socket. I am missing somthing but don't know what. Any help is appreciated! Andreas

3 27

[Dovecot] Dovecot "sleep" for short snapshots
by Peer Heinlein 15 Dec '12

15 Dec '12

Making consistent backups from Dovecot with mdbox requires a snapshoted filesystem with (at least) a short Downtime for Dovecot. I'd like to avoid killing several thenthousand IMAP-sessions for 60 seconds. Users don't like that... And the admin dislakes that too... What about a "short sleep" mechanism for Dovecot, where all writes are finished and new writes are easily delayed? I'd like to following process: *) "doveadm sleep" puts Dovecot in sleep-Mode: -- All existing writes are finished (before "doveadm sleep" is allowed to exit) -- All new writes are simply delayed -- All readonly-operations could work normally, so users can fetch and read mails *) The the admin can create a LVM-/SAN-snapshot of the filesystems *) "doveadm unsleep" will finish the magic Overall the whole process will take just some seconds. Users will recognize a simple write-delay, but they can work normally and the aren't unconnected at all. If the snapshot is really fast the users won't recognize the whole situation at all. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1

[Dovecot] BUG: mishandling of username if it's a keyword?
by Jack Bates 14 Dec '12

14 Dec '12

Dec 14 14:33:03 test2 dovecot: auth: Debug: auth client connected (pid=24143) Dec 14 14:33:14 test2 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011secured#011session=D6dl6dDQdAAAAAAAAAAAAAAAAAAAAAAB#011lip=::1#011rip=::1#011lport=110#011rport=38004#011resp=<hidden> Dec 14 14:33:14 test2 dovecot: auth: Debug: static(home,::1,<D6dl6dDQdAAAAAAAAAAAAAAAAAAAAAAB>): lookup Dec 14 14:33:14 test2 dovecot: auth: Debug: client passdb out: OK#0111#011user=home Dec 14 14:33:14 test2 dovecot: auth: Debug: master in: REQUEST#0112033451009#01124143#0111#011243997dcca92c2dc1d1e401c78b4ea4f Dec 14 14:33:14 test2 dovecot: auth: Debug: master userdb out: USER#0112033451009#011uid=503#011gid=503#011home=/nfs/maildir/vmail/home#011mail_location=maildir:~/Maildir Dec 14 14:33:14 test2 dovecot: pop3-login: Login: user=<home>, method=PLAIN, rip=::1, lip=::1, mpid=24145, secured, session=<D6dl6dDQdAAAAAAAAAAAAAAAAAAAAAAB> Dec 14 14:33:14 test2 dovecot: pop3: Debug: Added userdb setting: mail_location=maildir:~/Maildir Dec 14 14:33:14 test2 dovecot: pop3(uid=503): Error: user uid=503: Couldn't drop privileges: User is missing UID (see mail_uid setting) Dec 14 14:33:14 test2 dovecot: pop3(uid=503): Error: Internal error occurred. Refer to server log for more information. compared to: Dec 14 14:37:25 test2 dovecot: pop3-login: Login: user=<home2>, method=PLAIN, rip=::1, lip=::1, mpid=24190, secured, session=<5Zdb+NDQdQAAAAAAAAAAAAAAAAAAAAAB> Dec 14 14:37:25 test2 dovecot: pop3: Debug: Added userdb setting: mail_location=maildir:~/Maildir Dec 14 14:37:25 test2 dovecot: pop3(home2): Debug: Effective uid=503, gid=503, home=/nfs/maildir/vmail/home2 userdb { args = uid=vmail gid=vmail home=/nfs/maildir/vmail/%u mail_location=maildir:~/Maildir driver = static } This was tested on a static passdb/userdb on a test server as well as production. version 2.1.10. When I have time, I'll dig into it myself after an upgrade to 2.1.12. Jack

2 5

[Dovecot] can't connect to server
by Bernics Gábor | Penta Unió Zrt. 14 Dec '12

14 Dec '12

Hello, I can't connect to a dovecot server (Debian 6.0, default version of Dovecot), I started the daemon but I didn't see errors on console. dovecot-lda works. logs: 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: Loading modules from directory: /usr/lib/dovecot/modules/lda 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: Module loaded: /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so 2012-12-14 12:47:10 auth(default): Info: master in: USER<------>1<----->bernics.gabor(a)penta.hu<>service=deliver 2012-12-14 12:47:10 auth-worker(default): Info: sql(bernics.gabor(a)penta.hu): query: SELECT email AS user, password FROM users WHERE email 2012-12-14 12:47:10 auth(default): Info: password(bernics.gabor(a)penta.hu): Credentials: 54617661737a69737a656c 2012-12-14 12:47:10 auth(default): Info: master out: USER<----->1<----->bernics.gabor(a)penta.hu 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: Quota root: name=user backend=dict args=:proxy::quotadict 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: dict quota: user=bernics.gabor(a)penta.hu, uri=proxy::quotadict, noenforcing=0 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: maildir: data=/home/vmail/mail/penta.hu/bernics.gabor(a)penta.hu/Maildir 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: maildir++: root=/home/vmail/mail/penta.hu/bernics.gabor(a)penta.hu/Maildir, inde 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: dict quota: user=bernics.gabor(a)penta.hu, uri=proxy::quotadict, noenforcing=0 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: sieve: user's script path /home/vmail/penta.hu/bernics.gabor(a)penta.hu/Maildir/ 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: sieve: using sieve path for user's script: /etc/dovecot/dovecot.sieve 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: sieve: executed before user's script(1): /etc/dovecot/dovecot.sieve.before 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: sieve: opening script /etc/dovecot/dovecot.sieve.before 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: sieve: opening script /etc/dovecot/dovecot.sieve 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: Namespace : Using permissions from /home/vmail/mail/penta.hu/bernics.gabor@pen 2012-12-14 12:47:10 deliver(bernics.gabor(a)penta.hu): Info: sieve: msgid=<20121214114708.5BD7917402D(a)mail2.penta.hu>: stored mail into mai config: http://pastebin.com/4imMFZSi Best Regards, Gabor

2 1

[Dovecot] Copying just the folders to new Dovecot server?
by Bjørn T Johansen 14 Dec '12

14 Dec '12

I am setting up a new Dovecot server and I want to start from scratch, i.e. with an empty mailbox. But I want to have the same folders in my new mailbox that I have in my old. Is there a way to create these folders without manually creating one by one? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" ----------------------------------------------------------------------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 2

[Dovecot] Dovecote Warnings
by anarchos78 14 Dec '12

14 Dec '12

Greetings, I have setup Postfix/Dovecote on Ubuntu 12.04 (apt-get install mail-stack-delivery). While everything is working fine in the mail server I have niticed the following errors: srv dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:13: listen=..:port has been replaced by service { inet_listener { port } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:13: protocol { listen } has been replaced by service { inet_listener { address } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:14: protocol { ssl_listen } has been replaced by service { inet_listener { address } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:14: ssl_listen=..:port has been replaced by service { inet_listener { port } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:21: listen=..:port has been replaced by service { inet_listener { port } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:21: protocol { listen } has been replaced by service { inet_listener { address } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:22: protocol { ssl_listen } has been replaced by service { inet_listener { address } }: 2 Time(s) *The "01-mail-stack-delivery.conf" file looks like this:* # Some general options protocols = imap pop3 sieve disable_plaintext_auth = yes ssl = yes ssl_cert = </etc/ssl/certs/ssl-mail.pem ssl_key = </etc/ssl/private/ssl-mail.key ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM mail_location = maildir:~/Maildir auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # IMAP configuration protocol imap { listen = *:143 ssl_listen = *:993 mail_max_userip_connections = 10 imap_client_workarounds = delay-newmail } # POP3 configuration protocol pop3 { listen = *:110 ssl_listen = *:995 mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } # LDA configuration protocol lda { postmaster_address = postmaster mail_plugins = sieve quota_full_tempfail = yes deliver_log_format = msgid=%m: %$ rejection_reason = Your message to <%t> was automatically rejected:%n%r } # Plugins configuration plugin { sieve=~/.dovecot.sieve sieve_dir=~/sieve } # Authentication configuration auth_mechanisms = plain login service auth { # Postfix smtp-auth unix_listener /var/spool/postfix/private/dovecot-auth { mode = 0660 user = postfix group = postfix } } What is going wrong with Dovecote. I am a newcomer and i need little help. Many thanks, Tom Greece -- View this message in context: http://dovecot.2317879.n4.nabble.com/Dovecote-Warnings-tp39221.html Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] More detail re dovecot-uidlist and -uidvalidity files
by Dale Gallagher 13 Dec '12

13 Dec '12

Regarding the dovecot-uidlist header (first line) - I've tried to search for and figure out what exactly is meant by the "mailbox global uid" and once I do, how to manually generate the 128 bit hex variation of it? Could someone elaborate on this, please. How would omitting the global uid field, beginning with G, affect remote clients' syncing of mail? Is this field mandatory? Would "3 V$uid_validity N$next_uid" be sufficient to ensure that clients don't re-download everything? I also see that Dovecot's dovecot-uidvalidity is of the form 4df8a4e2, whereas the IMAP syncing utility which I'm using (isync) uses an integer. I'd appreciate it if someone could elaborate on what Dovecot uses and whether I need to convert one to the other (ie. after syncing with isync, do I need to convert it to work with Dovecot? Thanks.

2 1