From rick at havokmon.com Tue Jul 1 00:05:53 2014 From: rick at havokmon.com (Rick Romero) Date: Mon, 30 Jun 2014 19:05:53 -0500 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <1404171685.5018.15.camel@worklian> References: <53B1EA48.2020806@thinline.cz> <1404171685.5018.15.camel@worklian> Message-ID: <20140630190553.Horde.GLVIpw7MAQozVS0hfd8Vrw1@www.vfemail.net> Quoting Bob Miller : > Hi, >> Suggestions and warnings are most welcome. >> >> Thanks! >> >> Since you're using maildir, you might want to check rsync out as well, >> especially with --link-dest. In short, you call rsync on your backup >> machine like this: >> >> rsync --link-dest=previous-backup-dir source new-backup-dir > > check out rsnapshot.? Tried, tested, and true on my systems for > justshort of a decade now... rsnapshot was great until the filelists got too long for me.? Scripted ZFS snapshots &B send/receives were my solution. Rick From tim at timgws.com.au Tue Jul 1 00:46:24 2014 From: tim at timgws.com.au (Tim Groeneveld) Date: Tue, 01 Jul 2014 10:46:24 +1000 Subject: =?UTF-8?Q?Re:_Mailboxes_are_in_Maildir_format._Any_good_b?= =?UTF-8?Q?ackup_tips=3F_Had=C2=A0=C2=A0=C2=A0=C2=A0succe?= =?UTF-8?Q?ss_with_version_control=3F?= In-Reply-To: <1404171685.5018.15.camel@worklian> References: <1404171685.5018.15.camel@worklian> Message-ID: <146ef630b2c.-8084358786343568900.4857626717770059831@timgws.com.au> ---- On Tue, 01 Jul 2014 09:41:25 +1000 Bob Miller wrote ---- > check out rsnapshot. Tried, tested, and true on my systems for just > short of a decade now... +1 for rsnapshot. With the config file you can determine how many backups for different days that you want to keep. eg from the config file: retain hourly 6 retain daily 7 retain weekly 7 retain monthly 3 Add to the awesome config that it will save you disk space by hardlinking existing copies to previous files that were already backup up, while ensuring that each snapshot folder is easily restored. You will have yourself a perfect backup platform which is deployed in less time then it takes to have a relaxing bath! Also, a version control system is not a backup system. Check out this blog post: http://blog.codekills.net/2009/12/08/using-git-for-backup-is-asking-for-pain/ From nick.z.edwards at gmail.com Tue Jul 1 02:57:29 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Tue, 1 Jul 2014 12:57:29 +1000 Subject: postfix alias and dovecot quota In-Reply-To: <53B14BF6.3000206@thinline.cz> References: <5068E3FB-381B-4EDA-B40A-6D8943D797F9@numeezy.com> <53B14BF6.3000206@thinline.cz> Message-ID: On 6/30/14, Jiri Bourek wrote: > > > On 30.6.2014 12:33, Nick Edwards wrote: >> On 6/29/14, Alexandre Ellert wrote: >>> Le 29 juin 2014 ? 06:24, Nick Edwards a ?crit >>> : >>> >>>> it is the job of postfix to do this, aliases are just that, aliases of >>> >>>> the real mail account, they do not exist in real storage, else, they >>>> would not be alias. >>> >>> The problem i'm trying to solve is about dovecot capability to serve >>> quota >>> status via Postfix policy server protocol. >>> It works fine when the destination address is a real mailbox, but if it's >>> a >>> Postfix alias, then the email is not rejected because dovecot doesn't >>> know >>> this user. >>> Maybe it's a wrong idea to try to make Postfix alias visible to dovecot. >>> >>> Do you have another suggestion ? >> >> of course its wrong >> mail aliases are for MTA's *only* its not for dovecot (or any >> pop3/imap server), if postfix is not saying oh ok alias foo really >> goes to user bar, do we;ll check out bar's quota, status etc,, then ur >> postfix is foobarred somehow. >> > > I'm not completely sure about that. If you want to use Dovecot's > quota-status to reject message during SMTP session, Postfix' smtpd > process needs to do that and - to my knowledge - it's only able to pass > recipient address, not the aliases involved. > > I was looking for a solution to this few months ago as well. In the end > I created sort of policy service proxy between Postfix and Dovecot. The > proxy looks up aliases in database, converts them into real users and > asks Dovecot about those. Final result is then reported back to > postfix/smtpd. > http://dovecot.2317879.n4.nabble.com/Postfix-aliases-with-quota-status-service-td43511.html search for post from Ulrich Zehl From charlesc-dovecot at pyropus.ca Tue Jul 1 03:16:48 2014 From: charlesc-dovecot at pyropus.ca (Charles Cazabon) Date: Mon, 30 Jun 2014 21:16:48 -0600 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: References: Message-ID: <20140701031648.GA28666@pyropus.ca> deoren wrote: > > Right now I'm using LVM snapshots + tarballs for daily backups, but > I'd like to get better coverage for incremental changes that occur > throughout the day. The size of existing content is low, but (small) > changes are frequent. If you actually want to preserve those increments (as opposed to just keeping an rsync mirror up-to-date), I like rdiff-backup. It handles maildirs well because of the one-message-per-file design. Charles -- ----------------------------------------------------------------------- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ ----------------------------------------------------------------------- From infoomatic at gmx.at Tue Jul 1 08:48:49 2014 From: infoomatic at gmx.at (Infoomatic) Date: Tue, 1 Jul 2014 10:48:49 +0200 Subject: Aw: Re: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <20140701031648.GA28666@pyropus.ca> References: , <20140701031648.GA28666@pyropus.ca> Message-ID: > If you actually want to preserve those increments (as opposed to just keeping > an rsync mirror up-to-date), I like rdiff-backup. It handles maildirs well > because of the one-message-per-file design. Second that. It's great tool that keeps an actual sync (rsync-based) of the data-directory and the metadata (delta) in a seperate directory to restore data from any date. Alternatively, you might want to take a look at bacula, which was faster in most cases (development seems to have stalled, but there is a fork I have not had time to take a look at: bareos). However, I liked the rdiff-backup way because I can restore files via scp or rsync (most of my requests were like "please restore from yesterday") or if I want to restore data from a certain date I can use rdiff-backup from command line (bacula is much more complex, and you need the admin tool to restore files - rdiff-backup works from command line locally or via ssh/keyauth) hth, Robert From jerry at seibercom.net Tue Jul 1 11:10:16 2014 From: jerry at seibercom.net (Jerry) Date: Tue, 1 Jul 2014 07:10:16 -0400 Subject: Error receiving mail from postfix Message-ID: <20140701071016.5f97c28f@scorpio> When mail is relayed to dovecot from postfix, I am getting this error message in the maillog: Jul 1 07:05:19 scorpio postfix/pipe[45488]: 3h2jQl3Xldz3FMPc: to=, relay=dovecot, delay=0.16, delays=0.12/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Error: user user at domain.com: Error reading configuration: Invalid settings: postmaster_address setting not given lda: Fatal: Internal error occurred. Refer to server log for more information. ) Is this a Postfix problem or a Dovecot problem? # OS: FreeBSD 10.0-RELEASE-p3 amd64 ufs auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 digest-md5 ntlm auth_verbose = yes auth_verbose_passwords = plain log_path = /var/log/dovecot mail_location = maildir:/var/mail/vmail/seibercom/gerard managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = username_format=%u /usr/local/etc/dovecot/user/passwd driver = passwd-file } passdb { driver = pam } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/user/passwd driver = passwd-file } plugin { sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = References: <20140701031648.GA28666@pyropus.ca> Message-ID: <53B29F57.8010205@solutti.com.br> Em 01/07/14 00:16, Charles Cazabon escreveu: > deoren wrote: >> Right now I'm using LVM snapshots + tarballs for daily backups, but >> I'd like to get better coverage for incremental changes that occur >> throughout the day. The size of existing content is low, but (small) >> changes are frequent. > If you actually want to preserve those increments (as opposed to just keeping > an rsync mirror up-to-date), I like rdiff-backup. It handles maildirs well > because of the one-message-per-file design. > > Some may agree with me, some may disagree. But for my Maildir backups, i usually exclude the files "dovecot.index*". On the most common situations, you'll need to restore just one or other mailbox, so rebuilding those indexes wont kill the server. And by excluding these, i could save 10-15% of backup space on some cases with virtually no disadvantage. And on a worst case scenario, where i would need to restore the whole server and mailboxes, things will already be screwed, so knowing that dovecot would be harder on I/O for rebuilding the indexes will be just another problem :) -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, N?O mandem email gertrudes at solutti.com.br My SPAMTRAP, do not email it From bourek at thinline.cz Tue Jul 1 11:57:26 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 01 Jul 2014 13:57:26 +0200 Subject: Error receiving mail from postfix In-Reply-To: <20140701071016.5f97c28f@scorpio> References: <20140701071016.5f97c28f@scorpio> Message-ID: <53B2A226.5070404@thinline.cz> On 1.7.2014 13:10, Jerry wrote: > When mail is relayed to dovecot from postfix, I am getting this error message > in the maillog: > > Jul 1 07:05:19 scorpio postfix/pipe[45488]: 3h2jQl3Xldz3FMPc: to=, relay=dovecot, delay=0.16, delays=0.12/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Error: user user at domain.com: Error reading configuration: Invalid settings: postmaster_address setting not given lda: Fatal: Internal error occurred. Refer to server log for more information. ) > > Is this a Postfix problem or a Dovecot problem? > Misconfigured Dovecot, it's missing postmaster_address setting for LDA as the log message is telling you. From bourek at thinline.cz Tue Jul 1 12:06:06 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 01 Jul 2014 14:06:06 +0200 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B29F57.8010205@solutti.com.br> References: <20140701031648.GA28666@pyropus.ca> <53B29F57.8010205@solutti.com.br> Message-ID: <53B2A42E.1000607@thinline.cz> On 1.7.2014 13:45, Leonardo Rodrigues wrote: > Em 01/07/14 00:16, Charles Cazabon escreveu: >> deoren wrote: >>> Right now I'm using LVM snapshots + tarballs for daily backups, but >>> I'd like to get better coverage for incremental changes that occur >>> throughout the day. The size of existing content is low, but (small) >>> changes are frequent. >> If you actually want to preserve those increments (as opposed to just >> keeping >> an rsync mirror up-to-date), I like rdiff-backup. It handles maildirs >> well >> because of the one-message-per-file design. >> >> > > Some may agree with me, some may disagree. But for my Maildir > backups, i usually exclude the files "dovecot.index*". > > On the most common situations, you'll need to restore just one or > other mailbox, so rebuilding those indexes wont kill the server. And by > excluding these, i could save 10-15% of backup space on some cases with > virtually no disadvantage. > > And on a worst case scenario, where i would need to restore the > whole server and mailboxes, things will already be screwed, so knowing > that dovecot would be harder on I/O for rebuilding the indexes will be > just another problem :) > That really depends, rebuilding indexes can increase your downtime for hours, so it may be better to pay a bit for extra storage space instead of not being paid at all by your customers. From jerry at seibercom.net Tue Jul 1 12:31:55 2014 From: jerry at seibercom.net (Jerry) Date: Tue, 1 Jul 2014 08:31:55 -0400 Subject: Error receiving mail from postfix In-Reply-To: <53B2A226.5070404@thinline.cz> References: <20140701071016.5f97c28f@scorpio> <53B2A226.5070404@thinline.cz> Message-ID: <20140701083155.513c24ac@scorpio> On Tue, 01 Jul 2014 13:57:26 +0200, Jiri Bourek stated: > On 1.7.2014 13:10, Jerry wrote: > > When mail is relayed to dovecot from postfix, I am getting this error > > message in the maillog: > > > > Jul 1 07:05:19 scorpio postfix/pipe[45488]: 3h2jQl3Xldz3FMPc: > > to=, relay=dovecot, delay=0.16, delays=0.12/0.01/0/0.03, > > dsn=4.3.0, status=deferred (temporary failure. Command output: lda: > > Error: user user at domain.com: Error reading configuration: Invalid > > settings: postmaster_address setting not given lda: Fatal: Internal error > > occurred. Refer to server log for more information. ) > > > > Is this a Postfix problem or a Dovecot problem? > > > > Misconfigured Dovecot, it's missing postmaster_address setting for LDA > as the log message is telling you. Okay, perhaps a dump question, but exactly where am I suppose to enter that information? I have tried reading the documentation, but I must be missing it. -- jerry From leolistas at solutti.com.br Tue Jul 1 12:51:42 2014 From: leolistas at solutti.com.br (Leonardo Rodrigues) Date: Tue, 01 Jul 2014 09:51:42 -0300 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2A42E.1000607@thinline.cz> References: <20140701031648.GA28666@pyropus.ca> <53B29F57.8010205@solutti.com.br> <53B2A42E.1000607@thinline.cz> Message-ID: <53B2AEDE.4000907@solutti.com.br> Em 01/07/14 09:06, Jiri Bourek escreveu: > >> And on a worst case scenario, where i would need to restore the >> whole server and mailboxes, things will already be screwed, so knowing >> that dovecot would be harder on I/O for rebuilding the indexes will be >> just another problem :) >> > > That really depends, rebuilding indexes can increase your downtime for > hours, so it may be better to pay a bit for extra storage space > instead of not being paid at all by your customers. Anyway, for those not running a that critical system and can afford for an extra half hour of slowness, i really think the tip worths. And for those who, by any reason, cannot afford that extra storage space as well. But you're right, it's all a matter of calculating how critical your mission is and take the correct decisions for it. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, N?O mandem email gertrudes at solutti.com.br My SPAMTRAP, do not email it From eliezer at ngtech.co.il Tue Jul 1 13:06:49 2014 From: eliezer at ngtech.co.il (Eliezer Croitoru) Date: Tue, 01 Jul 2014 16:06:49 +0300 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2A42E.1000607@thinline.cz> References: <20140701031648.GA28666@pyropus.ca> <53B29F57.8010205@solutti.com.br> <53B2A42E.1000607@thinline.cz> Message-ID: <53B2B269.4040005@ngtech.co.il> On 07/01/2014 03:06 PM, Jiri Bourek wrote: > > That really depends, rebuilding indexes can increase your downtime for > hours, so it may be better to pay a bit for extra storage space instead > of not being paid at all by your customers. Building the index as far as I remember doesn't cost in downtime but in higher I/O usage which slows down the server. Eliezer From gheskett at wdtv.com Tue Jul 1 13:09:18 2014 From: gheskett at wdtv.com (Gene Heskett) Date: Tue, 1 Jul 2014 09:09:18 -0400 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2A42E.1000607@thinline.cz> References: <53B29F57.8010205@solutti.com.br> <53B2A42E.1000607@thinline.cz> Message-ID: <201407010909.18569.gheskett@wdtv.com> On Tuesday 01 July 2014 08:06:06 Jiri Bourek did opine And Gene did reply: > On 1.7.2014 13:45, Leonardo Rodrigues wrote: > > Em 01/07/14 00:16, Charles Cazabon escreveu: > >> deoren wrote: > >>> Right now I'm using LVM snapshots + tarballs for daily backups, but > >>> I'd like to get better coverage for incremental changes that occur > >>> throughout the day. The size of existing content is low, but > >>> (small) changes are frequent. > >> > >> If you actually want to preserve those increments (as opposed to > >> just keeping > >> an rsync mirror up-to-date), I like rdiff-backup. It handles > >> maildirs well > >> because of the one-message-per-file design. > >> > > Some may agree with me, some may disagree. But for my Maildir > > > > backups, i usually exclude the files "dovecot.index*". > > > > On the most common situations, you'll need to restore just one > > or > > > > other mailbox, so rebuilding those indexes wont kill the server. And > > by excluding these, i could save 10-15% of backup space on some > > cases with virtually no disadvantage. > > > > And on a worst case scenario, where i would need to restore the > > > > whole server and mailboxes, things will already be screwed, so > > knowing that dovecot would be harder on I/O for rebuilding the > > indexes will be just another problem :) > > That really depends, rebuilding indexes can increase your downtime for > hours, so it may be better to pay a bit for extra storage space instead > of not being paid at all by your customers. I would like to point out that in almost any situation referred to as backing up, if the system is active and processing mail flow during the backup (by any normal backup software), the database(the mail IOW) and the index, will be read and appended to the backup at separate times. Avoiding a duff index that requires a rebuild, is only going to be achieved if the mail system is disabled for the duration of the backup. That leads to the question of how, even if you have 2 systems so that incoming mail can still be handled, how do you go about putting the two back into sync before switching back to the primary server after the backup has been done. This seems to be a problem that has not been well addressed in any mail service scheme I am aware of. Here for instance, I could kill kmail's local fetching for the duration, which allows the fetchmail/procmail/sa/clam chain to continue to collect mail in /var/spool/mail, while the kmail corpus is being archived, and once that has been done, re-enable kmail's local pulling, that, if properly timed in the backup schedual would likely be at most 10 minutes of downtime for incoming (the corpus is around 20G's), because once thats been done, whatever is in /var/spool/mail can be pulled, sorted, and made available to the user in just a couple minutes. That could be accomplished by disabling the script driving inotifywait, but I don't have a clue how to incorporate that function into amanda, which I use here. Any such scheme is also likely to be highly personalized because of the surplus of ways to skin this cat called backing up. But I feel it is something that needs to be addressed, if only to prevent the lengthy delays when rebuilding the index. In kmails case, it doesn't take too long on a per folder basis, seems to be done as a background process the user is just barely aware of via keyboard response times. In fact, since I am on the amanda list too, I intend to ask if such a feature like establishing a handshake signal to achieve this could be obtained from amanda. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS From leolistas at solutti.com.br Tue Jul 1 13:55:37 2014 From: leolistas at solutti.com.br (Leonardo Rodrigues) Date: Tue, 01 Jul 2014 10:55:37 -0300 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2B269.4040005@ngtech.co.il> References: <20140701031648.GA28666@pyropus.ca> <53B29F57.8010205@solutti.com.br> <53B2A42E.1000607@thinline.cz> <53B2B269.4040005@ngtech.co.il> Message-ID: <53B2BDD9.6020605@solutti.com.br> Em 01/07/14 10:06, Eliezer Croitoru escreveu: > On 07/01/2014 03:06 PM, Jiri Bourek wrote: >> >> That really depends, rebuilding indexes can increase your downtime for >> hours, so it may be better to pay a bit for extra storage space instead >> of not being paid at all by your customers. > Building the index as far as I remember doesn't cost in downtime but > in higher I/O usage which slows down the server. > That's my knowledge as well. Rebuilt of indexes are done on-the-fly when the account is accessed and, thus, there's no downtime involved on that. Of course, with lots of big accounts and lots of initial accesses on the scenario where ALL accounts were restored without indexes, the I/O increase can be so high that the server will be basically unresponsive. That can happen for sure. But on the more common case, which will be restoring just a few accounts, that I/O increase will probably be unnoticable. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, N?O mandem email gertrudes at solutti.com.br My SPAMTRAP, do not email it From bourek at thinline.cz Tue Jul 1 14:08:40 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 01 Jul 2014 16:08:40 +0200 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2BDD9.6020605@solutti.com.br> References: <20140701031648.GA28666@pyropus.ca> <53B29F57.8010205@solutti.com.br> <53B2A42E.1000607@thinline.cz> <53B2B269.4040005@ngtech.co.il> <53B2BDD9.6020605@solutti.com.br> Message-ID: <53B2C0E8.9070306@thinline.cz> On 1.7.2014 15:55, Leonardo Rodrigues wrote: > Em 01/07/14 10:06, Eliezer Croitoru escreveu: >> On 07/01/2014 03:06 PM, Jiri Bourek wrote: >>> >>> That really depends, rebuilding indexes can increase your downtime for >>> hours, so it may be better to pay a bit for extra storage space instead >>> of not being paid at all by your customers. >> Building the index as far as I remember doesn't cost in downtime but >> in higher I/O usage which slows down the server. >> > > That's my knowledge as well. Rebuilt of indexes are done on-the-fly > when the account is accessed and, thus, there's no downtime involved on > that. > > Of course, with lots of big accounts and lots of initial accesses > on the scenario where ALL accounts were restored without indexes, the > I/O increase can be so high that the server will be basically > unresponsive. That can happen for sure. Exactly my point. I saw that happen once and the slowdown effectively became a downtime. > > But on the more common case, which will be restoring just a few > accounts, that I/O increase will probably be unnoticable. > > From jost+lists at dimejo.at Tue Jul 1 15:00:12 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Tue, 01 Jul 2014 17:00:12 +0200 Subject: Error receiving mail from postfix In-Reply-To: <20140701083155.513c24ac@scorpio> References: <20140701071016.5f97c28f@scorpio> <53B2A226.5070404@thinline.cz> <20140701083155.513c24ac@scorpio> Message-ID: <53B2CCFC.4080702@dimejo.at> Am 01.07.2014 14:31, schrieb Jerry: > On Tue, 01 Jul 2014 13:57:26 +0200, Jiri Bourek stated: > >> On 1.7.2014 13:10, Jerry wrote: >>> When mail is relayed to dovecot from postfix, I am getting this error >>> message in the maillog: >>> >>> Jul 1 07:05:19 scorpio postfix/pipe[45488]: 3h2jQl3Xldz3FMPc: >>> to=, relay=dovecot, delay=0.16, delays=0.12/0.01/0/0.03, >>> dsn=4.3.0, status=deferred (temporary failure. Command output: lda: >>> Error: user user at domain.com: Error reading configuration: Invalid >>> settings: postmaster_address setting not given lda: Fatal: Internal error >>> occurred. Refer to server log for more information. ) >>> >>> Is this a Postfix problem or a Dovecot problem? >>> >> >> Misconfigured Dovecot, it's missing postmaster_address setting for LDA >> as the log message is telling you. > > Okay, perhaps a dump question, but exactly where am I suppose to enter that > information? I have tried reading the documentation, but I must be missing it. > As Edgar Pettijohn has written on the Postfix mailing list this setting should be found in /usr/local/etc/dovecot/conf.d/15-lda.conf -- Alex JOST From bind at enas.net Tue Jul 1 15:03:11 2014 From: bind at enas.net (Urban Loesch) Date: Tue, 01 Jul 2014 17:03:11 +0200 Subject: Crash in service imap with version 2.2.13 In-Reply-To: <53A9397F.6060008@enas.net> References: <53A9397F.6060008@enas.net> Message-ID: <53B2CDAF.2000908@enas.net> Hi, I did some more debugging and now I can reproduce the crash with one of the affected mailboxes: I made a test with telnet: ... telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. L LOGIN "user at domain.net" "secretpassword" L OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE COMPRESS=DEFLATE QUOTA] Logged in 00000003 STATUS INBOX (MESSAGES RECENT UNSEEN UIDNEXT UIDVALIDITY) * STATUS INBOX (MESSAGES 3 RECENT 0 UIDNEXT 10255 UIDVALIDITY 1309600294 UNSEEN 0) 00000003 OK Status completed. 00000004 NOOP 00000004 OK NOOP completed. 00000005 EXAMINE INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 3 EXISTS * 0 RECENT * OK [UIDVALIDITY 1309600294] UIDs valid * OK [UIDNEXT 10255] Predicted next UID 00000005 OK [READ-ONLY] Examine completed (0.001 secs). 00000006 UID THREAD REFERENCES US-ASCII ALL Connection closed by foreign host. ... As you can see dovecots segfaults one the imap command "00000006 UID THREAD REFERENCES US-ASCII ALL". during this session I made an strace, too: ... 16:01:30.589383 epoll_wait(11, {{EPOLLIN, {u32=15105616, u64=15105616}}}, 5, 1793648) = 1 16:01:42.604817 read(7, "00000003 STATUS INBOX (MESSAGES "..., 8192) = 68 16:01:42.604997 open("/proc/meminfo", O_RDONLY) = 4 16:01:42.605180 fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 16:01:42.605453 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f07e45df000 16:01:42.605732 read(4, "MemTotal: 8388608 kB\nMemF"..., 1024) = 1024 16:01:42.605840 close(4) = 0 16:01:42.605866 munmap(0x7f07e45df000, 4096) = 0 16:01:42.605965 stat("/home/vmail/domain.net/user/mailboxes/INBOX/dbox-Mails", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:42.606013 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:42.606050 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:42.606093 stat("/home/vmail/domain.net/user/mailboxes/INBOX", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:42.606134 open("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.log", O_RDWR|O_APPEND) = 4 16:01:42.606164 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:42.606195 brk(0xea7000) = 0xea7000 16:01:42.606222 pread(4, "\1\2(\0$\352\16N{\0\0\0z\0\0\0\304\200\0\0\t\362\261S\0\0\0\0\0\0\0\0"..., 3984, 0) = 3984 16:01:42.606263 open("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index", O_RDWR) = 12 16:01:42.606290 fstat(12, {st_mode=S_IFREG|0600, st_size=516, ...}) = 0 16:01:42.606321 pread(12, "\7\2x\0(\1\0\0,\0\0\0\1\0\0\0$\352\16N\0\0\0\0&\352\16N\5(\0\0"..., 8192, 0) = 516 16:01:42.606369 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:42.606476 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:42.606510 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:42.606544 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:42.606576 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:42.606648 setsockopt(7, SOL_TCP, TCP_CORK, [1], 4) = 0 16:01:42.606674 write(7, "* STATUS INBOX (MESSAGES 3 RECEN"..., 115) = 115 16:01:42.606699 setsockopt(7, SOL_TCP, TCP_CORK, [0], 4) = 0 16:01:42.606798 epoll_wait(11, {}, 5, 5000) = 0 16:01:47.609442 epoll_wait(11, {{EPOLLIN, {u32=15105616, u64=15105616}}}, 5, 5000) = 1 16:01:48.193526 read(7, "00000004 NOOP\r\n", 8124) = 15 16:01:48.193707 setsockopt(7, SOL_TCP, TCP_CORK, [1], 4) = 0 16:01:48.193745 write(7, "00000004 OK NOOP completed.\r\n", 29) = 29 16:01:48.193940 setsockopt(7, SOL_TCP, TCP_CORK, [0], 4) = 0 16:01:48.194084 epoll_wait(11, {}, 5, 4415) = 0 16:01:52.609478 close(12) = 0 16:01:52.609543 close(4) = 0 16:01:52.609618 epoll_wait(11, {{EPOLLIN, {u32=15105616, u64=15105616}}}, 5, 1795584) = 1 16:01:52.685853 read(7, "00000005 EXAMINE INBOX\r\n", 8109) = 24 16:01:52.686081 brk(0xea5000) = 0xea5000 16:01:52.686282 stat("/home/vmail/domain.net/user/mailboxes/INBOX/dbox-Mails", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:52.686557 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:52.686611 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:52.686654 stat("/home/vmail/domain.net/user/mailboxes/INBOX", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 16:01:52.686691 open("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.log", O_RDWR|O_APPEND) = 4 16:01:52.686720 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:52.686750 pread(4, "\1\2(\0$\352\16N{\0\0\0z\0\0\0\304\200\0\0\t\362\261S\0\0\0\0\0\0\0\0"..., 3984, 0) = 3984 16:01:52.686786 open("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index", O_RDWR) = 12 16:01:52.686821 fstat(12, {st_mode=S_IFREG|0600, st_size=516, ...}) = 0 16:01:52.686850 pread(12, "\7\2x\0(\1\0\0,\0\0\0\1\0\0\0$\352\16N\0\0\0\0&\352\16N\5(\0\0"..., 8192, 0) = 516 16:01:52.686887 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:52.686968 stat("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.log", {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:52.687002 fstat(4, {st_mode=S_IFREG|0600, st_size=3984, ...}) = 0 16:01:52.687056 setsockopt(7, SOL_TCP, TCP_CORK, [1], 4) = 0 16:01:52.687079 write(7, "* FLAGS (\\Answered \\Flagged \\Del"..., 261) = 261 16:01:52.687105 setsockopt(7, SOL_TCP, TCP_CORK, [0], 4) = 0 16:01:52.687207 epoll_wait(11, {{EPOLLIN, {u32=15105616, u64=15105616}}}, 5, 1800000) = 1 16:02:04.438436 read(7, "00000006 UID THREAD REFERENCES U"..., 8085) = 45 16:02:04.438728 open("/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.thread", O_RDWR) = 13 16:02:04.438808 fstat(13, {st_mode=S_IFREG|0600, st_size=136, ...}) = 0 16:02:04.438921 pread(13, "\1\0\0\0&\352\16N\200\200\200\276\242M\0\1 \343z\1\0\0\0a\0\235\204\246\373\2\0\0"..., 8192, 0) = 136 ... Deleting the "/home/dovecotindex/domain.net/user/mailboxes/INBOX/dovecot.index.thread" file resolves the problem, but I'm not shure if this is the correct solution. I mean, if I have to delete all "dovecot.index.thread" files on my servers after upgrading to Dovecot 2.2.13 and I can't say if the problem comes back. Are there some changes between version 2.1.15 and 2.2.13 which affects the dovecot indexes? I can't find nothing in the wiki to this. As I just said, the probkem only happens with Horde Webmail. Thanks Urban Am 24.06.2014 10:40, schrieb Urban Loesch: > > Hi, > > yesterday I upgraded to version 2.2.13 under Debian Squeeze. > > Since today morning sometimes my logfile shows the folling error: > > .. > Jun 24 10:14:16 mailstore dovecot: imap(user at domain.net pid:23434 session:): Fatal: master: service(imap): child 23434 killed with > signal 11 (core dumped) > ... > > The kernel error log shows: > ... > Jun 24 10:14:16 mailstore kernel: [13959701.899726] imap[23434]: segfault at 1012acec0 ip 00007f7dd89b5e52 sp 00007ffffd33d9b0 error 4 in > libdovecot-storage.so.0.0.0[7f7dd88ed000+10d000] > ... > > This seems only to happen in conjunction with Horde Webmail. Other IMAP clients aren't affected. > > I made a backtrace: > > -----> start backtrace <----- > Core was generated by `dovecot/imap'. > Program terminated with signal 11, Segmentation fault. > #0 mail_index_strmap_uid_exists (ctx=0x7ffffd33d9f0, uid=8442) at mail-index-strmap.c:395 > 395 mail-index-strmap.c: No such file or directory. > in mail-index-strmap.c > (gdb) bt full > #0 mail_index_strmap_uid_exists (ctx=0x7ffffd33d9f0, uid=8442) at mail-index-strmap.c:395 > rec = 0x1012acec0 > #1 0x00007f7dd89b79ab in mail_index_strmap_view_renumber (_sync=) at mail-index-strmap.c:842 > ctx = {view = 0x12b2d80, input = 0x0, end_offset = 0, highest_str_idx = 0, uid_lookup_seq = 0, lost_expunged_uid = 0, data = 0x0, end = 0x0, > str_idx_base = 0x0, rec = {uid = 0, ref_index = 0, str_idx = 0}, next_ref_index = 0, > rec_size = 0, too_large_uids = 0} > str_idx = 0 > count = 1 > ret = > prev_uid = 8442 > i = 0 > dest = 0 > count2 = > #2 mail_index_strmap_write (_sync=) at mail-index-strmap.c:1189 > ret = > #3 mail_index_strmap_view_sync_commit (_sync=) at mail-index-strmap.c:1236 > sync = > view = > #4 0x00007f7dd899fc23 in mail_thread_index_map_build (box=, args=, ctx_r=) at > index-thread.c:332 > last_uid = 8442 > search_ctx = > mail = > seq1 = 0 > tbox = 0x12af2e0 > headers_ctx = 0x12b7e50 > search_args = > seq2 = > wanted_headers = {0x7f7dd89d8542 "message-id", 0x7f7dd89d9f96 "in-reply-to", 0x7f7dd89d9fa2 "references", 0x0} > #5 mail_thread_init (box=, args=, ctx_r=) at index-thread.c:569 > tbox = 0x12af2e0 > ctx = 0x12afc10 > search_ctx = 0x12b2b20 > ret = > __FUNCTION__ = "mail_thread_init" > #6 0x0000000000414ef3 in imap_thread (cmd=0x12a7eb0) at cmd-thread.c:90 > ctx = > str = 0x12afbd0 > #7 cmd_thread (cmd=0x12a7eb0) at cmd-thread.c:281 > client = 0x12a72b0 > thread_type = MAIL_THREAD_REFERENCES > sargs = 0x12b04a0 > args = 0x128faf8 > charset = 0x128fc18 "US-ASCII" > str = 0x128fc08 "REFERENCES" > ret = > #8 0x00000000004181fd in command_exec (cmd=0x12a7eb0) at imap-commands.c:158 > hook = 0x128d110 > ret = > #9 0x00000000004172e0 in client_command_input (cmd=0x12a7eb0) at imap-client.c:778 > client = 0x12a72b0 > command = > __FUNCTION__ = "client_command_input" > #10 0x0000000000417376 in client_command_input (cmd=0x12a7eb0) at imap-client.c:839 > client = 0x12a72b0 > command = 0x12acd00 > __FUNCTION__ = "client_command_input" > #11 0x000000000041765d in client_handle_next_command (client=0x12a72b0) at imap-client.c:877 > No locals. > #12 client_handle_input (client=0x12a72b0) at imap-client.c:889 > _data_stack_cur_id = 3 > ret = 80 > remove_io = > handled_commands = false > ---Type to continue, or q to quit--- > __FUNCTION__ = "client_handle_input" > #13 0x00000000004179ef in client_input (client=0x12a72b0) at imap-client.c:931 > cmd = > output = 0x12a7cf0 > bytes = > __FUNCTION__ = "client_input" > #14 0x00007f7dd869808e in io_loop_call_io (io=0x12a7dc0) at ioloop.c:441 > ioloop = 0x128c760 > t_id = 2 > __FUNCTION__ = "io_loop_call_io" > #15 0x00007f7dd869923f in io_loop_handler_run_internal (ioloop=) at ioloop-epoll.c:220 > ctx = 0x128d3f0 > event = 0x128e260 > list = 0x128ee50 > io = 0x12acde0 > tv = {tv_sec = 4, tv_usec = 996567} > msecs = > ret = 1 > i = 0 > call = false > __FUNCTION__ = "io_loop_handler_run_internal" > #16 0x00007f7dd8698119 in io_loop_handler_run (ioloop=0x12acde0) at ioloop.c:488 > No locals. > #17 0x00007f7dd86981a8 in io_loop_run (ioloop=0x128c760) at ioloop.c:465 > __FUNCTION__ = "io_loop_run" > #18 0x00007f7dd8645153 in master_service_run (service=0x128c5f0, callback=0x20fa) at master-service.c:566 > No locals. > #19 0x0000000000420f87 in main (argc=1, argv=0x128c3a0) at main.c:410 > set_roots = {0x428fc0, 0x0} > login_set = {auth_socket_path = 0x1284050 "\210@(\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x421180 > , failure_callback = 0x421120 , > request_auth_token = 1} > service_flags = > storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT > username = 0x0 > c = > > -----> end backtrace <----- > > Have you any idea how I can solve this? > > Many thanks > Urban Loesch > > doveconf -n: > > ... > # 2.2.13 (38cd37cea8b1): /etc/dovecot/dovecot.conf > # OS: Linux 3.4.67-vs2.3.3.9-rol-em64t-efigpt x86_64 Debian 6.0.9 ext4 > auth_cache_negative_ttl = 0 > auth_cache_size = 80 M > auth_cache_ttl = 1 weeks > auth_mechanisms = plain login > auth_verbose = yes > default_client_limit = 2000 > deliver_log_format = msgid=%m: %$ %p %w > disable_plaintext_auth = no > login_trusted_networks = INTERNAL_IPS > mail_gid = mailstore > mail_location = mdbox:/home/vmail/%d/%n:INDEX=/home/dovecotindex/%d/%n > mail_log_prefix = "%s(%u pid:%p session:<%{session}>): " > mail_plugins = " quota mail_log notify zlib" > mail_uid = mailstore > mailbox_idle_check_interval = 1 mins > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags > copy include variables body enotify environment mailbox date ihave duplicate imapflags notify > mdbox_rotate_size = 10 M > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Items" { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > separator = / > type = private > } > passdb { > args = /etc/dovecot/dovecot-sql-account.conf > driver = sql > } > plugin { > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mailbox_create append > mail_log_fields = uid box msgid size from > mail_log_group_events = no > quota = dict:Storage used::file:%h/dovecot-quota > quota_rule2 = Trash:storage=+100M > quota_warning = storage=95%% quota-warning 95 %u > quota_warning2 = storage=80%% quota-warning 80 %u > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > sieve_extensions = +notify +imapflags > sieve_max_redirects = 15 > zlib_save = gz > zlib_save_level = 9 > } > protocols = imap pop3 lmtp sieve > service auth-worker { > service_count = 0 > vsz_limit = 512 M > } > service auth { > unix_listener auth-userdb { > group = mailstore > mode = 0660 > user = root > } > } > service imap-login { > inet_listener imap { > port = 143 > } > process_limit = 256 > process_min_avail = 50 > service_count = 1 > } > service imap { > process_limit = 2048 > process_min_avail = 50 > service_count = 1 > vsz_limit = 512 M > } > service lmtp { > inet_listener lmtp { > address = * > port = 24 > } > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0666 > user = postfix > } > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > process_limit = 256 > process_min_avail = 25 > service_count = 1 > } > service pop3 { > process_limit = 256 > process_min_avail = 25 > service_count = 1 > } > service quota-warning { > executable = script /usr/local/rol/dovecot/quota-warning.sh > unix_listener quota-warning { > user = mailstore > } > user = mailstore > } > ssl = no > ssl_cert = ssl_key = userdb { > args = /etc/dovecot/dovecot-sql-account.conf > driver = sql > } > protocol lmtp { > mail_fsync = optimized > mail_plugins = " quota mail_log notify zlib sieve zlib" > } > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > imap_id_log = * > imap_logout_format = bytes=%i/%o session=<%{session}> > mail_max_userip_connections = 40 > mail_plugins = " quota mail_log notify zlib imap_quota imap_zlib" > } > protocol pop3 { > mail_plugins = " quota mail_log notify zlib" > pop3_logout_format = bytes_sent=%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s uidl_hash=%u session=<%{session}> > } > > .... > From gheskett at wdtv.com Tue Jul 1 15:11:49 2014 From: gheskett at wdtv.com (Gene Heskett) Date: Tue, 1 Jul 2014 11:11:49 -0400 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2BDD9.6020605@solutti.com.br> References: <53B2B269.4040005@ngtech.co.il> <53B2BDD9.6020605@solutti.com.br> Message-ID: <201407011111.49456.gheskett@wdtv.com> On Tuesday 01 July 2014 09:55:37 Leonardo Rodrigues did opine And Gene did reply: > Em 01/07/14 10:06, Eliezer Croitoru escreveu: > > On 07/01/2014 03:06 PM, Jiri Bourek wrote: > >> That really depends, rebuilding indexes can increase your downtime > >> for hours, so it may be better to pay a bit for extra storage space > >> instead of not being paid at all by your customers. > > > > Building the index as far as I remember doesn't cost in downtime but > > in higher I/O usage which slows down the server. > > That's my knowledge as well. Rebuilt of indexes are done > on-the-fly when the account is accessed and, thus, there's no downtime > involved on that. > > Of course, with lots of big accounts and lots of initial accesses > on the scenario where ALL accounts were restored without indexes, the > I/O increase can be so high that the server will be basically > unresponsive. That can happen for sure. > > But on the more common case, which will be restoring just a few > accounts, that I/O increase will probably be unnoticable. And I just got a reply from the amanda list, it IS possible to construct a "dumptype" to do that via callable scripts, see: No clue if bacula or the others are that well equipt. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS From lists at wiesinger.com Tue Jul 1 15:53:49 2014 From: lists at wiesinger.com (Gerhard Wiesinger) Date: Tue, 01 Jul 2014 17:53:49 +0200 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: References: Message-ID: <53B2D98D.20101@wiesinger.com> On 01.07.2014 00:28, deoren wrote: > I'm still pretty new to running a mail server, but one thing I've come > to appreciate over the years is a good backup strategy. Since I have > always run my own servers for practice and for personal use I don't > have access to Enterprise backup solutions. Because of that I usually > just fall back to scripts and tarballs and offload the content on a > regular basis. > > Right now I'm using LVM snapshots + tarballs for daily backups, but > I'd like to get better coverage for incremental changes that occur > throughout the day. The size of existing content is low, but (small) > changes are frequent. > > I went with Maildir format because based on my reading it is referred > to as time tested and corruption resistant. Because individual emails > are stored as separate files this also leads me to believe that a > version control system (Git, SVN) would allow for easy point in time > restores. > > I'm also going to research the GNU tar utility's support for > incremental archives as that sounds promising. Hello Deoren, I can recommend dirvish (http://www.dirvish.org/). Supports incremental backups with aging strategy and hardlinks and very efficient storage. Works for years for me. In the background rsync is used for syncing the backups but with a high level interface. Ciao, Gerhard From dovecot.fdop at tagged.lorens.org Tue Jul 1 16:54:14 2014 From: dovecot.fdop at tagged.lorens.org (Lorens Kockum) Date: Tue, 1 Jul 2014 18:54:14 +0200 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B2A42E.1000607@thinline.cz> References: <20140701031648.GA28666@pyropus.ca> <53B29F57.8010205@solutti.com.br> <53B2A42E.1000607@thinline.cz> Message-ID: <20140701165413.GA4640@tagged.lorens.org> On Tue, Jul 01, 2014 at 02:06:06PM +0200, Jiri Bourek wrote: > On 1.7.2014 13:45, Leonardo Rodrigues wrote: > > i usually exclude the files "dovecot.index*". > > [...] > > On the most common situations, you'll need to restore just one or > > other mailbox, so rebuilding those indexes wont kill the server. And by > > excluding these, i could save 10-15% of backup space on some cases with > > virtually no disadvantage. > > > That really depends, rebuilding indexes can increase your downtime > for hours, so it may be better to pay a bit for extra storage space > instead of not being paid at all by your customers. Easy to answer that one. You are talking about two different situations, and the solutions are different. The usual situation is one person having lost mail (whether one mail or all his mail), the catastrophe situation is when you as admin lose everything. To cover both cases, keep the mail files for however long you want/need/can, but only keep the most up-to-date instance of the dovecot index files (maybe two if you want to protect against corruption). That should be a lot less than 10%. I see no reason you'd need an index older than the last known valid index even for one client, and if it's just one client, then 1) reconstructing can't be a big problem 2) it's just one client. What I practise and recommend (not only for mail): - for the catastrophe scenario, keep at least a working day of snapshots. Both restore speed and completeness mandate it, and my (maybe expensive) filers (or ZFS servers) can mirror them off-site. Integrate that cost into the disk cost as you certainly do with RAID. (Yes, that's yet another reason you get the "Waaah my IT guys tell me that disk space costs $xxxx per TB but I can get a TB USB drive at WhateverMart for 1/xx of that price!!!) - for the individual restores, backup non-trivially-reconstructable files for a longer term to slower/cheaper-per-TB media, eventually compressed, deduplicated, and/or offline. Your cost depends on the data size, your retention, the compression rate, your redundancy and your churn: it's backup. Since you already have snapshots, you can make your backup from your snapshots to preserve consistency (and since you need snapshots for consistency, why not keep a working day or so hanging around, right?). Bonus points for keeping recent backups on faster storage, and staging backups older than a week or so to cheap storage. The only scenario I can see where I would need to very urgently restore any significant percentage of user files to anything but the most recent version would be some kind of not instantly detected corruption or admin error, thus the several snapshots. HTH, HAND From asai at globalchangemusic.org Tue Jul 1 19:02:12 2014 From: asai at globalchangemusic.org (Asai) Date: Tue, 01 Jul 2014 12:02:12 -0700 Subject: Android Sync Doesn't Work Too Good Message-ID: <53B305B4.8020505@globalchangemusic.org> Greetings, I'm getting reports from a user who's reading and deleting mail on Thunderbird, but read flags and deletions don't show up in his Android phone. He's using the native Android mail app with the newest Android OS. My question is, where do I start with troubleshooting this kind of issue? Thanks for anyone's insight here. We're using Dovecot 2.2.13. -- --Asai From thomas-lists at nybeta.com Tue Jul 1 19:55:32 2014 From: thomas-lists at nybeta.com (Thomas Harold) Date: Tue, 01 Jul 2014 15:55:32 -0400 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: References: Message-ID: <53B31234.2020108@nybeta.com> On 6/30/2014 6:28 PM, deoren wrote: > I'm still pretty new to running a mail server, but one thing I've come > to appreciate over the years is a good backup strategy. Since I have > always run my own servers for practice and for personal use I don't have > access to Enterprise backup solutions. Because of that I usually just > fall back to scripts and tarballs and offload the content on a regular > basis. > LVM snapshots of the file system combined with rdiff-backup to a second server. The main advantages over tar/rsync: - Deltas instead of entire file. Plus deltas are compressed. - It handles lots and lots of files well. - You can easily age off older deltas. Not hard to keep 26W or 52W of daily or a few-times-per-day backups. - Metadata such as file permissions / owner / group are stored in regular files in the rdiff-backup target directory, so the destination file system where you store the rdiff-backup files does not matter much. - Files are stored along with a SHA1 hash, making it possible to detect bitrot in your backups. Downsides: - Restoring a file more then 10 or 20 deltas old requires a lot of disk activity (putting /tmp on a SSD helps a lot) Suggestions: - Each mailbox folder should be its own rdiff-backup target. That allows you to only backup mailbox folders which have changed in last N hours/days. It also means that if things go pear-shaped with rdiff-backup, only that one backup target is at risk. - Put /tmp on a SSD, especially if you run rdiff-backup "verify" and validate more then 1-2 revisions into the past. - Once you have your rdiff-backup directories on another server it is trivial to LVM snapshot that and then rsync to either a USB drive or offsite server (or both). The rdiff-backup directory structure is very rsync-friendly. - If you're going to do hourly backups, have (2) rdiff-backup locations. One that deals with the hourly backups and has a short retention cycle of only 3-4 weeks. Another location that deals with daily backups and has a 55W retention cycle. That way you can restore to an hour within the past 3-4 weeks, or any day within the past 55W. From thomas-lists at nybeta.com Tue Jul 1 19:59:09 2014 From: thomas-lists at nybeta.com (Thomas Harold) Date: Tue, 01 Jul 2014 15:59:09 -0400 Subject: Aw: Re: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: References: , <20140701031648.GA28666@pyropus.ca> Message-ID: <53B3130D.8010209@nybeta.com> On 7/1/2014 4:48 AM, Infoomatic wrote: >> If you actually want to preserve those increments (as opposed to just keeping >> an rsync mirror up-to-date), I like rdiff-backup. It handles maildirs well >> because of the one-message-per-file design. > Second that. It's great tool that keeps an actual sync > (rsync-based) of the data-directory and the metadata (delta) in a > seperate directory to restore data from any date. > > Alternatively, you might want to take a look at bacula, which was faster > in most cases (development seems to have stalled, but there is a fork I > have not had time to take a look at: bareos). However, I liked the > rdiff-backup way because I can restore files via scp or rsync (most of > my requests were like "please restore from yesterday") or if I want to > restore data from a certain date I can use rdiff-backup from command > line (bacula is much more complex, and you need the admin tool to > restore files - rdiff-backup works from command line locally or via ssh/keyauth) > I looked at Bacula/Amanda - which are great systems if your focus is tape or backup to disk. But neither of them had good support for "backup to disk, rsync to offsite". rsnapshot / rdiff-backup are just better at creating backups which are rsync-friendly over the WAN. Which also means you can easily push the backups to USB drives without having to wait hours and hours. From rs at sys4.de Tue Jul 1 20:04:25 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 01 Jul 2014 22:04:25 +0200 Subject: Android Sync Doesn't Work Too Good In-Reply-To: <53B305B4.8020505@globalchangemusic.org> References: <53B305B4.8020505@globalchangemusic.org> Message-ID: <53B31449.2010205@sys4.de> Am 01.07.2014 21:02, schrieb Asai: > Greetings, > > I'm getting reports from a user who's reading and deleting mail on > Thunderbird, but read flags and deletions don't show up in his Android > phone. He's using the native Android mail app with the newest Android OS. in imap mode ? > > My question is, where do I start with troubleshooting this kind of > issue? Thanks for anyone's insight here. We're using Dovecot 2.2.13. > look at the verbose logs, and dont expect android app to be a good imap client ( i never tried it that kind ) , better use k9 Mail with imap on Android https://code.google.com/p/k9mail/ Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From asai at globalchangemusic.org Tue Jul 1 20:26:05 2014 From: asai at globalchangemusic.org (Asai) Date: Tue, 01 Jul 2014 13:26:05 -0700 Subject: Android Sync Doesn't Work Too Good In-Reply-To: <53B31449.2010205@sys4.de> References: <53B305B4.8020505@globalchangemusic.org> <53B31449.2010205@sys4.de> Message-ID: <53B3195D.9000407@globalchangemusic.org> > Am 01.07.2014 21:02, schrieb Asai: >> Greetings, >> >> I'm getting reports from a user who's reading and deleting mail on >> Thunderbird, but read flags and deletions don't show up in his Android >> phone. He's using the native Android mail app with the newest Android OS. > in imap mode ? Yes > >> My question is, where do I start with troubleshooting this kind of >> issue? Thanks for anyone's insight here. We're using Dovecot 2.2.13. >> > look at the verbose logs, and dont expect android app to be a good imap > client > ( i never tried it that kind ) , better use k9 Mail with imap on Android > > > https://code.google.com/p/k9mail/ > Thanks, Robert. This user did once use K9, but they like the native app better... I suggested to them that they double check the syncing in K9 rather than native. From ler at lerctr.org Tue Jul 1 15:32:18 2014 From: ler at lerctr.org (Larry Rosenman) Date: Tue, 1 Jul 2014 10:32:18 -0500 Subject: indexer failure: lucene: while doing doveadm commands Message-ID: <20140701153217.GA58803@thebighonker.lerctr.org> I have the following script: #!/bin/sh PATH=$PATH:/usr/local/bin #Expects to be run after midnight on the first of the month # to archive all the previous months mail #Date Run: TODAY=`date "+%Y-%m-%d"` #last month in YYYY/MM YEAR_LAST_MONTH=`date -v-1d "+%Y/%m"` #1st of last month as 01-Mon-YYYY FIRST_LAST_MONTH=`date -v-1d "+01-%b-%Y"` echo 'TODAY=' ${TODAY} echo 'YEAR_LAST_MONTH=' ${YEAR_LAST_MONTH} echo 'FIRST_LAST_MONTH=' ${FIRST_LAST_MONTH} # get a list of all the mailboxes with at least one real message doveadm -f table mailbox status vsize \* 2>/dev/null | \ awk '{if ($2 > 0) print $1}' >/tmp/ler-mailbox-list.$$ 2>/dev/null # archive all the mails for i in `cat /tmp/ler-mailbox-list.$$` do echo `date` start ${i} doveadm mailbox create \#ARCHIVE/${YEAR_LAST_MONTH}/${i} doveadm -f tab mailbox status messages ${i} doveadm move \#ARCHIVE/${YEAR_LAST_MONTH}/${i} mailbox \ ${i} BEFORE ${TODAY} SINCE ${FIRST_LAST_MONTH} doveadm -f tab mailbox status messages ${i} echo `date` done ${i} done rm /tmp/ler-mailbox-list.$$ It runs at 00:30:00 local time on the first of the month. While it was running I got: Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:00 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20538 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:00 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20683 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:00 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20693 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:01 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:01 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:01 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:01 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20700 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:01 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:01 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:01 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:01 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20707 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:02 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:02 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:02 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:02 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20717 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:08 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:08 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:08 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 7 requests for ler Jul 1 00:30:08 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20719 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:16 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:16 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:16 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 10 requests for ler Jul 1 00:30:16 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20753 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:20 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:20 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:20 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 10 requests for ler Jul 1 00:30:20 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20797 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:21 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:21 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:21 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:21 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20841 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:24 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 13 requests for ler Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20842 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:24 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20905 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:24 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:24 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20912 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:25 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:25 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:25 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:25 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20919 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:25 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:25 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:25 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:25 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20926 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:27 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:27 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:27 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:27 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20936 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:30 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:30 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:30 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 4 requests for ler Jul 1 00:30:30 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20939 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:31 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20964 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:31 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20971 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:31 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:31 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20978 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:32 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:32 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:32 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:32 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20985 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:34 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:34 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:34 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 6 requests for ler Jul 1 00:30:34 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 20986 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:36 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:36 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:36 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 4 requests for ler Jul 1 00:30:36 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21013 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:36 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:36 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:36 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:36 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21039 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:38 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:38 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:38 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 3 requests for ler Jul 1 00:30:38 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21040 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:40 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:40 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:40 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:40 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21075 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:42 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:42 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:42 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 2 requests for ler Jul 1 00:30:42 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21076 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:43 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:43 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:43 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:43 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21092 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:44 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:44 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:44 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 4 requests for ler Jul 1 00:30:44 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21094 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) Jul 1 00:30:45 thebighonker dovecot: indexer-worker(ler): Indexed 1 messages in root-mail Jul 1 00:30:48 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable Jul 1 00:30:48 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Jul 1 00:30:48 thebighonker dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for ler Jul 1 00:30:48 thebighonker dovecot: indexer-worker(ler): Fatal: master: service(indexer-worker): child 21119 killed with signal 6 (core not dumped - set service indexer-worker { drop_priv_before_exec=yes }) So, what's my problem here? doveconf -n: # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.0-STABLE amd64 auth_default_realm = lerctr.org auth_mechanisms = plain login auth_realms = lerctr.org thebighonker.lerctr.org tbh.lerctr.org auth_username_format = %Ln lda_mailbox_autocreate = yes lmtp_save_to_detail_mailbox = yes login_access_sockets = tcpwrap mail_debug = yes mail_location = mbox:~/mail:INBOX=~/mail/INBOX mail_plugins = fts fts_lucene stats mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate vacation-seconds editheader namespace archive { hidden = no inbox = no list = no location = mbox:~/MAILARCHIVE prefix = "#ARCHIVE/" separator = / } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX { auto = create } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = failure_show_msg=yes session=yes max_requests=20 driver = pam } plugin { fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. normalize no_snowball recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +vacation-seconds stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_refresh = 5s stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-client { mode = 0666 } unix_listener auth-master { mode = 0666 } } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0666 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } ssl_cert = References: <53B3130D.8010209@nybeta.com> Message-ID: <201407011650.37240.gheskett@wdtv.com> On Tuesday 01 July 2014 15:59:09 Thomas Harold did opine And Gene did reply: > On 7/1/2014 4:48 AM, Infoomatic wrote: > >> If you actually want to preserve those increments (as opposed to > >> just keeping an rsync mirror up-to-date), I like rdiff-backup. It > >> handles maildirs well because of the one-message-per-file design. > > > > Second that. It's great tool that keeps an actual sync > > (rsync-based) of the data-directory and the metadata (delta) in a > > seperate directory to restore data from any date. > > > > Alternatively, you might want to take a look at bacula, which was > > faster in most cases (development seems to have stalled, but there > > is a fork I have not had time to take a look at: bareos). However, I > > liked the rdiff-backup way because I can restore files via scp or > > rsync (most of my requests were like "please restore from > > yesterday") or if I want to restore data from a certain date I can > > use rdiff-backup from command line (bacula is much more complex, and > > you need the admin tool to restore files - rdiff-backup works from > > command line locally or via ssh/keyauth) > > I looked at Bacula/Amanda - which are great systems if your focus is > tape or backup to disk. But neither of them had good support for > "backup to disk, rsync to offsite". > > rsnapshot / rdiff-backup are just better at creating backups which are > rsync-friendly over the WAN. Which also means you can easily push the > backups to USB drives without having to wait hours and hours. Well, I've been using amanda since 1998, and it was fairly mature then, and its always done what I wanted. I do backup to disk, but if I wanted offsite, then copying its backup and index files to an external drive offers bare metal recovery completely up to the date of the last backup the way I do it. As is, I just use a separate disk from the OS's disk as virtual tape. Works a treat. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS From slitt at troubleshooters.com Tue Jul 1 20:56:38 2014 From: slitt at troubleshooters.com (Steve Litt) Date: Tue, 1 Jul 2014 16:56:38 -0400 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: <53B1EA48.2020806@thinline.cz> References: <53B1EA48.2020806@thinline.cz> Message-ID: <20140701165638.461a3ebe@mydesq2.domain.cxm> On Tue, 01 Jul 2014 00:52:56 +0200 Jiri Bourek wrote: > On 1.7.2014 00:28, deoren wrote: > > I'm still pretty new to running a mail server, but one thing I've > > come to appreciate over the years is a good backup strategy. Since > > I have always run my own servers for practice and for personal use > > I don't have access to Enterprise backup solutions. Because of that > > I usually just fall back to scripts and tarballs and offload the > > content on a regular basis. > > > > Right now I'm using LVM snapshots + tarballs for daily backups, but > > I'd like to get better coverage for incremental changes that occur > > throughout the day. The size of existing content is low, but (small) > > changes are frequent. > > > > I went with Maildir format because based on my reading it is > > referred to as time tested and corruption resistant. Because > > individual emails are stored as separate files this also leads me > > to believe that a version control system (Git, SVN) would allow for > > easy point in time restores. > > > > I'm also going to research the GNU tar utility's support for > > incremental archives as that sounds promising. > > > > Suggestions and warnings are most welcome. > > > > Thanks! > > Since you're using maildir, you might want to check rsync out as > well, especially with --link-dest. In short, you call rsync on your > backup machine like this: > > rsync --link-dest=previous-backup-dir source new-backup-dir > > This compares current files with their copies in previous backup. All > files which didn't change are hardlinked, saving storage space. This is pretty much what I do. I have a backup server that rsync pulls off the Dovecot Maildir on my desktop. With a backup server, most of the processing is done on the backup server: the box with the Maildir is only being read. For reasons I've long since forgotten, in order to keep hardlink increments to old backups, I use a separate cp -al on the backup server instead of doing --link-dest=previous-backup-dir. Theoretically, I should shut off the fetchmail that feeds my Maildir before doing such a backup (and probably shut down Dovecot too). But I'm the only user, so... A few days ago I deleted my whole INBOX and rsync'ed it back in a matter of minutes. Here's some info on my backup system: http://troubleshooters.com/lpm/200609/200609.htm If anyone's interested in backing up to Blu-Ray, here's some info I wrote: http://www.troubleshooters.com/linux/blu-ray-backup.htm SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance From nick.z.edwards at gmail.com Wed Jul 2 00:06:45 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Wed, 2 Jul 2014 10:06:45 +1000 Subject: Error receiving mail from postfix In-Reply-To: <20140701083155.513c24ac@scorpio> References: <20140701071016.5f97c28f@scorpio> <53B2A226.5070404@thinline.cz> <20140701083155.513c24ac@scorpio> Message-ID: protocol lda { auth_socket_path = /var/run/dovecot/auth-userdb deliver_log_format = msgid=%m: from=%f: %$ log_path = /var/log/dovedel/deliver.log mail_plugins = $mail_plugins sieve postmaster_address = postmaster at YOUR_DOMAIN quota_full_tempfail = no } On 7/1/14, Jerry wrote: > On Tue, 01 Jul 2014 13:57:26 +0200, Jiri Bourek stated: > >> On 1.7.2014 13:10, Jerry wrote: >> > When mail is relayed to dovecot from postfix, I am getting this error >> > message in the maillog: >> > >> > Jul 1 07:05:19 scorpio postfix/pipe[45488]: 3h2jQl3Xldz3FMPc: >> > to=, relay=dovecot, delay=0.16, >> > delays=0.12/0.01/0/0.03, >> > dsn=4.3.0, status=deferred (temporary failure. Command output: lda: >> > Error: user user at domain.com: Error reading configuration: Invalid >> > settings: postmaster_address setting not given lda: Fatal: Internal >> > error >> > occurred. Refer to server log for more information. ) >> > >> > Is this a Postfix problem or a Dovecot problem? >> > >> >> Misconfigured Dovecot, it's missing postmaster_address setting for LDA >> as the log message is telling you. > > Okay, perhaps a dump question, but exactly where am I suppose to enter that > information? I have tried reading the documentation, but I must be missing > it. > > -- > jerry > From nick.z.edwards at gmail.com Wed Jul 2 00:10:23 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Wed, 2 Jul 2014 10:10:23 +1000 Subject: Android Sync Doesn't Work Too Good In-Reply-To: <53B3195D.9000407@globalchangemusic.org> References: <53B305B4.8020505@globalchangemusic.org> <53B31449.2010205@sys4.de> <53B3195D.9000407@globalchangemusic.org> Message-ID: On 7/2/14, Asai wrote: >> Am 01.07.2014 21:02, schrieb Asai: >>> Greetings, >>> >>> I'm getting reports from a user who's reading and deleting mail on >>> Thunderbird, but read flags and deletions don't show up in his Android >>> phone. He's using the native Android mail app with the newest Android >>> OS. >> in imap mode ? > Yes >> >>> My question is, where do I start with troubleshooting this kind of >>> issue? Thanks for anyone's insight here. We're using Dovecot 2.2.13. >>> >> look at the verbose logs, and dont expect android app to be a good imap >> client >> ( i never tried it that kind ) , better use k9 Mail with imap on Android >> >> >> https://code.google.com/p/k9mail/ >> > Thanks, Robert. This user did once use K9, but they like the native app > better... I suggested to them that they double check the syncing in K9 > rather than native. > native is OK for pop;3, but imap - hopeless., as bad as apple's native mail app is with pop3 (not issuing QUIT) etc +1 for k9 rufff :) From nick.z.edwards at gmail.com Wed Jul 2 00:12:30 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Wed, 2 Jul 2014 10:12:30 +1000 Subject: i need a little advice with dovecot master user In-Reply-To: <1404135293.3677.35.camel@secoges-laptop> References: <1404135293.3677.35.camel@secoges-laptop> Message-ID: On 6/30/14, Francesco wrote: > > what am i doing wrong? > Using a NON SUPPORTED EOL'd version of dovecot for starters. From nick.z.edwards at gmail.com Wed Jul 2 00:21:44 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Wed, 2 Jul 2014 10:21:44 +1000 Subject: Managing users and home dirs In-Reply-To: <426fb533bc5564b3a7fe8cdb3a0959d7@areyes.com> References: <426fb533bc5564b3a7fe8cdb3a0959d7@areyes.com> Message-ID: On 6/22/14, deano-dovecot at areyes.com wrote: > > > For those of you using virtual users, and SQL, how are you managing > your users and their home dirs ? That is, what process do you use for > adding/deleting users, creating their home dirs etc ? I suppose it's > easy enough to do manually, inserting rows in the database, creating > dirs, chown/chmod yada yada, but there must be a better way to do it ... > If you're doing dovecot replication then it gets even more cumbersome, > having to duplicate the effort in two places (and make sure it's > correct). Simple perl script called directly, or even from control panel or hosting management software that can call hooks to call the script. but it adds them into the user DB, the mail DB, the http-auth DB and creates their own DB (we give users 1 mysql DB each) you have a base path (say /var/vmail) you can use variables, substr, and so on to simplify it , once in the DB dovecot LDA automatically creates the users home dir based on mail location and things ;like that IOW, spending 10 mins to write teh script saves years of manual pain From mtrainer at westnet.com.au Wed Jul 2 01:24:55 2014 From: mtrainer at westnet.com.au (Murray Trainer) Date: Wed, 02 Jul 2014 09:24:55 +0800 Subject: Direct groups of users to pairs of backend mailstores? Message-ID: Hi All, We are using Dovecot in a Director setup with two director proxies, six backend mailstores, mailbox storage in NFS, and user accounts stored in LDAP.?? Currently we have five NFS filesystems on EMC VNX storage which are all mounted on each of the six backend mailstores.?? At the moment all users could be directed to any of the six mailstores.? We have a group of users with very large mailboxes we want to put on separate cheaper Backblaze NFS storage.? Because this will be less reliable than our VNX storage we want to be able to direct this group of users to a new pair of backend mailstores that only have the Backblaze NFS mounts.?? This would isolate the rest of the users isolation from problems with the Backblaze NFS servers.? I have read the Dovecot documentation which indicates it is possible to direct users always to a single backend server.??? Can Dovecot direct users to a pair or more of backend mailstores - ie a subset or another set of mailstores.??? If not it would be a great enhancement which would allow more scalability, flexibility and redundancy. Thanks Murray From slusarz at curecanti.org Wed Jul 2 04:20:15 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Tue, 01 Jul 2014 22:20:15 -0600 Subject: Imaptest script testing In-Reply-To: <1403775446782-48607.post@n4.nabble.com> Message-ID: <20140701222015.Horde.4Z3PtzvQVRo7w7PYcR7Vgg3@bigworm.curecanti.org> Quoting kaustubh : > http://www.imapwiki.org/ImapTest/ > > I am doing imap testing using imaptest scripts. But, i am unable to append > message. > > APPEND INBOX "15-Jun-2015 05:30:05 -0700" "From:abc at gmail.com" "Subject: > test. HI this is msg". Not sure if imaptest has a special format... But this is an invalid IMAP APPEND command. The entire message body is in a single literal. This has a better chance of working (APPEND actually requires a literal for message data, but I am assuming Dovecot/imaptest is liberal about what it parses and will also accept a quoted string in this situation): APPEND INBOX "15-Jun-2015 05:30:05 -0700" "From:abc at gmail.com\nSubject: test.\n\nHI this is msg" michael From compul at coletteral.net Wed Jul 2 07:49:56 2014 From: compul at coletteral.net (Niklas Lemcke - =?UTF-8?B?5p6X5qiC5a+s?=) Date: Wed, 2 Jul 2014 15:49:56 +0800 Subject: Permissions with mailman Message-ID: <20140702154956.13103a04@compul-debian.me.org> Hi, I'm running a Mailserver, and recently also a Mailinglist. I'm sporting # dovecot --version 2.1.7 on a debian stable machine with postfix & mailman. Everything works fine, except that no archive is being created (here an excerpt from my log): Jul 2 15:29:39 blade01 postfix/qmgr[5217]: B30BCE1F52: from=, size=802, nrcpt=1 (queue active) Jul 2 15:29:39 blade01 dovecot: lda(list): Error: user list: Initialization failed: Initializing mail storage from mail_location setting failed: mkdir(/var/mail/vmail//list/mail) failed: Permission denied (euid=38(list) egid=38(list) missing +w perm: /var/mail/vmail/, we're not in group 5000(vmail), dir owned by 5000:5000 mode=0775) Jul 2 15:29:39 blade01 dovecot: lda(list): Fatal: Invalid user settings. Refer to server log for more information. Jul 2 15:29:39 blade01 postfix/local[2778]: B30BCE1F52: to=, orig_to=, relay=local, delay=12578, delays=12578/0.16/0/0.17, dsn=4.3.0, status=deferred (temporary failure) Now since dovecot is running as user vmail (the other mail folders are all well managed and accessed by it, and all owned by vmail:vmail) I thought it might be saying that the user list is not in group vmail. Now: $ groups list list : list vmail and the permissions are 775, but it's still complaining about "missing +w perm". What is it referring to with "we're not in group 5000"? Thanks for any help! -- Niklas - ??? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From mailinglist at darac.org.uk Wed Jul 2 09:48:52 2014 From: mailinglist at darac.org.uk (Darac Marjal) Date: Wed, 2 Jul 2014 10:48:52 +0100 Subject: Android Sync Doesn't Work Too Good In-Reply-To: <53B3195D.9000407@globalchangemusic.org> References: <53B305B4.8020505@globalchangemusic.org> <53B31449.2010205@sys4.de> <53B3195D.9000407@globalchangemusic.org> Message-ID: <20140702094851.GA12000@darac.org.uk> On Tue, Jul 01, 2014 at 01:26:05PM -0700, Asai wrote: > >Am 01.07.2014 21:02, schrieb Asai: > >>Greetings, > >> > >>I'm getting reports from a user who's reading and deleting mail on > >>Thunderbird, but read flags and deletions don't show up in his Android > >>phone. He's using the native Android mail app with the newest Android OS. > >in imap mode ? > Yes > > > >>My question is, where do I start with troubleshooting this kind of > >>issue? Thanks for anyone's insight here. We're using Dovecot 2.2.13. > >> > >look at the verbose logs, and dont expect android app to be a good imap > >client > >( i never tried it that kind ) , better use k9 Mail with imap on Android > > > > > >https://code.google.com/p/k9mail/ > > > Thanks, Robert. This user did once use K9, but they like the native app > better... I suggested to them that they double check the syncing in K9 > rather than native. If it's the look of K9 they don't like, can I recommend K-@ Mail. K-@ Mail uses K9Mail's mail engines, but puts a modern interface on the top. From bambero at gmail.com Wed Jul 2 11:04:46 2014 From: bambero at gmail.com (Bambero) Date: Wed, 2 Jul 2014 13:04:46 +0200 Subject: Shared folders not listed by IMAP Message-ID: Hello I just upgraded my system and there is a problem with shared mailboxes. When I use the doveadm command I can see shared folders: doveadm mailbox list -u 'test at mydomain.pl' Drafts Sent Spam Trash Shared Virtuals Virtuals/all Shared/test2 at mydomain.pl Shared/test2 at mydomain.pl/Sent INBOX But I can't see them over IMAP protocol. Some config opts: valid_chroot_dirs = /var/mail mail_chroot = /var/mail namespace { type = shared separator = / prefix = Shared/%%u/ location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u subscriptions = yes list = yes } plugin { acl = vfile:cache_secs=5 } plugin { acl_shared_dict = file:/var/mail/%i.db } protocol imap { mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib } My version of dovecot is 2.2.10. Regards Bambero From giedrius at su.lt Wed Jul 2 11:29:54 2014 From: giedrius at su.lt (=?UTF-8?B?R2llZHJpdXMgTGl1YmF2acSNaXVz?=) Date: Wed, 02 Jul 2014 14:29:54 +0300 Subject: Shared folders not listed by IMAP In-Reply-To: References: Message-ID: <53B3ED32.60504@su.lt> Hi, doveadm mailbox subscribe -u test at mydomain.pl Shared/test2 at mydomain.pl doveadm mailbox subscribe -u test at mydomain.pl Shared/test2 at mydomain.pl/Sent 2014.07.02 14:04, Bambero ra??: > Hello > > I just upgraded my system and there is a problem with shared mailboxes. > > When I use the doveadm command I can see shared folders: > > doveadm mailbox list -u 'test at mydomain.pl' > Drafts > Sent > Spam > Trash > Shared > Virtuals > Virtuals/all > Shared/test2 at mydomain.pl > Shared/test2 at mydomain.pl/Sent > INBOX > > But I can't see them over IMAP protocol. > > Some config opts: > > valid_chroot_dirs = /var/mail > mail_chroot = /var/mail > > namespace { > type = shared > separator = / > prefix = Shared/%%u/ > location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u > subscriptions = yes > list = yes > } > > plugin { > acl = vfile:cache_secs=5 > } > > plugin { > acl_shared_dict = file:/var/mail/%i.db > } > > protocol imap { > mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib > } > > > My version of dovecot is 2.2.10. > > Regards > Bambero > -------------- next part -------------- A non-text attachment was scrubbed... Name: giedrius.vcf Type: text/x-vcard Size: 197 bytes Desc: not available URL: From giedrius at su.lt Wed Jul 2 11:41:44 2014 From: giedrius at su.lt (=?UTF-8?B?R2llZHJpdXMgTGl1YmF2acSNaXVz?=) Date: Wed, 02 Jul 2014 14:41:44 +0300 Subject: [Dovecot] lazy_expunge and shared folders In-Reply-To: <3960101.rXVyUmmHoz@vulcan.ricint.oeaw.ac.at> References: <1655855.hMDViD39ls@vulcan.ricint.oeaw.ac.at> <3960101.rXVyUmmHoz@vulcan.ricint.oeaw.ac.at> Message-ID: <53B3EFF8.80300@su.lt> Hi, i've had the save problem. This is /quick/ and /dirty/ fix for this problem [gzipped patch file attached] After patching source, recompile lazy_expunge plugin (make -C src/plugins/lazy_expunge all install) AND add this to the configuration: > plugin { > lazy_expunge_ignore_namespace_not_found = yes > } 2014.05.26 17:12, Florian Tischler ra??: > Am Dienstag, 20. Mai 2014, 14:00:11 schrieben Sie: >> Hi, >> >> since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon >> as a user shares a folder. The user the folder is shared to cannot login >> anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace: >> '.EXPUNGED/' >> >> - When no folder is shared lazy_expunge is working fine, deleted mails are >> moved to the expunged namespace and can be recovered without any >> problems. - Sharing folders works as long as I disable lazy_expunge. >> >> I have used the config (with minor changes) with dovecot 2.0 for years >> without any problem. Switching to dovecot 2.2.10 (atrps repository) or >> 2.2.12 (dovecot enterprise repo) lazy_expunge and acl do not work together >> anymore. > Hi, > > unfortunately I got no response to the acl breaks lazy_expunge problem. > > Maybe the developers can give me some feedback? > Is it supposed (not) to work? Will it be fixed? > > Currently it prevents me from sucessfully migration from 2.0 to 2.2 without > losing features. > > Thanks, > Florian > >> Is it a bug, a known limitation or is something wrong with my config? >> Any hints are welcome. >> >> Thanks in advance, >> Florian >> >> dovecot -n >> >> # 2.2.12.12 (03196f188677): /etc/dovecot/dovecot.conf >> # OS: Linux 2.6.32-042stab085.20 x86_64 CentOS release 6.5 (Final) >> auth_cache_negative_ttl = 10 mins >> auth_cache_size = 10 M >> auth_cache_ttl = 2 hours >> auth_failure_delay = 10 secs >> auth_mechanisms = plain login >> auth_socket_path = /var/run/dovecot/auth-userdb >> base_dir = /var/run/dovecot/ >> disable_plaintext_auth = no >> first_valid_gid = 105 >> first_valid_uid = 105 >> hostname = ... >> imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags >> imap_idle_notify_interval = 10 mins >> last_valid_uid = 105 >> listen = ... >> lmtp_save_to_detail_mailbox = yes >> login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c >> mail_gid = vimap >> mail_home = /var/imap/spool/%1n/%n >> mail_location = mdbox:~/mdbox >> mail_plugins = " fts fts_lucene acl" >> mail_temp_dir = /var/imap/tmp >> mail_uid = vimap >> managesieve_notify_capability = mailto >> managesieve_sieve_capability = fileinto reject envelope encoded-character >> vacation subaddress comparator-i;ascii-numeric relational regex imap4flags >> copy include variables body enotify environment mailbox date ihave >> mbox_write_locks = fcntl >> mdbox_rotate_interval = 1 days >> namespace { >> list = children >> location = >> mdbox:/var/imap/spool/%%1n/%%n/mdbox:INDEXPVT=/var/imap/spool/%1n/%n/mdbox >> /shared/%%u prefix = User/%%u/ >> separator = / >> subscriptions = no >> type = shared >> } >> namespace expunged { >> hidden = yes >> list = no >> location = mdbox:/var/imap/spool/%1n/%n/mdbox:MAILBOXDIR=expunged >> prefix = .EXPUNGED/ >> separator = / >> subscriptions = no >> type = private >> } >> namespace inbox { >> inbox = yes >> location = mdbox:/var/imap/spool/%1n/%n/mdbox >> mailbox Drafts { >> auto = subscribe >> special_use = \Drafts >> } >> mailbox Learn { >> auto = subscribe >> } >> mailbox Learn/Ham { >> auto = subscribe >> } >> mailbox Learn/Spam { >> auto = subscribe >> } >> mailbox Sent { >> auto = subscribe >> special_use = \Sent >> } >> mailbox Spam { >> auto = subscribe >> special_use = \Junk >> } >> mailbox Trash { >> auto = subscribe >> special_use = \Trash >> } >> mailbox virtual/All { >> special_use = \All >> } >> mailbox virtual/Flagged { >> special_use = \Flagged >> } >> prefix = >> separator = / >> type = private >> } >> passdb { >> args = /etc/dovecot/master-users >> driver = passwd-file >> master = yes >> } >> passdb { >> args = /etc/dovecot/dovecot-ldap.conf.ext >> driver = ldap >> } >> passdb { >> args = /etc/dovecot/extra-users >> driver = passwd-file >> } >> plugin { >> acl = vfile:/var/imap/global-acls:cache_secs=300 >> acl_shared_dict = file:/var/imap/shared-mailboxes/shared-mailboxes >> fts = lucene >> fts_autoindex = yes >> fts_lucene = whitespace_chars=@. >> lazy_expunge = .EXPUNGED/ >> lazy_expunge_only_last_instance = yes >> recipient_delimiter = + >> sieve = ~/.dovecot.sieve >> sieve_dir = ~/sieve >> sieve_max_actions = 32 >> sieve_max_redirects = 4 >> sieve_max_script_size = 1M >> } >> pop3_client_workarounds = outlook-no-nuls oe-ns-eoh >> postmaster_address = postmaster at ... >> protocols = imap pop3 lmtp sieve >> service auth { >> unix_listener /var/spool/postfix/private/auth { >> group = postfix >> mode = 0660 >> user = postfix >> } >> unix_listener auth-userdb { >> group = vimap >> mode = 0600 >> user = vimap >> } >> user = $default_internal_user >> } >> service imap-login { >> process_min_avail = 4 >> service_count = 0 >> } >> service imap { >> process_limit = 1024 >> vsz_limit = 256 M >> } >> service lmtp { >> inet_listener lmtp { >> address = ... >> port = 24 >> } >> } >> service managesieve-login { >> inet_listener sieve { >> port = 4190 >> } >> inet_listener sieve_deprecated { >> port = 2000 >> } >> service_count = 1 >> vsz_limit = 64 M >> } >> service pop3-login { >> inet_listener pop3s { >> port = 995 >> ssl = yes >> } >> process_min_avail = 4 >> service_count = 0 >> } >> service pop3 { >> process_limit = 512 >> } >> ssl_cert = > ssl_key = > userdb { >> args = /etc/dovecot/dovecot-ldap.conf.ext >> driver = ldap >> } >> userdb { >> args = uid=vimap gid=vimap home=/var/imap/spool/%1n/%n >> driver = static >> } >> protocol lda { >> mail_plugins = " fts fts_lucene acl sieve" >> } >> protocol imap { >> mail_max_userip_connections = 20 >> mail_plugins = " fts fts_lucene acl imap_acl" >> } >> protocol lmtp { >> mail_plugins = " fts fts_lucene acl sieve" >> } >> protocol sieve { >> mail_max_userip_connections = 10 >> managesieve_implementation_string = Dovecot Pigeonhole >> managesieve_logout_format = bytes=%i/%o >> managesieve_max_line_length = 65536 >> } >> protocol pop3 { >> mail_max_userip_connections = 20 >> } -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-2.2.13-lazy_expunge_acl_fix.diff.gz Type: application/gzip Size: 919 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: giedrius.vcf Type: text/x-vcard Size: 197 bytes Desc: not available URL: From ihab_mishriki at hotmail.com Wed Jul 2 14:01:35 2014 From: ihab_mishriki at hotmail.com (ihab) Date: Wed, 2 Jul 2014 07:01:35 -0700 (PDT) Subject: number of users Message-ID: <1404309695543-48701.post@n4.nabble.com> Hello, i using roundcube with dovecot, i have a question if there is possible to know the number of users that using the mail system (in other word the online users) . thanks, best regards, ihab :) -- View this message in context: http://dovecot.2317879.n4.nabble.com/number-of-users-tp48701.html Sent from the Dovecot mailing list archive at Nabble.com. From h.reindl at thelounge.net Wed Jul 2 14:04:34 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 02 Jul 2014 16:04:34 +0200 Subject: number of users In-Reply-To: <1404309695543-48701.post@n4.nabble.com> References: <1404309695543-48701.post@n4.nabble.com> Message-ID: <53B41172.2020807@thelounge.net> Am 02.07.2014 16:01, schrieb ihab: > i using roundcube with dovecot, i have a question if there is possible to > know the number of users that using the mail system (in other word the > online users) no - how do you imagine that? * roundcube is a web-application * HTTP is stateless * so there are no permanent connections -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From jonnyt at abpni.co.uk Wed Jul 2 14:11:09 2014 From: jonnyt at abpni.co.uk (Jonathan Tripathy) Date: Wed, 02 Jul 2014 15:11:09 +0100 Subject: number of users Message-ID: On 2014-07-02 15:04, Reindl Harald wrote: > Am 02.07.2014 16:01, schrieb ihab: >> i using roundcube with dovecot, i have a question if there is >> possible to >> know the number of users that using the mail system (in other word >> the >> online users) > > no - how do you imagine that? > > * roundcube is a web-application > * HTTP is stateless > * so there are no permanent connections It is possible as Roundcube does have its own session management, which you could maybe hook into. From h.reindl at thelounge.net Wed Jul 2 14:16:35 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 02 Jul 2014 16:16:35 +0200 Subject: number of users In-Reply-To: <23d720eccdcba6bbd71be61576495907@abpni.co.uk> References: <1404309695543-48701.post@n4.nabble.com> <53B41172.2020807@thelounge.net> <23d720eccdcba6bbd71be61576495907@abpni.co.uk> Message-ID: <53B41443.7060106@thelounge.net> Am 02.07.2014 16:10, schrieb Jonathan Tripathy: > On 2014-07-02 15:04, Reindl Harald wrote: >> Am 02.07.2014 16:01, schrieb ihab: >>> i using roundcube with dovecot, i have a question if there is possible to >>> know the number of users that using the mail system (in other word the >>> online users) >> >> no - how do you imagine that? >> >> * roundcube is a web-application >> * HTTP is stateless >> * so there are no permanent connections > > It is possible as Roundcube does have its own session management, which you could maybe hook into first: why do you respond off-list? second: any of such magic is outside of dovecots scope and from security point of view you don't want user-login-sessions dealing with other users session infos and any smart session-backend is doing what it can to prevent from such a breach -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From jonnyt at abpni.co.uk Wed Jul 2 14:24:50 2014 From: jonnyt at abpni.co.uk (Jonathan Tripathy) Date: Wed, 02 Jul 2014 15:24:50 +0100 Subject: number of users In-Reply-To: <53B41443.7060106@thelounge.net> References: "<1404309695543-48701.post@n4.nabble.com>" <53B41172.2020807@thelounge.net> <23d720eccdcba6bbd71be61576495907@abpni.co.uk> <53B41443.7060106@thelounge.net> Message-ID: <31c1d4348d195c40746e8b1d6140052a@abpni.co.uk> On 2014-07-02 15:16, Reindl Harald wrote: > Am 02.07.2014 16:10, schrieb Jonathan Tripathy: >> On 2014-07-02 15:04, Reindl Harald wrote: >>> Am 02.07.2014 16:01, schrieb ihab: >>>> i using roundcube with dovecot, i have a question if there is >>>> possible to >>>> know the number of users that using the mail system (in other >>>> word the >>>> online users) >>> >>> no - how do you imagine that? >>> >>> * roundcube is a web-application >>> * HTTP is stateless >>> * so there are no permanent connections >> >> It is possible as Roundcube does have its own session management, >> which you could maybe hook into > > first: why do you respond off-list? > > second: > any of such magic is outside of dovecots scope > > and from security point of view you don't want user-login-sessions > dealing with other users session infos and any smart session-backend > is doing what it can to prevent from such a breach first: I did respond on list as well as directly to you. second: There is nothing wrong with expanding roundcube to print a list of online based users. This may be just as easy as printing a certain database table of active sessions. Yes, there are security concerns but of course these need to be dealt with properly. third: Yes, it's outside Dovecot's scope, hence the Roundcube sugestion. From adi at cg.tuwien.ac.at Wed Jul 2 14:29:32 2014 From: adi at cg.tuwien.ac.at (Adi Kriegisch) Date: Wed, 2 Jul 2014 16:29:32 +0200 Subject: [Dovecot] TLS/SSL for Win8 & Outlook In-Reply-To: <53AC3890.7050608@sys4.de> References: <536BEEFA.3090708@sys4.de> <536C75D2.4030109@goodrick.ch> <536C92E0.8040107@sys4.de> <53779EDB.9050908@sys4.de> <5378F610.6040102@goodrick.ch> <5379000F.1050503@sys4.de> <537CE6CB.6070908@goodrick.ch> <537CFB12.5070009@sys4.de> <20140626095349.GA28654@vrvis.at> <53AC3890.7050608@sys4.de> Message-ID: <20140702142932.GF18805@vrvis.at> On Thu, Jun 26, 2014 at 05:13:20PM +0200, Robert Schetterer wrote: > Am 26.06.2014 11:53, schrieb Adi Kriegisch: > > On Wed, May 21, 2014 at 09:14:26PM +0200, Robert Schetterer wrote: > >> Am 21.05.2014 19:47, schrieb Sebastian Goodrick: > >>> I just installed the (rapid-ssl) certificate and it works now. > >>> Needless to say that I don't understand it. The old certificate worked > >>> with all other clients but win8/outlook, plus the old dovecot install > >>> worked with win8/outlook as well. > > I am struggling with the same issue for some time now: win8/outlook isn't > > able to connect to dovecot 2.2.9 (from Debian/backports); the error on the > > outlook side of things is 0x800CCC0E which is really helpful. > > read again orig thread, i ve tested brand new win 8.1 outlook 2013 > install all latest patchlevel with dovecot 2.2.13 tls, no problem, the > orig problem had gone using another crt from rapid-ssl by unknown > reason, needless to say that there may tons of other reasons > why it fails at your site, however im nearly sure tha tthere is no > default bug in dovecot Right. The "bug" is in Windows: SHA512 isn't configured as a valid hash for a certificate (SHA256 and SHA384 are) and Windows is unable to provide a reasonable error message. (**) To solve this, adding "RSA/SHA512" to the following registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Cryptography\Configuration\Local\SSL\00010003\Functions solves the issue. (This affects CACert as well as their default signature algorithm is SHA512 by now) Do not forget to reboot after adding this registry entry. -- Adi (**) In Windows 8, certificate validation seems to behave quite different for TLSv1.2 than for older protocol incarnations. So there might be other pitfalls as well (like for example self signed certificates including the CA flag set to true will not be considered valid)... PS: This hinted me in the right direction: http://www.michaelm.info/blog/?p=1273 From h.reindl at thelounge.net Wed Jul 2 14:37:29 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 02 Jul 2014 16:37:29 +0200 Subject: number of users In-Reply-To: <31c1d4348d195c40746e8b1d6140052a@abpni.co.uk> References: <53B41172.2020807@thelounge.net> <23d720eccdcba6bbd71be61576495907@abpni.co.uk> <53B41443.7060106@thelounge.net> <31c1d4348d195c40746e8b1d6140052a@abpni.co.uk> Message-ID: <53B41929.5040901@thelounge.net> Am 02.07.2014 16:24, schrieb Jonathan Tripathy: > On 2014-07-02 15:16, Reindl Harald wrote: >> Am 02.07.2014 16:10, schrieb Jonathan Tripathy: >>> On 2014-07-02 15:04, Reindl Harald wrote: >>>> Am 02.07.2014 16:01, schrieb ihab: >>>>> i using roundcube with dovecot, i have a question if there is possible to >>>>> know the number of users that using the mail system (in other word the >>>>> online users) >>>> >>>> no - how do you imagine that? >>>> >>>> * roundcube is a web-application >>>> * HTTP is stateless >>>> * so there are no permanent connections >>> >>> It is possible as Roundcube does have its own session management, which you could maybe hook into >> >> first: why do you respond off-list? >> >> second: >> any of such magic is outside of dovecots scope >> >> and from security point of view you don't want user-login-sessions >> dealing with other users session infos and any smart session-backend >> is doing what it can to prevent from such a breach > > first: I did respond on list as well as directly to you. with a second message while i was already responding that's even more bad than reply-all on mailing-lists > second: There is nothing wrong with expanding roundcube to print a list of online based users. This may be just as > easy as printing a certain database table of active sessions. Yes, there are security concerns but of course these > need to be dealt with properly. which never can be a real number, it's just a random one which maybe or maybe not come close to the reality > third: Yes, it's outside Dovecot's scope, hence the Roundcube sugestion and that's why it is the wrong mailing-list from the first moment on -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From asai at globalchangemusic.org Wed Jul 2 15:09:58 2014 From: asai at globalchangemusic.org (Asai) Date: Wed, 02 Jul 2014 08:09:58 -0700 Subject: Android Sync Doesn't Work Too Good In-Reply-To: <20140702094851.GA12000@darac.org.uk> References: <53B305B4.8020505@globalchangemusic.org> <53B31449.2010205@sys4.de> <53B3195D.9000407@globalchangemusic.org> <20140702094851.GA12000@darac.org.uk> Message-ID: <53B420C6.30404@globalchangemusic.org> Am 01.07.2014 21:02, schrieb Asai: >>>> Greetings, >>>> >>>> I'm getting reports from a user who's reading and deleting mail on >>>> Thunderbird, but read flags and deletions don't show up in his Android >>>> phone. He's using the native Android mail app with the newest Android OS. >>> in imap mode ? >> Yes >>>> My question is, where do I start with troubleshooting this kind of >>>> issue? Thanks for anyone's insight here. We're using Dovecot 2.2.13. >>>> >>> look at the verbose logs, and dont expect android app to be a good imap >>> client >>> ( i never tried it that kind ) , better use k9 Mail with imap on Android >>> >>> >>> https://code.google.com/p/k9mail/ >>> >> Thanks, Robert. This user did once use K9, but they like the native app >> better... I suggested to them that they double check the syncing in K9 >> rather than native. > If it's the look of K9 they don't like, can I recommend K-@ Mail. K-@ > Mail uses K9Mail's mail engines, but puts a modern interface on the top. Thanks for the recommendation, I've passed it on to the user. From antondollmaier at aditsystems.de Wed Jul 2 15:14:42 2014 From: antondollmaier at aditsystems.de (Anton Dollmaier) Date: Wed, 02 Jul 2014 17:14:42 +0200 Subject: Android Sync Doesn't Work Too Good In-Reply-To: <53B420C6.30404@globalchangemusic.org> References: <53B305B4.8020505@globalchangemusic.org> <53B31449.2010205@sys4.de> <53B3195D.9000407@globalchangemusic.org> <20140702094851.GA12000@darac.org.uk> <53B420C6.30404@globalchangemusic.org> Message-ID: <53B421E2.8090601@aditsystems.de> Hi, >> If it's the look of K9 they don't like, can I recommend K-@ Mail. K-@ >> Mail uses K9Mail's mail engines, but puts a modern interface on the top. Also, the developers of K-9 Mail are working on a new version with improved GUI, called "Kaiten" (K-10...): > https://play.google.com/store/apps/details?id=com.kaitenmail.adsupported The paid version is ad free: > https://play.google.com/store/apps/details?id=com.kaitenmail Best, Anton -- ADITSYSTEMS Anton Dollmaier, M.Sc. Im Moos 22 84323 Massing Telefon: +49-8724-3949990 (Mo-Fr, 10:00-18:00 Uhr, dt. Festnetz) Telefax: +49-8724-3949999 Umsatzsteuer-ID: DE221493781 Blog: http://blog.aditsystems.de/ Twitter: http://twitter.com/ADITSystems Google+: http://google.com/+AditsystemsDe KundenCenter: https://kunden.aditsystems.de/kc/ Wiki: https://kunden.aditsystems.de/wiki/ From bambero at gmail.com Wed Jul 2 16:03:54 2014 From: bambero at gmail.com (Bambero) Date: Wed, 2 Jul 2014 18:03:54 +0200 Subject: Shared folders not listed by IMAP In-Reply-To: <53B3ED32.60504@su.lt> References: <53B3ED32.60504@su.lt> Message-ID: But the problem is that I can't see shared folders to subscribe (shared by other users) while connecting via IMAP. There is also an error: Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No such file or directory Probably becouse of chroot (/var/mail). On Wed, Jul 2, 2014 at 1:29 PM, Giedrius Liubavi?ius wrote: > Hi, > doveadm mailbox subscribe -u test at mydomain.pl Shared/test2 at mydomain.pl > doveadm mailbox subscribe -u test at mydomain.pl > Shared/test2 at mydomain.pl/Sent > > 2014.07.02 14:04, Bambero ra??: > > Hello > > > > I just upgraded my system and there is a problem with shared mailboxes. > > > > When I use the doveadm command I can see shared folders: > > > > doveadm mailbox list -u 'test at mydomain.pl' > > Drafts > > Sent > > Spam > > Trash > > Shared > > Virtuals > > Virtuals/all > > Shared/test2 at mydomain.pl > > Shared/test2 at mydomain.pl/Sent > > INBOX > > > > But I can't see them over IMAP protocol. > > > > Some config opts: > > > > valid_chroot_dirs = /var/mail > > mail_chroot = /var/mail > > > > namespace { > > type = shared > > separator = / > > prefix = Shared/%%u/ > > location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u > > subscriptions = yes > > list = yes > > } > > > > plugin { > > acl = vfile:cache_secs=5 > > } > > > > plugin { > > acl_shared_dict = file:/var/mail/%i.db > > } > > > > protocol imap { > > mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib > > } > > > > > > My version of dovecot is 2.2.10. > > > > Regards > > Bambero > > > > > From tss at iki.fi Wed Jul 2 17:40:30 2014 From: tss at iki.fi (Timo Sirainen) Date: Wed, 2 Jul 2014 20:40:30 +0300 Subject: Bug in quota_get_status In-Reply-To: References: <53ABD9C6.9070801@qnipp.com> Message-ID: <74D0FE22-B226-495C-883D-E0E8DAC71E92@iki.fi> On 26.6.2014, at 18.10, Markus Gebert wrote: > > On 26.06.2014, at 10:28, Franz Knipp wrote: > >> the configuration option >> >> lmtp_rcpt_check_quota = yes > > I noticed that too, and my quick&dirty fix was to make quota_get_status() call quota_test_alloc() with size = 1, which fixes the problem as well. See patch below [1]. This should fix it properly: http://hg.dovecot.org/dovecot-2.2/rev/76d573ec5045 (Requires http://hg.dovecot.org/dovecot-2.2/rev/0d4de84a54f0) > I keep wondering why quota_is_over() does not just check ctx->*_over in the first place instead of doing math with ctx->*_used and ctx->*_ceil. It would seem so much easier. So either ctx->*over was added after quota_is_over() had been written, or this is an oversight, or there?s a specific reason the author did not use/trust ctx->*_over and preferred doing it in a more complicated way. Grepping trough the file, I see much more places the the ctx->*_used and ctx->*_ceil get updated compared to ctx->*_over, so that might indicate that the latter is only updated in specific cases, and cannot be trusted under all circumstances. Then again, I just took a short look at the quota code, so this hunch might me completely wrong. The problem is that within the same transaction it's possible to add/remove multiple mails. The *_ceil and *_over are set only once at the beginning of the transaction. From THerrmann at ADwin.de Wed Jul 2 14:25:59 2014 From: THerrmann at ADwin.de (Thomas Herrmann) Date: Wed, 02 Jul 2014 16:25:59 +0200 Subject: Flags in public folders disappear when more than 25 flags are used Message-ID: <53B41677.6080300@ADwin.de> Hello, I have been using flags in public folders for quite a while with no problems. Once the flags were added to all clients (Thunderbird), they were visible and synchronized properly. Now I have added some new flags, and in the dovecot-keywords files I see that I am now using more than 25 flags (in which case they are not stored using an additional letter in the filename). Now I see that newly added flags are only visible in the client for a short time and then suddenly disappear. How can I debug this, or what may be a reason for this? Regards Thomas Herrmann root at mailsrv2:~# dovecot --version 2.1.7 root at mailsrv2:~# dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.5 xfs disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_fsync = never mail_location = maildir:/home/vmail/adwin.de/%n/Maildir mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave imapflags namespace { inbox = yes location = prefix = separator = / subscriptions = yes type = private } namespace { list = children location = maildir:/home/vmail/public:INDEX=/home/vmail/adwin.de/%n/public prefix = ADwin/ separator = / subscriptions = no type = public } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile sieve = /home/vmail/adwin.de/%n/dovecot.sieve sieve_dir = /home/vmail/adwin.de/%n/sieve sieve_extensions = +imapflags +imap4flags } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } service imap-login { inet_listener imap { address = *,:: port = 56143 } inet_listener imaps { address = *,:: port = 56993 ssl = yes } service_count = 0 } service imap { vsz_limit = 512 M } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { executable = /usr/lib/dovecot/managesieve-login service_count = 0 } service managesieve { executable = /usr/lib/dovecot/managesieve } ssl_ca = From giedrius at su.lt Wed Jul 2 18:03:59 2014 From: giedrius at su.lt (=?UTF-8?B?R2llZHJpdXMgTGl1YmF2acSNaXVz?=) Date: Wed, 02 Jul 2014 21:03:59 +0300 Subject: Shared folders not listed by IMAP In-Reply-To: References: <53B3ED32.60504@su.lt> Message-ID: <53B4498F.9040202@su.lt> OK, This is the problem why your configuration is not working. My shared folder did not work up until I fixed auth-userdb permissions in a way so that user my A (not dovecot user) [test at mydomain.pl in your case] could connect to it and get info about user B [test2 at mydomain.pl in your case] Just change the auth-userdb file location (and probably permissions) or duplicate it to real root location. either from within configuration files or just as a plain symlink (maybe pre-login script ?) 2014.07.02 19:03, Bambero ra??: > But the problem is that I can't see shared folders to subscribe (shared by > other users) while connecting via IMAP. > > There is also an error: > Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No such > file or directory > > Probably becouse of chroot (/var/mail). > > > On Wed, Jul 2, 2014 at 1:29 PM, Giedrius Liubavi?ius wrote: > >> Hi, >> doveadm mailbox subscribe -u test at mydomain.pl Shared/test2 at mydomain.pl >> doveadm mailbox subscribe -u test at mydomain.pl >> Shared/test2 at mydomain.pl/Sent >> >> 2014.07.02 14:04, Bambero ra??: >>> Hello >>> >>> I just upgraded my system and there is a problem with shared mailboxes. >>> >>> When I use the doveadm command I can see shared folders: >>> >>> doveadm mailbox list -u 'test at mydomain.pl' >>> Drafts >>> Sent >>> Spam >>> Trash >>> Shared >>> Virtuals >>> Virtuals/all >>> Shared/test2 at mydomain.pl >>> Shared/test2 at mydomain.pl/Sent >>> INBOX >>> >>> But I can't see them over IMAP protocol. >>> >>> Some config opts: >>> >>> valid_chroot_dirs = /var/mail >>> mail_chroot = /var/mail >>> >>> namespace { >>> type = shared >>> separator = / >>> prefix = Shared/%%u/ >>> location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u >>> subscriptions = yes >>> list = yes >>> } >>> >>> plugin { >>> acl = vfile:cache_secs=5 >>> } >>> >>> plugin { >>> acl_shared_dict = file:/var/mail/%i.db >>> } >>> >>> protocol imap { >>> mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib >>> } >>> >>> >>> My version of dovecot is 2.2.10. >>> >>> Regards >>> Bambero >>> >> >> -------------- next part -------------- A non-text attachment was scrubbed... Name: giedrius.vcf Type: text/x-vcard Size: 197 bytes Desc: not available URL: From john.j.rowan.jr at gmail.com Wed Jul 2 19:21:03 2014 From: john.j.rowan.jr at gmail.com (=?utf-8?B?am9obi5qLnJvd2FuLmpyQGdtYWlsLmNvbQ==?=) Date: Wed, 02 Jul 2014 15:21:03 -0400 Subject: =?utf-8?B?UmU6IFNoYXJlZCBmb2xkZXJzIG5vdCBsaXN0ZWQgYnkgSU1BUA==?= Message-ID: <53b45ba1.4745e00a.0a44.4482@mx.google.com> Sent from my Verizon Wireless 4GLTE smartphone ----- Reply message ----- From: "Giedrius Liubavi?ius" To: Subject: Shared folders not listed by IMAP Date: Wed, Jul 2, 2014 14:03 OK, This is the problem why your configuration is not working. My shared folder did not work up until I fixed auth-userdb permissions in a way so that user my A (not dovecot user) [test at mydomain.pl in your case] could connect to it and get info about user B [test2 at mydomain.pl in your case] Just change the auth-userdb file location (and probably permissions) or duplicate it to real root location. either from within configuration files or just as a plain symlink (maybe pre-login script ?) 2014.07.02 19:03, Bambero ra??: > But the problem is that I can't see shared folders to subscribe (shared by > other users) while connecting via IMAP. > > There is also an error: > Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No such > file or directory > > Probably becouse of chroot (/var/mail). > > > On Wed, Jul 2, 2014 at 1:29 PM, Giedrius Liubavi?ius wrote: > >> Hi, >> doveadm mailbox subscribe -u test at mydomain.pl Shared/test2 at mydomain.pl >> doveadm mailbox subscribe -u test at mydomain.pl >> Shared/test2 at mydomain.pl/Sent >> >> 2014.07.02 14:04, Bambero ra??: >>> Hello >>> >>> I just upgraded my system and there is a problem with shared mailboxes. >>> >>> When I use the doveadm command I can see shared folders: >>> >>> doveadm mailbox list -u 'test at mydomain.pl' >>> Drafts >>> Sent >>> Spam >>> Trash >>> Shared >>> Virtuals >>> Virtuals/all >>> Shared/test2 at mydomain.pl >>> Shared/test2 at mydomain.pl/Sent >>> INBOX >>> >>> But I can't see them over IMAP protocol. >>> >>> Some config opts: >>> >>> valid_chroot_dirs = /var/mail >>> mail_chroot = /var/mail >>> >>> namespace { >>> type = shared >>> separator = / >>> prefix = Shared/%%u/ >>> location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u >>> subscriptions = yes >>> list = yes >>> } >>> >>> plugin { >>> acl = vfile:cache_secs=5 >>> } >>> >>> plugin { >>> acl_shared_dict = file:/var/mail/%i.db >>> } >>> >>> protocol imap { >>> mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib >>> } >>> >>> >>> My version of dovecot is 2.2.10. >>> >>> Regards >>> Bambero >>> >> >> From john.j.rowan.jr at gmail.com Wed Jul 2 19:21:12 2014 From: john.j.rowan.jr at gmail.com (=?utf-8?B?am9obi5qLnJvd2FuLmpyQGdtYWlsLmNvbQ==?=) Date: Wed, 02 Jul 2014 15:21:12 -0400 Subject: =?utf-8?B?UmU6IFNoYXJlZCBmb2xkZXJzIG5vdCBsaXN0ZWQgYnkgSU1BUA==?= Message-ID: <53b45baa.441d8c0a.422d.4bab@mx.google.com> . t,yV e Sent from my Verizon Wireless 4GLTE smartphone ----- Reply message ----- From: "Giedrius Liubavi?ius" To: Subject: Shared folders not listed by IMAP Date: Wed, Jul 2, 2014 14:03 OK, This is the problem why your configuration is not working. My shared folder did not work up until I fixed auth-userdb permissions in a way so that user my A (not dovecot user) [test at mydomain.pl in your case] could connect to it and get info about user B [test2 at mydomain.pl in your case] Just change the auth-userdb file location (and probably permissions) or duplicate it to real root location. either from within configuration files or just as a plain symlink (maybe pre-login script ?) 2014.07.02 19:03, Bambero ra??: > But the problem is that I can't see shared folders to subscribe (shared by > other users) while connecting via IMAP. > > There is also an error: > Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No such > file or directory > > Probably becouse of chroot (/var/mail). > > > On Wed, Jul 2, 2014 at 1:29 PM, Giedrius Liubavi?ius wrote: > >> Hi, >> doveadm mailbox subscribe -u test at mydomain.pl Shared/test2 at mydomain.pl >> doveadm mailbox subscribe -u test at mydomain.pl >> Shared/test2 at mydomain.pl/Sent >> >> 2014.07.02 14:04, Bambero ra??: >>> Hello >>> >>> I just upgraded my system and there is a problem with shared mailboxes. >>> >>> When I use the doveadm command I can see shared folders: >>> >>> doveadm mailbox list -u 'test at mydomain.pl' >>> Drafts >>> Sent >>> Spam >>> Trash >>> Shared >>> Virtuals >>> Virtuals/all >>> Shared/test2 at mydomain.pl >>> Shared/test2 at mydomain.pl/Sent >>> INBOX >>> >>> But I can't see them over IMAP protocol. >>> >>> Some config opts: >>> >>> valid_chroot_dirs = /var/mail >>> mail_chroot = /var/mail >>> >>> namespace { >>> type = shared >>> separator = / >>> prefix = Shared/%%u/ >>> location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u >>> subscriptions = yes >>> list = yes >>> } >>> >>> plugin { >>> acl = vfile:cache_secs=5 >>> } >>> >>> plugin { >>> acl_shared_dict = file:/var/mail/%i.db >>> } >>> >>> protocol imap { >>> mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib >>> } >>> >>> >>> My version of dovecot is 2.2.10. >>> >>> Regards >>> Bambero >>> >> >> From toml at engr.orst.edu Wed Jul 2 21:08:52 2014 From: toml at engr.orst.edu (Tom Lieuallen) Date: Wed, 02 Jul 2014 14:08:52 -0700 Subject: dovecot 2.2.13 core dump (signal 11) In-Reply-To: <53A27CC7.80503@engr.orst.edu> References: <53A27CC7.80503@engr.orst.edu> Message-ID: <53B474E4.8030902@engr.orst.edu> This problem is now affecting more than just that one user. The 2nd (at least) victim is myself, so this problem is now more urgent. Any thoughts on this? Should I start familiarizing myself with source code, or just downgrade to 2.1.16 again? I hate going backward. :-( thank you Tom L On 6/18/14, 11:01 PM, Tom Lieuallen wrote: > We just upgraded from 2.1.16 to 2.2.13. One user is experiencing > problems when using the shared namespace. Specifically it happens when > opening/reading a message and when deleting messages. These functions > work for other users. So far, this appears to be only affecting one user. > > The shared folder is a local ext4 file system and utilizes acls > > # 2.2.13: /private/dovecot/etc/dovecot/dovecot.conf > doveconf: Warning: service auth { client_limit=1000 } is lower than > required under max. load (15360) > doveconf: Warning: service anvil { client_limit=1000 } is lower than > required under max. load (10243) > # OS: Linux 2.6.32-358.11.1.el6.x86_64 x86_64 Red Hat Enterprise Linux > Server release 6.5 (Santiago) > default_process_limit = 5120 > first_valid_uid = 100 > listen = * > mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=/a2/imap-index/%u > mail_plugins = quota acl > namespace { > hidden = yes > inbox = no > list = children > location = maildir:/a1/dove-shared:INDEX=/a2/imap-index/dove-shared/%u > prefix = sharedimap/ > separator = / > type = shared > } > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = /private/dovecot/etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > } > passdb { > args = scheme=CRYPT username_format=%u /private/dovecot/etc/passwd > driver = passwd-file > } > plugin { > acl = vfile > quota = fs:INBOX:mount=/a1 > quota2 = fs:Home quota:mount=%h > } > protocols = imap lmtp > service imap-login { > service_count = 1 > } > service imap { > process_limit = 2048 > } > ssl_cert = ssl_key = userdb { > args = /private/dovecot/etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > } > userdb { > args = username_format=%u /private/dovecot/etc/passwd > driver = passwd-file > } > protocol imap { > mail_max_userip_connections = 20 > } > > > Here's the backtrace in gdb. > > Core was generated by `dovecot/imap'. > Program terminated with signal 11, Segmentation fault. > #0 acl_mailbox_right_lookup (box=0x12e6730, right_idx=7) at > acl-mailbox.c:40 > 40 if (abox->skip_acl_checks) > Missing separate debuginfos, use: debuginfo-install > glibc-2.12-1.132.el6_5.2.x86_64 sssd-client-1.9.2-129.el6.x86_64 > (gdb) bt full > #0 acl_mailbox_right_lookup (box=0x12e6730, right_idx=7) at > acl-mailbox.c:40 > abox = 0x0 > alist = > ret = > #1 0x00007f4c11604d06 in acl_copy_has_rights (ctx=0x12f9810, > mail=0x12f5030) > at acl-mailbox.c:409 > destbox = 0x12edf90 > save_right = > #2 acl_copy (ctx=0x12f9810, mail=0x12f5030) at acl-mailbox.c:430 > t = > abox = 0x12ee5f8 > #3 0x00007f4c11b741ed in mailbox_copy (_ctx=, > mail=0x12f5030) at mail-storage.c:2149 > ctx = 0x12f9810 > t = 0x12f32d0 > keywords = 0x12f9b80 > pvt_flags = 0 > backend_mail = 0x12f5030 > ret = > __FUNCTION__ = "mailbox_copy" > #4 0x00007f4c11b742dd in mailbox_move (_ctx=, > mail=0x12f5030) at mail-storage.c:2170 > ctx = 0x12f9810 > #5 0x000000000040c587 in fetch_and_copy (cmd=0x12e3f10, move=true) > at cmd-copy.c:67 > search_ctx = 0x12f4db0 > src_trans = 0x12f4090 > srcset_ctx = {str = 0x12bf328, first_uid = 0, last_uid = > 4294967295} > ret = 1 > save_ctx = 0x0 > mail = 0x12f5030 > copy_count = 1 > src_uidset = 0x12bf328 > #6 cmd_copy_full (cmd=0x12e3f10, move=true) at cmd-copy.c:123 > client = 0x12e3330 > dest_storage = > destbox = 0x12edf90 > t = 0x12f32d0 > src_trans = > search_args = 0x12ecf80 > messageset = 0x12cac10 "112850,112871,112903:112905,112919" > mailbox = 0x12cac38 "Trash" > src_uidset = > sync_flags = 0 > imap_flags = 0 > changes = {pool = 0x12e6730, uid_validity = 19807984, > saved_uids = { > > > (I'm not sure how much more info is needed; let me know if more...) > > thank you > > Tom Lieuallen From uothrawn at yahoo.com Wed Jul 2 21:36:35 2014 From: uothrawn at yahoo.com (G H) Date: Wed, 2 Jul 2014 14:36:35 -0700 Subject: doveadm director userdb Message-ID: <1404336995.66126.YahooMailNeo@web161406.mail.bf1.yahoo.com> How do you configure an iterate_query SQL lookup for the doveadm director? I tried: service director { ?userdb { ? ... ?} } but userdb is not a valid stanza for director. I do not have a default userdb stanza, all my userdb definitions are specified in service imap/lda/lmtp blocks. Thanks. G H From Dovecot-mailing-list at whyaskwhy.org Thu Jul 3 02:28:25 2014 From: Dovecot-mailing-list at whyaskwhy.org (deoren) Date: Wed, 02 Jul 2014 21:28:25 -0500 Subject: Mailboxes are in Maildir format. Any good backup tips? Had success with version control? In-Reply-To: References: Message-ID: <53B4BFC9.6020808@whyaskwhy.org> On 6/30/2014 5:28 PM, deoren wrote: > I'm still pretty new to running a mail server, but one thing I've come > to appreciate over the years is a good backup strategy. Since I have > always run my own servers for practice and for personal use I don't have > access to Enterprise backup solutions. Because of that I usually just > fall back to scripts and tarballs and offload the content on a regular > basis. > > Right now I'm using LVM snapshots + tarballs for daily backups, but I'd > like to get better coverage for incremental changes that occur > throughout the day. The size of existing content is low, but (small) > changes are frequent. > > I went with Maildir format because based on my reading it is referred to > as time tested and corruption resistant. Because individual emails are > stored as separate files this also leads me to believe that a version > control system (Git, SVN) would allow for easy point in time restores. > > I'm also going to research the GNU tar utility's support for incremental > archives as that sounds promising. > > Suggestions and warnings are most welcome. > > Thanks! > Sorry for the late reply, and thanks to everyone who replied with suggestions. I appreciate you taking the time to do that and you've given me a lot of good ideas to look over. Options are good! From franz at qnipp.com Thu Jul 3 06:40:34 2014 From: franz at qnipp.com (Franz Knipp) Date: Thu, 03 Jul 2014 08:40:34 +0200 Subject: Bug in quota_get_status In-Reply-To: <74D0FE22-B226-495C-883D-E0E8DAC71E92@iki.fi> References: <53ABD9C6.9070801@qnipp.com> <74D0FE22-B226-495C-883D-E0E8DAC71E92@iki.fi> Message-ID: <53B4FAE2.7090207@qnipp.com> Am 2014-07-02 19:40, schrieb Timo Sirainen: > This should fix it properly: > http://hg.dovecot.org/dovecot-2.2/rev/76d573ec5045 (Requires > http://hg.dovecot.org/dovecot-2.2/rev/0d4de84a54f0) Ok. Thanks. When do you plan to release the next stable version (containing these fixes)? > The problem is that within the same transaction it's possible to > add/remove multiple mails. The *_ceil and *_over are set only once at > the beginning of the transaction. Thanks for the explanation. In the case of LMTP, this doesn't matter :-) -- Franz Knipp, +43 664 3980169 qnipp GmbH, Hauptstra?e 54, 7064 Oslip, ?sterreich http://qnipp.com http://qnipp.com/qnipp.vcf From nick.z.edwards at gmail.com Thu Jul 3 07:13:04 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Thu, 3 Jul 2014 17:13:04 +1000 Subject: number of users In-Reply-To: <1404309695543-48701.post@n4.nabble.com> References: <1404309695543-48701.post@n4.nabble.com> Message-ID: Yes there is, kind of, if you use imapproxy (you should be if you run a busy server) it will cache logins for n* time, then doveadm using the IP of the webmail will show them. On 7/3/14, ihab wrote: > Hello, > i using roundcube with dovecot, i have a question if there is possible to > know the number of users that using the mail system (in other word the > online users) . > thanks, > best regards, > ihab :) > > > > -- > View this message in context: > http://dovecot.2317879.n4.nabble.com/number-of-users-tp48701.html > Sent from the Dovecot mailing list archive at Nabble.com. > From jerry at seibercom.net Thu Jul 3 10:36:10 2014 From: jerry at seibercom.net (Jerry) Date: Thu, 3 Jul 2014 06:36:10 -0400 Subject: stripping extension from domain name Message-ID: <20140703063610.4874f7aa@scorpio> Thu, 3 Jul 2014 06:29:06 -0400 I know that the "%d" parameter is for the domain. Is there any way to use just the domain name sans its extension. EXAMPLE: example.com ==> example Also, I have a lot of logging going on in my dovecot log file. I want to limit it to just the barest amount, such as indicting what mail box mail was delivered to. Authentication errors, etcetera should only be shown if an error occurs. Is this possible? Thanks! -- Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: From aellert at numeezy.com Thu Jul 3 12:05:50 2014 From: aellert at numeezy.com (Alexandre Ellert) Date: Thu, 03 Jul 2014 14:05:50 +0200 Subject: postfix alias and dovecot quota In-Reply-To: References: <5068E3FB-381B-4EDA-B40A-6D8943D797F9@numeezy.com> <53B14BF6.3000206@thinline.cz> Message-ID: <902975FA-1D99-4016-9F03-F5054A8BFCC7@numeezy.com> Le 1 juil. 2014 ? 04:57, Nick Edwards a ?crit : > http://dovecot.2317879.n4.nabble.com/Postfix-aliases-with-quota-status-service-td43511.html > search for post from Ulrich Zehl Thanks for the link, I use a SQL backend containing user and alias data. So I've changed the user_query to include alias and it's actually working fine on my test environnement. From HFlor at gmx.de Thu Jul 3 12:52:30 2014 From: HFlor at gmx.de (Hardy Flor) Date: Thu, 03 Jul 2014 14:52:30 +0200 Subject: imap(hardy): Panic: file istream-tee.c: line 138 (i_stream_tee_read): assertion failed: (last_high_offset == input->v_offset + size) Message-ID: <53B5520E.8050304@gmx.de> Hello, I'm copy with imapsync (on the new server with dovecot) with a single user all mails from a old server to the new server. The error-message ist after 20-30 minutes in the log, and I must restart the imapsync. The next mail is normal store on the destination box. Hardy From crohmann at netcologne.de Thu Jul 3 14:55:35 2014 From: crohmann at netcologne.de (Christian Rohmann) Date: Thu, 03 Jul 2014 16:55:35 +0200 Subject: [Dovecot] zlib maildir reindex broken In-Reply-To: <530491FE-0E95-4FCA-9B6C-B2175DC52513@iki.fi> References: <3CE707A9-5DA4-4B34-9F70-79FBEE11B118@tucows.com> <530491FE-0E95-4FCA-9B6C-B2175DC52513@iki.fi> Message-ID: <53B56EE7.5060101@netcologne.de> Hey Timo, On 02.05.2014 12:37, Timo Sirainen wrote: >> During a reindex maildir_mail_get_received_date() does an i_stream_stat on the the i_stream_seekable stream created in zlib_mail_cache_open, but this istream does not know about the original maildir message file and always returns the current time for the file's stat times. >> This is also broken on initial index, but if mail is indexed when it's received (ours isn't) it coincidentally gets the right time. > > Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/9f1460682295 It seems this is unfortunately also broken in 2.1.17. If possible could you also provide a fix for the 2.1.x tree, as we are still happily running your code from that era. Your fix for 2.2 does sadly not apply without modifications and I don't want to destroy things with incompetent attempts to do production grade C coding ;-) With regards from Cologne, Christian From tss at iki.fi Thu Jul 3 15:47:14 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 18:47:14 +0300 Subject: imap(hardy): Panic: file istream-tee.c: line 138 (i_stream_tee_read): assertion failed: (last_high_offset == input->v_offset + size) In-Reply-To: <53B5520E.8050304@gmx.de> References: <53B5520E.8050304@gmx.de> Message-ID: On 3.7.2014, at 15.52, Hardy Flor wrote: > I'm copy with imapsync (on the new server with dovecot) with a single user all mails from a old server to the new server. > > The error-message ist after 20-30 minutes in the log, and I must restart the imapsync. The next mail is normal store on the destination box. What Dovecot version? Can you get a gdb backtrace? http://dovecot.org/bugreport.html From tss at iki.fi Thu Jul 3 16:13:01 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 19:13:01 +0300 Subject: dovecot 2.2.13 core dump (signal 11) In-Reply-To: <53A27CC7.80503@engr.orst.edu> References: <53A27CC7.80503@engr.orst.edu> Message-ID: <0C410630-E24C-4E61-85A2-E8A4C89B311C@iki.fi> On 19.6.2014, at 9.01, Tom Lieuallen wrote: > namespace { > hidden = yes > inbox = no > list = children > location = maildir:/a1/dove-shared:INDEX=/a2/imap-index/dove-shared/%u > prefix = sharedimap/ > separator = / > type = shared > } type=shared namespaces are meant for mailboxes that users share among each others. Use type=public for this. That should fix the crash. It's also fixed in hg. From tss at iki.fi Thu Jul 3 16:28:18 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 19:28:18 +0300 Subject: indexer failure: lucene: while doing doveadm commands In-Reply-To: <20140701153217.GA58803@thebighonker.lerctr.org> References: <20140701153217.GA58803@thebighonker.lerctr.org> Message-ID: <62BFE2B8-13B8-468D-B8F7-2F8F831697F9@iki.fi> On 1.7.2014, at 18.32, Larry Rosenman wrote: > Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable > Jul 1 00:30:00 thebighonker dovecot: indexer-worker(ler): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) .. > mail_location = mbox:~/mail:INBOX=~/mail/INBOX Fixed: http://hg.dovecot.org/dovecot-2.2/rev/120b2a1645d8 From tss at iki.fi Thu Jul 3 16:30:57 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 19:30:57 +0300 Subject: Crash in service imap with version 2.2.13 In-Reply-To: <53A9397F.6060008@enas.net> References: <53A9397F.6060008@enas.net> Message-ID: On 24.6.2014, at 11.40, Urban Loesch wrote: > yesterday I upgraded to version 2.2.13 under Debian Squeeze. .. > #0 mail_index_strmap_uid_exists (ctx=0x7ffffd33d9f0, uid=8442) at mail-index-strmap.c:395 > 395 mail-index-strmap.c: No such file or directory. > in mail-index-strmap.c .. > # 2.2.13 (38cd37cea8b1): /etc/dovecot/dovecot.conf Note that it's not the v2.2.13 release, it's a recent snapshot from hg. This should fix the crash anyway: http://hg.dovecot.org/dovecot-2.2/rev/d25443778208 From tss at iki.fi Thu Jul 3 16:58:01 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 19:58:01 +0300 Subject: [UPDATE]: Another Crash in service imap with version 2.2.13 - Debian Wheezy In-Reply-To: <53AC1BD6.6020801@enas.net> References: <53ABCAE7.3020208@enas.net> <53AC1BD6.6020801@enas.net> Message-ID: <57994496-95F8-4789-AD2B-E5AB7B29B415@iki.fi> On 26.6.2014, at 16.10, Urban Loesch wrote: > #1 0x00007fbf26650c44 in mailbox_save_cancel (_ctx=) at mail-storage.c:2116 > ctx = 0xa95500 > keywords = 0x0 > mail = > #2 0x00007fbf2665104f in mailbox_save_begin (ctx=ctx at entry=0x7fff64b53048, input=0xaaaea0) at mail-storage.c:2041 > box = 0xa6f800 > ret = > #3 0x00007fbf26648bb6 in mail_storage_try_copy (mail=0xa90d20, _ctx=0x7fff64b53048) at mail-copy.c:76 > ctx = 0xa95500 > pmail = 0xa90d20 > input = 0xaaaea0 > #4 mail_storage_copy (ctx=0x0, mail=0xa90d20) at mail-copy.c:101 > No locals. > #5 0x00007fbf24f12679 in notify_copy (ctx=0xa95500, mail=0xa90d20) at notify-storage.c:107 > lt = 0xa8bdd0 > lbox = 0xa70870 > ret = > #6 0x00007fbf2573d06b in acl_copy (ctx=0xa95500, mail=0xa90d20) at acl-mailbox.c:435 > t = > abox = 0xa6fe48 > #7 0x00007fbf26650e8d in mailbox_copy (_ctx=_ctx at entry=0x7fff64b53190, mail=0xa90d20) at mail-storage.c:2152 > ctx = 0xa95500 > t = 0xa8de20 > keywords = 0x0 > pvt_flags = 0 > backend_mail = 0xa90d20 > ret = > __FUNCTION__ = "mailbox_copy" The client is trying to use COPY or MOVE command, but the copying fails for some reason and the cleanup code crashes. I can't reproduce this though, so would be helpful to know what exactly it's doing. So getting the gdb output for these commands (instead of just bt full) would help: p *ctx p *ctx.dest_mail f 7 p (*_ctx).transaction.box.vname p (*_ctx).transaction.box.storage.error_string p mail.box.vname From tss at iki.fi Thu Jul 3 17:31:25 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 20:31:25 +0300 Subject: question on lmtp logged message In-Reply-To: <53AAEE8D.9050604@solutti.com.br> References: <53AAEE8D.9050604@solutti.com.br> Message-ID: On 25.6.2014, at 18.45, Leonardo Rodrigues wrote: > I have dovecot running for IMAP4/POP3 and also local delivery through LMTP. It's working just fine, absolutely no problem on that, setup is fine. > > Anyway, sometimes LMTP seems to not be able to deliver some messages and keep them on postfixqueue. And on the next or third try, the message gets delivered successfully. The logged message, however, is not helping me identify what is happening.Example: > > (error - message was expunged) > Jun 25 11:49:39 correio postfix/lmtp[21835]: ADB0A1AC05108: to=, relay=correio.domain.com.br[private/dovecot-lmtp], conn_use=6, delay=13, delays=0.07/0/0/13, dsn=4.2.0, status=deferred (host correio.domain.com.br[private/dovecot-lmtp] said: 451 4.2.0 Message was expunged (received-date) (in reply to end of DATA command)) I guess the only good fix for this is to just get rid of this deduplication feature for now: http://hg.dovecot.org/dovecot-2.2/rev/51274bf2a47d Hopefully people don't rely on this feature too much. From tss at iki.fi Thu Jul 3 17:34:48 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 20:34:48 +0300 Subject: BUG: segfault in auth when user listed multiple times in LDAP In-Reply-To: <53AD4667.8000102@linguamatics.com> References: <53AD4667.8000102@linguamatics.com> Message-ID: <24D28CEC-4289-49F5-89D4-95D761BD0C11@iki.fi> On 27.6.2014, at 13.24, Laszlo Toth wrote: > I think I found a bug in the auth module. It can be triggered when the userdb is in LDAP and an user is found multiple times in LDAP. > > Dovecot version 2.2.10 (from ATrpms Testing) running on CentOS 6.5 x64. > > Jun 27 10:34:34 server dovecot: auth: Debug: ldap(USER): user search: base=dc=linguamatics,dc=com scope=subtree filter=( & (uid=user) (| (&(objectClass=posixAccount)(|(employeeType=staff)(employeeType=guest))) (objectClass=account) ) ) fields=uid > Jun 27 10:34:34 server kernel: auth[15916]: segfault at 8 ip 00007f45e5aa9bef sp 00007fff5b17e210 error 4 in libauthdb_ldap.so[7f45e5aa4000+a000] > Jun 27 10:34:34 server dovecot: auth: Error: ldap(user): LDAP search returned multiple entries > Jun 27 10:34:34 server dovecot: auth: Debug: ldap(user): no fields returned by the server > Jun 27 10:34:35 server abrtd: Directory 'ccpp-2014-06-27-10:34:34-15916' creation detected > Jun 27 10:34:35 server abrt[16137]: Saved core dump of pid 15916 (/usr/libexec/dovecot/auth) to /var/spool/abrt/ccpp-2014-06-27-10:34:34-15916 (2863104 bytes) > Jun 27 10:34:35 server dovecot: doveadm(user): Error: userdb lookup(user): Disconnected unexpectedly > Jun 27 10:34:35 server dovecot: doveadm(user): Error: sync: User lookup failed: Internal error occurred. Refer to server log for more information. > Jun 27 10:34:35 server dovecot: auth: Fatal: master: service(auth): child 15916 killed with signal 11 (core dumped) Doesn't crash in latest hg, so I guess this is fixed already. From bind at enas.net Thu Jul 3 17:51:24 2014 From: bind at enas.net (Urban Loesch) Date: Thu, 03 Jul 2014 19:51:24 +0200 Subject: [UPDATE]: Another Crash in service imap with version 2.2.13 - Debian Wheezy In-Reply-To: <57994496-95F8-4789-AD2B-E5AB7B29B415@iki.fi> References: <53ABCAE7.3020208@enas.net> <53AC1BD6.6020801@enas.net> <57994496-95F8-4789-AD2B-E5AB7B29B415@iki.fi> Message-ID: <53B5981C.8070804@enas.net> Hi, Am 03.07.2014 18:58, schrieb Timo Sirainen: > On 26.6.2014, at 16.10, Urban Loesch wrote: > > The client is trying to use COPY or MOVE command, but the copying fails for some reason and the cleanup code crashes. I can't reproduce this though, so would be helpful to know what exactly it's doing. So getting the gdb output for these commands (instead of just bt full) would help: > > p *ctx > p *ctx.dest_mail > f 7 > p (*_ctx).transaction.box.vname > p (*_ctx).transaction.box.storage.error_string > p mail.box.vname > After some days the customer begans to complain, that he is not able read his mails with his IPhone. So I decided to delete his account and reinstalled it on the IPhone, since that it works without error. Unfortunately now I switched to the latest hg version so I don't have the affected "imap" binary any more. But I have the core file from the latest crash. If you would like I can send it to you off list. Many Thanks Urban From larryrtx at gmail.com Thu Jul 3 17:55:03 2014 From: larryrtx at gmail.com (Larry Rosenman) Date: Thu, 3 Jul 2014 12:55:03 -0500 Subject: [Dovecot] fts_lucene - hiding lucene-indexes folder? In-Reply-To: <536D127D.7060706@sys4.de> References: <536D0F56.20205@sys4.de> <536D127D.7060706@sys4.de> Message-ID: Timo, Is there any chance of this happening (making lucene-indexes \NOSELECT)? On Fri, May 9, 2014 at 12:38 PM, Robert Schetterer wrote: > Am 09.05.2014 19:27, schrieb Larry Rosenman: > > I'm using mbox, so it DOES show up. > > > > thebighonker.lerctr.org /home/ler $ > > more /tmp/doveconf.n.out > > > > # 2.2.12: /usr/local/etc/dovecot/dovecot.conf > > > > # OS: FreeBSD 10.0-STABLE amd64 > > > > auth_default_realm = lerctr.org > > > > auth_mechanisms = plain login > > > > auth_realms = lerctr.org thebighonker.lerctr.org > > tbh.lerctr.org > > > > auth_username_format = %Ln > > > > disable_plaintext_auth = no > > > > lda_mailbox_autocreate = yes > > > > lmtp_save_to_detail_mailbox = yes > > > > login_access_sockets = tcpwrap > > > > mail_debug = yes > > > > mail_location = mbox:~/mail:INBOX=~/mail/INBOX > > > > mail_plugins = snarf fts fts_lucene stats > > > > mail_privileged_group = mail > > > > managesieve_notify_capability = mailto > > > > managesieve_sieve_capability = fileinto reject envelope > > encoded-character vacation subaddress comparator-i;ascii-numeric > > relational regex imap4flags copy include variables body enotify > > environment mailbox date ihave > > > > namespace Snarf { > > > > hidden = yes > > > > list = no > > > > location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=MEMORY > > > > prefix = ~~Snarfbox/ > > > > separator = / > > > > } > > > > namespace archive { > > > > hidden = no > > > > inbox = no > > > > list = no > > > > location = mbox:~/MAILARCHIVE > > > > prefix = "#ARCHIVE/" > > > > separator = / > > > > } > > > > namespace default { > > > > hidden = yes > > > > list = no > > > > location = > > > > prefix = ~~default/ > > > > separator = / > > > > } > > > > namespace inbox { > > > > inbox = yes > > > > location = > > > > mailbox Drafts { > > > > special_use = \Drafts > > > > } > > > > mailbox INBOX { > > > > auto = create > > > > } > > > > mailbox Junk { > > > > special_use = \Junk > > > > } > > > > mailbox Sent { > > > > special_use = \Sent > > > > } > > > > mailbox "Sent Messages" { > > > > special_use = \Sent > > > > } > > > > mailbox Trash { > > > > special_use = \Trash > > > > } > > > > prefix = > > > > } > > > > passdb { > > > > args = failure_show_msg=yes session=yes max_requests=20 > > > > driver = pam > > > > } > > > > plugin { > > > > fts = lucene > > > > fts_lucene = whitespace_chars=@. normalize no_snowball > > > > mbox_snarf = ~/mail/INBOX > > > > sieve = ~/.dovecot.sieve > > > > sieve_dir = ~/sieve > > > > snarf = ~~Snarfbox/INBOX > > > > stats_command_min_time = 1 mins > > > > stats_domain_min_time = 12 hours > > > > stats_ip_min_time = 12 hours > > > > stats_memory_limit = 16 M > > > > stats_refresh = 5s > > > > stats_session_min_time = 15 mins > > > > stats_track_cmds = yes > > > > stats_user_min_time = 1 hours > > > > } > > > > service auth { > > > > unix_listener auth-client { > > > > mode = 0666 > > > > } > > > > unix_listener auth-master { > > > > mode = 0666 > > > > } > > > > } > > > > service stats { > > > > chroot = empty > > > > client_limit = 0 > > > > drop_priv_before_exec = no > > > > executable = stats > > > > extra_groups = > > > > fifo_listener stats-mail { > > > > group = > > > > mode = 0666 > > > > user = > > > > } > > > > group = > > > > idle_kill = 4294967295 secs > > > > privileged_group = > > > > process_limit = 1 > > > > process_min_avail = 0 > > > > protocol = > > > > service_count = 0 > > > > type = > > > > unix_listener stats { > > > > group = > > > > mode = 0666 > > > > user = > > > > } > > > > user = $default_internal_user > > > > vsz_limit = 18446744073709551615 B > > > > } > > > > service tcpwrap { > > > > unix_listener login/tcpwrap { > > > > group = $default_login_user > > > > mode = 0600 > > > > user = $default_login_user > > > > } > > > > } > > > > ssl_cert = > > > ssl_key = > > > userdb { > > > > driver = passwd > > > > } > > > > protocol imap { > > > > imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags > > > > mail_max_userip_connections = 50 > > > > mail_plugins = snarf fts fts_lucene stats imap_stats > > > > } > > i am not using mbox , didnt analyse your conf very deeply > but my bet is ,your namespace and/or directory layout setup is the problem > > > perhaps reread > > http://wiki2.dovecot.org/MboxChildFolders?highlight=%28index%29 > > http://wiki2.dovecot.org/Plugins/FTS/Lucene > > Requires Dovecot v2.1+ to work properly. The CLucene version must be > v2.3 (not v0.9). Dovecot builds only a single Lucene index for all > mailboxes. The Lucene indexes are stored in lucene-indexes/ directory > under the mail root index directory (e.g. ~/Maildir/lucene-indexes/). > > so perhaps you need configure index directory seperate/extra setting etc > > > > > thebighonker.lerctr.org /home/ler $ > > > > > > > > On Fri, May 9, 2014 at 12:24 PM, Robert Schetterer > > wrote: > > > > Am 09.05.2014 18:20, schrieb Nicholas Riley: > > > Hi, > > > > > > Is there any way to hide this folder from IMAP clients? I can see > > it is > > > not runtime configurable and just #defined as > LUCENE_INDEX_DIR_NAME in > > > fts-backend-lucene.c. > > > > > > > you shouldnt see it, guess you configured something wrong like > > > > i.e > > > > maildir_stat_dirs=no (default): Assume that all the files beginning > with > > a dot in the maildir are maildirs. You shouldn't have any > non-directory > > files beginning with a dot in the maildirs, but if you do you may > need > > to set this to "yes", in which case Dovecot needs to stat() each > > directory entry, which degrades the performance. Some filesystems > > provide the directory/non-directory status for free without having to > > stat(). In those filesystems this setting is ignored. > > > > etc > > > > post your full dove conf to give chance for analysis > > > > > > > > Best Regards > > MfG Robert Schetterer > > > > -- > > [*] sys4 AG > > > > http://sys4.de, +49 (89) 30 90 46 64 > > > > Franziskanerstra?e 15, 81669 M?nchen > > > > Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 > > Vorstand: Patrick Ben Koetter, Marc Schiffbauer > > Aufsichtsratsvorsitzender: Florian Kirstein > > > > > > > > > > -- > > Larry Rosenman http://www.lerctr.org/~ler > > Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com > > > > US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 > > > > Best Regards > MfG Robert Schetterer > > -- > [*] sys4 AG > > http://sys4.de, +49 (89) 30 90 46 64 > Franziskanerstra?e 15, 81669 M?nchen > > Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 > Vorstand: Patrick Ben Koetter, Marc Schiffbauer > Aufsichtsratsvorsitzender: Florian Kirstein > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 From rs at sys4.de Thu Jul 3 17:56:53 2014 From: rs at sys4.de (Robert Schetterer) Date: Thu, 03 Jul 2014 19:56:53 +0200 Subject: [Dovecot] zlib maildir reindex broken In-Reply-To: <53B56EE7.5060101@netcologne.de> References: <3CE707A9-5DA4-4B34-9F70-79FBEE11B118@tucows.com> <530491FE-0E95-4FCA-9B6C-B2175DC52513@iki.fi> <53B56EE7.5060101@netcologne.de> Message-ID: <53B59965.6010809@sys4.de> Am 03.07.2014 16:55, schrieb Christian Rohmann: > Hey Timo, > > On 02.05.2014 12:37, Timo Sirainen wrote: >>> During a reindex maildir_mail_get_received_date() does an i_stream_stat on the the i_stream_seekable stream created in zlib_mail_cache_open, but this istream does not know about the original maildir message file and always returns the current time for the file's stat times. >>> This is also broken on initial index, but if mail is indexed when it's received (ours isn't) it coincidentally gets the right time. >> >> Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/9f1460682295 > > It seems this is unfortunately also broken in 2.1.17. > > If possible could you also provide a fix for the 2.1.x tree, as we are > still happily running your code from that era. Your fix for 2.2 does > sadly not apply without modifications and I don't want to destroy things > with incompetent attempts to do production grade C coding ;-) > > > > With regards from Cologne, > > > Christian > I strongly vote for a 2.1.18 including such fix Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From tss at iki.fi Thu Jul 3 17:57:09 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 20:57:09 +0300 Subject: IMAP sessions quit when calling MYRIGHTS on shared namespace In-Reply-To: <53AA763E.3070305@qnipp.com> References: <53AA763E.3070305@qnipp.com> Message-ID: On 25.6.2014, at 10.11, Franz Knipp wrote: > the IMAP connection is dropped, when I call MYRIGHTS on the root of my > shared folders. > > . MYRIGHTS shared Fixed: http://hg.dovecot.org/dovecot-2.2/rev/5f21c78cd7b2 From tss at iki.fi Thu Jul 3 17:58:27 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 20:58:27 +0300 Subject: Dsync replication one-way In-Reply-To: <53A99381.6040504@gmail.com> References: <53A99381.6040504@gmail.com> Message-ID: On 24.6.2014, at 18.04, Muriel wrote: > Hi all, > I know that I can do a backup using doveadm: > doveadm backup -u user ssh backup.server doveadm dsync-server -u user > > But it's possible to use replicator service to do the same job? Or dsync with replicator can only be used in a two-way environment? You could try adding -1 to replication_dsync_parameters setting, but I'm not sure if that actually works or not. From tss at iki.fi Thu Jul 3 18:02:05 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 21:02:05 +0300 Subject: Bug/feature: mail fs pollution on IMAP select namespace/{non-existent} In-Reply-To: References: Message-ID: <0C1688F2-CD82-4BBB-A1C9-E7881F4B945A@iki.fi> On 24.6.2014, at 16.04, Peter Benko wrote: > I have noticed a strange behavior with dovecot (tested with 2.2.13). I use shared folders to share mailboxes between users. I have a namespace called "Accounts" that hosts the shared folder for the users (prefix Accounts/%%n/). However, When I issue an IMAP select command on a random non-existent mailbox name under "Accounts", dovecot auto-creates it and pollutes my mail root directory: .. > mail_location = mdbox:~ .. > namespace { > list = children > location = mdbox:/mail/mailboxes/%%d/%%n:INDEX=/mail/mailboxes/%%d/%%n:INDEXPVT=/mail/mailboxes/%d/%n/indexpvt-accounts/%%n location = mdbox:%%h:INDEXPVT=/mail/mailboxes/%d/%n/indexpvt-accounts/%%n This forces Dovecot to do a userdb lookup for the user to get the home dir, which should fail if the user doesn't exist. From compul at coletteral.net Thu Jul 3 18:03:42 2014 From: compul at coletteral.net (Niklas Lemcke - =?UTF-8?B?5p6X5qiC5a+s?=) Date: Fri, 4 Jul 2014 02:03:42 +0800 Subject: Permissions with mailman In-Reply-To: <20140702154956.13103a04@compul-debian.me.org> References: <20140702154956.13103a04@compul-debian.me.org> Message-ID: <20140704020342.64ab3398@compul-debian.me.org> On Wed, 2 Jul 2014 15:49:56 +0800 Niklas Lemcke - ??? wrote: > Hi, > > I'm running a Mailserver, and recently also a Mailinglist. > > I'm sporting > # dovecot --version > 2.1.7 > on a debian stable machine with postfix & mailman. Everything works > fine, except that no archive is being created (here an excerpt from my > log): > > > Jul 2 15:29:39 blade01 postfix/qmgr[5217]: B30BCE1F52: > from=, size=802, nrcpt=1 (queue active) > > Jul 2 15:29:39 blade01 dovecot: lda(list): Error: user list: > Initialization failed: Initializing mail storage from mail_location > setting failed: mkdir(/var/mail/vmail//list/mail) failed: Permission > denied (euid=38(list) egid=38(list) missing +w perm: /var/mail/vmail/, > we're not in group 5000(vmail), dir owned by 5000:5000 mode=0775) > > Jul 2 15:29:39 blade01 dovecot: lda(list): Fatal: Invalid user > settings. Refer to server log for more information. > > Jul 2 15:29:39 blade01 postfix/local[2778]: B30BCE1F52: > to=, orig_to=, relay=local, delay=12578, > delays=12578/0.16/0/0.17, dsn=4.3.0, status=deferred (temporary failure) > > > Now since dovecot is running as user vmail (the other mail folders are > all well managed and accessed by it, and all owned by vmail:vmail) I > thought it might be saying that the user list is not in group vmail. > Now: > $ groups list > list : list vmail > and the permissions are 775, but it's still complaining about "missing > +w perm". What is it referring to with "we're not in group 5000"? > > > Thanks for any help! > Does nobody happen to know what I'm talking about? If I phrased the question in a poor way, please let me know. Thank you. -- Niklas - ??? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From tss at iki.fi Thu Jul 3 18:28:51 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 21:28:51 +0300 Subject: OOM in Dovecot 2.2.13 imap In-Reply-To: References: Message-ID: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> On 23.6.2014, at 15.18, Bernhard Schmidt wrote: > we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes. > We have two users that repeatedly trigger an OOM condition with IMAP. > > Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal: pool_system_realloc(268435456): Out of memory .. > #6 0x00007f11766e6cda in o_stream_grow_buffer (fstream=fstream at entry=0x7f11789f41c0, bytes=) at ostream-file.c:440 > size = 268435456 > new_size = > end_size = .. > #11 0x00007f1175692849 in o_stream_zlib_send_outbuf (zstream=0x7f11789f9340) at ostream-zlib.c:94 > ret = > size = 12113 > #12 0x00007f1175692982 in o_stream_zlib_send_flush (zstream=zstream at entry=0x7f11789f9340, final=final at entry=true) at ostream-zlib.c:189 This is most likely because of the IMAP COMPRESS extension, which causes the output stream buffer to get really large. So the easiest fix would be to just disable imap_zlib plugin and it'll probably work. But this should get fixed properly.. I just can't figure out how this can happen. What was the IMAP client doing that caused it? Could you run a few more gdb commands: > #17 0x00007f1176e8d269 in client_output (client=0x7f11789f4470) at imap-client.c:1019 Assuming client_output is again in frame 17, run: f 17 p *client.command_queue p *client.command_queue.next From tss at iki.fi Thu Jul 3 18:56:07 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 21:56:07 +0300 Subject: OOM in Dovecot 2.2.13 imap In-Reply-To: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> References: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> Message-ID: <03C1B098-999F-4FC2-B6CF-987EBC7219DB@iki.fi> Actually, I think these fix it: http://hg.dovecot.org/dovecot-2.2/rev/5740cb57d02c http://hg.dovecot.org/dovecot-2.2/rev/00b3aa3842b7 On 3.7.2014, at 21.28, Timo Sirainen wrote: > On 23.6.2014, at 15.18, Bernhard Schmidt wrote: > >> we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes. >> We have two users that repeatedly trigger an OOM condition with IMAP. >> >> Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal: pool_system_realloc(268435456): Out of memory > .. >> #6 0x00007f11766e6cda in o_stream_grow_buffer (fstream=fstream at entry=0x7f11789f41c0, bytes=) at ostream-file.c:440 >> size = 268435456 >> new_size = >> end_size = > .. >> #11 0x00007f1175692849 in o_stream_zlib_send_outbuf (zstream=0x7f11789f9340) at ostream-zlib.c:94 >> ret = >> size = 12113 >> #12 0x00007f1175692982 in o_stream_zlib_send_flush (zstream=zstream at entry=0x7f11789f9340, final=final at entry=true) at ostream-zlib.c:189 > > This is most likely because of the IMAP COMPRESS extension, which causes the output stream buffer to get really large. So the easiest fix would be to just disable imap_zlib plugin and it'll probably work. But this should get fixed properly.. I just can't figure out how this can happen. What was the IMAP client doing that caused it? Could you run a few more gdb commands: > >> #17 0x00007f1176e8d269 in client_output (client=0x7f11789f4470) at imap-client.c:1019 > > Assuming client_output is again in frame 17, run: > > f 17 > p *client.command_queue > p *client.command_queue.next From tss at iki.fi Thu Jul 3 18:58:01 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 21:58:01 +0300 Subject: [Dovecot] fts_lucene - hiding lucene-indexes folder? In-Reply-To: References: <536D0F56.20205@sys4.de> <536D127D.7060706@sys4.de> Message-ID: <91C1A91F-60E6-486B-9D43-404520826713@iki.fi> Try the latest hg version. The lucene-indexes directory should be hidden under .imap/ directory. On 3.7.2014, at 20.55, Larry Rosenman wrote: > Timo, > Is there any chance of this happening (making lucene-indexes \NOSELECT)? > > > On Fri, May 9, 2014 at 12:38 PM, Robert Schetterer wrote: > >> Am 09.05.2014 19:27, schrieb Larry Rosenman: >>> I'm using mbox, so it DOES show up. >>> >>> thebighonker.lerctr.org /home/ler $ >>> more /tmp/doveconf.n.out >>> >>> # 2.2.12: /usr/local/etc/dovecot/dovecot.conf >>> >>> # OS: FreeBSD 10.0-STABLE amd64 >>> >>> auth_default_realm = lerctr.org >>> >>> auth_mechanisms = plain login >>> >>> auth_realms = lerctr.org thebighonker.lerctr.org >>> tbh.lerctr.org >>> >>> auth_username_format = %Ln >>> >>> disable_plaintext_auth = no >>> >>> lda_mailbox_autocreate = yes >>> >>> lmtp_save_to_detail_mailbox = yes >>> >>> login_access_sockets = tcpwrap >>> >>> mail_debug = yes >>> >>> mail_location = mbox:~/mail:INBOX=~/mail/INBOX >>> >>> mail_plugins = snarf fts fts_lucene stats >>> >>> mail_privileged_group = mail >>> >>> managesieve_notify_capability = mailto >>> >>> managesieve_sieve_capability = fileinto reject envelope >>> encoded-character vacation subaddress comparator-i;ascii-numeric >>> relational regex imap4flags copy include variables body enotify >>> environment mailbox date ihave >>> >>> namespace Snarf { >>> >>> hidden = yes >>> >>> list = no >>> >>> location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=MEMORY >>> >>> prefix = ~~Snarfbox/ >>> >>> separator = / >>> >>> } >>> >>> namespace archive { >>> >>> hidden = no >>> >>> inbox = no >>> >>> list = no >>> >>> location = mbox:~/MAILARCHIVE >>> >>> prefix = "#ARCHIVE/" >>> >>> separator = / >>> >>> } >>> >>> namespace default { >>> >>> hidden = yes >>> >>> list = no >>> >>> location = >>> >>> prefix = ~~default/ >>> >>> separator = / >>> >>> } >>> >>> namespace inbox { >>> >>> inbox = yes >>> >>> location = >>> >>> mailbox Drafts { >>> >>> special_use = \Drafts >>> >>> } >>> >>> mailbox INBOX { >>> >>> auto = create >>> >>> } >>> >>> mailbox Junk { >>> >>> special_use = \Junk >>> >>> } >>> >>> mailbox Sent { >>> >>> special_use = \Sent >>> >>> } >>> >>> mailbox "Sent Messages" { >>> >>> special_use = \Sent >>> >>> } >>> >>> mailbox Trash { >>> >>> special_use = \Trash >>> >>> } >>> >>> prefix = >>> >>> } >>> >>> passdb { >>> >>> args = failure_show_msg=yes session=yes max_requests=20 >>> >>> driver = pam >>> >>> } >>> >>> plugin { >>> >>> fts = lucene >>> >>> fts_lucene = whitespace_chars=@. normalize no_snowball >>> >>> mbox_snarf = ~/mail/INBOX >>> >>> sieve = ~/.dovecot.sieve >>> >>> sieve_dir = ~/sieve >>> >>> snarf = ~~Snarfbox/INBOX >>> >>> stats_command_min_time = 1 mins >>> >>> stats_domain_min_time = 12 hours >>> >>> stats_ip_min_time = 12 hours >>> >>> stats_memory_limit = 16 M >>> >>> stats_refresh = 5s >>> >>> stats_session_min_time = 15 mins >>> >>> stats_track_cmds = yes >>> >>> stats_user_min_time = 1 hours >>> >>> } >>> >>> service auth { >>> >>> unix_listener auth-client { >>> >>> mode = 0666 >>> >>> } >>> >>> unix_listener auth-master { >>> >>> mode = 0666 >>> >>> } >>> >>> } >>> >>> service stats { >>> >>> chroot = empty >>> >>> client_limit = 0 >>> >>> drop_priv_before_exec = no >>> >>> executable = stats >>> >>> extra_groups = >>> >>> fifo_listener stats-mail { >>> >>> group = >>> >>> mode = 0666 >>> >>> user = >>> >>> } >>> >>> group = >>> >>> idle_kill = 4294967295 secs >>> >>> privileged_group = >>> >>> process_limit = 1 >>> >>> process_min_avail = 0 >>> >>> protocol = >>> >>> service_count = 0 >>> >>> type = >>> >>> unix_listener stats { >>> >>> group = >>> >>> mode = 0666 >>> >>> user = >>> >>> } >>> >>> user = $default_internal_user >>> >>> vsz_limit = 18446744073709551615 B >>> >>> } >>> >>> service tcpwrap { >>> >>> unix_listener login/tcpwrap { >>> >>> group = $default_login_user >>> >>> mode = 0600 >>> >>> user = $default_login_user >>> >>> } >>> >>> } >>> >>> ssl_cert = >> >>> ssl_key = >> >>> userdb { >>> >>> driver = passwd >>> >>> } >>> >>> protocol imap { >>> >>> imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags >>> >>> mail_max_userip_connections = 50 >>> >>> mail_plugins = snarf fts fts_lucene stats imap_stats >>> >>> } >> >> i am not using mbox , didnt analyse your conf very deeply >> but my bet is ,your namespace and/or directory layout setup is the problem >> >> >> perhaps reread >> >> http://wiki2.dovecot.org/MboxChildFolders?highlight=%28index%29 >> >> http://wiki2.dovecot.org/Plugins/FTS/Lucene >> >> Requires Dovecot v2.1+ to work properly. The CLucene version must be >> v2.3 (not v0.9). Dovecot builds only a single Lucene index for all >> mailboxes. The Lucene indexes are stored in lucene-indexes/ directory >> under the mail root index directory (e.g. ~/Maildir/lucene-indexes/). >> >> so perhaps you need configure index directory seperate/extra setting etc >> >>> >>> thebighonker.lerctr.org /home/ler $ >>> >>> >>> >>> On Fri, May 9, 2014 at 12:24 PM, Robert Schetterer >> > wrote: >>> >>> Am 09.05.2014 18:20, schrieb Nicholas Riley: >>>> Hi, >>>> >>>> Is there any way to hide this folder from IMAP clients? I can see >>> it is >>>> not runtime configurable and just #defined as >> LUCENE_INDEX_DIR_NAME in >>>> fts-backend-lucene.c. >>>> >>> >>> you shouldnt see it, guess you configured something wrong like >>> >>> i.e >>> >>> maildir_stat_dirs=no (default): Assume that all the files beginning >> with >>> a dot in the maildir are maildirs. You shouldn't have any >> non-directory >>> files beginning with a dot in the maildirs, but if you do you may >> need >>> to set this to "yes", in which case Dovecot needs to stat() each >>> directory entry, which degrades the performance. Some filesystems >>> provide the directory/non-directory status for free without having to >>> stat(). In those filesystems this setting is ignored. >>> >>> etc >>> >>> post your full dove conf to give chance for analysis >>> >>> >>> >>> Best Regards >>> MfG Robert Schetterer >>> >>> -- >>> [*] sys4 AG >>> >>> http://sys4.de, +49 (89) 30 90 46 64 >>> >>> Franziskanerstra?e 15, 81669 M?nchen >>> >>> Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 >>> Vorstand: Patrick Ben Koetter, Marc Schiffbauer >>> Aufsichtsratsvorsitzender: Florian Kirstein >>> >>> >>> >>> >>> -- >>> Larry Rosenman http://www.lerctr.org/~ler >>> Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com >>> >>> US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 >> >> >> >> Best Regards >> MfG Robert Schetterer >> >> -- >> [*] sys4 AG >> >> http://sys4.de, +49 (89) 30 90 46 64 >> Franziskanerstra?e 15, 81669 M?nchen >> >> Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 >> Vorstand: Patrick Ben Koetter, Marc Schiffbauer >> Aufsichtsratsvorsitzender: Florian Kirstein >> > > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com > US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 From tss at iki.fi Thu Jul 3 19:18:14 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 22:18:14 +0300 Subject: BUG: Mail folder with space in its name is not supported in the global acl file In-Reply-To: <539EA713.5040002@icdsoft.com> References: <539EA713.5040002@icdsoft.com> Message-ID: On 16.6.2014, at 11.13, Iavor Stoev wrote: > I tried to escape it with "",'',/ and enclose the whole name with "" & '' without success Added: http://hg.dovecot.org/dovecot-2.2/rev/40dc5774aa69 From larryrtx at gmail.com Thu Jul 3 19:30:28 2014 From: larryrtx at gmail.com (Larry Rosenman) Date: Thu, 3 Jul 2014 14:30:28 -0500 Subject: [Dovecot] fts_lucene - hiding lucene-indexes folder? In-Reply-To: <91C1A91F-60E6-486B-9D43-404520826713@iki.fi> References: <536D0F56.20205@sys4.de> <536D127D.7060706@sys4.de> <91C1A91F-60E6-486B-9D43-404520826713@iki.fi> Message-ID: Yeah, I see that now -- I needed to move all my users lucene-indexes, or they'll get rebuilt over time...... On Thu, Jul 3, 2014 at 1:58 PM, Timo Sirainen wrote: > Try the latest hg version. The lucene-indexes directory should be hidden > under .imap/ directory. > > On 3.7.2014, at 20.55, Larry Rosenman wrote: > > > Timo, > > Is there any chance of this happening (making lucene-indexes > \NOSELECT)? > > > > > > On Fri, May 9, 2014 at 12:38 PM, Robert Schetterer wrote: > > > >> Am 09.05.2014 19:27, schrieb Larry Rosenman: > >>> I'm using mbox, so it DOES show up. > >>> > >>> thebighonker.lerctr.org /home/ler $ > >>> more /tmp/doveconf.n.out > >>> > >>> # 2.2.12: /usr/local/etc/dovecot/dovecot.conf > >>> > >>> # OS: FreeBSD 10.0-STABLE amd64 > >>> > >>> auth_default_realm = lerctr.org > >>> > >>> auth_mechanisms = plain login > >>> > >>> auth_realms = lerctr.org thebighonker.lerctr.org > >>> tbh.lerctr.org > > >>> > >>> auth_username_format = %Ln > >>> > >>> disable_plaintext_auth = no > >>> > >>> lda_mailbox_autocreate = yes > >>> > >>> lmtp_save_to_detail_mailbox = yes > >>> > >>> login_access_sockets = tcpwrap > >>> > >>> mail_debug = yes > >>> > >>> mail_location = mbox:~/mail:INBOX=~/mail/INBOX > >>> > >>> mail_plugins = snarf fts fts_lucene stats > >>> > >>> mail_privileged_group = mail > >>> > >>> managesieve_notify_capability = mailto > >>> > >>> managesieve_sieve_capability = fileinto reject envelope > >>> encoded-character vacation subaddress comparator-i;ascii-numeric > >>> relational regex imap4flags copy include variables body enotify > >>> environment mailbox date ihave > >>> > >>> namespace Snarf { > >>> > >>> hidden = yes > >>> > >>> list = no > >>> > >>> location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=MEMORY > >>> > >>> prefix = ~~Snarfbox/ > >>> > >>> separator = / > >>> > >>> } > >>> > >>> namespace archive { > >>> > >>> hidden = no > >>> > >>> inbox = no > >>> > >>> list = no > >>> > >>> location = mbox:~/MAILARCHIVE > >>> > >>> prefix = "#ARCHIVE/" > >>> > >>> separator = / > >>> > >>> } > >>> > >>> namespace default { > >>> > >>> hidden = yes > >>> > >>> list = no > >>> > >>> location = > >>> > >>> prefix = ~~default/ > >>> > >>> separator = / > >>> > >>> } > >>> > >>> namespace inbox { > >>> > >>> inbox = yes > >>> > >>> location = > >>> > >>> mailbox Drafts { > >>> > >>> special_use = \Drafts > >>> > >>> } > >>> > >>> mailbox INBOX { > >>> > >>> auto = create > >>> > >>> } > >>> > >>> mailbox Junk { > >>> > >>> special_use = \Junk > >>> > >>> } > >>> > >>> mailbox Sent { > >>> > >>> special_use = \Sent > >>> > >>> } > >>> > >>> mailbox "Sent Messages" { > >>> > >>> special_use = \Sent > >>> > >>> } > >>> > >>> mailbox Trash { > >>> > >>> special_use = \Trash > >>> > >>> } > >>> > >>> prefix = > >>> > >>> } > >>> > >>> passdb { > >>> > >>> args = failure_show_msg=yes session=yes max_requests=20 > >>> > >>> driver = pam > >>> > >>> } > >>> > >>> plugin { > >>> > >>> fts = lucene > >>> > >>> fts_lucene = whitespace_chars=@. normalize no_snowball > >>> > >>> mbox_snarf = ~/mail/INBOX > >>> > >>> sieve = ~/.dovecot.sieve > >>> > >>> sieve_dir = ~/sieve > >>> > >>> snarf = ~~Snarfbox/INBOX > >>> > >>> stats_command_min_time = 1 mins > >>> > >>> stats_domain_min_time = 12 hours > >>> > >>> stats_ip_min_time = 12 hours > >>> > >>> stats_memory_limit = 16 M > >>> > >>> stats_refresh = 5s > >>> > >>> stats_session_min_time = 15 mins > >>> > >>> stats_track_cmds = yes > >>> > >>> stats_user_min_time = 1 hours > >>> > >>> } > >>> > >>> service auth { > >>> > >>> unix_listener auth-client { > >>> > >>> mode = 0666 > >>> > >>> } > >>> > >>> unix_listener auth-master { > >>> > >>> mode = 0666 > >>> > >>> } > >>> > >>> } > >>> > >>> service stats { > >>> > >>> chroot = empty > >>> > >>> client_limit = 0 > >>> > >>> drop_priv_before_exec = no > >>> > >>> executable = stats > >>> > >>> extra_groups = > >>> > >>> fifo_listener stats-mail { > >>> > >>> group = > >>> > >>> mode = 0666 > >>> > >>> user = > >>> > >>> } > >>> > >>> group = > >>> > >>> idle_kill = 4294967295 secs > >>> > >>> privileged_group = > >>> > >>> process_limit = 1 > >>> > >>> process_min_avail = 0 > >>> > >>> protocol = > >>> > >>> service_count = 0 > >>> > >>> type = > >>> > >>> unix_listener stats { > >>> > >>> group = > >>> > >>> mode = 0666 > >>> > >>> user = > >>> > >>> } > >>> > >>> user = $default_internal_user > >>> > >>> vsz_limit = 18446744073709551615 B > >>> > >>> } > >>> > >>> service tcpwrap { > >>> > >>> unix_listener login/tcpwrap { > >>> > >>> group = $default_login_user > >>> > >>> mode = 0600 > >>> > >>> user = $default_login_user > >>> > >>> } > >>> > >>> } > >>> > >>> ssl_cert = >>> > >>> ssl_key = >>> > >>> userdb { > >>> > >>> driver = passwd > >>> > >>> } > >>> > >>> protocol imap { > >>> > >>> imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags > >>> > >>> mail_max_userip_connections = 50 > >>> > >>> mail_plugins = snarf fts fts_lucene stats imap_stats > >>> > >>> } > >> > >> i am not using mbox , didnt analyse your conf very deeply > >> but my bet is ,your namespace and/or directory layout setup is the > problem > >> > >> > >> perhaps reread > >> > >> http://wiki2.dovecot.org/MboxChildFolders?highlight=%28index%29 > >> > >> http://wiki2.dovecot.org/Plugins/FTS/Lucene > >> > >> Requires Dovecot v2.1+ to work properly. The CLucene version must be > >> v2.3 (not v0.9). Dovecot builds only a single Lucene index for all > >> mailboxes. The Lucene indexes are stored in lucene-indexes/ directory > >> under the mail root index directory (e.g. ~/Maildir/lucene-indexes/). > >> > >> so perhaps you need configure index directory seperate/extra setting etc > >> > >>> > >>> thebighonker.lerctr.org /home/ler $ > >>> > >>> > >>> > >>> On Fri, May 9, 2014 at 12:24 PM, Robert Schetterer >>> > wrote: > >>> > >>> Am 09.05.2014 18:20, schrieb Nicholas Riley: > >>>> Hi, > >>>> > >>>> Is there any way to hide this folder from IMAP clients? I can see > >>> it is > >>>> not runtime configurable and just #defined as > >> LUCENE_INDEX_DIR_NAME in > >>>> fts-backend-lucene.c. > >>>> > >>> > >>> you shouldnt see it, guess you configured something wrong like > >>> > >>> i.e > >>> > >>> maildir_stat_dirs=no (default): Assume that all the files beginning > >> with > >>> a dot in the maildir are maildirs. You shouldn't have any > >> non-directory > >>> files beginning with a dot in the maildirs, but if you do you may > >> need > >>> to set this to "yes", in which case Dovecot needs to stat() each > >>> directory entry, which degrades the performance. Some filesystems > >>> provide the directory/non-directory status for free without having > to > >>> stat(). In those filesystems this setting is ignored. > >>> > >>> etc > >>> > >>> post your full dove conf to give chance for analysis > >>> > >>> > >>> > >>> Best Regards > >>> MfG Robert Schetterer > >>> > >>> -- > >>> [*] sys4 AG > >>> > >>> http://sys4.de, +49 (89) 30 90 46 64 > >>> > >>> Franziskanerstra?e 15, 81669 M?nchen > >>> > >>> Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 > >>> Vorstand: Patrick Ben Koetter, Marc Schiffbauer > >>> Aufsichtsratsvorsitzender: Florian Kirstein > >>> > >>> > >>> > >>> > >>> -- > >>> Larry Rosenman http://www.lerctr.org/~ler > >>> Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com > >>> > >>> US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 > >> > >> > >> > >> Best Regards > >> MfG Robert Schetterer > >> > >> -- > >> [*] sys4 AG > >> > >> http://sys4.de, +49 (89) 30 90 46 64 > >> Franziskanerstra?e 15, 81669 M?nchen > >> > >> Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 > >> Vorstand: Patrick Ben Koetter, Marc Schiffbauer > >> Aufsichtsratsvorsitzender: Florian Kirstein > >> > > > > > > > > -- > > Larry Rosenman http://www.lerctr.org/~ler > > Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com > > US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 > > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 From tss at iki.fi Thu Jul 3 19:33:42 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 22:33:42 +0300 Subject: ACL configuration migration from Dovecot 2.1.17 to 2.2.13 In-Reply-To: <539850FE.4050501@icdsoft.com> References: <539850FE.4050501@icdsoft.com> Message-ID: <3725BD0E-88E7-4E59-AAAB-06886AF466B4@iki.fi> On 11.6.2014, at 15.52, Iavor Stoev wrote: > I'm preparing migration to the latest Dovecot version 2.2.13 > from the previous stable branch 2.1.17 which is deployed on my servers. > > With version 2.1.17 I use global acl dir to prevent all mail users to delete their INBOX.Junk Mail folder, which is part from our spam protection system. > > My current config is: > > cat /etc/dovecot/acls/INBOX.Junk\ Mail > owner lrwstiae > > With version 2.2.13, the global acl dir support is disabled (with the above config, the imap server shows no folders at all) so I must > use global acl file. It's not supposed to be disabled. It's supposed to work exactly as in v2.1. In my test it still works, so the problem is something more complex than "it's completely broken". Would be nice to know what exactly is broken with it. From tss at iki.fi Thu Jul 3 19:35:34 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 22:35:34 +0300 Subject: OT - Finding/removing duplicate emails - WAS: Re: [Dovecot] dovecot/lmtp munmap()-ing a lot In-Reply-To: <5396E689.5000508@Media-Brokers.com> References: <20140608085943.GA7734@sys4.de> <20140609214425.GA31799@sys4.de> <5396E689.5000508@Media-Brokers.com> Message-ID: On 10.6.2014, at 14.05, Charles Marcus wrote: > On 6/9/2014 5:44 PM, Ralf Hildebrandt wrote: >> That's probably the problem here. The user had LOTS of (duplicate!) >> mails in his inbox. > > Anyone ever found a reliable way to do this? > > It sure would be nice if dovecot could perform this on a per account and/or per maildir/mailbox case with a simple doveadm command... doveadm deduplicate From lists at tigertech.com Thu Jul 3 19:49:14 2014 From: lists at tigertech.com (Robert L Mathews) Date: Thu, 03 Jul 2014 12:49:14 -0700 Subject: Permissions with mailman In-Reply-To: <20140704020342.64ab3398@compul-debian.me.org> References: <20140702154956.13103a04@compul-debian.me.org> <20140704020342.64ab3398@compul-debian.me.org> Message-ID: <53B5B3BA.5010509@tigertech.com> On 7/3/14, 11:03 AM, Niklas Lemcke - ??? wrote: > Jul 2 15:29:39 blade01 dovecot: lda(list): Error: user list: > Initialization failed: Initializing mail storage from mail_location > setting failed: mkdir(/var/mail/vmail//list/mail) failed: Permission > denied (euid=38(list) egid=38(list) > Now since dovecot is running as user vmail According to the error, it's not running as user vmail for this delivery. It's running as uid/gid 38, "list". Look at how "lda" gets executed for this delivery to see why it's using uid 38. -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/ From tss at iki.fi Thu Jul 3 19:50:59 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 3 Jul 2014 22:50:59 +0300 Subject: [Dovecot] dovecot: disable ssl compression In-Reply-To: <20140520194906.GB15438@solar.andreasschulze.de> References: <20140410150440.Horde.Gbn7XHx4blr0ZfiXKEbaAA1@horde.andreasschulze.de> <5346ADA2.7000203@thelounge.net> <20140423235219.Horde.PR-DrnYWXvVrgZ8sQM1XxQ2@horde.andreasschulze.de> <53583B70.5010507@thelounge.net> <20140424064127.Horde.PmGX52ciDTWb1ia6iZDURA1@horde.andreasschulze.de> <5358AF76.5090409@thinline.cz> <20140520194906.GB15438@solar.andreasschulze.de> Message-ID: <95DEB543-2727-4C87-8645-A72C747A8E63@iki.fi> On 20.5.2014, at 22.49, Andreas Schulze wrote: > Jiri Bourek: >> Well they seem to know what they are talking about. The description >> of the threat in linked screenshot says "attacker needs to have >> ability to submit any plain text" > > I wrote the attached patch to add SSL_OP_NO_COMPRESSION to dovecot. > Looks not perfect but definitly works. Added a Postfix-like ssl_options setting: http://hg.dovecot.org/dovecot-2.2/rev/cea292767b95 But now I'm wondering if no-compression should be enabled by default?.. From compul at coletteral.net Thu Jul 3 20:03:19 2014 From: compul at coletteral.net (Niklas Lemcke - =?UTF-8?B?5p6X5qiC5a+s?=) Date: Fri, 4 Jul 2014 04:03:19 +0800 Subject: Permissions with mailman In-Reply-To: <53B5B3BA.5010509@tigertech.com> References: <20140702154956.13103a04@compul-debian.me.org> <20140704020342.64ab3398@compul-debian.me.org> <53B5B3BA.5010509@tigertech.com> Message-ID: <20140704040319.5b25f330@compul-debian.me.org> On Thu, 03 Jul 2014 12:49:14 -0700 Robert L Mathews wrote: > On 7/3/14, 11:03 AM, Niklas Lemcke - ??? wrote: > > > Jul 2 15:29:39 blade01 dovecot: lda(list): Error: user list: > > Initialization failed: Initializing mail storage from mail_location > > setting failed: mkdir(/var/mail/vmail//list/mail) failed: Permission > > denied (euid=38(list) egid=38(list) > > > Now since dovecot is running as user vmail > > According to the error, it's not running as user vmail for this > delivery. It's running as uid/gid 38, "list". > > Look at how "lda" gets executed for this delivery to see why it's using > uid 38. > Thanks I'm not sure why it's using uid 38, but even so, the user list is in the group vmail and thus should be able to write to /var/mail/vmail. However it reports it's not in the group. => confused -- Niklas - ??? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From d.parthey at metaways.de Thu Jul 3 20:37:01 2014 From: d.parthey at metaways.de (Daniel Parthey) Date: Thu, 03 Jul 2014 22:37:01 +0200 Subject: stripping extension from domain name In-Reply-To: <20140703063610.4874f7aa@scorpio> References: <20140703063610.4874f7aa@scorpio> Message-ID: On 3. Juli 2014 12:36:10 MESZ, Jerry wrote: >Thu, 3 Jul 2014 06:29:06 -0400 > >I know that the "%d" parameter is for the domain. Is there any way to >use >just the domain name sans its extension. > >EXAMPLE: > >example.com ==> example I don't know of any. >Also, I have a lot of logging going on in my dovecot log file. I want >to >limit it to just the barest amount, such as indicting what mail box >mail was >delivered to. Authentication errors, etcetera should only be shown if >an >error occurs. Is this possible? I would recommend to filter the desired message types with syslog-ng or rsyslog using regular expressions and write important messages into a separate logfile. Regards Daniel From berni at birkenwald.de Thu Jul 3 20:56:54 2014 From: berni at birkenwald.de (Bernhard Schmidt) Date: Thu, 03 Jul 2014 22:56:54 +0200 Subject: OOM in Dovecot 2.2.13 imap In-Reply-To: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> References: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> Message-ID: <53B5C396.4090109@birkenwald.de> Hi Timo, thanks for your answer. >> we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand >> mailboxes. We have two users that repeatedly trigger an OOM >> condition with IMAP. >> >> Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal: >> pool_system_realloc(268435456): Out of memory > .. >> #6 0x00007f11766e6cda in o_stream_grow_buffer >> (fstream=fstream at entry=0x7f11789f41c0, bytes=) at >> ostream-file.c:440 size = 268435456 new_size = >> end_size = > .. >> #11 0x00007f1175692849 in o_stream_zlib_send_outbuf >> (zstream=0x7f11789f9340) at ostream-zlib.c:94 ret = > out> size = 12113 #12 0x00007f1175692982 in >> o_stream_zlib_send_flush (zstream=zstream at entry=0x7f11789f9340, >> final=final at entry=true) at ostream-zlib.c:189 > > This is most likely because of the IMAP COMPRESS extension, which > causes the output stream buffer to get really large. So the easiest > fix would be to just disable imap_zlib plugin and it'll probably > work. But this should get fixed properly.. I just can't figure out > how this can happen. What was the IMAP client doing that caused it? > Could you run a few more gdb commands: > >> #17 0x00007f1176e8d269 in client_output (client=0x7f11789f4470) at >> imap-client.c:1019 > > Assuming client_output is again in frame 17, run: > > f 17 p *client.command_queue p *client.command_queue.next #0 0x00007f1176307475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) f 17 #17 0x00007f1176e8d269 in client_output (client=0x7f11789f4470) at imap-client.c:1019 1019 imap-client.c: No such file or directory. (gdb) p *client.command_queue $1 = {prev = 0x0, next = 0x0, client = 0x7f11789f4470, pool = 0x7f11789f4c60, tag = 0x7f11789f4d60 "9", name = 0x7f11789f4d68 "UID fetch", args = 0x7f11789f4d78 "3044 (UID RFC822.SIZE BODY.PEEK[])", cmd_flags = COMMAND_FLAG_BREAKS_SEQS, func = 0x7f1176e83d10 , context = 0x7f11789f4da0, module_contexts = {arr = {buffer = 0x7f11789f4d00, element_size = 8}, v = 0x7f11789f4d00, v_modifiable = 0x7f11789f4d00}, parser = 0x7f11789df950, state = CLIENT_COMMAND_STATE_WAIT_OUTPUT, sync = 0x0, uid = 1, cancel = 0, param_error = 0, search_save_result = 0, search_save_result_used = 0, temp_executed = 1, tagline_sent = 0} (gdb) p *client.command_queue.next Cannot access memory at address 0x0 We could easily live without IMAP COMPRESS for now, but if this backtrace confirms your suspicion we will gladly try a build with your patches applied. Thanks, Bernhard From gfa at zumbi.com.ar Thu Jul 3 21:38:55 2014 From: gfa at zumbi.com.ar (gustavo panizzo ) Date: Thu, 03 Jul 2014 18:38:55 -0300 Subject: mixing Maildir and mdbox Message-ID: <53B5CD6F.6080604@zumbi.com.ar> Hello i'm in the process to architect a new email system. i plan to use dovecot 2.2.9 (debian's wheezy). i would like to use maildir for 2 folders on each account (spam and no-spam) and the rest of the folders stored on mdbox. this should be opaque to my users. the reason for this, is i want to be able to train my anti-spam tools, but they read maildir or mbox, they don't read mdbox or dbox. but i want the other folders as mdbox (performance, backups, alternate storage) is there any way?, i prefer if is configurable in advance for all accounts but i could live with something that is done after account is created thanks! -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 From tss at iki.fi Thu Jul 3 21:41:23 2014 From: tss at iki.fi (Timo Sirainen) Date: Fri, 4 Jul 2014 00:41:23 +0300 Subject: OOM in Dovecot 2.2.13 imap In-Reply-To: <53B5C396.4090109@birkenwald.de> References: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> <53B5C396.4090109@birkenwald.de> Message-ID: <0F0301B6-3DB7-44F4-BF35-FF4D66425F0C@iki.fi> On 3.7.2014, at 23.56, Bernhard Schmidt wrote: >>> #17 0x00007f1176e8d269 in client_output (client=0x7f11789f4470) at >>> imap-client.c:1019 >> >> Assuming client_output is again in frame 17, run: >> >> f 17 p *client.command_queue p *client.command_queue.next .. > We could easily live without IMAP COMPRESS for now, but if this > backtrace confirms your suspicion we will gladly try a build with your > patches applied. Yeah, I'm pretty sure my patches will fix it. I'm planning on v2.2.14 hopefully this week, although looks like either I'd have to leave some reported bugs unfixed or delay it.. From sca at andreasschulze.de Thu Jul 3 21:55:47 2014 From: sca at andreasschulze.de (A. Schulze) Date: Thu, 03 Jul 2014 23:55:47 +0200 Subject: [Dovecot] dovecot: disable ssl compression In-Reply-To: <95DEB543-2727-4C87-8645-A72C747A8E63@iki.fi> References: <20140410150440.Horde.Gbn7XHx4blr0ZfiXKEbaAA1@horde.andreasschulze.de> <5346ADA2.7000203@thelounge.net> <20140423235219.Horde.PR-DrnYWXvVrgZ8sQM1XxQ2@horde.andreasschulze.de> <53583B70.5010507@thelounge.net> <20140424064127.Horde.PmGX52ciDTWb1ia6iZDURA1@horde.andreasschulze.de> <5358AF76.5090409@thinline.cz> <20140520194906.GB15438@solar.andreasschulze.de> <95DEB543-2727-4C87-8645-A72C747A8E63@iki.fi> Message-ID: <20140703235547.Horde.AEK38twBphLxWcM51fLfRA1@horde.andreasschulze.de> Timo Sirainen: > But now I'm wondering if no-compression should be enabled by default?.. to not potential break something I would not change the default now but maybe later... Thanks! Andreas From bourek at thinline.cz Thu Jul 3 22:03:06 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Fri, 04 Jul 2014 00:03:06 +0200 Subject: [Dovecot] dovecot: disable ssl compression In-Reply-To: <20140703235547.Horde.AEK38twBphLxWcM51fLfRA1@horde.andreasschulze.de> References: <20140410150440.Horde.Gbn7XHx4blr0ZfiXKEbaAA1@horde.andreasschulze.de> <5346ADA2.7000203@thelounge.net> <20140423235219.Horde.PR-DrnYWXvVrgZ8sQM1XxQ2@horde.andreasschulze.de> <53583B70.5010507@thelounge.net> <20140424064127.Horde.PmGX52ciDTWb1ia6iZDURA1@horde.andreasschulze.de> <5358AF76.5090409@thinline.cz> <20140520194906.GB15438@solar.andreasschulze.de> <95DEB543-2727-4C87-8645-A72C747A8E63@iki.fi> <20140703235547.Horde.AEK38twBphLxWcM51fLfRA1@horde.andreasschulze.de> Message-ID: <53B5D31A.1060208@thinline.cz> On 3.7.2014 23:55, A. Schulze wrote: > > Timo Sirainen: > >> But now I'm wondering if no-compression should be enabled by default?.. > > to not potential break something I would not change the default now > but maybe later... > > Thanks! > Andreas Not sure if it's upstream change, but Debian disabled compression in openssl by default in June (http://metadata.ftp-master.debian.org/changelogs//main/o/openssl/openssl_1.0.1e-2+deb7u11_changelog) As I understand it, any program using the library has compression turned off by default. From leolistas at solutti.com.br Thu Jul 3 22:20:00 2014 From: leolistas at solutti.com.br (Leonardo Rodrigues) Date: Thu, 03 Jul 2014 19:20:00 -0300 Subject: question on lmtp logged message In-Reply-To: References: <53AAEE8D.9050604@solutti.com.br> Message-ID: <53B5D710.5060202@solutti.com.br> Em 03/07/14 14:31, Timo Sirainen escreveu: > On 25.6.2014, at 18.45, Leonardo Rodrigues wrote: > >> I have dovecot running for IMAP4/POP3 and also local delivery through LMTP. It's working just fine, absolutely no problem on that, setup is fine. >> >> Anyway, sometimes LMTP seems to not be able to deliver some messages and keep them on postfixqueue. And on the next or third try, the message gets delivered successfully. The logged message, however, is not helping me identify what is happening.Example: >> >> (error - message was expunged) >> Jun 25 11:49:39 correio postfix/lmtp[21835]: ADB0A1AC05108: to=, relay=correio.domain.com.br[private/dovecot-lmtp], conn_use=6, delay=13, delays=0.07/0/0/13, dsn=4.2.0, status=deferred (host correio.domain.com.br[private/dovecot-lmtp] said: 451 4.2.0 Message was expunged (received-date) (in reply to end of DATA command)) > I guess the only good fix for this is to just get rid of this deduplication feature for now: http://hg.dovecot.org/dovecot-2.2/rev/51274bf2a47d > > Hopefully people don't rely on this feature too much. > Hi Timo, I patched the 2.2.13 tree source, recompiled and installed. I'll let it run for some days and look again if the messages dissapeared. I'm still getting some few of these everyday, so noticing if they dissapeared or continue to happen will be easy. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, N?O mandem email gertrudes at solutti.com.br My SPAMTRAP, do not email it From bourek at thinline.cz Thu Jul 3 22:28:18 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Fri, 04 Jul 2014 00:28:18 +0200 Subject: OT - Finding/removing duplicate emails - WAS: Re: [Dovecot] dovecot/lmtp munmap()-ing a lot In-Reply-To: References: <20140608085943.GA7734@sys4.de> <20140609214425.GA31799@sys4.de> <5396E689.5000508@Media-Brokers.com> Message-ID: <53B5D902.8010406@thinline.cz> On 3.7.2014 21:35, Timo Sirainen wrote: > On 10.6.2014, at 14.05, Charles Marcus wrote: > >> On 6/9/2014 5:44 PM, Ralf Hildebrandt wrote: >>> That's probably the problem here. The user had LOTS of (duplicate!) >>> mails in his inbox. >> >> Anyone ever found a reliable way to do this? >> >> It sure would be nice if dovecot could perform this on a per account and/or per maildir/mailbox case with a simple doveadm command... > > doveadm deduplicate > When I last tried, doveadm deduplicate was quite unreliable (IMO to the point of not being worth using at all.) http://www.dovecot.org/list/dovecot/2014-March/095447.html (Tried again, the behaviour is the same in 2.2.13 from Debian testing) From giel+dovecot at mortis.eu Thu Jul 3 22:30:47 2014 From: giel+dovecot at mortis.eu (Giel van Schijndel) Date: Fri, 4 Jul 2014 00:30:47 +0200 Subject: rmdir() EBUSY warnings on 2.2.12 Message-ID: <20140703223046.GB24263@salidar.me.mortis.eu> Hi, I'm getting a lot of syslog spam on FreeBSD 10 from nfs_flush_file_handle_cache_dir where, apparently it tries to rmdir() the mountpoint of my mail storage. > Jul 4 00:04:44 mailhost dovecot: imap(user at example.com): Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail/vhosts/example.com) failed: Device busy We're using ZFS and have /var, /var/mail, /var/mail/vhosts, /var/mail/vhosts/example.com and /var/mail/vhosts/example.com/user as separate ZFS datasets (to enable per-user and per-domain snapshotting). So apart from NFS flushing being unnecessary (ZFS != NFS) I'm not really sure why using rmdir() for another directory than the Maildir specified in mail_location is a good idea. I.e. given that Maildirs shouldn't ever be emtpy (cur,new,tmp) anyway. -- Met vriendelijke groet, With kind regards, Giel van Schijndel -- > A programmer started to cuss > Because getting to sleep was a fuss > As he lay there in bed Looping 'round in his head > was: while(!asleep()) sheep++; > -- piercings -- http://bash.org/?845468 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From tss at iki.fi Thu Jul 3 22:59:02 2014 From: tss at iki.fi (Timo Sirainen) Date: Fri, 4 Jul 2014 01:59:02 +0300 Subject: rmdir() EBUSY warnings on 2.2.12 In-Reply-To: <20140703223046.GB24263@salidar.me.mortis.eu> References: <20140703223046.GB24263@salidar.me.mortis.eu> Message-ID: On 4.7.2014, at 1.30, Giel van Schijndel wrote: > I'm getting a lot of syslog spam on FreeBSD 10 from > nfs_flush_file_handle_cache_dir where, apparently it tries to rmdir() > the mountpoint of my mail storage. > >> Jul 4 00:04:44 mailhost dovecot: imap(user at example.com): Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail/vhosts/example.com) failed: Device busy > > We're using ZFS and have /var, /var/mail, /var/mail/vhosts, > /var/mail/vhosts/example.com and /var/mail/vhosts/example.com/user as > separate ZFS datasets (to enable per-user and per-domain snapshotting). > > So apart from NFS flushing being unnecessary (ZFS != NFS) I'm not really > sure why using rmdir() for another directory than the Maildir specified > in mail_location is a good idea. I.e. given that Maildirs shouldn't ever > be emtpy (cur,new,tmp) anyway. Don't set mail_nfs_index=yes or mail_nfs_storage=yes and Dovecot won't try these kludgy things to flush NFS caches. They don't fully work anyway and they are highly discouraged for any kind of use, ever. Mainly they exist for backwards compatibility. From lukashaase at gmx.at Fri Jul 4 02:10:40 2014 From: lukashaase at gmx.at (Lukas Haase) Date: Thu, 03 Jul 2014 19:10:40 -0700 Subject: BUG: Authentication client sent unknown handshake command Message-ID: Hi, Some time ago my dovecot started to become BUGgy: Evertime I restart the system, dovecot is started but I cannot login. I see the following information in the logs: Jul 4 04:04:36 mail dovecot: auth: passwd-file(user,127.11.91.218,): no passwd file: /etc/dovecot/imap.passwd Jul 4 04:04:36 mail dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa Jul 4 04:04:36 mail dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH#011PLAIN#011plaintext Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=20438 client-id=1) Jul 4 04:04:36 mail dovecot: imap-login: Internal login failure (pid=20438 id=1) (internal failure, 1 succesful auths): user=, method=PLAIN, rip=127.11.91.218, lip=73.82.101.172, mpid=20439, TLS, session= It does not help to restart the client. But when I then restart the server service dovecot restart it works again. But this is very dangerous because the server might reboot and I might not immideately have the chance to restart dovecot manually. What's going on here? mail:/# uname -a Linux mail 2.6.32-openvz-042stab090.2-amd64 #1 SMP Sat Jun 21 00:22:42 MSK 2014 i686 GNU/Linux mail:/# dovecot --version 2.1.7 Thanks, Luke From ta at geuka.net Fri Jul 4 04:44:32 2014 From: ta at geuka.net (Andreas Tauscher) Date: Fri, 04 Jul 2014 07:44:32 +0300 Subject: number of users In-Reply-To: <1404309695543-48701.post@n4.nabble.com> References: <1404309695543-48701.post@n4.nabble.com> Message-ID: <53B63130.6060703@geuka.net> > i using roundcube with dovecot, i have a question if there is possible to > know the number of users that using the mail system (in other word the > online users) . doveadm who From sca at andreasschulze.de Fri Jul 4 05:23:15 2014 From: sca at andreasschulze.de (A. Schulze) Date: Fri, 04 Jul 2014 07:23:15 +0200 Subject: [Dovecot] dovecot: disable ssl compression In-Reply-To: <53B5D31A.1060208@thinline.cz> References: <20140410150440.Horde.Gbn7XHx4blr0ZfiXKEbaAA1@horde.andreasschulze.de> <5346ADA2.7000203@thelounge.net> <20140423235219.Horde.PR-DrnYWXvVrgZ8sQM1XxQ2@horde.andreasschulze.de> <53583B70.5010507@thelounge.net> <20140424064127.Horde.PmGX52ciDTWb1ia6iZDURA1@horde.andreasschulze.de> <5358AF76.5090409@thinline.cz> <20140520194906.GB15438@solar.andreasschulze.de> <95DEB543-2727-4C87-8645-A72C747A8E63@iki.fi> <20140703235547.Horde.AEK38twBphLxWcM51fLfRA1@horde.andreasschulze.de> <53B5D31A.1060208@thinline.cz> Message-ID: <20140704072315.Horde.81Wq7BpcmA5qdYbg7_6pQA7@horde.andreasschulze.de> Jiri Bourek: > As I understand it, any program using the library has compression > turned off by default. yes, and any program using an older library version can turn off compression now, too. From giel+dovecot at mortis.eu Fri Jul 4 06:27:56 2014 From: giel+dovecot at mortis.eu (Giel van Schijndel) Date: Fri, 4 Jul 2014 08:27:56 +0200 Subject: rmdir() EBUSY warnings on 2.2.12 In-Reply-To: References: <20140703223046.GB24263@salidar.me.mortis.eu> Message-ID: <20140704062756.GA26072@salidar.me.mortis.eu> On Fri, Jul 04, 2014 at 01:59:02 +0300, Timo Sirainen wrote: > On 4.7.2014, at 1.30, Giel van Schijndel wrote: > >> I'm getting a lot of syslog spam on FreeBSD 10 from >> nfs_flush_file_handle_cache_dir where, apparently it tries to rmdir() >> the mountpoint of my mail storage. >> >>> Jul 4 00:04:44 mailhost dovecot: imap(user at example.com): Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail/vhosts/example.com) failed: Device busy >> >> We're using ZFS and have /var, /var/mail, /var/mail/vhosts, >> /var/mail/vhosts/example.com and /var/mail/vhosts/example.com/user as >> separate ZFS datasets (to enable per-user and per-domain snapshotting). >> >> So apart from NFS flushing being unnecessary (ZFS != NFS) I'm not really >> sure why using rmdir() for another directory than the Maildir specified >> in mail_location is a good idea. I.e. given that Maildirs shouldn't ever >> be emtpy (cur,new,tmp) anyway. > > Don't set mail_nfs_index=yes or mail_nfs_storage=yes and Dovecot won't > try these kludgy things to flush NFS caches. They don't fully work > anyway and they are highly discouraged for any kind of use, ever. > Mainly they exist for backwards compatibility. 1. Aren't those the defaults? Because I didn't set these options. 2. I've just explicitly set both to 'no' and I'm still seeing these errors. -- Met vriendelijke groet, With kind regards, Giel van Schijndel -- "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From HFlor at gmx.de Fri Jul 4 07:59:32 2014 From: HFlor at gmx.de (Hardy Flor) Date: Fri, 04 Jul 2014 09:59:32 +0200 Subject: imap(hardy): Panic: file istream-tee.c: line 138 (i_stream_tee_read): assertion failed: (last_high_offset == input->v_offset + size) In-Reply-To: References: <53B5520E.8050304@gmx.de> Message-ID: <53B65EE4.9060002@gmx.de> Dovecot version is 2.2.13-auto+84 Am 03.07.2014 17:47, schrieb Timo Sirainen: > On 3.7.2014, at 15.52, Hardy Flor wrote: > >> I'm copy with imapsync (on the new server with dovecot) with a single user all mails from a old server to the new server. >> >> The error-message ist after 20-30 minutes in the log, and I must restart the imapsync. The next mail is normal store on the destination box. > What Dovecot version? Can you get a gdb backtrace? http://dovecot.org/bugreport.html -------------- next part -------------- GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/lib/dovecot/imap...(no debugging symbols found)...done. Attaching to program: /usr/lib/dovecot/imap, process 27504 ptrace: Kein passender Prozess gefunden. [New LWP 27504] warning: Can't read pathname for load map: Eingabe-/Ausgabefehler. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. #0 0x00007fc66e1c0475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007fc66e1c0475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007fc66e1c36f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x00007fc66e585df5 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00007fc66e585e5e in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00007fc66e53e93e in i_panic () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x00007fc66e595a21 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #6 0x00007fc66e58ed18 in i_stream_read () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #7 0x00007fc66e58f63d in i_stream_read_data () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #8 0x00007fc66e57800e in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #9 0x00007fc66e579517 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #10 0x00007fc66e5798a9 in message_parser_parse_next_block () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #11 0x00007fc66e8931cf in index_mail_cache_parse_continue () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #12 0x00007fc66e88f2a3 in index_attachment_save_continue () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #13 0x000000000040ced1 in _start () No symbol table info available. (gdb) -------------- next part -------------- # 2.2.13 (0343869d47cf): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.5 ext4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ default_vsz_limit = 512 M dict { acl = mysql:/etc/dovecot/conf.d/dovecot-dict-sql.conf.ext } first_valid_uid = 999 hostname = ptb-mail last_valid_uid = 65533 mail_attachment_dir = /var/files/attachments mail_attachment_hash = %{md5} mail_attachment_min_size = 16 k mail_debug = yes mail_gid = vmail mail_location = mdbox:/var/mail/user/%n:LAYOUT=fs mail_plugins = acl listescape virtual mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate mdbox_rotate_size = 2000000 B namespace { list = children location = mdbox:/var/mail/projekte/:INDEXPVT=/var/mail/user/%n/projekte prefix = Projekte/ separator = / subscriptions = no type = public } namespace { list = children location = mdbox:/var/mail/user/%%n:INDEXPVT=/var/mail/user/%n/shared/%%u prefix = Benutzer/%%u/ separator = / subscriptions = no type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Archiv { auto = subscribe special_use = \Archive } mailbox Entw??rfe { auto = subscribe special_use = \Drafts } mailbox Papierkorb { auto = subscribe special_use = \Trash } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox gesendet { auto = subscribe special_use = \Sent } mailbox sent { special_use = \Sent } mailbox trash { special_use = \Trash } mailbox virtual/alle { special_use = \All } mailbox virtual/markiert { special_use = \Flagged } prefix = separator = / subscriptions = yes type = private } namespace virtual { location = virtual:/etc/dovecot/virtual:INDEX=/var/mail/user/%n/virtual:LAYOUT=fs prefix = virtual/ separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { driver = passwd } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/mail/user/share_dict mail_log_events = save delete undelete expunge copy flag_change mailbox_delete mailbox_rename mailbox_create append mail_log_fields = box msgid flags size from subject sieve = /var/mail/user/%u/dovecot.sieve sieve_dir = /var/mail/sieve/%u sieve_global_dir = /var/mail/sieve/_global sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 0 sieve_quota_max_storage = 0 } postmaster_address = postmaster at ptb-gmbh.de protocols = " imap lmtp sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/dev/lmtp { mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl_cert = References: =?UTF-8?Q?<20140608085943.GA7734@sys4.de>=09=09<20140609214425.GA31799@sys4.de>=09<5396E689.5000508@Media-Brokers.com>=20, =20<53B5D902.8010406@thinline.cz>?= Message-ID: > >> On 6/9/2014 5:44 PM, Ralf Hildebrandt wrote: > >>> That's probably the problem here. The user had LOTS of (duplicate!) > >>> mails in his inbox. I had the same problem with a corrupted IBM Domino mailfile which gave me lots of duplicates, however imapsync with the options "--useheader Date --useheader Subject --skipheader X.*" to eliminate headers according to date+subject did the trick. Alternatively you could have a look at the Thunderbird Addon "Remove Duplicate Message (alternate) 0.39" - havent used it on large IMAP folders but works also nicely. hth, infoomatic From tss at iki.fi Fri Jul 4 08:49:37 2014 From: tss at iki.fi (Timo Sirainen) Date: Fri, 4 Jul 2014 11:49:37 +0300 Subject: rmdir() EBUSY warnings on 2.2.12 In-Reply-To: <20140704062756.GA26072@salidar.me.mortis.eu> References: <20140703223046.GB24263@salidar.me.mortis.eu> <20140704062756.GA26072@salidar.me.mortis.eu> Message-ID: On 4.7.2014, at 9.27, Giel van Schijndel wrote: >> Don't set mail_nfs_index=yes or mail_nfs_storage=yes and Dovecot won't >> try these kludgy things to flush NFS caches. They don't fully work >> anyway and they are highly discouraged for any kind of use, ever. >> Mainly they exist for backwards compatibility. > > 1. Aren't those the defaults? Because I didn't set these options. > 2. I've just explicitly set both to 'no' and I'm still seeing these errors. Are you using dict-file? Looks like the NFS flushing was done there unconditionally, removed now: http://hg.dovecot.org/dovecot-2.2/rev/b2f3b9f5d7cc From florent at coppint.com Fri Jul 4 08:52:42 2014 From: florent at coppint.com (Florent B) Date: Fri, 04 Jul 2014 10:52:42 +0200 Subject: Disable user login for a few seconds ? Message-ID: <53B66B5A.4070004@coppint.com> Hi all, I need to move e-mail files of my users from one file system to another. I use a MySQL backend on Dovecot 2.1. How can I do to disable temporary an account while moving files ? I have an "active" bit in my DB, but if I set it to 0, my MX servers are bouncing mails. How can I do to disable temporary an account ? In fact, I need dovecot not to do any change on files... I think I could change account password for a while, and reset it after migration, but it will disturb connected users. Maybe I could chmod 0 files on my old file system during migration ? How Dovecot will act ? Thank you :) Flo From rs at sys4.de Fri Jul 4 09:33:35 2014 From: rs at sys4.de (Robert Schetterer) Date: Fri, 04 Jul 2014 11:33:35 +0200 Subject: Disable user login for a few seconds ? In-Reply-To: <53B66B5A.4070004@coppint.com> References: <53B66B5A.4070004@coppint.com> Message-ID: <53B674EF.20104@sys4.de> Am 04.07.2014 10:52, schrieb Florent B: > Hi all, > > I need to move e-mail files of my users from one file system to another. > > I use a MySQL backend on Dovecot 2.1. > > How can I do to disable temporary an account while moving files ? > > I have an "active" bit in my DB, but if I set it to 0, my MX servers are > bouncing mails. > > How can I do to disable temporary an account ? In fact, I need dovecot > not to do any change on files... > > I think I could change account password for a while, and reset it after > migration, but it will disturb connected users. > > Maybe I could chmod 0 files on my old file system during migration ? How > Dovecot will act ? > > Thank you :) > > Flo > read about this http://wiki2.dovecot.org/Authentication/RestrictAccess and/or if your user has static ip use firwall to reject ( be aware of nat ) and/or change behave of sql active table with i.e postfix to tmp fail etc i.e ( dont copy paste ,must fit to your postfix(sql)config !!! ) smtpd_recipient_restrictions = reject_unknown_recipient_domain, reject_non_fqdn_recipient, permit_mynetworks, check_recipient_access mysql:/etc/postfix/mysql_virtual_inactive_mailaddress.cf, mysql_virtual_inactive_mailaddress.cf ... query = SELECT CONCAT('421 mailaddress %s is set in inactive mode') address FROM mailbox WHERE username='%s' AND active = '0' be aware of all other involved postfix/sql tables where active = 0 is honored too, do hard testing before use in production after all change password might be the most easy way for only seconds Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From florent at coppint.com Fri Jul 4 09:46:40 2014 From: florent at coppint.com (Florent B) Date: Fri, 04 Jul 2014 11:46:40 +0200 Subject: Disable user login for a few seconds ? In-Reply-To: <53B674EF.20104@sys4.de> References: <53B66B5A.4070004@coppint.com> <53B674EF.20104@sys4.de> Message-ID: <53B67800.3090008@coppint.com> On 07/04/2014 11:33 AM, Robert Schetterer wrote: > Am 04.07.2014 10:52, schrieb Florent B: >> Hi all, >> >> I need to move e-mail files of my users from one file system to another. >> >> I use a MySQL backend on Dovecot 2.1. >> >> How can I do to disable temporary an account while moving files ? >> >> I have an "active" bit in my DB, but if I set it to 0, my MX servers are >> bouncing mails. >> >> How can I do to disable temporary an account ? In fact, I need dovecot >> not to do any change on files... >> >> I think I could change account password for a while, and reset it after >> migration, but it will disturb connected users. >> >> Maybe I could chmod 0 files on my old file system during migration ? How >> Dovecot will act ? >> >> Thank you :) >> >> Flo >> > read about this > > http://wiki2.dovecot.org/Authentication/RestrictAccess > > and/or > > if your user has static ip use firwall to reject ( be aware of nat ) > > and/or > > change behave of sql active table with i.e postfix to tmp fail etc > > i.e ( dont copy paste ,must fit to your postfix(sql)config !!! ) > > smtpd_recipient_restrictions = reject_unknown_recipient_domain, > reject_non_fqdn_recipient, > permit_mynetworks, > check_recipient_access > mysql:/etc/postfix/mysql_virtual_inactive_mailaddress.cf, > > mysql_virtual_inactive_mailaddress.cf > > ... > query = SELECT CONCAT('421 mailaddress %s is set in inactive mode') > address FROM mailbox WHERE username='%s' AND active = '0' > > be aware of all other involved postfix/sql tables where active = 0 is > honored too, do hard testing before use in production > > after all change password might be the most easy way for only seconds > > Best Regards > MfG Robert Schetterer > Thank you very much Robert. I also had a look at "dsync" tool. But I think it handles only mails directory, and not all user's home (my users's home contains indexes, Maildir and sieve directories). From h.reindl at thelounge.net Fri Jul 4 10:02:03 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 04 Jul 2014 12:02:03 +0200 Subject: Disable user login for a few seconds ? In-Reply-To: <53B67800.3090008@coppint.com> References: <53B66B5A.4070004@coppint.com> <53B674EF.20104@sys4.de> <53B67800.3090008@coppint.com> Message-ID: <53B67B9B.7090206@thelounge.net> Am 04.07.2014 11:46, schrieb Florent B: > Thank you very much Robert. > > I also had a look at "dsync" tool. But I think it handles only mails > directory, and not all user's home (my users's home contains indexes, > Maildir and sieve directories) rsync --force --delete-after --devices --specials -tPrlpogEAX /home/ root at new:/home/ stop services rsync --force --delete-after --devices --specials -tPrlpogEAX /home/ root at new:/home/ start services you have nearly zero downtime because rsync at the second run only transfers changed / new files and building the filelist is also much faster due OS caches -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From bambero at gmail.com Fri Jul 4 12:32:28 2014 From: bambero at gmail.com (Bambero) Date: Fri, 4 Jul 2014 14:32:28 +0200 Subject: Shared folders not listed by IMAP In-Reply-To: <53B4498F.9040202@su.lt> References: <53B3ED32.60504@su.lt> <53B4498F.9040202@su.lt> Message-ID: I made another socket in my chroot (/var/mail) and now I can see shared folders. Now my config looks like this: service auth { unix_listener auth-userdb { #mode = 0660 #user = _exim #group =. } unix_listener /var/mail/var/dovecot/auth-userdb { mode = 0666 } unix_listener auth-client { mode = 0660 user = _exim } } But why this is necessary ? In my previous version of dovecot 2.0.13 auth-userdb socket was in default location (outside chroot) and everything worked well. On Wed, Jul 2, 2014 at 8:03 PM, Giedrius Liubavi?ius wrote: > OK, > This is the problem why your configuration is not working. My shared > folder did not work up until I fixed auth-userdb permissions in a way > so that user my A (not dovecot user) [test at mydomain.pl in your > case] could connect to it and get info about user B [test2 at mydomain.pl > in your case] > > Just change the auth-userdb file location (and probably permissions) > or duplicate it to real root location. > either from within configuration files or just as a plain symlink > (maybe pre-login script ?) > > 2014.07.02 19:03, Bambero ra??: > > But the problem is that I can't see shared folders to subscribe (shared > by > > other users) while connecting via IMAP. > > > > There is also an error: > > Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No such > > file or directory > > > > Probably becouse of chroot (/var/mail). > > > > > > On Wed, Jul 2, 2014 at 1:29 PM, Giedrius Liubavi?ius > wrote: > > > >> Hi, > >> doveadm mailbox subscribe -u test at mydomain.pl Shared/ > test2 at mydomain.pl > >> doveadm mailbox subscribe -u test at mydomain.pl > >> Shared/test2 at mydomain.pl/Sent > >> > >> 2014.07.02 14:04, Bambero ra??: > >>> Hello > >>> > >>> I just upgraded my system and there is a problem with shared mailboxes. > >>> > >>> When I use the doveadm command I can see shared folders: > >>> > >>> doveadm mailbox list -u 'test at mydomain.pl' > >>> Drafts > >>> Sent > >>> Spam > >>> Trash > >>> Shared > >>> Virtuals > >>> Virtuals/all > >>> Shared/test2 at mydomain.pl > >>> Shared/test2 at mydomain.pl/Sent > >>> INBOX > >>> > >>> But I can't see them over IMAP protocol. > >>> > >>> Some config opts: > >>> > >>> valid_chroot_dirs = /var/mail > >>> mail_chroot = /var/mail > >>> > >>> namespace { > >>> type = shared > >>> separator = / > >>> prefix = Shared/%%u/ > >>> location = maildir:/%%u/Maildir:INDEX=~/Maildir/Shared/%%u > >>> subscriptions = yes > >>> list = yes > >>> } > >>> > >>> plugin { > >>> acl = vfile:cache_secs=5 > >>> } > >>> > >>> plugin { > >>> acl_shared_dict = file:/var/mail/%i.db > >>> } > >>> > >>> protocol imap { > >>> mail_plugins = $mail_plugins imap_quota imap_acl imap_zlib > >>> } > >>> > >>> > >>> My version of dovecot is 2.2.10. > >>> > >>> Regards > >>> Bambero > >>> > >> > >> > > > From tss at iki.fi Fri Jul 4 12:34:05 2014 From: tss at iki.fi (Timo Sirainen) Date: Fri, 4 Jul 2014 15:34:05 +0300 Subject: imap(hardy): Panic: file istream-tee.c: line 138 (i_stream_tee_read): assertion failed: (last_high_offset == input->v_offset + size) In-Reply-To: <53B65EE4.9060002@gmx.de> References: <53B5520E.8050304@gmx.de> <53B65EE4.9060002@gmx.de> Message-ID: On 4.7.2014, at 10.59, Hardy Flor wrote: > Dovecot version is 2.2.13-auto+84 > > > Am 03.07.2014 17:47, schrieb Timo Sirainen: >> On 3.7.2014, at 15.52, Hardy Flor wrote: >> >>> I'm copy with imapsync (on the new server with dovecot) with a single user all mails from a old server to the new server. >>> >>> The error-message ist after 20-30 minutes in the log, and I must restart the imapsync. The next mail is normal store on the destination box. >> What Dovecot version? Can you get a gdb backtrace? http://dovecot.org/bugreport.html > > This should fix it: http://hg.dovecot.org/dovecot-2.2/rev/dffc6dd2be0d From allan.cassaro at gmail.com Fri Jul 4 20:06:39 2014 From: allan.cassaro at gmail.com (Allan Cassaro) Date: Fri, 4 Jul 2014 17:06:39 -0300 Subject: Shared Mailbox + LDAP Easy with this script Message-ID: Hello guys, After some hours fighting with shared mailbox, I finally understand how it works - and, realy, I can't believe how easy it is! So, to help others like me and to improve the shared mailbox with Dovecot this script does all the "hard work". I don't know if this group permit attachments, so, let's the link: https://sites.google.com/site/allancassaro/mkshared.tar.gz Enjoy! ===== From README file ===== This is a simple code to help with Dovecot Public Shared Mailbox function. Just configure a public shared mailbox with ACLs, change the configuration file and run this program. How it works: 1) The program connect to the LDAP server and fetch groups from it (with ldap filter) 2) With groups, it fetches the members and owners (or any attribute you want); 3) It will walk into the "shared folder" folder base directory and: 3.1) Rename any directory that was renamed in LDAP (based on entryUUID ldap attribute); 3.2) Create diretories and skeletion (new, cur and tmp) of any group that exists in LDAP; 3.3) Optionaly, remove any "orphan" directory (wihtout a ldap entrey); Example: dn: cn=Everyone,ou=Shared_Mailbox,dc=example,dc=com objectClass: labeledURIObject objectClass: top objectClass: groupOfURLs cn: Everyone labeledURI: ldap:///ou=Users,dc=example,dc=com?uid?one?(objectClass=person) member: uid=user2,ou=users,dc=example,dc=com member: uid=user3,ou=users,dc=example,dc=com member: uid=user1,ou=users,dc=example,dc=com member: uid=user.surname,ou=users,dc=example,dc=com owner: uid=user4,ou=Users,dc=example,dc=com This will create a folder tree like this: /path/toshared/.Everyone /path/toshared/.Everyone/new /path/toshared/.Everyone/cur /path/toshared/.Everyone/tmp With permission file (/path/toshared/.Everyone/dovecot-acl): user=user1 lr ... user=user.surname lr user=user4 lrwstipekxa Hope this helps you! Enjoy. -- Use c?pia oculta (BCC ou CCO) e apague dados pessoais no campo da mensagem ao encaminhar qualquer e-mail. http://allan.cassaro.googlepages.com -------------- next part -------------- A non-text attachment was scrubbed... Name: mkshared.tar.gz Type: application/x-gzip Size: 2752 bytes Desc: not available URL: From allan.cassaro at gmail.com Fri Jul 4 23:46:18 2014 From: allan.cassaro at gmail.com (Allan Cassaro) Date: Fri, 4 Jul 2014 20:46:18 -0300 Subject: Shared Mailbox + LDAP Easy with this script Message-ID: Hello guys, After some hours fighting with shared mailbox, I finally understand how it works - and, realy, I can't believe how easy it is! So, to help others like me and to improve the shared mailbox with Dovecot this script does all the "hard work". I don't know if this group permit attachments, so, let's the link: https://sites.google.com/site/allancassaro/mkshared.tar.gz Enjoy! ===== From README file ===== This is a simple code to help with Dovecot Public Shared Mailbox function. Just configure a public shared mailbox with ACLs, change the configuration file and run this program. How it works: 1) The program connect to the LDAP server and fetch groups from it (with ldap filter) 2) With groups, it fetches the members and owners (or any attribute you want); 3) It will walk into the "shared folder" folder base directory and: 3.1) Rename any directory that was renamed in LDAP (based on entryUUID ldap attribute); 3.2) Create diretories and skeletion (new, cur and tmp) of any group that exists in LDAP; 3.3) Optionaly, remove any "orphan" directory (wihtout a ldap entrey); Example: dn: cn=Everyone,ou=Shared_Mailbox, dc=example,dc=com objectClass: labeledURIObject objectClass: top objectClass: groupOfURLs cn: Everyone labeledURI: ldap:///ou=Users,dc=example,dc=com?uid?one?(objectClass=person) member: uid=user2,ou=users,dc=example,dc=com member: uid=user3,ou=users,dc=example,dc=com member: uid=user1,ou=users,dc=example,dc=com member: uid=user.surname,ou=users,dc=example,dc=com owner: uid=user4,ou=Users,dc=example,dc=com This will create a folder tree like this: /path/toshared/.Everyone /path/toshared/.Everyone/new /path/toshared/.Everyone/cur /path/toshared/.Everyone/tmp With permission file (/path/toshared/.Everyone/dovecot-acl): user=user1 lr ... user=user.surname lr user=user4 lrwstipekxa Hope this helps you! Enjoy. -- Use c?pia oculta (BCC ou CCO) e apague dados pessoais no campo da mensagem ao encaminhar qualquer e-mail. http://allan.cassaro.googlepages.com From nick.z.edwards at gmail.com Sat Jul 5 00:55:54 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Sat, 5 Jul 2014 10:55:54 +1000 Subject: Disable user login for a few seconds ? In-Reply-To: <53B67800.3090008@coppint.com> References: <53B66B5A.4070004@coppint.com> <53B674EF.20104@sys4.de> <53B67800.3090008@coppint.com> Message-ID: stop mail server daemons (you DO have a backup MX I hope if you only have one mail server), rsync, (or if theres not much, sshfs and "cp -a") start mail server daemons. if this is a different machine, with new IP, hope you changed your DNS to TTL 0 - and did it at least 24 hours ago so changes are picked up right away (dont forget to reset TTL to 1D again) On 7/4/14, Florent B wrote: > On 07/04/2014 11:33 AM, Robert Schetterer wrote: >> Am 04.07.2014 10:52, schrieb Florent B: >>> Hi all, >>> >>> I need to move e-mail files of my users from one file system to another. >>> >>> I use a MySQL backend on Dovecot 2.1. >>> >>> How can I do to disable temporary an account while moving files ? >>> >>> I have an "active" bit in my DB, but if I set it to 0, my MX servers are >>> bouncing mails. >>> >>> How can I do to disable temporary an account ? In fact, I need dovecot >>> not to do any change on files... >>> >>> I think I could change account password for a while, and reset it after >>> migration, but it will disturb connected users. >>> >>> Maybe I could chmod 0 files on my old file system during migration ? How >>> Dovecot will act ? >>> >>> Thank you :) >>> >>> Flo >>> >> read about this >> >> http://wiki2.dovecot.org/Authentication/RestrictAccess >> >> and/or >> >> if your user has static ip use firwall to reject ( be aware of nat ) >> >> and/or >> >> change behave of sql active table with i.e postfix to tmp fail etc >> >> i.e ( dont copy paste ,must fit to your postfix(sql)config !!! ) >> >> smtpd_recipient_restrictions = reject_unknown_recipient_domain, >> reject_non_fqdn_recipient, >> permit_mynetworks, >> check_recipient_access >> mysql:/etc/postfix/mysql_virtual_inactive_mailaddress.cf, >> >> mysql_virtual_inactive_mailaddress.cf >> >> ... >> query = SELECT CONCAT('421 mailaddress %s is set in inactive mode') >> address FROM mailbox WHERE username='%s' AND active = '0' >> >> be aware of all other involved postfix/sql tables where active = 0 is >> honored too, do hard testing before use in production >> >> after all change password might be the most easy way for only seconds >> >> Best Regards >> MfG Robert Schetterer >> > > Thank you very much Robert. > > I also had a look at "dsync" tool. But I think it handles only mails > directory, and not all user's home (my users's home contains indexes, > Maildir and sieve directories). > From ta at geuka.net Sat Jul 5 05:28:13 2014 From: ta at geuka.net (Andreas Tauscher) Date: Sat, 05 Jul 2014 08:28:13 +0300 Subject: number of users In-Reply-To: <53B6BEF7.7010004@cs.ucy.ac.cy> References: <1404309695543-48701.post@n4.nabble.com> <53B63130.6060703@geuka.net> <53B6BEF7.7010004@cs.ucy.ac.cy> Message-ID: <53B78CED.4050805@geuka.net> > No, this will not do it. Any user coming from an HTTP connection will > appear very briefly on the Dovecot server and is unlikely to appear > on the "doveadm who" list. This is a result of the HTTP > connectionless protocol, nothing to do with Dovecot (ie > connects-carries a brief data > transmission/commands-disconnects-connects again after a > predetermined time). The connection time is very brief, even though > you can probably catch a few if you insist on typing doveadm who. If like from Nick Edwards suggested a imapproxy is used it will. imapproxy is keeping the connection open. doveadm who will give you a list of all actual logged in users. Without imapproxy you are right: Every page reload will cause a login and a logoff. I get some webmail users by "accident". To get an overview how many users used roudcube within a period check the database table users/last_login. Andreas From tlx at leuxner.net Sat Jul 5 05:52:38 2014 From: tlx at leuxner.net (Thomas Leuxner) Date: Sat, 5 Jul 2014 07:52:38 +0200 Subject: Assertion virtual-storage.c Message-ID: <20140705055238.GA37160@nihlus.leuxner.net> # 2.2.13 (dffc6dd2be0d): /etc/dovecot/dovecot.conf # OS: Linux 3.14-0.bpo.1-amd64 x86_64 Debian 7.5 Latest HG has issues with Virtual Mailboxes. I was unable to get it dump a core. Jul 5 07:46:51 nihlus dovecot: imap(tlx at leuxner.net): Panic: file virtual-storage.c: line 326 (virtual_backend_box_open): assertion failed: (!bbox->box->opened) Jul 5 07:46:51 nihlus dovecot: imap(tlx at leuxner.net): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6ce3f) [0x7fe9e733ee3f] -> /usr/lib/dovecot/libdovecot.so.0(+0x6ce9e) [0x7fe9e733ee9e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fe9e72f796e] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0xa1d4) [0x7fe9e5ae01d4] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0xa237) [0x7fe9e5ae0237] -> dovecot/imap(cmd_idle+0x45) [0x410595] -> dovecot/imap(command_exec+0x3c) [0x41849c] -> dovecot/imap() [0x4174e0] -> dovecot/imap() [0x417574] -> dovecot/imap(client_handle_input+0x115) [0x417855] -> dovecot/imap(client_input+0x72) [0x417c02] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4e) [0x7fe9e735002e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fe9e7351057] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fe9e73500b9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fe9e7350138] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fe9e72fcdd3] -> dovecot/imap(main+0x298) [0x40c238] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fe9e6f65ead] -> dovecot/imap() [0x40c39d] Jul 5 07:46:51 nihlus dovecot: imap(tlx at leuxner.net): Fatal: master: service(imap): child 37155 killed with signal 6 (core not dumped) Regards Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From giel+dovecot at mortis.eu Sat Jul 5 08:32:53 2014 From: giel+dovecot at mortis.eu (Giel van Schijndel) Date: Sat, 5 Jul 2014 10:32:53 +0200 Subject: rmdir() EBUSY warnings on 2.2.12 In-Reply-To: References: <20140703223046.GB24263@salidar.me.mortis.eu> <20140704062756.GA26072@salidar.me.mortis.eu> Message-ID: <20140705083253.GB29708@salidar.dom.custoft.eu> On Fri, Jul 04, 2014 at 11:49:37 +0300, Timo Sirainen wrote: > On 4.7.2014, at 9.27, Giel van Schijndel wrote: >>> Don't set mail_nfs_index=yes or mail_nfs_storage=yes and Dovecot won't >>> try these kludgy things to flush NFS caches. They don't fully work >>> anyway and they are highly discouraged for any kind of use, ever. >>> Mainly they exist for backwards compatibility. >> >> 1. Aren't those the defaults? Because I didn't set these options. >> 2. I've just explicitly set both to 'no' and I'm still seeing these errors. > > Are you using dict-file? Looks like the NFS flushing was done there unconditionally, removed now: http://hg.dovecot.org/dovecot-2.2/rev/b2f3b9f5d7cc I'm using acl_shared_dict > acl_shared_dict = file:/var/mail/vhosts/%d/shared-mailboxes.db That uses a file-stored dictionary but I'm not sure that means it uses dict-file. Would that trigger the NFS flushing attempts? -- Met vriendelijke groet, With kind regards, Giel van Schijndel -- "A clever person solves a problem. A wise person avoids it." -- Albert Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From toni at solu.fi Sun Jul 6 09:07:15 2014 From: toni at solu.fi (Toni Mattila) Date: Sun, 06 Jul 2014 12:07:15 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d Message-ID: <53B911C3.2020004@solu.fi> Hi, Getting following panics with traces: Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Cached message size smaller than expected (1782 < 1872) Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Maildir filename has wrong S value, renamed the file from /path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S to /path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1872:2,S Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Corrupted index cache file /path/cencored/Maildir/dovecot.index.cache: Broken physical size for mail UID 5758 Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: read(/path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S) failed: Invalid argument Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: read(/path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S) failed: Invalid argument (uid=5758) Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Cached message size smaller than expected (1781 < 1869) Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Maildir filename has wrong S value, renamed the file from /path/cencored/Maildir/cur/1201767850.29173.host.cencored.fi,S=1781:2,S to /path/cencored/Maildir/cur/1201767850.29173.host.cencored.fi,S=1869:2,S Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Corrupted index cache file /path/cencored/Maildir/dovecot.index.cache: Broken physical size for mail UID 5767 Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: read(/path/cencored/Maildir/cur/1201767850.29173.host.cencored.fi,S=1781:2,S) failed: Invalid argument Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: read(/path/cencored/Maildir/cur/1201767850.29173.host.cencored.fi,S=1781:2,S) failed: Invalid argument (uid=5767) Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Cached message size smaller than expected (9252 < 9346) Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Maildir filename has wrong S value, renamed the file from /path/cencored/Maildir/cur/1205131753.12346.host.cencored.fi,S=9252:2,RS to /path/cencored/Maildir/cur/1205131753.12346.host.cencored.fi,S=9346:2,RS Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Corrupted index cache file /path/cencored/Maildir/dovecot.index.cache: Broken physical size for mail UID 6296 Jul 6 08:11:52 dovecot: imap(user at domain.tld): Panic: file istream.c: line 167 (i_stream_read): assertion failed: (old_size <= _stream->pos - _stream->skip) Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x575c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x575c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x575514] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x13b) [0x57f99b] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x2b) [0x57fbfb] -> /usr/lib/dovecot/libdovecot.so.0 [0x565b5e] -> /usr/lib/dovecot/libdovecot.so.0 [0x567469] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x43) [0x565cd3] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_body+0x2c) [0x565e4c] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x944dd2] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_parts+0x6a) [0x945c7a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_parts+0x16) [0x91ad76] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x94aa7c] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x94ba89] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblo Jul 6 08:11:52 dovecot: imap(user at domain.tld): Fatal: master: service(imap): child 31268 killed with signal 6 (core dumps disabled) These can of course be fixed with maildir-size-fix.pl and deleting dovecot index files, but there are thousands like these. Dovecot 1.2 didn't have any issues with these old maildirs transfered over from courierimap. Best Regards, Toni Mattila From tss at iki.fi Sun Jul 6 16:10:38 2014 From: tss at iki.fi (Timo Sirainen) Date: Sun, 6 Jul 2014 19:10:38 +0300 Subject: Assertion virtual-storage.c In-Reply-To: <20140705055238.GA37160@nihlus.leuxner.net> References: <20140705055238.GA37160@nihlus.leuxner.net> Message-ID: On 5.7.2014, at 8.52, Thomas Leuxner wrote: > Latest HG has issues with Virtual Mailboxes. I was unable to get it dump a core. > > Jul 5 07:46:51 nihlus dovecot: imap(tlx at leuxner.net): Panic: file virtual-storage.c: line 326 (virtual_backend_box_open): assertion failed: (!bbox->box->opened) http://hg.dovecot.org/dovecot-2.2/rev/f1d29866e147 should fix this. There are some other larger virtual mailbox changes though, hopefully not too badly broken. But on the plus side it should now be able to handle virtual folders that consist of a large number of physical folders. From tss at iki.fi Sun Jul 6 16:11:15 2014 From: tss at iki.fi (Timo Sirainen) Date: Sun, 6 Jul 2014 19:11:15 +0300 Subject: rmdir() EBUSY warnings on 2.2.12 In-Reply-To: <20140705083253.GB29708@salidar.dom.custoft.eu> References: <20140703223046.GB24263@salidar.me.mortis.eu> <20140704062756.GA26072@salidar.me.mortis.eu> <20140705083253.GB29708@salidar.dom.custoft.eu> Message-ID: On 5.7.2014, at 11.32, Giel van Schijndel wrote: > On Fri, Jul 04, 2014 at 11:49:37 +0300, Timo Sirainen wrote: >> >> Are you using dict-file? Looks like the NFS flushing was done there unconditionally, removed now: http://hg.dovecot.org/dovecot-2.2/rev/b2f3b9f5d7cc > > I'm using acl_shared_dict >> acl_shared_dict = file:/var/mail/vhosts/%d/shared-mailboxes.db > > That uses a file-stored dictionary but I'm not sure that means it uses > dict-file. Would that trigger the NFS flushing attempts? Yep, that's the one ("file:" = dict file backend). From tss at iki.fi Sun Jul 6 17:23:11 2014 From: tss at iki.fi (Timo Sirainen) Date: Sun, 6 Jul 2014 20:23:11 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: <53B911C3.2020004@solu.fi> References: <53B911C3.2020004@solu.fi> Message-ID: On 6.7.2014, at 12.07, Toni Mattila wrote: > Getting following panics with traces: > Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Cached message size smaller than expected (1782 < 1872) > Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Maildir filename has wrong S value, renamed the file from /path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S to /path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1872:2,S > Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Corrupted index cache file /path/cencored/Maildir/dovecot.index.cache: Broken physical size for mail UID 5758 > Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: read(/path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S) failed: Invalid argument > Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: read(/path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S) failed: Invalid argument (uid=5758) This is intended. > Jul 6 08:11:52 dovecot: imap(user at domain.tld): Panic: file istream.c: line 167 (i_stream_read): assertion failed: (old_size <= _stream->pos - _stream->skip) This isn't intended, but I can't seem to be able to reproduce the crash. What's your doveconf -n output? > These can of course be fixed with maildir-size-fix.pl and deleting dovecot index files, but there are thousands like these. Dovecot 1.2 didn't have any issues with these old maildirs transfered over from courierimap. maildir_broken_filename_sizes=yes restores the old behavior. From toni at solu.fi Sun Jul 6 18:07:08 2014 From: toni at solu.fi (Toni Mattila) Date: Sun, 06 Jul 2014 21:07:08 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: References: <53B911C3.2020004@solu.fi> Message-ID: <53B9904C.1090003@solu.fi> Hi, On 6.7.2014 20:23, Timo Sirainen wrote: >> Jul 6 08:11:52 dovecot: imap(user at domain.tld): Panic: file istream.c: line 167 (i_stream_read): assertion failed: (old_size <= _stream->pos - _stream->skip) > This isn't intended, but I can't seem to be able to reproduce the crash. What's your doveconf -n output? auth_mechanisms = plain apop auth_verbose = yes auth_verbose_passwords = plain:5 default_client_limit = 5000 default_process_limit = 1000 default_vsz_limit = 384 M disable_plaintext_auth = no first_valid_uid = 89 imap_idle_notify_interval = 6 mins mail_location = maildir:~/Maildir mail_plugins = " mail_log notify" mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . } passdb { driver = vpopmail } plugin { mail_log_events = mailbox_delete mailbox_rename sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_max_script_size = 5M } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %f protocols = imap pop3 lmtp sieve service imap-login { inet_listener imap { address = 0.0.0.0 port = 143 } inet_listener imaps { address = 0.0.0.0 port = 993 } } service managesieve-login { inet_listener sieve { address = 0.0.0.0 port = 4190 } service_count = 1 } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { address = 0.0.0.0 port = 110 } inet_listener pop3s { address = 0.0.0.0 port = 995 } } ssl_cert = > These can of course be fixed with maildir-size-fix.pl and deleting dovecot index files, but there are thousands like these. Dovecot 1.2 didn't have any issues with these old maildirs transfered over from courierimap. > maildir_broken_filename_sizes=yes restores the old behavior. Ok will try that too. I have now enabled coredumps just to see if I can get more info. This 32bit Centos 5. Thanks, Toni From tlx at leuxner.net Sun Jul 6 19:09:18 2014 From: tlx at leuxner.net (Thomas Leuxner) Date: Sun, 6 Jul 2014 21:09:18 +0200 Subject: Assertion virtual-storage.c In-Reply-To: References: <20140705055238.GA37160@nihlus.leuxner.net> Message-ID: <20140706190918.GA32626@nihlus.leuxner.net> * Timo Sirainen 2014.07.06 18:10: > http://hg.dovecot.org/dovecot-2.2/rev/f1d29866e147 should fix this. There are some other larger virtual mailbox changes though, hopefully not too badly broken. But on the plus side it should now be able to handle virtual folders that consist of a large number of physical folders. That seems to have fixed it. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From wuweiwwd at sina.com Mon Jul 7 07:37:56 2014 From: wuweiwwd at sina.com (wuwei) Date: Mon, 7 Jul 2014 00:37:56 -0700 (PDT) Subject: [help]how to refresh pigeonhole sieve vacation days data Message-ID: <1404718676404-48784.post@n4.nabble.com> hello everybody: I'm using dovecot with pigeonhole sieve Plugin.everything goes well.but when i use vacation module,i found a problem: I write a sieve with a vacation module in, and put it to the sieve location ,used *PUTSCRIPT* comand with *ManageSieve* and *set it ACTIVE*.It's work!I use A email send mail to him and receive an auto-reply.then ,I modify the sieve only change the days num from 7 to 1.Then I use B email send mail to him and receive an auto-reply too. The next day,I send two mails too.But only B receive the auto-reply.I thought that I would receive two mails too. so i think that A email's data in sieve maybe still 7 days.Then I restart the dovecot,but the problem still exsit. Is anyone know how to refresh the data or is their anyother way to solve the problem? thank you! -- View this message in context: http://dovecot.2317879.n4.nabble.com/help-how-to-refresh-pigeonhole-sieve-vacation-days-data-tp48784.html Sent from the Dovecot mailing list archive at Nabble.com. From halflife4 at gmx.com Mon Jul 7 09:02:23 2014 From: halflife4 at gmx.com (Toney Mareo) Date: Mon, 7 Jul 2014 11:02:23 +0200 Subject: Fw: LMTP segfaulting constantly References: Message-ID: Hello ? I have the dmesg loaded with lmtp crash messages. My OS: ? No LSB modules are available. Distributor ID:?? ?Debian Description:?? ?Debian GNU/Linux 7.4 (wheezy) Release:?? ?7.4 Codename:?? ?wheezy ? My postfix version: ? i? postfix??????????????????????????? 2.9.6-2?????????????????????? amd64??????? High-performance mail transport agent ii? postfix-doc??????????????????????? 2.9.6-2?????????????????????? all????????? Documentation for Postfix ii? postfix-mysql????????????????????? 2.9.6-2?????????????????????? amd64??????? MySQL map support for Postfix ii? postfix-pcre?????????????????????? 2.9.6-2?????????????????????? amd64??????? PCRE map support for Postfix ii dovecot-antispam 2.0+20130822-21 amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-11 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-11 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 1:2.2.10-11 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 1:2.2.10-11 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.10-11 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.10-11 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.10-11 amd64 secure POP3/IMAP server - Sieve filters support Wed Jun 18 13:09:14 2014] lmtp[17453]: segfault at 238 ip 00007f560c3c8ce4 sp 00007fff15b0a440 error 4 in libdovecot-sieve.so.0.0.0[7f560c3a2000+82000] [Wed Jun 18 15:56:22 2014] lmtp[17325]: segfault at 238 ip 00007f2b359aace4 sp 00007fffc3a63e10 error 4 in libdovecot-sieve.so.0.0.0[7f2b35984000+82000] [Mon Jun 23 06:56:44 2014] lmtp[1168]: segfault at 238 ip 00007f5ec34d2ce4 sp 00007fff76545070 error 4 in libdovecot-sieve.so.0.0.0[7f5ec34ac000+82000] [Mon Jun 23 09:47:01 2014] lmtp[20612]: segfault at 238 ip 00007f5fb3830ce4 sp 00007fffea15dc60 error 4 in libdovecot-sieve.so.0.0.0[7f5fb380a000+82000] [Mon Jun 23 10:19:31 2014] lmtp[24839]: segfault at 238 ip 00007f8098ddbce4 sp 00007fffff3f8af0 error 4 in libdovecot-sieve.so.0.0.0[7f8098db5000+82000] [Mon Jun 23 14:45:27 2014] lmtp[28080]: segfault at 238 ip 00007fc2ea901ce4 sp 00007fff528f62d0 error 4 in libdovecot-sieve.so.0.0.0[7fc2ea8db000+82000] [Tue Jun 24 13:58:35 2014] lmtp[31028]: segfault at 238 ip 00007f2c4c493ce4 sp 00007fff5ab22080 error 4 in libdovecot-sieve.so.0.0.0[7f2c4c46d000+82000] [Tue Jun 24 14:50:51 2014] lmtp[9487]: segfault at 238 ip 00007f384ca7ece4 sp 00007fff7a02c520 error 4 in libdovecot-sieve.so.0.0.0[7f384ca58000+82000] [Tue Jun 24 14:55:19 2014] lmtp[10541]: segfault at 238 ip 00007f640e9e3ce4 sp 00007fff9e538060 error 4 in libdovecot-sieve.so.0.0.0[7f640e9bd000+82000] [Tue Jun 24 20:37:47 2014] lmtp[5914]: segfault at 238 ip 00007f7869e11ce4 sp 00007fff962eaaf0 error 4 in libdovecot-sieve.so.0.0.0[7f7869deb000+82000] [Wed Jun 25 09:28:43 2014] lmtp[1855]: segfault at 238 ip 00007ff5c473ace4 sp 00007fff521f08e0 error 4 in libdovecot-sieve.so.0.0.0[7ff5c4714000+82000] [Thu Jun 26 08:11:30 2014] lmtp[4735]: segfault at 238 ip 00007ffe9017fce4 sp 00007fffbe67ed90 error 4 in libdovecot-sieve.so.0.0.0[7ffe90159000+82000] [Thu Jun 26 11:49:57 2014] lmtp[17082]: segfault at 238 ip 00007f5ce9e20ce4 sp 00007fff234152e0 error 4 in libdovecot-sieve.so.0.0.0[7f5ce9dfa000+82000] [Thu Jun 26 15:34:27 2014] lmtp[682]: segfault at 238 ip 00007ffa9c191ce4 sp 00007fff0c6ee870 error 4 in libdovecot-sieve.so.0.0.0[7ffa9c16b000+82000] [Thu Jun 26 16:43:17 2014] lmtp[15603]: segfault at 238 ip 00007f3994435ce4 sp 00007fff32b93500 error 4 in libdovecot-sieve.so.0.0.0[7f399440f000+82000] [Mon Jun 30 10:19:43 2014] lmtp[473]: segfault at 238 ip 00007fe0e4706ce4 sp 00007fff97b648b0 error 4 in libdovecot-sieve.so.0.0.0[7fe0e46e0000+82000] [Tue Jul? 1 07:06:12 2014] lmtp[28516]: segfault at 238 ip 00007f62fbcfcce4 sp 00007fffdd76fd80 error 4 in libdovecot-sieve.so.0.0.0[7f62fbcd6000+82000] [Tue Jul? 1 12:43:01 2014] lmtp[32438]: segfault at 238 ip 00007fc4bdda6ce4 sp 00007fff6f527820 error 4 in libdovecot-sieve.so.0.0.0[7fc4bdd80000+82000] [Wed Jul? 2 13:21:20 2014] lmtp[28053]: segfault at 238 ip 00007f112a1d4ce4 sp 00007fff0706e350 error 4 in libdovecot-sieve.so.0.0.0[7f112a1ae000+82000] [Wed Jul? 2 16:19:42 2014] lmtp[30986]: segfault at 238 ip 00007f7e0ad15ce4 sp 00007fff68c1b710 error 4 in libdovecot-sieve.so.0.0.0[7f7e0acef000+82000] [Wed Jul? 2 16:36:18 2014] lmtp[2223]: segfault at 238 ip 00007f69ecc40ce4 sp 00007fff2e8783d0 error 4 in libdovecot-sieve.so.0.0.0[7f69ecc1a000+82000] [Thu Jul? 3 09:14:59 2014] lmtp[30956]: segfault at 238 ip 00007f86f1dccce4 sp 00007fffae17fc70 error 4 in libdovecot-sieve.so.0.0.0[7f86f1da6000+82000] [Thu Jul? 3 09:38:18 2014] lmtp[3631]: segfault at 238 ip 00007fae2d901ce4 sp 00007fff3f7a9270 error 4 in libdovecot-sieve.so.0.0.0[7fae2d8db000+82000] [Thu Jul? 3 10:18:09 2014] lmtp[12435]: segfault at 238 ip 00007f49343bfce4 sp 00007fff29e64670 error 4 in libdovecot-sieve.so.0.0.0[7f4934399000+82000] [Fri Jul? 4 11:34:27 2014] lmtp[22575]: segfault at 238 ip 00007f9e52493ce4 sp 00007fff765e9fe0 error 4 in libdovecot-sieve.so.0.0.0[7f9e5246d000+82000] [Fri Jul? 4 11:49:37 2014] lmtp[26586]: segfault at 238 ip 00007f387638fce4 sp 00007fff624bf970 error 4 in libdovecot-sieve.so.0.0.0[7f3876369000+82000] [Sun Jul? 6 13:49:15 2014] lmtp[15451]: segfault at 238 ip 00007fa435865ce4 sp 00007fff436a28f0 error 4 in libdovecot-sieve.so.0.0.0[7fa43583f000+82000] ? The server itself is working, but it's annoying seeing these messages in the logs. Sometimes when it's overloaded it refuses to authenticate users (i don't think this has to do with it). ? Any ideas what causes it? I have my debian wheezy updated to the latest. ? Thanks From toni at solu.fi Mon Jul 7 09:47:18 2014 From: toni at solu.fi (Toni Mattila) Date: Mon, 07 Jul 2014 12:47:18 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: References: <53B911C3.2020004@solu.fi> Message-ID: <53BA6CA6.3050705@solu.fi> Hi, Here is gdb backtrace for the crash. #0 0x00f69402 in __kernel_vsyscall () No symbol table info available. #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #3 0x00575c14 in default_fatal_finish (type=, status=0) at failures.c:193 backtrace = 0x86ae100 "/usr/lib/dovecot/libdovecot.so.0 [0x575c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x575c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x575514] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x13b) [0x57"... #4 0x00575c9d in i_internal_fatal_handler (ctx=0xbfbc1c94, format=0x5a2784 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfbc1cb4 "\f?Z") at failures.c:657 status = 0 #5 0x00575514 in i_panic (format=0x5a2784 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:267 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = 0xbfbc1cb4 "\f?Z" #6 0x0057f99b in i_stream_read (stream=0x86ea960) at istream.c:170 _stream = (struct istream_private *) 0x86ea928 old_size = 8192 ret = -2 __FUNCTION__ = "i_stream_read" #7 0x0057fbfb in i_stream_read_data (stream=0x86ea960, data_r=0xbfbc1d64, size_r=0xbfbc1d60, threshold=8192) at istream.c:536 ret = 8191 read_more = false __FUNCTION__ = "i_stream_read_data" #8 0x00564927 in message_parse_header_next (ctx=0x86f1770, hdr_r=0xbfbc1da4) at message-header-parser.c:89 msg = ( const unsigned char *) 0x871de58 "References: <1397041424.77339.YahooMailNeo at web161206.mail.bf1.yahoo.com> <1397041447.45218.YahooMailNeo at web161202.mail.bf1.yahoo.com> <1397041471.51235.YahooMailNeo at web161205.mail.bf1.yahoo.com> <1397"... i = size = 8192 startpos = 8191 colon_pos = 10 parse_size = 8191 ret = 1 continued = false continues = crlf_newline = __FUNCTION__ = "message_parse_header_next" #9 0x00565414 in message_parse_header (input=0x86ea960, hdr_size=0x0, flags=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=0x94ae40 , context=0xbfbc1e0c) at message-header-parser.c:393 hdr_ctx = (struct message_header_parser_ctx *) 0x86f1770 hdr = (struct message_header_line *) 0x0 ret = __FUNCTION__ = "message_parse_header" #10 0x0094a9c8 in search_match_once (ctx=0x86ee338) at index-search.c:697 ret = #11 0x0094ba89 in search_more (ctx=0x86ee338, mail_r=0xbfbc1f28) at index-search.c:1401 imail = ret = #12 0x0094c5fe in index_storage_search_next_nonblock (_ctx=0x86ee338, mail_r=0xbfbc1f94, tryagain_r=0xbfbc1f9b) at index-search.c:1677 ctx = (struct index_search_context *) 0x0 mail = mailp = seq = ret = #13 0x009222ee in mailbox_search_next_nonblock (ctx=0x86ee338, mail_r=0xbfbc1f94, tryagain_r=0xbfbc1f9b) at mail-storage.c:1796 box = (struct mailbox *) 0x6 #14 0x08062b40 in cmd_search_more (cmd=0x86cc438) at imap-search.c:443 ctx = (struct imap_search_context *) 0x86cc500 opts = SEARCH_RETURN_ALL mail = (struct mail *) 0x0 sync_flags = end_time = {tv_sec = 6135364, tv_usec = 141343184} id = 8050 id_min = 8050 id_max = 8050 time_msecs = tryagain = lost_data = __FUNCTION__ = "cmd_search_more" #15 0x08063214 in cmd_search_more_callback (cmd=0x86cc438) at imap-search.c:527 client = (struct client *) 0x86cb9d0 finished = #16 0x0058822e in io_loop_handle_timeouts (ioloop=0x86b6498) at ioloop.c:410 timeout = _data_stack_cur_id = 2 #17 0x005896e7 in io_loop_handler_run_internal (ioloop=0x86b6498) at ioloop-epoll.c:193 ctx = (struct ioloop_handler_context *) 0x86b7610 event = list = io = tv = {tv_sec = 0, tv_usec = 0} msecs = 0 ret = 0 i = j = call = __FUNCTION__ = "io_loop_handler_run_internal" #18 0x00587e1e in io_loop_handler_run (ioloop=0x86b6498) at ioloop.c:488 No locals. #19 0x00587ea8 in io_loop_run (ioloop=0x86b6498) at ioloop.c:465 __FUNCTION__ = "io_loop_run" #20 0x0052e42d in master_service_run (service=0x86b63c0, callback=0x8066000 ) at master-service.c:566 No locals. #21 0x08065e9f in main (argc=Cannot access memory at address 0x0 ) at main.c:400 login_set = {auth_socket_path = 0x86ae038 "P?j\b", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x80660c0 , failure_callback = 0x8066060 , request_auth_token = 1} service_flags = storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = set_roots = {0x806daa0, 0x0} Panic: file istream.c: line 167 (i_stream_read): assertion failed: (old_size <= _stream->pos - _stream->skip) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x575c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x575c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x575514] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x13b) [0x57f99b] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x2b) [0x57fbfb] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x87) [0x564927] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x54) [0x565414] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x94a9c8] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x94ba89] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0xde) [0x94c5fe] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x3e) [0x9222ee] -> dovecot/imap [0x8062b40] -> dovecot/imap [0x8063214] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xbe) [0x58822e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x97) [0x Fatal: master: service(imap): child 6201 killed with signal 6 (core dumped) Thanks, Toni From mailinglists at easy-mail.it Mon Jul 7 10:01:35 2014 From: mailinglists at easy-mail.it (Francesco) Date: Mon, 07 Jul 2014 12:01:35 +0200 Subject: dbox alternate storage and samba Message-ID: <1404727295.3690.21.camel@secoges-laptop> Hello everyone, i was just wondering if it's possible to use a samba share as an alternate storage for dbox format. I tried creating a samba share, but when i try to move the email to the alternate storage using doveadm altmove, no errors are printed but no mails are moved. Everything works if the alternate storage is simply another directory on the server hard drive. am i mssing something? thanks in advance. From h.reindl at thelounge.net Mon Jul 7 10:04:34 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 07 Jul 2014 12:04:34 +0200 Subject: dbox alternate storage and samba In-Reply-To: <1404727295.3690.21.camel@secoges-laptop> References: <1404727295.3690.21.camel@secoges-laptop> Message-ID: <53BA70B2.3080102@thelounge.net> Am 07.07.2014 12:01, schrieb Francesco: > i was just wondering if it's possible to use a samba share as an > alternate storage for dbox format mailstorage on samba? don't do that even if it would work in theory -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From mailinglists at easy-mail.it Mon Jul 7 10:07:35 2014 From: mailinglists at easy-mail.it (Francesco) Date: Mon, 07 Jul 2014 12:07:35 +0200 Subject: dbox alternate storage and samba In-Reply-To: <53BA70B2.3080102@thelounge.net> References: <1404727295.3690.21.camel@secoges-laptop> <53BA70B2.3080102@thelounge.net> Message-ID: <1404727655.3690.22.camel@secoges-laptop> Il giorno lun, 07/07/2014 alle 12.04 +0200, Reindl Harald ha scritto: > > Am 07.07.2014 12:01, schrieb Francesco: > > i was just wondering if it's possible to use a samba share as an > > alternate storage for dbox format > > mailstorage on samba? > don't do that even if it would work in theory > well, indeed i agree with you, but i was asked to check if it could be done.. guess what.. orders from the above :( i think NFS would do? From giel+dovecot at mortis.eu Mon Jul 7 10:06:28 2014 From: giel+dovecot at mortis.eu (Giel van Schijndel) Date: Mon, 7 Jul 2014 12:06:28 +0200 Subject: rmdir() EBUSY warnings on 2.2.12 In-Reply-To: References: <20140703223046.GB24263@salidar.me.mortis.eu> <20140704062756.GA26072@salidar.me.mortis.eu> <20140705083253.GB29708@salidar.dom.custoft.eu> Message-ID: <20140707100628.GA28877@galileo.sioux.eu> On Sun, Jul 06, 2014 at 07:11:15PM +0300, Timo Sirainen wrote: > On 5.7.2014, at 11.32, Giel van Schijndel wrote: >> On Fri, Jul 04, 2014 at 11:49:37 +0300, Timo Sirainen wrote: >>> Are you using dict-file? Looks like the NFS flushing was done there unconditionally, removed now: http://hg.dovecot.org/dovecot-2.2/rev/b2f3b9f5d7cc >> >> I'm using acl_shared_dict >>> acl_shared_dict = file:/var/mail/vhosts/%d/shared-mailboxes.db >> >> That uses a file-stored dictionary but I'm not sure that means it uses >> dict-file. Would that trigger the NFS flushing attempts? > > Yep, that's the one ("file:" = dict file backend). I'm now using b2f3b9f5d7cc on top of 2.2.13 (as a patch in the FreeBSD port) and I no longer see this nfs flushing errors being spammed to the logs. -- Met vriendelijke groet, With kind regards, Giel van Schijndel -- "A clever person solves a problem. A wise person avoids it." -- Albert Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: From tss at iki.fi Mon Jul 7 10:16:05 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 7 Jul 2014 13:16:05 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: <53BA6CA6.3050705@solu.fi> References: <53B911C3.2020004@solu.fi> <53BA6CA6.3050705@solu.fi> Message-ID: <8C6061E2-BCA6-4875-89ED-3A4526E9ACBB@iki.fi> Should be fixed by http://hg.dovecot.org/dovecot-2.2/rev/1a38a85d952e On 7.7.2014, at 12.47, Toni Mattila wrote: > Hi, > > Here is gdb backtrace for the crash. > #0 0x00f69402 in __kernel_vsyscall () > No symbol table info available. > #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 > No symbol table info available. > #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 > No symbol table info available. > #3 0x00575c14 in default_fatal_finish (type=, status=0) at failures.c:193 > backtrace = 0x86ae100 "/usr/lib/dovecot/libdovecot.so.0 [0x575c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x575c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x575514] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x13b) [0x57"... > #4 0x00575c9d in i_internal_fatal_handler (ctx=0xbfbc1c94, format=0x5a2784 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfbc1cb4 "\f?Z") at failures.c:657 > status = 0 > #5 0x00575514 in i_panic (format=0x5a2784 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:267 > ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} > args = 0xbfbc1cb4 "\f?Z" > #6 0x0057f99b in i_stream_read (stream=0x86ea960) at istream.c:170 > _stream = (struct istream_private *) 0x86ea928 > old_size = 8192 > ret = -2 > __FUNCTION__ = "i_stream_read" > #7 0x0057fbfb in i_stream_read_data (stream=0x86ea960, data_r=0xbfbc1d64, size_r=0xbfbc1d60, threshold=8192) at istream.c:536 > ret = 8191 > read_more = false > __FUNCTION__ = "i_stream_read_data" > #8 0x00564927 in message_parse_header_next (ctx=0x86f1770, hdr_r=0xbfbc1da4) at message-header-parser.c:89 > msg = ( > const unsigned char *) 0x871de58 "References: <1397041424.77339.YahooMailNeo at web161206.mail.bf1.yahoo.com> <1397041447.45218.YahooMailNeo at web161202.mail.bf1.yahoo.com> <1397041471.51235.YahooMailNeo at web161205.mail.bf1.yahoo.com> <1397"... > i = > size = 8192 > startpos = 8191 > colon_pos = 10 > parse_size = 8191 > ret = 1 > continued = false > continues = > crlf_newline = > __FUNCTION__ = "message_parse_header_next" > #9 0x00565414 in message_parse_header (input=0x86ea960, hdr_size=0x0, flags=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=0x94ae40 , context=0xbfbc1e0c) at message-header-parser.c:393 > hdr_ctx = (struct message_header_parser_ctx *) 0x86f1770 > hdr = (struct message_header_line *) 0x0 > ret = > __FUNCTION__ = "message_parse_header" > #10 0x0094a9c8 in search_match_once (ctx=0x86ee338) at index-search.c:697 > ret = > #11 0x0094ba89 in search_more (ctx=0x86ee338, mail_r=0xbfbc1f28) at index-search.c:1401 > imail = > ret = > #12 0x0094c5fe in index_storage_search_next_nonblock (_ctx=0x86ee338, mail_r=0xbfbc1f94, tryagain_r=0xbfbc1f9b) at index-search.c:1677 > ctx = (struct index_search_context *) 0x0 > mail = > mailp = > seq = > ret = > #13 0x009222ee in mailbox_search_next_nonblock (ctx=0x86ee338, mail_r=0xbfbc1f94, tryagain_r=0xbfbc1f9b) at mail-storage.c:1796 > box = (struct mailbox *) 0x6 > #14 0x08062b40 in cmd_search_more (cmd=0x86cc438) at imap-search.c:443 > ctx = (struct imap_search_context *) 0x86cc500 > opts = SEARCH_RETURN_ALL > mail = (struct mail *) 0x0 > sync_flags = > end_time = {tv_sec = 6135364, tv_usec = 141343184} > id = 8050 > id_min = 8050 > id_max = 8050 > time_msecs = > tryagain = > lost_data = > __FUNCTION__ = "cmd_search_more" > #15 0x08063214 in cmd_search_more_callback (cmd=0x86cc438) at imap-search.c:527 > client = (struct client *) 0x86cb9d0 > finished = > #16 0x0058822e in io_loop_handle_timeouts (ioloop=0x86b6498) at ioloop.c:410 > timeout = > _data_stack_cur_id = 2 > #17 0x005896e7 in io_loop_handler_run_internal (ioloop=0x86b6498) at ioloop-epoll.c:193 > ctx = (struct ioloop_handler_context *) 0x86b7610 > event = > list = > io = > tv = {tv_sec = 0, tv_usec = 0} > msecs = 0 > ret = 0 > i = > j = > call = > __FUNCTION__ = "io_loop_handler_run_internal" > #18 0x00587e1e in io_loop_handler_run (ioloop=0x86b6498) at ioloop.c:488 > No locals. > #19 0x00587ea8 in io_loop_run (ioloop=0x86b6498) at ioloop.c:465 > __FUNCTION__ = "io_loop_run" > #20 0x0052e42d in master_service_run (service=0x86b63c0, callback=0x8066000 ) at master-service.c:566 > No locals. > #21 0x08065e9f in main (argc=Cannot access memory at address 0x0 > ) at main.c:400 > login_set = {auth_socket_path = 0x86ae038 "P?j\b", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x80660c0 , failure_callback = 0x8066060 , > request_auth_token = 1} > service_flags = > storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT > username = 0x0 > c = > set_roots = {0x806daa0, 0x0} > > Panic: file istream.c: line 167 (i_stream_read): assertion failed: (old_size <= _stream->pos - _stream->skip) > > Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x575c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x575c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x575514] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x13b) [0x57f99b] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x2b) [0x57fbfb] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x87) [0x564927] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x54) [0x565414] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x94a9c8] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x94ba89] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0xde) [0x94c5fe] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x3e) [0x9222ee] -> dovecot/imap [0x8062b40] -> dovecot/imap [0x8063214] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xbe) [0x58822e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x97) [0x > Fatal: master: service(imap): child 6201 killed with signal 6 (core dumped) > > Thanks, > Toni From h.reindl at thelounge.net Mon Jul 7 10:22:07 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 07 Jul 2014 12:22:07 +0200 Subject: dbox alternate storage and samba In-Reply-To: <1404727655.3690.22.camel@secoges-laptop> References: <1404727295.3690.21.camel@secoges-laptop> <53BA70B2.3080102@thelounge.net> <1404727655.3690.22.camel@secoges-laptop> Message-ID: <53BA74CF.9000709@thelounge.net> Am 07.07.2014 12:07, schrieb Francesco: > Il giorno lun, 07/07/2014 alle 12.04 +0200, Reindl Harald ha scritto: >> >> Am 07.07.2014 12:01, schrieb Francesco: >>> i was just wondering if it's possible to use a samba share as an >>> alternate storage for dbox format >> >> mailstorage on samba? >> don't do that even if it would work in theory >> > > well, indeed i agree with you, but i was asked to check if it could be > done.. guess what.. orders from the above :( > > i think NFS would do? yes, better however, depending on the load a block-level storage over iSCSI would be preferred because it *really* works like a local disk but still over the network -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From toni at solu.fi Mon Jul 7 10:25:08 2014 From: toni at solu.fi (Toni Mattila) Date: Mon, 07 Jul 2014 13:25:08 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: <8C6061E2-BCA6-4875-89ED-3A4526E9ACBB@iki.fi> References: <53B911C3.2020004@solu.fi> <53BA6CA6.3050705@solu.fi> <8C6061E2-BCA6-4875-89ED-3A4526E9ACBB@iki.fi> Message-ID: <53BA7584.8070906@solu.fi> Hei, On 7.7.2014 13:16, Timo Sirainen wrote: > Should be fixed by http://hg.dovecot.org/dovecot-2.2/rev/1a38a85d952e Cheers for the quick fix. I have that now running on production and will report back soon. Thanks, Toni From toni at solu.fi Mon Jul 7 11:35:19 2014 From: toni at solu.fi (Toni Mattila) Date: Mon, 07 Jul 2014 14:35:19 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: <8C6061E2-BCA6-4875-89ED-3A4526E9ACBB@iki.fi> References: <53B911C3.2020004@solu.fi> <53BA6CA6.3050705@solu.fi> <8C6061E2-BCA6-4875-89ED-3A4526E9ACBB@iki.fi> Message-ID: <53BA85F7.5040107@solu.fi> Hi, On 7.7.2014 13:16, Timo Sirainen wrote: > Should be fixed by http://hg.dovecot.org/dovecot-2.2/rev/1a38a85d952e Nope. Still happens: (gdb) bt #0 0x00568402 in __kernel_vsyscall () #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 #3 0x00d13c14 in default_fatal_finish (type=, status=0) at failures.c:193 #4 0x00d13c9d in i_internal_fatal_handler (ctx=0xbf824104, format=0xd40784 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf824124 "\f??") at failures.c:657 #5 0x00d13514 in i_panic (format=0xd40784 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:267 #6 0x00d1d99b in i_stream_read (stream=0x85c7d20) at istream.c:170 #7 0x00d1dbfb in i_stream_read_data (stream=0x85c7d20, data_r=0xbf824264, size_r=0xbf824268, threshold=31) at istream.c:538 #8 0x00d03b5e in message_parser_read_more (ctx=0x85dc020, block_r=0xbf82425c, full_r=0xbf8241db) at message-parser.c:128 #9 0x00d05469 in parse_next_body_to_boundary (ctx=0x85dc020, block_r=0xbf82425c) at message-parser.c:361 #10 0x00d03cd3 in message_parser_parse_next_block (ctx=0x85dc020, block_r=0xbf82425c) at message-parser.c:1015 #11 0x00d03e4c in message_parser_parse_body (ctx=0x85dc020, hdr_callback=0, context=0x0) at message-parser.c:1079 #12 0x0026fdd2 in index_mail_parse_body (mail=0x85da810, field=MAIL_CACHE_FLAGS) at index-mail.c:914 #13 0x00270c7a in index_mail_get_parts (_mail=0x85da810, parts_r=0xbf824358) at index-mail.c:285 #14 0x00245d76 in mail_get_parts (mail=0x85da810, parts_r=0xbf824358) at mail.c:114 #15 0x00275a7c in search_match_once (ctx=0x85cbc28) at index-search.c:745 #16 0x00276a89 in search_more (ctx=0x85cbc28, mail_r=0xbf824458) at index-search.c:1401 #17 0x002775fe in index_storage_search_next_nonblock (_ctx=0x85cbc28, mail_r=0xbf8244c4, tryagain_r=0xbf8244cb) at index-search.c:1677 #18 0x0024d2ee in mailbox_search_next_nonblock (ctx=0x85cbc28, mail_r=0xbf8244c4, tryagain_r=0xbf8244cb) at mail-storage.c:1796 #19 0x08062b40 in cmd_search_more (cmd=0x85ac430) at imap-search.c:443 #20 0x08063079 in imap_search_start (ctx=0x85ac4e8, sargs=0x85d9000, sort_program=0x0) at imap-search.c:610 #21 0x08056d86 in cmd_search (cmd=0x85ac430) at cmd-search.c:48 #22 0x0805c953 in command_exec (cmd=0x85ac430) at imap-commands.c:158 #23 0x0805b69f in client_command_input (cmd=0x85ac430) at imap-client.c:778 #24 0x0805b751 in client_command_input (cmd=0x85ac430) at imap-client.c:839 #25 0x0805b913 in client_handle_input (client=0x85ab9c8) at imap-client.c:877 #26 0x0805bd71 in client_input (client=0x85ab9c8) at imap-client.c:931 #27 0x00d25d88 in io_loop_call_io (io=0x85ac3b0) at ioloop.c:441 #28 0x00d2775f in io_loop_handler_run_internal (ioloop=0x8596490) at ioloop-epoll.c:220 #29 0x00d25e2e in io_loop_handler_run (ioloop=0x8596490) at ioloop.c:488 #30 0x00d25eb8 in io_loop_run (ioloop=0x8596490) at ioloop.c:465 #31 0x00ccc42d in master_service_run (service=0x85963b8, callback=0x8066000 ) at master-service.c:566 #32 0x08065e9f in main (argc=Cannot access memory at address 0x0 ) at main.c:400 (gdb) f 6 #6 0x00d1d99b in i_stream_read (stream=0x85c7d20) at istream.c:170 170 i_assert(_stream->skip != _stream->pos); (gdb) p *_stream $1 = {m = {refcount = 2, name = 0x0, error = 0x85cc0a8 "Cached message size smaller than expected (3082265 < 3082342)", close = 0xd1e1e0 , destroy = 0xd1e400 , set_max_buffer_size = 0xd1e140 , destroy_callbacks = {arr = {buffer = 0x85cc070, element_size = 8}, v = 0x85cc070, v_modifiable = 0x85cc070}}, read = 0x26bf10 , seek = 0xd1cee0 , sync = 0, stat = 0xd1d140 , get_size = 0xd1cf10 , switch_ioloop = 0, istream = {v_offset = 0, stream_errno = 22, mmaped = 0, blocking = 1, closed = 0, readable_fd = 0, seekable = 1, eof = 0, real_stream = 0x85c7ce8}, fd = 16, abs_start_offset = 0, statbuf = {st_dev = 2050, __pad1 = 0, __st_ino = 45313747, st_mode = 33152, st_nlink = 1, st_uid = 89, st_gid = 89, st_rdev = 0, __pad2 = 0, st_size = 3082342, st_blksize = 4096, st_blocks = 6032, st_atim = {tv_sec = 1334256398, tv_nsec = 0}, st_mtim = {tv_sec = 1303455370, tv_nsec = 0}, st_ctim = {tv_sec = 1334256398, tv_nsec = 0}, st_ino = 45313747}, io = 0x0, buffer = 0x863cb30 "\nALUNAAC2DQAAtw0AALgNAAC5DQAAug0AALsNAAC8DQAAvQ0AAL4NAAC/DQAAwA0AAMENAADCDQAA\nww0AAMQNAADFDQAAxg0AAMcNAADIDQAAyQ0AAMoNAADLDQAAzA0AAM0NAADODQAAzw0AANANAADR\nDQAA0g0AANMNAADUDQAA1Q0AANYNAADXDQAA2A0AANkNA"..., w_buffer = 0x0, buffer_size = 0, max_buffer_size = 8192, init_buffer_size = 8192, skip = 0, pos = 0, try_alloc_limit = 0, parent = 0x8600988, parent_start_offset = 0, parent_expected_offset = 3077052, access_counter = 1136, line_str = 0x0, line_crlf = 0, return_nolf_line = 0, stream_size_passthrough = 1} (gdb) p *_stream.parent.real_stream $2 = {m = {refcount = 1, name = 0x85c7c70 "/cencored/Maildir/cur/1303455370.23018.cencored.fi,S=3082265:2,RS", error = 0x0, close = 0xd217d0 , destroy = 0xd1e400 , set_max_buffer_size = 0xd1e140 , destroy_callbacks = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, read = 0xd213f0 , seek = 0xd212c0 , sync = 0xd21000 , stat = 0xd21200 , get_size = 0xd1cf10 , switch_ioloop = 0, istream = { v_offset = 3077052, stream_errno = 0, mmaped = 0, blocking = 1, closed = 0, readable_fd = 1, seekable = 1, eof = 0, real_stream = 0x8600950}, fd = 16, abs_start_offset = 0, statbuf = {st_dev = 2050, __pad1 = 0, __st_ino = 45313747, st_mode = 33152, st_nlink = 1, st_uid = 89, st_gid = 89, st_rdev = 0, __pad2 = 0, st_size = 3082342, st_blksize = 4096, st_blocks = 6032, st_atim = {tv_sec = 1334256398, tv_nsec = 0}, st_mtim = {tv_sec = 1303455370, tv_nsec = 0}, st_ctim = {tv_sec = 1334256398, tv_nsec = 0}, st_ino = 45313747}, io = 0x0, buffer = 0x863cb30 "\nALUNAAC2DQAAtw0AALgNAAC5DQAAug0AALsNAAC8DQAAvQ0AAL4NAAC/DQAAwA0AAMENAADCDQAA\nww0AAMQNAADFDQAAxg0AAMcNAADIDQAAyQ0AAMoNAADLDQAAzA0AAM0NAADODQAAzw0AANANAADR\nDQAA0g0AANMNAADUDQAA1Q0AANYNAADXDQAA2A0AANkNA"..., w_buffer = 0x863cb30 "\nALUNAAC2DQAAtw0AALgNAAC5DQAAug0AALsNAAC8DQAAvQ0AAL4NAAC/DQAAwA0AAMENAADCDQAA\nww0AAMQNAADFDQAAxg0AAMcNAADIDQAAyQ0AAMoNAADLDQAAzA0AAM0NAADODQAAzw0AANANAADR\nDQAA0g0AANMNAADUDQAA1Q0AANYNAADXDQAA2A0AANkNA"..., buffer_size = 8192, max_buffer_size = 8192, init_buffer_size = 8192, skip = 0, pos = 5290, try_alloc_limit = 0, parent = 0x0, parent_start_offset = 0, parent_expected_offset = 0, access_counter = 1136, line_str = 0x0, line_crlf = 0, return_nolf_line = 0, stream_size_passthrough = 0} Thanks, Toni From leolistas at solutti.com.br Mon Jul 7 12:28:29 2014 From: leolistas at solutti.com.br (Leonardo Rodrigues) Date: Mon, 07 Jul 2014 09:28:29 -0300 Subject: question on lmtp logged message In-Reply-To: References: <53AAEE8D.9050604@solutti.com.br> Message-ID: <53BA926D.7080706@solutti.com.br> Em 03/07/14 14:31, Timo Sirainen escreveu: > On 25.6.2014, at 18.45, Leonardo Rodrigues wrote: > >> I have dovecot running for IMAP4/POP3 and also local delivery through LMTP. It's working just fine, absolutely no problem on that, setup is fine. >> >> Anyway, sometimes LMTP seems to not be able to deliver some messages and keep them on postfixqueue. And on the next or third try, the message gets delivered successfully. The logged message, however, is not helping me identify what is happening.Example: >> >> (error - message was expunged) >> Jun 25 11:49:39 correio postfix/lmtp[21835]: ADB0A1AC05108: to=, relay=correio.domain.com.br[private/dovecot-lmtp], conn_use=6, delay=13, delays=0.07/0/0/13, dsn=4.2.0, status=deferred (host correio.domain.com.br[private/dovecot-lmtp] said: 451 4.2.0 Message was expunged (received-date) (in reply to end of DATA command)) > I guess the only good fix for this is to just get rid of this deduplication feature for now: http://hg.dovecot.org/dovecot-2.2/rev/51274bf2a47d > > Hopefully people don't rely on this feature too much. > Timo, Is it expected deliveries through LMTP to get slower with this patch ? I mean ... despite i was seeing the 'message was expunged' some few times a day, after applying the patch they really dissapear, but my deliveries starts to apparently get slower. I dont have real numbers to prove that, i can only guanratee that my queues are starting to grow up a lot with to-be-local-delivered messages. I experienced that last week after running the patched version for some hours. Reverted to plain 2.2.13 and queues were successfully emptied after some minutes. This weekend i installed the 2.2.13 patched one again and, by this morning, queues are growing again. I really do not understand dovecot internals and, sincerily, dont even know if i'm using some feature that depends on deduplication. Fact is that i'm running a pretty busy server and those 'message was expunged' situations werent a real problem. When it happened, message would be on the queue and probably delivered some minutes later, on the 1st or 2nd queue run after that. But if removing this deduplication tests/feature will slow down that much the deliveries, i'm afraid that, overall, the non-patched version is better to me. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, N?O mandem email gertrudes at solutti.com.br My SPAMTRAP, do not email it From lazy404 at gmail.com Mon Jul 7 13:18:10 2014 From: lazy404 at gmail.com (Lazy) Date: Mon, 7 Jul 2014 15:18:10 +0200 Subject: [PATH] expire plugins segfault with misconfigured dict Message-ID: dovecot 2.2.13 With configuration like plugin { expire_dict = blblbla } expiere plugins segfaults during deinit. It might also segfault if the dict service was unavaiable. attached bellow is a diff against 2.2.13 Jul 7 14:51:11 dovecot1 dovecot: lmtp(10548, lazy): Error: expire plugin: dict_init(blblbla) failed: Dictionary URI is missing ':': blblbla Jul 7 14:51:11 dovecot1 dovecot: lmtp(10548, lazy): Fatal: master: service(lmtp): child 10548 killed with signal 11 (core dumps disabled) Program received signal SIGSEGV, Segmentation fault. 0x00007f337d8af8ae in dict_deinit (_dict=0x8) at dict.c:87 87 struct dict *dict = *_dict; (gdb) bt #0 0x00007f337d8af8ae in dict_deinit (_dict=0x8) at dict.c:87 #1 0x00007f337c88f647 in expire_mail_user_deinit (user=0x1b60e80) at expire-plugin.c:299 #2 0x00007f337cca3e7f in quota_user_deinit (user=0x1b60e80) at quota-storage.c:491 #3 0x00007f337dbcb0f1 in mail_user_unref (_user=0x1b2d070) at mail-user.c:163 #4 0x000000000040832b in client_input_data_write_local (client=0x1b2cf60, input=0x1b43f10) at commands.c:830 #5 0x0000000000408755 in client_input_data_write (client=0x1b2cf60) at commands.c:939 #6 0x0000000000408b18 in client_input_data_handle (client=0x1b2cf60) at commands.c:1033 #7 0x0000000000408b52 in client_input_data (client=0x1b2cf60) at commands.c:1042 #8 0x00007f337d8fc723 in io_loop_call_io (io=0x1b2c360) at ioloop.c:441 #9 0x00007f337d8fe6e5 in io_loop_handler_run_internal (ioloop=0x1b27740) at ioloop-epoll.c:220 #10 0x00007f337d8fc8be in io_loop_handler_run (ioloop=0x1b27740) at ioloop.c:488 #11 0x00007f337d8fc817 in io_loop_run (ioloop=0x1b27740) at ioloop.c:465 #12 0x00007f337d888d40 in master_service_run (service=0x1b275d0, callback=0x404b5c ) at master-service.c:566 #13 0x0000000000404db2 in main (argc=1, argv=0x1b27390) at main.c:122 (gdb) p _dict $1 = (struct dict **) 0x8 (gdb) bt full #0 0x00007f337d8af8ae in dict_deinit (_dict=0x8) at dict.c:87 dict = 0x10 #1 0x00007f337c88f647 in expire_mail_user_deinit (user=0x1b60e80) at expire-plugin.c:299 euser = 0x0 #2 0x00007f337cca3e7f in quota_user_deinit (user=0x1b60e80) at quota-storage.c:491 quser = 0x1b62958 quota_set = 0x1b656a0 #3 0x00007f337dbcb0f1 in mail_user_unref (_user=0x1b2d070) at mail-user.c:163 user = 0x1b60e80 __FUNCTION__ = "mail_user_unref" #4 0x000000000040832b in client_input_data_write_local (client=0x1b2cf60, input=0x1b43f10) at commands.c:830 session = 0x1b60a70 src_mail = 0x1b5c250 old_uid = 300 first_uid = 4294967295 __FUNCTION__ = "client_input_data_write_local" #5 0x0000000000408755 in client_input_data_write (client=0x1b2cf60) at commands.c:939 input = 0x1b43f10 ret = true #6 0x0000000000408b18 in client_input_data_handle (client=0x1b2cf60) at commands.c:1033 data = 0x1b556b8 "\330\001" size = 2 ret = -1 #7 0x0000000000408b52 in client_input_data (client=0x1b2cf60) at commands.c:1042 -- Michal Grzedzicki -------------- next part -------------- A non-text attachment was scrubbed... Name: expire.path Type: application/octet-stream Size: 571 bytes Desc: not available URL: From siefke_listen at web.de Mon Jul 7 13:22:45 2014 From: siefke_listen at web.de (Silvio Siefke) Date: Mon, 7 Jul 2014 15:22:45 +0200 Subject: Dovecot Auth Tries Spam Message-ID: <20140707152245.b02679ead16a9215175cb5fc@web.de> Hello, i more and more become this messages in logs: Jul 6 20:43:56 ks3374456 dovecot: auth: Error: passwd-file(jean at proxy.silviosiefke.com,213.130.118.102): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 21:35:32 ks3374456 dovecot: auth: Error: passwd-file(jennifer at proxy.silviosiefke.com,41.160.109.28): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 21:35:38 ks3374456 dovecot: auth: Error: passwd-file(jennifer at proxy.silviosiefke.com,41.160.109.28): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 21:35:44 ks3374456 dovecot: auth: Error: passwd-file(jennifer at proxy.silviosiefke.com,41.160.109.28): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 22:27:13 ks3374456 dovecot: auth: Error: passwd-file(jack at proxy.silviosiefke.com,203.113.206.105): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 22:27:20 ks3374456 dovecot: auth: Error: passwd-file(jack at proxy.silviosiefke.com,203.113.206.105): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 22:27:26 ks3374456 dovecot: auth: Error: passwd-file(jack at proxy.silviosiefke.com,203.113.206.105): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory Jul 6 22:36:49 ks3374456 dovecot: auth: Error: passwd-file(eric at proxy.silviosiefke.com,41.21.178.38): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory I understand not, because i have set dovecot so it launched only on my vpn ips. Give there a way to underbind this tries? I have installed fail2ban. Maybe im stupid, because this help not or i has set wrong entrys. service imap-login { inet_listener imap { address = 10.8.0.1 port = 12520 } inet_listener imaps { address = 10.8.0.1 port = 12550 } } [dovecot] enabled = true filter = dovecot action = iptables-multiport[name=dovecot, port="pop3,pop3s,imap,imaps,submission,465,sieve", protocol=tcp] logpath = /var/log/mail.log [dovecot-auth] enabled = true filter = dovecot action = iptables-multiport[name=dovecot-auth, port="12520,12550,submission,465,sieve", protocol=tcp] logpath = /var/log/mail.log Thanks for help & Nice day Silvio From ronleach at tesco.net Mon Jul 7 13:38:07 2014 From: ronleach at tesco.net (Ron Leach) Date: Mon, 07 Jul 2014 14:38:07 +0100 Subject: Dovecot Auth Tries Spam In-Reply-To: <20140707152245.b02679ead16a9215175cb5fc@web.de> References: <20140707152245.b02679ead16a9215175cb5fc@web.de> Message-ID: <53BAA2BF.30004@tesco.net> On 07/07/2014 14:22, Silvio Siefke wrote: > service imap-login { > port = 12520 > > inet_listener imaps { > port = 12550 > > > [dovecot] > enabled = true > filter = dovecot > action = iptables-multiport[name=dovecot, port="pop3,pop3s,imap,imaps,submission,465,sieve", protocol=tcp] > logpath = /var/log/mail.log > Silvio, one reason why fail 2 ban is not trapping those may be because: (a) in Dovecot you have defined your imap and imaps services to be ports around 125x0, whereas (b) in fail2ban you have relied on the standard imap and imaps definitions, which are 143 (I think) and 993 Might you need to enter 12520 and 12550 in your fail2ban stanza, instead of imap and imaps? Just an idea, I could be wrong; I've never set that up, myself. You mention vpn. There may also be a second problem with your network anyway, if 12520 and 12550 are vpn ports, because external traffic should not be able to appear on those, unless a vpn entry is compromised, somewhere. (That is, assuming there is a separate vpn access control system outside of Dovecot.) regards, Ron From alandaluz at gmail.com Mon Jul 7 23:10:26 2014 From: alandaluz at gmail.com (Cassidy Larson) Date: Mon, 7 Jul 2014 17:10:26 -0600 Subject: Multiple Instances with Director Message-ID: I have four front end servers with two backend servers. Each front end server has three instances for different mail hosts (individual SSL certs, etc). I'm looking at adding a fourth instance on each front end server for the director process. Currently we just return the backend server ip via SQL and use the old master username/password to proxy the inbound POP/IMAP sessions to the correct backend server. The plan is for each instance to have connect to the same list of director_servers (one from each front end server). What's the trick to separate a director instance into its own setup and having multiple instances/servers connect to that director? Currently I have on my proxy instance: director_servers = 10.128.1.42:9090 (this is the inet_listener from the director instance) service director { unix_listener login/director { mode = 0666 } fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } unix_listener director-userdb { mode = 0600 } } And I get in logs: director: Fatal: No inet_listeners defined for director service (for standalone keep director_servers empty) Do I need an inet_listener on the front end instance if I want to forward all director queries to the director_servers list? Or is there some other trick to get a proxy front end to talk to a separate director instance(s)? Thanks, Cassidy From toml at engr.orst.edu Mon Jul 7 23:36:00 2014 From: toml at engr.orst.edu (Tom Lieuallen) Date: Mon, 07 Jul 2014 16:36:00 -0700 Subject: dovecot 2.2.13 core dump (signal 11) In-Reply-To: <0C410630-E24C-4E61-85A2-E8A4C89B311C@iki.fi> References: <53A27CC7.80503@engr.orst.edu> <0C410630-E24C-4E61-85A2-E8A4C89B311C@iki.fi> Message-ID: <53BB2EE0.5050203@engr.orst.edu> On 7/3/14, 9:13 AM, Timo Sirainen wrote: > On 19.6.2014, at 9.01, Tom Lieuallen wrote: > >> namespace { >> hidden = yes >> inbox = no >> list = children >> location = maildir:/a1/dove-shared:INDEX=/a2/imap-index/dove-shared/%u >> prefix = sharedimap/ >> separator = / >> type = shared >> } > > type=shared namespaces are meant for mailboxes that users share among each others. Use type=public for this. That should fix the crash. It's also fixed in hg. Timo, I finally changed the settings yesterday. It may be too early to tell for sure, but it appears your suggestion has worked around the issue with the official 2.2.13 code release. thank you Tom Lieuallen From lazy404 at gmail.com Tue Jul 8 08:28:33 2014 From: lazy404 at gmail.com (Lazy) Date: Tue, 8 Jul 2014 10:28:33 +0200 Subject: Redis sentinel support in dict Message-ID: Redis sentinel ( http://redis.io/topics/sentinel ) is a service that monitors and manages redis master slave replication. Using sentinel you can easily create a redis ha cluster. You can connect to a sentiniel and subscribe to certain events then in case of an failover update the redis address to new master etc. I think this is better suited to be used with dict proxy. Do You think it can be implemented without changes to dovecot core ? -- Michal Grzedzicki From mlnospam at yahoo.com Tue Jul 8 08:30:35 2014 From: mlnospam at yahoo.com (ML mail) Date: Tue, 8 Jul 2014 01:30:35 -0700 Subject: doveadm quota recalc -A Message-ID: <1404808235.64141.YahooMailNeo@web162506.mail.bf1.yahoo.com> Hello, It looks like my iteration SQL query (iterate_query) does not work as when I try to run "doveadm quota recalc -A" I get the following error: $ sudo -u vmail doveadm quota recalc -A doveadm(nobody): Error: user nobody: Mail access for users with UID 65534 not permitted (see first_valid_uid in config file, uid from userdb lookup). doveadm(nobody): Error: User init failed My iterate_query is quite simple: iterate_query = SELECT username FROM mailbox So from the output I really don't understand why it looks up the user "nobody". I don't have any user "nobody" in my mailbox SQL table. Anyone has an idea? Regards ML From jost+lists at dimejo.at Tue Jul 8 09:18:03 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Tue, 08 Jul 2014 11:18:03 +0200 Subject: Dovecot Auth Tries Spam In-Reply-To: <20140707152245.b02679ead16a9215175cb5fc@web.de> References: <20140707152245.b02679ead16a9215175cb5fc@web.de> Message-ID: <53BBB74B.5030808@dimejo.at> Am 07.07.2014 15:22, schrieb Silvio Siefke: > Hello, > > i more and more become this messages in logs: > > Jul 6 20:43:56 ks3374456 dovecot: auth: Error: passwd-file(jean at proxy.silviosiefke.com,213.130.118.102): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 21:35:32 ks3374456 dovecot: auth: Error: passwd-file(jennifer at proxy.silviosiefke.com,41.160.109.28): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 21:35:38 ks3374456 dovecot: auth: Error: passwd-file(jennifer at proxy.silviosiefke.com,41.160.109.28): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 21:35:44 ks3374456 dovecot: auth: Error: passwd-file(jennifer at proxy.silviosiefke.com,41.160.109.28): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 22:27:13 ks3374456 dovecot: auth: Error: passwd-file(jack at proxy.silviosiefke.com,203.113.206.105): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 22:27:20 ks3374456 dovecot: auth: Error: passwd-file(jack at proxy.silviosiefke.com,203.113.206.105): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 22:27:26 ks3374456 dovecot: auth: Error: passwd-file(jack at proxy.silviosiefke.com,203.113.206.105): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > Jul 6 22:36:49 ks3374456 dovecot: auth: Error: passwd-file(eric at proxy.silviosiefke.com,41.21.178.38): stat(/var/vmail/auth.d/proxy.silviosiefke.com/passwd) failed: No such file or directory > > I understand not, because i have set dovecot so it launched only on my > vpn ips. Give there a way to underbind this tries? I have installed > fail2ban. Maybe im stupid, because this help not or i has set wrong > entrys. > > > > service imap-login { > inet_listener imap { > address = 10.8.0.1 > port = 12520 > } > > inet_listener imaps { > address = 10.8.0.1 > port = 12550 > } > } > > > > [dovecot] > enabled = true > filter = dovecot > action = iptables-multiport[name=dovecot, port="pop3,pop3s,imap,imaps,submission,465,sieve", protocol=tcp] > logpath = /var/log/mail.log > > [dovecot-auth] > enabled = true > filter = dovecot > action = iptables-multiport[name=dovecot-auth, port="12520,12550,submission,465,sieve", protocol=tcp] > logpath = /var/log/mail.log > > > Thanks for help & Nice day > Silvio > Seems as if you have configured Dovecot to use a file that doesn't exist. This has nothing to do with fail2ban. Let's see the output of "doveconf -n" to start with. -- Alex JOST From mitchelldmcmillan at gmail.com Tue Jul 8 10:58:06 2014 From: mitchelldmcmillan at gmail.com (Mitchell McMillan) Date: Tue, 8 Jul 2014 20:58:06 +1000 Subject: Dovecot not changing SSL key and certificate as in config file Message-ID: I am trying to use my (decrypted) SSL key and certificate in Dovecot. I have changed /etc/dovecot/conf.d/10-ssl.conf like so: ssl_cert = Hi, I'm using Dovecot 2.0.9, and was trying to set up a dictionary process to use an sqlite database for quota management. The wiki page has examples for MySQL and PostgreSQL: http://wiki2.dovecot.org/Quota/Dict For sqlite, a trigger needs to be created to get it to work. But I was not sufficiently skilled in sqlite to adapt the PostgreSQL trigger (given on the above URL) for use. Nor did Googling find any example of anyone else who had done it. Does anyone here have an example, or the ability? (Through Googling I found an example trigger for using sqlite with expiries - but I was looking at quotas). Best wishes, David -- UpdraftPlus - best WordPress backups - http://updraftplus.com WordShell - WordPress fast from the CLI - http://wordshell.net From jost+lists at dimejo.at Tue Jul 8 11:15:35 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Tue, 08 Jul 2014 13:15:35 +0200 Subject: Dovecot not changing SSL key and certificate as in config file In-Reply-To: References: Message-ID: <53BBD2D7.70809@dimejo.at> Am 08.07.2014 12:58, schrieb Mitchell McMillan: > I am trying to use my (decrypted) SSL key and certificate in Dovecot. I > have changed /etc/dovecot/conf.d/10-ssl.conf like so: > ssl_cert = ssl_key = > However, after running service dovecot restart, dovecot -n still says that > the files /etc/dovecot/dovecot.pem and /etc/dovecot/private/dovecot.pem are > being used. > I am using dovecot 2.2.9, any help would be greatly appreciated. > Maybe the values got overwritten by another file. grep -ER 'ssl_(key|cert)' /etc/dovecot/ -- Alex JOST From h.reindl at thelounge.net Tue Jul 8 11:18:54 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 08 Jul 2014 13:18:54 +0200 Subject: Dovecot not changing SSL key and certificate as in config file In-Reply-To: References: Message-ID: <53BBD39E.5010301@thelounge.net> Am 08.07.2014 12:58, schrieb Mitchell McMillan: > I am trying to use my (decrypted) SSL key and certificate in Dovecot. I > have changed /etc/dovecot/conf.d/10-ssl.conf like so: > ssl_cert = ssl_key = > However, after running service dovecot restart, dovecot -n still says that > the files /etc/dovecot/dovecot.pem and /etc/dovecot/private/dovecot.pem are > being used. > I am using dovecot 2.2.9, any help would be greatly appreciated and that's why i use *one* dovecot.conf or if i work with snippets place them far away from default locations another config snippet coming later overwrites your value most likely -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From martin.vegter at aol.com Tue Jul 8 11:52:26 2014 From: martin.vegter at aol.com (Martin Vegter) Date: Tue, 08 Jul 2014 13:52:26 +0200 Subject: Dovecot ignores existing mailboxes and creates its own Message-ID: <53BBDB7A.9080203@aol.com> Hello, I have Postfix with Maildir format. User's emails are being delivered into $HOME/mail/inbox Apart from ~/mail/inbox, there are the usual folders: $HOME/mail/archive $HOME/mail/drafts $HOME/mail/inbox $HOME/mail/trash Now I have installed dovecot, and set mail_location = maildir:~/mail:LAYOUT=fs additionally, I have defined mailboxes as follows: namespace inbox { mailbox drafts { special_use = \Drafts } mailbox sent { special_use = \Sent } mailbox trash { special_use = \Trash } } The problem I am having is following: 1) dovecot ignores the folders (drafts, sent, trash) and creates its own folders begining with capiotal letter: Drafts Sent Trash 2) dovecot ignores ~/mail/inbox and instead creates ~/mail/cur ~/mail/new ~/mail/tmp can somebody please advise how to tell dovecot, to use my existing folder structure, ie: ~/mail/inbox/{cur,new,tmp} ~/mail/drafts/{cur,new,tmp} ~/mail/sent/{cur,new,tmp} ~/mail/trash/{cur,new,tmp} any advice would be much appreciated thanks, Martin From THerrmann at ADwin.de Tue Jul 8 15:01:30 2014 From: THerrmann at ADwin.de (Thomas Herrmann) Date: Tue, 08 Jul 2014 17:01:30 +0200 Subject: Flags in public folders disappear when more than 25 flags are used In-Reply-To: <53B41677.6080300@ADwin.de> References: <53B41677.6080300@ADwin.de> Message-ID: <53BC07CA.5060106@ADwin.de> On 07/02/2014 04:25 PM, Thomas Herrmann wrote: > root at mailsrv2:~# dovecot --version > 2.1.7 Since I did not receive any replies to my previous question, I did the following: - Upgraded to 2.2.13 (still debian packages) - learned how to use doveadm to debug problems Now I am a little closer to the problem. I discovered that the dovecot-keywords file is out of sync with what doveadm reports. Is that a problem? Any idea how that could happen and how to fix that? Strangely, doveadm reports less than 25 keywords. root at mailsrv2:/home/vmail/public/.Info# cat dovecot-keywords 0 NonJunk [...] 20 zu_erledigen_ec 21 erledigt_bika 22 zu_erledigen_bik 23 erledigt_bik 24 sp_wichtig 25 erledigt_bl -- Extension 3 -- name ........ = cache hdr_size .... = 0 reset_id .... = 1333086435 record_offset = 16 record_size . = 4 record_align = 4 -- Keywords -- 0 = NonJunk [...] 20 = sp_wichtig 21 = zu_erledigen_bik 22 = erledigt_bl -- CACHE: ./dovecot.index.cache Regards Thomas Herrmann -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4246 bytes Desc: S/MIME Cryptographic Signature URL: From micah at riseup.net Tue Jul 8 18:50:14 2014 From: micah at riseup.net (Micah Anderson) Date: Tue, 08 Jul 2014 14:50:14 -0400 Subject: Limit confusion Message-ID: <87d2df65y1.fsf@muck.riseup.net> Hi, On one of my dovecot servers, i've got a limit problem... and I'm a little confused about which knobs I should adjust to solve it. I've been getting both of these: Error: net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailableess This one caused me to go read that wiki page, but none of those seem to apply to me: . i'm running 2.2.9 . i dont have service imap { client_limit }, although I do have service auth ( client_limit = 1024 } . my dovecot/auth process shows: dovecot/auth [91 wait, 0 passdb, 0 userdb] . it doesn't appear the master process is using very much cpu (in fact the system is mostly low load in general) . I have service_count = 0 set for imap-login for the 'high performance mode' dovecot: master: Warning: service(imap): process_limit (2560) reached, client connections are being dropped The second is because I have process_limit of 2560 for the imap service... I can raise that to 4096, but I suspect there are other limits I need to juggle? Thanks a lot for any suggestions! I have ulimit -n 2048 set for the dovecot processes (in /etc/default/dovecot) and the following is my dovecot -n: # 2.2.9: /etc/dovecot/dovecot.conf auth_verbose = yes default_process_limit = 256 default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf quota = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 listen = * login_greeting = howdy, ready. mail_location = mdbox:~/mdbox:INDEX=/srv/dovecot_indexes/%d/%1n/%n mail_plugins = expire quota zlib maildir_very_dirty_syncs = yes namespace { inbox = yes location = prefix = separator = . } namespace { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_allow_append_to_spam = yes antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/local/bin/train_spam antispam_pipe_program_args = -d;10.0.1.109 antispam_pipe_program_notspam_arg = ham antispam_pipe_program_spam_arg = spam antispam_pipe_tmpdir = /var/tmp antispam_signature = X-Spam-Flag antispam_signature_missing = error antispam_spam_pattern_ignorecase = SPAM antispam_trash_pattern = trash;Trash;Deleted * expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:Your mail quota::proxy::quota quota_rule = *:bytes=100663296 quota_rule2 = Trash:bytes=+20%% quota_rule3 = Spam:bytes=+10%% quota_rule4 = INBOX.Trash:bytes=+20%% quota_rule5 = INBOX.Spam:bytes=+10%% sieve = ~/.dovecot.sieve sieve_after = /var/lib/dovecot/sieve/after.sieve sieve_before = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } protocols = " imap pop3" service anvil { unix_listener anvil { group = dovecot mode = 0660 user = root } } service auth { client_limit = 1024 unix_listener auth-userdb { group = mail mode = 0600 user = mail } } service dict { unix_listener dict { group = mail mode = 0600 user = mail } } service imap-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/sbin/postlogin_imap } service imap { executable = imap imap-postlogin process_limit = 4096 } service pop3-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service pop3-postlogin { executable = script-login /usr/local/sbin/postlogin_pop } service pop3 { executable = pop3 pop3-postlogin } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl_cert = Hi! I've managed to setup a virtual mailbox that shows all unread or flagged mail from a selection of IMAP folders. This works great with Roundcube, which I use as webmail client. However, using K9 mail on my android phone, a mail that is opened seems to be immediately marked as read, and any flagging I do doesn't take. Presumably this is because it can't be reached any longer in the virtual folder. I tried adding the recent flag to the virtual search line, but that doesn't make any difference. I haven't been able to locate any information about anyone else experiencing this problem, so I was hoping that someone here could help. I realise that this is not exactly a "dovecot problem", but perhaps someone here has found a solution that they are willing to share. The search line in dovecot-virtual is currently "OR RECENT (OR UNSEEN FLAGGED). Regards From lukashaase at gmx.at Tue Jul 8 21:03:23 2014 From: lukashaase at gmx.at (Lukas Haase) Date: Tue, 08 Jul 2014 14:03:23 -0700 Subject: BUG: Authentication client sent unknown handshake command In-Reply-To: References: Message-ID: May I gently "push" this? The string "BUG: Authentication client sent unknown handshake command" comes from dovecot (presumably it's in the source code) so I think it shouldn't be too mysterious what's happening here. Thank you, Luke On 2014-07-03 19:10, Lukas Haase wrote: > Hi, > > Some time ago my dovecot started to become BUGgy: Evertime I restart the > system, dovecot is started but I cannot login. I see the following > information in the logs: > > Jul 4 04:04:36 mail dovecot: auth: > passwd-file(user,127.11.91.218,): no passwd file: > /etc/dovecot/imap.passwd > Jul 4 04:04:36 mail dovecot: auth: Error: BUG: Authentication client > sent unknown handshake command: > REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa > Jul 4 04:04:36 mail dovecot: imap: Error: Authentication server didn't > send valid SPID as expected: MECH#011PLAIN#011plaintext > Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from auth > server, aborting (client-pid=20438 client-id=1) > Jul 4 04:04:36 mail dovecot: imap-login: Internal login failure > (pid=20438 id=1) (internal failure, 1 succesful auths): user=, > method=PLAIN, rip=127.11.91.218, lip=73.82.101.172, mpid=20439, TLS, > session= > > It does not help to restart the client. But when I then restart the server > service dovecot restart > it works again. > > But this is very dangerous because the server might reboot and I might > not immideately have the chance to restart dovecot manually. > > What's going on here? > > mail:/# uname -a > Linux mail 2.6.32-openvz-042stab090.2-amd64 #1 SMP Sat Jun 21 00:22:42 > MSK 2014 i686 GNU/Linux > mail:/# dovecot --version > 2.1.7 > > Thanks, > Luke > From marc at perkel.com Wed Jul 9 15:23:06 2014 From: marc at perkel.com (Marc Perkel) Date: Wed, 09 Jul 2014 08:23:06 -0700 Subject: Multiple email clients not in sync Message-ID: <53BD5E5A.2090804@perkel.com> Hello everyone, I'm not sure if this is an issue with dovecot or my various email clients, or my settings. I'm running 2.2.13 and I have Thunderbird on my desktop and K at mail on my android phone. In theory if I delete email on one it should delete it on the other. It does delete it on the server - but the other client isn't always "aware" of it. Same thing sometimes with read messages. I read on one device but the other didn't know it's read unless I shut down and restart the app. Not knowing the details of how this all works I'm assuming there is some form of notification that goes on in the background so as to let other clients know what other clients do so they can sync up. And that where my setup isn't working consistently. Maybe my expectations are just too high? Maybe I don't have things set up correctly? What am I missing? Thanks in advance. From mtrainer at westnet.com.au Wed Jul 9 16:24:13 2014 From: mtrainer at westnet.com.au (Murray Trainer) Date: Thu, 10 Jul 2014 00:24:13 +0800 Subject: Dovecot ldap quotas in MB Message-ID: <53BD6CAD.1010506@westnet.com.au> Hi All, I have the Dovecot quota value coming from LDAP using the line below but my values are stored in MB, not bytes. What can I put in the line to set quotas in MB? user_attrs = homeDirectory=home,mailUID=uid,mailGID=gid,mailQuota=quota_rule=*:bytes=%$ Thanks Murray From h.reindl at thelounge.net Wed Jul 9 16:49:03 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 09 Jul 2014 18:49:03 +0200 Subject: Multiple email clients not in sync In-Reply-To: <53BD5E5A.2090804@perkel.com> References: <53BD5E5A.2090804@perkel.com> Message-ID: <53BD727F.6090705@thelounge.net> Am 09.07.2014 17:23, schrieb Marc Perkel: > Hello everyone, > > I'm not sure if this is an issue with dovecot or my various email clients, or my settings. > > I'm running 2.2.13 and I have Thunderbird on my desktop and K at mail on my android phone. In theory if I delete email > on one it should delete it on the other. It does delete it on the server - but the other client isn't always > "aware" of it. Same thing sometimes with read messages. I read on one device but the other didn't know it's read > unless I shut down and restart the app. > > Not knowing the details of how this all works I'm assuming there is some form of notification that goes on in the > background so as to let other clients know what other clients do so they can sync up. And that where my setup isn't > working consistently. > > Maybe my expectations are just too high? Maybe I don't have things set up correctly? > > What am I missing? Thanks in advance * do you have imap idle enabled on the server * do you have imap idle enabled on all clients * if both is yes - in case of subfolders: make sure enough connections are allowed * thunderbird AFAIK needs some tweek to watch all folders for notifications too lazy to dig in my configs however "imap idle" and your software on each end should be a good start for Google -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From jeff at jrice.me Wed Jul 9 18:20:03 2014 From: jeff at jrice.me (Jeff Rice) Date: Wed, 09 Jul 2014 14:20:03 -0400 Subject: Differences in "Delivered-To" header between deliver and LMTP Message-ID: <53BD87D3.9070108@jrice.me> Hi, I'm transitioning my server over from using the deliver LDA and LMTP. Suddenly a bunch of sieve filters stopped working, and I noticed the contents of the Delivered-To header are different. Using Dovecot's deliver LDA, the contents are a bare email address (foo at bar.com). Using Dovecot LMTP, they are in brackets (). Is there a reason why this isn't consistent between the two delivery agents? It seems like it ought to be. Jeff From marc at perkel.com Wed Jul 9 18:27:33 2014 From: marc at perkel.com (Marc Perkel) Date: Wed, 09 Jul 2014 11:27:33 -0700 Subject: Multiple email clients not in sync In-Reply-To: <53BD727F.6090705@thelounge.net> References: <53BD5E5A.2090804@perkel.com> <53BD727F.6090705@thelounge.net> Message-ID: <53BD8995.7060009@perkel.com> On 7/9/2014 9:49 AM, Reindl Harald wrote: > Am 09.07.2014 17:23, schrieb Marc Perkel: >> Hello everyone, >> >> I'm not sure if this is an issue with dovecot or my various email clients, or my settings. >> >> I'm running 2.2.13 and I have Thunderbird on my desktop and K at mail on my android phone. In theory if I delete email >> on one it should delete it on the other. It does delete it on the server - but the other client isn't always >> "aware" of it. Same thing sometimes with read messages. I read on one device but the other didn't know it's read >> unless I shut down and restart the app. >> >> Not knowing the details of how this all works I'm assuming there is some form of notification that goes on in the >> background so as to let other clients know what other clients do so they can sync up. And that where my setup isn't >> working consistently. >> >> Maybe my expectations are just too high? Maybe I don't have things set up correctly? >> >> What am I missing? Thanks in advance > * do you have imap idle enabled on the server > * do you have imap idle enabled on all clients > * if both is yes - in case of subfolders: make sure enough connections are allowed > * thunderbird AFAIK needs some tweek to watch all folders for notifications > too lazy to dig in my configs > > however "imap idle" and your software on each end should be a good start for Google Thanks for your help. How do I turn on idle on the server? From h.reindl at thelounge.net Wed Jul 9 18:42:03 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 09 Jul 2014 20:42:03 +0200 Subject: Differences in "Delivered-To" header between deliver and LMTP In-Reply-To: <53BD87D3.9070108@jrice.me> References: <53BD87D3.9070108@jrice.me> Message-ID: <53BD8CFB.2000206@thelounge.net> Am 09.07.2014 20:20, schrieb Jeff Rice: > I'm transitioning my server over from using the deliver LDA and LMTP. Suddenly a bunch of sieve filters stopped > working, and I noticed the contents of the Delivered-To header are different. > > Using Dovecot's deliver LDA, the contents are a bare email address (foo at bar.com). Using Dovecot LMTP, they are in > brackets (). Is there a reason why this isn't consistent between the two delivery agents? It seems > like it ought to be LMTP is practically SMTP http://www.faqs.org/rfcs/rfc2822.html A mailbox receives mail. It is a conceptual entity which does not necessarily pertain to file storage. For example, some sites may choose to print mail on a printer and deliver the output to the addressee's desk. Normally, a mailbox is comprised of two parts: (1) an optional display name that indicates the name of the recipient (which could be a person or a system) that could be displayed to the user of a mail application, and (2) an addr-spec address enclosed in angle brackets ("<" and ">"). There is also an alternate simple form of a mailbox where the addr-spec address appears alone, without the recipient's name or the angle brackets. The Internet addr-spec address is described in section 3.4.1. Note: Some legacy implementations used the simple form where the addr-spec appears without the angle brackets, but included the name of the recipient in parentheses as a comment following the addr-spec. Since the meaning of the information in a comment is unspecified, implementations SHOULD use the full name-addr form of the mailbox, instead of the legacy form, to specify the display name associated with a mailbox. Also, because some legacy implementations interpret the comment, comments generally SHOULD NOT be used in address fields to avoid confusing such implementations. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From marc at perkel.com Wed Jul 9 18:44:39 2014 From: marc at perkel.com (Marc Perkel) Date: Wed, 09 Jul 2014 11:44:39 -0700 Subject: Multiple email clients not in sync In-Reply-To: <53BD727F.6090705@thelounge.net> References: <53BD5E5A.2090804@perkel.com> <53BD727F.6090705@thelounge.net> Message-ID: <53BD8D97.2010803@perkel.com> On 7/9/2014 9:49 AM, Reindl Harald wrote: > Am 09.07.2014 17:23, schrieb Marc Perkel: >> Hello everyone, >> >> I'm not sure if this is an issue with dovecot or my various email clients, or my settings. >> >> I'm running 2.2.13 and I have Thunderbird on my desktop and K at mail on my android phone. In theory if I delete email >> on one it should delete it on the other. It does delete it on the server - but the other client isn't always >> "aware" of it. Same thing sometimes with read messages. I read on one device but the other didn't know it's read >> unless I shut down and restart the app. >> >> Not knowing the details of how this all works I'm assuming there is some form of notification that goes on in the >> background so as to let other clients know what other clients do so they can sync up. And that where my setup isn't >> working consistently. >> >> Maybe my expectations are just too high? Maybe I don't have things set up correctly? >> >> What am I missing? Thanks in advance > * do you have imap idle enabled on the server > * do you have imap idle enabled on all clients > * if both is yes - in case of subfolders: make sure enough connections are allowed > * thunderbird AFAIK needs some tweek to watch all folders for notifications > too lazy to dig in my configs > > however "imap idle" and your software on each end should be a good start for Google > Yes - server and all email clients do IDLE. And it does seem to work sometime. My real question is if it can work all the time or are my expectations too high? From h.reindl at thelounge.net Wed Jul 9 18:54:56 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 09 Jul 2014 20:54:56 +0200 Subject: Multiple email clients not in sync In-Reply-To: <53BD8D97.2010803@perkel.com> References: <53BD5E5A.2090804@perkel.com> <53BD727F.6090705@thelounge.net> <53BD8D97.2010803@perkel.com> Message-ID: <53BD9000.3040601@thelounge.net> Am 09.07.2014 20:44, schrieb Marc Perkel: > On 7/9/2014 9:49 AM, Reindl Harald wrote: >> Am 09.07.2014 17:23, schrieb Marc Perkel: >>> Hello everyone, >>> >>> I'm not sure if this is an issue with dovecot or my various email clients, or my settings. >>> >>> I'm running 2.2.13 and I have Thunderbird on my desktop and K at mail on my android phone. In theory if I delete email >>> on one it should delete it on the other. It does delete it on the server - but the other client isn't always >>> "aware" of it. Same thing sometimes with read messages. I read on one device but the other didn't know it's read >>> unless I shut down and restart the app. >>> >>> Not knowing the details of how this all works I'm assuming there is some form of notification that goes on in the >>> background so as to let other clients know what other clients do so they can sync up. And that where my setup isn't >>> working consistently. >>> >>> Maybe my expectations are just too high? Maybe I don't have things set up correctly? >>> >>> What am I missing? Thanks in advance >> * do you have imap idle enabled on the server >> * do you have imap idle enabled on all clients >> * if both is yes - in case of subfolders: make sure enough connections are allowed >> * thunderbird AFAIK needs some tweek to watch all folders for notifications >> too lazy to dig in my configs >> >> however "imap idle" and your software on each end should be a good start for Google > > Yes - server and all email clients do IDLE. And it does seem to work sometime. My real question is if it can work > all the time or are my expectations too high? there may be devices between clients and server which are closing long living connections and especially in case of mobile devices the client is in charge to keep connections alive if the device moves to a different cell, switch betwenen WLAN/3G and so on on the server side play around with tcp keep alive could help add or cahnge the following values in "/etc/sysctl.conf" followed by "sysctl -p" net.ipv4.tcp_keepalive_time = 90 net.ipv4.tcp_keepalive_intvl = 5 net.ipv4.tcp_keepalive_probes = 2 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From kmansoft at gmail.com Wed Jul 9 20:12:15 2014 From: kmansoft at gmail.com (Kostya Vasilyev) Date: Thu, 10 Jul 2014 00:12:15 +0400 Subject: HIGHESTMODSEQ tracking Message-ID: Hello, I'd like to follow up on someone else's old thread: http://dovecot.org/list/dovecot/2012-April/082624.html I understand that Dovecot (that 2012 discussion was about version 2.0.18) can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was never enabled for a mailbox. I'd like to get a clarification on how to enable proper persistent modseq tracking. Per RFC 4551, "A client supporting CONDSTORE.... indicates its willingness to receive mod-sequence updates... by issuing:" SELECT mailbox (CONDSTORE) STATUS (... HIGHESTMODSEQ ...) ... others ... It seems that Dovecot 2.1.7 (Debian 7.5) enables persistent modseq tracking after one of the above two commands (and maybe others). So far so good. So my questions are: 1 - Is this (enabling persistent modseq) also the case for all Dovecot versions prior to 2.1.7 that advertise CONDSTORE? There must be people running older versions out there, older than 2.1.7. If not, how can I branch my logic to not use HIGHESTMODSEQ, given that Dovecot doesn't appear to return any version info via its greeting or via the ID command? 2 - Is persistent modseq tracking (assuming it's been enabled) available for all types of backend mailbox formats that Dovecot might be using? To be more specific, can it ever be the case that Dovecot appears to enable modseq tracking, returning nice looking HIGHESTMODSEQ values from SELECT / STATUS, but the actual values get reset or not get updated because they're not properly persistent? I'm excluding changes to UIDVALIDITY here, obviously when that changes, the entire mailbox state must be assumed to have changed completely. 3 - I guess the change to return NOMOSEQ instead of "1" for mailboxes with modseq tracking disabled, as mentioned in that discussion from 2012, never happened? At least on the 2.1 branch? Thanks, -- K From slusarz at curecanti.org Wed Jul 9 21:37:45 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Wed, 09 Jul 2014 15:37:45 -0600 Subject: HIGHESTMODSEQ tracking In-Reply-To: Message-ID: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> Quoting Kostya Vasilyev : > Hello, > > I'd like to follow up on someone else's old thread: > > http://dovecot.org/list/dovecot/2012-April/082624.html > > I understand that Dovecot (that 2012 discussion was about version 2.0.18) > can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was > never enabled for a mailbox. This behavior is largely irrelevant ... a client should ignore any HIGHESTMODSEQ data that is sent if it (the client) hasn't sent a CONDSTORE enabling command. > I'd like to get a clarification on how to enable proper persistent modseq > tracking. > > Per RFC 4551, "A client supporting CONDSTORE.... indicates its willingness > to receive mod-sequence updates... by issuing:" > > SELECT mailbox (CONDSTORE) > STATUS (... HIGHESTMODSEQ ...) > ... others ... 4551 is deprecated --> it is now RFC 7162. Also note there's actually 6 different categories of CONDSTORE-enabling commands. SELECT/EXAMINE with CONDSTORE is just one of the categories. These days, you *really* should be using QRESYNC instead though. > It seems that Dovecot 2.1.7 (Debian 7.5) enables persistent modseq tracking > after one of the above two commands (and maybe others). So far so good. Incorrect. Dovecot has supported CONDSTORE/QRESYNC since 1.2.0. And as mentioned above, there are 6 different ways of enabling CONDSTORE. (Enabling QRESYNC is done 1 way ... the "ENABLE QRESYNC" command). > So my questions are: > > 1 - Is this (enabling persistent modseq) also the case for all Dovecot > versions prior to 2.1.7 that advertise CONDSTORE? > > There must be people running older versions out there, older than 2.1.7. > > If not, how can I branch my logic to not use HIGHESTMODSEQ, given that > Dovecot doesn't appear to return any version info via its greeting or via > the ID command? As noted above, this is irrelevant. As a client author, you should ALWAYS ignore HIGHESTMODSEQ if you haven't enabled CONDSTORE/QRESYNC . > 3 - I guess the change to return NOMOSEQ instead of "1" for mailboxes with > modseq tracking disabled, as mentioned in that discussion from 2012, never > happened? At least on the 2.1 branch? NOMODSEQ is only relevant *if* you have enabled CONDSTORE. Returning NOMODSEQ on mailboxes that don't support persistent mod-sequences has worked since 1.2.0, at least as far as I know. michael From axel.luttgens at skynet.be Wed Jul 9 22:01:35 2014 From: axel.luttgens at skynet.be (Axel Luttgens) Date: Thu, 10 Jul 2014 00:01:35 +0200 Subject: Trigger for using an sqlite dictionary for quota In-Reply-To: <53BBD14A.1050005@wordshell.net> References: <53BBD14A.1050005@wordshell.net> Message-ID: Le 8 juil. 2014 ? 13:08, David Anderson a ?crit : > Hi, > > I'm using Dovecot 2.0.9, and was trying to set up a dictionary process to use an sqlite database for quota management. > > The wiki page has examples for MySQL and PostgreSQL: http://wiki2.dovecot.org/Quota/Dict > > For sqlite, a trigger needs to be created to get it to work. But I was not sufficiently skilled in sqlite to adapt the PostgreSQL trigger (given on the above URL) for use. Nor did Googling find any example of anyone else who had done it. Does anyone here have an example, or the ability? Hello David, You could have a look at: http://dovecot.org/pipermail/dovecot/2013-July/091421.html HTH, Axel From kmansoft at gmail.com Wed Jul 9 22:33:26 2014 From: kmansoft at gmail.com (Kostya Vasilyev) Date: Thu, 10 Jul 2014 02:33:26 +0400 Subject: Fwd: HIGHESTMODSEQ tracking In-Reply-To: References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> Message-ID: Michael, 2014-07-10 1:37 GMT+04:00 Michael M Slusarz : Quoting Kostya Vasilyev : > > Hello, >> >> I'd like to follow up on someone else's old thread: >> >> http://dovecot.org/list/dovecot/2012-April/082624.html >> >> I understand that Dovecot (that 2012 discussion was about version 2.0.18) >> can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was >> never enabled for a mailbox. >> > > This behavior is largely irrelevant ... a client should ignore any > HIGHESTMODSEQ data that is sent if it (the client) hasn't sent a CONDSTORE > enabling command. True, but I was just pointing out a quirk that existed in a older version, to ask for a clarification. > > > I'd like to get a clarification on how to enable proper persistent modseq >> tracking. >> >> Per RFC 4551, "A client supporting CONDSTORE.... indicates its willingness >> to receive mod-sequence updates... by issuing:" >> >> SELECT mailbox (CONDSTORE) >> STATUS (... HIGHESTMODSEQ ...) >> ... others ... >> > > 4551 is deprecated --> it is now RFC 7162. > Thanks, didn't notice that 4551 was "obsoleted". > > Also note there's actually 6 different categories of CONDSTORE-enabling > commands. SELECT/EXAMINE with CONDSTORE is just one of the categories. > There are five listed in RFC 4551, yes, there are six in 7162, but my question was about two specific ones out of those five / six. > > These days, you *really* should be using QRESYNC instead though. There are some mail servers that support CONDSTORE but not QRESYNC. The old chicken and egg IMAP problem :) > > > It seems that Dovecot 2.1.7 (Debian 7.5) enables persistent modseq >> tracking >> after one of the above two commands (and maybe others). So far so good. >> > > Incorrect. Dovecot has supported CONDSTORE/QRESYNC since 1.2.0. Incorrect? I wrote: "it seems that Dovecot 2.1.7 enables persistent modseq tracking...". Are you implying that Dovecot 2.1.7 doesn't enable persistent modseq tracking in this case? I never claimed that earlier versions of Dovecot didn't advertise CONDSTORE or didn't implement it properly, etc. Perhaps I should have written "...after *any* of the two commands... (and maybe others)" -- meaning it does after either of those two commands, and the other ones I don't care about and so didn't test. > And as mentioned above, there are 6 different ways of enabling CONDSTORE. > (Enabling QRESYNC is done 1 way ... the "ENABLE QRESYNC" command). Yes, agreed, noted. I'm asking about two out of those five / six. And not just about what the RFC says, but about how real, out in the field, installed on mail servers that people use, possibly quite old, versions of Dovecot behave. So let me try again: Is sending SELECT ... (CONDSTORE) or STATUS (... HIGHESTMODSEQ ...) enough to enable reliable persistent modseq tracking for all versions of Dovecot which advertise CONDSTORE in their capabilities? Not what the currently relevant RFC says, but how Dovecot versions with CONDSTORE in their caps behave. This is the one thing I'd really like to know. > > > So my questions are: >> >> 1 - Is this (enabling persistent modseq) also the case for all Dovecot >> versions prior to 2.1.7 that advertise CONDSTORE? >> >> There must be people running older versions out there, older than 2.1.7. >> >> If not, how can I branch my logic to not use HIGHESTMODSEQ, given that >> Dovecot doesn't appear to return any version info via its greeting or via >> the ID command? >> > > As noted above, this is irrelevant. As a client author, you should ALWAYS > ignore HIGHESTMODSEQ if you haven't enabled CONDSTORE/QRESYNC . All caps look nice in RFCs, but the real world has more variety :) > > > 3 - I guess the change to return NOMOSEQ instead of "1" for mailboxes with >> modseq tracking disabled, as mentioned in that discussion from 2012, never >> happened? At least on the 2.1 branch? >> > > NOMODSEQ is only relevant *if* you have enabled CONDSTORE. Agreed. However: > Returning NOMODSEQ on mailboxes that don't support persistent > mod-sequences has worked since 1.2.0, at least as far as I know. The linked message from 2012, discussing 2.0.18, says: "2) If a mailbox doesn't have modseqs enabled, return NOMODSEQ. This isn't ideal, but seems like the only possibility" And based on my tests, Dovecot 2.1.7 returns "HIGHESTMODSEQ 1" for mailboxes where modseq tracking has not been enabled. You're largely right about the value only being relevant if the client enabled CONDSTORE, and I don't care too much about this quirk, just wanted to to get a clarification on this as well, if possible. Thanks, -- K From fumiyas at osstech.jp Wed Jul 9 23:48:05 2014 From: fumiyas at osstech.jp (SATOH Fumiyasu) Date: Thu, 10 Jul 2014 08:48:05 +0900 Subject: Dovecot ldap quotas in MB In-Reply-To: <53BD6CAD.1010506@westnet.com.au> References: <53BD6CAD.1010506@westnet.com.au> Message-ID: <87bnsyaybu.wl%fumiyas@osstech.jp> At Thu, 10 Jul 2014 00:24:13 +0800, Murray Trainer wrote: > I have the Dovecot quota value coming from LDAP using the line below but my values are stored in MB, not bytes. What can I put in the line to set quotas in MB? > > user_attrs = homeDirectory=home,mailUID=uid,mailGID=gid,mailQuota=quota_rule=*:bytes=%$ Append 'M' to the value of quota_rule in user_attrs. user_attrs = homeDirectory=home,mailUID=uid,mailGID=gid,mailQuota=quota_rule=*:bytes=%$M -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA From slusarz at curecanti.org Thu Jul 10 00:05:37 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Wed, 09 Jul 2014 18:05:37 -0600 Subject: HIGHESTMODSEQ tracking In-Reply-To: References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> Message-ID: <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> Quoting Kostya Vasilyev : > 2014-07-10 1:37 GMT+04:00 Michael M Slusarz : > > Quoting Kostya Vasilyev : >> >> These days, you *really* should be using QRESYNC instead though. > > There are some mail servers that support CONDSTORE but not QRESYNC. The old > chicken and egg IMAP problem :) This is the wrong way to look at it though. You should implement QRESYNC initially, because it will force you to implement CONDSTORE also. It's going to be 10x harder to implement CONDSTORE and then add QRESYNC functionality on top of it later. Do it right the first time. Both Dovecot and Cyrus support both CONDSTORE and QRESYNC, and combined that is more than 50% market share, so that should be incentive enough. Gmail only supports CONDSTORE, but it's the outlier. > So let me try again: > > Is sending SELECT ... (CONDSTORE) or STATUS (... HIGHESTMODSEQ ...) enough > to enable reliable persistent modseq tracking for all versions of Dovecot > which advertise CONDSTORE in their capabilities? Maybe. You can't tell until you actually see whether the EXAMINE/SELECT returns HIGHESTMODSEQ or NOMODSEQ. >> 3 - I guess the change to return NOMOSEQ instead of "1" for mailboxes with >>> modseq tracking disabled, as mentioned in that discussion from 2012, never >>> happened? At least on the 2.1 branch? >>> >> >> NOMODSEQ is only relevant *if* you have enabled CONDSTORE. > > > Agreed. However: > > >> Returning NOMODSEQ on mailboxes that don't support persistent >> mod-sequences has worked since 1.2.0, at least as far as I know. > > > The linked message from 2012, discussing 2.0.18, says: > > "2) If a mailbox doesn't have modseqs enabled, return NOMODSEQ. This isn't > ideal, but seems like the only possibility" AFAICT, the mailing list message you are referring to is talking about what Dovecot returns **when CONDSTORE is not enabled**. As I mentioned before, this should be irrelevant to your client since you shouldn't be using HIGHESTMODSEQ if you haven't enabled CONDSTORE. Older versions of Dovecot happen to send CONDSTORE info even if it's not active (which is perfectly valid IMAP behavior). *This* was the issue referred to in that message ... some clients didn't enable CONDSTORE but were using HIGHESTMODSEQ if it existed to use it as a "Uniqu eID" (combined with the current UIDVALIDITY) of the mailbox for polling purposes. It was these clients that were seeing broken behavior since this "Unique ID" never changed - since UIDVALIDITY normally won't ever change - since HIGHESTMODSEQ would always be 1. These clients should have never been doing that in the first place, but whatever. Once you issue a CONDSTORE-enabling command, this is no longer an issue. So it's not something a client ever has to workaround as long as they are following the RFC. michael From kmansoft at gmail.com Thu Jul 10 09:44:38 2014 From: kmansoft at gmail.com (Kostya Vasilyev) Date: Thu, 10 Jul 2014 13:44:38 +0400 Subject: HIGHESTMODSEQ tracking In-Reply-To: <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> Message-ID: 2014-07-10 4:05 GMT+04:00 Michael M Slusarz : > Quoting Kostya Vasilyev : > > 2014-07-10 1:37 GMT+04:00 Michael M Slusarz : >> >> Quoting Kostya Vasilyev : >> >>> >>> These days, you *really* should be using QRESYNC instead though. >>> >> >> There are some mail servers that support CONDSTORE but not QRESYNC. The >> old >> chicken and egg IMAP problem :) >> > > [ snip ] > Both Dovecot and Cyrus support both CONDSTORE and QRESYNC, and combined > that is more than 50% market share, so that should be incentive enough. > Gmail only supports CONDSTORE, but it's the outlier. Gmail still does have a few users, though. A few dozen at least, maybe more :) And it has a big advantage, from my point of view, over Cyrus / Dovecot -- there is but one server version that's consistent for all accounts. Yes, they do some things wrong (like not sending message flags changes over IDLE connections), but I can test something in my personal account, get feedback from 3-5-10 users with @gmail accounts, and be reasonably confident that everything is fine (and that I'd know know if it's not). Now, Cyrus and Dovecot (and Courier I guess) is a different story, there is a variety of versions out there, and software being software, there may be bugs / glitches / quirks. Since you mention Cyrus, do you know that it often (like, almost always) responds to "ID" with a "NO"? This is not RFC compliant, but it's what is actually does. For the "more than 50% market share" of Dovecot / Cyrus, do you have a breakdown by version number? At least in terms of 1.* vs 2.0 and higher? > > > So let me try again: >> >> Is sending SELECT ... (CONDSTORE) or STATUS (... HIGHESTMODSEQ ...) enough >> to enable reliable persistent modseq tracking for all versions of Dovecot >> which advertise CONDSTORE in their capabilities? >> > > Maybe. You can't tell until you actually see whether the EXAMINE/SELECT > returns HIGHESTMODSEQ or NOMODSEQ. Are you saying that Dovecot will always (*will always*, and I mean *always*) return NOMODSEQ after a client "expresses interested in modseq values" and the server can't enable it for some reason? Or if it was previously enabled, and then well, I don't know, "something happened"? By *always* I mean -- since Dovecot first started having a CONDSTORE in its CAPS, including version a.b.c that came with now really old Debian X, and version h.j.k that came with now really old RHEL Y, but which are still out there on actual mail servers, being used in actual mail accounts? When something goes wrong in an email app, then to the user, it's always the email app developer's fault. Nobody gives a damn about the subtleties of what RFC abc says about xyz, or if server version j.k.l from three years ago had a bug. So, before enabling certain optimizations for Dovecot, I thought I'd ask on a Dovecot mailing list, about actual behavior for this server feature. I assume this mailing list has people with real Dovecot experience and knowledge, and maybe even the developers are lurking here too. Specifically, I was hoping to hear back maybe something like this: "Dovecot version X which was packaged in Debian Z, would not update the modseq value after command Y". Or maybe -- which would be great: "There were no issues with modseq tracking, at all, no reported bugs, code not touched, since the feature was originally implemented and advertised as CONDSTORE in CAPS in version 1.2.*". -- K From THerrmann at ADwin.de Thu Jul 10 09:54:42 2014 From: THerrmann at ADwin.de (Thomas Herrmann) Date: Thu, 10 Jul 2014 11:54:42 +0200 Subject: Flags in public folders disappear when more than 25 flags are used In-Reply-To: <53BC07CA.5060106@ADwin.de> References: <53B41677.6080300@ADwin.de> <53BC07CA.5060106@ADwin.de> Message-ID: <53BE62E2.7060708@ADwin.de> On 08.07.2014 17:01, Thomas Herrmann wrote: > Now I am a little closer to the problem. I discovered that the > dovecot-keywords file is out of sync with what doveadm reports. Is that > a problem? To continue my monologue, this does not seem to be a problem. The numbering in the dovecot-keywords is different from the ones reported by doveadm in almost all of my folders. Now that I am using 2.2.13, I have observed this: - The flags that are present in the dovecot-keywords are synced between all clients. - The flags that are not in the dovecot-keywords files are not synced between clients, they are in fact per-user keywords (I use per-user seen flags for the public folders). When I set the keywords, I see changes in the dovecot.index.* files located at "/home/vmail/adwin.de/%n/public", while that information should be stored at "/home/vmail/public". Maybe this happens because I am using 2.2.* with INDEX instead of INDEXPVT, so now my question is, how do I upgrade from INDEX to INDEXPVT without losing information? Will dovecot convert the old files automatically? I did not find anything about that at http://wiki2.dovecot.org/Upgrading/2.2 Regards Thomas Herrmann -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4246 bytes Desc: S/MIME Cryptographic Signature URL: From cj.keist at colostate.edu Thu Jul 10 15:04:53 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 09:04:53 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Message-ID: <53BEAB95.4000802@colostate.edu> All, Just move our mail servers over to a new mail server running postfix 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my /var/adm/files. People are complaining of loosing their connections to the mail server. I've been able to google this error but haven't found fix for this yet. NOt sure where to put the drop-priv option in the config files either. Any suggestions? Var adm message: Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Here is config output: root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc auth_failure_delay = 5 secs auth_mechanisms = plain login cram-md5 auth_worker_max_count = 300 base_dir = /userM/mail-services/dovecot/var/run/dovecot/ disable_plaintext_auth = no hostname = mail2.engr.colostate.edu managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = passwd } postmaster_address = cjay at engr.colostate.edu service auth { unix_listener /var/lib/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = References: <53BEAB95.4000802@colostate.edu> Message-ID: <53BEACBB.6040609@colostate.edu> Added info: These errors seem to come from users using mbox format. On 7/10/14, 9:04 AM, CJ Keist wrote: > All, > Just move our mail servers over to a new mail server running postfix > 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my > /var/adm/files. People are complaining of loosing their connections to > the mail server. > > I've been able to google this error but haven't found fix for this yet. > NOt sure where to put the drop-priv option in the config files either. > > Any suggestions? > > Var adm message: > Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): Fatal: > master: service(imap): child 20258 killed with signal 6 (core not dumped > - set service imap { drop_priv_before_exec=yes }) > > Here is config output: > > root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n > # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf > # OS: SunOS 5.11 i86pc > auth_failure_delay = 5 secs > auth_mechanisms = plain login cram-md5 > auth_worker_max_count = 300 > base_dir = /userM/mail-services/dovecot/var/run/dovecot/ > disable_plaintext_auth = no > hostname = mail2.engr.colostate.edu > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date ihave duplicate > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > driver = pam > } > passdb { > driver = passwd > } > postmaster_address = cjay at engr.colostate.edu > service auth { > unix_listener /var/lib/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = postfix > mode = 0666 > user = postfix > } > user = root > } > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > ssl_cert = ssl_key = userdb { > args = blocking=yes > driver = passwd > } > protocol imap { > mail_max_userip_connections = 50 > } > protocol lda { > mail_plugins = sieve > } > > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From r at sys4.de Thu Jul 10 15:12:00 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Thu, 10 Jul 2014 17:12:00 +0200 Subject: SIGSEGV in 2.2.13 with IMAP Proxying to an Exchange Server In-Reply-To: <20140616134549.GM20042@charite.de> References: <20140616134549.GM20042@charite.de> Message-ID: <20140710151200.GF8997@sys4.de> Any Idea on this one? * Ralf Hildebrandt : > 100% reproducible. User is using alpine to write an email. > > Continue postponed composition (answering "No" won't erase it)? > y -> [>Empty folder! No messages really postponed!<] > Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs > > Setup: > ====== > > http://wiki2.dovecot.org/HowTo/ImapcProxy > > coredump available for further inspection > > Full backtrace: > =============== > > Attaching to program: /usr/lib/dovecot/imap, process 15573 > [New LWP 15573] > Core was generated by `dovecot/imap'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 imapc_client_mailbox_cmd (box=0x0, callback=callback at entry=0x7f6ba2ed40e0 , context=context at entry=0x7fff68b7f1a0) at imapc-client.c:351 > #0 imapc_client_mailbox_cmd (box=0x0, callback=callback at entry=0x7f6ba2ed40e0 , context=context at entry=0x7fff68b7f1a0) at imapc-client.c:351 > cmd = > __FUNCTION__ = "imapc_client_mailbox_cmd" > #1 0x00007f6ba2ed4815 in imapc_mailbox_noop (mbox=mbox at entry=0x1294060) at imapc-storage.c:154 > cmd = > sctx = {client = 0x123b400, ret = -2} > #2 0x00007f6ba2ed2d30 in imapc_mailbox_sync_init (box=0x1294060, flags=(MAILBOX_SYNC_FLAG_FULL_READ | MAILBOX_SYNC_FLAG_FIX_INCONSISTENT)) at imapc-sync.c:476 > mbox = 0x1294060 > list = > capabilities = > changes = true > ret = 0 > #3 0x00007f6ba2ee53c9 in mailbox_sync_init (box=box at entry=0x1294060, flags=(MAILBOX_SYNC_FLAG_FULL_READ | MAILBOX_SYNC_FLAG_FIX_INCONSISTENT)) at mail-storage.c:1677 > _data_stack_cur_id = 4 > ctx = > #4 0x00007f6ba2ee54d7 in mailbox_sync (box=box at entry=0x1294060, flags=, flags at entry=MAILBOX_SYNC_FLAG_FULL_READ) at mail-storage.c:1725 > ctx = 0x1294060 > status = {sync_delayed_expunges = 0} > #5 0x00007f6ba2f0fdcb in mailbox_expunge_all_data (box=0x1294060) at index-storage.c:648 > ctx = 0x7fff68b7f35c > t = 0x7fff68b7f35c > mail = 0x0 > search_args = 0x0 > #6 index_storage_mailbox_delete (box=0x1294060) at index-storage.c:701 > metadata = {guid = "\000\000\000\000\000\000\000\000\030\377\347\242\000\000\000", virtual_size = 19480672, cache_fields = 0x0, > precache_fields = (MAIL_FETCH_RECEIVED_DATE | MAIL_FETCH_SAVE_DATE | MAIL_FETCH_PHYSICAL_SIZE | MAIL_FETCH_IMAP_ENVELOPE | MAIL_FETCH_UIDL_FILE_NAME | MAIL_FETCH_GUID | unknown: 16777216), > backend_ns_prefix = 0x7f6ba2ee64b0 "\211\302\061\300\205\322x\bH\203\304\030[]?\366\203\230\002", backend_ns_type = (unknown: 0)} > status = {messages = 0, recent = 0, unseen = 19029536, uidvalidity = 0, uidnext = 1, first_unseen_seq = 0, first_recent_uid = 2730247353, last_cached_seq = 32619, highest_modseq = 19480672, > highest_pvt_modseq = 140100271760191, keywords = 0x1, permanent_flags = 0, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, no_modseq_tracking = 0, have_guids = 0, > have_save_guids = 0, have_only_guid128 = 0} > ret_guid = > #7 0x00007f6ba2ee66a7 in mailbox_delete (box=0x1294060) at mail-storage.c:1319 > ret = > #8 0x000000000040d0e1 in cmd_delete (cmd=0x125ce40) at cmd-delete.c:39 > client = > ns = > box = 0x1294060 > name = 0x121b2b8 "postponed-msgs" > errstr = > error = 32767 > disconnect = false > #9 0x0000000000416cfc in command_exec (cmd=0x125ce40) at imap-commands.c:158 > hook = 0x12240e0 > ret = > #10 0x0000000000415d5f in client_command_input (cmd=0x125ce40) at imap-client.c:778 > client = 0x1268c10 > command = > __FUNCTION__ = "client_command_input" > #11 0x0000000000415e15 in client_command_input (cmd=0x125ce40) at imap-client.c:839 > client = 0x1268c10 > command = > __FUNCTION__ = "client_command_input" > #12 0x0000000000416115 in client_handle_next_command (remove_io_r=, client=0x1268c10) at imap-client.c:877 > No locals. > #13 client_handle_input (client=client at entry=0x1268c10) at imap-client.c:889 > _data_stack_cur_id = 3 > remove_io = false > handled_commands = false > __FUNCTION__ = "client_handle_input" > #14 0x00000000004164a2 in client_input (client=0x1268c10) at imap-client.c:931 > cmd = 0x1234630 > output = 0x125cd30 > bytes = 32 > __FUNCTION__ = "client_input" > #15 0x00007f6ba2c19e6f in io_loop_call_io (io=0x125ae10) at ioloop.c:441 > ioloop = 0x1223730 > t_id = 2 > __FUNCTION__ = "io_loop_call_io" > #16 0x00007f6ba2c1ad77 in io_loop_handler_run_internal (ioloop=ioloop at entry=0x1223730) at ioloop-epoll.c:220 > ctx = 0x12243c0 > list = 0x1225e20 > io = > tv = {tv_sec = 1739, tv_usec = 977960} > events_count = > msecs = > ret = 1 > i = 0 > call = > __FUNCTION__ = "io_loop_handler_run_internal" > #17 0x00007f6ba2c19ed9 in io_loop_handler_run (ioloop=ioloop at entry=0x1223730) at ioloop.c:488 > No locals. > #18 0x00007f6ba2c19f58 in io_loop_run (ioloop=0x1223730) at ioloop.c:465 > __FUNCTION__ = "io_loop_run" > #19 0x00007f6ba2bc9133 in master_service_run (service=0x12235c0, callback=callback at entry=0x41ee50 ) at master-service.c:566 > No locals. > #20 0x000000000040b06f in main (argc=1, argv=0x1223390) at main.c:400 > set_roots = {0x426ca0 , 0x0} > login_set = {auth_socket_path = 0x121b048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x41f200 , > failure_callback = 0x41ef30 , request_auth_token = 1} > service_flags = > storage_service_flags = > username = 0x0 > c = > > -- > Ralf Hildebrandt > Gesch?ftsbereich IT | Abteilung Netzwerk > Charit? - Universit?tsmedizin Berlin > Campus Benjamin Franklin > Hindenburgdamm 30 | D-12203 Berlin > Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 > ralf.hildebrandt at charite.de | http://www.charite.de > -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From tss at iki.fi Thu Jul 10 15:23:26 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 10 Jul 2014 18:23:26 +0300 Subject: BUG: Authentication client sent unknown handshake command In-Reply-To: References: Message-ID: <1217E34B-6648-4CF3-9226-813DFA42DD89@iki.fi> You have misconfigured Dovecot's auth sockets. Providing doveconf -n output would help figuring out the problem. Or just delete all the auth-related socket settings from config files and it should work. On 9.7.2014, at 0.03, Lukas Haase wrote: > May I gently "push" this? > The string "BUG: Authentication client sent unknown handshake command" > comes from dovecot (presumably it's in the source code) so I think it > shouldn't be too mysterious what's happening here. > > Thank you, > Luke > > On 2014-07-03 19:10, Lukas Haase wrote: >> Hi, >> >> Some time ago my dovecot started to become BUGgy: Evertime I restart the >> system, dovecot is started but I cannot login. I see the following >> information in the logs: >> >> Jul 4 04:04:36 mail dovecot: auth: >> passwd-file(user,127.11.91.218,): no passwd file: >> /etc/dovecot/imap.passwd >> Jul 4 04:04:36 mail dovecot: auth: Error: BUG: Authentication client >> sent unknown handshake command: >> REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa >> Jul 4 04:04:36 mail dovecot: imap: Error: Authentication server didn't >> send valid SPID as expected: MECH#011PLAIN#011plaintext >> Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from auth >> server, aborting (client-pid=20438 client-id=1) >> Jul 4 04:04:36 mail dovecot: imap-login: Internal login failure >> (pid=20438 id=1) (internal failure, 1 succesful auths): user=, >> method=PLAIN, rip=127.11.91.218, lip=73.82.101.172, mpid=20439, TLS, >> session= >> >> It does not help to restart the client. But when I then restart the server >> service dovecot restart >> it works again. >> >> But this is very dangerous because the server might reboot and I might >> not immideately have the chance to restart dovecot manually. >> >> What's going on here? >> >> mail:/# uname -a >> Linux mail 2.6.32-openvz-042stab090.2-amd64 #1 SMP Sat Jun 21 00:22:42 >> MSK 2014 i686 GNU/Linux >> mail:/# dovecot --version >> 2.1.7 >> >> Thanks, >> Luke >> From tss at iki.fi Thu Jul 10 15:29:15 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 10 Jul 2014 18:29:15 +0300 Subject: Differences in "Delivered-To" header between deliver and LMTP In-Reply-To: <53BD87D3.9070108@jrice.me> References: <53BD87D3.9070108@jrice.me> Message-ID: <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> On 9.7.2014, at 21.20, Jeff Rice wrote: > I'm transitioning my server over from using the deliver LDA and LMTP. Suddenly a bunch of sieve filters stopped working, and I noticed the contents of the Delivered-To header are different. > > Using Dovecot's deliver LDA, the contents are a bare email address (foo at bar.com). Using Dovecot LMTP, they are in brackets (). Is there a reason why this isn't consistent between the two delivery agents? It seems like it ought to be. Oh, that's annoying. Dovecot LDA doesn't actually add this header, it was your MTA that added it. But looks like I hadn't checked what the MTAs actually write to the header when I added this feature to LMTP, and nobody had mentioned this before either. I wonder if anybody's system breaks if I just change it now.. From cj.keist at colostate.edu Thu Jul 10 15:32:10 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 09:32:10 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEACBB.6040609@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> Message-ID: <53BEB1FA.3000902@colostate.edu> Another problem is people are getting error message from their clients stating they have exceeded their number of connections. On 7/10/14, 9:09 AM, CJ Keist wrote: > Added info: These errors seem to come from users using mbox format. > > > On 7/10/14, 9:04 AM, CJ Keist wrote: >> All, >> Just move our mail servers over to a new mail server running postfix >> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >> /var/adm/files. People are complaining of loosing their connections to >> the mail server. >> >> I've been able to google this error but haven't found fix for this yet. >> NOt sure where to put the drop-priv option in the config files either. >> >> Any suggestions? >> >> Var adm message: >> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): Fatal: >> master: service(imap): child 20258 killed with signal 6 (core not dumped >> - set service imap { drop_priv_before_exec=yes }) >> >> Here is config output: >> >> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >> # OS: SunOS 5.11 i86pc >> auth_failure_delay = 5 secs >> auth_mechanisms = plain login cram-md5 >> auth_worker_max_count = 300 >> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >> disable_plaintext_auth = no >> hostname = mail2.engr.colostate.edu >> managesieve_notify_capability = mailto >> managesieve_sieve_capability = fileinto reject envelope >> encoded-character vacation subaddress comparator-i;ascii-numeric >> relational regex imap4flags copy include variables body enotify >> environment mailbox date ihave duplicate >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> driver = pam >> } >> passdb { >> driver = passwd >> } >> postmaster_address = cjay at engr.colostate.edu >> service auth { >> unix_listener /var/lib/postfix/private/auth { >> mode = 0666 >> } >> unix_listener auth-userdb { >> group = postfix >> mode = 0666 >> user = postfix >> } >> user = root >> } >> service imap-login { >> inet_listener imap { >> port = 143 >> } >> inet_listener imaps { >> port = 993 >> ssl = yes >> } >> } >> service pop3-login { >> inet_listener pop3 { >> port = 110 >> } >> inet_listener pop3s { >> port = 995 >> ssl = yes >> } >> } >> ssl_cert = > ssl_key = > userdb { >> args = blocking=yes >> driver = passwd >> } >> protocol imap { >> mail_max_userip_connections = 50 >> } >> protocol lda { >> mail_plugins = sieve >> } >> >> > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From tss at iki.fi Thu Jul 10 15:37:20 2014 From: tss at iki.fi (Timo Sirainen) Date: Thu, 10 Jul 2014 18:37:20 +0300 Subject: Flags in public folders disappear when more than 25 flags are used In-Reply-To: <53BE62E2.7060708@ADwin.de> References: <53B41677.6080300@ADwin.de> <53BC07CA.5060106@ADwin.de> <53BE62E2.7060708@ADwin.de> Message-ID: <7EFAF990-6348-42AA-9956-71E2D0A73A14@iki.fi> On 10.7.2014, at 12.54, Thomas Herrmann wrote: > > Now that I am using 2.2.13, I have observed this: > > - The flags that are present in the dovecot-keywords are synced between > all clients. > - The flags that are not in the dovecot-keywords files are not synced > between clients, they are in fact per-user keywords (I use per-user seen > flags for the public folders). When I set the keywords, I see changes in > the dovecot.index.* files located at "/home/vmail/adwin.de/%n/public", > while that information should be stored at "/home/vmail/public". > > Maybe this happens because I am using 2.2.* with INDEX instead of > INDEXPVT, Right. > so now my question is, how do I upgrade from INDEX to INDEXPVT > without losing information? Will dovecot convert the old files > automatically? I did not find anything about that at I think it would work if you simply change INDEX -> INDEXPVT, but test first with some test users. From h.reindl at thelounge.net Thu Jul 10 15:45:01 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 10 Jul 2014 17:45:01 +0200 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEB1FA.3000902@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> Message-ID: <53BEB4FD.5070502@thelounge.net> Am 10.07.2014 17:32, schrieb CJ Keist: > Another problem is people are getting error message from their clients stating > they have exceeded their number of connections. mail_max_userip_connections = 50 well, how much folders do the have keep in mind that fpr IDLE you have one connection per user and folder 10 users with 10 folders behind the same NAT router are 100 connections from the same IP > On 7/10/14, 9:09 AM, CJ Keist wrote: >> Added info: These errors seem to come from users using mbox format. >> >> >> On 7/10/14, 9:04 AM, CJ Keist wrote: >>> All, >>> Just move our mail servers over to a new mail server running postfix >>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>> /var/adm/files. People are complaining of loosing their connections to >>> the mail server. >>> >>> I've been able to google this error but haven't found fix for this yet. >>> NOt sure where to put the drop-priv option in the config files either. >>> >>> Any suggestions? >>> >>> Var adm message: >>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): Fatal: >>> master: service(imap): child 20258 killed with signal 6 (core not dumped >>> - set service imap { drop_priv_before_exec=yes }) >>> >>> Here is config output: >>> >>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>> # OS: SunOS 5.11 i86pc >>> auth_failure_delay = 5 secs >>> auth_mechanisms = plain login cram-md5 >>> auth_worker_max_count = 300 >>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>> disable_plaintext_auth = no >>> hostname = mail2.engr.colostate.edu >>> managesieve_notify_capability = mailto >>> managesieve_sieve_capability = fileinto reject envelope >>> encoded-character vacation subaddress comparator-i;ascii-numeric >>> relational regex imap4flags copy include variables body enotify >>> environment mailbox date ihave duplicate >>> namespace inbox { >>> inbox = yes >>> location = >>> mailbox Drafts { >>> special_use = \Drafts >>> } >>> mailbox Junk { >>> special_use = \Junk >>> } >>> mailbox Sent { >>> special_use = \Sent >>> } >>> mailbox "Sent Messages" { >>> special_use = \Sent >>> } >>> mailbox Trash { >>> special_use = \Trash >>> } >>> prefix = >>> } >>> passdb { >>> driver = pam >>> } >>> passdb { >>> driver = passwd >>> } >>> postmaster_address = cjay at engr.colostate.edu >>> service auth { >>> unix_listener /var/lib/postfix/private/auth { >>> mode = 0666 >>> } >>> unix_listener auth-userdb { >>> group = postfix >>> mode = 0666 >>> user = postfix >>> } >>> user = root >>> } >>> service imap-login { >>> inet_listener imap { >>> port = 143 >>> } >>> inet_listener imaps { >>> port = 993 >>> ssl = yes >>> } >>> } >>> service pop3-login { >>> inet_listener pop3 { >>> port = 110 >>> } >>> inet_listener pop3s { >>> port = 995 >>> ssl = yes >>> } >>> } >>> ssl_cert = >> ssl_key = >> userdb { >>> args = blocking=yes >>> driver = passwd >>> } >>> protocol imap { >>> mail_max_userip_connections = 50 >>> } >>> protocol lda { >>> mail_plugins = sieve >>> } -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From cj.keist at colostate.edu Thu Jul 10 15:50:20 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 09:50:20 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEB4FD.5070502@thelounge.net> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> Message-ID: <53BEB63C.7010604@colostate.edu> Thanks for the reply. I have seen threads about setting the mail_max_userip_connections, I have set this to 5000 and still people getting the exceeding connections errorl root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc auth_failure_delay = 5 secs auth_mechanisms = plain login cram-md5 auth_worker_max_count = 3000 base_dir = /userM/mail-services/dovecot/var/run/dovecot/ disable_plaintext_auth = no hostname = mail2.engr.colostate.edu managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = passwd } postmaster_address = cjay at engr.colostate.edu service auth { unix_listener /var/lib/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = > > Am 10.07.2014 17:32, schrieb CJ Keist: >> Another problem is people are getting error message from their clients stating >> they have exceeded their number of connections. > > mail_max_userip_connections = 50 > > well, how much folders do the have > > keep in mind that fpr IDLE you have one connection per user and folder > 10 users with 10 folders behind the same NAT router are 100 connections > from the same IP > >> On 7/10/14, 9:09 AM, CJ Keist wrote: >>> Added info: These errors seem to come from users using mbox format. >>> >>> >>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>> All, >>>> Just move our mail servers over to a new mail server running postfix >>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>> /var/adm/files. People are complaining of loosing their connections to >>>> the mail server. >>>> >>>> I've been able to google this error but haven't found fix for this yet. >>>> NOt sure where to put the drop-priv option in the config files either. >>>> >>>> Any suggestions? >>>> >>>> Var adm message: >>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): Fatal: >>>> master: service(imap): child 20258 killed with signal 6 (core not dumped >>>> - set service imap { drop_priv_before_exec=yes }) >>>> >>>> Here is config output: >>>> >>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>> # OS: SunOS 5.11 i86pc >>>> auth_failure_delay = 5 secs >>>> auth_mechanisms = plain login cram-md5 >>>> auth_worker_max_count = 300 >>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>> disable_plaintext_auth = no >>>> hostname = mail2.engr.colostate.edu >>>> managesieve_notify_capability = mailto >>>> managesieve_sieve_capability = fileinto reject envelope >>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>> relational regex imap4flags copy include variables body enotify >>>> environment mailbox date ihave duplicate >>>> namespace inbox { >>>> inbox = yes >>>> location = >>>> mailbox Drafts { >>>> special_use = \Drafts >>>> } >>>> mailbox Junk { >>>> special_use = \Junk >>>> } >>>> mailbox Sent { >>>> special_use = \Sent >>>> } >>>> mailbox "Sent Messages" { >>>> special_use = \Sent >>>> } >>>> mailbox Trash { >>>> special_use = \Trash >>>> } >>>> prefix = >>>> } >>>> passdb { >>>> driver = pam >>>> } >>>> passdb { >>>> driver = passwd >>>> } >>>> postmaster_address = cjay at engr.colostate.edu >>>> service auth { >>>> unix_listener /var/lib/postfix/private/auth { >>>> mode = 0666 >>>> } >>>> unix_listener auth-userdb { >>>> group = postfix >>>> mode = 0666 >>>> user = postfix >>>> } >>>> user = root >>>> } >>>> service imap-login { >>>> inet_listener imap { >>>> port = 143 >>>> } >>>> inet_listener imaps { >>>> port = 993 >>>> ssl = yes >>>> } >>>> } >>>> service pop3-login { >>>> inet_listener pop3 { >>>> port = 110 >>>> } >>>> inet_listener pop3s { >>>> port = 995 >>>> ssl = yes >>>> } >>>> } >>>> ssl_cert = >>> ssl_key = >>> userdb { >>>> args = blocking=yes >>>> driver = passwd >>>> } >>>> protocol imap { >>>> mail_max_userip_connections = 50 >>>> } >>>> protocol lda { >>>> mail_plugins = sieve >>>> } > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From jeff at jrice.me Thu Jul 10 15:54:10 2014 From: jeff at jrice.me (Jeff Rice) Date: Thu, 10 Jul 2014 11:54:10 -0400 Subject: Differences in "Delivered-To" header between deliver and LMTP In-Reply-To: <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> References: <53BD87D3.9070108@jrice.me> <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> Message-ID: <53BEB722.3070000@jrice.me> I don't know if there is a convention for whether the brackets should be included or not. But consistency is a virtue. The MTA in question is Postfix 2.9.6. I assumed it was the Dovecot LDA adding the Delivered-To header because it was rewritten when I did a redirect in sieve, but redirect must put the message back into Postfix's queue where the header gets added (or replaced, in this case). Maybe other folks can chime in if they see emails in brackets (<>) or not for this type of header for other MTAs and we can get a sense of which is more common. Jeff > Timo Sirainen > July 10, 2014 at 11:29 AM > > Oh, that's annoying. Dovecot LDA doesn't actually add this header, it > was your MTA that added it. But looks like I hadn't checked what the > MTAs actually write to the header when I added this feature to LMTP, > and nobody had mentioned this before either. I wonder if anybody's > system breaks if I just change it now.. > > Jeff Rice > July 9, 2014 at 2:20 PM > Hi, > I'm transitioning my server over from using the deliver LDA and LMTP. > Suddenly a bunch of sieve filters stopped working, and I noticed the > contents of the Delivered-To header are different. > > Using Dovecot's deliver LDA, the contents are a bare email address > (foo at bar.com). Using Dovecot LMTP, they are in brackets > (). Is there a reason why this isn't consistent between > the two delivery agents? It seems like it ought to be. > > Jeff -------------- next part -------------- A non-text attachment was scrubbed... Name: compose-unknown-contact.jpg Type: image/jpeg Size: 770 bytes Desc: not available URL: From cj.keist at colostate.edu Thu Jul 10 16:03:29 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 10:03:29 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEB63C.7010604@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> Message-ID: <53BEB951.8070002@colostate.edu> It looks like on the system that once we hit around 200 imap processes it stops there and no more imap processes can be created. Is there a number of max imap processes in the config file somewhere. By the way running on OmniOS: SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc On 7/10/14, 9:50 AM, CJ Keist wrote: > Thanks for the reply. I have seen threads about setting the > mail_max_userip_connections, I have set this to 5000 and still people > getting the exceeding connections errorl > > > root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n > # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf > # OS: SunOS 5.11 i86pc > auth_failure_delay = 5 secs > auth_mechanisms = plain login cram-md5 > auth_worker_max_count = 3000 > base_dir = /userM/mail-services/dovecot/var/run/dovecot/ > disable_plaintext_auth = no > hostname = mail2.engr.colostate.edu > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date ihave duplicate > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > driver = pam > } > passdb { > driver = passwd > } > postmaster_address = cjay at engr.colostate.edu > service auth { > unix_listener /var/lib/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = postfix > mode = 0666 > user = postfix > } > user = root > } > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > ssl_cert = ssl_key = userdb { > args = blocking=yes > driver = passwd > } > protocol imap { > mail_max_userip_connections = 5000 > } > protocol lda { > mail_plugins = sieve > } > > > On 7/10/14, 9:45 AM, Reindl Harald wrote: >> >> >> Am 10.07.2014 17:32, schrieb CJ Keist: >>> Another problem is people are getting error message from their >>> clients stating >>> they have exceeded their number of connections. >> >> mail_max_userip_connections = 50 >> >> well, how much folders do the have >> >> keep in mind that fpr IDLE you have one connection per user and folder >> 10 users with 10 folders behind the same NAT router are 100 connections >> from the same IP >> >>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>> Added info: These errors seem to come from users using mbox format. >>>> >>>> >>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>> All, >>>>> Just move our mail servers over to a new mail server running >>>>> postfix >>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>> /var/adm/files. People are complaining of loosing their >>>>> connections to >>>>> the mail server. >>>>> >>>>> I've been able to google this error but haven't found fix for this >>>>> yet. >>>>> NOt sure where to put the drop-priv option in the config files >>>>> either. >>>>> >>>>> Any suggestions? >>>>> >>>>> Var adm message: >>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>> Fatal: >>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>> dumped >>>>> - set service imap { drop_priv_before_exec=yes }) >>>>> >>>>> Here is config output: >>>>> >>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>> # OS: SunOS 5.11 i86pc >>>>> auth_failure_delay = 5 secs >>>>> auth_mechanisms = plain login cram-md5 >>>>> auth_worker_max_count = 300 >>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>> disable_plaintext_auth = no >>>>> hostname = mail2.engr.colostate.edu >>>>> managesieve_notify_capability = mailto >>>>> managesieve_sieve_capability = fileinto reject envelope >>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>> relational regex imap4flags copy include variables body enotify >>>>> environment mailbox date ihave duplicate >>>>> namespace inbox { >>>>> inbox = yes >>>>> location = >>>>> mailbox Drafts { >>>>> special_use = \Drafts >>>>> } >>>>> mailbox Junk { >>>>> special_use = \Junk >>>>> } >>>>> mailbox Sent { >>>>> special_use = \Sent >>>>> } >>>>> mailbox "Sent Messages" { >>>>> special_use = \Sent >>>>> } >>>>> mailbox Trash { >>>>> special_use = \Trash >>>>> } >>>>> prefix = >>>>> } >>>>> passdb { >>>>> driver = pam >>>>> } >>>>> passdb { >>>>> driver = passwd >>>>> } >>>>> postmaster_address = cjay at engr.colostate.edu >>>>> service auth { >>>>> unix_listener /var/lib/postfix/private/auth { >>>>> mode = 0666 >>>>> } >>>>> unix_listener auth-userdb { >>>>> group = postfix >>>>> mode = 0666 >>>>> user = postfix >>>>> } >>>>> user = root >>>>> } >>>>> service imap-login { >>>>> inet_listener imap { >>>>> port = 143 >>>>> } >>>>> inet_listener imaps { >>>>> port = 993 >>>>> ssl = yes >>>>> } >>>>> } >>>>> service pop3-login { >>>>> inet_listener pop3 { >>>>> port = 110 >>>>> } >>>>> inet_listener pop3s { >>>>> port = 995 >>>>> ssl = yes >>>>> } >>>>> } >>>>> ssl_cert = >>>> ssl_key = >>>> userdb { >>>>> args = blocking=yes >>>>> driver = passwd >>>>> } >>>>> protocol imap { >>>>> mail_max_userip_connections = 50 >>>>> } >>>>> protocol lda { >>>>> mail_plugins = sieve >>>>> } >> > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From cj.keist at colostate.edu Thu Jul 10 16:35:57 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 10:35:57 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEB951.8070002@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> Message-ID: <53BEC0ED.8010906@colostate.edu> I fixed this issue about the process limit in the 10-master.conf file: default_process_limit = 5000 default_client_limit = 30000 On 7/10/14, 10:03 AM, CJ Keist wrote: > It looks like on the system that once we hit around 200 imap processes > it stops there and no more imap processes can be created. Is there a > number of max imap processes in the config file somewhere. By the way > running on OmniOS: > > SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc > > > > On 7/10/14, 9:50 AM, CJ Keist wrote: >> Thanks for the reply. I have seen threads about setting the >> mail_max_userip_connections, I have set this to 5000 and still people >> getting the exceeding connections errorl >> >> >> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >> # OS: SunOS 5.11 i86pc >> auth_failure_delay = 5 secs >> auth_mechanisms = plain login cram-md5 >> auth_worker_max_count = 3000 >> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >> disable_plaintext_auth = no >> hostname = mail2.engr.colostate.edu >> managesieve_notify_capability = mailto >> managesieve_sieve_capability = fileinto reject envelope >> encoded-character vacation subaddress comparator-i;ascii-numeric >> relational regex imap4flags copy include variables body enotify >> environment mailbox date ihave duplicate >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> driver = pam >> } >> passdb { >> driver = passwd >> } >> postmaster_address = cjay at engr.colostate.edu >> service auth { >> unix_listener /var/lib/postfix/private/auth { >> mode = 0666 >> } >> unix_listener auth-userdb { >> group = postfix >> mode = 0666 >> user = postfix >> } >> user = root >> } >> service imap-login { >> inet_listener imap { >> port = 143 >> } >> inet_listener imaps { >> port = 993 >> ssl = yes >> } >> } >> service pop3-login { >> inet_listener pop3 { >> port = 110 >> } >> inet_listener pop3s { >> port = 995 >> ssl = yes >> } >> } >> ssl_cert = > ssl_key = > userdb { >> args = blocking=yes >> driver = passwd >> } >> protocol imap { >> mail_max_userip_connections = 5000 >> } >> protocol lda { >> mail_plugins = sieve >> } >> >> >> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>> >>> >>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>> Another problem is people are getting error message from their >>>> clients stating >>>> they have exceeded their number of connections. >>> >>> mail_max_userip_connections = 50 >>> >>> well, how much folders do the have >>> >>> keep in mind that fpr IDLE you have one connection per user and folder >>> 10 users with 10 folders behind the same NAT router are 100 connections >>> from the same IP >>> >>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>> Added info: These errors seem to come from users using mbox format. >>>>> >>>>> >>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>> All, >>>>>> Just move our mail servers over to a new mail server running >>>>>> postfix >>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>> /var/adm/files. People are complaining of loosing their >>>>>> connections to >>>>>> the mail server. >>>>>> >>>>>> I've been able to google this error but haven't found fix for this >>>>>> yet. >>>>>> NOt sure where to put the drop-priv option in the config files >>>>>> either. >>>>>> >>>>>> Any suggestions? >>>>>> >>>>>> Var adm message: >>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>> Fatal: >>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>> dumped >>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>> >>>>>> Here is config output: >>>>>> >>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>> # OS: SunOS 5.11 i86pc >>>>>> auth_failure_delay = 5 secs >>>>>> auth_mechanisms = plain login cram-md5 >>>>>> auth_worker_max_count = 300 >>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>> disable_plaintext_auth = no >>>>>> hostname = mail2.engr.colostate.edu >>>>>> managesieve_notify_capability = mailto >>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>> relational regex imap4flags copy include variables body enotify >>>>>> environment mailbox date ihave duplicate >>>>>> namespace inbox { >>>>>> inbox = yes >>>>>> location = >>>>>> mailbox Drafts { >>>>>> special_use = \Drafts >>>>>> } >>>>>> mailbox Junk { >>>>>> special_use = \Junk >>>>>> } >>>>>> mailbox Sent { >>>>>> special_use = \Sent >>>>>> } >>>>>> mailbox "Sent Messages" { >>>>>> special_use = \Sent >>>>>> } >>>>>> mailbox Trash { >>>>>> special_use = \Trash >>>>>> } >>>>>> prefix = >>>>>> } >>>>>> passdb { >>>>>> driver = pam >>>>>> } >>>>>> passdb { >>>>>> driver = passwd >>>>>> } >>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>> service auth { >>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>> mode = 0666 >>>>>> } >>>>>> unix_listener auth-userdb { >>>>>> group = postfix >>>>>> mode = 0666 >>>>>> user = postfix >>>>>> } >>>>>> user = root >>>>>> } >>>>>> service imap-login { >>>>>> inet_listener imap { >>>>>> port = 143 >>>>>> } >>>>>> inet_listener imaps { >>>>>> port = 993 >>>>>> ssl = yes >>>>>> } >>>>>> } >>>>>> service pop3-login { >>>>>> inet_listener pop3 { >>>>>> port = 110 >>>>>> } >>>>>> inet_listener pop3s { >>>>>> port = 995 >>>>>> ssl = yes >>>>>> } >>>>>> } >>>>>> ssl_cert = >>>>> ssl_key = >>>>> userdb { >>>>>> args = blocking=yes >>>>>> driver = passwd >>>>>> } >>>>>> protocol imap { >>>>>> mail_max_userip_connections = 50 >>>>>> } >>>>>> protocol lda { >>>>>> mail_plugins = sieve >>>>>> } >>> >> > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From cj.keist at colostate.edu Thu Jul 10 17:26:05 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 11:26:05 -0600 Subject: dovecot lda invalid user settings Message-ID: <53BECCAD.40402@colostate.edu> I'm now dealing with issue with some users on mbox getting invalid user settings in /var/adm/messages. /var/log/syslog has: Jul 10 11:21:42 mail2 dovecot: [ID 583609 mail.error] lda(ejames): Error: user ejames: Initialization failed: Namespace '': Mail storage autodetection failed with home=/top/academic/Atmos/people/ejames/home Jul 10 11:21:42 mail2 dovecot: [ID 583609 mail.crit] lda(ejames): Fatal: Invalid user settings. Refer to server log for more information. I checked this users home directory and the mail folder is there and permissions are all correct. I'm running in a mixed mbox and Maildir environment. I read to support this environment you simply comment out the mail_location lines in 10-mail.conf file which will force dovecot to auto detect what format a user is using. This worked fine in dovecot 1.2.12, but seems to failing here. root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc auth_failure_delay = 5 secs auth_mechanisms = plain login cram-md5 auth_worker_max_count = 3000 base_dir = /userM/mail-services/dovecot/var/run/dovecot/ default_client_limit = 30000 default_process_limit = 5000 disable_plaintext_auth = no hostname = mail2.engr.colostate.edu managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = passwd } postmaster_address = cjay at engr.colostate.edu service auth { unix_listener /var/lib/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = References: <53BD87D3.9070108@jrice.me> <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> <53BEB722.3070000@jrice.me> Message-ID: There is no Delivered-To: in Exim, there is an "Envelope-To:" which is added withOUT the the angle-brackets(<>) Return-path: Envelope-to: parents at lerctr.org Delivery-date: Thu, 10 Jul 2014 12:17:54 -0500 Does that help? On Thu, Jul 10, 2014 at 10:54 AM, Jeff Rice wrote: > I don't know if there is a convention for whether the brackets should be > included or not. But consistency is a virtue. The MTA in question is > Postfix 2.9.6. I assumed it was the Dovecot LDA adding the Delivered-To > header because it was rewritten when I did a redirect in sieve, but > redirect must put the message back into Postfix's queue where the header > gets added (or replaced, in this case). > > Maybe other folks can chime in if they see emails in brackets (<>) or not > for this type of header for other MTAs and we can get a sense of which is > more common. > > Jeff > > Timo Sirainen >> July 10, 2014 at 11:29 AM >> >> >> Oh, that's annoying. Dovecot LDA doesn't actually add this header, it was >> your MTA that added it. But looks like I hadn't checked what the MTAs >> actually write to the header when I added this feature to LMTP, and nobody >> had mentioned this before either. I wonder if anybody's system breaks if I >> just change it now.. >> >> Jeff Rice >> July 9, 2014 at 2:20 PM >> Hi, >> >> I'm transitioning my server over from using the deliver LDA and LMTP. >> Suddenly a bunch of sieve filters stopped working, and I noticed the >> contents of the Delivered-To header are different. >> >> Using Dovecot's deliver LDA, the contents are a bare email address ( >> foo at bar.com). Using Dovecot LMTP, they are in brackets (). >> Is there a reason why this isn't consistent between the two delivery >> agents? It seems like it ought to be. >> >> Jeff >> > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 From cj.keist at colostate.edu Thu Jul 10 18:33:05 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 12:33:05 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEC0ED.8010906@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> Message-ID: <53BEDC61.4060706@colostate.edu> It's not fixed. Now the limit looks to be around 500 processes and we start to get number of connections exceeded. Any ideas? On 7/10/14, 10:35 AM, CJ Keist wrote: > I fixed this issue about the process limit in the 10-master.conf file: > > default_process_limit = 5000 > default_client_limit = 30000 > > > On 7/10/14, 10:03 AM, CJ Keist wrote: >> It looks like on the system that once we hit around 200 imap processes >> it stops there and no more imap processes can be created. Is there a >> number of max imap processes in the config file somewhere. By the way >> running on OmniOS: >> >> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >> >> >> >> On 7/10/14, 9:50 AM, CJ Keist wrote: >>> Thanks for the reply. I have seen threads about setting the >>> mail_max_userip_connections, I have set this to 5000 and still people >>> getting the exceeding connections errorl >>> >>> >>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>> # OS: SunOS 5.11 i86pc >>> auth_failure_delay = 5 secs >>> auth_mechanisms = plain login cram-md5 >>> auth_worker_max_count = 3000 >>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>> disable_plaintext_auth = no >>> hostname = mail2.engr.colostate.edu >>> managesieve_notify_capability = mailto >>> managesieve_sieve_capability = fileinto reject envelope >>> encoded-character vacation subaddress comparator-i;ascii-numeric >>> relational regex imap4flags copy include variables body enotify >>> environment mailbox date ihave duplicate >>> namespace inbox { >>> inbox = yes >>> location = >>> mailbox Drafts { >>> special_use = \Drafts >>> } >>> mailbox Junk { >>> special_use = \Junk >>> } >>> mailbox Sent { >>> special_use = \Sent >>> } >>> mailbox "Sent Messages" { >>> special_use = \Sent >>> } >>> mailbox Trash { >>> special_use = \Trash >>> } >>> prefix = >>> } >>> passdb { >>> driver = pam >>> } >>> passdb { >>> driver = passwd >>> } >>> postmaster_address = cjay at engr.colostate.edu >>> service auth { >>> unix_listener /var/lib/postfix/private/auth { >>> mode = 0666 >>> } >>> unix_listener auth-userdb { >>> group = postfix >>> mode = 0666 >>> user = postfix >>> } >>> user = root >>> } >>> service imap-login { >>> inet_listener imap { >>> port = 143 >>> } >>> inet_listener imaps { >>> port = 993 >>> ssl = yes >>> } >>> } >>> service pop3-login { >>> inet_listener pop3 { >>> port = 110 >>> } >>> inet_listener pop3s { >>> port = 995 >>> ssl = yes >>> } >>> } >>> ssl_cert = >> ssl_key = >> userdb { >>> args = blocking=yes >>> driver = passwd >>> } >>> protocol imap { >>> mail_max_userip_connections = 5000 >>> } >>> protocol lda { >>> mail_plugins = sieve >>> } >>> >>> >>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>> >>>> >>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>> Another problem is people are getting error message from their >>>>> clients stating >>>>> they have exceeded their number of connections. >>>> >>>> mail_max_userip_connections = 50 >>>> >>>> well, how much folders do the have >>>> >>>> keep in mind that fpr IDLE you have one connection per user and folder >>>> 10 users with 10 folders behind the same NAT router are 100 connections >>>> from the same IP >>>> >>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>> Added info: These errors seem to come from users using mbox format. >>>>>> >>>>>> >>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>> All, >>>>>>> Just move our mail servers over to a new mail server running >>>>>>> postfix >>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>> connections to >>>>>>> the mail server. >>>>>>> >>>>>>> I've been able to google this error but haven't found fix for this >>>>>>> yet. >>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>> either. >>>>>>> >>>>>>> Any suggestions? >>>>>>> >>>>>>> Var adm message: >>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>> Fatal: >>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>> dumped >>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>> >>>>>>> Here is config output: >>>>>>> >>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>> # OS: SunOS 5.11 i86pc >>>>>>> auth_failure_delay = 5 secs >>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>> auth_worker_max_count = 300 >>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>> disable_plaintext_auth = no >>>>>>> hostname = mail2.engr.colostate.edu >>>>>>> managesieve_notify_capability = mailto >>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>> environment mailbox date ihave duplicate >>>>>>> namespace inbox { >>>>>>> inbox = yes >>>>>>> location = >>>>>>> mailbox Drafts { >>>>>>> special_use = \Drafts >>>>>>> } >>>>>>> mailbox Junk { >>>>>>> special_use = \Junk >>>>>>> } >>>>>>> mailbox Sent { >>>>>>> special_use = \Sent >>>>>>> } >>>>>>> mailbox "Sent Messages" { >>>>>>> special_use = \Sent >>>>>>> } >>>>>>> mailbox Trash { >>>>>>> special_use = \Trash >>>>>>> } >>>>>>> prefix = >>>>>>> } >>>>>>> passdb { >>>>>>> driver = pam >>>>>>> } >>>>>>> passdb { >>>>>>> driver = passwd >>>>>>> } >>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>> service auth { >>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>> mode = 0666 >>>>>>> } >>>>>>> unix_listener auth-userdb { >>>>>>> group = postfix >>>>>>> mode = 0666 >>>>>>> user = postfix >>>>>>> } >>>>>>> user = root >>>>>>> } >>>>>>> service imap-login { >>>>>>> inet_listener imap { >>>>>>> port = 143 >>>>>>> } >>>>>>> inet_listener imaps { >>>>>>> port = 993 >>>>>>> ssl = yes >>>>>>> } >>>>>>> } >>>>>>> service pop3-login { >>>>>>> inet_listener pop3 { >>>>>>> port = 110 >>>>>>> } >>>>>>> inet_listener pop3s { >>>>>>> port = 995 >>>>>>> ssl = yes >>>>>>> } >>>>>>> } >>>>>>> ssl_cert = >>>>>> ssl_key = >>>>>> userdb { >>>>>>> args = blocking=yes >>>>>>> driver = passwd >>>>>>> } >>>>>>> protocol imap { >>>>>>> mail_max_userip_connections = 50 >>>>>>> } >>>>>>> protocol lda { >>>>>>> mail_plugins = sieve >>>>>>> } >>>> >>> >> > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From bind at enas.net Thu Jul 10 18:48:33 2014 From: bind at enas.net (Urban Loesch) Date: Thu, 10 Jul 2014 20:48:33 +0200 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEDC61.4060706@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> Message-ID: <53BEE001.4070309@enas.net> Hi, not shure if that helps. In 10-master.conf file exists a "service imap { ... }" section. You could try to increase the "process_limit = " parameter in it. On one of oour servers there we have "process_limit = 2048" and we habe about 1200 concurrent connections without problems. Best, Urban Am 10.07.2014 20:33, schrieb CJ Keist: > It's not fixed. Now the limit looks to be around 500 processes and we > start to get number of connections exceeded. Any ideas? > > > > On 7/10/14, 10:35 AM, CJ Keist wrote: >> I fixed this issue about the process limit in the 10-master.conf file: >> >> default_process_limit = 5000 >> default_client_limit = 30000 >> >> >> On 7/10/14, 10:03 AM, CJ Keist wrote: >>> It looks like on the system that once we hit around 200 imap processes >>> it stops there and no more imap processes can be created. Is there a >>> number of max imap processes in the config file somewhere. By the way >>> running on OmniOS: >>> >>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>> >>> >>> >>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>> Thanks for the reply. I have seen threads about setting the >>>> mail_max_userip_connections, I have set this to 5000 and still people >>>> getting the exceeding connections errorl >>>> >>>> >>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>> # OS: SunOS 5.11 i86pc >>>> auth_failure_delay = 5 secs >>>> auth_mechanisms = plain login cram-md5 >>>> auth_worker_max_count = 3000 >>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>> disable_plaintext_auth = no >>>> hostname = mail2.engr.colostate.edu >>>> managesieve_notify_capability = mailto >>>> managesieve_sieve_capability = fileinto reject envelope >>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>> relational regex imap4flags copy include variables body enotify >>>> environment mailbox date ihave duplicate >>>> namespace inbox { >>>> inbox = yes >>>> location = >>>> mailbox Drafts { >>>> special_use = \Drafts >>>> } >>>> mailbox Junk { >>>> special_use = \Junk >>>> } >>>> mailbox Sent { >>>> special_use = \Sent >>>> } >>>> mailbox "Sent Messages" { >>>> special_use = \Sent >>>> } >>>> mailbox Trash { >>>> special_use = \Trash >>>> } >>>> prefix = >>>> } >>>> passdb { >>>> driver = pam >>>> } >>>> passdb { >>>> driver = passwd >>>> } >>>> postmaster_address = cjay at engr.colostate.edu >>>> service auth { >>>> unix_listener /var/lib/postfix/private/auth { >>>> mode = 0666 >>>> } >>>> unix_listener auth-userdb { >>>> group = postfix >>>> mode = 0666 >>>> user = postfix >>>> } >>>> user = root >>>> } >>>> service imap-login { >>>> inet_listener imap { >>>> port = 143 >>>> } >>>> inet_listener imaps { >>>> port = 993 >>>> ssl = yes >>>> } >>>> } >>>> service pop3-login { >>>> inet_listener pop3 { >>>> port = 110 >>>> } >>>> inet_listener pop3s { >>>> port = 995 >>>> ssl = yes >>>> } >>>> } >>>> ssl_cert = >>> ssl_key = >>> userdb { >>>> args = blocking=yes >>>> driver = passwd >>>> } >>>> protocol imap { >>>> mail_max_userip_connections = 5000 >>>> } >>>> protocol lda { >>>> mail_plugins = sieve >>>> } >>>> >>>> >>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>> >>>>> >>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>> Another problem is people are getting error message from their >>>>>> clients stating >>>>>> they have exceeded their number of connections. >>>>> >>>>> mail_max_userip_connections = 50 >>>>> >>>>> well, how much folders do the have >>>>> >>>>> keep in mind that fpr IDLE you have one connection per user and folder >>>>> 10 users with 10 folders behind the same NAT router are 100 >>>>> connections >>>>> from the same IP >>>>> >>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>> Added info: These errors seem to come from users using mbox format. >>>>>>> >>>>>>> >>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>> All, >>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>> postfix >>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>> connections to >>>>>>>> the mail server. >>>>>>>> >>>>>>>> I've been able to google this error but haven't found fix for this >>>>>>>> yet. >>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>> either. >>>>>>>> >>>>>>>> Any suggestions? >>>>>>>> >>>>>>>> Var adm message: >>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>> Fatal: >>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>> dumped >>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>> >>>>>>>> Here is config output: >>>>>>>> >>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>> auth_failure_delay = 5 secs >>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>> auth_worker_max_count = 300 >>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>> disable_plaintext_auth = no >>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>> managesieve_notify_capability = mailto >>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>> environment mailbox date ihave duplicate >>>>>>>> namespace inbox { >>>>>>>> inbox = yes >>>>>>>> location = >>>>>>>> mailbox Drafts { >>>>>>>> special_use = \Drafts >>>>>>>> } >>>>>>>> mailbox Junk { >>>>>>>> special_use = \Junk >>>>>>>> } >>>>>>>> mailbox Sent { >>>>>>>> special_use = \Sent >>>>>>>> } >>>>>>>> mailbox "Sent Messages" { >>>>>>>> special_use = \Sent >>>>>>>> } >>>>>>>> mailbox Trash { >>>>>>>> special_use = \Trash >>>>>>>> } >>>>>>>> prefix = >>>>>>>> } >>>>>>>> passdb { >>>>>>>> driver = pam >>>>>>>> } >>>>>>>> passdb { >>>>>>>> driver = passwd >>>>>>>> } >>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>> service auth { >>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>> mode = 0666 >>>>>>>> } >>>>>>>> unix_listener auth-userdb { >>>>>>>> group = postfix >>>>>>>> mode = 0666 >>>>>>>> user = postfix >>>>>>>> } >>>>>>>> user = root >>>>>>>> } >>>>>>>> service imap-login { >>>>>>>> inet_listener imap { >>>>>>>> port = 143 >>>>>>>> } >>>>>>>> inet_listener imaps { >>>>>>>> port = 993 >>>>>>>> ssl = yes >>>>>>>> } >>>>>>>> } >>>>>>>> service pop3-login { >>>>>>>> inet_listener pop3 { >>>>>>>> port = 110 >>>>>>>> } >>>>>>>> inet_listener pop3s { >>>>>>>> port = 995 >>>>>>>> ssl = yes >>>>>>>> } >>>>>>>> } >>>>>>>> ssl_cert = >>>>>>> ssl_key = >>>>>>> userdb { >>>>>>>> args = blocking=yes >>>>>>>> driver = passwd >>>>>>>> } >>>>>>>> protocol imap { >>>>>>>> mail_max_userip_connections = 50 >>>>>>>> } >>>>>>>> protocol lda { >>>>>>>> mail_plugins = sieve >>>>>>>> } >>>>> >>>> >>> >> > From cj.keist at colostate.edu Thu Jul 10 19:11:40 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 13:11:40 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEE001.4070309@enas.net> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <53BEE001.4070309@enas.net> Message-ID: <53BEE56C.4000703@colostate.edu> That didn't work. Still seem to stop accepting new imap connections when we hit around 500 processes. On 7/10/14, 12:48 PM, Urban Loesch wrote: > Hi, > > not shure if that helps. > > In 10-master.conf file exists a "service imap { ... }" section. > You could try to increase the "process_limit = " parameter in it. > > On one of oour servers there we have "process_limit = 2048" and we habe > about 1200 concurrent connections without problems. > > Best, > Urban > > > Am 10.07.2014 20:33, schrieb CJ Keist: >> It's not fixed. Now the limit looks to be around 500 processes and we >> start to get number of connections exceeded. Any ideas? >> >> >> >> On 7/10/14, 10:35 AM, CJ Keist wrote: >>> I fixed this issue about the process limit in the 10-master.conf file: >>> >>> default_process_limit = 5000 >>> default_client_limit = 30000 >>> >>> >>> On 7/10/14, 10:03 AM, CJ Keist wrote: >>>> It looks like on the system that once we hit around 200 imap processes >>>> it stops there and no more imap processes can be created. Is there a >>>> number of max imap processes in the config file somewhere. By the way >>>> running on OmniOS: >>>> >>>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>>> >>>> >>>> >>>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>>> Thanks for the reply. I have seen threads about setting the >>>>> mail_max_userip_connections, I have set this to 5000 and still people >>>>> getting the exceeding connections errorl >>>>> >>>>> >>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>> # OS: SunOS 5.11 i86pc >>>>> auth_failure_delay = 5 secs >>>>> auth_mechanisms = plain login cram-md5 >>>>> auth_worker_max_count = 3000 >>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>> disable_plaintext_auth = no >>>>> hostname = mail2.engr.colostate.edu >>>>> managesieve_notify_capability = mailto >>>>> managesieve_sieve_capability = fileinto reject envelope >>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>> relational regex imap4flags copy include variables body enotify >>>>> environment mailbox date ihave duplicate >>>>> namespace inbox { >>>>> inbox = yes >>>>> location = >>>>> mailbox Drafts { >>>>> special_use = \Drafts >>>>> } >>>>> mailbox Junk { >>>>> special_use = \Junk >>>>> } >>>>> mailbox Sent { >>>>> special_use = \Sent >>>>> } >>>>> mailbox "Sent Messages" { >>>>> special_use = \Sent >>>>> } >>>>> mailbox Trash { >>>>> special_use = \Trash >>>>> } >>>>> prefix = >>>>> } >>>>> passdb { >>>>> driver = pam >>>>> } >>>>> passdb { >>>>> driver = passwd >>>>> } >>>>> postmaster_address = cjay at engr.colostate.edu >>>>> service auth { >>>>> unix_listener /var/lib/postfix/private/auth { >>>>> mode = 0666 >>>>> } >>>>> unix_listener auth-userdb { >>>>> group = postfix >>>>> mode = 0666 >>>>> user = postfix >>>>> } >>>>> user = root >>>>> } >>>>> service imap-login { >>>>> inet_listener imap { >>>>> port = 143 >>>>> } >>>>> inet_listener imaps { >>>>> port = 993 >>>>> ssl = yes >>>>> } >>>>> } >>>>> service pop3-login { >>>>> inet_listener pop3 { >>>>> port = 110 >>>>> } >>>>> inet_listener pop3s { >>>>> port = 995 >>>>> ssl = yes >>>>> } >>>>> } >>>>> ssl_cert = >>>> ssl_key = >>>> userdb { >>>>> args = blocking=yes >>>>> driver = passwd >>>>> } >>>>> protocol imap { >>>>> mail_max_userip_connections = 5000 >>>>> } >>>>> protocol lda { >>>>> mail_plugins = sieve >>>>> } >>>>> >>>>> >>>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>>> >>>>>> >>>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>>> Another problem is people are getting error message from their >>>>>>> clients stating >>>>>>> they have exceeded their number of connections. >>>>>> >>>>>> mail_max_userip_connections = 50 >>>>>> >>>>>> well, how much folders do the have >>>>>> >>>>>> keep in mind that fpr IDLE you have one connection per user and >>>>>> folder >>>>>> 10 users with 10 folders behind the same NAT router are 100 >>>>>> connections >>>>>> from the same IP >>>>>> >>>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>>> Added info: These errors seem to come from users using mbox >>>>>>>> format. >>>>>>>> >>>>>>>> >>>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>>> All, >>>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>>> postfix >>>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors >>>>>>>>> in my >>>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>>> connections to >>>>>>>>> the mail server. >>>>>>>>> >>>>>>>>> I've been able to google this error but haven't found fix for this >>>>>>>>> yet. >>>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>>> either. >>>>>>>>> >>>>>>>>> Any suggestions? >>>>>>>>> >>>>>>>>> Var adm message: >>>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>>> Fatal: >>>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>>> dumped >>>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>>> >>>>>>>>> Here is config output: >>>>>>>>> >>>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>>> auth_failure_delay = 5 secs >>>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>>> auth_worker_max_count = 300 >>>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>>> disable_plaintext_auth = no >>>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>>> managesieve_notify_capability = mailto >>>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>>> environment mailbox date ihave duplicate >>>>>>>>> namespace inbox { >>>>>>>>> inbox = yes >>>>>>>>> location = >>>>>>>>> mailbox Drafts { >>>>>>>>> special_use = \Drafts >>>>>>>>> } >>>>>>>>> mailbox Junk { >>>>>>>>> special_use = \Junk >>>>>>>>> } >>>>>>>>> mailbox Sent { >>>>>>>>> special_use = \Sent >>>>>>>>> } >>>>>>>>> mailbox "Sent Messages" { >>>>>>>>> special_use = \Sent >>>>>>>>> } >>>>>>>>> mailbox Trash { >>>>>>>>> special_use = \Trash >>>>>>>>> } >>>>>>>>> prefix = >>>>>>>>> } >>>>>>>>> passdb { >>>>>>>>> driver = pam >>>>>>>>> } >>>>>>>>> passdb { >>>>>>>>> driver = passwd >>>>>>>>> } >>>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>>> service auth { >>>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>>> mode = 0666 >>>>>>>>> } >>>>>>>>> unix_listener auth-userdb { >>>>>>>>> group = postfix >>>>>>>>> mode = 0666 >>>>>>>>> user = postfix >>>>>>>>> } >>>>>>>>> user = root >>>>>>>>> } >>>>>>>>> service imap-login { >>>>>>>>> inet_listener imap { >>>>>>>>> port = 143 >>>>>>>>> } >>>>>>>>> inet_listener imaps { >>>>>>>>> port = 993 >>>>>>>>> ssl = yes >>>>>>>>> } >>>>>>>>> } >>>>>>>>> service pop3-login { >>>>>>>>> inet_listener pop3 { >>>>>>>>> port = 110 >>>>>>>>> } >>>>>>>>> inet_listener pop3s { >>>>>>>>> port = 995 >>>>>>>>> ssl = yes >>>>>>>>> } >>>>>>>>> } >>>>>>>>> ssl_cert = >>>>>>>> ssl_key = >>>>>>>> userdb { >>>>>>>>> args = blocking=yes >>>>>>>>> driver = passwd >>>>>>>>> } >>>>>>>>> protocol imap { >>>>>>>>> mail_max_userip_connections = 50 >>>>>>>>> } >>>>>>>>> protocol lda { >>>>>>>>> mail_plugins = sieve >>>>>>>>> } >>>>>> >>>>> >>>> >>> >> -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From cj.keist at colostate.edu Thu Jul 10 19:59:28 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 13:59:28 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEE56C.4000703@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <53BEE001.4070309@enas.net> <53BEE56C.4000703@colostate.edu> Message-ID: <53BEF0A0.2000106@colostate.edu> Update: I had to fall back to the 1.2.17 dovecot code. Doing that solved the invalid user settings and dovecot inability to auto detect between mbox and Maildir format for user accounts and no longer have the limited number of imap processes either. Not sure what I was missing in the config files, but this is the route I will stay on for now. If it helps here is the 1.2.17 config: root at mail2:/userM/mail-services/dovecot2/sbin# ./dovecot -n # 1.2.17: /userM/mail-services/dovecot2/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: SunOS 5.11 i86pc base_dir: /userM/mail-services/dovecot2/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot2/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot2/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /userM/mail-services/dovecot2/var/run/dovecot/login login_executable(default): /userM/mail-services/dovecot2/libexec/dovecot/imap-login login_executable(imap): /userM/mail-services/dovecot2/libexec/dovecot/imap-login login_executable(pop3): /userM/mail-services/dovecot2/libexec/dovecot/pop3-login login_greeting: Cyrus ready. login_max_processes_count: 1024 max_mail_processes: 1024 mail_debug: yes mmap_disable: yes mail_nfs_index: yes mbox_write_locks: fcntl dotlock mbox_dotlock_change_timeout: 60 mail_executable(default): /userM/mail-services/dovecot2/libexec/dovecot/imap mail_executable(imap): /userM/mail-services/dovecot2/libexec/dovecot/imap mail_executable(pop3): /userM/mail-services/dovecot2/libexec/dovecot/pop3 mail_plugin_dir(default): /userM/mail-services/dovecot2/lib/dovecot/imap mail_plugin_dir(imap): /userM/mail-services/dovecot2/lib/dovecot/imap mail_plugin_dir(pop3): /userM/mail-services/dovecot2/lib/dovecot/pop3 lda: postmaster_address: cjay at engr.colostate.edu hostname: mail1.engr.colostate.edu mail_plugins: cmusieve mail_plugin_dir: /userM/mail-services/dovecot2/lib/dovecot/lda sendmail_path: /userM/mail-services/postfix/lib/sendmail rejection_reason: Your message to <%t> was automatically rejected:%n%r auth default: mechanisms: plain login verbose: yes debug: yes worker_max_count: 1024 passdb: driver: pam passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/lib/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /userM/mail-services/dovecot2/var/run/dovecot//auth-master mode: 384 On 7/10/14, 1:11 PM, CJ Keist wrote: > That didn't work. Still seem to stop accepting new imap connections when > we hit around 500 processes. > > > On 7/10/14, 12:48 PM, Urban Loesch wrote: >> Hi, >> >> not shure if that helps. >> >> In 10-master.conf file exists a "service imap { ... }" section. >> You could try to increase the "process_limit = " parameter in it. >> >> On one of oour servers there we have "process_limit = 2048" and we habe >> about 1200 concurrent connections without problems. >> >> Best, >> Urban >> >> >> Am 10.07.2014 20:33, schrieb CJ Keist: >>> It's not fixed. Now the limit looks to be around 500 processes and we >>> start to get number of connections exceeded. Any ideas? >>> >>> >>> >>> On 7/10/14, 10:35 AM, CJ Keist wrote: >>>> I fixed this issue about the process limit in the 10-master.conf file: >>>> >>>> default_process_limit = 5000 >>>> default_client_limit = 30000 >>>> >>>> >>>> On 7/10/14, 10:03 AM, CJ Keist wrote: >>>>> It looks like on the system that once we hit around 200 imap processes >>>>> it stops there and no more imap processes can be created. Is there a >>>>> number of max imap processes in the config file somewhere. By the way >>>>> running on OmniOS: >>>>> >>>>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>>>> >>>>> >>>>> >>>>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>>>> Thanks for the reply. I have seen threads about setting the >>>>>> mail_max_userip_connections, I have set this to 5000 and still people >>>>>> getting the exceeding connections errorl >>>>>> >>>>>> >>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>> # OS: SunOS 5.11 i86pc >>>>>> auth_failure_delay = 5 secs >>>>>> auth_mechanisms = plain login cram-md5 >>>>>> auth_worker_max_count = 3000 >>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>> disable_plaintext_auth = no >>>>>> hostname = mail2.engr.colostate.edu >>>>>> managesieve_notify_capability = mailto >>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>> relational regex imap4flags copy include variables body enotify >>>>>> environment mailbox date ihave duplicate >>>>>> namespace inbox { >>>>>> inbox = yes >>>>>> location = >>>>>> mailbox Drafts { >>>>>> special_use = \Drafts >>>>>> } >>>>>> mailbox Junk { >>>>>> special_use = \Junk >>>>>> } >>>>>> mailbox Sent { >>>>>> special_use = \Sent >>>>>> } >>>>>> mailbox "Sent Messages" { >>>>>> special_use = \Sent >>>>>> } >>>>>> mailbox Trash { >>>>>> special_use = \Trash >>>>>> } >>>>>> prefix = >>>>>> } >>>>>> passdb { >>>>>> driver = pam >>>>>> } >>>>>> passdb { >>>>>> driver = passwd >>>>>> } >>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>> service auth { >>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>> mode = 0666 >>>>>> } >>>>>> unix_listener auth-userdb { >>>>>> group = postfix >>>>>> mode = 0666 >>>>>> user = postfix >>>>>> } >>>>>> user = root >>>>>> } >>>>>> service imap-login { >>>>>> inet_listener imap { >>>>>> port = 143 >>>>>> } >>>>>> inet_listener imaps { >>>>>> port = 993 >>>>>> ssl = yes >>>>>> } >>>>>> } >>>>>> service pop3-login { >>>>>> inet_listener pop3 { >>>>>> port = 110 >>>>>> } >>>>>> inet_listener pop3s { >>>>>> port = 995 >>>>>> ssl = yes >>>>>> } >>>>>> } >>>>>> ssl_cert = >>>>> ssl_key = >>>>> userdb { >>>>>> args = blocking=yes >>>>>> driver = passwd >>>>>> } >>>>>> protocol imap { >>>>>> mail_max_userip_connections = 5000 >>>>>> } >>>>>> protocol lda { >>>>>> mail_plugins = sieve >>>>>> } >>>>>> >>>>>> >>>>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>>>> >>>>>>> >>>>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>>>> Another problem is people are getting error message from their >>>>>>>> clients stating >>>>>>>> they have exceeded their number of connections. >>>>>>> >>>>>>> mail_max_userip_connections = 50 >>>>>>> >>>>>>> well, how much folders do the have >>>>>>> >>>>>>> keep in mind that fpr IDLE you have one connection per user and >>>>>>> folder >>>>>>> 10 users with 10 folders behind the same NAT router are 100 >>>>>>> connections >>>>>>> from the same IP >>>>>>> >>>>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>>>> Added info: These errors seem to come from users using mbox >>>>>>>>> format. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>>>> All, >>>>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>>>> postfix >>>>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors >>>>>>>>>> in my >>>>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>>>> connections to >>>>>>>>>> the mail server. >>>>>>>>>> >>>>>>>>>> I've been able to google this error but haven't found fix for >>>>>>>>>> this >>>>>>>>>> yet. >>>>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>>>> either. >>>>>>>>>> >>>>>>>>>> Any suggestions? >>>>>>>>>> >>>>>>>>>> Var adm message: >>>>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>>>> Fatal: >>>>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>>>> dumped >>>>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>>>> >>>>>>>>>> Here is config output: >>>>>>>>>> >>>>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>>>> auth_failure_delay = 5 secs >>>>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>>>> auth_worker_max_count = 300 >>>>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>>>> disable_plaintext_auth = no >>>>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>>>> managesieve_notify_capability = mailto >>>>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>>>> environment mailbox date ihave duplicate >>>>>>>>>> namespace inbox { >>>>>>>>>> inbox = yes >>>>>>>>>> location = >>>>>>>>>> mailbox Drafts { >>>>>>>>>> special_use = \Drafts >>>>>>>>>> } >>>>>>>>>> mailbox Junk { >>>>>>>>>> special_use = \Junk >>>>>>>>>> } >>>>>>>>>> mailbox Sent { >>>>>>>>>> special_use = \Sent >>>>>>>>>> } >>>>>>>>>> mailbox "Sent Messages" { >>>>>>>>>> special_use = \Sent >>>>>>>>>> } >>>>>>>>>> mailbox Trash { >>>>>>>>>> special_use = \Trash >>>>>>>>>> } >>>>>>>>>> prefix = >>>>>>>>>> } >>>>>>>>>> passdb { >>>>>>>>>> driver = pam >>>>>>>>>> } >>>>>>>>>> passdb { >>>>>>>>>> driver = passwd >>>>>>>>>> } >>>>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>>>> service auth { >>>>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>>>> mode = 0666 >>>>>>>>>> } >>>>>>>>>> unix_listener auth-userdb { >>>>>>>>>> group = postfix >>>>>>>>>> mode = 0666 >>>>>>>>>> user = postfix >>>>>>>>>> } >>>>>>>>>> user = root >>>>>>>>>> } >>>>>>>>>> service imap-login { >>>>>>>>>> inet_listener imap { >>>>>>>>>> port = 143 >>>>>>>>>> } >>>>>>>>>> inet_listener imaps { >>>>>>>>>> port = 993 >>>>>>>>>> ssl = yes >>>>>>>>>> } >>>>>>>>>> } >>>>>>>>>> service pop3-login { >>>>>>>>>> inet_listener pop3 { >>>>>>>>>> port = 110 >>>>>>>>>> } >>>>>>>>>> inet_listener pop3s { >>>>>>>>>> port = 995 >>>>>>>>>> ssl = yes >>>>>>>>>> } >>>>>>>>>> } >>>>>>>>>> ssl_cert = >>>>>>>>> ssl_key = >>>>>>>>> userdb { >>>>>>>>>> args = blocking=yes >>>>>>>>>> driver = passwd >>>>>>>>>> } >>>>>>>>>> protocol imap { >>>>>>>>>> mail_max_userip_connections = 50 >>>>>>>>>> } >>>>>>>>>> protocol lda { >>>>>>>>>> mail_plugins = sieve >>>>>>>>>> } >>>>>>> >>>>>> >>>>> >>>> >>> > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From me at junc.eu Thu Jul 10 20:38:32 2014 From: me at junc.eu (Benny Pedersen) Date: Thu, 10 Jul 2014 22:38:32 +0200 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEF0A0.2000106@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <53BEE001.4070309@enas.net> <53BEE56C.4000703@colostate.edu> <53BEF0A0.2000106@colostate.edu> Message-ID: <8bd6e740-11c0-4323-a42a-8a6ed3ac8286@email.android.com> On 10. jul. 2014 21.59.28 CEST, CJ Keist wrote: >root at mail2:/userM/mail-services/dovecot2/sbin# ./dovecot -n ># 1.2.17: /userM/mail-services/dovecot2/etc/dovecot.conf >Warning: fd limit 256 is lower than what Dovecot can use under full >load >(more than 3072). Either grow the limit or change >login_max_processes_count and max_mail_processes settings Warning there is an os limit, not a dovecot fault ># OS: SunOS 5.11 i86pc >base_dir: /userM/mail-services/dovecot2/var/run/dovecot/ >protocols: imap imaps pop3 pop3s Why ssl if non ssl is provided aswell ? >login_max_processes_count: 1024 >max_mail_processes: 1024 Exeded os limit > master: > path: /userM/mail-services/dovecot2/var/run/dovecot//auth-master Doubble slash From cj.keist at colostate.edu Thu Jul 10 20:45:04 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Thu, 10 Jul 2014 14:45:04 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <8bd6e740-11c0-4323-a42a-8a6ed3ac8286@email.android.com> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <53BEE001.4070309@enas.net> <53BEE56C.4000703@colostate.edu> <53BEF0A0.2000106@colostate.edu> <8bd6e740-11c0-4323-a42a-8a6ed3ac8286@email.android.com> Message-ID: <53BEFB50.2000103@colostate.edu> After starting dovecot the following is run to take care of the fd limit: /usr/bin/plimit -n 16384,16384 `cat ../var/run/dovecot/master.pid` I was doing this same commend for 2.2. dovecot as well. I do have ssl configured and working. My mail client confirms the secure connection is made. Not sure why the dovecot -n showed double slash, it's not that way in the config file. On 7/10/14, 2:38 PM, Benny Pedersen wrote: > On 10. jul. 2014 21.59.28 CEST, CJ Keist wrote: > >> root at mail2:/userM/mail-services/dovecot2/sbin# ./dovecot -n >> # 1.2.17: /userM/mail-services/dovecot2/etc/dovecot.conf >> Warning: fd limit 256 is lower than what Dovecot can use under full >> load >> (more than 3072). Either grow the limit or change >> login_max_processes_count and max_mail_processes settings > > Warning there is an os limit, not a dovecot fault > >> # OS: SunOS 5.11 i86pc >> base_dir: /userM/mail-services/dovecot2/var/run/dovecot/ >> protocols: imap imaps pop3 pop3s > > Why ssl if non ssl is provided aswell ? > >> login_max_processes_count: 1024 >> max_mail_processes: 1024 > > Exeded os limit > >> master: >> path: /userM/mail-services/dovecot2/var/run/dovecot//auth-master > > Doubble slash > -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From arekm at maven.pl Fri Jul 11 07:59:58 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Fri, 11 Jul 2014 09:59:58 +0200 Subject: macros Message-ID: <201407110959.58784.arekm@maven.pl> Does dovecot support any form of macros? I would like to share configuration file between several servers. Configs are different only in tiny aspects. Somethine like: dovecot-server.conf (different on each server): %define ID 55 %define SOMETHING SELECT FROM * WHERE something %define MECHANISMS digest-md5 dovecot-main.conf (common, shared config) !include dovecot-server.conf user_query = ${SOMETHING} AND id=${ID} auth_mechanisms = plain login ${MECHANISMS} etc -- Arkadiusz Mi?kiewicz, arekm / maven.pl From nick.z.edwards at gmail.com Fri Jul 11 08:04:03 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Fri, 11 Jul 2014 18:04:03 +1000 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEAB95.4000802@colostate.edu> References: <53BEAB95.4000802@colostate.edu> Message-ID: On 7/11/14, CJ Keist wrote: see inlines, its what we needed, we found dovecots default is great - for SOHO, but hopeless for ISP size use which is what you need, I wish Timo would include a conf file for large organisations, by defaults we had issues same as you all limits way too low > > service auth { client_limit = 2248 <------------------------------------- > unix_listener /var/lib/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = postfix > mode = 0666 > user = postfix > } > user = root > } > service imap-login { process_limit = 1024 <------------------ > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > service pop3-login { process_limit = 1024 <------------ > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > ssl_cert = ssl_key = userdb { > args = blocking=yes > driver = passwd > } > protocol imap { process_limit = 1024 <---------- (and bigger for pop3 but pop3 is more popular here) > mail_max_userip_connections = 50 > } service anvil { client_limit = 2251 } > protocol lda { > mail_plugins = sieve > } > > > -- > C. J. Keist Email: cj.keist at colostate.edu > Systems Group Manager Solaris 10 OS (SAI) > Engineering Network Services Phone: 970-491-0630 > College of Engineering, CSU Fax: 970-491-5569 > Ft. Collins, CO 80523-1301 > > All I want is a chance to prove 'Money can't buy happiness' > From CMarcus at Media-Brokers.com Fri Jul 11 09:23:43 2014 From: CMarcus at Media-Brokers.com (Charles Marcus) Date: Fri, 11 Jul 2014 05:23:43 -0400 Subject: Differences in "Delivered-To" header between deliver and LMTP In-Reply-To: <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> References: <53BD87D3.9070108@jrice.me> <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> Message-ID: <53BFAD1F.3020406@Media-Brokers.com> On 7/10/2014 11:29 AM, Timo Sirainen wrote: > On 9.7.2014, at 21.20, Jeff Rice wrote: > >> I'm transitioning my server over from using the deliver LDA and LMTP. Suddenly a bunch of sieve filters stopped working, and I noticed the contents of the Delivered-To header are different. >> >> Using Dovecot's deliver LDA, the contents are a bare email address (foo at bar.com). Using Dovecot LMTP, they are in brackets (). Is there a reason why this isn't consistent between the two delivery agents? It seems like it ought to be. > Oh, that's annoying. Dovecot LDA doesn't actually add this header, it was your MTA that added it. But looks like I hadn't checked what the MTAs actually write to the header when I added this feature to LMTP, and nobody had mentioned this before either. I wonder if anybody's system breaks if I just change it now.. If you do this Timo, would you please also consider going ahead and adding the 20 or so lines of code you said it would take to also add support for the x-original-to header (this specific was in a private email to me while our support contract was active), as we discussed on this list - and you then discussed with Wietse, back in April or so of 2012: http://dovecot.org/list/dovecot/2012-April/082585.html Thanks! Charles From cj.keist at colostate.edu Fri Jul 11 13:45:33 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Fri, 11 Jul 2014 07:45:33 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: References: <53BEAB95.4000802@colostate.edu> Message-ID: <53BFEA7D.6010108@colostate.edu> Thank you. I will try these settings out and give 2.2 one more shot. On 7/11/2014 2:04 AM, Nick Edwards wrote: > On 7/11/14, CJ Keist wrote: > see inlines, its what we needed, we found dovecots default is great - > for SOHO, but hopeless for ISP size use which is what you need, I > wish Timo would include a conf file for large organisations, by > defaults we had issues same as you all limits way too low > > >> >> service auth { > client_limit = 2248 <------------------------------------- >> unix_listener /var/lib/postfix/private/auth { >> mode = 0666 >> } >> unix_listener auth-userdb { >> group = postfix >> mode = 0666 >> user = postfix >> } >> user = root >> } > > > >> service imap-login { > process_limit = 1024 <------------------ >> inet_listener imap { >> port = 143 >> } >> inet_listener imaps { >> port = 993 >> ssl = yes >> } >> } >> service pop3-login { > process_limit = 1024 <------------ >> inet_listener pop3 { >> port = 110 >> } >> inet_listener pop3s { >> port = 995 >> ssl = yes >> } >> } >> ssl_cert = > ssl_key = > userdb { >> args = blocking=yes >> driver = passwd >> } >> protocol imap { > process_limit = 1024 <---------- (and bigger for pop3 but pop3 is > more popular here) > >> mail_max_userip_connections = 50 >> } > > service anvil { > client_limit = 2251 > } > > > >> protocol lda { >> mail_plugins = sieve >> } >> >> >> -- >> C. J. Keist Email: cj.keist at colostate.edu >> Systems Group Manager Solaris 10 OS (SAI) >> Engineering Network Services Phone: 970-491-0630 >> College of Engineering, CSU Fax: 970-491-5569 >> Ft. Collins, CO 80523-1301 >> >> All I want is a chance to prove 'Money can't buy happiness' >> -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From iain.hallam at bristol.ac.uk Fri Jul 11 14:10:10 2014 From: iain.hallam at bristol.ac.uk (Iain Hallam) Date: Fri, 11 Jul 2014 15:10:10 +0100 Subject: 1.2.4 disk full errors Message-ID: Hi. A user on a rather old mail system we have filled their disk space, and Dovecot has started to give lots of errors in the logs about "Expunged message reappeared" and "Duplicate file entry". The user can only see a few new messages, not the 33,551 in their inbox. In the TODO file in the current source code[1], Timo notes that (line 147): maildir: out-of-disk-space failures apparently cause all kinds of problems, e.g. "Expunged message reappeared", "Duplicate file entry"? [1] http://hg.dovecot.org/dovecot-2.2/file/c55c660d6e9d/TODO Does anyone know what's happening with Dovecot here and how to recover so that this user can see mail again? Unforuntately we're on a very old version, 1.2.4. Though there is a plan for migrating to a newer platform, I need to get this user accessing email again rather more urgently. Thanks, Iain Hallam. From mcbdovecot at robuust.nl Fri Jul 11 14:59:41 2014 From: mcbdovecot at robuust.nl (Maarten Bezemer) Date: Fri, 11 Jul 2014 16:59:41 +0200 (CEST) Subject: 1.2.4 disk full errors In-Reply-To: References: Message-ID: On Fri, 11 Jul 2014, Iain Hallam wrote: > maildir: out-of-disk-space failures apparently cause all kinds of > problems, e.g. "Expunged message reappeared", "Duplicate file entry"? > > Does anyone know what's happening with Dovecot here and how to recover > so that this user can see mail again? Assuming you use Maildir format for storing this user's mails, based on your quote of the maildir todo message... If you manage to add extra disk space, and access to mail is more important than e.g. losing message flags etc., then I'd say you can remove the dovecot.index / cache files for the maildirs affected. These would be regenerated the next time dovecot accesses the maildir. Could take a while tho, for that amount of mails.. HTH.. -- Maarten From tom at analytical-labs.com Fri Jul 11 16:05:48 2014 From: tom at analytical-labs.com (Tom Barber(Alabs)) Date: Fri, 11 Jul 2014 17:05:48 +0100 Subject: Replication on dovecot 2.0 Message-ID: <53C00B5C.80802@analytical-labs.com> Hi Guys I'm running an Ubuntu 12.04 LTS server and not being particually inclined to upgrade I'm wondering what options I have for replication as it appears to be running dovecot 2.0.19. I saw the wiki page about replication and whilst it says you should use 2.2+ it doesn't say what the minimum requirements are, so I tried doing what it says but I get: Fatal: Plugin 'replication' not found from directory /usr/lib/dovecot/modules Any ideas or tips. Thanks Tom From rs at sys4.de Fri Jul 11 16:13:06 2014 From: rs at sys4.de (Robert Schetterer) Date: Fri, 11 Jul 2014 18:13:06 +0200 Subject: Replication on dovecot 2.0 In-Reply-To: <53C00B5C.80802@analytical-labs.com> References: <53C00B5C.80802@analytical-labs.com> Message-ID: <53C00D12.8090906@sys4.de> Am 11.07.2014 18:05, schrieb Tom Barber(Alabs): > Hi Guys > > I'm running an Ubuntu 12.04 LTS server and not being particually > inclined to upgrade I'm wondering what options I have for replication as > it appears to be running dovecot 2.0.19. > > I saw the wiki page about replication and whilst it says you should use > 2.2+ it doesn't say what the minimum requirements are, so I tried doing > what it says but I get: > > Fatal: Plugin 'replication' not found from directory > /usr/lib/dovecot/modules > > Any ideas or tips. don t waste time go Ubuntu 14.04 LTS http://packages.ubuntu.com/trusty/dovecot-core vers 2.2.9 or recompile/install/upgrade yourself from http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages deb http://xi.rename-it.nl/debian/ testing-auto/dovecot-2.2 main https://sys4.de/de/blog/2013/06/17/dovecot-patching-mit-debian-und-ubuntu/ ( sorry german only ) > > Thanks > > Tom Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From tom at analytical-labs.com Fri Jul 11 16:15:29 2014 From: tom at analytical-labs.com (Tom Barber(Alabs)) Date: Fri, 11 Jul 2014 17:15:29 +0100 Subject: Replication on dovecot 2.0 In-Reply-To: <53C00D12.8090906@sys4.de> References: <53C00B5C.80802@analytical-labs.com> <53C00D12.8090906@sys4.de> Message-ID: <53C00DA1.6010304@analytical-labs.com> Fair enough, thanks :) On 11/07/14 17:13, Robert Schetterer wrote: > Am 11.07.2014 18:05, schrieb Tom Barber(Alabs): >> Hi Guys >> >> I'm running an Ubuntu 12.04 LTS server and not being particually >> inclined to upgrade I'm wondering what options I have for replication as >> it appears to be running dovecot 2.0.19. >> >> I saw the wiki page about replication and whilst it says you should use >> 2.2+ it doesn't say what the minimum requirements are, so I tried doing >> what it says but I get: >> >> Fatal: Plugin 'replication' not found from directory >> /usr/lib/dovecot/modules >> >> Any ideas or tips. > don t waste time go Ubuntu 14.04 LTS > > http://packages.ubuntu.com/trusty/dovecot-core > vers 2.2.9 > > or recompile/install/upgrade yourself from > > http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages > deb http://xi.rename-it.nl/debian/ testing-auto/dovecot-2.2 main > > https://sys4.de/de/blog/2013/06/17/dovecot-patching-mit-debian-und-ubuntu/ > ( sorry german only ) > >> Thanks >> >> Tom > > > Best Regards > MfG Robert Schetterer > From tss at iki.fi Fri Jul 11 23:40:00 2014 From: tss at iki.fi (Timo Sirainen) Date: Sat, 12 Jul 2014 02:40:00 +0300 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53BEDC61.4060706@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> Message-ID: <71984EBD-3257-455D-9502-740CA9DB248E@iki.fi> Find the first error/warning that Dovecot logs, which should happen just before you reach the limit. On 10.7.2014, at 21.33, CJ Keist wrote: > It's not fixed. Now the limit looks to be around 500 processes and we start to get number of connections exceeded. Any ideas? > > > > On 7/10/14, 10:35 AM, CJ Keist wrote: >> I fixed this issue about the process limit in the 10-master.conf file: >> >> default_process_limit = 5000 >> default_client_limit = 30000 >> >> >> On 7/10/14, 10:03 AM, CJ Keist wrote: >>> It looks like on the system that once we hit around 200 imap processes >>> it stops there and no more imap processes can be created. Is there a >>> number of max imap processes in the config file somewhere. By the way >>> running on OmniOS: >>> >>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>> >>> >>> >>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>> Thanks for the reply. I have seen threads about setting the >>>> mail_max_userip_connections, I have set this to 5000 and still people >>>> getting the exceeding connections errorl >>>> >>>> >>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>> # OS: SunOS 5.11 i86pc >>>> auth_failure_delay = 5 secs >>>> auth_mechanisms = plain login cram-md5 >>>> auth_worker_max_count = 3000 >>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>> disable_plaintext_auth = no >>>> hostname = mail2.engr.colostate.edu >>>> managesieve_notify_capability = mailto >>>> managesieve_sieve_capability = fileinto reject envelope >>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>> relational regex imap4flags copy include variables body enotify >>>> environment mailbox date ihave duplicate >>>> namespace inbox { >>>> inbox = yes >>>> location = >>>> mailbox Drafts { >>>> special_use = \Drafts >>>> } >>>> mailbox Junk { >>>> special_use = \Junk >>>> } >>>> mailbox Sent { >>>> special_use = \Sent >>>> } >>>> mailbox "Sent Messages" { >>>> special_use = \Sent >>>> } >>>> mailbox Trash { >>>> special_use = \Trash >>>> } >>>> prefix = >>>> } >>>> passdb { >>>> driver = pam >>>> } >>>> passdb { >>>> driver = passwd >>>> } >>>> postmaster_address = cjay at engr.colostate.edu >>>> service auth { >>>> unix_listener /var/lib/postfix/private/auth { >>>> mode = 0666 >>>> } >>>> unix_listener auth-userdb { >>>> group = postfix >>>> mode = 0666 >>>> user = postfix >>>> } >>>> user = root >>>> } >>>> service imap-login { >>>> inet_listener imap { >>>> port = 143 >>>> } >>>> inet_listener imaps { >>>> port = 993 >>>> ssl = yes >>>> } >>>> } >>>> service pop3-login { >>>> inet_listener pop3 { >>>> port = 110 >>>> } >>>> inet_listener pop3s { >>>> port = 995 >>>> ssl = yes >>>> } >>>> } >>>> ssl_cert = >>> ssl_key = >>> userdb { >>>> args = blocking=yes >>>> driver = passwd >>>> } >>>> protocol imap { >>>> mail_max_userip_connections = 5000 >>>> } >>>> protocol lda { >>>> mail_plugins = sieve >>>> } >>>> >>>> >>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>> >>>>> >>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>> Another problem is people are getting error message from their >>>>>> clients stating >>>>>> they have exceeded their number of connections. >>>>> >>>>> mail_max_userip_connections = 50 >>>>> >>>>> well, how much folders do the have >>>>> >>>>> keep in mind that fpr IDLE you have one connection per user and folder >>>>> 10 users with 10 folders behind the same NAT router are 100 connections >>>>> from the same IP >>>>> >>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>> Added info: These errors seem to come from users using mbox format. >>>>>>> >>>>>>> >>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>> All, >>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>> postfix >>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>> connections to >>>>>>>> the mail server. >>>>>>>> >>>>>>>> I've been able to google this error but haven't found fix for this >>>>>>>> yet. >>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>> either. >>>>>>>> >>>>>>>> Any suggestions? >>>>>>>> >>>>>>>> Var adm message: >>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>> Fatal: >>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>> dumped >>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>> >>>>>>>> Here is config output: >>>>>>>> >>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>> auth_failure_delay = 5 secs >>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>> auth_worker_max_count = 300 >>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>> disable_plaintext_auth = no >>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>> managesieve_notify_capability = mailto >>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>> environment mailbox date ihave duplicate >>>>>>>> namespace inbox { >>>>>>>> inbox = yes >>>>>>>> location = >>>>>>>> mailbox Drafts { >>>>>>>> special_use = \Drafts >>>>>>>> } >>>>>>>> mailbox Junk { >>>>>>>> special_use = \Junk >>>>>>>> } >>>>>>>> mailbox Sent { >>>>>>>> special_use = \Sent >>>>>>>> } >>>>>>>> mailbox "Sent Messages" { >>>>>>>> special_use = \Sent >>>>>>>> } >>>>>>>> mailbox Trash { >>>>>>>> special_use = \Trash >>>>>>>> } >>>>>>>> prefix = >>>>>>>> } >>>>>>>> passdb { >>>>>>>> driver = pam >>>>>>>> } >>>>>>>> passdb { >>>>>>>> driver = passwd >>>>>>>> } >>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>> service auth { >>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>> mode = 0666 >>>>>>>> } >>>>>>>> unix_listener auth-userdb { >>>>>>>> group = postfix >>>>>>>> mode = 0666 >>>>>>>> user = postfix >>>>>>>> } >>>>>>>> user = root >>>>>>>> } >>>>>>>> service imap-login { >>>>>>>> inet_listener imap { >>>>>>>> port = 143 >>>>>>>> } >>>>>>>> inet_listener imaps { >>>>>>>> port = 993 >>>>>>>> ssl = yes >>>>>>>> } >>>>>>>> } >>>>>>>> service pop3-login { >>>>>>>> inet_listener pop3 { >>>>>>>> port = 110 >>>>>>>> } >>>>>>>> inet_listener pop3s { >>>>>>>> port = 995 >>>>>>>> ssl = yes >>>>>>>> } >>>>>>>> } >>>>>>>> ssl_cert = >>>>>>> ssl_key = >>>>>>> userdb { >>>>>>>> args = blocking=yes >>>>>>>> driver = passwd >>>>>>>> } >>>>>>>> protocol imap { >>>>>>>> mail_max_userip_connections = 50 >>>>>>>> } >>>>>>>> protocol lda { >>>>>>>> mail_plugins = sieve >>>>>>>> } >>>>> >>>> >>> >> > > -- > C. J. Keist Email: cj.keist at colostate.edu > Systems Group Manager Solaris 10 OS (SAI) > Engineering Network Services Phone: 970-491-0630 > College of Engineering, CSU Fax: 970-491-5569 > Ft. Collins, CO 80523-1301 > > All I want is a chance to prove 'Money can't buy happiness' From lukashaase at gmx.at Sat Jul 12 00:45:42 2014 From: lukashaase at gmx.at (Lukas Haase) Date: Fri, 11 Jul 2014 17:45:42 -0700 Subject: BUG: Authentication client sent unknown handshake command In-Reply-To: <1217E34B-6648-4CF3-9226-813DFA42DD89@iki.fi> References: <1217E34B-6648-4CF3-9226-813DFA42DD89@iki.fi> Message-ID: Hi Timo, Thank you very much. I really appreciate your response! I have indeed a non-default socket config because I also let exim4 authenticate against it. So I I am not really able to remove the config. What makes me wonder is that the problem just appeared recently. I think I have the config running for 2 years now or so. I provide "doveconf -n" in any case, maybe you can spot an issue? Thanks, Luke # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-openvz-042stab090.2-amd64 i686 Debian 7.5 auth_mechanisms = plain login auth_verbose = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:~/Maildir mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave imapflags namespace { hidden = yes inbox = no list = no location = maildir:~/Maildir-root prefix = separator = . subscriptions = yes type = private } namespace { inbox = yes location = maildir:~/Maildir prefix = INBOX. separator = . subscriptions = yes type = private } namespace { hidden = no inbox = no list = yes location = maildir:/var/mail/public:INDEX=~/Maildir/public prefix = Public. separator = . subscriptions = no type = public } namespace { hidden = no inbox = no list = yes location = maildir:/var/mail/shared:INDEX=~/Maildir/shared:LAYOUT=fs prefix = Shared. separator = . subscriptions = no type = public } passdb { args = /etc/dovecot/%Ls.passwd driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = failure_show_msg=yes dovecotp driver = pam } plugin { acl = vfile sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +imapflags sieve_global_path = /etc/dovecot/default.sieve } protocols = sieve imap service auth { unix_listener auth-client { mode = 0666 } user = root } service imap-login { inet_listener imap { port = 0 } } service imap { executable = /usr/local/sbin/dovecot-imap-fix } ssl_ca = You have misconfigured Dovecot's auth sockets. Providing doveconf -n > output would help figuring out the problem. Or just delete all the > auth-related socket settings from config files and it should work. > > On 9.7.2014, at 0.03, Lukas Haase wrote: > >> May I gently "push" this? The string "BUG: Authentication client >> sent unknown handshake command" comes from dovecot (presumably it's >> in the source code) so I think it shouldn't be too mysterious >> what's happening here. >> >> Thank you, Luke >> >> On 2014-07-03 19:10, Lukas Haase wrote: >>> Hi, >>> >>> Some time ago my dovecot started to become BUGgy: Evertime I >>> restart the system, dovecot is started but I cannot login. I see >>> the following information in the logs: >>> >>> Jul 4 04:04:36 mail dovecot: auth: >>> passwd-file(user,127.11.91.218,): no passwd >>> file: /etc/dovecot/imap.passwd Jul 4 04:04:36 mail dovecot: >>> auth: Error: BUG: Authentication client sent unknown handshake >>> command: >>> REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa Jul >>> 4 04:04:36 mail dovecot: imap: Error: Authentication server >>> didn't send valid SPID as expected: MECH#011PLAIN#011plaintext >>> Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from >>> auth server, aborting (client-pid=20438 client-id=1) Jul 4 >>> 04:04:36 mail dovecot: imap-login: Internal login failure >>> (pid=20438 id=1) (internal failure, 1 succesful auths): >>> user=, method=PLAIN, rip=127.11.91.218, lip=73.82.101.172, >>> mpid=20439, TLS, session= >>> >>> It does not help to restart the client. But when I then restart >>> the server service dovecot restart it works again. >>> >>> But this is very dangerous because the server might reboot and I >>> might not immideately have the chance to restart dovecot >>> manually. >>> >>> What's going on here? >>> >>> mail:/# uname -a Linux mail 2.6.32-openvz-042stab090.2-amd64 #1 >>> SMP Sat Jun 21 00:22:42 MSK 2014 i686 GNU/Linux mail:/# dovecot >>> --version 2.1.7 >>> >>> Thanks, Luke >>> > From HFlor at gmx.de Sat Jul 12 06:43:29 2014 From: HFlor at gmx.de (Hardy Flor) Date: Sat, 12 Jul 2014 08:43:29 +0200 Subject: imap(hardy): Panic: file istream-tee.c: line 138 (i_stream_tee_read): assertion failed: (last_high_offset == input->v_offset + size) In-Reply-To: References: <53B5520E.8050304@gmx.de> <53B65EE4.9060002@gmx.de> Message-ID: <53C0D911.1090901@gmx.de> Am 04.07.2014 14:34, schrieb Timo Sirainen: > On 4.7.2014, at 10.59, Hardy Flor wrote: > >> Dovecot version is 2.2.13-auto+84 >> >> >> Am 03.07.2014 17:47, schrieb Timo Sirainen: >>> On 3.7.2014, at 15.52, Hardy Flor wrote: >>> >>>> I'm copy with imapsync (on the new server with dovecot) with a single user all mails from a old server to the new server. >>>> >>>> The error-message ist after 20-30 minutes in the log, and I must restart the imapsync. The next mail is normal store on the destination box. >>> What Dovecot version? Can you get a gdb backtrace? http://dovecot.org/bugreport.html >> > This should fix it: http://hg.dovecot.org/dovecot-2.2/rev/dffc6dd2be0d Many thanks, with the change it worked. From HFlor at gmx.de Sat Jul 12 06:46:02 2014 From: HFlor at gmx.de (Hardy Flor) Date: Sat, 12 Jul 2014 08:46:02 +0200 Subject: [Dovecot] mdbox-files over 2 MB In-Reply-To: <5326987F.3060403@gmx.de> References: <5326987F.3060403@gmx.de> Message-ID: <53C0D9AA.5050905@gmx.de> Am 17.03.2014 07:38, schrieb Hardy Flor: > Hello, > > I received an e-mail, this includes 9 forwarding, each with a file. > These files are not removed from the e-mail and stored in the > attachments-directory, although they are larger than 16 KB. For all > files the "Content-Transfer-Encoding: base64" is set. > The email is stored in completely in "m.00000034" > > ------------------------------------- doveconf: > > # 2.2.12: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 ext4 > mail_attachment_dir = /var/mail/attachments > mail_attachment_hash = %{md5} > mail_attachment_min_size = 16 k > mail_location = mdbox:/var/mail/user/%n > mdbox_rotate_interval = 1 weeks > mdbox_rotate_size = 2 M > > ------------------------------------- directory: > > root at xxx:/var/mail/user/xxx/storage# ls -al > ... > -rw------- 1 vmail mail 14433784 M?r 16 13:51 m.00000034 > ... Has this really not a solution? I've found some e-mails where the attachments are not stored separately. From slitt at troubleshooters.com Sat Jul 12 11:31:29 2014 From: slitt at troubleshooters.com (Steve Litt) Date: Sat, 12 Jul 2014 07:31:29 -0400 Subject: If local Dovecot stops working, check lo Message-ID: <20140712073129.0e208f57@mydesq2.domain.cxm> Hi all, You probably know this already, but just in case... Let's say you have your email client getting mail from a Dovecot server on the same computer (which is a really good way of doing things, by the way). Then one day your email client starts saying "connection refused" after a suitably long timeout. So then, to find out where things are getting stuck, you do the following command: openssl s_client -connect 127.0.0.1:993 -quiet And you don't even get an OK back. This means it's not your username or password, because you never even got that far. Before spending a lot of time doing diagnostic tests and narrowing it to the root cause, try this as root: ifdown lo ifup lo A malfunctioning lo will cause Dovecot not to connect to clients. My experience with Debian Wheezy is that lo "goes down" a lot, so this is one of the first things I do when odd stuff happens. HTH, SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance From h.reindl at thelounge.net Sat Jul 12 11:41:37 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Sat, 12 Jul 2014 13:41:37 +0200 Subject: If local Dovecot stops working, check lo In-Reply-To: <20140712073129.0e208f57@mydesq2.domain.cxm> References: <20140712073129.0e208f57@mydesq2.domain.cxm> Message-ID: <53C11EF1.6010908@thelounge.net> Am 12.07.2014 13:31, schrieb Steve Litt: > ifdown lo > ifup lo > > A malfunctioning lo will cause Dovecot not to connect to clients. My > experience with Debian Wheezy is that lo "goes down" a lot, so this is > one of the first things I do when odd stuff happens uhm if you *loopback device* goes down your machine has a serious problem - within 15 years Linux expierience i never faced a broken "lo" device and i guess the same for 99.9999% of all admins -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From patrickdk at patrickdk.com Sat Jul 12 23:54:46 2014 From: patrickdk at patrickdk.com (Patrick Domack) Date: Sat, 12 Jul 2014 19:54:46 -0400 Subject: Pigeonhole sieve misfile Message-ID: <20140712195446.Horde._-LHFL2nY4mSuby-Q0ZPrg3@mail.patrickdk.com> I'm having an issue with sieve putting some emails into the spam folder, that should not be matching the spam rule. I tried looking but can't seem to find a debug option. Is there any way I can get a log of what the sieve rule path that matches so I can locate the misfiring rule? or maybe something else that is going on. I already checked the dovecot sieve log file, and there is nothing in there. From michael at orlitzky.com Sun Jul 13 03:18:24 2014 From: michael at orlitzky.com (Michael Orlitzky) Date: Sat, 12 Jul 2014 23:18:24 -0400 Subject: macros In-Reply-To: <201407110959.58784.arekm@maven.pl> References: <201407110959.58784.arekm@maven.pl> Message-ID: <53C1FA80.6070504@orlitzky.com> On 07/11/2014 03:59 AM, Arkadiusz Mi?kiewicz wrote: > > Does dovecot support any form of macros? I would like to share configuration > file between several servers. Configs are different only in tiny aspects. > As a last resort, you can use `make` to accomplish this. dovecot-server.conf.sh ---------------------- id=55 something="SELECT FROM * WHERE something" mechanisms="digest-md5" dovecot-main.conf.sh -------------------- source ~/dovecot-server.conf.sh cat < $@ From stephan at rename-it.nl Sun Jul 13 06:27:36 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Sun, 13 Jul 2014 08:27:36 +0200 Subject: Pigeonhole sieve misfile In-Reply-To: <20140712195446.Horde._-LHFL2nY4mSuby-Q0ZPrg3@mail.patrickdk.com> References: <20140712195446.Horde._-LHFL2nY4mSuby-Q0ZPrg3@mail.patrickdk.com> Message-ID: <53C226D8.7040009@rename-it.nl> On 7/13/2014 1:54 AM, Patrick Domack wrote: > I'm having an issue with sieve putting some emails into the spam > folder, that should not be matching the spam rule. > > I tried looking but can't seem to find a debug option. > > Is there any way I can get a log of what the sieve rule path that > matches so I can locate the misfiring rule? or maybe something else > that is going on. > > I already checked the dovecot sieve log file, and there is nothing in > there. Use the sieve-test tool. Regards, Stephan. From wdgarc88 at gmail.com Sun Jul 13 06:55:41 2014 From: wdgarc88 at gmail.com (Edwardo Garcia) Date: Sun, 13 Jul 2014 16:55:41 +1000 Subject: High user number tune Message-ID: Halo, This might seem like another indirect thread. I Monday started new job, first task must replace courier. The job use POP3. and IMAP only for webmail, but must server support 4K POP3 at one times. I see from similar thread current settings not adequate , we will use TLS and if wiki read right Iprotocol So am close in think that need ? service pop3-login { process_limit = 4096 } service pop3 { process_limit = 4096 } service imap-login { process_limit = 2048 } service imap { process_limit = 2048 } then we have service managesieve { process_limit = 1024 } is that all we need change? I see in other thread someone says service anvil but I can not find out about it, does need change as well ? Why is it so complicated to change to let more user on, most other change one setting, dovecot want dozen :( From bourek at thinline.cz Sun Jul 13 10:07:54 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Sun, 13 Jul 2014 12:07:54 +0200 Subject: High user number tune In-Reply-To: References: Message-ID: <53C25A7A.3070107@thinline.cz> On 13.7.2014 08:55, Edwardo Garcia wrote: > Halo, > This might seem like another indirect thread. > I Monday started new job, first task must replace courier. The job use > POP3. and IMAP only for webmail, but must server support 4K POP3 at one > times. I see from similar thread current settings not adequate , we will > use TLS and if wiki read right Iprotocol > > So am close in think that need ? > > service pop3-login { > process_limit = 4096 > } > service pop3 { > process_limit = 4096 > } > > service imap-login { > process_limit = 2048 > } > service imap { > process_limit = 2048 > } > > then we have > service managesieve { > process_limit = 1024 > } > > is that all we need change? I see in other thread someone says service > anvil but I can not find out about it, does need change as well ? > Why is it so complicated to change to let more user on, most other change > one setting, dovecot want dozen :( > http://wiki2.dovecot.org/Services http://wiki2.dovecot.org/Design/Processes You will most likely need to change client_limit for processes anvil and auth. If you have some sort of testing environment, you can start Dovecot and check its logs - I'm not quite sure but I think it will complain about service auth's client_limit being too low. After you fix that it'll complain about service anvil - in both cases with specific number you need to set. From Jochen.Bern at LINworks.de Sun Jul 13 15:09:43 2014 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Sun, 13 Jul 2014 17:09:43 +0200 Subject: If local Dovecot stops working, check lo In-Reply-To: <53C11EF1.6010908@thelounge.net> References: <20140712073129.0e208f57@mydesq2.domain.cxm> <53C11EF1.6010908@thelounge.net> Message-ID: <53C2A137.4090709@LINworks.de> On 07/12/2014 01:41 PM, Reindl Harald wrote: > Am 12.07.2014 13:31, schrieb Steve Litt: >> A malfunctioning lo will cause Dovecot not to connect to clients. My >> experience with Debian Wheezy is that lo "goes down" a lot, so this is >> one of the first things I do when odd stuff happens > > uhm if you *loopback device* goes down your machine has a serious > problem - within 15 years Linux expierience i never faced a broken > "lo" device and i guess the same for 99.9999% of all admins While I *am* part of those 99+%, I would like to point out that there *also* is a lot of stuff that is perfectly normal for run-of-the-mill network interfaces, but likely has never been tried by said 99+ with lo, either. In particular, the following possibilities come to my mind: 1. Flaky IPv6 support (which wouldn't affect "127.0.0.1" directly, but might cause frequent changes of lo to add/remove/repeat ::1) 2. New interface naming schemes (I note that while eth0 starts to appear under all sorts of fancy names, nonempty iptables rules still routinely do a "-i lo -j ACCEPT" name reference in filter/INPUT) 3. Taking ntpd's 127.127.x.y pseudo-IPs for clocks a tad too literally To sum it up - I think that you *do* want to try and nail a root cause there. Regards, J. Bern -- *NEU* - NEC IT-Infrastruktur-Produkte im : Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel From nick.z.edwards at gmail.com Sun Jul 13 22:24:36 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Mon, 14 Jul 2014 08:24:36 +1000 Subject: If local Dovecot stops working, check lo In-Reply-To: <20140712073129.0e208f57@mydesq2.domain.cxm> References: <20140712073129.0e208f57@mydesq2.domain.cxm> Message-ID: On 7/12/14, Steve Litt wrote: > experience with Debian Wheezy is that lo "goes down" a lot, so this is > one of the first things I do when odd stuff happens. > Use a better operating system then, I've used at work and home, suse, opensuse, rhel, centos, slackware and fedora, and never in my all my years of linux (I've used it since I was 14 and am mid twenties now) has loopback ever *gone away* unless i deliberately made it so. From bourek at thinline.cz Sun Jul 13 22:30:56 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Mon, 14 Jul 2014 00:30:56 +0200 Subject: If local Dovecot stops working, check lo In-Reply-To: References: <20140712073129.0e208f57@mydesq2.domain.cxm> Message-ID: <53C308A0.1020501@thinline.cz> On 14.7.2014 00:24, Nick Edwards wrote: > On 7/12/14, Steve Litt wrote: > >> experience with Debian Wheezy is that lo "goes down" a lot, so this is >> one of the first things I do when odd stuff happens. >> > > Use a better operating system then Blaming operating system after *one* person reports something strange about it seems a bit overboard, doesn't it...? From sven at svenhartge.de Sun Jul 13 22:39:46 2014 From: sven at svenhartge.de (Sven Hartge) Date: Mon, 14 Jul 2014 00:39:46 +0200 Subject: If local Dovecot stops working, check lo References: <20140712073129.0e208f57@mydesq2.domain.cxm> Message-ID: <5ar1mm527rv8@mids.svenhartge.de> Nick Edwards wrote: > On 7/12/14, Steve Litt wrote: >> experience with Debian Wheezy is that lo "goes down" a lot, so this >> is one of the first things I do when odd stuff happens. > Use a better operating system then, I've used at work and home, suse, > opensuse, rhel, centos, slackware and fedora, and never in my all my > years of linux (I've used it since I was 14 and am mid twenties now) > has loopback ever *gone away* unless i deliberately made it so. And the same goes for Debian. I have never in the last 16 years "lost" a loopback device out of the blue. If your lo "goes down" a lot, then there is something suspicious at foot and this need to be investigated. This is not normal Debian behavior. Gr??e, Sven. -- Sigmentation fault. Core dumped. From HFlor at gmx.de Mon Jul 14 07:58:08 2014 From: HFlor at gmx.de (Hardy Flor) Date: Mon, 14 Jul 2014 09:58:08 +0200 Subject: Panic: file mail-index.c: line 650 (mail_index_close): assertion failed: (index->open_count > 0) Message-ID: <53C38D90.4000001@gmx.de> Hello, I'm use the virtual plugin for list all unread messages in the public namespace. Every time the connection is terminated with this error message when I select the virtual/projekte mailbox. Do not show any emails. The version is build today from source 2.2.13.auto+102 Hardy *** dovecot-virtual *** !INBOX Projekte/* unseen ********************** *** part of dovecot -n *** # 2.2.13 (fd0616d553b0): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.5 ext4 namespace { list = children location = mdbox:/var/mail/projekte/:INDEXPVT=/var/mail/user/%n/projekte prefix = Projekte/ separator = / subscriptions = no type = public } ************************* GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/lib/dovecot/imap...(no debugging symbols found)...done. Attaching to program: /usr/lib/dovecot/imap, process 6839 ptrace: Kein passender Prozess gefunden. [New LWP 6839] warning: Can't read pathname for load map: Eingabe-/Ausgabefehler. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/imap imap-postlogin'. Program terminated with signal 6, Aborted. #0 0x00007f38fc37c475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007f38fc37c475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f38fc37f6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x00007f38fc742395 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00007f38fc7423fe in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00007f38fc6fa96e in i_panic () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x00007f38fca6a1e1 in mail_index_close () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #6 0x00007f38fca5c46c in index_storage_mailbox_close () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #7 0x00007f38fca2fb8d in mailbox_close () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #8 0x00007f38fb0f600d in ?? () from /usr/lib/dovecot/modules/lib20_virtual_plugin.so No symbol table info available. #9 0x00007f38fb0f61b0 in virtual_backend_box_open () from /usr/lib/dovecot/modules/lib20_virtual_plugin.so No symbol table info available. #10 0x00007f38fb0f7860 in virtual_storage_sync_init () from /usr/lib/dovecot/modules/lib20_virtual_plugin.so No symbol table info available. #11 0x00007f38fca30703 in mailbox_sync_init () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #12 0x00007f38fca30827 in mailbox_sync () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #13 0x00007f38fca5afd0 in index_storage_get_status () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #14 0x00007f38fb0f5458 in ?? () from /usr/lib/dovecot/modules/lib20_virtual_plugin.so No symbol table info available. #15 0x00007f38fbb1b794 in ?? () from /usr/lib/dovecot/modules/lib01_acl_plugin.so No symbol table info available. #16 0x00007f38fca31a30 in mailbox_get_status () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #17 0x000000000041eb4b in imap_status_get () No symbol table info available. #18 0x0000000000414329 in cmd_status () No symbol table info available. #19 0x000000000041849c in command_exec () No symbol table info available. #20 0x00000000004174e0 in ?? () No symbol table info available. #21 0x0000000000417574 in ?? () No symbol table info available. ---Type to continue, or q to quit--- #22 0x0000000000417855 in client_handle_input () No symbol table info available. #23 0x0000000000417c02 in client_input () No symbol table info available. #24 0x00007f38fc7538be in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #25 0x00007f38fc7548cb in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #26 0x00007f38fc753949 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #27 0x00007f38fc7539c8 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #28 0x00007f38fc6ffe13 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #29 0x000000000040c238 in main () No symbol table info available. (gdb) From fumiyas at osstech.jp Mon Jul 14 10:42:10 2014 From: fumiyas at osstech.jp (SATOH Fumiyasu) Date: Mon, 14 Jul 2014 19:42:10 +0900 Subject: doveadm-server does NOT know fts commands Message-ID: <87wqbgkyrh.wl%fumiyas@osstech.jp> Hi, I'm using Dovecot 2.2.13 with Dovecot Director, Doveadm server and FTS. I want to run doveadm on Director hosts, but Dovecot server on backend hosts reject "fts *" commands. On Dovecot Director hosts: # doveadm fts optimize -u u0001 at example.jp # echo $? 75 # doveadm fts rescan -u u0001 at example.jp # echo $? 75 doveadm index -u u0001 at example.jp INBOX # echo $? 0 On Dovecot backend hosts: # grep doveadm /var/log/maillog Jul 14 10:25:40 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts optimize Jul 14 10:25:51 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts rescan Is this doveadm-server restriction? On Dovecot backend hosts (2): # doveadm fts optimize -u u0001 at example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm fts rescan -u u0001 at example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm index -u u0001 at example.jp -S /var/run/dovecot/doveadm-server INBOX # echo $? 0 # doveadm fts optimize -u u0001 at example.jp # echo $? 0 # doveadm fts rescan -u u0001 at example.jp # echo $? 0 # doveadm index -u u0001 at example.jp INBOX # echo $? 0 -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA From THerrmann at ADwin.de Mon Jul 14 13:14:06 2014 From: THerrmann at ADwin.de (Thomas Herrmann) Date: Mon, 14 Jul 2014 15:14:06 +0200 Subject: Flags in public folders disappear when more than 25 flags are used In-Reply-To: <7EFAF990-6348-42AA-9956-71E2D0A73A14@iki.fi> References: <53B41677.6080300@ADwin.de> <53BC07CA.5060106@ADwin.de> <53BE62E2.7060708@ADwin.de> <7EFAF990-6348-42AA-9956-71E2D0A73A14@iki.fi> Message-ID: <53C3D79E.4010802@ADwin.de> On 07/10/2014 05:37 PM, Timo Sirainen wrote: >> Maybe this happens because I am using 2.2.* with INDEX instead of >> INDEXPVT, > > Right. Confirmed; I set up a testbed (2.2.13), and I have observed this: - when using public folders with per-user seen flags (using INDEX), only the first 25 keywords are shared, the other keywords are per-user. - the problem disappears when using INDEXPVT instead of INDEX >> so now my question is, how do I upgrade from INDEX to INDEXPVT >> without losing information? Will dovecot convert the old files >> automatically? I did not find anything about that at > > I think it would work if you simply change INDEX -> INDEXPVT, but test first with some test users. Switching from INDEX to INDEXPVT keeps the first 25 keywords, and dumps the others (which is ok since they were not in sync anyways). However, switching to INDEXPVT also lost the SEEN status for _some_ users. Any idea how to prevent that? Will corrupted dovecot.index/log/cache files in the future automatically lead to a partial loss of keywords? I have been using and upgrading dovecot for quite a while now, and deleting cache files was often my first step when unexpected behaviour or strange log entries occurred... Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4246 bytes Desc: S/MIME Cryptographic Signature URL: From THerrmann at ADwin.de Mon Jul 14 13:43:27 2014 From: THerrmann at ADwin.de (Thomas Herrmann) Date: Mon, 14 Jul 2014 15:43:27 +0200 Subject: doveadm dump ignores .pvt Message-ID: <53C3DE7F.6010806@ADwin.de> While debugging a different problem, I used "doveadm dump" to show information about a maildir folder; it happily reported values from dovecot.index and dovecot.index.log (confirmed by strace): [...] messages count ........... = 978 seen messages count ...... = 967 [...] However, mail clients reported different values, I guess because the Seen flags were actually stored in the dovecot.index.pvt.log files. Is this a known problem or a result of my (maybe unsupported?) setup? My public maildir folder contains only links to mailboxes of the private maildir of the mail admin, i.e.: /home/vmail/public/.Info -> ../adwin.de/mail-admin/Maildir/.Info namespace { list = children location = maildir:/home/vmail/public:INDEXPVT=/home/vmail/adwin.de/%n/public prefix = ADwin/ separator = / subscriptions = no type = public } My setups leads to .pvt-files in the public namespace, could this be a problem? http://wiki2.dovecot.org/SharedMailboxes/Symlinks explicitly states that symlinking _should_ work. Using version 2.2.13 (debian packages). Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4246 bytes Desc: S/MIME Cryptographic Signature URL: From claus.r at bayern-mail.de Mon Jul 14 14:04:02 2014 From: claus.r at bayern-mail.de (claus) Date: Mon, 14 Jul 2014 16:04:02 +0200 Subject: protocol specific AuthDatabase Queries Message-ID: Hi, i have to configure different sql-queries for protocol lmtp, another for protocol smtp and one query for other protocols. I have configured in "/etc/dovecot/conf.d/auth-sql.conf.ext" one entry for all protocols and 2 protocol specific entries: protocol lmtp { passdb { driver = sql args = /etc/dovecot/dovecot-lmtp-sql.conf.ext } } protocol smtp { passdb { driver = sql args = /etc/dovecot/dovecot-smtp-sql.conf.ext } } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } is this correct or do i have to configure all possible protocols seperately? First i had a working configuration for all protocols except for lmtp (but now i need additionally a special query for smtp): protocol !lmtp { .. } protocol lmtp { .. } Can you tell me whats the prefered configuration? Thanks Claus From patrickdk at patrickdk.com Mon Jul 14 16:05:35 2014 From: patrickdk at patrickdk.com (Patrick Domack) Date: Mon, 14 Jul 2014 12:05:35 -0400 Subject: OOM in Dovecot 2.2.13 imap In-Reply-To: <03C1B098-999F-4FC2-B6CF-987EBC7219DB@iki.fi> References: <607573E0-17A3-4044-8079-11A2F96C7844@iki.fi> <03C1B098-999F-4FC2-B6CF-987EBC7219DB@iki.fi> Message-ID: <20140714120535.Horde.8Su3ChU7VyBI2ypXJsP9mQ9@mail.patrickdk.com> Just as a random follow up for other people that might google this. I also started to have this issue. I tried the two patches but they didn't help. I came to find out, this can also be caused from a disk full issue, atleast when using maildir. Quoting Timo Sirainen : > Actually, I think these fix it: > > http://hg.dovecot.org/dovecot-2.2/rev/5740cb57d02c > http://hg.dovecot.org/dovecot-2.2/rev/00b3aa3842b7 > > On 3.7.2014, at 21.28, Timo Sirainen wrote: > >> On 23.6.2014, at 15.18, Bernhard Schmidt wrote: >> >>> we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes. >>> We have two users that repeatedly trigger an OOM condition with IMAP. >>> >>> Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal: >>> pool_system_realloc(268435456): Out of memory >> .. >>> #6 0x00007f11766e6cda in o_stream_grow_buffer >>> (fstream=fstream at entry=0x7f11789f41c0, bytes=) at >>> ostream-file.c:440 >>> size = 268435456 >>> new_size = >>> end_size = >> .. >>> #11 0x00007f1175692849 in o_stream_zlib_send_outbuf >>> (zstream=0x7f11789f9340) at ostream-zlib.c:94 >>> ret = >>> size = 12113 >>> #12 0x00007f1175692982 in o_stream_zlib_send_flush >>> (zstream=zstream at entry=0x7f11789f9340, final=final at entry=true) at >>> ostream-zlib.c:189 >> >> This is most likely because of the IMAP COMPRESS extension, which >> causes the output stream buffer to get really large. So the easiest >> fix would be to just disable imap_zlib plugin and it'll probably >> work. But this should get fixed properly.. I just can't figure out >> how this can happen. What was the IMAP client doing that caused it? >> Could you run a few more gdb commands: >> >>> #17 0x00007f1176e8d269 in client_output (client=0x7f11789f4470) at >>> imap-client.c:1019 >> >> Assuming client_output is again in frame 17, run: >> >> f 17 >> p *client.command_queue >> p *client.command_queue.next From ihab_mishriki at hotmail.com Mon Jul 14 16:49:04 2014 From: ihab_mishriki at hotmail.com (ihab) Date: Mon, 14 Jul 2014 09:49:04 -0700 (PDT) Subject: how many connection by pop3 ? Message-ID: <1405356544110-48876.post@n4.nabble.com> how many connection by pop3 ? Thanks, Best regrades, -- View this message in context: http://dovecot.2317879.n4.nabble.com/how-many-connection-by-pop3-tp48876.html Sent from the Dovecot mailing list archive at Nabble.com. From h.reindl at thelounge.net Mon Jul 14 17:15:42 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 14 Jul 2014 19:15:42 +0200 Subject: how many connection by pop3 ? In-Reply-To: <1405356544110-48876.post@n4.nabble.com> References: <1405356544110-48876.post@n4.nabble.com> Message-ID: <53C4103E.3090404@thelounge.net> Am 14.07.2014 18:49, schrieb ihab: > how many connection by pop3? what is that for question? that many users are connected and you allow process_limit = process_min_avail = service_count = -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From rs at sys4.de Mon Jul 14 17:22:32 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 14 Jul 2014 19:22:32 +0200 Subject: how many connection by pop3 ? In-Reply-To: <1405356544110-48876.post@n4.nabble.com> References: <1405356544110-48876.post@n4.nabble.com> Message-ID: <53C411D8.9090001@sys4.de> Am 14.07.2014 18:49, schrieb ihab: > how many connection by pop3 ? my top score is about at 1000 pop3 logins per minute , if you liked to know that > > Thanks, > Best regrades, > > > > > -- > View this message in context: http://dovecot.2317879.n4.nabble.com/how-many-connection-by-pop3-tp48876.html > Sent from the Dovecot mailing list archive at Nabble.com. > Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From me at junc.eu Mon Jul 14 17:39:07 2014 From: me at junc.eu (Benny Pedersen) Date: Mon, 14 Jul 2014 19:39:07 +0200 Subject: how many connection by pop3 =?UTF-8?Q?=3F?= In-Reply-To: <1405356544110-48876.post@n4.nabble.com> References: <1405356544110-48876.post@n4.nabble.com> Message-ID: ihab skrev den 2014-07-14 18:49: > how many connection by pop3 ? how would the lotto numbers look like next week ? From cj.keist at colostate.edu Mon Jul 14 19:10:00 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Mon, 14 Jul 2014 13:10:00 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <71984EBD-3257-455D-9502-740CA9DB248E@iki.fi> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <71984EBD-3257-455D-9502-740CA9DB248E@iki.fi> Message-ID: <53C42B08.7020106@colostate.edu> Here are the log entires just before the signal 6 error: Jul 10 00:19:56 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/DailySmarts/dovecot.index: CPU architecture changed Jul 10 00:19:58 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/engr101/dovecot.index: CPU architecture changed Jul 10 00:19:59 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/INTO/dovecot.index: CPU architecture changed Jul 10 00:19:59 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/Drafts/dovecot.index: CPU architecture changed Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Index /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index: Lost log for seq=1 offset=0 Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.warning] imap(tjs): Warning: fscking index file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Fixed index file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index: log_file_seq 1 -> 33554432 Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Corrupted transaction log file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/FundingOpportunities/dovecot.index.log seq 33554432: log file shrank (1124 < 6144) (sync_offset=6144) Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Raw backtrace: /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'default_fatal_finish+0x51 [0xfede0f41] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'i_internal_fatal_handler+0x31 [0xfede1071] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'i_fatal+0x0 [0xfee0c4e2] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'0x6d595 [0xfeddd595] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_file_add_to_list+0x9c [0xfef3f5cc] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_file_open+0x25c [0xfef401dc] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_open+0xda [0xfef3bdba] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_index_open_files+0x23 [0xfef239e3] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0' Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Fatal: master: service(imap): child 2238 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Jul 10 00:20:01 mail2 dovecot: [ID 583609 mail.info] imap-login: Login: user=, method=PLAIN, rip=129.82.226.98, lip=129.82.20.15, mpid=2943, TLS, session= Jul 10 00:20:01 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Transaction log file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/FundingOpportunities/dovecot.index.log: marked corrupted On 7/11/14, 5:40 PM, Timo Sirainen wrote: > Find the first error/warning that Dovecot logs, which should happen just before you reach the limit. > > On 10.7.2014, at 21.33, CJ Keist wrote: > >> It's not fixed. Now the limit looks to be around 500 processes and we start to get number of connections exceeded. Any ideas? >> >> >> >> On 7/10/14, 10:35 AM, CJ Keist wrote: >>> I fixed this issue about the process limit in the 10-master.conf file: >>> >>> default_process_limit = 5000 >>> default_client_limit = 30000 >>> >>> >>> On 7/10/14, 10:03 AM, CJ Keist wrote: >>>> It looks like on the system that once we hit around 200 imap processes >>>> it stops there and no more imap processes can be created. Is there a >>>> number of max imap processes in the config file somewhere. By the way >>>> running on OmniOS: >>>> >>>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>>> >>>> >>>> >>>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>>> Thanks for the reply. I have seen threads about setting the >>>>> mail_max_userip_connections, I have set this to 5000 and still people >>>>> getting the exceeding connections errorl >>>>> >>>>> >>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>> # OS: SunOS 5.11 i86pc >>>>> auth_failure_delay = 5 secs >>>>> auth_mechanisms = plain login cram-md5 >>>>> auth_worker_max_count = 3000 >>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>> disable_plaintext_auth = no >>>>> hostname = mail2.engr.colostate.edu >>>>> managesieve_notify_capability = mailto >>>>> managesieve_sieve_capability = fileinto reject envelope >>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>> relational regex imap4flags copy include variables body enotify >>>>> environment mailbox date ihave duplicate >>>>> namespace inbox { >>>>> inbox = yes >>>>> location = >>>>> mailbox Drafts { >>>>> special_use = \Drafts >>>>> } >>>>> mailbox Junk { >>>>> special_use = \Junk >>>>> } >>>>> mailbox Sent { >>>>> special_use = \Sent >>>>> } >>>>> mailbox "Sent Messages" { >>>>> special_use = \Sent >>>>> } >>>>> mailbox Trash { >>>>> special_use = \Trash >>>>> } >>>>> prefix = >>>>> } >>>>> passdb { >>>>> driver = pam >>>>> } >>>>> passdb { >>>>> driver = passwd >>>>> } >>>>> postmaster_address = cjay at engr.colostate.edu >>>>> service auth { >>>>> unix_listener /var/lib/postfix/private/auth { >>>>> mode = 0666 >>>>> } >>>>> unix_listener auth-userdb { >>>>> group = postfix >>>>> mode = 0666 >>>>> user = postfix >>>>> } >>>>> user = root >>>>> } >>>>> service imap-login { >>>>> inet_listener imap { >>>>> port = 143 >>>>> } >>>>> inet_listener imaps { >>>>> port = 993 >>>>> ssl = yes >>>>> } >>>>> } >>>>> service pop3-login { >>>>> inet_listener pop3 { >>>>> port = 110 >>>>> } >>>>> inet_listener pop3s { >>>>> port = 995 >>>>> ssl = yes >>>>> } >>>>> } >>>>> ssl_cert = >>>> ssl_key = >>>> userdb { >>>>> args = blocking=yes >>>>> driver = passwd >>>>> } >>>>> protocol imap { >>>>> mail_max_userip_connections = 5000 >>>>> } >>>>> protocol lda { >>>>> mail_plugins = sieve >>>>> } >>>>> >>>>> >>>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>>> >>>>>> >>>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>>> Another problem is people are getting error message from their >>>>>>> clients stating >>>>>>> they have exceeded their number of connections. >>>>>> >>>>>> mail_max_userip_connections = 50 >>>>>> >>>>>> well, how much folders do the have >>>>>> >>>>>> keep in mind that fpr IDLE you have one connection per user and folder >>>>>> 10 users with 10 folders behind the same NAT router are 100 connections >>>>>> from the same IP >>>>>> >>>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>>> Added info: These errors seem to come from users using mbox format. >>>>>>>> >>>>>>>> >>>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>>> All, >>>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>>> postfix >>>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>>> connections to >>>>>>>>> the mail server. >>>>>>>>> >>>>>>>>> I've been able to google this error but haven't found fix for this >>>>>>>>> yet. >>>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>>> either. >>>>>>>>> >>>>>>>>> Any suggestions? >>>>>>>>> >>>>>>>>> Var adm message: >>>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>>> Fatal: >>>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>>> dumped >>>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>>> >>>>>>>>> Here is config output: >>>>>>>>> >>>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>>> auth_failure_delay = 5 secs >>>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>>> auth_worker_max_count = 300 >>>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>>> disable_plaintext_auth = no >>>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>>> managesieve_notify_capability = mailto >>>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>>> environment mailbox date ihave duplicate >>>>>>>>> namespace inbox { >>>>>>>>> inbox = yes >>>>>>>>> location = >>>>>>>>> mailbox Drafts { >>>>>>>>> special_use = \Drafts >>>>>>>>> } >>>>>>>>> mailbox Junk { >>>>>>>>> special_use = \Junk >>>>>>>>> } >>>>>>>>> mailbox Sent { >>>>>>>>> special_use = \Sent >>>>>>>>> } >>>>>>>>> mailbox "Sent Messages" { >>>>>>>>> special_use = \Sent >>>>>>>>> } >>>>>>>>> mailbox Trash { >>>>>>>>> special_use = \Trash >>>>>>>>> } >>>>>>>>> prefix = >>>>>>>>> } >>>>>>>>> passdb { >>>>>>>>> driver = pam >>>>>>>>> } >>>>>>>>> passdb { >>>>>>>>> driver = passwd >>>>>>>>> } >>>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>>> service auth { >>>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>>> mode = 0666 >>>>>>>>> } >>>>>>>>> unix_listener auth-userdb { >>>>>>>>> group = postfix >>>>>>>>> mode = 0666 >>>>>>>>> user = postfix >>>>>>>>> } >>>>>>>>> user = root >>>>>>>>> } >>>>>>>>> service imap-login { >>>>>>>>> inet_listener imap { >>>>>>>>> port = 143 >>>>>>>>> } >>>>>>>>> inet_listener imaps { >>>>>>>>> port = 993 >>>>>>>>> ssl = yes >>>>>>>>> } >>>>>>>>> } >>>>>>>>> service pop3-login { >>>>>>>>> inet_listener pop3 { >>>>>>>>> port = 110 >>>>>>>>> } >>>>>>>>> inet_listener pop3s { >>>>>>>>> port = 995 >>>>>>>>> ssl = yes >>>>>>>>> } >>>>>>>>> } >>>>>>>>> ssl_cert = >>>>>>>> ssl_key = >>>>>>>> userdb { >>>>>>>>> args = blocking=yes >>>>>>>>> driver = passwd >>>>>>>>> } >>>>>>>>> protocol imap { >>>>>>>>> mail_max_userip_connections = 50 >>>>>>>>> } >>>>>>>>> protocol lda { >>>>>>>>> mail_plugins = sieve >>>>>>>>> } >>>>>> >>>>> >>>> >>> >> >> -- >> C. J. Keist Email: cj.keist at colostate.edu >> Systems Group Manager Solaris 10 OS (SAI) >> Engineering Network Services Phone: 970-491-0630 >> College of Engineering, CSU Fax: 970-491-5569 >> Ft. Collins, CO 80523-1301 >> >> All I want is a chance to prove 'Money can't buy happiness' -- C. J. Keist Email: cj.keist at colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' From iavor at icdsoft.com Mon Jul 14 20:05:23 2014 From: iavor at icdsoft.com (Iavor Stoev) Date: Mon, 14 Jul 2014 23:05:23 +0300 Subject: Changed IMAP MOVE behavior in Dovecot 2.2.x Message-ID: <53C43803.1080101@icdsoft.com> Hello, After the migration to Dovecot 2.2.13 from Dovecot 2.1.17, I noticed a changed behavior when I move a message from one folder to another. I use Thunderbird with: Account Settings -> Server Settings -> When I delete a message: Just mark it as deleted. I use Thunderbird 24.6.0 with IMAP. With Dovecot 2.1.x when I move a message, the message appears in the new folder and is marked for deletion in the original folder (which gives me an easy option to undo the action if I made a mistake until I choose to Compact/Purge the folder). With Dovecot 2.2.x when I move the a message it is marked for deletion and is AUTO Compacted/Purged immediately. Is there a way to achieve the 2.1.x behavior with Dovecot 2.2.x? Thank you Iavor From wegge at wegge.dk Mon Jul 14 20:22:15 2014 From: wegge at wegge.dk (Anders Wegge Keller) Date: 14 Jul 2014 22:22:15 +0200 Subject: Transition from one server to another. Message-ID: <87zjgbadxk.fsf@huddi.jernurt.dk> A frind of mine and I are running a dedicated server, that among other things host mail for ourselves and friends and families. All in all about 15 different domains with 35-40 users. The machine in question is old, so we are doing a slow transition from the old server to the new one. So far, we've managed to move web hosts seamlessly. Due to the technical capabilities at some of the user base, it would be nice to get to a setup, where we can move individual users imaps from the old server to the new one, as we get the time to visit them. I have an idea how such a transition could go: 1. Upgrade the old dovecot 1.2.15 to 2.1.whateveritis from debian squeeze backports. 2. Set dsync up to replicate mails from the old server to the new server. I know that 2.2 is recommended, but with a limited amount of user, I'm willing to take a performance hit. 3. Migrate my parents &c to use the new server. 4. When all users have been moved on to using the new server, upgrade MX records for the domain to point at the new server. 5. When all MX records are updated, decalre success. Is this feasible, and what would the risks be. For instance, during step 4, mails are bound to arrive at bothe the old and new server for some time. Will this cause problems? Is there a simpler solution to the problem? -- /Wegge Leder efter redundant peering af dk.*,linux.debian.* From rs at sys4.de Mon Jul 14 20:23:02 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 14 Jul 2014 22:23:02 +0200 Subject: Changed IMAP MOVE behavior in Dovecot 2.2.x In-Reply-To: <53C43803.1080101@icdsoft.com> References: <53C43803.1080101@icdsoft.com> Message-ID: <53C43C26.6000000@sys4.de> Am 14.07.2014 22:05, schrieb Iavor Stoev: > Hello, > > After the migration to Dovecot 2.2.13 from Dovecot 2.1.17, > I noticed a changed behavior when I move a message from one folder to > another. I use Thunderbird with: Account Settings -> Server Settings -> > When I delete a message: Just mark it as deleted. > > I use Thunderbird 24.6.0 with IMAP. > > With Dovecot 2.1.x when I move a message, the message appears in the new > folder and is marked for deletion in the original folder (which gives me > an easy option to undo the action if I made a mistake until I choose to > Compact/Purge the folder). > > With Dovecot 2.2.x when I move the a message it is marked for deletion > and is AUTO Compacted/Purged immediately. > > Is there a way to achieve the 2.1.x behavior with Dovecot 2.2.x? > > Thank you > > Iavor i am not sure dovecot version has big impact, show logs and configs http://wiki2.dovecot.org/Upgrading/2.2 please read http://kb.mozillazine.org/Thunderbird_:_Tips_:_Compacting_Folders Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From slusarz at curecanti.org Mon Jul 14 20:45:18 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Mon, 14 Jul 2014 14:45:18 -0600 Subject: Changed IMAP MOVE behavior in Dovecot 2.2.x In-Reply-To: <53C43803.1080101@icdsoft.com> Message-ID: <20140714144518.Horde.YkmZDMt8flj5eihYjh0A-A9@bigworm.curecanti.org> Quoting Iavor Stoev : > Hello, > > After the migration to Dovecot 2.2.13 from Dovecot 2.1.17, > I noticed a changed behavior when I move a message from one folder > to another. I use Thunderbird with: Account Settings -> Server > Settings -> When I delete a message: Just mark it as deleted. > > I use Thunderbird 24.6.0 with IMAP. > > With Dovecot 2.1.x when I move a message, the message appears in the > new folder and is marked for deletion in the original folder (which > gives me an easy option to undo the action if I made a mistake until > I choose to Compact/Purge the folder). > > With Dovecot 2.2.x when I move the a message it is marked for > deletion and is AUTO Compacted/Purged immediately. > > Is there a way to achieve the 2.1.x behavior with Dovecot 2.2.x? Dovecot 2.2 implemented the new IMAP MOVE extension, which Thunderbird is using. Short of manually removing MOVE from Dovecot's CAPABILITY listing, there's not much you can do since I don't think Thunderbird provides an easy way to alter the low-level IMAP interaction. The IMAP MOVE functionality is much preferred over your expected behavior since a COPY/STORE/EXPUNGE (how you must do a move without the MOVE extension) is not atomic and can leave the mailbox(es) in an inconsistent state. Leaving a copy of the message in the original mailbox, that requires manual deletion, is most definitely not what most users expect for a move, even given a liberal interpretation of "move", so you are describing a very non-standard way of accessing your mailboxes. michael From pettijohne at hotmail.com Mon Jul 14 21:10:39 2014 From: pettijohne at hotmail.com (Edgar Pettijohn) Date: Mon, 14 Jul 2014 16:10:39 -0500 Subject: Fatal: master: service(imap): child 20258 killed with, signal 6 (core not dumped - set service imap {, drop_priv_before_exec=yes }) (CJ Keist) In-Reply-To: References: Message-ID: Have you tried: 10-master.conf service imap { drop_priv_before_exec=yes } as suggested by the error? From ricardo at wenn.com Mon Jul 14 22:01:52 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Mon, 14 Jul 2014 23:01:52 +0100 Subject: Postfix user@domain splitting Message-ID: <53C45350.3080102@wenn.com> I have been trying looking though all the wiki documents to setup LMTP. It now seems to all be connected except that it keeps saying that the user is not recognised when postfix sends to LMTP, it sends the full recipent email address but seems that on the dovecot side it is unable to work with this. I have checked the userdb and made sure its using %n but alas it still does not work. Currently ive had to revert to using LDA as it works fine with that but i still dont know how as the postfix config variable $RECIPIENT is the full email address and does not seem to matter to LDA. From terry at dop.com Mon Jul 14 22:27:18 2014 From: terry at dop.com (Terry Barnum) Date: Mon, 14 Jul 2014 15:27:18 -0700 Subject: Transition from one server to another. In-Reply-To: <87zjgbadxk.fsf@huddi.jernurt.dk> References: <87zjgbadxk.fsf@huddi.jernurt.dk> Message-ID: On Jul 14, 2014, at 1:22 PM, Anders Wegge Keller wrote: > > A frind of mine and I are running a dedicated server, that among > other things host mail for ourselves and friends and families. All in > all about 15 different domains with 35-40 users. The machine in > question is old, so we are doing a slow transition from the old server > to the new one. So far, we've managed to move web hosts > seamlessly. Due to the technical capabilities at some of the user > base, it would be nice to get to a setup, where we can move individual > users imaps from the old server to the new one, as we get the time to > visit them. > > I have an idea how such a transition could go: > > 1. Upgrade the old dovecot 1.2.15 to 2.1.whateveritis from debian > squeeze backports. > > 2. Set dsync up to replicate mails from the old server to the new > server. I know that 2.2 is recommended, but with a limited amount > of user, I'm willing to take a performance hit. > > 3. Migrate my parents &c to use the new server. > > 4. When all users have been moved on to using the new server, upgrade > MX records for the domain to point at the new server. > > 5. When all MX records are updated, decalre success. > > > Is this feasible, and what would the risks be. For instance, during > step 4, mails are bound to arrive at bothe the old and new server for > some time. Will this cause problems? > > Is there a simpler solution to the problem? > > -- > /Wegge > > Leder efter redundant peering af dk.*,linux.debian.* I did this several years ago using imapsync to sync the accounts from an old server to a new server. Once all the accounts have been sync'd and you're ready to cut over to the new server, run imapsync one last time to catch anything new that's arrived. It will go very quickly. Disable postfix/dovecot on the old server and change your DNS to point to the new server. Or better yet, if the old and new servers are on the same network, just swap the names and IPs of the new and old servers. -Terry Terry Barnum digital OutPost http://www.dop.com From deano-dovecot at areyes.com Mon Jul 14 22:32:38 2014 From: deano-dovecot at areyes.com (deano-dovecot at areyes.com) Date: Mon, 14 Jul 2014 18:32:38 -0400 Subject: Transition from one server to another. In-Reply-To: <87zjgbadxk.fsf@huddi.jernurt.dk> References: <87zjgbadxk.fsf@huddi.jernurt.dk> Message-ID: <2f04fa259b5820d82365cd8d5f7e700e@areyes.com> I've done this a couple of times, and there are a couple of things you can do to help make it go smoothly. I did it not too long ago to move to a new single server, and am getting ready to do it again to a fully redundant setup (3 nodes for percona clustering, 2 of the nodes as dovecot with sync). * Set your current MX records TTL to the lowest you can, usually 30 minutes. This will make it quicker to do the final transition when you do. * Create an A record in DNS for the new server, but no MX records for it just yet. * If you're using SPF, add your new server IP address to the TXT record. Get your new server up and ready and *tested*. Verify everything works. Web access to roundcube/squirrelmail/whatever, imaps access from thunderbird/outlook/whatever and so on, sending mail from the new server. The works. Get bi-directional replication going between the two servers. This doesn't have to be dovecot dsync, you can use offlineimap too. Whatever, get sync going. The aim is to be sure that any changes on one server are synced to the other one. Test it - use swaks to create mail on the new server, make sure it shows up cleanly on the old (that people are still using). * NOW, add an MX record of higher (lower number) priority pointing to the new server. Remove the MX record for the old server. Point clients to the new server. This can be done gradually, as mail will be replicated between the two systems. All new mail should now be going to the new server, while some systems with cached DNS will still use the old one. Any mail they deliver to the old server will replicate to the new one. The cached MX records should expire fairly soon (remember the 30 minute TTL you set) but sometimes they don't for a while. Wait a few hours. * Disable inbound smtp on the old server. Now any connections coming into the old will fail, and the source systems should spool the mail for retry later, delivering to the new server. Clients can still use the old server, and even send mail from it. Wait a day or so and watch the old server. Pretty quickly you should see no more connections coming into it. "tshark port 25 or port 587" is your friend here. Finally decommission the old server once you have all clients moved over to the new server. If anyone is interested, that redundant setup is part of an automated installer I've been working on. You can set up a 3-node environment on cheap VPS', two 2gig ram nodes for the dovecot/exim4/roundcube/spamassassin/clamav and a 512meg ram one for the 3rd Percona cluster DB node (to make a quorum). Everything replicates via encrypted vpn, so you can point to either main node for roundcube or imaps. Works fine in Amazon AWS too, though that's a little pricier than the cheap VPS providers. On 2014-07-14 16:22, Anders Wegge Keller wrote: > A frind of mine and I are running a dedicated server, that among > other things host mail for ourselves and friends and families. All in > all about 15 different domains with 35-40 users. The machine in > question is old, so we are doing a slow transition from the old server > to the new one. So far, we've managed to move web hosts > seamlessly. Due to the technical capabilities at some of the user > base, it would be nice to get to a setup, where we can move individual > users imaps from the old server to the new one, as we get the time to > visit them. > > I have an idea how such a transition could go: > > 1. Upgrade the old dovecot 1.2.15 to 2.1.whateveritis from debian > squeeze backports. > > 2. Set dsync up to replicate mails from the old server to the new > server. I know that 2.2 is recommended, but with a limited amount > of user, I'm willing to take a performance hit. > > 3. Migrate my parents &c to use the new server. > > 4. When all users have been moved on to using the new server, upgrade > MX records for the domain to point at the new server. > > 5. When all MX records are updated, decalre success. > > > Is this feasible, and what would the risks be. For instance, during > step 4, mails are bound to arrive at bothe the old and new server for > some time. Will this cause problems? > > Is there a simpler solution to the problem? From tss at iki.fi Mon Jul 14 22:50:04 2014 From: tss at iki.fi (Timo Sirainen) Date: Tue, 15 Jul 2014 00:50:04 +0200 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <53C42B08.7020106@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <71984EBD-3257-455D-9502-740CA9DB248E@iki.fi> <53C42B08.7020106@colostate.edu> Message-ID: Did you actually switch from sparc to x86 CPU in the server? If yes, then looks like the code to handle the switching could use some fixing. But in any case you can just delete the .imap/ directories and have the indexes be rebuilt. On 14.7.2014, at 21.10, CJ Keist wrote: > Here are the log entires just before the signal 6 error: > > Jul 10 00:19:56 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/DailySmarts/dovecot.index: CPU architecture changed > Jul 10 00:19:58 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/engr101/dovecot.index: CPU architecture changed > Jul 10 00:19:59 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/INTO/dovecot.index: CPU architecture changed > Jul 10 00:19:59 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/Drafts/dovecot.index: CPU architecture changed > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Index /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index: Lost log for seq=1 offset=0 > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.warning] imap(tjs): Warning: fscking index file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Fixed index file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index: log_file_seq 1 -> 33554432 > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Corrupted transaction log file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/FundingOpportunities/dovecot.index.log seq 33554432: log file shrank (1124 < 6144) (sync_offset=6144) > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Raw backtrace: /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'default_fatal_finish+0x51 [0xfede0f41] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'i_internal_fatal_handler+0x31 [0xfede1071] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'i_fatal+0x0 [0xfee0c4e2] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'0x6d595 [0xfeddd595] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_file_add_to_list+0x9c [0xfef3f5cc] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_file_open+0x25c [0xfef401dc] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_open+0xda [0xfef3bdba] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_index_open_files+0x23 [0xfef239e3] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0' > > Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Fatal: master: service(imap): child 2238 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) > Jul 10 00:20:01 mail2 dovecot: [ID 583609 mail.info] imap-login: Login: user=, method=PLAIN, rip=129.82.226.98, lip=129.82.20.15, mpid=2943, TLS, session= > Jul 10 00:20:01 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Transaction log file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/FundingOpportunities/dovecot.index.log: marked corrupted > > > > On 7/11/14, 5:40 PM, Timo Sirainen wrote: >> Find the first error/warning that Dovecot logs, which should happen just before you reach the limit. >> >> On 10.7.2014, at 21.33, CJ Keist wrote: >> >>> It's not fixed. Now the limit looks to be around 500 processes and we start to get number of connections exceeded. Any ideas? >>> >>> >>> >>> On 7/10/14, 10:35 AM, CJ Keist wrote: >>>> I fixed this issue about the process limit in the 10-master.conf file: >>>> >>>> default_process_limit = 5000 >>>> default_client_limit = 30000 >>>> >>>> >>>> On 7/10/14, 10:03 AM, CJ Keist wrote: >>>>> It looks like on the system that once we hit around 200 imap processes >>>>> it stops there and no more imap processes can be created. Is there a >>>>> number of max imap processes in the config file somewhere. By the way >>>>> running on OmniOS: >>>>> >>>>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>>>> >>>>> >>>>> >>>>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>>>> Thanks for the reply. I have seen threads about setting the >>>>>> mail_max_userip_connections, I have set this to 5000 and still people >>>>>> getting the exceeding connections errorl >>>>>> >>>>>> >>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>> # OS: SunOS 5.11 i86pc >>>>>> auth_failure_delay = 5 secs >>>>>> auth_mechanisms = plain login cram-md5 >>>>>> auth_worker_max_count = 3000 >>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>> disable_plaintext_auth = no >>>>>> hostname = mail2.engr.colostate.edu >>>>>> managesieve_notify_capability = mailto >>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>> relational regex imap4flags copy include variables body enotify >>>>>> environment mailbox date ihave duplicate >>>>>> namespace inbox { >>>>>> inbox = yes >>>>>> location = >>>>>> mailbox Drafts { >>>>>> special_use = \Drafts >>>>>> } >>>>>> mailbox Junk { >>>>>> special_use = \Junk >>>>>> } >>>>>> mailbox Sent { >>>>>> special_use = \Sent >>>>>> } >>>>>> mailbox "Sent Messages" { >>>>>> special_use = \Sent >>>>>> } >>>>>> mailbox Trash { >>>>>> special_use = \Trash >>>>>> } >>>>>> prefix = >>>>>> } >>>>>> passdb { >>>>>> driver = pam >>>>>> } >>>>>> passdb { >>>>>> driver = passwd >>>>>> } >>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>> service auth { >>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>> mode = 0666 >>>>>> } >>>>>> unix_listener auth-userdb { >>>>>> group = postfix >>>>>> mode = 0666 >>>>>> user = postfix >>>>>> } >>>>>> user = root >>>>>> } >>>>>> service imap-login { >>>>>> inet_listener imap { >>>>>> port = 143 >>>>>> } >>>>>> inet_listener imaps { >>>>>> port = 993 >>>>>> ssl = yes >>>>>> } >>>>>> } >>>>>> service pop3-login { >>>>>> inet_listener pop3 { >>>>>> port = 110 >>>>>> } >>>>>> inet_listener pop3s { >>>>>> port = 995 >>>>>> ssl = yes >>>>>> } >>>>>> } >>>>>> ssl_cert = >>>>> ssl_key = >>>>> userdb { >>>>>> args = blocking=yes >>>>>> driver = passwd >>>>>> } >>>>>> protocol imap { >>>>>> mail_max_userip_connections = 5000 >>>>>> } >>>>>> protocol lda { >>>>>> mail_plugins = sieve >>>>>> } >>>>>> >>>>>> >>>>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>>>> >>>>>>> >>>>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>>>> Another problem is people are getting error message from their >>>>>>>> clients stating >>>>>>>> they have exceeded their number of connections. >>>>>>> >>>>>>> mail_max_userip_connections = 50 >>>>>>> >>>>>>> well, how much folders do the have >>>>>>> >>>>>>> keep in mind that fpr IDLE you have one connection per user and folder >>>>>>> 10 users with 10 folders behind the same NAT router are 100 connections >>>>>>> from the same IP >>>>>>> >>>>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>>>> Added info: These errors seem to come from users using mbox format. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>>>> All, >>>>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>>>> postfix >>>>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>>>> connections to >>>>>>>>>> the mail server. >>>>>>>>>> >>>>>>>>>> I've been able to google this error but haven't found fix for this >>>>>>>>>> yet. >>>>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>>>> either. >>>>>>>>>> >>>>>>>>>> Any suggestions? >>>>>>>>>> >>>>>>>>>> Var adm message: >>>>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>>>> Fatal: >>>>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>>>> dumped >>>>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>>>> >>>>>>>>>> Here is config output: >>>>>>>>>> >>>>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>>>> auth_failure_delay = 5 secs >>>>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>>>> auth_worker_max_count = 300 >>>>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>>>> disable_plaintext_auth = no >>>>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>>>> managesieve_notify_capability = mailto >>>>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>>>> environment mailbox date ihave duplicate >>>>>>>>>> namespace inbox { >>>>>>>>>> inbox = yes >>>>>>>>>> location = >>>>>>>>>> mailbox Drafts { >>>>>>>>>> special_use = \Drafts >>>>>>>>>> } >>>>>>>>>> mailbox Junk { >>>>>>>>>> special_use = \Junk >>>>>>>>>> } >>>>>>>>>> mailbox Sent { >>>>>>>>>> special_use = \Sent >>>>>>>>>> } >>>>>>>>>> mailbox "Sent Messages" { >>>>>>>>>> special_use = \Sent >>>>>>>>>> } >>>>>>>>>> mailbox Trash { >>>>>>>>>> special_use = \Trash >>>>>>>>>> } >>>>>>>>>> prefix = >>>>>>>>>> } >>>>>>>>>> passdb { >>>>>>>>>> driver = pam >>>>>>>>>> } >>>>>>>>>> passdb { >>>>>>>>>> driver = passwd >>>>>>>>>> } >>>>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>>>> service auth { >>>>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>>>> mode = 0666 >>>>>>>>>> } >>>>>>>>>> unix_listener auth-userdb { >>>>>>>>>> group = postfix >>>>>>>>>> mode = 0666 >>>>>>>>>> user = postfix >>>>>>>>>> } >>>>>>>>>> user = root >>>>>>>>>> } >>>>>>>>>> service imap-login { >>>>>>>>>> inet_listener imap { >>>>>>>>>> port = 143 >>>>>>>>>> } >>>>>>>>>> inet_listener imaps { >>>>>>>>>> port = 993 >>>>>>>>>> ssl = yes >>>>>>>>>> } >>>>>>>>>> } >>>>>>>>>> service pop3-login { >>>>>>>>>> inet_listener pop3 { >>>>>>>>>> port = 110 >>>>>>>>>> } >>>>>>>>>> inet_listener pop3s { >>>>>>>>>> port = 995 >>>>>>>>>> ssl = yes >>>>>>>>>> } >>>>>>>>>> } >>>>>>>>>> ssl_cert = >>>>>>>>> ssl_key = >>>>>>>>> userdb { >>>>>>>>>> args = blocking=yes >>>>>>>>>> driver = passwd >>>>>>>>>> } >>>>>>>>>> protocol imap { >>>>>>>>>> mail_max_userip_connections = 50 >>>>>>>>>> } >>>>>>>>>> protocol lda { >>>>>>>>>> mail_plugins = sieve >>>>>>>>>> } >>>>>>> >>>>>> >>>>> >>>> >>> >>> -- >>> C. J. Keist Email: cj.keist at colostate.edu >>> Systems Group Manager Solaris 10 OS (SAI) >>> Engineering Network Services Phone: 970-491-0630 >>> College of Engineering, CSU Fax: 970-491-5569 >>> Ft. Collins, CO 80523-1301 >>> >>> All I want is a chance to prove 'Money can't buy happiness' > > -- > C. J. Keist Email: cj.keist at colostate.edu > Systems Group Manager Solaris 10 OS (SAI) > Engineering Network Services Phone: 970-491-0630 > College of Engineering, CSU Fax: 970-491-5569 > Ft. Collins, CO 80523-1301 > > All I want is a chance to prove 'Money can't buy happiness' From bourek at thinline.cz Mon Jul 14 23:14:48 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 15 Jul 2014 01:14:48 +0200 Subject: Transition from one server to another. In-Reply-To: <87zjgbadxk.fsf@huddi.jernurt.dk> References: <87zjgbadxk.fsf@huddi.jernurt.dk> Message-ID: <53C46468.1040106@thinline.cz> > > I have an idea how such a transition could go: > > 1. Upgrade the old dovecot 1.2.15 to 2.1.whateveritis from debian > squeeze backports. Backports version is a bit outdated so you might want to consider using version from jessie, which seems to follow the upstream more closely. The tradeoff is of course the need to pull some system libraries with it as well, namely libc. Newer version may interfere with whatever else you run on the server and you'll probably need to solve some dependencies manually. It's working for me on pure dovecot server, YMMV Other than that I more or less aggree with the post from Terry Barnum - stop postfix to prevent delivery of new mail, block the old IMAP/POP3 server from regular users, use some sort of IMAP sync (either imapsync or - IMO - even better doveadm sync) to download data from the old server to the new one. After that's done, switch IP addresses and enable services on new server. It'll need some late-evening/night time work and maybe console access if the IP switch goes wrong, but otherwise it should be hassle-free - particulary no need to change ppl's mail client settings this way From slusarz at curecanti.org Mon Jul 14 23:47:19 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Mon, 14 Jul 2014 17:47:19 -0600 Subject: HIGHESTMODSEQ tracking In-Reply-To: References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> Message-ID: <20140714174719.Horde.px3Mk2olwJghwWJ-q5T5kw6@bigworm.curecanti.org> Quoting Kostya Vasilyev : > 2014-07-10 4:05 GMT+04:00 Michael M Slusarz : > >> Quoting Kostya Vasilyev : >> >> 2014-07-10 1:37 GMT+04:00 Michael M Slusarz : >>> >>> Quoting Kostya Vasilyev : >>> >>>> >>>> These days, you *really* should be using QRESYNC instead though. >>>> >>> >>> There are some mail servers that support CONDSTORE but not QRESYNC. The >>> old >>> chicken and egg IMAP problem :) >>> >> >> [ snip ] >> Both Dovecot and Cyrus support both CONDSTORE and QRESYNC, and combined >> that is more than 50% market share, so that should be incentive enough. >> Gmail only supports CONDSTORE, but it's the outlier. > > > Gmail still does have a few users, though. A few dozen at least, maybe more > :) > > And it has a big advantage, from my point of view, over Cyrus / Dovecot -- > there is but one server version that's consistent for all accounts. > > Yes, they do some things wrong (like not sending message flags changes over > IDLE connections), but I can test something in my personal account, get > feedback from 3-5-10 users with @gmail accounts, and be reasonably > confident that everything is fine (and that I'd know know if it's not). This is getting a bit off-topic on this list... but Gmail does a LOT of things wrong. Head over to one of the IMAP lists for further information. If you are testing against Gmail as the gold standard as to how a IMAP server should operate, I can safely say you are Doing It Wrong. > For the "more than 50% market share" of Dovecot / Cyrus, do you have a > breakdown by version number? At least in terms of 1.* vs 2.0 and higher? I do not. >> Maybe. You can't tell until you actually see whether the EXAMINE/SELECT >> returns HIGHESTMODSEQ or NOMODSEQ. > > Are you saying that Dovecot will always (*will always*, and I mean > *always*) return NOMODSEQ after a client "expresses interested in modseq > values" and the server can't enable it for some reason? Much like UIDVALIDITY should never change, NOMODSEQ will never be sent (practical usage) for an active CONDSTORE access. You are asking about a tremendously rare occurrence. The whole deal with "HIGHESTMODSEQ 1" is irrelevant if you enable CONDSTORE. I can't tell you what a server will return if you enable CONDSTORE in one session, but then don't in another. But that doesn't matter, since you aren't using HIGHESTMODSEQ in the latter case. As long as CONDSTORE is active, HIGHESTMODSEQ will be updated, at least in my 6 year experience with Dovecot which involves handling installations with millions of users. > Or if it was previously enabled, and then well, I don't know, "something > happened"? > > By *always* I mean -- since Dovecot first started having a CONDSTORE in its > CAPS, including version a.b.c that came with now really old Debian X, and > version h.j.k that came with now really old RHEL Y, but which are still out > there on actual mail servers, being used in actual mail accounts? I have never run into an issue with HIGHESTMODSEQ for a properly CONDSTORE-enabled session for Dovecot ever. I was one of the first people (that I am aware of) that implemented CONDSTORE/QRESYNC back in the early days (2009) ... and Dovecot was exclusively the server I was developing with at that time. > When something goes wrong in an email app, then to the user, it's always > the email app developer's fault. Nobody gives a damn about the subtleties > of what RFC abc says about xyz, or if server version j.k.l from three years > ago had a bug. Agree, but only up to a certain point. If something is so onerous to work around, then it *is* ok to say "it's the server's fault and we're not going to work around this." Like everything else in life, there is a cost/benefit analysis that must be done to determine where that line needs to be drawn. > So, before enabling certain optimizations for Dovecot, I thought I'd ask on > a Dovecot mailing list, about actual behavior for this server feature. > > I assume this mailing list has people with real Dovecot experience and > knowledge, and maybe even the developers are lurking here too. > > Specifically, I was hoping to hear back maybe something like this: > > "Dovecot version X which was packaged in Debian Z, would not update the > modseq value after command Y". > > Or maybe -- which would be great: > > "There were no issues with modseq tracking, at all, no reported bugs, code > not touched, since the feature was originally implemented and advertised as > CONDSTORE in CAPS in version 1.2.*". There are certainly bugs - I found several of them years ago when the code was brand new (here's a thread: http://markmail.org/message/fj74xta5z5uv4nix). But nothing that was showstopping. And none of those versions are being run anymore for all intents and purposes. The bigger issue, specifically with QRESYNC, is not implementation bugs but rather some deficiencies in the original standards (e.g. unsolicited FETCHs without UIDs; VANISHED wasn't a required response so sequence number tracking was still required) that weren't addressed until RFC 7162. Those are more likely to trip you up then some transient implementation bug. michael From gessel at blackrosetech.com Tue Jul 15 01:12:27 2014 From: gessel at blackrosetech.com (David Gessel) Date: Tue, 15 Jul 2014 04:12:27 +0300 Subject: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) Message-ID: <53C47FFB.4040901@blackrosetech.com> Version Info: FreeBSD 9.2-RELEASE #0 r266046 AMD64, Dovecot 2.2.13, dovecot-pigeonhole-0.4.3, amavisd-new-2.8.0_2,1, clamav-0.98.4, postfix29-2.9.9_1,1, postfixadmin-2.3.6, spamassassin-3.4.0_12 (zpool data and output of dovecot -n at bottom of post) I suspect these are related problems and further that they are related to some trivial newb error I've made in my configuration, but searching descriptions of the symptoms has not yet guided me to a solution. I recently migrated from Courier to Dovecot on new hardware and imap synced a 16GB mailstore (du -hs) divided up into annual directories with about 15,000 messages each. I mention the size because it seems an errant Remove Duplicate Messages (Alternate) 0.3.9 acting on what seem to be false duplicates in Thunderbird reduced the inbox size from 7500-ish messages to 1300 (DOH!) and may have solved my K-9 problem described below. My old Courier server still has the vast majority of these messages and I will resync someday and then try to file them away more expediently than my previously somewhat lazy management style to keep the inbox small. * In thunderbird, I get constant downloading of messages. Every time I switch to the inbox from another folder, the messages start redownloading. This sometimes, but not always, seems to create duplicate messages, but I'm now fairly sure they are only created in the client and not on the server. Searching through various forums, it appears this has been a problem for Thunderbird for some time, but it wasn't for me on Courier. As posts about similar errors seem to have petered out over the last year without any clear guidance on how to fix it that I could find, I expect there's a simple fix I just haven't found yet, either in TB configuration or in Dovecot. Any hints? I tried Thunderfix to remove the .msf files and will be redownloading my mail over the thin pipe out to Iraq for the next 6 months (DOH!). One artifact is that when I restart thunderbird, my inbox is reported as having about 130 messages in it, then thunderbird starts redownloading headers and eventually gets back up to the 1297 currently listed both in the TB pane and by ls | wc -l in /cur. Is it possible there is a time out that needs to be extended? In TB, I've set (among other less apparently relevant options) mailnews.tcptimeout;1000 mail.db.idle_limit;30000000 * Also, with Thunderbird, I get duplication of messages in the client. I suspect this is related to the previous redownload error, but there is some indication in some posts that it is potentially related to a dirty flag. I've had this problem before with Thunderbird and Courier, but it went away after a TB update. It seems to have reappeared with Dovecot. The TB client hasn't been updated during the transition, so some interaction issue seems more likely than a pure TB bug. Likely TB's fault as this is a well known, but poorly diagnosed TB issue (deleting duplicates regularly seems to be the solution, but my inbox would double in size every few hours on the LAN. Now that I'm remote over a 2mbps link, it has slowed way down: bonus!). * "Expunged message reappeared, giving a new UID" errors appear a lot. This might well be related to the last error. This seems to happen with TB client connections, but I'm not sure what action triggers it. I am not replicating. I tried renaming 10-director.conf to 10-director.conf.disabled and got no complaints from Dovecot (as I'm not using replication, it shouldn't) but that indicates that this Expunged message reappeared error is probably of a different source than, for example, Simon Fraser's debug effort. * K9 was only showing a subset of my messages and generally not the new ones. They'd appear in the alert properly, but weren't visible in the client and sometimes they'd be visible and then disappear later. I imagined there could a correlation between TB checking mail and perhaps moving messages from /new to /cur and K9 losing track, but the potentially tragic "duplicate" removal may have reduced my inbox to a size that k9 can handle as K9 inbox display seems normal now as far as I can tell. When I resync (assuming I can), I sort of dread this problem reappearing. K9 worked as expected against Courier with the same inbox. These apparently difficult to diagnose problems are occasionally suggested as related to namespace configuration issues and thunderbird is reported to have issues with some separator options. I vaguely suspect this, but I'm pretty sure my namespace config is default and should be well tested. I haven't, for example, explicitly stated the default "/" but left it commented out. I increased the connection limit count per user*IP to 20 as TB seems to be parallel downloading a lot of folders. This has neither improved nor degraded performance in any way I can see and is probably irrelevant. Any hints greatly appreciated. Filesystem/Zpool data: NAME PROPERTY VALUE SOURCE zroot size 400G - zroot capacity 28% - zroot altroot - default zroot health ONLINE - zroot guid 1061309925223582150 default zroot version - default zroot bootfs zroot local zroot delegation on default zroot autoreplace off default zroot cachefile - default zroot failmode wait default zroot listsnapshots off default zroot autoexpand off default zroot dedupditto 0 default zroot dedupratio 1.10x - zroot free 286G - zroot allocated 114G - zroot readonly off - zroot comment - default zroot expandsize 0 - zroot freeing 0 default zroot feature at async_destroy enabled local zroot feature at empty_bpobj active local zroot feature at lz4_compress active local server # dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.2-RELEASE amd64 auth_default_realm = mydomain.com auth_mechanisms = plain login auth_realms = mydomain.com mydomain2.org disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 5000 hostname = mydomain.com imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins last_valid_gid = 5000 last_valid_uid = 5000 lda_mailbox_autocreate = yes listen = * mail_gid = 5000 mail_location = maildir:~/:CONTROL=/var/no-quota/%u mail_plugins = quota mail_log notify mail_temp_dir = /var/tmp mail_uid = 5000 maildir_broken_filename_sizes = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate spamtest spamtestplus editheader mbox_lazy_writes = no namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { expire = Trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_rule = *:storage=50G quota_rule2 = Trash:storage=+30%% quota_rule3 = Sent:storage=+30%% quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_before = /usr/local/etc/dovecot/sieve/ sieve_dir = ~/sieve sieve_extensions = +spamtest +spamtestplus +relational +comparator-i;ascii-numeric +editheader } postmaster_address = gessel at mydomain.com protocols = imap lmtp sieve sieve sendmail_path = /usr/local/sbin/sendmail service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 128 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_cert = Tried mailing the maintainer, but didn't get a response -- anyone know what's happened to the ATrpms repo? Not only is http://atrpms.net/name/dovecot/ empty, but: http://packages.atrpms.net/dist/el6/ seems to return a 404. Some of the mirrors still have the packages, but does anyone know if they're going to continue to build 2.2.x packages? w From dovecot.org at veggiechinese.net Tue Jul 15 03:48:04 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Mon, 14 Jul 2014 20:48:04 -0700 Subject: director / main instance Message-ID: <20140715034804.GB97784@aura.veggiechinese.net> I have directors and backend servers running on the same systems (x3). To be able to run doveadm foo with a minimum of fuss (without having to list socket paths explicitly), should it be the director that's the "default"? If so, is it safe to symlink '/var/run/dovecot' to '/var/run/dovecot-director', or should I just make the director's base path /var/run/dovecot directly? in dovecot-director.conf, I have: service doveadm { inet_listener { port = 8889 } } local 192.168.x.0/24 { doveadm_password = Foo } doveadm_proxy_port = 8888 and in dovecot-main.conf, I have: service doveadm { inet_listener { port = 8888 } } local 192.168.x.0/24 { doveadm_password = Foo } protocol doveadm { auth_socket_path = director-userdb } Is this correct (and is there anything unneeded / redundant there)? # dovecot instance list path name last used running /var/run/dovecot-director director 2014-07-14 20:36:49 yes /var/run/dovecot-main main 2014-07-14 20:36:49 yes # dovecot director status mail server ip vhosts users 192.168.x.xx 100 2 192.168.x.xx 100 0 192.168.x.xx 100 0 From cj.keist at colostate.edu Tue Jul 15 04:22:39 2014 From: cj.keist at colostate.edu (CJ Keist) Date: Mon, 14 Jul 2014 22:22:39 -0600 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <71984EBD-3257-455D-9502-740CA9DB248E@iki.fi> <53C42B08.7020106@colostate.edu> Message-ID: <9D3ABD35-B9D4-42BE-B4DF-C73C9E15DAC7@colostate.edu> Yes, I did switch from sparc server to x86. I also removed all the dovecot.indexes and .imap folders. I will try 2.2 again tomorrow with the process limits specified for imap, pop, and auth. My concern is with auto detection of user accounts using mbox or Maildir formats. Is it still the case to support mix mbox and Maildir by commenting out the mail_location lines? CJ Keist. Email: cj.keist at colostate.edu Systems Group Manager. Solaris 10 OS (SAI) Engineering Network Services. Phone: 970-491-0630 College of Engineering, CSU. Fax: 970-491-5569 Ft. Collins, CO 80523-1301 > On Jul 14, 2014, at 4:50 PM, Timo Sirainen wrote: > > Did you actually switch from sparc to x86 CPU in the server? If yes, then looks like the code to handle the switching could use some fixing. > > But in any case you can just delete the .imap/ directories and have the indexes be rebuilt. > >> On 14.7.2014, at 21.10, CJ Keist wrote: >> >> Here are the log entires just before the signal 6 error: >> >> Jul 10 00:19:56 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/DailySmarts/dovecot.index: CPU architecture changed >> Jul 10 00:19:58 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/engr101/dovecot.index: CPU architecture changed >> Jul 10 00:19:59 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/INTO/dovecot.index: CPU architecture changed >> Jul 10 00:19:59 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Rebuilding index file /top/admin/AcadAffairs/people/tjs/home/mail/.imap/Drafts/dovecot.index: CPU architecture changed >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Index /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index: Lost log for seq=1 offset=0 >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.warning] imap(tjs): Warning: fscking index file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Fixed index file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/RM-MSMSP/dovecot.index: log_file_seq 1 -> 33554432 >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Corrupted transaction log file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/FundingOpportunities/dovecot.index.log seq 33554432: log file shrank (1124 < 6144) (sync_offset=6144) >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Raw backtrace: /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'default_fatal_finish+0x51 [0xfede0f41] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'i_internal_fatal_handler+0x31 [0xfede1071] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'i_fatal+0x0 [0xfee0c4e2] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot.so.0.0.0'0x6d595 [0xfeddd595] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_file_add_to_list+0x9c [0xfef3f5cc] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_file_open+0x25c [0xfef401dc] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_transaction_log_open+0xda [0xfef3bdba] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0'mail_index_open_files+0x23 [0xfef239e3] -> /userM/mail-services/dovecot/lib/dovecot/libdovecot-storage.so.0.0.0' >> >> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Fatal: master: service(imap): child 2238 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) >> Jul 10 00:20:01 mail2 dovecot: [ID 583609 mail.info] imap-login: Login: user=, method=PLAIN, rip=129.82.226.98, lip=129.82.20.15, mpid=2943, TLS, session= >> Jul 10 00:20:01 mail2 dovecot: [ID 583609 mail.error] imap(tjs): Error: Transaction log file /top/admin/AcadAffairs/people/tjs/home/mail/Local/.imap/FundingOpportunities/dovecot.index.log: marked corrupted >> >> >> >>> On 7/11/14, 5:40 PM, Timo Sirainen wrote: >>> Find the first error/warning that Dovecot logs, which should happen just before you reach the limit. >>> >>>> On 10.7.2014, at 21.33, CJ Keist wrote: >>>> >>>> It's not fixed. Now the limit looks to be around 500 processes and we start to get number of connections exceeded. Any ideas? >>>> >>>> >>>> >>>>> On 7/10/14, 10:35 AM, CJ Keist wrote: >>>>> I fixed this issue about the process limit in the 10-master.conf file: >>>>> >>>>> default_process_limit = 5000 >>>>> default_client_limit = 30000 >>>>> >>>>> >>>>>> On 7/10/14, 10:03 AM, CJ Keist wrote: >>>>>> It looks like on the system that once we hit around 200 imap processes >>>>>> it stops there and no more imap processes can be created. Is there a >>>>>> number of max imap processes in the config file somewhere. By the way >>>>>> running on OmniOS: >>>>>> >>>>>> SunOS mail2 5.11 omnios-6de5e81 i86pc i386 i86pc >>>>>> >>>>>> >>>>>> >>>>>>> On 7/10/14, 9:50 AM, CJ Keist wrote: >>>>>>> Thanks for the reply. I have seen threads about setting the >>>>>>> mail_max_userip_connections, I have set this to 5000 and still people >>>>>>> getting the exceeding connections errorl >>>>>>> >>>>>>> >>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>> # OS: SunOS 5.11 i86pc >>>>>>> auth_failure_delay = 5 secs >>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>> auth_worker_max_count = 3000 >>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>> disable_plaintext_auth = no >>>>>>> hostname = mail2.engr.colostate.edu >>>>>>> managesieve_notify_capability = mailto >>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>> environment mailbox date ihave duplicate >>>>>>> namespace inbox { >>>>>>> inbox = yes >>>>>>> location = >>>>>>> mailbox Drafts { >>>>>>> special_use = \Drafts >>>>>>> } >>>>>>> mailbox Junk { >>>>>>> special_use = \Junk >>>>>>> } >>>>>>> mailbox Sent { >>>>>>> special_use = \Sent >>>>>>> } >>>>>>> mailbox "Sent Messages" { >>>>>>> special_use = \Sent >>>>>>> } >>>>>>> mailbox Trash { >>>>>>> special_use = \Trash >>>>>>> } >>>>>>> prefix = >>>>>>> } >>>>>>> passdb { >>>>>>> driver = pam >>>>>>> } >>>>>>> passdb { >>>>>>> driver = passwd >>>>>>> } >>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>> service auth { >>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>> mode = 0666 >>>>>>> } >>>>>>> unix_listener auth-userdb { >>>>>>> group = postfix >>>>>>> mode = 0666 >>>>>>> user = postfix >>>>>>> } >>>>>>> user = root >>>>>>> } >>>>>>> service imap-login { >>>>>>> inet_listener imap { >>>>>>> port = 143 >>>>>>> } >>>>>>> inet_listener imaps { >>>>>>> port = 993 >>>>>>> ssl = yes >>>>>>> } >>>>>>> } >>>>>>> service pop3-login { >>>>>>> inet_listener pop3 { >>>>>>> port = 110 >>>>>>> } >>>>>>> inet_listener pop3s { >>>>>>> port = 995 >>>>>>> ssl = yes >>>>>>> } >>>>>>> } >>>>>>> ssl_cert = >>>>>> ssl_key = >>>>>> userdb { >>>>>>> args = blocking=yes >>>>>>> driver = passwd >>>>>>> } >>>>>>> protocol imap { >>>>>>> mail_max_userip_connections = 5000 >>>>>>> } >>>>>>> protocol lda { >>>>>>> mail_plugins = sieve >>>>>>> } >>>>>>> >>>>>>> >>>>>>>> On 7/10/14, 9:45 AM, Reindl Harald wrote: >>>>>>>> >>>>>>>> >>>>>>>> Am 10.07.2014 17:32, schrieb CJ Keist: >>>>>>>>> Another problem is people are getting error message from their >>>>>>>>> clients stating >>>>>>>>> they have exceeded their number of connections. >>>>>>>> >>>>>>>> mail_max_userip_connections = 50 >>>>>>>> >>>>>>>> well, how much folders do the have >>>>>>>> >>>>>>>> keep in mind that fpr IDLE you have one connection per user and folder >>>>>>>> 10 users with 10 folders behind the same NAT router are 100 connections >>>>>>>> from the same IP >>>>>>>> >>>>>>>>>> On 7/10/14, 9:09 AM, CJ Keist wrote: >>>>>>>>>> Added info: These errors seem to come from users using mbox format. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On 7/10/14, 9:04 AM, CJ Keist wrote: >>>>>>>>>>> All, >>>>>>>>>>> Just move our mail servers over to a new mail server running >>>>>>>>>>> postfix >>>>>>>>>>> 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my >>>>>>>>>>> /var/adm/files. People are complaining of loosing their >>>>>>>>>>> connections to >>>>>>>>>>> the mail server. >>>>>>>>>>> >>>>>>>>>>> I've been able to google this error but haven't found fix for this >>>>>>>>>>> yet. >>>>>>>>>>> NOt sure where to put the drop-priv option in the config files >>>>>>>>>>> either. >>>>>>>>>>> >>>>>>>>>>> Any suggestions? >>>>>>>>>>> >>>>>>>>>>> Var adm message: >>>>>>>>>>> Jul 10 08:54:29 mail2 dovecot: [ID 583609 mail.crit] imap(chen): >>>>>>>>>>> Fatal: >>>>>>>>>>> master: service(imap): child 20258 killed with signal 6 (core not >>>>>>>>>>> dumped >>>>>>>>>>> - set service imap { drop_priv_before_exec=yes }) >>>>>>>>>>> >>>>>>>>>>> Here is config output: >>>>>>>>>>> >>>>>>>>>>> root at mail2:/userM/mail-services/dovecot/sbin# ./dovecot -n >>>>>>>>>>> # 2.2.13: /userM/mail-services/dovecot/etc/dovecot/dovecot.conf >>>>>>>>>>> # OS: SunOS 5.11 i86pc >>>>>>>>>>> auth_failure_delay = 5 secs >>>>>>>>>>> auth_mechanisms = plain login cram-md5 >>>>>>>>>>> auth_worker_max_count = 300 >>>>>>>>>>> base_dir = /userM/mail-services/dovecot/var/run/dovecot/ >>>>>>>>>>> disable_plaintext_auth = no >>>>>>>>>>> hostname = mail2.engr.colostate.edu >>>>>>>>>>> managesieve_notify_capability = mailto >>>>>>>>>>> managesieve_sieve_capability = fileinto reject envelope >>>>>>>>>>> encoded-character vacation subaddress comparator-i;ascii-numeric >>>>>>>>>>> relational regex imap4flags copy include variables body enotify >>>>>>>>>>> environment mailbox date ihave duplicate >>>>>>>>>>> namespace inbox { >>>>>>>>>>> inbox = yes >>>>>>>>>>> location = >>>>>>>>>>> mailbox Drafts { >>>>>>>>>>> special_use = \Drafts >>>>>>>>>>> } >>>>>>>>>>> mailbox Junk { >>>>>>>>>>> special_use = \Junk >>>>>>>>>>> } >>>>>>>>>>> mailbox Sent { >>>>>>>>>>> special_use = \Sent >>>>>>>>>>> } >>>>>>>>>>> mailbox "Sent Messages" { >>>>>>>>>>> special_use = \Sent >>>>>>>>>>> } >>>>>>>>>>> mailbox Trash { >>>>>>>>>>> special_use = \Trash >>>>>>>>>>> } >>>>>>>>>>> prefix = >>>>>>>>>>> } >>>>>>>>>>> passdb { >>>>>>>>>>> driver = pam >>>>>>>>>>> } >>>>>>>>>>> passdb { >>>>>>>>>>> driver = passwd >>>>>>>>>>> } >>>>>>>>>>> postmaster_address = cjay at engr.colostate.edu >>>>>>>>>>> service auth { >>>>>>>>>>> unix_listener /var/lib/postfix/private/auth { >>>>>>>>>>> mode = 0666 >>>>>>>>>>> } >>>>>>>>>>> unix_listener auth-userdb { >>>>>>>>>>> group = postfix >>>>>>>>>>> mode = 0666 >>>>>>>>>>> user = postfix >>>>>>>>>>> } >>>>>>>>>>> user = root >>>>>>>>>>> } >>>>>>>>>>> service imap-login { >>>>>>>>>>> inet_listener imap { >>>>>>>>>>> port = 143 >>>>>>>>>>> } >>>>>>>>>>> inet_listener imaps { >>>>>>>>>>> port = 993 >>>>>>>>>>> ssl = yes >>>>>>>>>>> } >>>>>>>>>>> } >>>>>>>>>>> service pop3-login { >>>>>>>>>>> inet_listener pop3 { >>>>>>>>>>> port = 110 >>>>>>>>>>> } >>>>>>>>>>> inet_listener pop3s { >>>>>>>>>>> port = 995 >>>>>>>>>>> ssl = yes >>>>>>>>>>> } >>>>>>>>>>> } >>>>>>>>>>> ssl_cert = >>>>>>>>>> ssl_key = >>>>>>>>>> userdb { >>>>>>>>>>> args = blocking=yes >>>>>>>>>>> driver = passwd >>>>>>>>>>> } >>>>>>>>>>> protocol imap { >>>>>>>>>>> mail_max_userip_connections = 50 >>>>>>>>>>> } >>>>>>>>>>> protocol lda { >>>>>>>>>>> mail_plugins = sieve >>>>>>>>>>> } >>>> >>>> -- >>>> C. J. Keist Email: cj.keist at colostate.edu >>>> Systems Group Manager Solaris 10 OS (SAI) >>>> Engineering Network Services Phone: 970-491-0630 >>>> College of Engineering, CSU Fax: 970-491-5569 >>>> Ft. Collins, CO 80523-1301 >>>> >>>> All I want is a chance to prove 'Money can't buy happiness' >> >> -- >> C. J. Keist Email: cj.keist at colostate.edu >> Systems Group Manager Solaris 10 OS (SAI) >> Engineering Network Services Phone: 970-491-0630 >> College of Engineering, CSU Fax: 970-491-5569 >> Ft. Collins, CO 80523-1301 >> >> All I want is a chance to prove 'Money can't buy happiness' From mtrainer at westnet.com.au Tue Jul 15 04:27:41 2014 From: mtrainer at westnet.com.au (Murray Trainer) Date: Tue, 15 Jul 2014 12:27:41 +0800 Subject: Integrity check of mailboxes before dsync Message-ID: <21337b99a921ce260b9ad60fc168c95183dfa999@webmail.westnet.com.au> Hi All, I am migrating a large number of Dovecot mailboxes - some of them are quite old.? I hit an issue yesterday with a corrupt file (index?) that was preventing the mailbox from being synced properly? As soon as I removed the file the dsync worked.? Is there a way to check the integrity of each mailbox / indexes before I dsync it??? Thanks Murray From rs at sys4.de Tue Jul 15 05:35:32 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 15 Jul 2014 07:35:32 +0200 Subject: Changed IMAP MOVE behavior in Dovecot 2.2.x In-Reply-To: <20140714144518.Horde.YkmZDMt8flj5eihYjh0A-A9@bigworm.curecanti.org> References: <20140714144518.Horde.YkmZDMt8flj5eihYjh0A-A9@bigworm.curecanti.org> Message-ID: <53C4BDA4.6060506@sys4.de> Am 14.07.2014 22:45, schrieb Michael M Slusarz: > Quoting Iavor Stoev : > >> Hello, >> >> After the migration to Dovecot 2.2.13 from Dovecot 2.1.17, >> I noticed a changed behavior when I move a message from one folder to >> another. I use Thunderbird with: Account Settings -> Server Settings >> -> When I delete a message: Just mark it as deleted. >> >> I use Thunderbird 24.6.0 with IMAP. >> >> With Dovecot 2.1.x when I move a message, the message appears in the >> new folder and is marked for deletion in the original folder (which >> gives me an easy option to undo the action if I made a mistake until I >> choose to Compact/Purge the folder). >> >> With Dovecot 2.2.x when I move the a message it is marked for deletion >> and is AUTO Compacted/Purged immediately. >> >> Is there a way to achieve the 2.1.x behavior with Dovecot 2.2.x? > > Dovecot 2.2 implemented the new IMAP MOVE extension, which Thunderbird > is using. Short of manually removing MOVE from Dovecot's CAPABILITY > listing, there's not much you can do since I don't think Thunderbird > provides an easy way to alter the low-level IMAP interaction. > > The IMAP MOVE functionality is much preferred over your expected > behavior since a COPY/STORE/EXPUNGE (how you must do a move without the > MOVE extension) is not atomic and can leave the mailbox(es) in an > inconsistent state. > > Leaving a copy of the message in the original mailbox, that requires > manual deletion, is most definitely not what most users expect for a > move, even given a liberal interpretation of "move", so you are > describing a very non-standard way of accessing your mailboxes. > > michael great you point that out , i missed this Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From maciej.uhlig at us.edu.pl Tue Jul 15 05:55:27 2014 From: maciej.uhlig at us.edu.pl (Maciej Uhlig) Date: Tue, 15 Jul 2014 07:55:27 +0200 Subject: Fatal: master: service(imap): child 20258 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) In-Reply-To: <9D3ABD35-B9D4-42BE-B4DF-C73C9E15DAC7@colostate.edu> References: <53BEAB95.4000802@colostate.edu> <53BEACBB.6040609@colostate.edu> <53BEB1FA.3000902@colostate.edu> <53BEB4FD.5070502@thelounge.net> <53BEB63C.7010604@colostate.edu> <53BEB951.8070002@colostate.edu> <53BEC0ED.8010906@colostate.edu> <53BEDC61.4060706@colostate.edu> <71984EBD-3257-455D-9502-740CA9DB248E@iki.fi> <53C42B08.7020106@colostate.edu> <9D3ABD35-B9D4-42BE-B4DF-C73C9E15DAC7@colostate.edu> Message-ID: <53C4C24F.8060202@us.edu.pl> Just a remark: this issue (Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc)) was reported by me on 2014-01-11 on 2.2.10, it still occurs on 2.2.13. Indeed, we also switched from sparc server to x86. We also removed all the dovecot indexes. We use maildir only. However, the issue persists and I can observe this panic almost every day. Thanks. MU CJ Keist - 2014-07-15 06:22: > Yes, > I did switch from sparc server to x86. I also removed all the dovecot.indexes and .imap folders. I will try 2.2 again tomorrow with the process limits specified for imap, pop, and auth. > My concern is with auto detection of user accounts using mbox or Maildir formats. Is it still the case to support mix mbox and Maildir by commenting out the mail_location lines? > > > >> On Jul 14, 2014, at 4:50 PM, Timo Sirainen wrote: >> >> Did you actually switch from sparc to x86 CPU in the server? If yes, then looks like the code to handle the switching could use some fixing. >> >> But in any case you can just delete the .imap/ directories and have the indexes be rebuilt. >> >>> On 14.7.2014, at 21.10, CJ Keist wrote: >>> >>> >>> Jul 10 00:20:00 mail2 dovecot: [ID 583609 mail.crit] imap(tjs): Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3354 bytes Desc: Kryptograficzna sygnatura S/MIME URL: From h.reindl at thelounge.net Tue Jul 15 08:43:32 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 15 Jul 2014 10:43:32 +0200 Subject: ATrpms repo In-Reply-To: <20140715034233.GA97784@aura.veggiechinese.net> References: <20140715034233.GA97784@aura.veggiechinese.net> Message-ID: <53C4E9B4.5090501@thelounge.net> Am 15.07.2014 05:42, schrieb Will Yardley: > Tried mailing the maintainer, but didn't get a response -- anyone know > what's happened to the ATrpms repo? > > Not only is > http://atrpms.net/name/dovecot/ > empty, but: > http://packages.atrpms.net/dist/el6/ > seems to return a 404. Some of the mirrors still have the packages, but > does anyone know if they're going to continue to build 2.2.x packages? avoid ATrpms enable this repo unconditionally sooner or later will *** your OS installation because he overrides base packages often in incompatible ways and mixed with sane repos like rpmfusion years ago already leaded in randomly crashing applications additionally the packages are poor tested i remember a WLAN driver which crashed my system after an update and the reponse was "sorry typo" which means for me careless maintaining -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From nick.z.edwards at gmail.com Tue Jul 15 09:13:26 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Tue, 15 Jul 2014 19:13:26 +1000 Subject: If local Dovecot stops working, check lo In-Reply-To: <53C308A0.1020501@thinline.cz> References: <20140712073129.0e208f57@mydesq2.domain.cxm> <53C308A0.1020501@thinline.cz> Message-ID: On 7/14/14, Jiri Bourek wrote: > On 14.7.2014 00:24, Nick Edwards wrote: >> On 7/12/14, Steve Litt wrote: >> >>> experience with Debian Wheezy is that lo "goes down" a lot, so this is >>> one of the first things I do when odd stuff happens. >>> >> >> Use a better operating system then > > Blaming operating system after *one* person reports something strange > about it seems a bit overboard, doesn't it...? > debian has a long history of being clueless: old packages in new releases, untested packages in releases (mailscanner did not, and was never going to, work out of thebox in a recent release) debian has history of thinking it knows better than upstream: openssl screwup they told debian was wrong but debian released it anyway causing grief for not only debian systems but all systems including windows that used certs generated on a debi\an server. and dont get me started on debians release/ftp manager and the personal biases there either, shall I go? I can but it would be a bore for most. From nick.z.edwards at gmail.com Tue Jul 15 09:19:10 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Tue, 15 Jul 2014 19:19:10 +1000 Subject: Postfix user@domain splitting In-Reply-To: <53C45350.3080102@wenn.com> References: <53C45350.3080102@wenn.com> Message-ID: you need to show doveconf -n and what you have in the master.conf for dovecot On 7/15/14, Ricardo Branco wrote: > I have been trying looking though all the wiki documents to setup LMTP. > It now seems to all be connected except that it keeps saying that the > user is not recognised when postfix sends to LMTP, it sends the full > recipent email address but seems that on the dovecot side it is unable > to work with this. > I have checked the userdb and made sure its using %n but alas it still > does not work. > Currently ive had to revert to using LDA as it works fine with that but > i still dont know how as the postfix config variable $RECIPIENT is the > full email address and does not seem to matter to LDA. > From skdovecot at smail.inf.fh-brs.de Tue Jul 15 09:40:11 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 15 Jul 2014 11:40:11 +0200 (CEST) Subject: Permissions with mailman In-Reply-To: <20140704040319.5b25f330@compul-debian.me.org> References: <20140702154956.13103a04@compul-debian.me.org> <20140704020342.64ab3398@compul-debian.me.org> <53B5B3BA.5010509@tigertech.com> <20140704040319.5b25f330@compul-debian.me.org> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 4 Jul 2014, Niklas Lemcke - ??? wrote: > On Thu, 03 Jul 2014 12:49:14 -0700 Robert L Mathews wrote: >> On 7/3/14, 11:03 AM, Niklas Lemcke - ??? wrote: >> >>> Jul 2 15:29:39 blade01 dovecot: lda(list): Error: user list: >>> Initialization failed: Initializing mail storage from mail_location >>> setting failed: mkdir(/var/mail/vmail//list/mail) failed: Permission >>> denied (euid=38(list) egid=38(list) >> >>> Now since dovecot is running as user vmail >> >> According to the error, it's not running as user vmail for this >> delivery. It's running as uid/gid 38, "list". >> >> Look at how "lda" gets executed for this delivery to see why it's using >> uid 38. >> > > I'm not sure why it's using uid 38, but even so, the user list is in the > group vmail and thus should be able to write to /var/mail/vmail. > However it reports it's not in the group. > > => confused is it possible that Dovecot cannot read /etc/group ? Maybe you can strace the Dovecot LDA and see something in the trace. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU8T2+3z1H7kL/d9rAQLMTAf/ZFovEOpyXMPqlOJxWR4Sgrm+grv0hhZV +pFnerDeDxKJxWGJ5LcfQaNWGQTMR1L3Hu7wiZ4Pk79tmaL0J3QRmBDCcXIh63Uu mLFnzJcDx9wtZ5lVzOELabrHEedmLScAEaqXmuz30hVdHM/uL/h5+RU1FmOQSvjB HKLs1HiGTkUaqazVY4lMM7Ig1MurqzWzOnko0VwnP5yVYSmQyO+V02T1TV7gulsB lOXR+cKHxcRm6IXnGTEKhm2Q4JFi+45Ny/RvnHb3nUsls3n2YZ6TPHFA2P9WrCEn +kOoKGCzXIqW3tz8GY4zemxWsF+iasoaux2OuQzAsHsTEHcOYcdasw== =fogh -----END PGP SIGNATURE----- From bourek at thinline.cz Tue Jul 15 09:46:36 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 15 Jul 2014 11:46:36 +0200 Subject: If local Dovecot stops working, check lo In-Reply-To: References: <20140712073129.0e208f57@mydesq2.domain.cxm> <53C308A0.1020501@thinline.cz> Message-ID: <53C4F87C.50602@thinline.cz> On 15.7.2014 11:13, Nick Edwards wrote: > On 7/14/14, Jiri Bourek wrote: >> On 14.7.2014 00:24, Nick Edwards wrote: >>> On 7/12/14, Steve Litt wrote: >>> >>>> experience with Debian Wheezy is that lo "goes down" a lot, so this is >>>> one of the first things I do when odd stuff happens. >>>> >>> >>> Use a better operating system then >> >> Blaming operating system after *one* person reports something strange >> about it seems a bit overboard, doesn't it...? >> > debian has a long history of being clueless: > old packages in new releases, untested packages in releases > (mailscanner did not, and was never going to, work out of thebox in a > recent release) As most Linux distributions, Debian is a collective work done mostly by volunteers. If you want newer versions and tested packages, feel free to help them. And honestly, the situation about untested and old packages isn't as grim as you're trying to say. > > debian has history of thinking it knows better than upstream: > openssl screwup they told debian was wrong but debian released it > anyway causing grief for not only debian systems but all systems > including windows that used certs generated on a debi\an server. AFAIK it was actually the other way around. Debian maintainers asked on openssl-dev list if their change is ok and were told that it is. > > and dont get me started on debians release/ftp manager and the > personal biases there either, shall I go? I can but it would be a bore > for most. > As far as I am concerned, there's no need to be more OT than we are now. Also please stop sending me personal messages, I am on the list. From lazy404 at gmail.com Tue Jul 15 09:53:28 2014 From: lazy404 at gmail.com (Lazy) Date: Tue, 15 Jul 2014 11:53:28 +0200 Subject: fts solr database size Message-ID: Hi, Could anyone share any numbers about real life solr database size/cpu/memory usage for certain amounts of messages ? We have now over 5TB of maildirs (about 5 000-6 000 concurrent imap clients) and I'm trying to guess how much hardware might be needed. -- Michal From jost+lists at dimejo.at Tue Jul 15 10:30:31 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Tue, 15 Jul 2014 12:30:31 +0200 Subject: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) In-Reply-To: <53C47FFB.4040901@blackrosetech.com> References: <53C47FFB.4040901@blackrosetech.com> Message-ID: <53C502C7.90803@dimejo.at> Am 15.07.2014 03:12, schrieb David Gessel: > * In thunderbird, I get constant downloading of messages. Every time I > switch to the inbox from another folder, the messages start > redownloading. This sometimes, but not always, seems to create > duplicate messages, but I'm now fairly sure they are only created in the > client and not on the server. Searching through various forums, it > appears this has been a problem for Thunderbird for some time, but it > wasn't for me on Courier. As posts about similar errors seem to have > petered out over the last year without any clear guidance on how to fix > it that I could find, I expect there's a simple fix I just haven't found > yet, either in TB configuration or in Dovecot. Any hints? I tried > Thunderfix to remove the .msf files and will be redownloading my mail > over the thin pipe out to Iraq for the next 6 months (DOH!). One > artifact is that when I restart thunderbird, my inbox is reported as > having about 130 messages in it, then thunderbird starts redownloading > headers and eventually gets back up to the 1297 currently listed both in > the TB pane and by ls | wc -l in /cur. Is it possible there is a time > out that needs to be extended? In TB, I've set (among other less > apparently relevant options) > mailnews.tcptimeout;1000 > mail.db.idle_limit;30000000 How old is your Thunderbird profile. Have you tried creating a new one and see if the problem persists? Thunderfix should not be needed by the way. Just right click on the folder => Properties => Repair > server # dovecot -n > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > # OS: FreeBSD 9.2-RELEASE amd64 > auth_default_realm = mydomain.com > auth_mechanisms = plain login > auth_realms = mydomain.com mydomain2.org > disable_plaintext_auth = no > first_valid_gid = 5000 > first_valid_uid = 5000 > hostname = mydomain.com > imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags > imap_idle_notify_interval = 29 mins > last_valid_gid = 5000 > last_valid_uid = 5000 > lda_mailbox_autocreate = yes > listen = * > mail_gid = 5000 > mail_location = maildir:~/:CONTROL=/var/no-quota/%u > mail_plugins = quota mail_log notify > mail_temp_dir = /var/tmp > mail_uid = 5000 > maildir_broken_filename_sizes = yes > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date ihave duplicate spamtest spamtestplus editheader > mbox_lazy_writes = no > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = /usr/local/etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > plugin { > expire = Trash > mail_log_events = delete undelete expunge copy mailbox_delete > mailbox_rename > mail_log_fields = uid box msgid size > quota = maildir:User quota > quota_exceeded_message = Storage quota for this account has been > exceeded, please try again later. > quota_rule = *:storage=50G > quota_rule2 = Trash:storage=+30%% > quota_rule3 = Sent:storage=+30%% > quota_warning = storage=90%% quota-warning 90 %u > quota_warning2 = storage=75%% quota-warning 75 %u > sieve = ~/.dovecot.sieve > sieve_before = /usr/local/etc/dovecot/sieve/ > sieve_dir = ~/sieve > sieve_extensions = +spamtest +spamtestplus +relational > +comparator-i;ascii-numeric +editheader > } > postmaster_address = gessel at mydomain.com > protocols = imap lmtp sieve sieve > sendmail_path = /usr/local/sbin/sendmail > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > unix_listener auth-userdb { > group = vmail > mode = 0600 > user = vmail > } > } > service managesieve-login { > inet_listener sieve { > port = 4190 > } > service_count = 1 > vsz_limit = 128 M > } > service quota-warning { > executable = script /usr/local/bin/quota-warning.sh > unix_listener quota-warning { > user = vmail > } > user = vmail > } > ssl = required > ssl_cert = ssl_cipher_list = > ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES256-SHA:!SSLv2 > ssl_key = ssl_prefer_server_ciphers = yes > userdb { > driver = prefetch > } > userdb { > args = /usr/local/etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > protocol lda { > mail_plugins = quota mail_log notify sieve > } > protocol imap { > mail_max_userip_connections = 20 > mail_plugins = quota mail_log notify imap_quota imap_zlib > } > protocol lmtp { > mail_plugins = quota mail_log notify sieve > } > I don't know if it makes a difference for you as you are not using "LAYOUT=fs" but try to disable those imap_client_workarounds. -- Alex JOST From ricardo at wenn.com Tue Jul 15 11:05:59 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Tue, 15 Jul 2014 12:05:59 +0100 Subject: fts solr database size In-Reply-To: References: Message-ID: <53C50B17.7020309@wenn.com> We are no way as big as you but in terms users but our user vs mailbox size is large. Dovecot: 50 users 425Gb (mdbox + zlib) Note solr only indexes folders within a mailbox when a search is done on them so size can vary and most people dont realise that the default type of search in Thunderbird is on Sender/Recipients/Subject which happens localy and not on the server so you dont get solr indexing unless the user does a custom search and forces remote. Webmail systems though will tend to do server searches. Solr: Num Docs: 17m Size: 4.5GB Lazy wrote, On 15/07/2014 10:53: > Hi, > > Could anyone share any numbers about real life solr database > size/cpu/memory usage for > certain amounts of messages ? > > We have now over 5TB of maildirs (about 5 000-6 000 concurrent imap clients) > and I'm trying to guess how much hardware might be needed. > From ricardo at wenn.com Tue Jul 15 11:12:08 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Tue, 15 Jul 2014 12:12:08 +0100 Subject: Postfix user@domain splitting In-Reply-To: References: <53C45350.3080102@wenn.com> Message-ID: <53C50C88.4070300@wenn.com> Attached files Nick Edwards wrote, On 15/07/2014 10:19: > you need to show doveconf -n > and what you have in the master.conf for dovecot > > On 7/15/14, Ricardo Branco wrote: >> I have been trying looking though all the wiki documents to setup LMTP. >> It now seems to all be connected except that it keeps saying that the >> user is not recognised when postfix sends to LMTP, it sends the full >> recipent email address but seems that on the dovecot side it is unable >> to work with this. >> I have checked the userdb and made sure its using %n but alas it still >> does not work. >> Currently ive had to revert to using LDA as it works fine with that but >> i still dont know how as the postfix config variable $RECIPIENT is the >> full email address and does not seem to matter to LDA. >> -------------- next part -------------- # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.20.3.el6.x86_64 x86_64 CentOS release 6.5 (Final) auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_ auth_username_format = %n base_dir = /var/run/dovecot/ debug_log_path = /var/log/imapd_debug.log deliver_log_format = msgid=%m: , From:%f , Subject:%s , Status:%$ disable_plaintext_auth = no dotlock_use_excl = no info_log_path = /var/log/imapd_info.log log_path = /var/log/imapd.log login_greeting = I am ready. mail_cache_min_mail_count = 5 mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = acl zlib fts fts_solr fts_squat mail_privileged_group = mail maildir_stat_dirs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate imapflags notify mdbox_rotate_interval = 1 days mmap_disable = yes namespace { location = maildir:/home/public prefix = Public/ separator = / subscriptions = no type = public } namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } plugin { acl = vfile antispam_allow_append_to_spam = no antispam_backend = mailtrain antispam_debug_target = /var/log/imapd_debug.log antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn-pipe.sh antispam_mail_spam = --spam antispam_signature = X-WENN-MailScanner-SpamCheck antispam_signature_missing = error antispam_spam_pattern_ignorecase = SPAM antispam_spool2dir_notspam = /tmp/spamspool/.HAM/%%020lu-%u-%%05luh antispam_spool2dir_spam = /tmp/spamspool/.SPAM/%%020lu-%u-%%05lus antispam_tmp = /tmp antispam_trash_pattern_ignorecase = mail-trash;Trash;*Deleted* antispam_unsure = CHECK4SPAM antispam_verbose_debug = 1 fts = solr fts_solr = break-imap-search url=http://db.wenn.com:8983/solr/dovecot/ fts_squat = partial=4 full=10 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags zlib_save = gz zlib_save_level = 2 } protocols = imap pop3 sieve lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } user = dovecot } service imap-login { process_min_avail = 2 service_count = 10 vsz_limit = 128 M } service imap-postlogin { executable = script-login /root/bin/imap_login_checks.sh } service imap { executable = imap imap-postlogin vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-postlogin { executable = script-login /root/bin/pop3_login_checks.sh } service pop3 { executable = pop3 pop3-postlogin } ssl_cert = service_count = 10 # Number of processes to always keep waiting for more connections. process_min_avail = 2 # If you set service_count=0, you probably need to grow this. vsz_limit = 128M } service pop3-login { inet_listener pop3 { #port = 110 } inet_listener pop3s { #port = 995 #ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { #mode = 0666 group = postfix mode = 0600 user = postfix } # Create inet listener only if you can't use the above UNIX socket inet_listener lmtp { # Avoid making LMTP visible for the entire internet address = 127.0.0.1 port = 24 } } service imap { executable = imap imap-postlogin # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. vsz_limit = 512M # Max. number of IMAP processes (connections) #process_limit = 1024 } service imap-postlogin { executable = script-login /root/bin/imap_login_checks.sh unix_listener imap-postlogin { } } service pop3 { executable = pop3 pop3-postlogin # Max. number of POP3 processes (connections) #process_limit = 1024 } service pop3-postlogin { executable = script-login /root/bin/pop3_login_checks.sh unix_listener pop3-postlogin { } } service auth { # auth_socket_path points to this userdb socket by default. It's typically # used by dovecot-lda, doveadm, possibly imap process, etc. Its default # permissions make it readable only by root, but you may need to relax these # permissions. Users that have access to this socket are able to get a list # of all usernames and get results of everyone's userdb lookups. unix_listener auth-userdb { #mode = 0600 #user = #group = } # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } # Auth process is run as this user. #user = $default_internal_user user = dovecot } service auth-worker { # Auth worker process is run as root by default, so that it can access # /etc/shadow. If this isn't necessary, the user should be changed to # $default_internal_user. #user = root } service dict { # If dict proxy is used, mail processes should have access to its socket. # For example: mode=0660, group=vmail and global mail_access_groups=vmail unix_listener dict { #mode = 0600 #user = #group = } } From gessel at blackrosetech.com Tue Jul 15 12:08:31 2014 From: gessel at blackrosetech.com (David Gessel) Date: Tue, 15 Jul 2014 15:08:31 +0300 Subject: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) In-Reply-To: <53C502C7.90803@dimejo.at> References: <53C47FFB.4040901@blackrosetech.com> <53C502C7.90803@dimejo.at> Message-ID: <53C519BF.6050803@blackrosetech.com> -------- Original Message -------- Subject: Re: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) From: Alex JOST To: dovecot at dovecot.org Date: Tue Jul 15 2014 13:30:31 GMT+0300 (Arabic Standard Time) > Am 15.07.2014 03:12, schrieb David Gessel: >> * In thunderbird, I get constant downloading of messages. Every time I >> switch to the inbox from another folder, the messages start >> redownloading. This sometimes, but not always, seems to create >> duplicate messages, but I'm now fairly sure they are only created in the >> client and not on the server. Searching through various forums, it >> appears this has been a problem for Thunderbird for some time, but it >> wasn't for me on Courier. As posts about similar errors seem to have >> petered out over the last year without any clear guidance on how to fix >> it that I could find, I expect there's a simple fix I just haven't found >> yet, either in TB configuration or in Dovecot. Any hints? I tried >> Thunderfix to remove the .msf files and will be redownloading my mail >> over the thin pipe out to Iraq for the next 6 months (DOH!). One >> artifact is that when I restart thunderbird, my inbox is reported as >> having about 130 messages in it, then thunderbird starts redownloading >> headers and eventually gets back up to the 1297 currently listed both in >> the TB pane and by ls | wc -l in /cur. Is it possible there is a time >> out that needs to be extended? In TB, I've set (among other less >> apparently relevant options) >> mailnews.tcptimeout;1000 >> mail.db.idle_limit;30000000 > > How old is your Thunderbird profile. Have you tried creating a new one > and see if the problem persists? It is a new profile created with the transition from Cyrus to Dovecot about a week ago, but I used IMAPSync to move all my mail from the ancient Cyrus server to the shiny new Dovecot server. I then deleted the old profile. > > Thunderfix should not be needed by the way. Just right click on the > folder => Properties => Repair I did see that, but first thought there was something magic about "thunderfix" then decided to use it anyway because I have annual sent/recieved archives from 2000 (and one for pre-2000) so that would have been a lotta right-clicking. > > >> server # dovecot -n >> # 2.2.13: /usr/local/etc/dovecot/dovecot.conf >> # OS: FreeBSD 9.2-RELEASE amd64 >> auth_default_realm = mydomain.com >> auth_mechanisms = plain login >> auth_realms = mydomain.com mydomain2.org >> disable_plaintext_auth = no >> first_valid_gid = 5000 >> first_valid_uid = 5000 >> hostname = mydomain.com >> imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags >> imap_idle_notify_interval = 29 mins >> last_valid_gid = 5000 >> last_valid_uid = 5000 >> lda_mailbox_autocreate = yes >> listen = * >> mail_gid = 5000 >> mail_location = maildir:~/:CONTROL=/var/no-quota/%u >> mail_plugins = quota mail_log notify >> mail_temp_dir = /var/tmp >> mail_uid = 5000 >> maildir_broken_filename_sizes = yes >> managesieve_notify_capability = mailto >> managesieve_sieve_capability = fileinto reject envelope >> encoded-character vacation subaddress comparator-i;ascii-numeric >> relational regex imap4flags copy include variables body enotify >> environment mailbox date ihave duplicate spamtest spamtestplus editheader >> mbox_lazy_writes = no >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> args = /usr/local/etc/dovecot/dovecot-sql.conf.ext >> driver = sql >> } >> plugin { >> expire = Trash >> mail_log_events = delete undelete expunge copy mailbox_delete >> mailbox_rename >> mail_log_fields = uid box msgid size >> quota = maildir:User quota >> quota_exceeded_message = Storage quota for this account has been >> exceeded, please try again later. >> quota_rule = *:storage=50G >> quota_rule2 = Trash:storage=+30%% >> quota_rule3 = Sent:storage=+30%% >> quota_warning = storage=90%% quota-warning 90 %u >> quota_warning2 = storage=75%% quota-warning 75 %u >> sieve = ~/.dovecot.sieve >> sieve_before = /usr/local/etc/dovecot/sieve/ >> sieve_dir = ~/sieve >> sieve_extensions = +spamtest +spamtestplus +relational >> +comparator-i;ascii-numeric +editheader >> } >> postmaster_address = gessel at mydomain.com >> protocols = imap lmtp sieve sieve >> sendmail_path = /usr/local/sbin/sendmail >> service auth { >> unix_listener /var/spool/postfix/private/auth { >> group = postfix >> mode = 0666 >> user = postfix >> } >> unix_listener auth-userdb { >> group = vmail >> mode = 0600 >> user = vmail >> } >> } >> service managesieve-login { >> inet_listener sieve { >> port = 4190 >> } >> service_count = 1 >> vsz_limit = 128 M >> } >> service quota-warning { >> executable = script /usr/local/bin/quota-warning.sh >> unix_listener quota-warning { >> user = vmail >> } >> user = vmail >> } >> ssl = required >> ssl_cert = > ssl_cipher_list = >> ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES256-SHA:!SSLv2 >> >> ssl_key = > ssl_prefer_server_ciphers = yes >> userdb { >> driver = prefetch >> } >> userdb { >> args = /usr/local/etc/dovecot/dovecot-sql.conf.ext >> driver = sql >> } >> protocol lda { >> mail_plugins = quota mail_log notify sieve >> } >> protocol imap { >> mail_max_userip_connections = 20 >> mail_plugins = quota mail_log notify imap_quota imap_zlib >> } >> protocol lmtp { >> mail_plugins = quota mail_log notify sieve >> } >> > > I don't know if it makes a difference for you as you are not using > "LAYOUT=fs" but try to disable those imap_client_workarounds. > Good catch, thank you. (I used LAYOUT=fs at first, but found behavior a little anomalous. I forgot to disable the workarounds). This may have stopped the problem of redownloading the entire mailbox (on restart I got downloading 1 of 8 instead of 1 of 170... 30 of 1330 in the status pane) . My other mailboxes still need to sync and it might take a few days to verify that things are stable. I did get 81 immediate "Warning: Maildir /mail/mydomain.com/gessel//.Bulkmail: Expunged message reappeared, giving a new UID" warnings on connect, but if this is the problem, it might stop after all the directories are resynced. I'll update with further data as it comes in. I am also somewhat suspect of QRSYNC from this post: http://dovecot.org/pipermail/dovecot/2011-August/130687.html - though this is from a long time ago and it seems a little surprising that bugs on this seemingly useful capability would persist. In any event (if useful information), my capability enumeration reads: # telnet localhost 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a login user pass a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE COMPRESS=DEFLATE QUOTA] Logged in I did try setting mail.server.default.use_condstore;false in Thunderbird, but that didn't change the behavior of reloading the entire inbox on startup so I've changed that back as that wasn't the desired result. From skdovecot at smail.inf.fh-brs.de Tue Jul 15 12:18:41 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 15 Jul 2014 14:18:41 +0200 (CEST) Subject: Postfix user@domain splitting In-Reply-To: <53C50C88.4070300@wenn.com> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 15 Jul 2014, Ricardo Branco wrote: > Attached files > > Nick Edwards wrote, On 15/07/2014 10:19: >> you need to show doveconf -n >> and what you have in the master.conf for dovecot >> >> On 7/15/14, Ricardo Branco wrote: >>> I have been trying looking though all the wiki documents to setup LMTP. >>> It now seems to all be connected except that it keeps saying that the >>> user is not recognised when postfix sends to LMTP, it sends the full >>> recipent email address but seems that on the dovecot side it is unable >>> to work with this. >>> I have checked the userdb and made sure its using %n but alas it still >>> does not work. userdb { args = username_format=%u /etc/passwd driver = passwd-file name = passwd-file } In opposite to your sentence I see a %u there. >>> Currently ive had to revert to using LDA as it works fine with that but >>> i still dont know how as the postfix config variable $RECIPIENT is the >>> full email address and does not seem to matter to LDA. >>> > > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU8UcInz1H7kL/d9rAQKXQAgAmu6NnZOqdQKEgKhk6q/CPtXza+dkUh7f 4Ms2tJFw2krwKNeZOvKGOsEeD7XyFDYpfZFDqEewjffqlABUUytIRPXzD3xFvzXV DuXTW1VseEP26ewR7odHN9J+WL1Unh52HnxFgM63Bo1IwYzF84K09VO3DxqobuF7 S8MqQYj6MPqB73IZUbVzRkCDBM0mv52Gx14LFmmPXbphgZFmtixkUy2CpPOT/l02 0aBSsJZqV/ySKcB2V5UNCj8GoGvwyH3Jh9RFeNIlUKYZYT9s534rfbKu7+T6645I 67daEtZjfAbBOi/foqh41kbSpSaHIMvF970EP/EozFgMBsnghQ+SLg== =6YKs -----END PGP SIGNATURE----- From kmansoft at gmail.com Tue Jul 15 13:00:19 2014 From: kmansoft at gmail.com (Kostya Vasilyev) Date: Tue, 15 Jul 2014 17:00:19 +0400 Subject: HIGHESTMODSEQ tracking In-Reply-To: <20140714174719.Horde.px3Mk2olwJghwWJ-q5T5kw6@bigworm.curecanti.org> References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> <20140714174719.Horde.px3Mk2olwJghwWJ-q5T5kw6@bigworm.curecanti.org> Message-ID: 2014-07-15 3:47 GMT+04:00 Michael M Slusarz : > Quoting Kostya Vasilyev : > > >> Gmail still does have a few users, though. A few dozen at least, maybe >> more >> :) >> >> And it has a big advantage, from my point of view, over Cyrus / Dovecot -- >> there is but one server version that's consistent for all accounts. >> >> Yes, they do some things wrong (like not sending message flags changes >> over >> IDLE connections), but I can test something in my personal account, get >> feedback from 3-5-10 users with @gmail accounts, and be reasonably >> confident that everything is fine (and that I'd know know if it's not). >> > > This is getting a bit off-topic on this list... but Gmail does a LOT of > things wrong. Head over to one of the IMAP lists for further information. > This is just one glaring example. Maybe you've ran into more than I have. In any case, the point stands - with Gmail, it's much easier to be confident, from actual testing, that things works a certain way. > > If you are testing against Gmail as the gold standard as to how a IMAP > server should operate, I never said or implied that. In fact, I pointed out a serious issue with Gmail's IMAP IDLE implementation, which means the exact opposite of holding it as a gold standard. > I can safely say you are Doing It Wrong. It seems you enjoy pointing out to people when they're "wrong" or "incorrect" so much, you actually put meaning into their words that's not there? Or it it just me? > > > For the "more than 50% market share" of Dovecot / Cyrus, do you have a >> breakdown by version number? At least in terms of 1.* vs 2.0 and higher? >> > > I do not. And without being able to get a version number from a Dovecot session (or so it seems to me -- nothing returned from ID...).... it looks kind of sad. > > > Maybe. You can't tell until you actually see whether the EXAMINE/SELECT >>> returns HIGHESTMODSEQ or NOMODSEQ. >>> >> >> Are you saying that Dovecot will always (*will always*, and I mean >> *always*) return NOMODSEQ after a client "expresses interested in modseq >> values" and the server can't enable it for some reason? >> > > Much like UIDVALIDITY should never change, NOMODSEQ will never be sent > (practical usage) for an active CONDSTORE access. You are asking about a > tremendously rare occurrence. > In theory, yes, but I just wouldn't want to be surprised (and surprise my users). > > The whole deal with "HIGHESTMODSEQ 1" is irrelevant if you enable > CONDSTORE. I can't tell you what a server will return if you enable > CONDSTORE in one session, but then don't in another. But that doesn't > matter, since you aren't using HIGHESTMODSEQ in the latter case. As long > as CONDSTORE is active, HIGHESTMODSEQ will be updated, at least in my 6 > year experience with Dovecot which involves handling installations with > millions of users. Thank you. This is the type of response, based on actual real-world experience, that I was looking for. > > > Or if it was previously enabled, and then well, I don't know, "something >> happened"? >> >> By *always* I mean -- since Dovecot first started having a CONDSTORE in >> its >> CAPS, including version a.b.c that came with now really old Debian X, and >> version h.j.k that came with now really old RHEL Y, but which are still >> out >> there on actual mail servers, being used in actual mail accounts? >> > > I have never run into an issue with HIGHESTMODSEQ for a properly > CONDSTORE-enabled session for Dovecot ever. I was one of the first people > (that I am aware of) that implemented CONDSTORE/QRESYNC back in the early > days (2009) ... and Dovecot was exclusively the server I was developing > with at that time. Great. Thank you again for a data point that comes from the real world. > > > When something goes wrong in an email app, then to the user, it's always >> the email app developer's fault. Nobody gives a damn about the subtleties >> of what RFC abc says about xyz, or if server version j.k.l from three >> years >> ago had a bug. >> > > Agree, but only up to a certain point. If something is so onerous to work > around, then it *is* ok to say "it's the server's fault and we're not going > to work around this." Like everything else in life, there is a > cost/benefit analysis that must be done to determine where that line needs > to be drawn. Using modseq is an optimization. An optimization that makes things not work is not something I'd like to have. > > > So, before enabling certain optimizations for Dovecot, I thought I'd ask >> on >> a Dovecot mailing list, about actual behavior for this server feature. >> > > [snip] > > > There are certainly bugs - I found several of them years ago when the code > was brand new (here's a thread: http://markmail.org/message/ > fj74xta5z5uv4nix). But nothing that was showstopping. And none of those > versions are being run anymore for all intents and purposes. > > Thanks. It's somewhat worrying that enabling CONDSTORE just once will cause the server to always track modseq values from that point on -- causing new code paths to execute. But again, thanks for your data points rooted in the real world. -- K From info at babaei.net Tue Jul 15 13:00:13 2014 From: info at babaei.net (Mohammad S. Babaei) Date: Tue, 15 Jul 2014 17:30:13 +0430 Subject: Dovecot2 Antispam MAILTRAIN backend with SpamAssassin Message-ID: <27cdaa7b81ab5c586d83b8dbe69e4604@babaei.net> Hi there, I've already asked this question on FreeBSD forums without getting any response. So, I thought it's a good idea to ask it again here. I've setup Dovecote2 (2.2.13) + Postfix + SpamAssassin on my FreeBSD 10 VPS and it works flawlessly. Though, I couldn't setup the Dovecot Antispam plugin to train SpamAssassin when I move mails to the Junk folder. I installed the plugin from FreeBSD ports and followed the official documentation [1] and the man page [2] without any success. This is my configuration: ######## # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.0-RELEASE-p6 i386 ufs auth_mechanisms = plain login digest-md5 disable_plaintext_auth = no first_valid_gid = 6 first_valid_uid = 26 last_valid_gid = 6 last_valid_uid = 26 lmtp_save_to_detail_mailbox = yes mail_gid = mail mail_location = mdbox:/mail/%d/%u mail_privileged_group = mail mail_uid = mailnull managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Archive { auto = no special_use = Archive } mailbox Drafts { auto = subscribe special_use = Drafts } mailbox Flagged { auto = no special_use = Flagged } mailbox Junk { auto = subscribe special_use = Junk } mailbox Sent { auto = subscribe special_use = Sent } mailbox Trash { auto = subscribe special_use = Trash } mailbox virtual/All { auto = no special_use = All } prefix = separator = / } passdb { args = /mail/%d/dovecot_passwd driver = passwd-file } plugin { antispam_backend = MAILTRAIN antispam_mail_notspam = --ham antispam_mail_sendmail = /mail/sa-learn-pipe.sh antispam_mail_spam = --spam antispam_spam = Junk antispam_trash = Trash quota_rule = *:storage=8GB sieve = /mail/%d/%u/dovecot.sieve sieve_dir = /mail/%d/%u sieve_global_dir = /mail/sieve sieve_global_path = /mail/sieve/globalfilter.sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-client { group = mail mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0600 user = mailnull } user = root } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 32 process_min_avail = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_limit = 32 process_min_avail = 1 } ssl_cert = > /tmp/sa-learn-pipe.log #echo $* > /tmp/sendmail-parms.txt cat<&0 >> /tmp/sendmail-msg-$$.txt /usr/local/bin/sa-learn $* /tmp/sendmail-msg-$$.txt rm -f /tmp/sendmail-msg-$$.txt echo "$$-end" >> /tmp/sa-learn-pipe.log exit 0 ######## I made it excecutable by all users using chmod a+x /mail/sa-learn-pipe.sh The problem is, there is no log in /var/log/maillog regarding the Antispam plugin, and the script won't get called when I move any message in/out to/from Junk folder. I'll appreciate any help. -- "When I give, I give myself." - Walt Whitman Links: ------ [1] http://wiki2.dovecot.org/Plugins/Antispam [2] http://hg.dovecot.org/dovecot-antispam-plugin/raw-file/tip/doc/dovecot-antispam.7.txt From info at netocean.de Tue Jul 15 13:13:12 2014 From: info at netocean.de (=?ISO-8859-15?Q?Leander_Sch=E4fer?=) Date: Tue, 15 Jul 2014 15:13:12 +0200 Subject: Dovecot2 Antispam MAILTRAIN backend with SpamAssassin In-Reply-To: <27cdaa7b81ab5c586d83b8dbe69e4604@babaei.net> References: <27cdaa7b81ab5c586d83b8dbe69e4604@babaei.net> Message-ID: <53C528E8.9000003@netocean.de> I remember, that I also struggled for quite a while until I figured it out. Here is what I used on my FreeBSD Dovecot installation ... Remember, that the following code is working on "dovecot --version 1.2.12" ... but it could also be valid for later versions. I simply havn't checked it out yet. ### Dovecot AntiSpam ### # mail signature (used with any backend requiring a signature) #antispam_signature = X-Spam-Status #antispam_signature_missing = move antispam_mail_sendmail = /usr/local/etc/dovecot/sa-learn-helper.sh antispam_mail_sendmail_args = --username=%Lu antispam_mail_spam = --spam antispam_mail_notspam = --ham antispam_mail_tmpdir = /tmp antispam_spam = Spam #antispam_unsure = Virus antispam_trash = Trash echo '#!/usr/local/bin/bash #/usr/local/bin/sa-learn ${1} ${2} ${3} ${4} &> /var/log/DoveDamnAntiSpam.log /usr/local/bin/sa-learn "${1}" "${2}" "${3}" "${4}" exit 0 ' > /usr/local/etc/dovecot/sa-learn-helper.sh chmod 0777 /usr/local/etc/dovecot/sa-learn-helper.sh ; chown root:wheel /usr/local/etc/dovecot/sa-learn-helper.sh ; Best regards Leander Am 15.07.14 15:00, schrieb Mohammad S. Babaei: > > > Hi there, > > I've already asked this question on FreeBSD forums without getting any > response. So, I thought it's a good idea to ask it again here. > > I've setup Dovecote2 (2.2.13) + Postfix + SpamAssassin on my FreeBSD 10 > VPS and it works flawlessly. Though, I couldn't setup the Dovecot > Antispam plugin to train SpamAssassin when I move mails to the Junk > folder. > > I installed the plugin from FreeBSD ports and followed the official > documentation [1] and the man page [2] without any success. > > This is my configuration: > > ######## > > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > # OS: FreeBSD 10.0-RELEASE-p6 i386 ufs > auth_mechanisms = plain login digest-md5 > disable_plaintext_auth = no > first_valid_gid = 6 > first_valid_uid = 26 > last_valid_gid = 6 > last_valid_uid = 26 > lmtp_save_to_detail_mailbox = yes > mail_gid = mail > mail_location = mdbox:/mail/%d/%u > mail_privileged_group = mail > mail_uid = mailnull > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date ihave > namespace inbox { > inbox = yes > location = > mailbox Archive { > auto = no > special_use = Archive > } > mailbox Drafts { > auto = subscribe > special_use = Drafts > } > mailbox Flagged { > auto = no > special_use = Flagged > } > mailbox Junk { > auto = subscribe > special_use = Junk > } > mailbox Sent { > auto = subscribe > special_use = Sent > } > mailbox Trash { > auto = subscribe > special_use = Trash > } > mailbox virtual/All { > auto = no > special_use = All > } > prefix = > separator = / > } > passdb { > args = /mail/%d/dovecot_passwd > driver = passwd-file > } > plugin { > antispam_backend = MAILTRAIN > antispam_mail_notspam = --ham > antispam_mail_sendmail = /mail/sa-learn-pipe.sh > antispam_mail_spam = --spam > antispam_spam = Junk > antispam_trash = Trash > quota_rule = *:storage=8GB > sieve = /mail/%d/%u/dovecot.sieve > sieve_dir = /mail/%d/%u > sieve_global_dir = /mail/sieve > sieve_global_path = /mail/sieve/globalfilter.sieve > } > protocols = imap pop3 lmtp sieve > service auth { > unix_listener auth-client { > group = mail > mode = 0660 > user = postfix > } > unix_listener auth-master { > group = mail > mode = 0600 > user = mailnull > } > user = root > } > service imap-login { > inet_listener imap { > address = * > port = 143 > } > inet_listener imaps { > address = * > port = 993 > } > process_limit = 32 > process_min_avail = 1 > } > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0660 > user = postfix > } > } > service managesieve-login { > inet_listener sieve { > port = 4190 > } > process_min_avail = 0 > service_count = 1 > vsz_limit = 64 M > } > service managesieve { > process_limit = 1024 > } > service pop3-login { > inet_listener pop3 { > address = * > port = 110 > } > inet_listener pop3s { > address = * > port = 995 > } > process_limit = 32 > process_min_avail = 1 > } > ssl_cert = ssl_key = userdb { > args = /mail/%d/dovecot_passwd > driver = passwd-file > } > verbose_proctitle = yes > protocol lmtp { > mail_plugins = " sieve" > postmaster_address = postmaster at SomeDomain.com > quota_full_tempfail = yes > } > protocol sieve { > mail_max_userip_connections = 10 > managesieve_implementation_string = Dovecot Pigeonhole > managesieve_logout_format = bytes=%i/%o > managesieve_max_line_length = 65536 > } > protocol imap { > imap_client_workarounds = delay-newmail tb-extra-mailbox-sep > mail_plugins = " quota imap_quota antispam" > } > protocol pop3 { > mail_plugins = " quota" > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > } > protocol lda { > mail_plugins = " quota sieve" > postmaster_address = postmaster at SomeDomain.com > sendmail_path = /usr/local/sbin/sendmail > } > > ######## > > And, this is the script /mail/sa-learn-pipe.sh: > > ######## > > echo /usr/local/bin/sa-learn $* /tmp/sendmail-msg-$$.txt > echo "$$-start ($*)" >> /tmp/sa-learn-pipe.log > > #echo $* > /tmp/sendmail-parms.txt > cat<&0 >> /tmp/sendmail-msg-$$.txt > > /usr/local/bin/sa-learn $* /tmp/sendmail-msg-$$.txt > > rm -f /tmp/sendmail-msg-$$.txt > > echo "$$-end" >> /tmp/sa-learn-pipe.log > > exit 0 > > ######## > > I made it excecutable by all users using chmod a+x > /mail/sa-learn-pipe.sh > > The problem is, there is no log in /var/log/maillog regarding the > Antispam plugin, and the script won't get called when I move any message > in/out to/from Junk folder. > > I'll appreciate any help. > From dovecot.org at veggiechinese.net Tue Jul 15 16:50:21 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Tue, 15 Jul 2014 09:50:21 -0700 Subject: ATrpms repo In-Reply-To: <53C4E9B4.5090501@thelounge.net> References: <20140715034233.GA97784@aura.veggiechinese.net> <53C4E9B4.5090501@thelounge.net> Message-ID: <20140715165021.GF96702@aura.veggiechinese.net> On Tue, Jul 15, 2014 at 10:43:32AM +0200, Reindl Harald wrote: > > > > Not only is > > http://atrpms.net/name/dovecot/ > > empty, but: > > http://packages.atrpms.net/dist/el6/ > > seems to return a 404. Some of the mirrors still have the packages, but > > does anyone know if they're going to continue to build 2.2.x packages? > > avoid ATrpms > > enable this repo unconditionally sooner or later will *** your > OS installation because he overrides base packages often in > incompatible ways and mixed with sane repos like rpmfusion > years ago already leaded in randomly crashing applications We don't have the repo enabled - we're just pulling in the package into our internal repo (after testing). That said, I'm happy to get recommendations for any RHEL6 repos that have Dovecot 2.2.x (or SRPMs that will build cleanly on EL6). While I'm comfortable with my ability to build my own packages, I'd rather not have to. Unfortunately, 2.1 didn't work properly with our setup (proxy / backend on the same machines), so despite some recent bugs, I need 2.2 train. w From info at babaei.net Tue Jul 15 17:01:48 2014 From: info at babaei.net (Mohammad S. Babaei) Date: Tue, 15 Jul 2014 21:31:48 +0430 Subject: Dovecot2 Antispam MAILTRAIN backend with SpamAssassin In-Reply-To: <53C528E8.9000003@netocean.de> References: <27cdaa7b81ab5c586d83b8dbe69e4604@babaei.net> <53C528E8.9000003@netocean.de> Message-ID: Hello Leander, Thank you so much for the answer. But I believe there are two versions of the AntiSpam plugin. One is so called Johannes version for version 1.x and the other Eugene version for 2.x series, which is also based on the Johannes version but it is different and the configurations for version 1.x may not work on 2.x. Anyway, thanks to you, there are now good news. I've tried you're configuration and script, it seemed that your script was getting called. Then I reverted back to my own configuration and script, and boom, automagically it started working. Probably, I may have made a stupid mistake the first time. Now I see the temp files are being created and I can see SpamAssassin getting called with the right parameters. Thank you so much. Regards, Mohammad S. Babaei --- "When I give, I give myself." - Walt Whitman On 2014-07-15 17:43, Leander Sch?fer wrote: > I remember, that I also struggled for quite a while until I figured it out. Here is what I used on my FreeBSD Dovecot installation ... > > Remember, that the following code is working on "dovecot --version 1.2.12" ... but it could also be valid for later versions. I simply havn't checked it out yet. > > ### Dovecot AntiSpam ### > # mail signature (used with any backend requiring a signature) > #antispam_signature = X-Spam-Status > #antispam_signature_missing = move > > antispam_mail_sendmail = /usr/local/etc/dovecot/sa-learn-helper.sh > antispam_mail_sendmail_args = --username=%Lu > antispam_mail_spam = --spam > antispam_mail_notspam = --ham > antispam_mail_tmpdir = /tmp > antispam_spam = Spam > #antispam_unsure = Virus > antispam_trash = Trash > > echo '#!/usr/local/bin/bash > > #/usr/local/bin/sa-learn ${1} ${2} ${3} ${4} &> /var/log/DoveDamnAntiSpam.log > /usr/local/bin/sa-learn "${1}" "${2}" "${3}" "${4}" > exit 0 > > ' > /usr/local/etc/dovecot/sa-learn-helper.sh > chmod 0777 /usr/local/etc/dovecot/sa-learn-helper.sh ; > chown root:wheel /usr/local/etc/dovecot/sa-learn-helper.sh ; > > Best regards > Leander > > Am 15.07.14 15:00, schrieb Mohammad S. Babaei: > >> Hi there, I've already asked this question on FreeBSD forums without getting any response. So, I thought it's a good idea to ask it again here. I've setup Dovecote2 (2.2.13) + Postfix + SpamAssassin on my FreeBSD 10 VPS and it works flawlessly. Though, I couldn't setup the Dovecot Antispam plugin to train SpamAssassin when I move mails to the Junk folder. I installed the plugin from FreeBSD ports and followed the official documentation [1] and the man page [2] without any success. This is my configuration: ######## # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.0-RELEASE-p6 i386 ufs auth_mechanisms = plain login digest-md5 disable_plaintext_auth = no first_valid_gid = 6 first_valid_uid = 26 last_valid_gid = 6 last_valid_uid = 26 lmtp_save_to_detail_mailbox = yes mail_gid = mail mail_location = mdbox:/mail/%d/%u mail_privileged_group = mail mail_uid = mailnull managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Archive { auto = no special_use = Archive } mailbox Drafts { auto = subscribe special_use = Drafts } mailbox Flagged { auto = no special_use = Flagged } mailbox Junk { auto = subscribe special_use = Junk } mailbox Sent { auto = subscribe special_use = Sent } mailbox Trash { auto = subscribe special_use = Trash } mailbox virtual/All { auto = no special_use = All } prefix = separator = / } passdb { args = /mail/%d/dovecot_passwd driver = passwd-file } plugin { antispam_backend = MAILTRAIN antispam_mail_notspam = --ham antispam_mail_sendmail = /mail/sa-learn-pipe.sh antispam_mail_spam = --spam antispam_spam = Junk antispam_trash = Trash quota_rule = *:storage=8GB sieve = /mail/%d/%u/dovecot.sieve sieve_dir = /mail/%d/%u sieve_global_dir = /mail/sieve sieve_global_path = /mail/sieve/globalfilter.sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-client { group = mail mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0600 user = mailnull } user = root } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 32 process_min_avail = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_limit = 32 process_min_avail = 1 } ssl_cert = > /tmp/sa-learn-pipe.log #echo $* > /tmp/sendmail-parms.txt cat<&0 >> /tmp/sendmail-msg-$$.txt /usr/local/bin/sa-learn $* /tmp/sendmail-msg-$$.txt rm -f /tmp/sendmail-msg-$$.txt echo "$$-end" >> /tmp/sa-learn-pipe.log exit 0 ######## I made it excecutable by all users using chmod a+x /mail/sa-learn-pipe.sh The problem is, there is no log in /var/log/maillog regarding the Antispam plugin, and the script won't get called when I move any message in/out to/from Junk folder. I'll appreciate any help. From ricardo at wenn.com Tue Jul 15 17:23:54 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Tue, 15 Jul 2014 18:23:54 +0100 Subject: Postfix user@domain splitting In-Reply-To: References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> Message-ID: <53C563AA.5060804@wenn.com> That was done for testing to see if it made any difference when I moved to LDA, in LDA mode it seems to not care if that is %n or %u, it always takes the first part of the email address which is weird. Ive just tested again to confirm on %n and its not working so ive reverted again back to LDA which does. Seems to not matter how that variable is set it does not do anything. When using %n ive tried to see if I can login via IMAP with the whole username but again no, this is the error, note the difference between the 'user' field on each line. Jul 15 18:22:17 imap-login: Info: Login: user=, method=PLAIN, rip=10.0.0.180, lip=10.100.0.198, mpid=9493, session= Jul 15 18:22:20 imap-login: Info: Disconnected: Shutting down (auth failed, 4 attempts in 37 secs): user=, method=PLAIN, rip=10.0.0.3, lip=10.100.0.198, TLS, session= Steffen Kaiser wrote, On 15/07/2014 13:18: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 15 Jul 2014, Ricardo Branco wrote: > >> Attached files >> >> Nick Edwards wrote, On 15/07/2014 10:19: >>> you need to show doveconf -n >>> and what you have in the master.conf for dovecot >>> >>> On 7/15/14, Ricardo Branco wrote: >>>> I have been trying looking though all the wiki documents to setup LMTP. >>>> It now seems to all be connected except that it keeps saying that the >>>> user is not recognised when postfix sends to LMTP, it sends the full >>>> recipent email address but seems that on the dovecot side it is unable >>>> to work with this. >>>> I have checked the userdb and made sure its using %n but alas it still >>>> does not work. > > userdb { > args = username_format=%u /etc/passwd > driver = passwd-file > name = passwd-file > } > > In opposite to your sentence I see a %u there. > >>>> Currently ive had to revert to using LDA as it works fine with that but >>>> i still dont know how as the postfix config variable $RECIPIENT is the >>>> full email address and does not seem to matter to LDA. >>>> >> >> > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU8UcInz1H7kL/d9rAQKXQAgAmu6NnZOqdQKEgKhk6q/CPtXza+dkUh7f > 4Ms2tJFw2krwKNeZOvKGOsEeD7XyFDYpfZFDqEewjffqlABUUytIRPXzD3xFvzXV > DuXTW1VseEP26ewR7odHN9J+WL1Unh52HnxFgM63Bo1IwYzF84K09VO3DxqobuF7 > S8MqQYj6MPqB73IZUbVzRkCDBM0mv52Gx14LFmmPXbphgZFmtixkUy2CpPOT/l02 > 0aBSsJZqV/ySKcB2V5UNCj8GoGvwyH3Jh9RFeNIlUKYZYT9s534rfbKu7+T6645I > 67daEtZjfAbBOi/foqh41kbSpSaHIMvF970EP/EozFgMBsnghQ+SLg== > =6YKs > -----END PGP SIGNATURE----- From user+dovecot at localhost.localdomain.org Tue Jul 15 18:04:22 2014 From: user+dovecot at localhost.localdomain.org (Pascal Volk) Date: Tue, 15 Jul 2014 18:04:22 +0000 Subject: ATrpms repo In-Reply-To: <20140715034233.GA97784@aura.veggiechinese.net> References: <20140715034233.GA97784@aura.veggiechinese.net> Message-ID: <53C56D26.6030202@localhost.localdomain.org> On 07/15/2014 03:42 AM Will Yardley wrote: > Tried mailing the maintainer, but didn't get a response -- anyone know > what's happened to the ATrpms repo? dunno :) > Not only is > http://atrpms.net/name/dovecot/ > empty, but: > http://packages.atrpms.net/dist/el6/ > seems to return a 404. Some of the mirrors still have the packages, but > does anyone know if they're going to continue to build 2.2.x packages? There are some mirrors: http://atrpms.net/documentation/mirrors/ Regards, Pascal -- The trapper recommends today: f007ba11.1419620 at localdomain.org From slusarz at curecanti.org Tue Jul 15 20:13:59 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Tue, 15 Jul 2014 14:13:59 -0600 Subject: HIGHESTMODSEQ tracking In-Reply-To: References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> <20140714174719.Horde.px3Mk2olwJghwWJ-q5T5kw6@bigworm.curecanti.org> Message-ID: <20140715141359.Horde.dexbWi1OkSM04YZc37jcmQ3@bigworm.curecanti.org> Quoting Kostya Vasilyev : >> This is getting a bit off-topic on this list... but Gmail does a LOT of >> things wrong. Head over to one of the IMAP lists for further information. >> > > This is just one glaring example. Maybe you've ran into more than I have. > > In any case, the point stands - with Gmail, it's much easier to be > confident, from actual testing, that things works a certain way. > > >> >> If you are testing against Gmail as the gold standard as to how a IMAP >> server should operate, > > > I never said or implied that. In fact, I pointed out a serious issue with > Gmail's IMAP IDLE implementation, which means the exact opposite of holding > it as a gold standard. > > >> I can safely say you are Doing It Wrong. > > > It seems you enjoy pointing out to people when they're "wrong" or > "incorrect" so much, you actually put meaning into their words that's not > there? Or it it just me? I was just trying to point out that this statement is very dangerous/incorrect: "In any case, the point stands - with Gmail, it's much easier to be confident, from actual testing, that things works a certain way." Gmail behavior may/can/will change overnight, and you will have no idea. It makes a lot more sense to pick a local server of a known version, that has deterministic behavior, to develop with. >> For the "more than 50% market share" of Dovecot / Cyrus, do you have a >>> breakdown by version number? At least in terms of 1.* vs 2.0 and higher? >>> >> >> I do not. > > > And without being able to get a version number from a Dovecot session (or > so it seems to me -- nothing returned from ID...).... it looks kind of sad. ID extension is pretty much worthless for version identification. It is trivially spoofed -- and some servers do exactly this in the real world. All it takes is one server/version to be spoofed to make that data worthless. It's possible to do some level of basic version sniffing by things like banner messages, Human-readable responses, CAPABILITY lists, and ordering of responses to various commands. However, this is really only useful for broad statistical surveys and not precise version determination. I have been able to work around all IMAP issues that have been reported to us solely based on the data returned, rather than knowing what IMAP server/version I am connected to. michael From kmansoft at gmail.com Tue Jul 15 20:43:30 2014 From: kmansoft at gmail.com (Kostya Vasilyev) Date: Wed, 16 Jul 2014 00:43:30 +0400 Subject: HIGHESTMODSEQ tracking In-Reply-To: <20140715141359.Horde.dexbWi1OkSM04YZc37jcmQ3@bigworm.curecanti.org> References: <20140709153745.Horde.75rqVkqynWzjwvzd3953jw1@bigworm.curecanti.org> <20140709180537.Horde.YGyQtaBeFXNmQ89BJlSi7Q1@bigworm.curecanti.org> <20140714174719.Horde.px3Mk2olwJghwWJ-q5T5kw6@bigworm.curecanti.org> <20140715141359.Horde.dexbWi1OkSM04YZc37jcmQ3@bigworm.curecanti.org> Message-ID: 2014-07-16 0:13 GMT+04:00 Michael M Slusarz : > Quoting Kostya Vasilyev : > >> >> >> It seems you enjoy pointing out to people when they're "wrong" or >> "incorrect" so much, you actually put meaning into their words that's not >> there? Or it it just me? >> > > I was just trying to point out that this statement is very > dangerous/incorrect: > > > "In any case, the point stands - with Gmail, it's much easier to be > confident, from actual testing, that things works a certain way." > > Gmail behavior may/can/will change overnight, and you will have no idea. Yes I will have a very good idea. First, I use GMail myself, and second, I'll get messages from my users if the changes cause something in my app to break. And because Gmail's software is pretty much identical for everyone (less the staged rollouts that I'm sure they use), I can see those changes very easily (one such case happened just recently). And not just for Gmail -- I get messages from users about other issues too, and then I can react by: - putting a banner on my web site / forum (e.g. Yahoo recently letting their SSL certificate for SMTP expire) - or making changes to my software > It makes a lot more sense to pick a local server of a known version, that > has deterministic behavior, to develop with. For development, I use about a dozen test accounts, from Fastmail (probably my overall favorite) to Gmail, Yahoo, Dovecot, Yandex, Hotmail, and a few more that you've probably not heard of. However, I'm not at liberty to pick mail servers / services for my users. Sometimes the decision is made for them by someone else -- a corporate mail system, or a web hosting company. Assuming latest versions of mail server software in those cases would be foolish on my part. And yes, sometimes I look at the app's network logs and tell the user "you won't be able to do this, the server is broken". However, I'd like to avoid such cases if I can, and sometimes have to implement compatibility hacks. > > > For the "more than 50% market share" of Dovecot / Cyrus, do you have a >>> >>>> breakdown by version number? At least in terms of 1.* vs 2.0 and higher? >>>> >>>> >>> I do not. >>> >> >> >> And without being able to get a version number from a Dovecot session (or >> so it seems to me -- nothing returned from ID...).... it looks kind of >> sad. >> > > ID extension is pretty much worthless for version identification. It is > trivially spoofed -- and some servers do exactly this in the real world. > All it takes is one server/version to be spoofed to make that data > worthless. > I'm not talking about doing it for security purposes, and for compatibility, spoofing seems to me like less of an issue. In the realm of technically possible, someone could even write a random text generator and run it on port 993. Why, GoDaddy has been doing exactly this for years, and they're even able to charge their customers for it. > > It's possible to do some level of basic version sniffing by things like > banner messages, Human-readable responses, CAPABILITY lists, and ordering > of responses to various commands. However, this is really only useful for > broad statistical surveys and not precise version determination. > Well, in theory, CAPABILITY is all you need, because all mail servers / services are strictly RFC compliant... ...and when they're not, they get fixed / upgraded very quickly... ...as soon as just one user relays a message from the developer of some "random" mail app to the mail service's support. Hahaha. I'd feel more confident about enabling CONDSTORE / modseq for Dovecot if I could exclude versions below 2.0, just to be safe. This has more practical value to me than a statistical survey. Oh well. Anyway, this thread has gotten quite far off-topic, thanks again for sharing your real-world experiences with Dovecot and its CONDSTORE / modseq support. -- K From sca at andreasschulze.de Tue Jul 15 20:47:10 2014 From: sca at andreasschulze.de (A. Schulze) Date: Tue, 15 Jul 2014 22:47:10 +0200 Subject: TRANSLATION extension to the NAMESPACE response supported? Message-ID: <20140715224710.Horde.vqYeRhpq_762eL9GynWYfg1@horde.andreasschulze.de> Hello, I would like to ask if the TRANSLATION extension to the NAMESPACE response is supported by dovecot. context: http://lists.horde.org/archives/horde/Week-of-Mon-20140714/052136.html Thanks, Andreas From stephan at rename-it.nl Tue Jul 15 21:01:14 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Tue, 15 Jul 2014 23:01:14 +0200 Subject: TRANSLATION extension to the NAMESPACE response supported? In-Reply-To: <20140715224710.Horde.vqYeRhpq_762eL9GynWYfg1@horde.andreasschulze.de> References: <20140715224710.Horde.vqYeRhpq_762eL9GynWYfg1@horde.andreasschulze.de> Message-ID: <53C5969A.6050601@rename-it.nl> On 7/15/2014 10:47 PM, A. Schulze wrote: > > Hello, > > I would like to ask if the TRANSLATION extension to the NAMESPACE > response > is supported by dovecot. > > context: > http://lists.horde.org/archives/horde/Week-of-Mon-20140714/052136.html Afaict, Oracle currently has the only implementation of the LANGUAGE capability: http://www.imapwiki.org/Specs I haven't seen any plans for it in Dovecot so far and I think you are one of the first to request it. :) Regards, Stephan. From lazy404 at gmail.com Tue Jul 15 21:05:50 2014 From: lazy404 at gmail.com (Lazy) Date: Tue, 15 Jul 2014 23:05:50 +0200 Subject: fts solr database size In-Reply-To: <53C50B17.7020309@wenn.com> References: <53C50B17.7020309@wenn.com> Message-ID: 2014-07-15 13:05 GMT+02:00 Ricardo Branco : > We are no way as big as you but in terms users but our user vs mailbox size > is large. > > Dovecot: > 50 users > 425Gb (mdbox + zlib) > > Note solr only indexes folders within a mailbox when a search is done on > them so size can vary and most people dont realise that the default type of > search in Thunderbird is on Sender/Recipients/Subject which happens localy > and not on the server so you dont get solr indexing unless the user does a > custom search and forces remote. Webmail systems though will tend to do > server searches. > Solr: > Num Docs: 17m > Size: 4.5GB Thank You for the data, I also have noticed that most of the fat clients do their own search, so fts whould be limited mostly to webmail users. -- Michal From gessel at blackrosetech.com Tue Jul 15 21:21:14 2014 From: gessel at blackrosetech.com (David Gessel) Date: Wed, 16 Jul 2014 00:21:14 +0300 Subject: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) In-Reply-To: <53C519BF.6050803@blackrosetech.com> References: <53C47FFB.4040901@blackrosetech.com> <53C502C7.90803@dimejo.at> <53C519BF.6050803@blackrosetech.com> Message-ID: <53C59B4A.70602@blackrosetech.com> -------- Original Message -------- Subject: Re: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) From: David Gessel To: Alex JOST , dovecot at dovecot.org Date: Tue Jul 15 2014 15:08:31 GMT+0300 (Arabic Standard Time) > -------- Original Message -------- > Subject: Re: Dovecot/K9/Thunderbird IMAP interaction issues: replicated > messages, constant reloading (TB) & missing new messages (K-9) > From: Alex JOST > To: dovecot at dovecot.org > Date: Tue Jul 15 2014 13:30:31 GMT+0300 (Arabic Standard Time) > >> Am 15.07.2014 03:12, schrieb David Gessel: >>> * In thunderbird, I get constant downloading of messages. Every time I >>> switch to the inbox from another folder, the messages start >>> redownloading. This sometimes, but not always, seems to create >>> duplicate messages, but I'm now fairly sure they are only created in the >>> client and not on the server. Searching through various forums, it >>> appears this has been a problem for Thunderbird for some time, but it >>> wasn't for me on Courier. As posts about similar errors seem to have >>> petered out over the last year without any clear guidance on how to fix >>> it that I could find, I expect there's a simple fix I just haven't found >>> yet, either in TB configuration or in Dovecot. Any hints? I tried >>> Thunderfix to remove the .msf files and will be redownloading my mail >>> over the thin pipe out to Iraq for the next 6 months (DOH!). One >>> artifact is that when I restart thunderbird, my inbox is reported as >>> having about 130 messages in it, then thunderbird starts redownloading >>> headers and eventually gets back up to the 1297 currently listed both in >>> the TB pane and by ls | wc -l in /cur. Is it possible there is a time >>> out that needs to be extended? In TB, I've set (among other less >>> apparently relevant options) >>> mailnews.tcptimeout;1000 >>> mail.db.idle_limit;30000000 >> >> How old is your Thunderbird profile. Have you tried creating a new one >> and see if the problem persists? > > It is a new profile created with the transition from Cyrus to Dovecot > about a week ago, but I used IMAPSync to move all my mail from the > ancient Cyrus server to the shiny new Dovecot server. I then deleted > the old profile. > >> >> Thunderfix should not be needed by the way. Just right click on the >> folder => Properties => Repair > > I did see that, but first thought there was something magic about > "thunderfix" then decided to use it anyway because I have annual > sent/recieved archives from 2000 (and one for pre-2000) so that would > have been a lotta right-clicking. > >> >> >>> server # dovecot -n >>> # 2.2.13: /usr/local/etc/dovecot/dovecot.conf >>> # OS: FreeBSD 9.2-RELEASE amd64 >>> auth_default_realm = mydomain.com >>> auth_mechanisms = plain login >>> auth_realms = mydomain.com mydomain2.org >>> disable_plaintext_auth = no >>> first_valid_gid = 5000 >>> first_valid_uid = 5000 >>> hostname = mydomain.com >>> imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags >>> imap_idle_notify_interval = 29 mins >>> last_valid_gid = 5000 >>> last_valid_uid = 5000 >>> lda_mailbox_autocreate = yes >>> listen = * >>> mail_gid = 5000 >>> mail_location = maildir:~/:CONTROL=/var/no-quota/%u >>> mail_plugins = quota mail_log notify >>> mail_temp_dir = /var/tmp >>> mail_uid = 5000 >>> maildir_broken_filename_sizes = yes >>> managesieve_notify_capability = mailto >>> managesieve_sieve_capability = fileinto reject envelope >>> encoded-character vacation subaddress comparator-i;ascii-numeric >>> relational regex imap4flags copy include variables body enotify >>> environment mailbox date ihave duplicate spamtest spamtestplus editheader >>> mbox_lazy_writes = no >>> namespace inbox { >>> inbox = yes >>> location = >>> mailbox Drafts { >>> special_use = \Drafts >>> } >>> mailbox Junk { >>> special_use = \Junk >>> } >>> mailbox Sent { >>> special_use = \Sent >>> } >>> mailbox "Sent Messages" { >>> special_use = \Sent >>> } >>> mailbox Trash { >>> special_use = \Trash >>> } >>> prefix = >>> } >>> passdb { >>> args = /usr/local/etc/dovecot/dovecot-sql.conf.ext >>> driver = sql >>> } >>> plugin { >>> expire = Trash >>> mail_log_events = delete undelete expunge copy mailbox_delete >>> mailbox_rename >>> mail_log_fields = uid box msgid size >>> quota = maildir:User quota >>> quota_exceeded_message = Storage quota for this account has been >>> exceeded, please try again later. >>> quota_rule = *:storage=50G >>> quota_rule2 = Trash:storage=+30%% >>> quota_rule3 = Sent:storage=+30%% >>> quota_warning = storage=90%% quota-warning 90 %u >>> quota_warning2 = storage=75%% quota-warning 75 %u >>> sieve = ~/.dovecot.sieve >>> sieve_before = /usr/local/etc/dovecot/sieve/ >>> sieve_dir = ~/sieve >>> sieve_extensions = +spamtest +spamtestplus +relational >>> +comparator-i;ascii-numeric +editheader >>> } >>> postmaster_address = gessel at mydomain.com >>> protocols = imap lmtp sieve sieve >>> sendmail_path = /usr/local/sbin/sendmail >>> service auth { >>> unix_listener /var/spool/postfix/private/auth { >>> group = postfix >>> mode = 0666 >>> user = postfix >>> } >>> unix_listener auth-userdb { >>> group = vmail >>> mode = 0600 >>> user = vmail >>> } >>> } >>> service managesieve-login { >>> inet_listener sieve { >>> port = 4190 >>> } >>> service_count = 1 >>> vsz_limit = 128 M >>> } >>> service quota-warning { >>> executable = script /usr/local/bin/quota-warning.sh >>> unix_listener quota-warning { >>> user = vmail >>> } >>> user = vmail >>> } >>> ssl = required >>> ssl_cert = >> ssl_cipher_list = >>> ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES256-SHA:!SSLv2 >>> >>> ssl_key = >> ssl_prefer_server_ciphers = yes >>> userdb { >>> driver = prefetch >>> } >>> userdb { >>> args = /usr/local/etc/dovecot/dovecot-sql.conf.ext >>> driver = sql >>> } >>> protocol lda { >>> mail_plugins = quota mail_log notify sieve >>> } >>> protocol imap { >>> mail_max_userip_connections = 20 >>> mail_plugins = quota mail_log notify imap_quota imap_zlib >>> } >>> protocol lmtp { >>> mail_plugins = quota mail_log notify sieve >>> } >>> >> >> I don't know if it makes a difference for you as you are not using >> "LAYOUT=fs" but try to disable those imap_client_workarounds. >> > > Good catch, thank you. (I used LAYOUT=fs at first, but found behavior a > little anomalous. I forgot to disable the workarounds). > > This may have stopped the problem of redownloading the entire mailbox > (on restart I got downloading 1 of 8 instead of 1 of 170... 30 of 1330 > in the status pane) . My other mailboxes still need to sync and it > might take a few days to verify that things are stable. I did get 81 > immediate "Warning: Maildir /mail/mydomain.com/gessel//.Bulkmail: > Expunged message reappeared, giving a new UID" warnings on connect, but > if this is the problem, it might stop after all the directories are > resynced. > > I'll update with further data as it comes in. > > I am also somewhat suspect of QRSYNC from this post: > http://dovecot.org/pipermail/dovecot/2011-August/130687.html - though > this is from a long time ago and it seems a little surprising that bugs > on this seemingly useful capability would persist. In any event (if > useful information), my capability enumeration reads: > > # telnet localhost 143 > > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. > a login user pass > a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS > THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN > NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH > ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY > MOVE COMPRESS=DEFLATE QUOTA] Logged in > > > I did try setting mail.server.default.use_condstore;false in > Thunderbird, but that didn't change the behavior of reloading the entire > inbox on startup so I've changed that back as that wasn't the desired > result. > Disabling the imap_client_workarounds in TB ended up neither helping nor harming. The first sync was promising but as soon as that was finished (it can take a while to download 8 messages to Iraq) it started over re-downloading the entire mailbox. I don't seem to be generating duplicate messages, but I am redownloading every message over and over. My TB activity manager is filled with paused "bringing folder XXX up to date" messages. Is there any indication of current problems with CONDSTORE/QRESYNC since 2011 or so? I've set: imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE COMPRESS=DEFLATE QUOTA and will report if this yields any changes From slusarz at curecanti.org Tue Jul 15 21:24:47 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Tue, 15 Jul 2014 15:24:47 -0600 Subject: TRANSLATION extension to the NAMESPACE response supported? In-Reply-To: <53C5969A.6050601@rename-it.nl> References: <20140715224710.Horde.vqYeRhpq_762eL9GynWYfg1@horde.andreasschulze.de> <53C5969A.6050601@rename-it.nl> Message-ID: <20140715152447.Horde.OflZ1zFVLFhxoVvqYTs6fg2@bigworm.curecanti.org> Quoting Stephan Bosch : > On 7/15/2014 10:47 PM, A. Schulze wrote: >> >> Hello, >> >> I would like to ask if the TRANSLATION extension to the NAMESPACE >> response >> is supported by dovecot. >> >> context: >> http://lists.horde.org/archives/horde/Week-of-Mon-20140714/052136.html > > Afaict, Oracle currently has the only implementation of the LANGUAGE > capability: > > http://www.imapwiki.org/Specs > > I haven't seen any plans for it in Dovecot so far and I think you are > one of the first to request it. :) This is not the LANGUAGE extension - this is namespace translations (I18NLEVEL=1). Dovecot has supported this since 1.1 according to that page. michael From dovecot.org at veggiechinese.net Tue Jul 15 22:28:18 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Tue, 15 Jul 2014 15:28:18 -0700 Subject: ATrpms repo In-Reply-To: <53C56D26.6030202@localhost.localdomain.org> References: <20140715034233.GA97784@aura.veggiechinese.net> <53C56D26.6030202@localhost.localdomain.org> Message-ID: <20140715222818.GI96702@aura.veggiechinese.net> On Tue, Jul 15, 2014 at 06:04:22PM +0000, Pascal Volk wrote: > On 07/15/2014 03:42 AM Will Yardley wrote: > > Not only is > > http://atrpms.net/name/dovecot/ > > empty, but: > > http://packages.atrpms.net/dist/el6/ > > seems to return a 404. Some of the mirrors still have the packages, but > > does anyone know if they're going to continue to build 2.2.x packages? > > There are some mirrors: http://atrpms.net/documentation/mirrors/ Yes, I can get to some of the mirrors, and they still have the latest version that atrpms packaged, but it's a little disconcerting that the main site has been broken for this long without an announcement. I thought it could be related to a security breach, but haven't heard anything so far. There are some pending bugs in their Bugzilla database, all assigned to the main guy (Axel), but don't see any status changes on them. w From skdovecot at smail.inf.fh-brs.de Wed Jul 16 05:35:12 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Wed, 16 Jul 2014 07:35:12 +0200 (CEST) Subject: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) In-Reply-To: <53C59B4A.70602@blackrosetech.com> References: <53C47FFB.4040901@blackrosetech.com> <53C502C7.90803@dimejo.at> <53C519BF.6050803@blackrosetech.com> <53C59B4A.70602@blackrosetech.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 16 Jul 2014, David Gessel wrote: > Disabling the imap_client_workarounds in TB ended up neither helping nor > harming. The first sync was promising but as soon as that was finished > (it can take a while to download 8 messages to Iraq) it started over > re-downloading the entire mailbox. I don't seem to be generating > duplicate messages, but I am redownloading every message over and over. > My TB activity manager is filled with paused "bringing folder XXX up to > date" messages. Maybe you should check: http://wiki2.dovecot.org/Debugging/Rawlog and see if the IMAP commands make sense. Check if IMAP validity / UIDs changing ... . If "it can take a while", maybe the connection gets interrupted or corrupted and some client is trying to work around this. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU8YPEXz1H7kL/d9rAQJ/jggAqJUsxAUFRCcQWtOHXj9X+nE9QU3ck/pR hMdzFtv6BZjAOC9eZrefD80Md6aUa1d35RzvE2kLG3D8mnkx6hLVETemT70I1KqA EniRIn6svb3jP2H32n0DdIIPHEtmC+Wf3k/HK2yhH6RAlZu2GNJhbuQ8Bf9kvATS pyauaQ+qHirPzo8MjAv90wBmyrgN3PHZ7+4kE2P6W9th9sHFgW3YOB0BuPqnBLvy Jb/qM1BHqz/Yt+T9qCDgCzPknm5RR+iwHPTcjF2Vz/GKz/8WWM0bJniRqFs4g1a6 9UWffK8FO5QC2oI5KpD6KOkJSKhUAs54Qj9+VuxesUC6Bm7eLfJ4CA== =AH5A -----END PGP SIGNATURE----- From stephan at rename-it.nl Wed Jul 16 06:44:51 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Wed, 16 Jul 2014 08:44:51 +0200 Subject: TRANSLATION extension to the NAMESPACE response supported? In-Reply-To: <20140715152447.Horde.OflZ1zFVLFhxoVvqYTs6fg2@bigworm.curecanti.org> References: <20140715224710.Horde.vqYeRhpq_762eL9GynWYfg1@horde.andreasschulze.de> <53C5969A.6050601@rename-it.nl> <20140715152447.Horde.OflZ1zFVLFhxoVvqYTs6fg2@bigworm.curecanti.org> Message-ID: <53C61F63.9010903@rename-it.nl> On 7/15/2014 11:24 PM, Michael M Slusarz wrote: > Quoting Stephan Bosch : > >> On 7/15/2014 10:47 PM, A. Schulze wrote: >>> >>> Hello, >>> >>> I would like to ask if the TRANSLATION extension to the NAMESPACE >>> response >>> is supported by dovecot. >>> >>> context: >>> http://lists.horde.org/archives/horde/Week-of-Mon-20140714/052136.html >> >> Afaict, Oracle currently has the only implementation of the LANGUAGE >> capability: >> >> http://www.imapwiki.org/Specs >> >> I haven't seen any plans for it in Dovecot so far and I think you are >> one of the first to request it. :) > > This is not the LANGUAGE extension - this is namespace translations > (I18NLEVEL=1). > > Dovecot has supported this since 1.1 according to that page. What gives you that idea? From http://tools.ietf.org/html/rfc5255#section-1: The LANGUAGE extension allows the client to request a suitable language for protocol error messages and in combination with the NAMESPACE extension [RFC2342 ] enables namespace translations. Also, the TRANSLATION NAMESPACE extension itself is described in Section 3.4, which is part of Section 3 with title "LANGUAGE Extension". I agree that this RFC could have been a bit more clear on this. Regards, Stephan. From slusarz at curecanti.org Wed Jul 16 07:12:24 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Wed, 16 Jul 2014 01:12:24 -0600 Subject: TRANSLATION extension to the NAMESPACE response supported? In-Reply-To: <53C61F63.9010903@rename-it.nl> References: <20140715224710.Horde.vqYeRhpq_762eL9GynWYfg1@horde.andreasschulze.de> <53C5969A.6050601@rename-it.nl> <20140715152447.Horde.OflZ1zFVLFhxoVvqYTs6fg2@bigworm.curecanti.org> <53C61F63.9010903@rename-it.nl> Message-ID: <20140716011224.Horde.q16XcH1dfrOLGZ4oBSPO0g7@bigworm.curecanti.org> Quoting Stephan Bosch : > On 7/15/2014 11:24 PM, Michael M Slusarz wrote: >> Quoting Stephan Bosch : >> >>> On 7/15/2014 10:47 PM, A. Schulze wrote: >>>> >>>> Hello, >>>> >>>> I would like to ask if the TRANSLATION extension to the NAMESPACE >>>> response >>>> is supported by dovecot. >>>> >>>> context: >>>> http://lists.horde.org/archives/horde/Week-of-Mon-20140714/052136.html >>> >>> Afaict, Oracle currently has the only implementation of the LANGUAGE >>> capability: >>> >>> http://www.imapwiki.org/Specs >>> >>> I haven't seen any plans for it in Dovecot so far and I think you are >>> one of the first to request it. :) >> >> This is not the LANGUAGE extension - this is namespace translations >> (I18NLEVEL=1). >> >> Dovecot has supported this since 1.1 according to that page. > > What gives you that idea? From http://tools.ietf.org/html/rfc5255#section-1: > > The LANGUAGE extension allows the client to request a suitable > language for protocol error messages and in combination with the > NAMESPACE extension [RFC2342 ] > enables namespace translations. My mistake. I implemented this long ago, and I explicitly remember parsing the extended namespace translation data. I assume this testing was done against a Dovecot server. However, a look at the code indicates that the testing was from static data in our unit tests. Whoops. I stand corrected. This is part of LANGUAGE rather than I18NLEVEL=1. LANGUAGE is pretty much worthless other than the namespace part ... who cares if the human-readable text is translated since, other than ALERT text, it is never shown to the end-user? That explains why nobody has implemented it. michael From wim at asgc.be Wed Jul 16 07:34:42 2014 From: wim at asgc.be (Wim Paulussen) Date: Wed, 16 Jul 2014 09:34:42 +0200 Subject: trying to build pigeonhole v0.4.3 sources on CentOs 6.5 - error while executing 'make' Message-ID: Hello all, I am trying to build pigeonhole from source but get the following (only error output) : ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `mail_get_backend_mail' collect2: ld returned 1 exit status make[3]: *** [sievec] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Output further shows following warning : ieve-actions.c:515 implicit declaration of function 'mail_get_backend_mail' dovecot -n : # 2.2.12: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.11.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) auth_debug = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /var/run/dovecot/ listen = * log_path = /var/log/dovecot.log mail_gid = 504 mail_home = /var/mail/vhost/%d/%n mail_location = maildir:~/ mail_uid = 503 passdb { args = /usr/local/etc/dovecot/dovecot-users driver = passwd-file } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl = required ssl_cert = Hi All, I have noticed that dovecot / exim on Cpanels appear to support sending emails via exim after authenticating to Dovecot - see message below 550-Please turn on SMTP Authentication in your mail client, or login to the 550-IMAP/POP3 server before sending your message We are migrating users mail off cpanels into split mta and dovecot servers and are having problems with some users being abble to send emails afterwards. Does anyone understand how the CPanel config works? Thanks Murray From h.reindl at thelounge.net Wed Jul 16 10:03:44 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 16 Jul 2014 12:03:44 +0200 Subject: Sending emails using dovecot auth In-Reply-To: <88359e0e6d5ba872c02c683aae4ba569b7c233a6@webmail.westnet.com.au> References: <88359e0e6d5ba872c02c683aae4ba569b7c233a6@webmail.westnet.com.au> Message-ID: <53C64E00.2000900@thelounge.net> Am 16.07.2014 11:59, schrieb Murray Trainer: > I have noticed that dovecot / exim on Cpanels appear to support > sending emails via exim after authenticating to Dovecot - see message > below > > 550-Please turn on SMTP Authentication in your mail client, or login > to the > 550-IMAP/POP3 server before sending your message > > We are migrating users mail off cpanels into split mta and dovecot > servers and are having problems with some users being abble to send > emails afterwards. > > Does anyone understand how the CPanel config works? don't use crap like POP-before-SMTP in 2014 that don't really work in times of carrier grade NAT and mobile devices where thousands of complete independent users coming from the same gateway IP use SMTP auth -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From s.potapov at rambler-co.ru Wed Jul 16 13:17:02 2014 From: s.potapov at rambler-co.ru (Potapov Sergey) Date: Wed, 16 Jul 2014 13:17:02 +0000 Subject: Dovecot 2.2.13 Assertion failed in mailbox_list_create Message-ID: <409CEB1649811749B2E36961BEE2DDBC45F2C1F3@srv-mbx4.rambler.ramblermedia.com> Hi I got this error when configured imapc proxy (http://wiki2.dovecot.org/HowTo/ImapcProxy) and moved indexes to memory (mail_location = imapc:~/imapc:INDEX=MEMORY), with indexes on disk this error does not occurred. Jul 16 17:06:31 imap-login: Info: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=21703, secured, session= Jul 16 17:06:31 imap(user87): Panic: file mailbox-list.c: line 136 (mailbox_list_create): assertion failed: (set->root_dir == NULL || *set->root_dir != '\0' || ((*class_p)->props & MAILBOX_LIST_PROP_NO_ROOT) != 0) Jul 16 17:06:31 imap(user87): Error: Raw backtrace: /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x872a6) [0x7f39be4d52a6] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x88683) [0x7f39be4d6683] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f39be4d55f9] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mailbox_list_create+0x204) [0x7f39be7ff031] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x78934) [0x7f39be7d4934] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x78bbb) [0x7f39be7d4bbb] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mailbox_list_get_path+0x34) [0x7f39be80230a] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mailbox_get_path_to+0x8a) [0x7f39be7f9455] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x9a0ee) [0x7f39be7f60ee] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x32) [0x7f39be7f793c] -> dovecot/imap(imap_status_get+0xf0) [ 0x4252ac] -> dovecot/imap(cmd_status+0x1b7) [0x416177] -> dovecot/imap(command_exec+0x5f) [0x41bdf4] -> dovecot/imap() [0x41ad47] -> dovecot/imap() [0x41b049] -> dovecot/imap() [0x41b169] -> dovecot/imap(client_handle_input+0x7e) [0x41b1e9] -> dovecot/imap(client_input+0xe6) [0x41b37c] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_call_io+0xb6) [0x7f39be4eec32] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x1e5) [0x7f39be4f0ce4] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x18) [0x7f39be4eedcd] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_run+0xaf) [0x7f39be4eed26] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(master_service_run+0x2e) [0x7f39be477d6d] -> dovecot/imap(main+0x2b3) [0x428a6d] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f39be0af76d] -> dovecot/imap() [0x40ad59] # 2.2.13 (fd0616d553b0+): /home/lion/dovecot-2.2/etc/dovecot/dovecot.conf # OS: Linux 3.11.0-24-generic x86_64 Ubuntu 12.04.4 LTS auth_mechanisms = plain login default_internal_user = lion default_login_user = lion disable_plaintext_auth = no imapc_host = localhost log_path = /home/lion/dovecot-2.2/var/log/dovecot.log mail_home = /home/lion/dovecot-2.2/home/vmail/%u mail_location = imapc:~/imapc:INDEX=MEMORY namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = host=localhost port=143 default_fields = userdb_imapc_user=%u userdb_imapc_password=%w driver = imap } plugin { fts = solr fts_solr = url=http://localhost:8080/solr/ break-imap-search mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } service anvil { chroot = } service auth-worker { user = $default_internal_user } service imap-login { chroot = inet_listener imap { port = 10143 } inet_listener imaps { port = 10993 } } service lmtp { chroot = } service pop3-login { chroot = inet_listener pop3 { port = 10110 } inet_listener pop3s { port = 10995 } } ssl = no userdb { driver = prefetch } From s.potapov at rambler-co.ru Wed Jul 16 13:31:13 2014 From: s.potapov at rambler-co.ru (Potapov Sergey) Date: Wed, 16 Jul 2014 13:31:13 +0000 Subject: Dovecot 2.2.13+ Assertion failed in sync_expunge_range Message-ID: <409CEB1649811749B2E36961BEE2DDBC45F2C255@srv-mbx4.rambler.ramblermedia.com> Hi! I got this error when build dovecot from source (rev 17627), configure it as imapc proxy (http://wiki2.dovecot.org/HowTo/ImapcProxy) and run imaptest with clients=2 or more, on latest stable version (2.2.13) and with clients=1 this error does not occurred. Jul 16 17:22:26 imap(user771): Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) Jul 16 17:22:26 imap(user771): Error: Raw backtrace: /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x872a6) [0x7f8a956682a6] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x88683) [0x7f8a95669683] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8a956685f9] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x106f13) [0x7f8a959f5f13] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x107e5a) [0x7f8a959f6e5a] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0x33) [0x7f8a959f76a3] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x4e8) [0x7f8a959f7d97] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x126) [0x7f8a959e1817] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0xeb410) [0x7f8a959da410] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0xeb707) [0x7f8a959da707] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage. so.0(mail_index_open+0x17e) [0x7f8a959daa33] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0xe7) [0x7f8a959c6742] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x81fd4) [0x7f8a95970fd4] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x9a5d4) [0x7f8a959895d4] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mailbox_open+0x1d) [0x7f8a9598975d] -> dovecot/imap() [0x414a3f] -> dovecot/imap(cmd_select_full+0x204) [0x414fac] -> dovecot/imap(cmd_select+0x1d) [0x414ff1] -> dovecot/imap(command_exec+0x5f) [0x41bdf4] -> dovecot/imap() [0x41ad47] -> dovecot/imap() [0x41b049] -> dovecot/imap() [0x41b169] -> dovecot/imap(client_handle_input+0x7e) [0x41b1e9] -> dovecot/imap(client_input+0xe6) [0x41b37c] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_call_io+0xb6) [0x7f8a95681c32] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x1e5) [0x7f8a95683ce4] -> /home/lion/dovecot-2.2/lib/ dovecot/libdovecot.so.0(io_loop_handler_run+0x18) [0x7f8a95681dcd] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_run+0xaf) [0x7f8a95681d26] Jul 16 17:22:26 imap(user771): Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) Jul 16 17:22:26 imap(user771): Error: Raw backtrace: /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x872a6) [0x7fc4005942a6] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x88683) [0x7fc400595683] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fc4005945f9] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x106f13) [0x7fc400921f13] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x107e5a) [0x7fc400922e5a] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0x33) [0x7fc4009236a3] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x4e8) [0x7fc400923d97] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x126) [0x7fc40090d817] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0xeb410) [0x7fc400906410] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0xeb707) [0x7fc400906707] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage. so.0(mail_index_open+0x17e) [0x7fc400906a33] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0xe7) [0x7fc4008f2742] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x81fd4) [0x7fc40089cfd4] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(+0x9a5d4) [0x7fc4008b55d4] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot-storage.so.0(mailbox_open+0x1d) [0x7fc4008b575d] -> dovecot/imap() [0x414a3f] -> dovecot/imap(cmd_select_full+0x204) [0x414fac] -> dovecot/imap(cmd_select+0x1d) [0x414ff1] -> dovecot/imap(command_exec+0x5f) [0x41bdf4] -> dovecot/imap() [0x41ad47] -> dovecot/imap() [0x41b049] -> dovecot/imap() [0x41b169] -> dovecot/imap(client_handle_input+0x7e) [0x41b1e9] -> dovecot/imap(client_input+0xe6) [0x41b37c] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_call_io+0xb6) [0x7fc4005adc32] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x1e5) [0x7fc4005afce4] -> /home/lion/dovecot-2.2/lib/ dovecot/libdovecot.so.0(io_loop_handler_run+0x18) [0x7fc4005addcd] -> /home/lion/dovecot-2.2/lib/dovecot/libdovecot.so.0(io_loop_run+0xaf) [0x7fc4005add26] # 2.2.13 (fd0616d553b0): /home/lion/dovecot-2.2/etc/dovecot/dovecot.conf # OS: Linux 3.11.0-24-generic x86_64 Ubuntu 12.04.4 LTS auth_mechanisms = plain login default_internal_user = lion default_login_user = lion disable_plaintext_auth = no imapc_host = localhost log_path = /home/lion/dovecot-2.2/var/log/dovecot.log mail_home = /home/lion/dovecot-2.2/home/vmail/%u mail_location = imapc:~/imapc namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = host=localhost port=143 default_fields = userdb_imapc_user=%u userdb_imapc_password=%w driver = imap } plugin { fts = solr fts_solr = url=http://localhost:8080/solr/ break-imap-search mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } service anvil { chroot = } service auth-worker { user = $default_internal_user } service imap-login { chroot = inet_listener imap { port = 10143 } inet_listener imaps { port = 10993 } } service lmtp { chroot = } service pop3-login { chroot = inet_listener pop3 { port = 10110 } inet_listener pop3s { port = 10995 } } ssl = no userdb { driver = prefetch } From lists at wiesinger.com Wed Jul 16 13:50:49 2014 From: lists at wiesinger.com (Gerhard Wiesinger) Date: Wed, 16 Jul 2014 15:50:49 +0200 Subject: Dovecot and remote SASL Client via TLS In-Reply-To: <53AFA9CA.6010103@wiesinger.com> References: <53AFA9CA.6010103@wiesinger.com> Message-ID: <53C68339.2040404@wiesinger.com> On 29.06.2014 07:53, Gerhard Wiesinger wrote: > Hello, > > Is it possible to configure Dovecot as SASL client for central > authentication (also remotely via TCP/TLS)? > > Following use case: > IMAP server (host 1) <=> Windows Domain Controller and /etc/shadow > authenticator via pam (host2) > > Should work as: > IMAP server (host 1) <=> SASL Client via TLS <=> Network <=> SASL > Server via TLS <=> Local SASL via pam <=> Windows Domain Controller > and /etc/shadow authenticator via pam (host2) > Any comments? Thank you. Ciao, Gerhard http://www.wiesinger.com/ From ricardo at wenn.com Wed Jul 16 13:56:41 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Wed, 16 Jul 2014 14:56:41 +0100 Subject: Postfix user@domain splitting In-Reply-To: <53C563AA.5060804@wenn.com> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> Message-ID: <53C68499.3000005@wenn.com> Shows that auth is not honouring the %n i have. Does the username_format need to be only in the userdb section or also the passdb part? http://pastie.org/9396504 Ricardo Branco wrote, On 15/07/2014 18:23: > That was done for testing to see if it made any difference when I moved to LDA, in LDA mode it seems to not care if > that is %n or %u, it always takes the first part of the email address which is weird. > Ive just tested again to confirm on %n and its not working so ive reverted again back to LDA which does. Seems to not > matter how that variable is set it does not do anything. > > When using %n ive tried to see if I can login via IMAP with the whole username but again no, this is the error, note > the difference between the 'user' field on each line. > > Jul 15 18:22:17 imap-login: Info: Login: user=, method=PLAIN, rip=10.0.0.180, lip=10.100.0.198, > mpid=9493, session= > Jul 15 18:22:20 imap-login: Info: Disconnected: Shutting down (auth failed, 4 attempts in 37 secs): > user=, method=PLAIN, rip=10.0.0.3, lip=10.100.0.198, TLS, session= > > Steffen Kaiser wrote, On 15/07/2014 13:18: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Tue, 15 Jul 2014, Ricardo Branco wrote: >> >>> Attached files >>> >>> Nick Edwards wrote, On 15/07/2014 10:19: >>>> you need to show doveconf -n >>>> and what you have in the master.conf for dovecot >>>> >>>> On 7/15/14, Ricardo Branco wrote: >>>>> I have been trying looking though all the wiki documents to setup LMTP. >>>>> It now seems to all be connected except that it keeps saying that the >>>>> user is not recognised when postfix sends to LMTP, it sends the full >>>>> recipent email address but seems that on the dovecot side it is unable >>>>> to work with this. >>>>> I have checked the userdb and made sure its using %n but alas it still >>>>> does not work. >> >> userdb { >> args = username_format=%u /etc/passwd >> driver = passwd-file >> name = passwd-file >> } >> >> In opposite to your sentence I see a %u there. >> >>>>> Currently ive had to revert to using LDA as it works fine with that but >>>>> i still dont know how as the postfix config variable $RECIPIENT is the >>>>> full email address and does not seem to matter to LDA. >>>>> >>> >>> >> >> - -- Steffen Kaiser >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.11 (GNU/Linux) >> >> iQEVAwUBU8UcInz1H7kL/d9rAQKXQAgAmu6NnZOqdQKEgKhk6q/CPtXza+dkUh7f >> 4Ms2tJFw2krwKNeZOvKGOsEeD7XyFDYpfZFDqEewjffqlABUUytIRPXzD3xFvzXV >> DuXTW1VseEP26ewR7odHN9J+WL1Unh52HnxFgM63Bo1IwYzF84K09VO3DxqobuF7 >> S8MqQYj6MPqB73IZUbVzRkCDBM0mv52Gx14LFmmPXbphgZFmtixkUy2CpPOT/l02 >> 0aBSsJZqV/ySKcB2V5UNCj8GoGvwyH3Jh9RFeNIlUKYZYT9s534rfbKu7+T6645I >> 67daEtZjfAbBOi/foqh41kbSpSaHIMvF970EP/EozFgMBsnghQ+SLg== >> =6YKs >> -----END PGP SIGNATURE----- From asai at globalchangemusic.org Wed Jul 16 15:24:03 2014 From: asai at globalchangemusic.org (Asai) Date: Wed, 16 Jul 2014 08:24:03 -0700 Subject: Dovecot EE on SciLinux 6.5: No Config Files in /etc Message-ID: <53C69913.1020306@globalchangemusic.org> Greetings, I tried installing Dovecot EE on Scientific 6.5 yesterday, but there was no repo under that release version, so I hardcoded the release version to 6 in yum.repos.d/dovecot.repo. That worked, but when I installed, it didn't install any default configuration files. /etc/dovecot was empty. Is that to be expected for EE? -- --Asai From HFlor at gmx.de Wed Jul 16 16:19:02 2014 From: HFlor at gmx.de (Hardy Flor) Date: Wed, 16 Jul 2014 18:19:02 +0200 Subject: BUG: dovecot -n writes no usable configuration file Message-ID: <53C6A5F6.5020007@gmx.de> Hello, For testing, I wanted to make create a small configuration file of dovecot. This created file but did not work imap-postLogin. It missing the lines: unix_listener imap-postlogin { } in the section "service imap-postLogin". Hardy From alandaluz at gmail.com Wed Jul 16 17:10:20 2014 From: alandaluz at gmail.com (Cassidy Larson) Date: Wed, 16 Jul 2014 11:10:20 -0600 Subject: Resource Temporarily Unavailable on replicator-doveadm Message-ID: We're running 2.2.13 on two servers with replication. Still trying to get my replication tweaked correctly and I?m noticing a bunch of these errors for the same users over and over again: dsync-server(user at host.com): Error: write(/var/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable The 5-7 that I see all have quite a number of individual mailboxes (20+), I?m wondering if that has something to do with it? Also, my replicator status for full resync requests has been hovering around 2300-2400 the last few days: # doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 2410 Waiting 'failed' requests 1 Total number of known users 9836 In checking the replication status for some of the ?Resource temporarily unavailable? list from above, if I run it multiple times it outputs different results for the fast and full sync time: # doveadm replicator status user at host.com username priority fast sync full sync failed user at host.com none 00:20:21 49:43:34 - # doveadm replicator status user at host.com username priority fast sync full sync failed user at host.com none 00:10:55 00:10:55 - # doveadm replicator status user at host.com username priority fast sync full sync failed user at host.com none 00:10:56 00:10:56 - # doveadm replicator status user at host.com username priority fast sync full sync failed user at host.com none 00:10:57 00:10:57 - # doveadm replicator status user at host.com username priority fast sync full sync failed user at host.com none 00:20:24 49:43:37 - doveconf output for the replicator service is: service replicator { process_limit = 10 process_min_avail = 2 unix_listener replicator-doveadm { group = mailsys mode = 0666 user = mailsys } unix_listener replicator { group = mailsys mode = 0666 user = mailsys } } Anybody have any clues or suggestions? I?d be much appreciative. Thanks, Cassidy From lists.zxinn at otaking.se Wed Jul 16 18:41:04 2014 From: lists.zxinn at otaking.se (=?ISO-8859-1?Q?Tobias_Franz=E9n?=) Date: Wed, 16 Jul 2014 20:41:04 +0200 Subject: Differences in "Delivered-To" header between deliver and LMTP In-Reply-To: <53BFAD1F.3020406@Media-Brokers.com> References: <53BD87D3.9070108@jrice.me> <665E335C-289C-4390-A7B9-9B2F3D2E72A2@iki.fi> <53BFAD1F.3020406@Media-Brokers.com> Message-ID: <53C6C740.4000201@otaking.se> On 2014-07-11 11:23, Charles Marcus wrote: > On 7/10/2014 11:29 AM, Timo Sirainen wrote: >> On 9.7.2014, at 21.20, Jeff Rice wrote: >> >>> I'm transitioning my server over from using the deliver LDA and >>> LMTP. Suddenly a bunch of sieve filters stopped working, and I >>> noticed the contents of the Delivered-To header are different. >>> >>> Using Dovecot's deliver LDA, the contents are a bare email address >>> (foo at bar.com). Using Dovecot LMTP, they are in brackets >>> (). Is there a reason why this isn't consistent >>> between the two delivery agents? It seems like it ought to be. >> Oh, that's annoying. Dovecot LDA doesn't actually add this header, it >> was your MTA that added it. But looks like I hadn't checked what the >> MTAs actually write to the header when I added this feature to LMTP, >> and nobody had mentioned this before either. I wonder if anybody's >> system breaks if I just change it now.. > > If you do this Timo, would you please also consider going ahead and > adding the 20 or so lines of code you said it would take to also add > support for the x-original-to header (this specific was in a private > email to me while our support contract was active), as we discussed on > this list - and you then discussed with Wietse, back in April or so of > 2012: > > http://dovecot.org/list/dovecot/2012-April/082585.html > > Thanks! > > Charles I am also very interested in the outcome of these discussions for X-Original-To header together with LMTP. My setup will be migrating from an old Courier-IMAP install with Postfix VDA and plan to keep using Postfix but this time with Dovecot and potentially Dovecot LMTP. My users have multiple aliases and rely on the X-Original-To header for filters, however they mostly reside within the same domain handled by the same mail server. Old threads in this and Postfix mail lists indicate that Timo thinks LMTP cannot solve this. Some of this could possibly be solved for local implementations if LMTP can expand aliases itself for local delivery. Is this possible? In general it seems that LMTP has to rely on previous layers to keep the original recipient in for example X-Original-To header. For reference: http://archives.neohapsis.com/archives/postfix/2012-04/0179.html http://dovecot.org/list/dovecot/2012-April/082585.html http://www.dovecot.org/list/dovecot/2014-January/094396.html Charles, you seem to also have been involved in the following Postfix list thread from 2011. Are you using this Postfix workaround detailed at the end to add X-Original-To? https://groups.google.com/forum/#!topic/mailing.postfix.users/ceRuhB8NFWQ Postfix/main.cf: # to make sure Delivered-To header contains only one address lmtp_destination_recipient_limit=1 # for X-Original-To header smtpd_recipient_restrictions = check_recipient_access pcre:/etc/postfix/recipient_access.pcre /etc/postfix/recipient_access.pcre /(.+)/ prepend X-Original-To: $1 Dovecot: lda_original_recipient_header = X-Original-To /Tobias From nick.z.edwards at gmail.com Wed Jul 16 22:59:07 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Thu, 17 Jul 2014 08:59:07 +1000 Subject: If local Dovecot stops working, check lo In-Reply-To: <53C4F87C.50602@thinline.cz> References: <20140712073129.0e208f57@mydesq2.domain.cxm> <53C308A0.1020501@thinline.cz> <53C4F87C.50602@thinline.cz> Message-ID: On 7/15/14, Jiri Bourek wrote: > On 15.7.2014 11:13, Nick Edwards wrote: >> On 7/14/14, Jiri Bourek wrote: >>> On 14.7.2014 00:24, Nick Edwards wrote: >>>> On 7/12/14, Steve Litt wrote: >>>> >>>>> experience with Debian Wheezy is that lo "goes down" a lot, so this is >>>>> one of the first things I do when odd stuff happens. >>>>> >>>> >>>> Use a better operating system then >>> >>> Blaming operating system after *one* person reports something strange >>> about it seems a bit overboard, doesn't it...? >>> >> debian has a long history of being clueless: >> old packages in new releases, untested packages in releases >> (mailscanner did not, and was never going to, work out of thebox in a >> recent release) > > As most Linux distributions, Debian is a collective work done mostly by > volunteers. If you want newer versions and tested packages, feel free to > help them. > Why would I do that when I'm happy using other systems, and one thing I hate about debian users is, they are all so shit scared of using the source if they want latest versions they wont use them unless someone creates a deb package, FFS, they call themselves sys admins > And honestly, the situation about untested and old packages isn't as > grim as you're trying to say. not from the bitches i hear daily on other lists, including one I am one of the developers of. >> >> debian has history of thinking it knows better than upstream: >> openssl screwup they told debian was wrong but debian released it >> anyway causing grief for not only debian systems but all systems >> including windows that used certs generated on a debi\an server. > > AFAIK it was actually the other way around. Debian maintainers asked on > openssl-dev list if their change is ok and were told that it is. not from my recollection. unless they were told by a normal user, which is why -dev lists should only be populated by devs and not public. >> >> and dont get me started on debians release/ftp manager and the >> personal biases there either, shall I go? I can but it would be a bore >> for most. >> > > As far as I am concerned, there's no need to be more OT than we are now. > > Also please stop sending me personal messages, I am on the list. pffft blame gmail, I could not be bothered checking the headers each time i click reply From agaran at pld-linux.org Thu Jul 17 07:01:53 2014 From: agaran at pld-linux.org (Maciej 'Agaran' Pijanka) Date: Thu, 17 Jul 2014 09:01:53 +0200 Subject: possible bug around ACL Message-ID: <20140717070153.GB16655@pld-linux.org> Hello I want to set readonly over IMAP for users mailboxes at Archive namespace, (and have single user who can move mails there on automated way) This don't work but found that if I add file to /srv/mail.archives//dovecot-acl containing only owner lr then login to imap (with telnet) and do 1 GETACL Archive I get following result from gdb attached to worker process serving particular connection. Program received signal SIGSEGV, Segmentation fault. acl_mailbox_right_lookup (box=0x7fd75e4e1dc0, right_idx=right_idx at entry=10) at acl-mailbox.c:40 40 if (abox->skip_acl_checks) (gdb) p abox $1 = (struct acl_mailbox *) 0x0 (gdb) # uname -a Linux omelette 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux ii dovecot-core 1:2.2.13-2 amd64 local build from sources in testing just disabled lucene ps. I am idling on #dovecot too, if any info is needed with faster round trip time than emails. best regards -- agaran at pld dash linux dot org I do not fear computers. I fear the lack of them. [Isaac Asimov] -------------- next part -------------- # dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 auth_verbose = yes listen = 192.168.1.32, 127.0.0.1 mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = acl namespace archive { inbox = no list = yes location = maildir:/srv/mail.archives/%n prefix = Archive. separator = . subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/etc/dovecot/global-acl:cache_secs=300 } protocols = " imap pop3" ssl_cert = Hello, there is a way with a sieve rule to add a Date: header when it is missing? Adding one with the time of reception of the message or using the date from the the first Received: header would be good options. Unfortunately I'm receiving some useful automated messages that lack a Date header and this screws up the sorting in my imap clients. I have a script to fix those acting on the Maildir storage, but I would prefer to have the thing solved more radically. Thanks. Cheers, Daniele From ricardo at wenn.com Thu Jul 17 14:24:12 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Thu, 17 Jul 2014 15:24:12 +0100 Subject: Postfix user@domain splitting In-Reply-To: <53C68499.3000005@wenn.com> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> <53C68499.3000005@wenn.com> Message-ID: <53C7DC8C.9080401@wenn.com> Latest config http://pastebin.com/XKNn6W24 Ricardo Branco wrote, On 16/07/2014 14:56: > Shows that auth is not honouring the %n i have. > Does the username_format need to be only in the userdb section or also the passdb part? > > http://pastie.org/9396504 > > Ricardo Branco wrote, On 15/07/2014 18:23: >> That was done for testing to see if it made any difference when I moved to LDA, in LDA mode it seems to not care if >> that is %n or %u, it always takes the first part of the email address which is weird. >> Ive just tested again to confirm on %n and its not working so ive reverted again back to LDA which does. Seems to not >> matter how that variable is set it does not do anything. >> >> When using %n ive tried to see if I can login via IMAP with the whole username but again no, this is the error, note >> the difference between the 'user' field on each line. >> >> Jul 15 18:22:17 imap-login: Info: Login: user=, method=PLAIN, rip=10.0.0.180, lip=10.100.0.198, >> mpid=9493, session= >> Jul 15 18:22:20 imap-login: Info: Disconnected: Shutting down (auth failed, 4 attempts in 37 secs): >> user=, method=PLAIN, rip=10.0.0.3, lip=10.100.0.198, TLS, session= >> >> Steffen Kaiser wrote, On 15/07/2014 13:18: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Tue, 15 Jul 2014, Ricardo Branco wrote: >>> >>>> Attached files >>>> >>>> Nick Edwards wrote, On 15/07/2014 10:19: >>>>> you need to show doveconf -n >>>>> and what you have in the master.conf for dovecot >>>>> >>>>> On 7/15/14, Ricardo Branco wrote: >>>>>> I have been trying looking though all the wiki documents to setup LMTP. >>>>>> It now seems to all be connected except that it keeps saying that the >>>>>> user is not recognised when postfix sends to LMTP, it sends the full >>>>>> recipent email address but seems that on the dovecot side it is unable >>>>>> to work with this. >>>>>> I have checked the userdb and made sure its using %n but alas it still >>>>>> does not work. >>> >>> userdb { >>> args = username_format=%u /etc/passwd >>> driver = passwd-file >>> name = passwd-file >>> } >>> >>> In opposite to your sentence I see a %u there. >>> >>>>>> Currently ive had to revert to using LDA as it works fine with that but >>>>>> i still dont know how as the postfix config variable $RECIPIENT is the >>>>>> full email address and does not seem to matter to LDA. >>>>>> >>>> >>>> >>> >>> - -- Steffen Kaiser >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.11 (GNU/Linux) >>> >>> iQEVAwUBU8UcInz1H7kL/d9rAQKXQAgAmu6NnZOqdQKEgKhk6q/CPtXza+dkUh7f >>> 4Ms2tJFw2krwKNeZOvKGOsEeD7XyFDYpfZFDqEewjffqlABUUytIRPXzD3xFvzXV >>> DuXTW1VseEP26ewR7odHN9J+WL1Unh52HnxFgM63Bo1IwYzF84K09VO3DxqobuF7 >>> S8MqQYj6MPqB73IZUbVzRkCDBM0mv52Gx14LFmmPXbphgZFmtixkUy2CpPOT/l02 >>> 0aBSsJZqV/ySKcB2V5UNCj8GoGvwyH3Jh9RFeNIlUKYZYT9s534rfbKu7+T6645I >>> 67daEtZjfAbBOi/foqh41kbSpSaHIMvF970EP/EozFgMBsnghQ+SLg== >>> =6YKs >>> -----END PGP SIGNATURE----- From h.reindl at thelounge.net Thu Jul 17 14:30:52 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 17 Jul 2014 16:30:52 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7DA08.6020506@grinta.net> References: <53C7DA08.6020506@grinta.net> Message-ID: <53C7DE1C.30908@thelounge.net> Am 17.07.2014 16:13, schrieb Daniele Nicolodi: > there is a way with a sieve rule to add a Date: header when it is > missing? Adding one with the time of reception of the message or using > the date from the the first Received: header would be good options. > > Unfortunately I'm receiving some useful automated messages that lack a > Date header and this screws up the sorting in my imap clients. I have a > script to fix those acting on the Maildir storage, but I would prefer to > have the thing solved more radically in no case that's dovecot related if at all the MTA has to deal with metadata as it does with missing message-id's - LDA/LMTP should never change anything inside a message and just store "as it is" BTW: i guess smokeping Fedora has fixed that after a bugreport from me months ago -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From Jochen.Bern at LINworks.de Thu Jul 17 14:40:54 2014 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Thu, 17 Jul 2014 16:40:54 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7DA08.6020506@grinta.net> References: <53C7DA08.6020506@grinta.net> Message-ID: <53C7E076.1090909@LINworks.de> On -10.01.-28163 20:59, Daniele Nicolodi wrote: > Unfortunately I'm receiving some useful automated messages that lack a > Date header and this screws up the sorting in my imap clients. I have a > script to fix those acting on the Maildir storage, but I would prefer to > have the thing solved more radically. RFC 5322 3.6. (and AFAIK *all* its predecessors) marks the Date: header as mandatory. sendmail used to forcibly add one if missing, I'm not sure about other MTAs (and MSAs). I'ld recommend to try fixing the problem as early and globally as possible, rather than on the last yard into *one specific* mailbox. Regards, J. Bern -- *NEU* - NEC IT-Infrastruktur-Produkte im : Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel From daniele at grinta.net Thu Jul 17 14:46:25 2014 From: daniele at grinta.net (Daniele Nicolodi) Date: Thu, 17 Jul 2014 16:46:25 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7DE1C.30908@thelounge.net> References: <53C7DA08.6020506@grinta.net> <53C7DE1C.30908@thelounge.net> Message-ID: <53C7E1C1.8070305@grinta.net> Hello Harald, On 17/07/2014 16:30, Reindl Harald wrote: > > Am 17.07.2014 16:13, schrieb Daniele Nicolodi: >> there is a way with a sieve rule to add a Date: header when it is >> missing? Adding one with the time of reception of the message or using >> the date from the the first Received: header would be good options. >> >> Unfortunately I'm receiving some useful automated messages that lack a >> Date header and this screws up the sorting in my imap clients. I have a >> script to fix those acting on the Maildir storage, but I would prefer to >> have the thing solved more radically > > in no case that's dovecot related Indeed. Maybe my question was not clear, what I'm asking is a way to add the header to the specific messages via a sieve rule. I can add headers via sieve but I don't know if there is a way to get the current time or to set an header with information from another. > if at all the MTA has to deal with metadata as it does > with missing message-id's - LDA/LMTP should never change > anything inside a message and just store "as it is" The default behavior of the clients I'm using is to use the time at which the message has been retrieved from the IMAP server, which does not really make sense to me. > BTW: > i guess smokeping > Fedora has fixed that after a bugreport from me months ago I don't know what smokeping is. Cheers, Daniele From h.reindl at thelounge.net Thu Jul 17 14:50:20 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 17 Jul 2014 16:50:20 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7E1C1.8070305@grinta.net> References: <53C7DA08.6020506@grinta.net> <53C7DE1C.30908@thelounge.net> <53C7E1C1.8070305@grinta.net> Message-ID: <53C7E2AC.6070304@thelounge.net> Am 17.07.2014 16:46, schrieb Daniele Nicolodi: > Hello Harald, > > On 17/07/2014 16:30, Reindl Harald wrote: >> >> Am 17.07.2014 16:13, schrieb Daniele Nicolodi: >>> there is a way with a sieve rule to add a Date: header when it is >>> missing? Adding one with the time of reception of the message or using >>> the date from the the first Received: header would be good options. >>> >>> Unfortunately I'm receiving some useful automated messages that lack a >>> Date header and this screws up the sorting in my imap clients. I have a >>> script to fix those acting on the Maildir storage, but I would prefer to >>> have the thing solved more radically >> >> in no case that's dovecot related > > Indeed. Maybe my question was not clear, what I'm asking is a way to add > the header to the specific messages via a sieve rule. I can add headers > via sieve but I don't know if there is a way to get the current time or > to set an header with information from another. as said: fix the application or try to solve that at MTA level >> if at all the MTA has to deal with metadata as it does >> with missing message-id's - LDA/LMTP should never change >> anything inside a message and just store "as it is" > > The default behavior of the clients I'm using is to use the time at > which the message has been retrieved from the IMAP server, which does > not really make sense to me. because the date header is mandatory undefined behavior i had running MTA's reject any message missing date or message-id at all >> BTW: >> i guess smokeping >> Fedora has fixed that after a bugreport from me months ago > > I don't know what smokeping is http://oss.oetiker.ch/smokeping/ well, it was a localized date header, not a missing one buit the result is the same - no date at all displayed by clients https://bugzilla.redhat.com/show_bug.cgi?id=1080949 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From jost+lists at dimejo.at Thu Jul 17 14:51:02 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Thu, 17 Jul 2014 16:51:02 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7DA08.6020506@grinta.net> References: <53C7DA08.6020506@grinta.net> Message-ID: <53C7E2D6.1010700@dimejo.at> Am 17.07.2014 16:13, schrieb Daniele Nicolodi: > Hello, > > there is a way with a sieve rule to add a Date: header when it is > missing? Adding one with the time of reception of the message or using > the date from the the first Received: header would be good options. > > Unfortunately I'm receiving some useful automated messages that lack a > Date header and this screws up the sorting in my imap clients. I have a > script to fix those acting on the Maildir storage, but I would prefer to > have the thing solved more radically. > > Thanks. Cheers, > Daniele > http://tools.ietf.org/html/rfc5260#section-5.1 Finally, currentdate can be used in conjunction with the editheader extension to insert a header-field containing date/time information: require ["variables", "date", "editheader"]; if currentdate :matches "std11" "*" {addheader "Processing-date" "${0}";} -- Alex JOST From ebroch at whitehorsetc.com Thu Jul 17 15:32:35 2014 From: ebroch at whitehorsetc.com (Eric Broch) Date: Thu, 17 Jul 2014 09:32:35 -0600 Subject: dspam dovecot-lda Message-ID: <53C7EC93.9030305@whitehorsetc.com> Hello list, Is there a way to call a spam filter in dovecot-lda like maildrop uses the xfilter command within the .mailfilter file to do the same? Eric From bourek at thinline.cz Thu Jul 17 15:34:19 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Thu, 17 Jul 2014 17:34:19 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7E076.1090909@LINworks.de> References: <53C7DA08.6020506@grinta.net> <53C7E076.1090909@LINworks.de> Message-ID: <53C7ECFB.8080602@thinline.cz> On 17.7.2014 16:40, Jochen Bern wrote: > On -10.01.-28163 20:59, Daniele Nicolodi wrote: >> Unfortunately I'm receiving some useful automated messages that lack a >> Date header and this screws up the sorting in my imap clients. I have a >> script to fix those acting on the Maildir storage, but I would prefer to >> have the thing solved more radically. > > RFC 5322 3.6. (and AFAIK *all* its predecessors) marks the Date: header > as mandatory. sendmail used to forcibly add one if missing, I'm not sure > about other MTAs (and MSAs). I'ld recommend to try fixing the problem as > early and globally as possible, rather than on the last yard into *one > specific* mailbox. > > Regards, > J. Bern > Postfix is able to add the header, if you configure it do so. According to its documentation "this may break DKIM signatures that cover non-existent headers", so it's off by default. (More in man 5 postconf - always_add_missing_headers.) From h.reindl at thelounge.net Thu Jul 17 15:35:28 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 17 Jul 2014 17:35:28 +0200 Subject: dspam dovecot-lda In-Reply-To: <53C7EC93.9030305@whitehorsetc.com> References: <53C7EC93.9030305@whitehorsetc.com> Message-ID: <53C7ED40.6060801@thelounge.net> Am 17.07.2014 17:32, schrieb Eric Broch: > Is there a way to call a spam filter in dovecot-lda like maildrop uses > the xfilter command within the .mailfilter file to do the same? are you aware that dspam is dead and the webinterface pratically not maintained and so very likely full of security bugs? -------- Original-Nachricht -------- Betreff: [Dspam-user] Leaving dspam project Datum: Wed, 09 Jul 2014 16:04:24 +0200 Von: Tom Hendrikx An: dspam-devel at lists.sourceforge.net, dspam-user at lists.sourceforge.net Hello DSPAM community, After a few years of being active in the DSPAM community, I've decided to leave the project. Unlike others who silently stopped responding to mails and other inquiries, I'm documenting my reasons in the hopes that it might be of help/interest to others. When I actively joined the DSPAM project, it was in need of some new blood that helped out on development and other tasks, after most of the original participants of the community takeover from Sensory Networks somehow silently abandoned the project for reasons unknown (to me). After being active for a few years, I think I've seen most of the problems in the DSPAM project, and tried to address a few without result. The main issues I learned are listed below. 1. No active development ------------------------ There is no one working on the DSPAM code. There are numerous bug reports and feature requests that could be addressed, and some parts in DSPAM have been ripe for refactoring or rewriting for a long time, but nobody is putting any effort into it. There is currently only one developer 'active' within the project, but you rarely see activity from this person. The most code changes in the last 2(?) years are from patches contributed through debian bugreports (thank you, debian maintainer). The fact that no one within the project is actively working on the code, creates a sort of chicken-or-egg problem: without existing activity, no major outside contributions can be expected, since no one is interested in becoming the new sole responsible developer in the project. 2. No value seen in making DSPAM more transparent ------------------------------------------------- On several occasions I've raised my voice on making DSPAM more usable to new users, for instance by making error messages more informative, or adding logging of normal operation (i.e. non-errors) so people get a better hang of the product. Changes like this don't 'improve' DSPAM filtering, but the they do make the software easier to use, and its operation more transparent to new and experienced users. Finding issues in software is easier when you actually understand what it's trying to do, which in turn could result in more active users, more useful bug reports, possible more contributed patches and in the end maybe even more developers. Right now DSPAM acts like a sort of black box for anyone not familiar with the source code, and that discourages investigation of odd behavior, which could be any of: configuration errors, bugs or missing (but expected) features. 3. No drive on changing the status quo -------------------------------------- The situation that DSPAM is in right now, a sort of dormant or zombie (not dead but far from alive) status, is not good. It doesn't attract new users, it doesn't attract new developers, actually it only only supports existing, experienced users. Nobody in the community, both in the project maintainers as in the users community, seems to be interested in changing that. Based on my observations, that seems that people seem to think that DSPAM is either feature-complete and bug-free, or they just lack the motivation/energy/time/whatever to contribute anything. Because I care about DSPAM, in the years I've active within the project all of these issues have bothered me multiple times. I've tried to address stuff that I could address, or tried to raise awareness for other things. I didn't get much done though. - From this I can only conclude that DSPAM is a sort of dead project. Just like I wouldn't like to get myself (or my company, for instance) depending on a piece of software in this state, I think that nobody should get the impression that DSPAM is supported by an active community, when that support actually never goes beyond answering easy questions on the users mailing list. Therefore I'm resigning as DSPAM release manager, and will remove myself as project admin from the sourceforge project. I hope others will take up responsibility for the work I leave behind (and unattended tasks listed above, or any tasks I didn't point out), so maybe DPAM will become an active project in the future. Kind regards, Tom Hendrikx PS: I tried to address some of the issues listed above (logging of regular operation, transparent code (including documentation), easier ways of contribution) outside of the DSPAM code base itself, which finally resulted in dspam-milter[1]. I'll continue to develop and support that software, probably until I'll stop using DSPAM myself. If I would ever abandon the project, proper notice (just like this one) will be given. [1] https://github.com/whyscream/dspam-milter ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Dspam-user mailing list Dspam-user at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From asai at globalchangemusic.org Thu Jul 17 15:47:55 2014 From: asai at globalchangemusic.org (Asai) Date: Thu, 17 Jul 2014 08:47:55 -0700 Subject: Dovecot Replication: First Run Message-ID: <53C7F02B.80303@globalchangemusic.org> Greetings, I'm working on building a redundant Dovecot server which will be replicated with my original. I would like to know if there's any potential problems I could run into in running this for the first time. For example, during an initial sync is it possible for the new server to sync improperly with the original and delete all of the emails on the original? Are there any gotchas that I should be aware of when doing a first run? -- --Asai From daniele at grinta.net Thu Jul 17 16:19:22 2014 From: daniele at grinta.net (Daniele Nicolodi) Date: Thu, 17 Jul 2014 18:19:22 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7ECFB.8080602@thinline.cz> References: <53C7DA08.6020506@grinta.net> <53C7E076.1090909@LINworks.de> <53C7ECFB.8080602@thinline.cz> Message-ID: <53C7F78A.3020903@grinta.net> On 17/07/2014 17:34, Jiri Bourek wrote: > On 17.7.2014 16:40, Jochen Bern wrote: >> On -10.01.-28163 20:59, Daniele Nicolodi wrote: >>> Unfortunately I'm receiving some useful automated messages that lack a >>> Date header and this screws up the sorting in my imap clients. I have a >>> script to fix those acting on the Maildir storage, but I would prefer to >>> have the thing solved more radically. >> >> RFC 5322 3.6. (and AFAIK *all* its predecessors) marks the Date: header >> as mandatory. sendmail used to forcibly add one if missing, I'm not sure >> about other MTAs (and MSAs). I'ld recommend to try fixing the problem as >> early and globally as possible, rather than on the last yard into *one >> specific* mailbox. >> >> Regards, >> J. Bern >> > > Postfix is able to add the header, if you configure it do so. According > to its documentation "this may break DKIM signatures that cover > non-existent headers", so it's off by default. > > (More in man 5 postconf - always_add_missing_headers.) Thanks Jiri, this is the best solution. Cheers, Daniele From daniele at grinta.net Thu Jul 17 16:21:31 2014 From: daniele at grinta.net (Daniele Nicolodi) Date: Thu, 17 Jul 2014 18:21:31 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7E2D6.1010700@dimejo.at> References: <53C7DA08.6020506@grinta.net> <53C7E2D6.1010700@dimejo.at> Message-ID: <53C7F80B.4050803@grinta.net> On 17/07/2014 16:51, Alex JOST wrote: > Am 17.07.2014 16:13, schrieb Daniele Nicolodi: >> Hello, >> >> there is a way with a sieve rule to add a Date: header when it is >> missing? Adding one with the time of reception of the message or using >> the date from the the first Received: header would be good options. >> >> Unfortunately I'm receiving some useful automated messages that lack a >> Date header and this screws up the sorting in my imap clients. I have a >> script to fix those acting on the Maildir storage, but I would prefer to >> have the thing solved more radically. >> >> Thanks. Cheers, >> Daniele >> > > http://tools.ietf.org/html/rfc5260#section-5.1 > > Finally, currentdate can be used in conjunction with the editheader > extension to insert a header-field containing date/time information: > require ["variables", "date", "editheader"]; > if currentdate :matches "std11" "*" > {addheader "Processing-date" "${0}";} > Thanks Alex, I expanded this a bit to use the date from the Received header: if not exists "Date" { if date :matches "received" "std11" "*" { addheader "Date" "${0}"; } } However I believe the issue is better fixed in the MTA and I instructed my Postfix to do it. Cheers, Daniele From daniele at grinta.net Thu Jul 17 16:24:08 2014 From: daniele at grinta.net (Daniele Nicolodi) Date: Thu, 17 Jul 2014 18:24:08 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7E2AC.6070304@thelounge.net> References: <53C7DA08.6020506@grinta.net> <53C7DE1C.30908@thelounge.net> <53C7E1C1.8070305@grinta.net> <53C7E2AC.6070304@thelounge.net> Message-ID: <53C7F8A8.9090009@grinta.net> On 17/07/2014 16:50, Reindl Harald wrote: > as said: > fix the application or try to solve that at MTA level If it were so simple to convince people to fix their applications (I especially hate applications refusing the "+" character in email address local part), the world would definitely be a better place :) Cheers, Daniele From h.reindl at thelounge.net Thu Jul 17 17:27:58 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 17 Jul 2014 19:27:58 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7F8A8.9090009@grinta.net> References: <53C7DA08.6020506@grinta.net> <53C7DE1C.30908@thelounge.net> <53C7E1C1.8070305@grinta.net> <53C7E2AC.6070304@thelounge.net> <53C7F8A8.9090009@grinta.net> Message-ID: <53C8079E.5060002@thelounge.net> Am 17.07.2014 18:24, schrieb Daniele Nicolodi: > On 17/07/2014 16:50, Reindl Harald wrote: >> as said: >> fix the application or try to solve that at MTA level > > If it were so simple to convince people to fix their applications (I > especially hate applications refusing the "+" character in email address > local part), the world would definitely be a better place :) that's why i said "or try to solve that at MTA level" sieve is just the wrong tool for that -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From Jost.Krieger+dovecot at rub.de Thu Jul 17 19:19:33 2014 From: Jost.Krieger+dovecot at rub.de (Jost Krieger) Date: Thu, 17 Jul 2014 21:19:33 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <53C7E2AC.6070304@thelounge.net> References: <53C7DA08.6020506@grinta.net> <53C7DE1C.30908@thelounge.net> <53C7E1C1.8070305@grinta.net> <53C7E2AC.6070304@thelounge.net> Message-ID: <20140717191933.GC15635@ruhr-uni-bochum.de> On Thu, Jul 17, 2014 at 04:50:20PM +0200, Reindl Harald wrote: > as said: > fix the application or try to solve that at MTA level The correct place would be the MSA. If all mail genrated by Web appliocations woul pass through a working MSA fixing them up, a lot of problems would go away. > >> if at all the MTA has to deal with metadata as it does > >> with missing message-id's - LDA/LMTP should never change > >> anything inside a message and just store "as it is" An intermediate MTA has no business meddling with headers except for trace headers as specified in the standard. > because the date header is mandatory > undefined behavior right > i had running MTA's reject any message missing date or message-id at all Message-ID is SHOULD. Only Date and From are required. And refusing mails without them is a good strategy, if your (recipient) customers don't complain. Jost -- | Helft Spam ausrotten! HTML in Mail ist unh?flich. | | Postmaster, JAPH, manchmal Wahrsager am RZ der RUB | | Bitte immer an Funktionsadressen schreiben: Postmaster at rub.de | From h.reindl at thelounge.net Thu Jul 17 19:48:28 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 17 Jul 2014 21:48:28 +0200 Subject: Sieve: adding Date: header when missing In-Reply-To: <20140717191933.GC15635@ruhr-uni-bochum.de> References: <53C7DA08.6020506@grinta.net> <53C7DE1C.30908@thelounge.net> <53C7E1C1.8070305@grinta.net> <53C7E2AC.6070304@thelounge.net> <20140717191933.GC15635@ruhr-uni-bochum.de> Message-ID: <53C8288C.2060301@thelounge.net> Am 17.07.2014 21:19, schrieb Jost Krieger: > On Thu, Jul 17, 2014 at 04:50:20PM +0200, Reindl Harald wrote: > >> as said: >> fix the application or try to solve that at MTA level > > The correct place would be the MSA. pfff MSA / MTA - 999 out of 1000 "MSA" setups are just postfix or exim on localhost and no need for RFC6409 at all > If all mail genrated by Web appliocations woul pass through a working > MSA fixing them up, a lot of problems would go away sane webservers have a MTA only listening on 127.0.0.1 and if it is only to queue them proper and finally relay them to the destination the first thing sane webservers do is block mail() functions like PHP's one using the sendmail binary and enforce using SMTP -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From skdovecot at smail.inf.fh-brs.de Thu Jul 17 20:36:40 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen) Date: Thu, 17 Jul 2014 22:36:40 +0200 Subject: Postfix user@domain splitting In-Reply-To: <53C7DC8C.9080401@wenn.com> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> <53C68499.3000005@wenn.com> <53C7DC8C.9080401@wenn.com> Message-ID: <53C833D8.2060300@smail.inf.fh-brs.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ricardo Branco wrote: > Latest config > > http://pastebin.com/XKNn6W24 > > Ricardo Branco wrote, On 16/07/2014 14:56: >> Shows that auth is not honouring the %n i have. Does the >> username_format need to be only in the userdb section or also the >> passdb part? >> >> http://pastie.org/9396504 >> >> Ricardo Branco wrote, On 15/07/2014 18:23: >>> That was done for testing to see if it made any difference when >>> I moved to LDA, in LDA mode it seems to not care if that is %n >>> or %u, it always takes the first part of the email address >>> which is weird. Ive just tested again to confirm on %n and its >>> not working so ive reverted again back to LDA which does. Seems >>> to not matter how that variable is set it does not do >>> anything. >>> >>> When using %n ive tried to see if I can login via IMAP with the >>> whole username but again no, this is the error, note the >>> difference between the 'user' field on each line. >>> >>> Jul 15 18:22:17 imap-login: Info: Login: >>> user=, method=PLAIN, rip=10.0.0.180, >>> lip=10.100.0.198, mpid=9493, session= Jul 15 >>> 18:22:20 imap-login: Info: Disconnected: Shutting down (auth >>> failed, 4 attempts in 37 secs): >>> user=, method=PLAIN, rip=10.0.0.3, >>> lip=10.100.0.198, TLS, session= Hi Ricardo, I seem to miss something: You are talking about LMTP and LDA, then present a log of an IMAP login attempt. Neither LDA not LMTP should need any authentification, where should the password come from? And yes, for auth you will need %n in passdb, too. username_format is not documented for passdb { driver = pam}, but you could try. Could you post a log of a LMTP delivery, when %n is in effect _and_ you are sure have reloaded Dovecot? >>> Steffen Kaiser wrote, On 15/07/2014 13:18: > On Tue, 15 Jul 2014, Ricardo Branco wrote: > >>>>>> Attached files >>>>>> >>>>>> Nick Edwards wrote, On 15/07/2014 10:19: >>>>>>> you need to show doveconf -n and what you have in the >>>>>>> master.conf for dovecot >>>>>>> >>>>>>> On 7/15/14, Ricardo Branco wrote: >>>>>>>> I have been trying looking though all the wiki >>>>>>>> documents to setup LMTP. It now seems to all be >>>>>>>> connected except that it keeps saying that the user >>>>>>>> is not recognised when postfix sends to LMTP, it >>>>>>>> sends the full recipent email address but seems that >>>>>>>> on the dovecot side it is unable to work with this. I >>>>>>>> have checked the userdb and made sure its using %n >>>>>>>> but alas it still does not work. > > userdb { args = username_format=%u /etc/passwd driver = > passwd-file name = passwd-file } > > In opposite to your sentence I see a %u there. > >>>>>>>> Currently ive had to revert to using LDA as it works >>>>>>>> fine with that but i still dont know how as the >>>>>>>> postfix config variable $RECIPIENT is the full email >>>>>>>> address and does not seem to matter to LDA. >>>>>>>> >>>>>> >>>>>> > > -- Steffen Kaiser - -- Steffen Kaiser H Bonn-Rhein-Sieg | e-mail: Steffen.Kaiser at H-BRS.DE FB Informatik | Grantham-Allee 20 | phone : +49 2241/865-203 53757 Sankt Augustin | Germany - Deutschland | fax : +49 2241/865-8203 - -- Steffen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEVAwUBU8gz2HD1/YhP6VMHAQL4GAf/XSv7IGGacR1R/KOWP+DjBiqtiIT33Niw DfZjRykZGYn1S2wb0S0UT9bvp0mxYABxSPuwEHOkAu56qtIJz/l37eneNE/mtyag 2ZxnWa6cJsEngKgkGA9+2OnKKZEeU5fI3RhN6VRDjCxwV0DnI9fpf/vvYli1s3GK LMeZq3cDVzZ+L23B2hBmWAOd1C9JU2mVRAchBF83TiEn+n7vAYGPGD9enFMphVBx PjF24YRquVYMW3Dv+bSrPRgAFo/WCoZ7Lur7kZ6f3jaO6irUw7yMYvu8GdWi8AFB y5CGOUBhCdsgEuZB4i2n1u+otgK+VhnF9+dLWSM5QB8uRTs+WRi5/w== =Gpq3 -----END PGP SIGNATURE----- From ricardo at wenn.com Thu Jul 17 21:10:29 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Thu, 17 Jul 2014 22:10:29 +0100 Subject: Postfix user@domain splitting In-Reply-To: <53C833D8.2060300@smail.inf.fh-brs.de> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> <53C68499.3000005@wenn.com> <53C7DC8C.9080401@wenn.com> <53C833D8.2060300@smail.inf.fh-brs.de> Message-ID: <53C83BC5.4050506@wenn.com> We have been using LDA in the past with our old Sendmail system, on our new mail server we were proposing to use LMTP with Postfix. LMTP does not work at all, it just keeps saying that the user is not recognised, LDA on the otherhand does work. I am unable to login via IMAP/POP using the full email address of the user even after the settings below are set. I have set auth_username_format=%n, also put username_format=%n in the userdb, even tried it in PAM but that just breaks it all. I just cant seem to make it all work, if i just use the username then its all fine but that does not resolve where i am planning to do. On 17/07/2014 21:36, Steffen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ricardo Branco wrote: >> Latest config >> >> http://pastebin.com/XKNn6W24 >> >> Ricardo Branco wrote, On 16/07/2014 14:56: >>> Shows that auth is not honouring the %n i have. Does the >>> username_format need to be only in the userdb section or also the >>> passdb part? >>> >>> http://pastie.org/9396504 >>> >>> Ricardo Branco wrote, On 15/07/2014 18:23: >>>> That was done for testing to see if it made any difference when >>>> I moved to LDA, in LDA mode it seems to not care if that is %n >>>> or %u, it always takes the first part of the email address >>>> which is weird. Ive just tested again to confirm on %n and its >>>> not working so ive reverted again back to LDA which does. Seems >>>> to not matter how that variable is set it does not do >>>> anything. >>>> >>>> When using %n ive tried to see if I can login via IMAP with the >>>> whole username but again no, this is the error, note the >>>> difference between the 'user' field on each line. >>>> >>>> Jul 15 18:22:17 imap-login: Info: Login: >>>> user=, method=PLAIN, rip=10.0.0.180, >>>> lip=10.100.0.198, mpid=9493, session= Jul 15 >>>> 18:22:20 imap-login: Info: Disconnected: Shutting down (auth >>>> failed, 4 attempts in 37 secs): >>>> user=, method=PLAIN, rip=10.0.0.3, >>>> lip=10.100.0.198, TLS, session= > > Hi Ricardo, > > I seem to miss something: You are talking about LMTP and LDA, then > present a log of an IMAP login attempt. Neither LDA not LMTP should > need any authentification, where should the password come from? And > yes, for auth you will need %n in passdb, too. username_format is not > documented for passdb { driver = pam}, but you could try. > > Could you post a log of a LMTP delivery, when %n is in effect _and_ > you are sure have reloaded Dovecot? > >>>> Steffen Kaiser wrote, On 15/07/2014 13:18: >> On Tue, 15 Jul 2014, Ricardo Branco wrote: >> >>>>>>> Attached files >>>>>>> >>>>>>> Nick Edwards wrote, On 15/07/2014 10:19: >>>>>>>> you need to show doveconf -n and what you have in the >>>>>>>> master.conf for dovecot >>>>>>>> >>>>>>>> On 7/15/14, Ricardo Branco wrote: >>>>>>>>> I have been trying looking though all the wiki >>>>>>>>> documents to setup LMTP. It now seems to all be >>>>>>>>> connected except that it keeps saying that the user >>>>>>>>> is not recognised when postfix sends to LMTP, it >>>>>>>>> sends the full recipent email address but seems that >>>>>>>>> on the dovecot side it is unable to work with this. I >>>>>>>>> have checked the userdb and made sure its using %n >>>>>>>>> but alas it still does not work. >> userdb { args = username_format=%u /etc/passwd driver = >> passwd-file name = passwd-file } >> >> In opposite to your sentence I see a %u there. >> >>>>>>>>> Currently ive had to revert to using LDA as it works >>>>>>>>> fine with that but i still dont know how as the >>>>>>>>> postfix config variable $RECIPIENT is the full email >>>>>>>>> address and does not seem to matter to LDA. >>>>>>>>> >>>>>>> >> -- Steffen Kaiser > - -- > > Steffen Kaiser > > H Bonn-Rhein-Sieg | e-mail: Steffen.Kaiser at H-BRS.DE > FB Informatik | > Grantham-Allee 20 | phone : +49 2241/865-203 > 53757 Sankt Augustin | > Germany - Deutschland | fax : +49 2241/865-8203 > > - -- > Steffen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Darwin) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEVAwUBU8gz2HD1/YhP6VMHAQL4GAf/XSv7IGGacR1R/KOWP+DjBiqtiIT33Niw > DfZjRykZGYn1S2wb0S0UT9bvp0mxYABxSPuwEHOkAu56qtIJz/l37eneNE/mtyag > 2ZxnWa6cJsEngKgkGA9+2OnKKZEeU5fI3RhN6VRDjCxwV0DnI9fpf/vvYli1s3GK > LMeZq3cDVzZ+L23B2hBmWAOd1C9JU2mVRAchBF83TiEn+n7vAYGPGD9enFMphVBx > PjF24YRquVYMW3Dv+bSrPRgAFo/WCoZ7Lur7kZ6f3jaO6irUw7yMYvu8GdWi8AFB > y5CGOUBhCdsgEuZB4i2n1u+otgK+VhnF9+dLWSM5QB8uRTs+WRi5/w== > =Gpq3 > -----END PGP SIGNATURE----- From ricardo at wenn.com Thu Jul 17 21:20:45 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Thu, 17 Jul 2014 22:20:45 +0100 Subject: user@domain splitting not working In-Reply-To: <53C83BC5.4050506@wenn.com> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> <53C68499.3000005@wenn.com> <53C7DC8C.9080401@wenn.com> <53C833D8.2060300@smail.inf.fh-brs.de> <53C83BC5.4050506@wenn.com> Message-ID: <53C83E2D.6050702@wenn.com> Also just to note that Postfix is not the problem here, that has now been ruled out Ive been trying the LMTP protocol directly and still confirm the problem.. 220 localhost I am ready. LHLO wenn.com 250-localhost 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING mail from: 250 2.1.0 OK rcpt to: 550 5.1.1 User doesn't exist: it at wenn.com quit 221 2.0.0 OK All I get in the LMTP log is.. Jul 17 22:13:57 lmtp(23016): Info: Connect from 127.0.0.1 Jul 17 22:14:16 lmtp(23016): Info: Disconnect from 127.0.0.1: Successful quit The Auth log.. Jul 17 22:19:47 auth: Debug: master in: USER 1 it at wenn.com service=lmtp lip=127.0.0.1 lport=24 rip=127.0.0.1 rport=41872 Jul 17 22:19:47 auth: Debug: userdb out: NOTFOUND 1 On 17/07/2014 22:10, Ricardo Branco wrote: > We have been using LDA in the past with our old Sendmail system, on > our new mail server we were proposing to use LMTP with Postfix. > LMTP does not work at all, it just keeps saying that the user is not > recognised, LDA on the otherhand does work. > I am unable to login via IMAP/POP using the full email address of the > user even after the settings below are set. > I have set auth_username_format=%n, also put username_format=%n in the > userdb, even tried it in PAM but that just breaks it all. > I just cant seem to make it all work, if i just use the username then > its all fine but that does not resolve where i am planning to do. > > On 17/07/2014 21:36, Steffen wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Ricardo Branco wrote: >>> Latest config >>> >>> http://pastebin.com/XKNn6W24 >>> >>> Ricardo Branco wrote, On 16/07/2014 14:56: >>>> Shows that auth is not honouring the %n i have. Does the >>>> username_format need to be only in the userdb section or also the >>>> passdb part? >>>> >>>> http://pastie.org/9396504 >>>> >>>> Ricardo Branco wrote, On 15/07/2014 18:23: >>>>> That was done for testing to see if it made any difference when >>>>> I moved to LDA, in LDA mode it seems to not care if that is %n >>>>> or %u, it always takes the first part of the email address >>>>> which is weird. Ive just tested again to confirm on %n and its >>>>> not working so ive reverted again back to LDA which does. Seems >>>>> to not matter how that variable is set it does not do >>>>> anything. >>>>> >>>>> When using %n ive tried to see if I can login via IMAP with the >>>>> whole username but again no, this is the error, note the >>>>> difference between the 'user' field on each line. >>>>> >>>>> Jul 15 18:22:17 imap-login: Info: Login: >>>>> user=, method=PLAIN, rip=10.0.0.180, >>>>> lip=10.100.0.198, mpid=9493, session= Jul 15 >>>>> 18:22:20 imap-login: Info: Disconnected: Shutting down (auth >>>>> failed, 4 attempts in 37 secs): >>>>> user=, method=PLAIN, rip=10.0.0.3, >>>>> lip=10.100.0.198, TLS, session= >> >> Hi Ricardo, >> >> I seem to miss something: You are talking about LMTP and LDA, then >> present a log of an IMAP login attempt. Neither LDA not LMTP should >> need any authentification, where should the password come from? And >> yes, for auth you will need %n in passdb, too. username_format is not >> documented for passdb { driver = pam}, but you could try. >> >> Could you post a log of a LMTP delivery, when %n is in effect _and_ >> you are sure have reloaded Dovecot? >> >>>>> Steffen Kaiser wrote, On 15/07/2014 13:18: >>> On Tue, 15 Jul 2014, Ricardo Branco wrote: >>> >>>>>>>> Attached files >>>>>>>> >>>>>>>> Nick Edwards wrote, On 15/07/2014 10:19: >>>>>>>>> you need to show doveconf -n and what you have in the >>>>>>>>> master.conf for dovecot >>>>>>>>> >>>>>>>>> On 7/15/14, Ricardo Branco wrote: >>>>>>>>>> I have been trying looking though all the wiki >>>>>>>>>> documents to setup LMTP. It now seems to all be >>>>>>>>>> connected except that it keeps saying that the user >>>>>>>>>> is not recognised when postfix sends to LMTP, it >>>>>>>>>> sends the full recipent email address but seems that >>>>>>>>>> on the dovecot side it is unable to work with this. I >>>>>>>>>> have checked the userdb and made sure its using %n >>>>>>>>>> but alas it still does not work. >>> userdb { args = username_format=%u /etc/passwd driver = >>> passwd-file name = passwd-file } >>> >>> In opposite to your sentence I see a %u there. >>> >>>>>>>>>> Currently ive had to revert to using LDA as it works >>>>>>>>>> fine with that but i still dont know how as the >>>>>>>>>> postfix config variable $RECIPIENT is the full email >>>>>>>>>> address and does not seem to matter to LDA. >>>>>>>>>> >>>>>>>> >>> -- Steffen Kaiser >> - -- >> Steffen Kaiser >> >> H Bonn-Rhein-Sieg | e-mail: Steffen.Kaiser at H-BRS.DE >> FB Informatik | >> Grantham-Allee 20 | phone : +49 2241/865-203 >> 53757 Sankt Augustin | >> Germany - Deutschland | fax : +49 2241/865-8203 >> >> - -- Steffen >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.9 (Darwin) >> Comment: Using GnuPG with undefined - http://www.enigmail.net/ >> >> iQEVAwUBU8gz2HD1/YhP6VMHAQL4GAf/XSv7IGGacR1R/KOWP+DjBiqtiIT33Niw >> DfZjRykZGYn1S2wb0S0UT9bvp0mxYABxSPuwEHOkAu56qtIJz/l37eneNE/mtyag >> 2ZxnWa6cJsEngKgkGA9+2OnKKZEeU5fI3RhN6VRDjCxwV0DnI9fpf/vvYli1s3GK >> LMeZq3cDVzZ+L23B2hBmWAOd1C9JU2mVRAchBF83TiEn+n7vAYGPGD9enFMphVBx >> PjF24YRquVYMW3Dv+bSrPRgAFo/WCoZ7Lur7kZ6f3jaO6irUw7yMYvu8GdWi8AFB >> y5CGOUBhCdsgEuZB4i2n1u+otgK+VhnF9+dLWSM5QB8uRTs+WRi5/w== >> =Gpq3 >> -----END PGP SIGNATURE----- From jost+lists at dimejo.at Thu Jul 17 22:32:55 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Fri, 18 Jul 2014 00:32:55 +0200 Subject: Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9) In-Reply-To: <53C519BF.6050803@blackrosetech.com> References: <53C47FFB.4040901@blackrosetech.com> <53C502C7.90803@dimejo.at> <53C519BF.6050803@blackrosetech.com> Message-ID: <53C84F17.2020203@dimejo.at> Am 2014-07-15 14:08, schrieb David Gessel: > Good catch, thank you. (I used LAYOUT=fs at first, but found behavior a > little anomalous. I forgot to disable the workarounds). > > This may have stopped the problem of redownloading the entire mailbox > (on restart I got downloading 1 of 8 instead of 1 of 170... 30 of 1330 > in the status pane) . My other mailboxes still need to sync and it > might take a few days to verify that things are stable. I did get 81 > immediate "Warning: Maildir /mail/mydomain.com/gessel//.Bulkmail: > Expunged message reappeared, giving a new UID" warnings on connect, but > if this is the problem, it might stop after all the directories are > resynced. > > I'll update with further data as it comes in. > > I am also somewhat suspect of QRSYNC from this post: > http://dovecot.org/pipermail/dovecot/2011-August/130687.html - though > this is from a long time ago and it seems a little surprising that bugs > on this seemingly useful capability would persist. In any event (if > useful information), my capability enumeration reads: > > # telnet localhost 143 > > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. > a login user pass > a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS > THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN > NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH > ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY > MOVE COMPRESS=DEFLATE QUOTA] Logged in > > > I did try setting mail.server.default.use_condstore;false in > Thunderbird, but that didn't change the behavior of reloading the entire > inbox on startup so I've changed that back as that wasn't the desired > result. > There are too many possible reasons for your problem. You should really start to locate the source of your problem by eliminating 1 possibility after the other instead of tweaking some (hidden) settings in Thunderbird. * Find the Message-ID of one of your duplicates and grep for it on the server * Use a local client (like Mutt or Roundcube) on the server to access the mailbox * Use a different client than Thunderbird on your PC -- Alex JOST From dovecot.org at veggiechinese.net Thu Jul 17 22:58:02 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Thu, 17 Jul 2014 15:58:02 -0700 Subject: ulimit warning when restarting Message-ID: <20140717225802.GA17379@aura.veggiechinese.net> When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 4096), because of default_client_limit # doveconf default_internal_user default_internal_user = dovecot Should dovecot print this warning based on $default_internal_user, or based on root? As root: # ulimit -n 1024 As user dovecot: $ ulimit -n 49152 $ whoami dovecot # grep dovecot /etc/security/limits.conf dovecot hard locks 49152 dovecot hard nofile 49152 dovecot hard maxlogins 8192 dovecot soft locks 49152 dovecot soft nofile 49152 dovecot soft maxlogins 8192 From h.reindl at thelounge.net Thu Jul 17 23:05:33 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 18 Jul 2014 01:05:33 +0200 Subject: ulimit warning when restarting In-Reply-To: <20140717225802.GA17379@aura.veggiechinese.net> References: <20140717225802.GA17379@aura.veggiechinese.net> Message-ID: <53C856BD.80008@thelounge.net> Am 18.07.2014 00:58, schrieb Will Yardley: > When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error: > Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 4096), because of default_client_limit > > # doveconf default_internal_user > default_internal_user = dovecot > > Should dovecot print this warning based on $default_internal_user, or > based on root? > > As root: > # ulimit -n > 1024 > > As user dovecot: > $ ulimit -n > 49152 > $ whoami > dovecot > > # grep dovecot /etc/security/limits.conf > dovecot hard locks 49152 > dovecot hard nofile 49152 > dovecot hard maxlogins 8192 > dovecot soft locks 49152 > dovecot soft nofile 49152 > dovecot soft maxlogins 8192 that all is not applied to services started by init scripts you need the ulimit command inside a from the init script *sourced* file or use something like systemd with native settings http://superuser.com/questions/454465/make-ulimits-work-with-start-stop-daemon http://www.freedesktop.org/software/systemd/man/systemd.exec.html LimitCPU=, LimitFSIZE=, LimitDATA=, LimitSTACK=, LimitCORE=, LimitRSS=, LimitNOFILE=, LimitAS=, LimitNPROC=, LimitMEMLOCK=, LimitLOCKS=, LimitSIGPENDING=, LimitMSGQUEUE=, LimitNICE=, LimitRTPRIO=, LimitRTTIME= These settings control various resource limits for executed processes. See setrlimit(2) for details. Use the string infinity to configure no limit on a specific resource. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From giovanni at neweden.uk.to Fri Jul 18 06:13:06 2014 From: giovanni at neweden.uk.to (giovanni at neweden.uk.to) Date: Fri, 18 Jul 2014 08:13:06 +0200 Subject: Panic: file mail-storage.c Message-ID: <53C8BAF2.5000601@neweden.uk.to> Greetings, In my installation I have debian 7.6 dovecot 2.2.13 dovecot-antispamplugin VERSION=2.0 for this enviroment some users cannot get imap connections. Here below an excerpt the log file. Jul 09 23:54:07 imap(xx at xxx.co.uk): Panic: file mail-storage.c: line 2158(mailbox_copy): assertion failed: (!ctx->unfinished) ul 09 23:54:07 imap(xx at xxx.co.uk): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x6bb4f) [0x7fd796ccdb4f] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x6bbae) [0x7fd796ccdbae] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd796c871ee] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x82519) [0x7fd796fb9519] -> dovecot/imap() [0x40dba4] -> dovecot/imap(command_exec+0x3c) [0x41822c] -> dovecot/imap() [0x417290] -> dovecot/imap() [0x41734a] -> dovecot/imap(client_handle_input+0x115) [0x417605] -> dovecot/imap(client_input+0x72) [0x4179b2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4e) [0x7fd796cde81e] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fd796cdf7f7] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fd796cde8a9] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd796cde928] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd796c8c4d3] -> dovecot/imap(main+0x277) [0x40c067] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fd7968f5ead] -> dovecot/imap() [0x40c1c5] for others users imap connection is ok with antispam plugin working fine (antispam_backend = spool2dir) To enable the imap connections for the unlucky users (with the previous error) I had to remove the anti spam plugin. Does anybody is experiencing the same errors? cheers Giovanni From skdovecot at smail.inf.fh-brs.de Fri Jul 18 07:31:28 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 18 Jul 2014 09:31:28 +0200 (CEST) Subject: user@domain splitting not working In-Reply-To: <53C83E2D.6050702@wenn.com> References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> <53C68499.3000005@wenn.com> <53C7DC8C.9080401@wenn.com> <53C833D8.2060300@smail.inf.fh-brs.de> <53C83BC5.4050506@wenn.com> <53C83E2D.6050702@wenn.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 17 Jul 2014, Ricardo Branco wrote: > Also just to note that Postfix is not the problem here, that has now been > ruled out I compiled to current hg version of Dovecot: changeset: 17627:fd0616d553b0 tag: tip user: Timo Sirainen date: Fri Jul 11 16:49:35 2014 +0300 summary: mailbox_list_index=yes: Don't update INBOX's STATUS information to index. I created a new user adduser --gecos 'DV test' --disabled-password dvtest I have setup a Dovecot config with: http://pastebin.com/XKNn6W24 Because sieve did not compile, I removed sieve from your config. Then I added "@" to auth_username_chars, because of this error: Info: userdb(?): Username character disallowed by auth_username_chars: 0x40 (username: dvtest at example.com) Then I ran: (echo LHLO loc; echo 'mail from:'; echo 'rcpt to:'; echo data; sleep 1; echo "To: From: Subject: Test Test .")|socat - UNIX:/var/spool/postfix/private/dovecot-lmtp 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING 250 2.1.0 OK 250 2.1.5 OK 354 OK 250 2.0.0 GjcYKafIyFPPdwAAbZ2bpg Saved ============================== Enabled password for user # passwd dvtest Connect to IMAP # telnet localhost 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL SPECIAL-USE STARTTLS AUTH=PLAIN AUTH=LOGIN] I am ready. 1 login dvtest at example.com pwd Jul 18 09:20:12 auth-worker(31129): Error: passwd-file /etc/passwd: User root has invalid UID '0' Jul 18 09:20:12 auth-worker(31129): Debug: passwd-file /etc/passwd: Read 41 users in 0 secs Jul 18 09:20:12 auth-worker(31129): Debug: pam(dvtest,127.0.0.1): lookup service=dovecot Jul 18 09:20:12 auth-worker(31129): Debug: pam(dvtest,127.0.0.1): #1/1 style=1 msg=Password: Jul 18 09:20:12 auth: Debug: client passdb out: OK 1 user=dvtest original_user=dvtest at example.com Jul 18 09:20:12 auth: Debug: master in: REQUEST 3026321409 31071 1 1fd6a55253e45ae1eda745081b58bccc session_pid=31130 request_auth_token Jul 18 09:20:12 auth: Debug: passwd-file(dvtest,127.0.0.1,): lookup: user=dvtest file=/etc/passwd Jul 18 09:20:12 auth: Debug: master userdb out: USER 3026321409 dvtest uid=1000 gid=30007 home=/home/dvtest auth_token=df55b42a58c6f34fac16dc677e8f5c5b518a3bbc auth_user=dvtest at example.com Jul 18 09:20:12 imap-login: Info: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=31130, secured, session= Jul 18 09:20:13 imap(dvtest): Error: net_connect_unix(/tmp/dovecot/imap-postlogin) failed: Connection refused Although the login did not succeed completely, I do assume that the last error means that original_user=dvtest at example.com had been authentificated as user=dvtest via PAM successfully as master userdb out has all relevant information. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU8jNUHz1H7kL/d9rAQKcsQf/bTKmToYgZ7/2Yie1Kg0+IsggZMAumEMP 3Jkraj3OkESmXG7xzQK27PDjtB1ipzyDTgVWvzV7u2HMsY5hM68gph/q3TrBfh5O p0N+jCFHUACNQGnPi8yXrt1spVyMovfUmk/rHaWqr87HDSndnR/bsWh1yVoyDUXg 7ZZ+DcDbb8E3lb12eeuZwAnupk5w064h4lLHiGvL0gurbxlCMmaiRPh7NuuaY7YS aqR/o+P4DwU0XS1FCkV59djEkT6K7JyDV3oYdIGn0dEH3m4Lf4gM/wmmncg7QLok qE0kikY9DbOl61mwGV6BE5OI4iM01giMiFsoQpNFLHbi/808lYOGnQ== =4xeB -----END PGP SIGNATURE----- From burak.arslan at arskom.com.tr Fri Jul 18 07:52:21 2014 From: burak.arslan at arskom.com.tr (Burak Arslan) Date: Fri, 18 Jul 2014 10:52:21 +0300 Subject: subfolders in public mailboxes Message-ID: <53C8D235.70202@arskom.com.tr> Hello, I added this to the configuration: namespace { type = public separator = . prefix = public. location = maildir:/var/mail/public subscriptions = no list = yes } and I can list maildirs inside these folders correctly. however, I can't see any subfolders. The issue seems to be that /var/mail/public dir itself is interpreted as a maildir directory. However, what I'd like to do is to have a bunch of directories inside /var/mail/public and treat them as separate maildirs. (I'd like to use this to make a few existing mailboxes public) is this possible? Best regards, Burak From ad+lists at uni-x.org Fri Jul 18 09:29:42 2014 From: ad+lists at uni-x.org (Alexander Dalloz) Date: Fri, 18 Jul 2014 11:29:42 +0200 Subject: ulimit warning when restarting In-Reply-To: <20140717225802.GA17379@aura.veggiechinese.net> References: <20140717225802.GA17379@aura.veggiechinese.net> Message-ID: <53C8E906.2060407@uni-x.org> Am 18.07.2014 00:58, schrieb Will Yardley: > When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error: > Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 4096), because of default_client_limit > > # doveconf default_internal_user > default_internal_user = dovecot > > Should dovecot print this warning based on $default_internal_user, or > based on root? > > As root: > # ulimit -n > 1024 > > As user dovecot: > $ ulimit -n > 49152 > $ whoami > dovecot > > # grep dovecot /etc/security/limits.conf > dovecot hard locks 49152 > dovecot hard nofile 49152 > dovecot hard maxlogins 8192 > dovecot soft locks 49152 > dovecot soft nofile 49152 > dovecot soft maxlogins 8192 > You need to specify the desired ulimit in /etc/sysconfig/dovecot Alexander From ricardo at wenn.com Fri Jul 18 09:44:23 2014 From: ricardo at wenn.com (Ricardo Branco) Date: Fri, 18 Jul 2014 10:44:23 +0100 Subject: user@domain splitting not working In-Reply-To: References: <53C45350.3080102@wenn.com> <53C50C88.4070300@wenn.com> <53C563AA.5060804@wenn.com> <53C68499.3000005@wenn.com> <53C7DC8C.9080401@wenn.com> <53C833D8.2060300@smail.inf.fh-brs.de> <53C83BC5.4050506@wenn.com> <53C83E2D.6050702@wenn.com> Message-ID: <53C8EC77.7070407@wenn.com> Thanks, your test has cracked the problem. You noticed that there was no @ added to the auth_username_chars. Bit of a wild goose chase as I would have thought that as the username had an @ but was not specified in the auth_username_chars it would not even go as far as authdb or passdb checks. The one log I did not check was my standard log file for the error that was noticed by you, I was looking at the debug logs and that message was not posted out to there. Personally and I dont know if its possible to get a fix inplace is that if the username has an invalid character it quits far earlier before getting though to authdb. Steffen Kaiser wrote, On 18/07/2014 08:31: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 17 Jul 2014, Ricardo Branco wrote: > >> Also just to note that Postfix is not the problem here, that has now been ruled out > > I compiled to current hg version of Dovecot: > > changeset: 17627:fd0616d553b0 > tag: tip > user: Timo Sirainen > date: Fri Jul 11 16:49:35 2014 +0300 > summary: mailbox_list_index=yes: Don't update INBOX's STATUS information to index. > > I created a new user > > adduser --gecos 'DV test' --disabled-password dvtest > > I have setup a Dovecot config with: http://pastebin.com/XKNn6W24 > > Because sieve did not compile, I removed sieve from your config. > > Then I added "@" to auth_username_chars, because of this error: > > Info: userdb(?): Username character disallowed by auth_username_chars: 0x40 (username: dvtest at example.com) > > Then I ran: > > (echo LHLO loc; echo 'mail from:'; > echo 'rcpt to:'; echo data; sleep 1; > echo "To: > From: > Subject: Test > > Test > .")|socat - UNIX:/var/spool/postfix/private/dovecot-lmtp > > 250-8BITMIME > 250-ENHANCEDSTATUSCODES > 250 PIPELINING > 250 2.1.0 OK > 250 2.1.5 OK > 354 OK > 250 2.0.0 GjcYKafIyFPPdwAAbZ2bpg Saved > > ============================== > > Enabled password for user > > # passwd dvtest > > Connect to IMAP > > # telnet localhost 143 > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES > THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN > CONTEXT=SEARCH LIST-STATUS ACL SPECIAL-USE STARTTLS AUTH=PLAIN AUTH=LOGIN] I am ready. > 1 login dvtest at example.com pwd > > Jul 18 09:20:12 auth-worker(31129): Error: passwd-file /etc/passwd: User root has invalid UID '0' > Jul 18 09:20:12 auth-worker(31129): Debug: passwd-file /etc/passwd: Read 41 users in 0 secs > Jul 18 09:20:12 auth-worker(31129): Debug: pam(dvtest,127.0.0.1): lookup service=dovecot > Jul 18 09:20:12 auth-worker(31129): Debug: pam(dvtest,127.0.0.1): #1/1 style=1 msg=Password: > Jul 18 09:20:12 auth: Debug: client passdb out: OK 1 user=dvtest original_user=dvtest at example.com > Jul 18 09:20:12 auth: Debug: master in: REQUEST 3026321409 31071 1 1fd6a55253e45ae1eda745081b58bccc > session_pid=31130 request_auth_token > Jul 18 09:20:12 auth: Debug: passwd-file(dvtest,127.0.0.1,): lookup: user=dvtest file=/etc/passwd > Jul 18 09:20:12 auth: Debug: master userdb out: USER 3026321409 dvtest uid=1000 gid=30007 > home=/home/dvtest auth_token=df55b42a58c6f34fac16dc677e8f5c5b518a3bbc auth_user=dvtest at example.com > Jul 18 09:20:12 imap-login: Info: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=31130, > secured, session= > Jul 18 09:20:13 imap(dvtest): Error: net_connect_unix(/tmp/dovecot/imap-postlogin) failed: Connection refused > > Although the login did not succeed completely, I do assume that the last error means that > original_user=dvtest at example.com had been authentificated as user=dvtest via PAM successfully as master userdb out has > all relevant information. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU8jNUHz1H7kL/d9rAQKcsQf/bTKmToYgZ7/2Yie1Kg0+IsggZMAumEMP > 3Jkraj3OkESmXG7xzQK27PDjtB1ipzyDTgVWvzV7u2HMsY5hM68gph/q3TrBfh5O > p0N+jCFHUACNQGnPi8yXrt1spVyMovfUmk/rHaWqr87HDSndnR/bsWh1yVoyDUXg > 7ZZ+DcDbb8E3lb12eeuZwAnupk5w064h4lLHiGvL0gurbxlCMmaiRPh7NuuaY7YS > aqR/o+P4DwU0XS1FCkV59djEkT6K7JyDV3oYdIGn0dEH3m4Lf4gM/wmmncg7QLok > qE0kikY9DbOl61mwGV6BE5OI4iM01giMiFsoQpNFLHbi/808lYOGnQ== > =4xeB > -----END PGP SIGNATURE----- From nathan at schultheiss.fr Fri Jul 18 22:54:15 2014 From: nathan at schultheiss.fr (Nathan Schultheiss) Date: Sat, 19 Jul 2014 00:54:15 +0200 Subject: Difference btw. Dovecot Director and Dovecot Proxy Message-ID: <177b0d4415b968526d6b7ac8b65efca3@schultheiss.fr> Hello, For a few days I try to understand what program (Dovecot Director or Dovecot Proxy) I should use for my email architecture. We are a hospital, and for security reasons, we must host ourselves our emails, and we must leave Google Apps... I wish to make a Dovecot backend for each department of the hospital. Each backend Dovecot has a local storage. Server 01: cardiology Server 02: emergency ... Server 05: administration Dovecot looks in the database which server to use to store email (lmtp) and transfer the mail for storage. I do not understand if I have to work with Dovecot Director or Proxy if I would that LMTP or IMAP request are forwarded to the right backend. Each have self storage and have not access to the other backend storage (no nfs, no network storage, ...). Users indicate imap.hospital.local, this point to Dovecot Director or Proxy and Dovecot check the login/password and forward the user to the right backend. In my database I put user at hospital = storage host 172.16.2.10 = folder /home/vmail/user/ (Maildir) I've read that the Director can refer the user to the same backend when there is a activ session (POP, IMAP, LMTP) But can we tell him to always refer the user to the same backend (IMAP and LMTP) ? I've found this picture schema who user have Dovecot Proxy => Dovecot Director => Dovecot Backend And I'm confused why they have proxy + director ?!? Can anyone tell me if I need to focus on Dovecot Director or Dovecot Proxy to create the architecture of this hospital ? My question is probably stupid for Dovecot sysadmin, but I'm lost in the WIKI :) Thanks in advance, Nathan From bourek at thinline.cz Fri Jul 18 23:31:33 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Sat, 19 Jul 2014 01:31:33 +0200 Subject: Difference btw. Dovecot Director and Dovecot Proxy In-Reply-To: <177b0d4415b968526d6b7ac8b65efca3@schultheiss.fr> References: <177b0d4415b968526d6b7ac8b65efca3@schultheiss.fr> Message-ID: <53C9AE55.9080207@thinline.cz> On 19.7.2014 00:54, Nathan Schultheiss wrote: > Hello, > > For a few days I try to understand what program (Dovecot Director or > Dovecot Proxy) I should use for my email architecture. > We are a hospital, and for security reasons, we must host ourselves our > emails, and we must leave Google Apps... OT: great, the less customers they have, the more they'll be forced to play nice with other mail service providers > > I wish to make a Dovecot backend for each department of the hospital. > Each backend Dovecot has a local storage. > > Server 01: cardiology > Server 02: emergency > ... > Server 05: administration > > Dovecot looks in the database which server to use to store email (lmtp) > and transfer the mail for storage. > > I do not understand if I have to work with Dovecot Director or Proxy if > I would that LMTP or IMAP request are forwarded to the right backend. > Each have self storage and have not access to the other backend storage > (no nfs, no network storage, ...). > > Users indicate imap.hospital.local, this point to Dovecot Director or > Proxy and Dovecot check the login/password and forward the user to the > right backend. > In my database I put user at hospital = storage host 172.16.2.10 = folder > /home/vmail/user/ (Maildir) > > I've read that the Director can refer the user to the same backend when > there is a activ session (POP, IMAP, LMTP) > But can we tell him to always refer the user to the same backend (IMAP > and LMTP) ? > > I've found this picture schema who user have Dovecot Proxy => Dovecot > Director => Dovecot Backend > And I'm confused why they have proxy + director ?!? > > Can anyone tell me if I need to focus on Dovecot Director or Dovecot > Proxy to create the architecture of this hospital ? > > My question is probably stupid for Dovecot sysadmin, but I'm lost in the > WIKI :) > > Thanks in advance, > > Nathan As for IMAP/POP3, I'd go for proxy - it's quite easy to set up if you have users in database, you pretty much just return 'y' as "proxy" field and storage backend's IP address as "host" field in password_query and Dovecot will do the rest. As for LMTP - you didn't mention what MTA are you using but if it's Postfix, you can configure it to use database data to translate user name into storage IP address - then you tell it to use LMTP to deliver to that IP. (Not sure about other MTAs.) From nathan at schultheiss.fr Sat Jul 19 00:14:10 2014 From: nathan at schultheiss.fr (Nathan Schultheiss) Date: Sat, 19 Jul 2014 02:14:10 +0200 (CEST) Subject: Difference btw. Dovecot Director and Dovecot Proxy In-Reply-To: <53C9AE55.9080207@thinline.cz> References: <177b0d4415b968526d6b7ac8b65efca3@schultheiss.fr> <53C9AE55.9080207@thinline.cz> Message-ID: <1093851900.299668.1405728850047.JavaMail.zimbra@schultheiss.fr> Hi, Thank for your reply. OK, if I understand I must just read doc with Dovecot Proxy :) Incoming mail: Postfix (LMTP) => Dovecot Proxy Server => Dovecot Backend Server (Final server and storage server) IMAP: Dovecot Proxy Server => Dovecot Backend Server (Final server and storage server) I can now read more doc about dovecot proxy this WE, and postfix LTMP. Lucky that I made ??is that a new system (no old database, old storage system, ...). The only compatibility is to create email accounts :D Again thank for your clarification about Director/Proxy Dovecot. Regards, Nathan ----- Mail original ----- De: "Jiri Bourek" ?: dovecot at dovecot.org Envoy?: Samedi 19 Juillet 2014 01:31:33 Objet: Re: Difference btw. Dovecot Director and Dovecot Proxy On 19.7.2014 00:54, Nathan Schultheiss wrote: > Hello, > > For a few days I try to understand what program (Dovecot Director or > Dovecot Proxy) I should use for my email architecture. > We are a hospital, and for security reasons, we must host ourselves our > emails, and we must leave Google Apps... OT: great, the less customers they have, the more they'll be forced to play nice with other mail service providers > > I wish to make a Dovecot backend for each department of the hospital. > Each backend Dovecot has a local storage. > > Server 01: cardiology > Server 02: emergency > ... > Server 05: administration > > Dovecot looks in the database which server to use to store email (lmtp) > and transfer the mail for storage. > > I do not understand if I have to work with Dovecot Director or Proxy if > I would that LMTP or IMAP request are forwarded to the right backend. > Each have self storage and have not access to the other backend storage > (no nfs, no network storage, ...). > > Users indicate imap.hospital.local, this point to Dovecot Director or > Proxy and Dovecot check the login/password and forward the user to the > right backend. > In my database I put user at hospital = storage host 172.16.2.10 = folder > /home/vmail/user/ (Maildir) > > I've read that the Director can refer the user to the same backend when > there is a activ session (POP, IMAP, LMTP) > But can we tell him to always refer the user to the same backend (IMAP > and LMTP) ? > > I've found this picture schema who user have Dovecot Proxy => Dovecot > Director => Dovecot Backend > And I'm confused why they have proxy + director ?!? > > Can anyone tell me if I need to focus on Dovecot Director or Dovecot > Proxy to create the architecture of this hospital ? > > My question is probably stupid for Dovecot sysadmin, but I'm lost in the > WIKI :) > > Thanks in advance, > > Nathan As for IMAP/POP3, I'd go for proxy - it's quite easy to set up if you have users in database, you pretty much just return 'y' as "proxy" field and storage backend's IP address as "host" field in password_query and Dovecot will do the rest. As for LMTP - you didn't mention what MTA are you using but if it's Postfix, you can configure it to use database data to translate user name into storage IP address - then you tell it to use LMTP to deliver to that IP. (Not sure about other MTAs.) From asai at globalchangemusic.org Sat Jul 19 18:16:16 2014 From: asai at globalchangemusic.org (Asai) Date: Sat, 19 Jul 2014 11:16:16 -0700 Subject: Dovecot Replication: First Run In-Reply-To: <53C7F02B.80303@globalchangemusic.org> References: <53C7F02B.80303@globalchangemusic.org> Message-ID: <53CAB5F0.3080602@globalchangemusic.org> If what I wrote is a little cryptic, I am talking about using doveadm to sync between two servers. --Asai On 7/17/14 8:47 AM, Asai wrote: > Greetings, > > I'm working on building a redundant Dovecot server which will be > replicated with my original. I would like to know if there's any > potential problems I could run into in running this for the first > time. For example, during an initial sync is it possible for the new > server to sync improperly with the original and delete all of the > emails on the original? > > Are there any gotchas that I should be aware of when doing a first run? > From jerry at seibercom.net Sat Jul 19 19:11:10 2014 From: jerry at seibercom.net (Jerry) Date: Sat, 19 Jul 2014 15:11:10 -0400 Subject: Mailboxes not showing up in MS Outlook Message-ID: <20140719151110.3d4c07fc@scorpio> Sat, 19 Jul 2014 15:03:03 -0400 I am not sure exactly where the problem is here. I am using a sieve script that sorts various incoming messages into their own mailbox. MS Outlook does not show those folders if they are not directly under INBOX. EXAMPLE: drwx------ 31 vmail vmail 1.0K 2014-07-19 14:46:55 EDT ./ drwx------ 3 vmail vmail 512B 2014-07-02 13:52:03 EDT ../ drwx------ 5 vmail vmail 512B 2014-07-10 08:33:03 EDT .Bass/ drwx------ 5 vmail vmail 512B 2014-07-16 07:33:18 EDT .Commissioners/ drwx------ 5 vmail vmail 512B 2014-07-08 13:41:19 EDT .Commissioners.Cordrey/ drwx------ 5 vmail vmail 512B 2014-07-03 17:01:31 EDT .Dover/ drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Drafts/ drwx------ 5 vmail vmail 512B 2014-07-18 19:07:15 EDT .Fitts/ drwx------ 5 vmail vmail 512B 2014-07-08 13:41:19 EDT .Gering/ drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Green/ drwx------ 5 vmail vmail 512B 2014-07-18 18:59:06 EDT .Haywood/ drwx------ 5 vmail vmail 512B 2014-07-03 17:01:31 EDT .Hornik/ drwx------ 5 vmail vmail 512B 2014-07-19 14:45:29 EDT .INBOX.Deleted Items/ drwx------ 5 vmail vmail 512B 2014-07-18 08:58:21 EDT .INBOX.Drafts/ drwx------ 5 vmail vmail 512B 2014-07-18 08:58:13 EDT .INBOX.Junk E-mail/ drwx------ 5 vmail vmail 512B 2014-07-19 14:46:56 EDT .INBOX.PSNC/ drwx------ 5 vmail vmail 512B 2014-07-19 14:46:57 EDT .INBOX.SGWASA/ drwx------ 5 vmail vmail 512B 2014-07-18 08:58:13 EDT .INBOX.Sent Items/ drwx------ 5 vmail vmail 512B 2014-07-19 14:46:58 EDT .INBOX.UNRBA/ drwx------ 5 vmail vmail 512B 2014-07-18 07:40:05 EDT .Locklear/ drwx------ 5 vmail vmail 512B 2014-07-08 13:39:58 EDT .PlanningBoard/ drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Queue/ drwx------ 5 vmail vmail 512B 2014-07-03 17:01:31 EDT .SawyerHomes/ drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Sent/ drwx------ 5 vmail vmail 512B 2014-07-19 06:54:07 EDT .Trash/ drwx------ 5 vmail vmail 512B 2014-07-10 19:19:51 EDT .Vicki/ drwx------ 5 vmail vmail 512B 2014-07-18 15:31:06 EDT .Westall/ drwx------ 2 vmail vmail 23K 2014-07-19 14:44:42 EDT cur/ -rw------- 1 vmail vmail 14B 2014-07-02 20:30:10 EDT dovecot-keywords -rw------- 1 vmail vmail 10K 2014-07-19 14:45:18 EDT dovecot-uidlist -rw------- 1 vmail vmail 8B 2014-07-18 08:58:13 EDT dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0B 2014-07-02 13:52:04 EDT dovecot-uidvalidity.53b446e2 -rw------- 1 vmail vmail 2.6K 2014-07-08 14:26:45 EDT dovecot.index -rw------- 1 vmail vmail 78K 2014-07-19 14:44:42 EDT dovecot.index.cache -rw------- 1 vmail vmail 21K 2014-07-19 14:45:18 EDT dovecot.index.log -rw------- 1 vmail vmail 1.8K 2014-07-19 14:46:55 EDT dovecot.mailbox.log drwx------ 2 vmail vmail 512B 2014-07-02 14:15:43 EDT new/ In the above example, only the following are displayed: .INBOX.Deleted Items/ .INBOX.Drafts/ .INBOX.Junk E-mail/ .INBOX.PSNC/ .INBOX.SGWASA/ .INBOX.Sent Items/ .INBOX.UNRBA/ Do I have a configuration problem? dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.0-RELEASE-p3 amd64 ufs auth_mechanisms = plain login cram-md5 digest-md5 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot mail_location = maildir:/var/mail/vmail/%d/gerard managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = username_format=%u /usr/local/etc/dovecot/user/passwd driver = passwd-file } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/user/passwd driver = passwd-file } passdb { driver = pam } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/user/passwd driver = passwd-file } plugin { sieve_global_dir = /usr/local/etc/dovecot/sieve/ sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve } postmaster_address = postmaster at seibercom.net service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = The attached trivial patch fixes a typo in src/imap-urlauth/imap-urlauth-worker.c. Cheers, Jelmer -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-fix-typo.diff Type: text/x-diff Size: 465 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From jost+lists at dimejo.at Sun Jul 20 14:22:25 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Sun, 20 Jul 2014 16:22:25 +0200 Subject: Mailboxes not showing up in MS Outlook In-Reply-To: <20140719151110.3d4c07fc@scorpio> References: <20140719151110.3d4c07fc@scorpio> Message-ID: <53CBD0A1.3000004@dimejo.at> Am 19.07.2014 21:11, schrieb Jerry: > Sat, 19 Jul 2014 15:03:03 -0400 > > I am not sure exactly where the problem is here. I am using a sieve script > that sorts various incoming messages into their own mailbox. MS Outlook does > not show those folders if they are not directly under INBOX. > > EXAMPLE: > > drwx------ 31 vmail vmail 1.0K 2014-07-19 14:46:55 EDT ./ > drwx------ 3 vmail vmail 512B 2014-07-02 13:52:03 EDT ../ > drwx------ 5 vmail vmail 512B 2014-07-10 08:33:03 EDT .Bass/ > drwx------ 5 vmail vmail 512B 2014-07-16 07:33:18 EDT .Commissioners/ > drwx------ 5 vmail vmail 512B 2014-07-08 13:41:19 EDT .Commissioners.Cordrey/ > drwx------ 5 vmail vmail 512B 2014-07-03 17:01:31 EDT .Dover/ > drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Drafts/ > drwx------ 5 vmail vmail 512B 2014-07-18 19:07:15 EDT .Fitts/ > drwx------ 5 vmail vmail 512B 2014-07-08 13:41:19 EDT .Gering/ > drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Green/ > drwx------ 5 vmail vmail 512B 2014-07-18 18:59:06 EDT .Haywood/ > drwx------ 5 vmail vmail 512B 2014-07-03 17:01:31 EDT .Hornik/ > drwx------ 5 vmail vmail 512B 2014-07-19 14:45:29 EDT .INBOX.Deleted Items/ > drwx------ 5 vmail vmail 512B 2014-07-18 08:58:21 EDT .INBOX.Drafts/ > drwx------ 5 vmail vmail 512B 2014-07-18 08:58:13 EDT .INBOX.Junk E-mail/ > drwx------ 5 vmail vmail 512B 2014-07-19 14:46:56 EDT .INBOX.PSNC/ > drwx------ 5 vmail vmail 512B 2014-07-19 14:46:57 EDT .INBOX.SGWASA/ > drwx------ 5 vmail vmail 512B 2014-07-18 08:58:13 EDT .INBOX.Sent Items/ > drwx------ 5 vmail vmail 512B 2014-07-19 14:46:58 EDT .INBOX.UNRBA/ > drwx------ 5 vmail vmail 512B 2014-07-18 07:40:05 EDT .Locklear/ > drwx------ 5 vmail vmail 512B 2014-07-08 13:39:58 EDT .PlanningBoard/ > drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Queue/ > drwx------ 5 vmail vmail 512B 2014-07-03 17:01:31 EDT .SawyerHomes/ > drwx------ 5 vmail vmail 512B 2014-07-19 08:32:05 EDT .Sent/ > drwx------ 5 vmail vmail 512B 2014-07-19 06:54:07 EDT .Trash/ > drwx------ 5 vmail vmail 512B 2014-07-10 19:19:51 EDT .Vicki/ > drwx------ 5 vmail vmail 512B 2014-07-18 15:31:06 EDT .Westall/ > drwx------ 2 vmail vmail 23K 2014-07-19 14:44:42 EDT cur/ > -rw------- 1 vmail vmail 14B 2014-07-02 20:30:10 EDT dovecot-keywords > -rw------- 1 vmail vmail 10K 2014-07-19 14:45:18 EDT dovecot-uidlist > -rw------- 1 vmail vmail 8B 2014-07-18 08:58:13 EDT dovecot-uidvalidity > -r--r--r-- 1 vmail vmail 0B 2014-07-02 13:52:04 EDT dovecot-uidvalidity.53b446e2 > -rw------- 1 vmail vmail 2.6K 2014-07-08 14:26:45 EDT dovecot.index > -rw------- 1 vmail vmail 78K 2014-07-19 14:44:42 EDT dovecot.index.cache > -rw------- 1 vmail vmail 21K 2014-07-19 14:45:18 EDT dovecot.index.log > -rw------- 1 vmail vmail 1.8K 2014-07-19 14:46:55 EDT dovecot.mailbox.log > drwx------ 2 vmail vmail 512B 2014-07-02 14:15:43 EDT new/ > > In the above example, only the following are displayed: > > .INBOX.Deleted Items/ > .INBOX.Drafts/ > .INBOX.Junk E-mail/ > .INBOX.PSNC/ > .INBOX.SGWASA/ > .INBOX.Sent Items/ > .INBOX.UNRBA/ > > Do I have a configuration problem? > > dovecot -n > > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > # OS: FreeBSD 10.0-RELEASE-p3 amd64 ufs > auth_mechanisms = plain login cram-md5 digest-md5 > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > log_path = /var/log/dovecot > mail_location = maildir:/var/mail/vmail/%d/gerard > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = username_format=%u /usr/local/etc/dovecot/user/passwd > driver = passwd-file > } > passdb { > args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/user/passwd > driver = passwd-file > } > passdb { > driver = pam > } > passdb { > args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/user/passwd > driver = passwd-file > } > plugin { > sieve_global_dir = /usr/local/etc/dovecot/sieve/ > sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve > } > postmaster_address = postmaster at seibercom.net > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > unix_listener auth-userdb { > group = vmail > mode = 0666 > user = vmail > } > } > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > ssl_cert = ssl_key = userdb { > args = username_format=%u /usr/local/etc/dovecot/user/passwd > default_fields = uid=vmail gid=vmail > driver = passwd-file > } > userdb { > driver = passwd > } > userdb { > args = username_format=%u /usr/local/etc/dovecot/user/passwd > driver = passwd-file > } > protocol lda { > mail_plugins = sieve sieve > } Have you tried to refresh the list of available IMAP folders? http://office.microsoft.com/en-us/outlook-help/download-an-imap-folder-list-HP010080418.aspx#BM1 -- Alex JOST From skdovecot at smail.inf.fh-brs.de Mon Jul 21 06:51:16 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 21 Jul 2014 08:51:16 +0200 (CEST) Subject: Mailboxes not showing up in MS Outlook In-Reply-To: <53CBD0A1.3000004@dimejo.at> References: <20140719151110.3d4c07fc@scorpio> <53CBD0A1.3000004@dimejo.at> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 20 Jul 2014, Alex JOST wrote: > Am 19.07.2014 21:11, schrieb Jerry: >> Sat, 19 Jul 2014 15:03:03 -0400 >> >> I am not sure exactly where the problem is here. I am using a sieve script >> that sorts various incoming messages into their own mailbox. MS Outlook >> does >> not show those folders if they are not directly under INBOX. [cut] >> >> In the above example, only the following are displayed: >> >> .INBOX.Deleted Items/ >> .INBOX.Drafts/ >> .INBOX.Junk E-mail/ >> .INBOX.PSNC/ >> .INBOX.SGWASA/ >> .INBOX.Sent Items/ >> .INBOX.UNRBA/ >> >> Do I have a configuration problem? Test IMAP yourself: telnet server 143 1 login user "password" 2 list "" * 3 lsub "" * 4 logout The list command should display all your mailboxes. The lsub command displayes "subscribed" ones. If list returns just the subset, you have an error on the Dovecot server. Then you should see errors in Dovecot's log. > Have you tried to refresh the list of available IMAP folders? > http://office.microsoft.com/en-us/outlook-help/download-an-imap-folder-list-HP010080418.aspx#BM1 Other problems: + You have a fixed IMAP root folder setting in Outlook. + Outlook shows only subscribed folders. See lsub above. The mailboxes returned by lsub should match Outlook. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU8y4ZXz1H7kL/d9rAQIjzwgAgPEjhGzeUJYpbM9jA0zYzIIw06Jv6azD tqxIneK8desarob3dxyr7zR1TzNOw/x4nm7k4VYeW4mjmXZ84X/mdXd++/VcofQN GG7k4fZhrxHgCYY6yiTUEEKvHiLaBxTvGls+81uqS1G5tab3C2Mx81JNP9J7lHgY tQU5eVnJpcjPYk/XStBJc/+0DT4lIs3g5QXkoUHDqZzz7HBJwONGRRXD5VKBxXnD gHMXhTjp/zM9crI70SI8We2tvds1nH4+M2E/VcWZclpbUO/ZZEc79iSvmMJk2sZn 65dDxaqHBUp7/RkWqVajImbGGVYffug8d5aZj4UTiiPUAkyaLpUPtQ== =Vsk6 -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Mon Jul 21 07:00:30 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 21 Jul 2014 09:00:30 +0200 (CEST) Subject: subfolders in public mailboxes In-Reply-To: <53C8D235.70202@arskom.com.tr> References: <53C8D235.70202@arskom.com.tr> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 18 Jul 2014, Burak Arslan wrote: > I added this to the configuration: > > namespace { > type = public > separator = . > prefix = public. > location = maildir:/var/mail/public > subscriptions = no > list = yes > } > > and I can list maildirs inside these folders correctly. however, I can't > see any subfolders. > > The issue seems to be that /var/mail/public dir itself is interpreted as > a maildir directory. > > However, what I'd like to do is to have a bunch of directories inside > /var/mail/public and treat them as separate maildirs. (I'd like to use > this to make a few existing mailboxes public) > > is this possible? Not that I know of. You could use shared mailboxes: http://wiki2.dovecot.org/SharedMailboxes/Shared Another Workaround might be to run a cron job to symlink mailboxes of "public" mailboxes into /var/.../public, e.g.: /var/mail/user1/Maildir/{cur,new,tmp} /var/mail/user1/Maildir/.box1/{cur,new,tmp} - -> ln -s /var/mail/user1/Maildir /var/mail/public/.user1 ln -s /var/mail/user1/Maildir/.box1 /var/mail/public/.user1.box1 Be aware of permission problems, e.g. all user might be able to delete change mails in the public mailboxes. a.s.o. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU8y6jnz1H7kL/d9rAQK06Af/VTVfeXZdEf52JVMmSTLVx3a0Yz3rNtKm m7i9DAx1L2rx6DgYQsFk4k6DubGG1CG2w/kgOQMBLcpbw8BktP8EFrXkP9AVQUET E8qg0intM4k8ToLmbV/gvZberZpVhlBv1Gs1LOXYs76TZQqTWvbyJ+NVd6M2DQ3V gQ6bSDpzepOSUGuH/FydyFNycwEVHRLJ5IiA1jJyPryB6ScyP/SM42RHn3Uf95hv DGvnnXie9L0pIuBhB1iXrBngCbezXX1t1Ekp/b6n2Av/XXkkRERJ9C7yHj+09SQj 5yDDcKITD8cJq7a+gS093OWZpzjdf1kYWfYaGxxWB2LVAUayWtYSeg== =k6KM -----END PGP SIGNATURE----- From lukashaase at gmx.at Tue Jul 22 00:39:57 2014 From: lukashaase at gmx.at (Lukas Haase) Date: Mon, 21 Jul 2014 17:39:57 -0700 Subject: BUG: Authentication client sent unknown handshake command In-Reply-To: References: <1217E34B-6648-4CF3-9226-813DFA42DD89@iki.fi> Message-ID: Hi, Just a very gentle reminder :) I don't see anything I am doing "wrong" in my config ... Thanks Luke On 2014-07-11 17:45, Lukas Haase wrote: > Hi Timo, > > Thank you very much. I really appreciate your response! > > I have indeed a non-default socket config because I also let exim4 > authenticate against it. So I I am not really able to remove the config. > > What makes me wonder is that the problem just appeared recently. I think > I have the config running for 2 years now or so. > > I provide "doveconf -n" in any case, maybe you can spot an issue? > > Thanks, Luke > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-openvz-042stab090.2-amd64 i686 Debian 7.5 > auth_mechanisms = plain login > auth_verbose = yes > log_timestamp = "%Y-%m-%d %H:%M:%S " > mail_location = maildir:~/Maildir > mail_privileged_group = mail > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date ihave imapflags > namespace { > hidden = yes > inbox = no > list = no > location = maildir:~/Maildir-root > prefix = > separator = . > subscriptions = yes > type = private > } > namespace { > inbox = yes > location = maildir:~/Maildir > prefix = INBOX. > separator = . > subscriptions = yes > type = private > } > namespace { > hidden = no > inbox = no > list = yes > location = maildir:/var/mail/public:INDEX=~/Maildir/public > prefix = Public. > separator = . > subscriptions = no > type = public > } > namespace { > hidden = no > inbox = no > list = yes > location = maildir:/var/mail/shared:INDEX=~/Maildir/shared:LAYOUT=fs > prefix = Shared. > separator = . > subscriptions = no > type = public > } > passdb { > args = /etc/dovecot/%Ls.passwd > driver = passwd-file > } > passdb { > args = /etc/dovecot/dovecot-ldap.conf > driver = ldap > } > passdb { > args = failure_show_msg=yes dovecotp > driver = pam > } > plugin { > acl = vfile > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > sieve_extensions = +imapflags > sieve_global_path = /etc/dovecot/default.sieve > } > protocols = sieve imap > service auth { > unix_listener auth-client { > mode = 0666 > } > user = root > } > service imap-login { > inet_listener imap { > port = 0 > } > } > service imap { > executable = /usr/local/sbin/dovecot-imap-fix > } > ssl_ca = ssl_cert = ssl_key = userdb { > driver = prefetch > } > userdb { > args = /etc/dovecot/dovecot-ldap.conf > driver = ldap > } > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > mail_max_userip_connections = 15 > mail_plugins = acl > } > protocol pop3 { > pop3_uidl_format = %08Xu%08Xv > } > protocol lda { > hostname = mail.intra.local > mail_plugins = sieve > postmaster_address = postmaster at intra.local > } > > > > On 2014-07-10 8:23, Timo Sirainen wrote: >> You have misconfigured Dovecot's auth sockets. Providing doveconf -n >> output would help figuring out the problem. Or just delete all the >> auth-related socket settings from config files and it should work. >> >> On 9.7.2014, at 0.03, Lukas Haase wrote: >> >>> May I gently "push" this? The string "BUG: Authentication client >>> sent unknown handshake command" comes from dovecot (presumably it's >>> in the source code) so I think it shouldn't be too mysterious >>> what's happening here. >>> >>> Thank you, Luke >>> >>> On 2014-07-03 19:10, Lukas Haase wrote: >>>> Hi, >>>> >>>> Some time ago my dovecot started to become BUGgy: Evertime I >>>> restart the system, dovecot is started but I cannot login. I see >>>> the following information in the logs: >>>> >>>> Jul 4 04:04:36 mail dovecot: auth: >>>> passwd-file(user,127.11.91.218,): no passwd >>>> file: /etc/dovecot/imap.passwd Jul 4 04:04:36 mail dovecot: >>>> auth: Error: BUG: Authentication client sent unknown handshake >>>> command: >>>> REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa Jul >>>> 4 04:04:36 mail dovecot: imap: Error: Authentication server >>>> didn't send valid SPID as expected: MECH#011PLAIN#011plaintext >>>> Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from >>>> auth server, aborting (client-pid=20438 client-id=1) Jul 4 >>>> 04:04:36 mail dovecot: imap-login: Internal login failure >>>> (pid=20438 id=1) (internal failure, 1 succesful auths): >>>> user=, method=PLAIN, rip=127.11.91.218, lip=73.82.101.172, >>>> mpid=20439, TLS, session= >>>> >>>> It does not help to restart the client. But when I then restart >>>> the server service dovecot restart it works again. >>>> >>>> But this is very dangerous because the server might reboot and I >>>> might not immideately have the chance to restart dovecot >>>> manually. >>>> >>>> What's going on here? >>>> >>>> mail:/# uname -a Linux mail 2.6.32-openvz-042stab090.2-amd64 #1 >>>> SMP Sat Jun 21 00:22:42 MSK 2014 i686 GNU/Linux mail:/# dovecot >>>> --version 2.1.7 >>>> >>>> Thanks, Luke >>>> >> > From mtrainer at westnet.com.au Tue Jul 22 01:57:13 2014 From: mtrainer at westnet.com.au (Murray Trainer) Date: Tue, 22 Jul 2014 09:57:13 +0800 Subject: Dovecot mailstore performance tuning Message-ID: <2b2d5f1633171ece02e0ade6abe3c56aba7927ee@webmail.westnet.com.au> HI All, We have a couple of dovecot director proxies and six backed mailstores each accessing mailboxes stored on five NFSv4 filsystems with about 1TB of mail on each in maildir format.? We have about 800 max users on each mailstore at peak times and performance appears to starting to degrade at these times.? The mailstores are pretty recent hardware with 64GB of RAM and 24 cores.?? The NFS storage is EMC VNX and we are doing about 250 I/O per sec upto max of 500 on each filesystem.?? I need to squeeze more performance out of these servers whether that is in the NFS client, Dovecot or Linux OS/kernel areas.?? We use LDAP for auth and I am doing some tuning in that area.?? The NFS filesystems are mounted with the options below: 10.11.0.238:/mailbox_store_01 on /home1 type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,nordirplus,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.11.0.96,local_lock=none,addr=10.11.0.238) My dovecot config is below.? I am not seeing any obvious issues in the server logs.??? Any suggestions on how to improve performance would be appreciated. Thanks Murray # doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=40960 } is lower than required under max. load (41280) doveconf: Warning: service anvil { client_limit=40970 } is lower than required under max. load (41183) # OS: Linux 3.13-0.bpo.1-amd64 x86_64 Debian 7.5 auth_cache_size = 64 M auth_cache_ttl = 2 hours auth_failure_delay = 0 auth_mechanisms = plain login auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!#$-=?^_{}~./@+%" auth_username_translation = +@ auth_worker_max_count = 256 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_gid = 1001 first_valid_uid = 1001 mail_fsync = always mail_location = maildir:~/ managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mmap_disable = yes namespace { ? inbox = yes ? location = ? prefix = INBOX. ? type = private } passdb { ? args = /etc/dovecot/dovecot-ldap.conf.ext ? driver = ldap } plugin { ? acl = vfile ? quota = maildir ? quota_rule = INBOX.Trash:ignore } protocols = " imap lmtp sieve pop3" service anvil { ? client_limit = 40970 } service auth-worker { ? user = dovecot } service auth { ? client_limit = 40960 ? unix_listener auth-userdb { ??? group = mail ??? mode = 0666 ??? user = dovecot ? } } service imap-login { ? chroot = login ? inet_listener imap { ??? address = *, [::] ??? port = 143 ? } ? inet_listener imaps { ??? address = * ??? port = 993 ??? ssl = yes ? } ? process_limit = 20480 ? process_min_avail = 32 ? service_count = 1 ? user = dovecot ? vsz_limit = 256 M } service imap { ? process_limit = 40960 ? vsz_limit = 256 M } service lmtp { ? inet_listener lmtp { ??? address = 27.54.95.41 ??? port = 24 ? } ? process_min_avail = 32 } service managesieve-login { ? client_limit = 40960 ? process_limit = 120 ? process_min_avail = 5 ? service_count = 0 ? vsz_limit = 64 M } service managesieve { ? process_limit = 4096 ? vsz_limit = 256 M } service pop3-login { ? chroot = login ? inet_listener pop3 { ??? address = *, [::] ??? port = 110 ? } ? inet_listener pop3s { ??? address = * ??? port = 995 ??? ssl = yes ? } ? process_limit = 20480 ? process_min_avail = 32 ? service_count = 1 ? user = dovecot ? vsz_limit = 256 M } service pop3 { ? process_limit = 40960 ? vsz_limit = 256 M } ssl_cert = From skdovecot at smail.inf.fh-brs.de Tue Jul 22 07:01:52 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 22 Jul 2014 09:01:52 +0200 (CEST) Subject: BUG: Authentication client sent unknown handshake command In-Reply-To: References: <1217E34B-6648-4CF3-9226-813DFA42DD89@iki.fi> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 21 Jul 2014, Lukas Haase wrote: >> I provide "doveconf -n" in any case, maybe you can spot an issue? I don't think, it's your config. Setup a new server from scratch, without touching anything else on the new system [no init.d scripts either], but copy Dovecot to it. And try that system. >>>>> Some time ago my dovecot started to become BUGgy: Evertime I >>>>> restart the system, dovecot is started but I cannot login. I see >>>>> the following information in the logs: >>>>> >>>>> Jul 4 04:04:36 mail dovecot: auth: >>>>> passwd-file(user,127.11.91.218,): no passwd >>>>> file: /etc/dovecot/imap.passwd Jul 4 04:04:36 mail dovecot: >>>>> auth: Error: BUG: Authentication client sent unknown handshake >>>>> command: >>>>> REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa Jul >>>>> 4 04:04:36 mail dovecot: imap: Error: Authentication server >>>>> didn't send valid SPID as expected: MECH#011PLAIN#011plaintext >>>>> Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from >>>>> auth server, aborting (client-pid=20438 client-id=1) Jul 4 >>>>> 04:04:36 mail dovecot: imap-login: Internal login failure >>>>> (pid=20438 id=1) (internal failure, 1 succesful auths): >>>>> user=, method=PLAIN, rip=127.11.91.218, lip=73.82.101.172, >>>>> mpid=20439, TLS, session= >>>>> >>>>> It does not help to restart the client. But when I then restart >>>>> the server service dovecot restart it works again. You say, _each_ time you restart the system, this happens, but _never_ if you start Dovecot manually? I would first look into: 0) Dovecot v2.1 is pretty old. ;-) a) Do you have more than one Dovecot version installed. b) When and how often which Dovecot installation is started. - -> e.g. is Dovecot started two times? I had some problem, when I started Postgres two times in init.d, it worked most of the time, but sometimes not. c) Is Dovecot started too early? - -> Maybe one dependency (LDAP, PAM, ...) blocks Dovecot, when someone is logging in too early and Dovecot gets desync'ed. d) Your init.d script throws an error, which you don't see on startup and which does not happen, if you call the script manually. - -> yes that can happen. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU84MYHz1H7kL/d9rAQJEswf/a9OHp7JB9Pghj4Zr+Bws1Hxy1Q/+TaXF RCL5ttvKLzcTQ5WCgso35AFtu7knERdcSn+BOaknVDHT2IFwZqdmGi0EpxG5F40n MIIv97SWCu8jj8/wNxHlVhPbEnFvJTK4f4+mFivhSSYZ9ZVJMy/4rDh9ZunsJ7UG Ri3SSvWAOOAlZLgYafmUX9UMhAfQJihqCRkMGLAc2eAvOuE7iludSJpIT8QWW/nI ea9+K9NJ+iK6cxHKN23LZ/7bIDhSu6JbG5xjgp0+YdYECsGSGHgDz2noQkgR66Bo 4z+qn/DdITYdx7+mc6kLbnA3dcTEM1Le41eu72lMwo9wioq9I5vu0g== =WyKT -----END PGP SIGNATURE----- From toni at solu.fi Tue Jul 22 07:20:04 2014 From: toni at solu.fi (Toni Mattila) Date: Tue, 22 Jul 2014 10:20:04 +0300 Subject: Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d In-Reply-To: <53BA85F7.5040107@solu.fi> References: <53B911C3.2020004@solu.fi> <53BA6CA6.3050705@solu.fi> <8C6061E2-BCA6-4875-89ED-3A4526E9ACBB@iki.fi> <53BA85F7.5040107@solu.fi> Message-ID: <53CE10A4.9040901@solu.fi> Hi, Any further ideas on this one or suggestions how to provide more info? Thanks, Toni On 7.7.2014 14:35, Toni Mattila wrote: > Hi, > > On 7.7.2014 13:16, Timo Sirainen wrote: >> Should be fixed by http://hg.dovecot.org/dovecot-2.2/rev/1a38a85d952e > > Nope. Still happens: > (gdb) bt > #0 0x00568402 in __kernel_vsyscall () > #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 > #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 > #3 0x00d13c14 in default_fatal_finish (type=, > status=0) at failures.c:193 > #4 0x00d13c9d in i_internal_fatal_handler (ctx=0xbf824104, > format=0xd40784 "file %s: line %d (%s): assertion failed: (%s)", > args=0xbf824124 "\f??") at failures.c:657 > #5 0x00d13514 in i_panic (format=0xd40784 "file %s: line %d (%s): > assertion failed: (%s)") at failures.c:267 > #6 0x00d1d99b in i_stream_read (stream=0x85c7d20) at istream.c:170 > #7 0x00d1dbfb in i_stream_read_data (stream=0x85c7d20, > data_r=0xbf824264, size_r=0xbf824268, threshold=31) at istream.c:538 > #8 0x00d03b5e in message_parser_read_more (ctx=0x85dc020, > block_r=0xbf82425c, full_r=0xbf8241db) at message-parser.c:128 > #9 0x00d05469 in parse_next_body_to_boundary (ctx=0x85dc020, > block_r=0xbf82425c) at message-parser.c:361 > #10 0x00d03cd3 in message_parser_parse_next_block (ctx=0x85dc020, > block_r=0xbf82425c) at message-parser.c:1015 > #11 0x00d03e4c in message_parser_parse_body (ctx=0x85dc020, > hdr_callback=0, context=0x0) at message-parser.c:1079 > #12 0x0026fdd2 in index_mail_parse_body (mail=0x85da810, > field=MAIL_CACHE_FLAGS) at index-mail.c:914 > #13 0x00270c7a in index_mail_get_parts (_mail=0x85da810, > parts_r=0xbf824358) at index-mail.c:285 > #14 0x00245d76 in mail_get_parts (mail=0x85da810, parts_r=0xbf824358) at > mail.c:114 > #15 0x00275a7c in search_match_once (ctx=0x85cbc28) at index-search.c:745 > #16 0x00276a89 in search_more (ctx=0x85cbc28, mail_r=0xbf824458) at > index-search.c:1401 > #17 0x002775fe in index_storage_search_next_nonblock (_ctx=0x85cbc28, > mail_r=0xbf8244c4, tryagain_r=0xbf8244cb) at index-search.c:1677 > #18 0x0024d2ee in mailbox_search_next_nonblock (ctx=0x85cbc28, > mail_r=0xbf8244c4, tryagain_r=0xbf8244cb) at mail-storage.c:1796 > #19 0x08062b40 in cmd_search_more (cmd=0x85ac430) at imap-search.c:443 > #20 0x08063079 in imap_search_start (ctx=0x85ac4e8, sargs=0x85d9000, > sort_program=0x0) at imap-search.c:610 > #21 0x08056d86 in cmd_search (cmd=0x85ac430) at cmd-search.c:48 > #22 0x0805c953 in command_exec (cmd=0x85ac430) at imap-commands.c:158 > #23 0x0805b69f in client_command_input (cmd=0x85ac430) at imap-client.c:778 > #24 0x0805b751 in client_command_input (cmd=0x85ac430) at imap-client.c:839 > #25 0x0805b913 in client_handle_input (client=0x85ab9c8) at > imap-client.c:877 > #26 0x0805bd71 in client_input (client=0x85ab9c8) at imap-client.c:931 > #27 0x00d25d88 in io_loop_call_io (io=0x85ac3b0) at ioloop.c:441 > #28 0x00d2775f in io_loop_handler_run_internal (ioloop=0x8596490) at > ioloop-epoll.c:220 > #29 0x00d25e2e in io_loop_handler_run (ioloop=0x8596490) at ioloop.c:488 > #30 0x00d25eb8 in io_loop_run (ioloop=0x8596490) at ioloop.c:465 > #31 0x00ccc42d in master_service_run (service=0x85963b8, > callback=0x8066000 ) at master-service.c:566 > #32 0x08065e9f in main (argc=Cannot access memory at address 0x0 > ) at main.c:400 > > (gdb) f 6 > #6 0x00d1d99b in i_stream_read (stream=0x85c7d20) at istream.c:170 > 170 i_assert(_stream->skip != _stream->pos); > (gdb) p *_stream > $1 = {m = {refcount = 2, name = 0x0, error = 0x85cc0a8 "Cached message > size smaller than expected (3082265 < 3082342)", close = 0xd1e1e0 > , destroy = 0xd1e400 , > set_max_buffer_size = 0xd1e140 > , destroy_callbacks = {arr = > {buffer = 0x85cc070, element_size = 8}, v = 0x85cc070, v_modifiable = > 0x85cc070}}, read = 0x26bf10 , > seek = 0xd1cee0 , sync = 0, stat = > 0xd1d140 , get_size = 0xd1cf10 > , switch_ioloop = 0, istream = {v_offset = 0, > stream_errno = 22, mmaped = 0, > blocking = 1, closed = 0, readable_fd = 0, seekable = 1, eof = 0, > real_stream = 0x85c7ce8}, fd = 16, abs_start_offset = 0, statbuf = > {st_dev = 2050, __pad1 = 0, __st_ino = 45313747, st_mode = 33152, > st_nlink = 1, st_uid = 89, > st_gid = 89, st_rdev = 0, __pad2 = 0, st_size = 3082342, st_blksize > = 4096, st_blocks = 6032, st_atim = {tv_sec = 1334256398, tv_nsec = 0}, > st_mtim = {tv_sec = 1303455370, tv_nsec = 0}, st_ctim = {tv_sec = > 1334256398, tv_nsec = 0}, > st_ino = 45313747}, io = 0x0, > buffer = 0x863cb30 > "\nALUNAAC2DQAAtw0AALgNAAC5DQAAug0AALsNAAC8DQAAvQ0AAL4NAAC/DQAAwA0AAMENAADCDQAA\nww0AAMQNAADFDQAAxg0AAMcNAADIDQAAyQ0AAMoNAADLDQAAzA0AAM0NAADODQAAzw0AANANAADR\nDQAA0g0AANMNAADUDQAA1Q0AANYNAADXDQAA2A0AANkNA"..., > > w_buffer = 0x0, buffer_size = 0, max_buffer_size = 8192, > init_buffer_size = 8192, skip = 0, pos = 0, try_alloc_limit = 0, parent > = 0x8600988, parent_start_offset = 0, parent_expected_offset = 3077052, > access_counter = 1136, > line_str = 0x0, line_crlf = 0, return_nolf_line = 0, > stream_size_passthrough = 1} > > (gdb) p *_stream.parent.real_stream > $2 = {m = {refcount = 1, name = 0x85c7c70 > "/cencored/Maildir/cur/1303455370.23018.cencored.fi,S=3082265:2,RS", > error = 0x0, close = 0xd217d0 , > destroy = 0xd1e400 , set_max_buffer_size > = 0xd1e140 , destroy_callbacks = > {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, > read = 0xd213f0 , seek = 0xd212c0 > , sync = 0xd21000 , stat = > 0xd21200 , get_size = 0xd1cf10 > , switch_ioloop = 0, istream = { > v_offset = 3077052, stream_errno = 0, mmaped = 0, blocking = 1, > closed = 0, readable_fd = 1, seekable = 1, eof = 0, real_stream = > 0x8600950}, fd = 16, abs_start_offset = 0, statbuf = {st_dev = 2050, > __pad1 = 0, __st_ino = 45313747, > st_mode = 33152, st_nlink = 1, st_uid = 89, st_gid = 89, st_rdev = > 0, __pad2 = 0, st_size = 3082342, st_blksize = 4096, st_blocks = 6032, > st_atim = {tv_sec = 1334256398, tv_nsec = 0}, st_mtim = {tv_sec = > 1303455370, tv_nsec = 0}, > st_ctim = {tv_sec = 1334256398, tv_nsec = 0}, st_ino = 45313747}, > io = 0x0, > buffer = 0x863cb30 > "\nALUNAAC2DQAAtw0AALgNAAC5DQAAug0AALsNAAC8DQAAvQ0AAL4NAAC/DQAAwA0AAMENAADCDQAA\nww0AAMQNAADFDQAAxg0AAMcNAADIDQAAyQ0AAMoNAADLDQAAzA0AAM0NAADODQAAzw0AANANAADR\nDQAA0g0AANMNAADUDQAA1Q0AANYNAADXDQAA2A0AANkNA"..., > > w_buffer = 0x863cb30 > "\nALUNAAC2DQAAtw0AALgNAAC5DQAAug0AALsNAAC8DQAAvQ0AAL4NAAC/DQAAwA0AAMENAADCDQAA\nww0AAMQNAADFDQAAxg0AAMcNAADIDQAAyQ0AAMoNAADLDQAAzA0AAM0NAADODQAAzw0AANANAADR\nDQAA0g0AANMNAADUDQAA1Q0AANYNAADXDQAA2A0AANkNA"..., > > buffer_size = 8192, max_buffer_size = 8192, init_buffer_size = 8192, > skip = 0, pos = 5290, try_alloc_limit = 0, parent = 0x0, > parent_start_offset = 0, parent_expected_offset = 0, access_counter = > 1136, line_str = 0x0, line_crlf = 0, > return_nolf_line = 0, stream_size_passthrough = 0} From crohmann at netcologne.de Tue Jul 22 15:11:05 2014 From: crohmann at netcologne.de (Christian Rohmann) Date: Tue, 22 Jul 2014 17:11:05 +0200 Subject: Defer email via LMTP when there is 'no space left on device' instead of rejecting it Message-ID: <53CE7F09.9070100@netcologne.de> Hello dovecot-users, (This problem was being discussed a little in this thread from 2011: http://www.dovecot.org/list/dovecot/2011-May/059009.html) I noticed (using LMTP) that Dovecot handles 'no space left on device' just like an 'over-quota', if I read this part of method "static int client_deliver(struct client *client, const struct mail_recipient *rcpt, struct mail *src_mail, struct mail_deliver_session *session)" "lmtp/commands.c" correctly: --- cut --- [...] else if (storage != NULL) { error = mail_storage_get_last_error(storage, &mail_error); if (mail_error == MAIL_ERROR_NOSPACE) { client_send_line(client, "%s <%s> %s", dctx.set->quota_full_tempfail ? "452 4.2.2" : "552 5.2.2", rcpt->address, error); } else { client_send_line(client, "451 4.2.0 <%s> %s", rcpt->address, error); } ret = -1; [...] --- /cut --- In consequence this means the configuration option quota_full_tempfail is applied in both cases. But to me there is a major difference between a full disk (a.k.a "admin fucked up") and over-quota (a.k.a. "user has simply too much stuff in his mailbox"). So I would like to be able tell Dovecot to reject messages due to full mailboxes, but simply defer those that cannot be stored due to a full disk (which I am to blame for). To me this should result in two separate configuration options for the two problem root-causes: quota_full_tempfail storage_full_tempfail Or did I simply miss or completely misunderstood anything here? Regards Christian From h.reindl at thelounge.net Tue Jul 22 15:31:14 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 22 Jul 2014 17:31:14 +0200 Subject: Defer email via LMTP when there is 'no space left on device' instead of rejecting it In-Reply-To: <53CE7F09.9070100@netcologne.de> References: <53CE7F09.9070100@netcologne.de> Message-ID: <53CE83C2.80708@thelounge.net> Am 22.07.2014 17:11, schrieb Christian Rohmann: > In consequence this means the configuration option quota_full_tempfail > is applied in both cases. But to me there is a major difference between > a full disk (a.k.a "admin fucked up") and over-quota (a.k.a. "user has > simply too much stuff in his mailbox"). So I would like to be able tell > Dovecot to reject messages due to full mailboxes, but simply defer those > that cannot be stored due to a full disk (which I am to blame for). > > To me this should result in two separate configuration options for the > two problem root-causes: > > quota_full_tempfail > storage_full_tempfail > > Or did I simply miss or completely misunderstood anything here? no - in case of quota full i can take a phone and call the RCPT, he can make free space due the phone call and say "try it again please" in case of disk full *this is* a permanent error likely not correctable by the user given that after delete a message a different one get a new and the disk is full again that sort of mistakes happens one per decade and hardly need special handling - if that happens your user quotas are wrongly configured because the idea behind them is to prevent "disk full" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From hanno at hboeck.de Tue Jul 22 15:54:55 2014 From: hanno at hboeck.de (Hanno =?UTF-8?B?QsO2Y2s=?=) Date: Tue, 22 Jul 2014 17:54:55 +0200 Subject: [patch] enable ECDH auto functions based on feature defines, not on version number Message-ID: <20140722175455.201ad8d0@pc> Hello, I recently tried to build my system with libressl instead of openssl. In dovecot one issue that popped up was that libressl doesn't have the ECDH auto functions from openssl 1.0.2 beta versions. However as the #ifdef's in dovecot's code check for the openssl version and libressl's version numbers are higher the compilation fails there. Attached is a patch that will change that checks. Instead of checking for the version number it checks for the availability of the feature itself (by checking for the define of SSL_CTRL_SET_ECDH_AUTO). This should make this check more robust and work independently of the version number of the used openssl instance. cu, -- Hanno B?ck http://hboeck.de/ mail/jabber: hanno at hboeck.de GPG: BBB51E42 -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-ecdh-auto.diff Type: text/x-patch Size: 3068 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From rick at havokmon.com Tue Jul 22 15:54:57 2014 From: rick at havokmon.com (Rick Romero) Date: Tue, 22 Jul 2014 10:54:57 -0500 Subject: Defer email via LMTP when there is 'no space left on device' instead of rejecting it In-Reply-To: <53CE83C2.80708@thelounge.net> References: <53CE7F09.9070100@netcologne.de> <53CE83C2.80708@thelounge.net> Message-ID: <20140722105457.Horde.7d0V3fVgX31KXmR-Si8DUQ7@www.vfemail.net> Quoting Reindl Harald : > Am 22.07.2014 17:11, schrieb Christian Rohmann: >> In consequence this means the configuration option quota_full_tempfail >> is applied in both cases. But to me there is a major difference between >> a full disk (a.k.a "admin fucked up") and over-quota (a.k.a. "user has >> simply too much stuff in his mailbox"). So I would like to be able tell >> Dovecot to reject messages due to full mailboxes, but simply defer those >> that cannot be stored due to a full disk (which I am to blame for). >> >> To me this should result in two separate configuration options for the >> two problem root-causes: >> >> quota_full_tempfail >> storage_full_tempfail >> >> Or did I simply miss or completely misunderstood anything here? > > no - in case of quota full i can take a phone and call the > RCPT, he can make free space due the phone call and say > "try it again please" > > in case of disk full *this is* a permanent error likely not > correctable by the user given that after delete a message a > different one get a new and the disk is full again > > that sort of mistakes happens one per decade and hardly > need special handling - if that happens your user quotas > are wrongly configured because the idea behind them isto prevent "disk > full" Being that there are a million different ways to create a storage entity and deliver to it, both of which is far outside the control of the user, I don't think it's a bad idea to allow a delivery deferral for storage issues.?? For example, at that point in the code, /could/ an NFS/CIFS/local/remote mount issue be reported as 'disk full', because the device is not attached?? If the answer is 'yes', then there should be an additional option. In my experience, users would rather have their mail delayed due to a storage issue than outright rejected - especially when many rejections would go to unattended mailboxes and can't be easily resent.? Like my Pizza Hut coupons.? Don't go messing with my Pizza Hut coupons. Rick From ml+dovecot at moritz.augsburger.name Tue Jul 22 17:00:26 2014 From: ml+dovecot at moritz.augsburger.name (Moritz Augsburger) Date: Tue, 22 Jul 2014 19:00:26 +0200 Subject: Defer email via LMTP when there is 'no space left on device' instead of rejecting it In-Reply-To: <53CE83C2.80708@thelounge.net> References: <53CE7F09.9070100@netcologne.de> <53CE83C2.80708@thelounge.net> Message-ID: <53CE98AA.9060508@moritz.augsburger.name> On 2014-07-22 17:31, Reindl Harald wrote: > in case of disk full *this is* a permanent error likely not > correctable by the user given that after delete a message a > different one get a new and the disk is full again The message could be already saved to disk by the MTA, so I don't see a reason for a hard reject, if it could be fixed within some hours by the admin (eg by expanding the volume, moving mailboxes between multiple storage systems etc). Mails aren't instant, and as long as the MTA handles it properly with a reject after some failed delivery attempts I see no problem making it at least configurable. > that sort of mistakes happens one per decade and hardly > need special handling - if that happens your user quotas > are wrongly configured because the idea behind them is > to prevent "disk full" In fact that's not the case in nearly all big mail systems. Available storage is mostly average mailbox size x user count x safety margin. Yes, it's an admin failure when no space is left, but why bother the user or people trying to send mail to your users as long as the admin can take countermeasures within adequate time? Moritz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From h.reindl at thelounge.net Tue Jul 22 17:10:51 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 22 Jul 2014 19:10:51 +0200 Subject: Defer email via LMTP when there is 'no space left on device' instead of rejecting it In-Reply-To: <53CE98AA.9060508@moritz.augsburger.name> References: <53CE7F09.9070100@netcologne.de> <53CE83C2.80708@thelounge.net> <53CE98AA.9060508@moritz.augsburger.name> Message-ID: <53CE9B1B.2010304@thelounge.net> Am 22.07.2014 19:00, schrieb Moritz Augsburger: > On 2014-07-22 17:31, Reindl Harald wrote: >> in case of disk full *this is* a permanent error likely not >> correctable by the user given that after delete a message a >> different one get a new and the disk is full again > > The message could be already saved to disk by the MTA, so I don't see a > reason for a hard reject, if it could be fixed within some hours by the > admin (eg by expanding the volume, moving mailboxes between multiple > storage systems etc). the same applies for single mailbox full so why handle the cases different? > Mails aren't instant, and as long as the MTA handles it properly with a > reject after some failed delivery attempts I see no problem making it at > least configurable. it makes things more complicated if you have different behavior for 'mailbox full' and 'disk full' >> that sort of mistakes happens one per decade and hardly >> need special handling - if that happens your user quotas >> are wrongly configured because the idea behind them is >> to prevent "disk full" > > In fact that's not the case in nearly all big mail systems. Available > storage is mostly average mailbox size x user count x safety margin. which hardly leads to 'disk full' from one day to another except the calculation assumes sunshine serveral contextes and allows a few accounts to fill your whole storage normally you have watchdogs which are crying out loud if a storage goes below 25% free, daily logwatch shows you the % of free space http://en.wikipedia.org/wiki/File_system_fragmentation#Preventing_fragmentation As time goes on, and the same factors are continuously present, free space as well as frequently appended files tend to fragment more. Shorter regions of free space also mean that the allocator is no longer able to allocate new files contiguously, and has to break them into fragments. This is especially true when the file system is more full ? longer contiguous regions of free space are less likely to occu > Yes, it's an admin failure when no space is left, but why bother the > user or people trying to send mail to your users as long as the admin > can take countermeasures within adequate time? because it happens only a few times per decade and admin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From lists at boyandin.name Wed Jul 23 04:16:53 2014 From: lists at boyandin.name (Boyandin Konstantin) Date: Wed, 23 Jul 2014 11:16:53 +0700 Subject: SSL certificate problem (SSL alert number 42) Message-ID: <2792921406089013@web26j.yandex.ru> Hello, After client (Thunderbird, now version 31.0) updated today, it stopped connecting to Dovecot IMAP4S. The infamous "SSL alert number 42" is reported. Mail server uses local (created for intranet) CA certificate as root. I would appreciate pieces of advice on how to handle that without enabling plaintext authentication over insecure channels. Other intranet services work with this local CA quite fine. Thank you in advance. Required data: # dovecot --version 2.0.9 # doveconf -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.5.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) auth_username_format = %n default_process_limit = 1200 disable_plaintext_auth = yes first_valid_uid = 300 mail_location = mbox:~/mail:INBOX=/var/mail/%n mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } protocols = imap pop3 service anvil { client_limit = 6000 } service auth { client_limit = 6000 } ssl_ca = Hi all, I'm still (mostly) on vacation this week and afterwards lots of different things to do .. But hopefully I'll still get around to answering all the pending mails in this list and applying some of the patches people have sent and get the next v2.2.14 release out. Anyway, people have kept asking about GMail API and Inbox App and how that affects Dovecot. For a while now I've been planning on implementing some kind of a HTTP API for mail access, so might as well use GMail's: http://www.dovecot.fi/dovecot-launches-a-gmail-api-compatible-rest-api-to-enable-third-party-developers-to-join-its-global-email-ecosystem/ From crohmann at netcologne.de Wed Jul 23 09:26:29 2014 From: crohmann at netcologne.de (Christian Rohmann) Date: Wed, 23 Jul 2014 11:26:29 +0200 Subject: Defer email via LMTP when there is 'no space left on device' instead of rejecting it In-Reply-To: <53CE98AA.9060508@moritz.augsburger.name> References: <53CE7F09.9070100@netcologne.de> <53CE83C2.80708@thelounge.net> <53CE98AA.9060508@moritz.augsburger.name> Message-ID: <53CF7FC5.2040301@netcologne.de> On 22.07.2014 19:00, Moritz Augsburger wrote: > The message could be already saved to disk by the MTA, so I don't see a > reason for a hard reject, if it could be fixed within some hours by the > admin (eg by expanding the volume, moving mailboxes between multiple > storage systems etc). > > Mails aren't instant, and as long as the MTA handles it properly with a > reject after some failed delivery attempts I see no problem making it at > least configurable. My point exactly. The message was accepted from the MTA already, but simply could not be delivered into the mailbox. This is a rare case yes, and yes, disk space has to be monitored. But this is not the point. The point is, what happens when it happens anyways, against all odds. Bounced / rejected messages for something that will be usually be resolved very quickly and the messages can then be delivered after all is just not very nice for users. The admin made a mistake and the users have to deal with the problems is just not my approach. But in the end I don't even want to argue that rejecting the messages might not be a valid behavior for some. That's why I suggested to make this configurable, just like the quota behavior. Regards Christian From s.potapov at rambler-co.ru Wed Jul 23 09:54:12 2014 From: s.potapov at rambler-co.ru (Potapov Sergey) Date: Wed, 23 Jul 2014 09:54:12 +0000 Subject: Maybe error in login-common/login-proxy.c/proxy_client_input Message-ID: <409CEB1649811749B2E36961BEE2DDBC45F2D306@srv-mbx4.rambler.ramblermedia.com> Hi! It seems that o_stream_cork should be done on proxy->server_output but not on proxy->client_output. o_stream_cork(proxy->client_output); ret2 = o_stream_send(proxy->server_output, buf, ret); o_stream_uncork(proxy->server_output); From weber at dimensional.de Wed Jul 23 07:02:29 2014 From: weber at dimensional.de (Alexander Weber) Date: Wed, 23 Jul 2014 09:02:29 +0200 Subject: SSL certificate problem (SSL alert number 42) In-Reply-To: <2792921406089013@web26j.yandex.ru> References: <2792921406089013@web26j.yandex.ru> Message-ID: <53CF5E05.4000208@dimensional.de> hey there, got the same issue a few days ago, reported a bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1036338 it is a error in Thunderbird 31,32,33 On 23.07.2014 06:16, Boyandin Konstantin wrote: > Hello, > > After client (Thunderbird, now version 31.0) updated today, it stopped connecting to Dovecot IMAP4S. The infamous "SSL alert number 42" is reported. > > Mail server uses local (created for intranet) CA certificate as root. > > I would appreciate pieces of advice on how to handle that without enabling plaintext authentication over insecure channels. > > Other intranet services work with this local CA quite fine. > > Thank you in advance. Required data: > > # dovecot --version > 2.0.9 > > # doveconf -n > > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-431.5.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) > auth_username_format = %n > default_process_limit = 1200 > disable_plaintext_auth = yes > first_valid_uid = 300 > mail_location = mbox:~/mail:INBOX=/var/mail/%n > mail_privileged_group = mail > mbox_write_locks = fcntl > passdb { > driver = pam > } > protocols = imap pop3 > service anvil { > client_limit = 6000 > } > service auth { > client_limit = 6000 > } > ssl_ca = ssl_cert = ssl_cipher_list = ALL:!LOW > ssl_key = userdb { > driver = passwd > } > verbose_ssl = yes > > > Records posted to Dovecot log file: > > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client hello A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server hello A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write certificate A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server done A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read finished A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write finished A [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x20, ret=1: SSL negotiation finished successfully [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL alert: where=0x4004, ret=554: fatal bad certificate [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Warning: SSL alert: where=0x4008, ret=256: warning close notify [10.x.x.x] > Jul 23 11:01:26 mailserver dovecot: imap-login: Disconnected (no auth attempts): rip=10.x.x.x, lip=10.y.y.y, TLS: SSL_read() failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate: SSL alert number 42 > > > Sincerely, > Konstantin > From blackvoid+dovecot at fantas.in Wed Jul 23 15:49:43 2014 From: blackvoid+dovecot at fantas.in (BlackVoid) Date: Wed, 23 Jul 2014 17:49:43 +0200 Subject: Multiple passwords with sql authentication Message-ID: <53CFD997.9030708@fantas.in> I'm currently working on a control panel which is using postfix, dovecot and other applications and I want to add application specific passwords to increase security. I found one solution [1], however it requires the password to be included in the query which is something I do not want to do, because the query may be written in clear-text to log-files. So I'm wondering if there is a way to have multiple passwords with dovecot without risking passwords being leakied in clear-text to log-files. [1] http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server From rick at havokmon.com Wed Jul 23 16:07:17 2014 From: rick at havokmon.com (Rick Romero) Date: Wed, 23 Jul 2014 11:07:17 -0500 Subject: Multiple passwords with sql authentication In-Reply-To: <53CFD997.9030708@fantas.in> Message-ID: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> Quoting BlackVoid : > I'm currently working on a control panel which is using postfix, dovecot > and other applications and I want to add application specific passwords > to increase security. > > I found one solution [1], however it requires the password to be > included in the query which is something I do not want to do, because > the query may be written in clear-text to log-files. So I'm wondering if > there is a way to have multiple passwords with dovecot without risking > passwords being leakied in clear-text to log-files. > > [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server You can run your query by host (or port - not sure if that variable is available in the query) and make it complex.. For example - (MySQL) SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password from user where userid = %u http://komlenic.com/254/mysql-nested-if-in-select-queries/ If you're using Dovecot as an auth backend for your control panel, I'd use a custom port only accessible from the web server(s) like 145 for IMAP+Control Panel. Rick From blackvoid+dovecot at fantas.in Wed Jul 23 16:29:23 2014 From: blackvoid+dovecot at fantas.in (BlackVoid) Date: Wed, 23 Jul 2014 18:29:23 +0200 Subject: Multiple passwords with sql authentication In-Reply-To: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> Message-ID: <53CFE2E3.2030105@fantas.in> The control panel uses the database to authenticate, however I want users to be able to use applications specific passwords when authentication via SMTP, IMAP and POP3. The issue with the solution I found is as I said that the password will be logged in clear-text in the query log. Perhaps I was no clear enough with what I'm trying to achieve. On Google you can have application-specific passwords. This means you can sign in either with your primary password or an application-specific password and this is what I'm trying to do. I could solve it using the solution in my first mail, but that is a security risk, because if someone gains access to my server for whatever reason, all the person has to do is check the mysql query log to see everyone's password in clear-text. If I did not explain it good enough, perhaps this will help. https://support.google.com/mail/answer/1173270?hl=en So I'm looking for a solution where the dovecot fetches all encrypted passwords for the user who is trying to sign in and checks if any of the returned hashes matched with the entered password and the risk is non-existent that the password is logged in clear-text. On 2014-07-23 18:07, Rick Romero wrote: > Quoting BlackVoid : > >> I'm currently working on a control panel which is using postfix, dovecot >> and other applications and I want to add application specific passwords >> to increase security. >> >> I found one solution [1], however it requires the password to be >> included in the query which is something I do not want to do, because >> the query may be written in clear-text to log-files. So I'm wondering if >> there is a way to have multiple passwords with dovecot without risking >> passwords being leakied in clear-text to log-files. >> >> > [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server > > > You can run your query by host (or port - not sure if that variable is > available in the query) and make it complex.. > > For example - (MySQL) > SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password from > user where userid = %u > > http://komlenic.com/254/mysql-nested-if-in-select-queries/ > > If you're using Dovecot as an auth backend for your control panel, I'd use > a custom port only accessible from the web server(s) like 145 for > IMAP+Control Panel. > > Rick From rick at havokmon.com Wed Jul 23 16:33:23 2014 From: rick at havokmon.com (Rick Romero) Date: Wed, 23 Jul 2014 11:33:23 -0500 Subject: Multiple passwords with sql authentication In-Reply-To: <53CFE2E3.2030105@fantas.in> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> Message-ID: <20140723113323.Horde.DCnBlNp9iMu4euYKpWaPWg1@www.vfemail.net> Quoting BlackVoid : > On 2014-07-23 18:07, Rick Romero wrote: >> Quoting BlackVoid : >> >>> I'm currently working on a control panel which is using postfix, dovecot >>> and other applications and I want to add application specific passwords >>> to increase security. >>> >>> I found one solution [1], however it requires the password to be >>> included in the query which is something I do not want to do, because >>> the query may be written in clear-text to log-files. So I'm wondering if >>> there is a way to have multiple passwords with dovecot without risking >>> passwords being leakied in clear-text to log-files. >>> ? >> >> [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server >> >> You can run your query by host (or port - not sure if that variable is >> available in the query) and make it complex.. >> >> For example - (MySQL) >> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >> from >> user where userid = %u >> >> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >> >> If you're using Dovecot as an auth backend for your control panel, I'd >> use >> a custom port only accessible from the web server(s) like 145 for >> IMAP+Control Panel. >> Rick > > The control panel uses the database to authenticate, however I want > users to be able to use applications specific passwords when > authentication via SMTP, IMAP and POP3. The issue with the solution I > found is as I said that the password will be logged in clear-text in the > query log. > > Perhaps I was no clear enough with what I'm trying to achieve. On Google > you can have application-specific passwords. This means you can sign in > either with your primary password or an application-specific password > and this is what I'm trying to do. I could solve it using the solution > in my first mail, but that is a security risk, because if someone gains > access to my server for whatever reason, all the person has to do is > check the mysql query log to see everyone's password in clear-text. If I > did not explain it good enough, perhaps this will help. > https://support.google.com/mail/answer/1173270?hl=en > > So I'm looking for a solution where the dovecot fetches all encrypted > passwords for the user who is trying to sign in and checks if any of the > returned hashes matched with the entered password and the risk is > non-existent that the password is logged in clear-text. > ? From rick at havokmon.com Wed Jul 23 16:40:33 2014 From: rick at havokmon.com (Rick Romero) Date: Wed, 23 Jul 2014 11:40:33 -0500 Subject: Multiple passwords with sql authentication In-Reply-To: <53CFE2E3.2030105@fantas.in> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> Message-ID: <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> Quoting BlackVoid : > On 2014-07-23 18:07, Rick Romero wrote: >> Quoting BlackVoid : >> >>> I'm currently working on a control panel which is using postfix, dovecot >>> and other applications and I want to add application specific passwords >>> to increase security. >>> >>> I found one solution [1], however it requires the password to be >>> included in the query which is something I do not want to do, because >>> the query may be written in clear-text to log-files. So I'm wondering if >>> there is a way to have multiple passwords with dovecot without risking >>> passwords being leakied in clear-text to log-files. >>> ? >> >> [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server >> >> You can run your query by host (or port - not sure if that variable is >> available in the query) and make it complex.. >> >> For example - (MySQL) >> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >> from >> user where userid = %u >> >> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >> >> If you're using Dovecot as an auth backend for your control panel, I'd >> use >> a custom port only accessible from the web server(s) like 145 for >> IMAP+Control Panel. >> Rick > > The control panel uses the database to authenticate, however I want > users to be able to use applications specific passwords when > authentication via SMTP, IMAP and POP3. The issue with the solution I > found is as I said that the password will be logged in clear-text in the > query log. > > Perhaps I was no clear enough with what I'm trying to achieve. On Google > you can have application-specific passwords. This means you can sign in > either with your primary password or an application-specific password > and this is what I'm trying to do. I could solve it using the solution > in my first mail, but that is a security risk, because if someone gains > access to my server for whatever reason, all the person has to do is > check the mysql query log to see everyone's password in clear-text. If I > did not explain it good enough, perhaps this will help. > https://support.google.com/mail/answer/1173270?hl=en > > So I'm looking for a solution where the dovecot fetches all encrypted > passwords for the user who is trying to sign in and checks if any of the > returned hashes matched with the entered password and the risk is > non-existent that the password is logged in clear-text. > ? Close.? The query returns a single hash, not all of them. The hash returned is specific to the app requesting it due to the complex query. Dovecot then compares the returned hash with the one submitted by the user (which will be specific to the app the user is using). Optimally you shouldn't be storing clear text passwords. The query will never contain the password submitted by the user, it will only return a password to compare.? If you are using CRYPT, then Dovecot will hash the submitted password and compare hashes. Rick From blackvoid+dovecot at fantas.in Wed Jul 23 18:55:25 2014 From: blackvoid+dovecot at fantas.in (BlackVoid) Date: Wed, 23 Jul 2014 20:55:25 +0200 Subject: Multiple passwords with sql authentication In-Reply-To: <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> Message-ID: <53D0051D.1040409@fantas.in> On 2014-07-23 18:40, Rick Romero wrote: > Quoting BlackVoid : > >> On 2014-07-23 18:07, Rick Romero wrote: >>> Quoting BlackVoid : >>> >>>> I'm currently working on a control panel which is using postfix, > dovecot >>>> and other applications and I want to add application specific passwords >>>> to increase security. >>>> >>>> I found one solution [1], however it requires the password to be >>>> included in the query which is something I do not want to do, because >>>> the query may be written in clear-text to log-files. So I'm wondering > if >>>> there is a way to have multiple passwords with dovecot without risking >>>> passwords being leakied in clear-text to log-files. >>>> >>> >>> > [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server > >>> >>> You can run your query by host (or port - not sure if that variable is >>> available in the query) and make it complex.. >>> >>> For example - (MySQL) >>> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >>> from >>> user where userid = %u >>> >>> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >>> >>> If you're using Dovecot as an auth backend for your control panel, I'd >>> use >>> a custom port only accessible from the web server(s) like 145 for >>> IMAP+Control Panel. >>> Rick >> >> The control panel uses the database to authenticate, however I want >> users to be able to use applications specific passwords when >> authentication via SMTP, IMAP and POP3. The issue with the solution I >> found is as I said that the password will be logged in clear-text in the >> query log. >> >> Perhaps I was no clear enough with what I'm trying to achieve. On Google >> you can have application-specific passwords. This means you can sign in >> either with your primary password or an application-specific password >> and this is what I'm trying to do. I could solve it using the solution >> in my first mail, but that is a security risk, because if someone gains >> access to my server for whatever reason, all the person has to do is >> check the mysql query log to see everyone's password in clear-text. If I >> did not explain it good enough, perhaps this will help. >> https://support.google.com/mail/answer/1173270?hl=en >> >> So I'm looking for a solution where the dovecot fetches all encrypted >> passwords for the user who is trying to sign in and checks if any of the >> returned hashes matched with the entered password and the risk is >> non-existent that the password is logged in clear-text. >> > > Close. The query returns a single hash, not all of them. The hash > returned is specific to the app requesting it due to the complex query. > Dovecot then compares the returned hash with the one submitted by the user > (which will be specific to the app the user is using). > > Optimally you shouldn't be storing clear text passwords. The query will > never contain the password submitted by the user, it will only return a > password to compare. If you are using CRYPT, then Dovecot will hash the > submitted password and compare hashes. > > Rick Yes, I know that. The passwords are hashed in SHA-512-CRYPT. As I've explained in previous mails, the issue is that only one result can be returned, so either I expose the password in the query, the password is hashed n-times (number of passwords the user has) and it gets logged (security risk) or I have to give up my idea to implement application-specific passwords and keep having only one password. You can't hash the password and use it in the query either, because the password needs to be hashed with the correct salt. So from what I can see there is no good solution to this unless I'm missing something. From rick at havokmon.com Wed Jul 23 19:23:01 2014 From: rick at havokmon.com (Rick Romero) Date: Wed, 23 Jul 2014 14:23:01 -0500 Subject: Multiple passwords with sql authentication In-Reply-To: <53D0051D.1040409@fantas.in> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> <53D0051D.1040409@fantas.in> Message-ID: <20140723142301.Horde.SqlMmtnpCshTTeGosL4DbA5@www.vfemail.net> Quoting BlackVoid : > On 2014-07-23 18:40, Rick Romero wrote: >> Quoting BlackVoid : >> >>> On 2014-07-23 18:07, Rick Romero wrote: >>>> Quoting BlackVoid : >>>> >>>>> I'm currently working on a control panel which is using postfix, >> >> dovecot >>>>> and other applications and I want to add application specific >>>>> passwords >>>>> to increase security. >>>>> >>>>> I found one solution [1], however it requires the password to be >>>>> included in the query which is something I do not want to do, because >>>>> the query may be written in clear-text to log-files. So I'm wondering >> >> if >>>>> there is a way to have multiple passwords with dovecot without risking >>>>> passwords being leakied in clear-text to log-files. >> >> [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server >> >>>> You can run your query by host (or port - not sure if that variable is >>>> available in the query) and make it complex.. >>>> >>>> For example - (MySQL) >>>> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >>>> from >>>> user where userid = %u >>>> >>>> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >>>> >>>> If you're using Dovecot as an auth backend for your control panel, I'd >>>> use >>>> a custom port only accessible from the web server(s) like 145 for >>>> IMAP+Control Panel. >>>> Rick >>> >>> The control panel uses the database to authenticate, however I want >>> users to be able to use applications specific passwords when >>> authentication via SMTP, IMAP and POP3. The issue with the solution I >>> found is as I said that the password will be logged in clear-text in the >>> query log. >>> >>> Perhaps I was no clear enough with what I'm trying to achieve. On Google >>> you can have application-specific passwords. This means you can sign in >>> either with your primary password or an application-specific password >>> and this is what I'm trying to do. I could solve it using the solution >>> in my first mail, but that is a security risk, because if someone gains >>> access to my server for whatever reason, all the person has to do is >>> check the mysql query log to see everyone's password in clear-text. If I >>> did not explain it good enough, perhaps this will help. >>> https://support.google.com/mail/answer/1173270?hl=en >>> >>> So I'm looking for a solution where the dovecot fetches all encrypted >>> passwords for the user who is trying to sign in and checks if any of the >>> returned hashes matched with the entered password and the risk is >>> non-existent that the password is logged in clear-text. >> >> Close.? The query returns a single hash, not all of them. The hash >> returned is specific to the app requesting it due to the complex query. >> Dovecot then compares the returned hash with the one submitted by the >> user >> (which will be specific to the app the user is using). >> >> Optimally you shouldn't be storing clear text passwords. The query will >> never contain the password submitted by the user, it will only return a >> password to compare.? If you are using CRYPT, then Dovecot will hash the >> submitted password and compare hashes. >> >> Rick > > Yes, I know that. The passwords are hashed in SHA-512-CRYPT. As I've > explained in previous mails, the issue is that only one result can be > returned, so either I expose the password in the query, the password is > hashed n-times (number of passwords the user has) and it gets logged > (security risk) or I have to give up my idea to implement > application-specific passwords and keep having only one password. You > can't hash the password and use it in the query either, because the > password needs to be hashed? with the correct salt. So from what I > cansee there is no good solution to this unless I'm missing something. I'm assuming you have a field for each application password.? I don't use a custom salt. So your table is like: CREATE TABLE users ( userid VARCHAR(128) NOT NULL, domain VARCHAR(128) NOT NULL, password_imap VARCHAR(64) NOT NULL, password_pop VARCHAR(64) NOT NULL, password_web VARCHAR(64) NOT NULL, password VARCHAR(64) NOT NULL, home VARCHAR(255) NOT NULL, uid INTEGER NOT NULL, gid INTEGER NOT NULL ); in order to return password_web, when the user is using the webmail system, I would use: SELECT ????????????? if ( '%r' = '127.0.0.1' AND password_web != " ", password_web, ???????????????? if ( '%s' = 'imap' AND password_imap != " ", password_imap, ??????????????????? if (password_pop != "", password_pop, password) ) ) ??? from users where userid = %u So if the remote system is 'localhost', and password_web exists, return password_web. ? If not, then if the remote system is using imap, and password_imap exists return password_imap. ?? If not imap, then return password_pop if password_pop exists, otherwise return password. And so on and so forth...? I plan on doing the same, just haven't gotten to it.? I guess I don't see what the problem would be...? am I oversimplifying it somehow?? This has been in the back of my head for a while, and even starting to put it on paper it looks fine for any purpose, even outside of Dovecot.?? Obviously it'll be a complex query.? Just write it out logically first. If you're allowing only particular applications, you'll have to make sure whatever doesn't have a password falls through to 'password'..?? Or, maybe have your 'app password' creation code just ensure any apps without specific passwords have a copy of the 'password' field...? Or maybe have a boolean field to check if app specific passwords are on and make that the first if() in the query checks that.... Rick From richard at walnut.gen.nz Wed Jul 23 21:37:27 2014 From: richard at walnut.gen.nz (Richard Hector) Date: Thu, 24 Jul 2014 09:37:27 +1200 Subject: Maildir migration - using separate INDEX and CONTROL directories? Message-ID: <53D02B17.9030402@walnut.gen.nz> Hi all, I'm working on a migration from Courier to Dovecot, and the courier-dovecot-migrate.pl seems to work ok, but it puts all the metadata files (dovecot-uidlist etc) in the Maildir, while I want to put them in the appropriate places as specified: mail_location = maildir:~/Maildir:INDEX=/var/mail/meta/index/%d/%1n/%1.1n/%n:CONTROL=/var/mail/meta/control/%d/%1n/%1.1n/%n http://wiki2.dovecot.org/Quota/FS explains why some of these files need to go in different places (which is why I'm doing it), but I haven't seen a complete list of what files will be moved as a result of those directives. Is there a handy tool to move the files to the right places? Or is there a complete list of what files need to go where? Thanks, Richard From blackvoid+dovecot at fantas.in Wed Jul 23 21:53:56 2014 From: blackvoid+dovecot at fantas.in (BlackVoid) Date: Wed, 23 Jul 2014 23:53:56 +0200 Subject: Multiple passwords with sql authentication In-Reply-To: <20140723142301.Horde.SqlMmtnpCshTTeGosL4DbA5@www.vfemail.net> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> <53D0051D.1040409@fantas.in> <20140723142301.Horde.SqlMmtnpCshTTeGosL4DbA5@www.vfemail.net> Message-ID: <53D02EF4.70908@fantas.in> On 2014-07-23 21:23, Rick Romero wrote: > Quoting BlackVoid : > >> On 2014-07-23 18:40, Rick Romero wrote: >>> Quoting BlackVoid : >>> >>>> On 2014-07-23 18:07, Rick Romero wrote: >>>>> Quoting BlackVoid : >>>>> >>>>>> I'm currently working on a control panel which is using postfix, >>> >>> dovecot >>>>>> and other applications and I want to add application specific >>>>>> passwords >>>>>> to increase security. >>>>>> >>>>>> I found one solution [1], however it requires the password to be >>>>>> included in the query which is something I do not want to do, because >>>>>> the query may be written in clear-text to log-files. So I'm wondering >>> >>> if >>>>>> there is a way to have multiple passwords with dovecot without > risking >>>>>> passwords being leakied in clear-text to log-files. >>> >>> > [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server > >>> >>>>> You can run your query by host (or port - not sure if that variable is >>>>> available in the query) and make it complex.. >>>>> >>>>> For example - (MySQL) >>>>> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >>>>> from >>>>> user where userid = %u >>>>> >>>>> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >>>>> >>>>> If you're using Dovecot as an auth backend for your control panel, I'd >>>>> use >>>>> a custom port only accessible from the web server(s) like 145 for >>>>> IMAP+Control Panel. >>>>> Rick >>>> >>>> The control panel uses the database to authenticate, however I want >>>> users to be able to use applications specific passwords when >>>> authentication via SMTP, IMAP and POP3. The issue with the solution I >>>> found is as I said that the password will be logged in clear-text in > the >>>> query log. >>>> >>>> Perhaps I was no clear enough with what I'm trying to achieve. On > Google >>>> you can have application-specific passwords. This means you can sign in >>>> either with your primary password or an application-specific password >>>> and this is what I'm trying to do. I could solve it using the solution >>>> in my first mail, but that is a security risk, because if someone gains >>>> access to my server for whatever reason, all the person has to do is >>>> check the mysql query log to see everyone's password in clear-text. If > I >>>> did not explain it good enough, perhaps this will help. >>>> https://support.google.com/mail/answer/1173270?hl=en >>>> >>>> So I'm looking for a solution where the dovecot fetches all encrypted >>>> passwords for the user who is trying to sign in and checks if any of > the >>>> returned hashes matched with the entered password and the risk is >>>> non-existent that the password is logged in clear-text. >>> >>> Close. The query returns a single hash, not all of them. The hash >>> returned is specific to the app requesting it due to the complex query. >>> Dovecot then compares the returned hash with the one submitted by the >>> user >>> (which will be specific to the app the user is using). >>> >>> Optimally you shouldn't be storing clear text passwords. The query will >>> never contain the password submitted by the user, it will only return a >>> password to compare. If you are using CRYPT, then Dovecot will hash > the >>> submitted password and compare hashes. >>> >>> Rick >> >> Yes, I know that. The passwords are hashed in SHA-512-CRYPT. As I've >> explained in previous mails, the issue is that only one result can be >> returned, so either I expose the password in the query, the password is >> hashed n-times (number of passwords the user has) and it gets logged >> (security risk) or I have to give up my idea to implement >> application-specific passwords and keep having only one password. You >> can't hash the password and use it in the query either, because the >> password needs to be hashed with the correct salt. So from what I >> cansee there is no good solution to this unless I'm missing something. > > I'm assuming you have a field for each application password. I don't use > a custom salt. > > So your table is like: > CREATE TABLE users ( userid VARCHAR(128) NOT NULL, domain > VARCHAR(128) NOT NULL, password_imap VARCHAR(64) NOT NULL, > password_pop VARCHAR(64) NOT NULL, password_web VARCHAR(64) NOT NULL, > password VARCHAR(64) NOT NULL, home VARCHAR(255) NOT NULL, uid > INTEGER NOT NULL, gid INTEGER NOT NULL ); > in order to return password_web, when the user is using the webmail system, > I would use: > > SELECT > if ( '%r' = '127.0.0.1' AND password_web != " ", > password_web, > if ( '%s' = 'imap' AND password_imap != " > ", password_imap, > if (password_pop != "", > password_pop, password) ) ) > from users where userid = %u > > So if the remote system is 'localhost', and password_web exists, return > password_web. > If not, then if the remote system is using imap, and password_imap > exists return password_imap. > If not imap, then return password_pop if password_pop exists, > otherwise return password. > > And so on and so forth... I plan on doing the same, just haven't gotten > to it. > > I guess I don't see what the problem would be... am I oversimplifying it > somehow? This has been in the back of my head for a while, and even > starting to put it on paper it looks fine for any purpose, even outside of > Dovecot. Obviously it'll be a complex query. Just write it out > logically first. If you're allowing only particular applications, you'll > have to make sure whatever doesn't have a password falls through to > 'password'.. Or, maybe have your 'app password' creation code just > ensure any apps without specific passwords have a copy of the 'password' > field... Or maybe have a boolean field to check if app specific passwords > are on and make that the first if() in the query checks that.... > > Rick That's not a bad solution, however I don't want it to be restricted to specific protocols. For example I have one application-specific password used on my phone, one on my laptop, one on my desktop and I can use it on multiple devices, so it's like an extra password. So that's where the issue lies. The only way I can think of is to prefix your username with an unique id to identify which password should be compared, however that's not practical nor a good solution in my opinion. From fbsd at dannysplace.net Wed Jul 23 22:22:04 2014 From: fbsd at dannysplace.net (Dan Carroll) Date: Thu, 24 Jul 2014 08:22:04 +1000 Subject: ACLs on Top level mailboxes. Message-ID: Hello, I?m in the process of migrating a mail server to new hardware. At the same time, I?ve made the decision to switch from courier to dovecot (v2.2.13) and from what I have seen so far I?m pretty happy. I have two questions for the list. I?d like my users mailboxes (Maildir format) to look like this: Inbox UserCreatedSubFolder1 UserCreatedSubFolder2 ? Sent UserCreatedSubFolder3 Drafts Trash Junk Archives The Top level folders (Sent, Drafts etc) are all ?Special? and I do not wish the users to be able to delete them. I also don?t want them to create new Top level folders. This will force all custom folders to be under a Top Level folder. The Maildir format currently looks like this: ~/Maildir/cur ~/Maildir/new ~/Maildir/tmp ~/Maildir/.INBOX/.UserCreatedSubFolder1/cur ~/Maildir/.INBOX/.UserCreatedSubFolder1/new ~/Maildir/.INBOX/.UserCreatedSubFolder1/tmp ~/Maildir/.Sent/cur ~/Maildir/.Sent/new ~/Maildir/.Sent/tmp etc?. I can get ACLs working with dovecot-acl files, and the permission I need (I think is) ?owner lrwstipe?. But if I put it into the ~/Maildir directory, then it applies to Inbox. I?ve tried creating an .INBOX dir and putting it in there but that did not work. I also tried some global-acl file settings but I could not make that work either. Basically, I?m wondering how to apply ACLs to the Top level and have different ACLs for the actual inbox when using this scheme. I?m not opposed to changing the Maildir format, but that would mean a lot of work re-doing proemial scripts. My second question relates to migration. Is it enough that I copy the Maildir structure and simply delete the courier files or is it a lot better to use a courier->dovecot migration tool? I realise folder subscriptions would be lost but that?s OK, I?ll recreate them manually anyway. Thanks for your time. -Dan From richard at walnut.gen.nz Wed Jul 23 22:23:20 2014 From: richard at walnut.gen.nz (Richard Hector) Date: Thu, 24 Jul 2014 10:23:20 +1200 Subject: Multiple servers and NFS Message-ID: <53D035D8.9080905@walnut.gen.nz> Hi all, For some reason, I didn't go to http://wiki2.dovecot.org/NFS until now, and I'm starting to get worried ... The plan was to have multple servers (MXes) receiving mail, and delivering via LMTP to multiple backend dovecot servers (with amavis in front of dovecot; LMTP both sides). Then we'd have multiple servers for clients to use IMAP or POP3. This is more or less how the system already works, except with Courier IMAP, and postfix on the backends, delivering to maildirs with procmail. But with the recommendation to use the Director for both IMAP/POP3 and LMTP - that starts to sound like I need a whole bunch more servers to run Directors and proxies, and even then it might not be a good idea to have different servers running lmtp and imap/pop. One possible mitigating point is that our 'load balancing' is DNS round-robin, so a given client will probably stick with a single imap/pop server anyway, but if the user has multiple clients (desktop/mobile etc) then they may still hit different servers. Can someone clarify best practice for a setup needing multiple servers for load balancing and redundancy? Is Courier already likely to have been suffering these problems? Oh, the NFS server is a NetApp Filer, if that matters. I'm using dovecot 2.2.9 from debian wheezy backports, in order to get the quota policy daemon support. Thanks, Richard From kabelpada at kabelmail.de Thu Jul 24 04:48:35 2014 From: kabelpada at kabelmail.de (Daniel Parthey) Date: Thu, 24 Jul 2014 06:48:35 +0200 Subject: Multiple servers and NFS In-Reply-To: <53D035D8.9080905@walnut.gen.nz> References: <53D035D8.9080905@walnut.gen.nz> Message-ID: <20140724044835.GA22912@daniel.localdomain> Richard Hector wrote: > But with the recommendation to use the Director for both IMAP/POP3 and LMTP > - that starts to sound like I need a whole bunch more servers to run > Directors and proxies, and even then it might not be a good idea to have > different servers running lmtp and imap/pop. Running Multiple Invocations of Dovecot is totally sufficient: http://wiki2.dovecot.org/RunningDovecot http://wiki2.dovecot.org/Tools/Doveadm/Instance Regards Daniel From dovecot at tengu.ch Thu Jul 24 05:36:16 2014 From: dovecot at tengu.ch (=?UTF-8?B?Q8OpZHJpYyBKZWFubmVyZXQ=?=) Date: Thu, 24 Jul 2014 07:36:16 +0200 Subject: Multiple passwords with sql authentication In-Reply-To: <53D02EF4.70908@fantas.in> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> <53D0051D.1040409@fantas.in> <20140723142301.Horde.SqlMmtnpCshTTeGosL4DbA5@www.vfemail.net> <53D02EF4.70908@fantas.in> Message-ID: <53D09B50.5060908@tengu.ch> On 07/23/2014 11:53 PM, BlackVoid wrote: > On 2014-07-23 21:23, Rick Romero wrote: >> Quoting BlackVoid : >> >>> On 2014-07-23 18:40, Rick Romero wrote: >>>> Quoting BlackVoid : >>>> >>>>> On 2014-07-23 18:07, Rick Romero wrote: >>>>>> Quoting BlackVoid : >>>>>> >>>>>>> I'm currently working on a control panel which is using postfix, >>>> >>>> dovecot >>>>>>> and other applications and I want to add application specific >>>>>>> passwords >>>>>>> to increase security. >>>>>>> >>>>>>> I found one solution [1], however it requires the password to be >>>>>>> included in the query which is something I do not want to do, because >>>>>>> the query may be written in clear-text to log-files. So I'm wondering >>>> >>>> if >>>>>>> there is a way to have multiple passwords with dovecot without >> risking >>>>>>> passwords being leakied in clear-text to log-files. >>>> >>>> >> [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server >> >>>> >>>>>> You can run your query by host (or port - not sure if that variable is >>>>>> available in the query) and make it complex.. >>>>>> >>>>>> For example - (MySQL) >>>>>> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >>>>>> from >>>>>> user where userid = %u >>>>>> >>>>>> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >>>>>> >>>>>> If you're using Dovecot as an auth backend for your control panel, I'd >>>>>> use >>>>>> a custom port only accessible from the web server(s) like 145 for >>>>>> IMAP+Control Panel. >>>>>> Rick >>>>> >>>>> The control panel uses the database to authenticate, however I want >>>>> users to be able to use applications specific passwords when >>>>> authentication via SMTP, IMAP and POP3. The issue with the solution I >>>>> found is as I said that the password will be logged in clear-text in >> the >>>>> query log. >>>>> >>>>> Perhaps I was no clear enough with what I'm trying to achieve. On >> Google >>>>> you can have application-specific passwords. This means you can sign in >>>>> either with your primary password or an application-specific password >>>>> and this is what I'm trying to do. I could solve it using the solution >>>>> in my first mail, but that is a security risk, because if someone gains >>>>> access to my server for whatever reason, all the person has to do is >>>>> check the mysql query log to see everyone's password in clear-text. If >> I >>>>> did not explain it good enough, perhaps this will help. >>>>> https://support.google.com/mail/answer/1173270?hl=en >>>>> >>>>> So I'm looking for a solution where the dovecot fetches all encrypted >>>>> passwords for the user who is trying to sign in and checks if any of >> the >>>>> returned hashes matched with the entered password and the risk is >>>>> non-existent that the password is logged in clear-text. >>>> >>>> Close. The query returns a single hash, not all of them. The hash >>>> returned is specific to the app requesting it due to the complex query. >>>> Dovecot then compares the returned hash with the one submitted by the >>>> user >>>> (which will be specific to the app the user is using). >>>> >>>> Optimally you shouldn't be storing clear text passwords. The query will >>>> never contain the password submitted by the user, it will only return a >>>> password to compare. If you are using CRYPT, then Dovecot will hash >> the >>>> submitted password and compare hashes. >>>> >>>> Rick >>> >>> Yes, I know that. The passwords are hashed in SHA-512-CRYPT. As I've >>> explained in previous mails, the issue is that only one result can be >>> returned, so either I expose the password in the query, the password is >>> hashed n-times (number of passwords the user has) and it gets logged >>> (security risk) or I have to give up my idea to implement >>> application-specific passwords and keep having only one password. You >>> can't hash the password and use it in the query either, because the >>> password needs to be hashed with the correct salt. So from what I >>> cansee there is no good solution to this unless I'm missing something. >> >> I'm assuming you have a field for each application password. I don't use >> a custom salt. >> >> So your table is like: >> CREATE TABLE users ( userid VARCHAR(128) NOT NULL, domain >> VARCHAR(128) NOT NULL, password_imap VARCHAR(64) NOT NULL, >> password_pop VARCHAR(64) NOT NULL, password_web VARCHAR(64) NOT NULL, >> password VARCHAR(64) NOT NULL, home VARCHAR(255) NOT NULL, uid >> INTEGER NOT NULL, gid INTEGER NOT NULL ); >> in order to return password_web, when the user is using the webmail system, >> I would use: >> >> SELECT >> if ( '%r' = '127.0.0.1' AND password_web != " ", >> password_web, >> if ( '%s' = 'imap' AND password_imap != " >> ", password_imap, >> if (password_pop != "", >> password_pop, password) ) ) >> from users where userid = %u >> >> So if the remote system is 'localhost', and password_web exists, return >> password_web. >> If not, then if the remote system is using imap, and password_imap >> exists return password_imap. >> If not imap, then return password_pop if password_pop exists, >> otherwise return password. >> >> And so on and so forth... I plan on doing the same, just haven't gotten >> to it. >> >> I guess I don't see what the problem would be... am I oversimplifying it >> somehow? This has been in the back of my head for a while, and even >> starting to put it on paper it looks fine for any purpose, even outside of >> Dovecot. Obviously it'll be a complex query. Just write it out >> logically first. If you're allowing only particular applications, you'll >> have to make sure whatever doesn't have a password falls through to >> 'password'.. Or, maybe have your 'app password' creation code just >> ensure any apps without specific passwords have a copy of the 'password' >> field... Or maybe have a boolean field to check if app specific passwords >> are on and make that the first if() in the query checks that.... >> >> Rick > > That's not a bad solution, however I don't want it to be restricted to > specific protocols. For example I have one application-specific password > used on my phone, one on my laptop, one on my desktop and I can use it > on multiple devices, so it's like an extra password. So that's where the > issue lies. The only way I can think of is to prefix your username with > an unique id to identify which password should be compared, however > that's not practical nor a good solution in my opinion. > Hello, maybe a stupid question, but why log queries? Just drop that log. Also, if I understand correctly Dovecot working scheme, it should hash the password in the query directly if you remove the PLAIN mechanism? Another solution (and probably the best): Dovecot should provide another variable than %w, like %W which will be the hashed password according to the password schema defined in the configuration? Your idea is really interesting by the way. Was thinking about it for some times now, never had the time to really try something? C. From skdovecot at smail.inf.fh-brs.de Thu Jul 24 06:18:50 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 24 Jul 2014 08:18:50 +0200 (CEST) Subject: Maildir migration - using separate INDEX and CONTROL directories? In-Reply-To: <53D02B17.9030402@walnut.gen.nz> References: <53D02B17.9030402@walnut.gen.nz> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 24 Jul 2014, Richard Hector wrote: > I'm working on a migration from Courier to Dovecot, and the > courier-dovecot-migrate.pl seems to work ok, but it puts all the metadata > files (dovecot-uidlist etc) in the Maildir, while I want to put them in the > appropriate places as specified: > > mail_location = > maildir:~/Maildir:INDEX=/var/mail/meta/index/%d/%1n/%1.1n/%n:CONTROL=/var/mail/meta/control/%d/%1n/%1.1n/%n > > http://wiki2.dovecot.org/Quota/FS explains why some of these files need to go > in different places (which is why I'm doing it), but I haven't seen a > complete list of what files will be moved as a result of those directives. > > Is there a handy tool to move the files to the right places? Or is there a > complete list of what files need to go where? IMHO: move all dovecot* files the migration script generates and the "subscriptions" file into the control directories, some INBOX-related files probably go to /.INBOX, dovecot-keywords and dovecot-uidlist - maybe more. The migration scripts I saw til today never create any indexes, so the assumption should be fine. And test it with one account, move some messages around, add some subscriptions and ACLs, ... - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9ClSnz1H7kL/d9rAQJ3NAgAgTj8v7AD/I3BaU1fIpx7WcjQj1jBBMUr dKWmPB/EvhXxpR+emT9j6p+YVPUTxYSLpTV7XyeFJHSO80UDqYqfDJqmaWyz0BH7 zp9GHeNaTmqHko2yOfcQN31lutTk8i9nsioqDt4rlTL6hAdzm/V9R0YtrB47wQDH YengWtWIUIrj7+G6+k11U/hjG2QY+CmD0f4tzTqx1nnIG8X9HgZDzw2qgTBv4Y2y L6fHg2fbwlbbhSMZGS2nf8WLgiwsBUJ1dC2fX9A47d6/eNs1vDzCBbf1KlPpVQ9w EpWuY/oxfJU8Ksc8xn7vP2vGvlapQFs7UOrfbbVQJhjf3FjibV6+nA== =SBrc -----END PGP SIGNATURE----- From fc193 at hotmail.com Thu Jul 24 08:50:21 2014 From: fc193 at hotmail.com (Franck CALLEJA) Date: Thu, 24 Jul 2014 10:50:21 +0200 Subject: Sieve plugin (fc17 + sendmail + roundcube) Message-ID: Hello, I'm trying to configure sieve plugin on my mail server so that people can do mail filtering (and mostly vacation notification) on their account. The mail server is running fine since 5 years and is based on :- sendmail- dovecot- roundcube It serves 2 differents domains. I've recently installed pigeonhole for fc17, and managed to configure managesieve plugin in roundcube successfully. Users can now manage filters from roundcube. The problem is that filters are not applied when new mails arrives. I've modified dovecot.conf to activate sieve plugin, and the configuration is as follow : # dovecot -n# 2.1.16: /etc/dovecot/dovecot.conf# OS: Linux 3.8.13-100.fc17.x86_64 x86_64 Fedora release 17 (Beefy Miracle) log_path = /var/log/dovecot.logmail_debug = yesmail_location = mbox:~/mail:INBOX=/var/spool/mail/%umanagesieve_notify_capability = mailtomanagesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihavembox_write_locks = fcntlnamespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = }passdb { driver = pam}plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve}protocols = imap pop3 lmtp sieveservice imap-login { service_count = 0}service lmtp { executable = lmtp -L}service pop3-login { service_count = 0}ssl_cert = -o /etc/mail/access.db')dnl FEATURE(`blacklist_recipients')dnlEXPOSED_USER(`root')dnl DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnlFEATURE(`accept_unresolvable_domains')dnl FEATURE(`relay_hosts_only')dnl FEATURE(`dnsbl', `ipwhois.rfc-ignorant.org',`"550 Mail from " $&{client_addr} " refused. Rejected for bad WHOIS info on IP of your SMTP server - see http://www.rfc-ignorant.org/"') FEATURE(`dnsbl', `proxies.blackholes.easynet.nl', `"550 5.7.1 ACCESS DENIED to OPEN PROXY SERVER "$&{client_name}" by easynet.nl DNSBL (http://proxies.blackholes.easynet.nl/errors.html)"', `') FEATURE(`dnsbl', `bl.spamcop.net', `"450 Mail from " $`'&{client_addr} " refused - see http://spamcop.net/bl.shtml"') FEATURE(`dnsbl',`sbl.spamhaus.org',`Rejected - see http://spamhaus.org/') MAILER(smtp)dnl MAILER(procmail)dnl I've created a /etc/procmailrc file in /etc to activate dovecot but this doesn't work and users can't get any mails : # cat /etc/procmailrc.old # file: /etc/procmailrc # system-wide settings for procmail DROPPRIVS=YES SHELL="/bin/bash" SENDMAIL="/usr/sbin/sendmail -oi -t" LOGFILE="/var/log/procmail.log" DELIVER="/usr/libexec/dovecot/deliver" # fallback: DEFAULT="$HOME/mail/" MAILDIR="$HOME/mail/" :0 w * ^X-Spam-Status: Yes | $DELIVER -m spam :0 w | $DELIVER As it is a production server, I'm not confident to make modifications in all directions, and would need some help to process safely this update on my mail server. I think I'm missing some parameters somewhere, but the question is... where ? so any help would be appreciated. RegardsFranck. From bluewind at xinu.at Thu Jul 24 08:53:08 2014 From: bluewind at xinu.at (Florian Pritz) Date: Thu, 24 Jul 2014 10:53:08 +0200 Subject: FTS lucene indexer-worker segfaulting Message-ID: <53D0C974.5010607@xinu.at> Hi, I've just set up fts-lucene and when I run searches on my inbox or when I run the indexer (`doveadm index INBOX`) I get the following segfault. I've run it multiple times and noticed that the data value is different each time so I guess it doesn't always crash at the same point. I'm running dovecot 2.2.13-1 with clucene 2.3.3.4-8 on Arch Linux. If you need any more information I'll be happy to help. config: > # 2.2.13: /etc/dovecot/dovecot.conf > # OS: Linux 3.15.2-1-ARCH i686 > mail_location = mdbox:~/.mdbox > mail_plugins = " fts fts_lucene" > namespace { > hidden = no > inbox = yes > location = > prefix = INBOX. > separator = . > type = private > } > passdb { > driver = pam > } > plugin { > fts = lucene > fts_autoindex = yes > fts_lucene = whitespace_chars=@. > } > protocols = imap > service auth { > user = root > } > ssl_cert = ssl_key = userdb { > driver = passwd > } > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > } > protocol lda { > postmaster_address = postmaster at server-speed.net > } syslog: > Jul 24 10:27:21 mistral dovecot: indexer-worker(flo): Warning: Growing data stack with: 32768 > Jul 24 10:27:26 mistral kernel: [1814196.532882] indexer-worker[22785] segfault at 9180000 ip b745d860 sp bfad86cc error 4 in libc-2.19.so[b73ba000+1bb000] > Jul 24 10:27:27 mistral dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for flo > Jul 24 10:27:27 mistral dovecot: indexer-worker(flo): Fatal: master: service(indexer-worker): child 22785 killed with signal 11 (core dumped) > Jul 24 10:27:27 mistral dovecot: imap(flo): Error: indexer failed to index mailbox INBOX backtrace: > #0 0xb745d860 in __wcslen_sse2 () from /usr/lib/libc.so.6 > No symbol table info available. > #1 0xb744e88b in wcsdup () from /usr/lib/libc.so.6 > No symbol table info available. > #2 0xb728cff0 in lucene::document::Field::Field(wchar_t const*, wchar_t const*, int, bool) () > from /usr/lib/libclucene-core.so.1 > No symbol table info available. > #3 0xb73aa5d8 in lucene_index_build_more (index=0x8b24130, uid=4403, part_idx=0, > data=0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size=8188, > hdr_name=0x0) at lucene-wrapper.cc:582 > namesize = > dest = 0x915f5d0 L"1: kernel: i7core_edac 0000:00:14 0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c 0: restoring config space at offset 0x1 (was 0x100000, writing "... > dest_free = 0x915f5d0 L"1: kernel: i7core_edac 0000:00:14 0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c 0: restoring config space at offset 0x1 (was 0x100000, writing "... > id = L"\x8cb0900\000\000\000\x8ebef98\x8c21978\000?\x8c93a10\xb74e2df5\xbfad8788\xbfad87d4\x8cb0938\xbfad88e8\xbfad88e4\x8925f300\x8cb0938\xbfad88e8\xb7624a4d\xb7684000?\x8b38f08\x8fbb488" > datasize = > #4 0xb73a8f47 in fts_backend_lucene_update_build_more (_ctx=0x8b3c578, > data=0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size=8188) > at fts-backend-lucene.c:415 > _data_stack_cur_id = 6 > ctx = 0x8b3c578 > backend = 0x8b23850 > ret = > #5 0xb7586cda in fts_backend_update_build_more (ctx=0x8b3c578, > data=0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size=8188) > at fts-api.c:193 > __FUNCTION__ = "fts_backend_update_build_more" > #6 0xb7587814 in fts_build_body_block (ctx=0xbfad88fc, block=0xbfad88ec, last=false) at fts-build-mail.c:236 > i = 8188 > __FUNCTION__ = "fts_build_body_block" > #7 0xb7587dfc in fts_build_mail_real (mail=, update_ctx=) at fts-build-mail.c:352 > ctx = {mail = 0x8b32ed0, update_ctx = 0x8b3c578, content_type = 0x0, content_disposition = 0x0, > body_parser = 0x8b40f20, word_buf = 0x0} > parser = 0x8c21948 > decoder = 0x8b51410 > raw_block = {part = 0x8b13668, hdr = 0x0, > data = 0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size = 8192} > block = {part = 0x8b13668, hdr = 0x0, > data = 0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size = 8192} > ret = -1079146260 > input = 0x8cb0938 > parts = 0x1133 > #8 fts_build_mail (update_ctx=0x8b3c578, mail=0x8b32ed0) at fts-build-mail.c:386 > _data_stack_cur_id = 5 > #9 0xb758d8cc in fts_mail_index (_mail=) at fts-storage.c:451 > ft = 0x8b2ef98 > #10 fts_mail_precache (_mail=0x8b32ed0) at fts-storage.c:468 > _data_stack_cur_id = 4 > fmail = 0x8b2ef98 > ft = 0x8b28920 > #11 0xb76f3e5b in mail_precache (mail=0x8b32ed0) at mail.c:350 > p = 0x8b32ed0 > #12 0x08049caf in index_mailbox_precache (conn=, box=) at master-connection.c:86 > percentage_str = "8\n\000\b" > storage = 0x9180000 > status = {messages = 35744, recent = 0, unseen = 0, uidvalidity = 1240057599, uidnext = 45338, > first_unseen_seq = 0, first_recent_uid = 45338, last_cached_seq = 2, highest_modseq = 0, highest_pvt_modseq = 0, > keywords = 0x0, permanent_flags = 0, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, > no_modseq_tracking = 0, have_guids = 1, have_save_guids = 1, have_only_guid128 = 0} > ctx = 0x8b32d38 > seq = 3275 > trans = 0x8b30128 > search_args = 0x0 > mail = 0x8b32ed0 > metadata = {guid = '\000' , virtual_size = 0, cache_fields = 0x0, > precache_fields = (MAIL_FETCH_STREAM_HEADER | MAIL_FETCH_STREAM_BODY | MAIL_FETCH_RECEIVED_DATE | MAIL_FETCH_SAVE_DATE | MAIL_FETCH_PHYSICAL_SIZE | MAIL_FETCH_VIRTUAL_SIZE | MAIL_FETCH_UIDL_BACKEND | MAIL_FETCH_GUID), > backend_ns_prefix = 0x0, backend_ns_type = (unknown: 0)} > counter = 3275 > max = 35742 > #13 index_mailbox (what=, max_recent_msgs=, mailbox=, user=, > conn=) at master-connection.c:172 > box = 0x8b2baf0 > status = {messages = 11, recent = 145850608, unseen = 2050, uidvalidity = 3076213424, uidnext = 0, > first_unseen_seq = 3076213430, first_recent_uid = 3077062656, last_cached_seq = 3076215829, > highest_modseq = 7510788772, highest_pvt_modseq = 3215821508, keywords = 0xb77ed7a0, > permanent_flags = 3215821476, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, > no_modseq_tracking = 1, have_guids = 0, have_save_guids = 1, have_only_guid128 = 1} > errstr = 0x9180000 > ns = 0x9180000 > path = 0x8b12428 "/home/flo/.mdbox/mailboxes/INBOX/dbox-Mails" > error = 35744 > sync_flags = (unknown: 152567808) > #14 master_connection_input_line (line=, conn=) at master-connection.c:208 > str = 0x9180000 > max_recent_msgs = 0 > args = 0xccb > input = {module = 0x804a2d7 "mail", service = 0x804a2c8 "indexer-worker", username = 0x8b11090 "flo", > session_id = 0x0, local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' , > __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = { > family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, > 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, > userdb_fields = 0x0, flags_override_add = (unknown: 0), flags_override_remove = (unknown: 0), > no_userdb_lookup = 0} > service_user = 0x8b1b508 > user = 0x8b246d8 > error = 0x25 > #15 master_connection_input (conn=0x8b19250) at master-connection.c:245 > _data_stack_cur_id = 3 > line = 0x8 > line = 0x9180000 > #16 0xb760e2c3 in io_loop_call_io (io=0x8b19270) at ioloop.c:441 > ioloop = 0x8b154b8 > t_id = 2 > __FUNCTION__ = "io_loop_call_io" > #17 0xb760f4ae in io_loop_handler_run_internal (ioloop=0x8b154b8) at ioloop-epoll.c:220 > ctx = 0x8b18908 > list = 0x8b192a8 > io = > tv = {tv_sec = 2147483, tv_usec = 0} > events_count = > msecs = > ret = 1 > i = > j = 0 > call = > __FUNCTION__ = "io_loop_handler_run_internal" > #18 0xb760e34a in io_loop_handler_run (ioloop=0x8b154b8) at ioloop.c:488 > No locals. > #19 0xb760e3e9 in io_loop_run (ioloop=0x8b154b8) at ioloop.c:465 > __FUNCTION__ = "io_loop_run" > #20 0xb75b49b5 in master_service_run (service=0x8b153e0, callback=0x80498f0 ) at master-service.c:566 > No locals. > #21 0x08049757 in main (argc=1, argv=0xbfad8d94) at indexer-worker.c:78 > storage_service_flags = > c = -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From skdovecot at smail.inf.fh-brs.de Thu Jul 24 09:00:13 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 24 Jul 2014 11:00:13 +0200 (CEST) Subject: Sieve plugin (fc17 + sendmail + roundcube) In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 24 Jul 2014, Franck CALLEJA wrote: > Date: Thu, 24 Jul 2014 10:50:21 +0200 > From: Franck CALLEJA > Reply-To: Dovecot Mailing List > To: "dovecot at dovecot.org" > Subject: Sieve plugin (fc17 + sendmail + roundcube) > > Hello, I'm trying to configure sieve plugin on my mail server so that people can do mail filtering (and mostly vacation notification) on their account. The mail server is running fine since 5 years and is based on :- sendmail- dovecot- roundcube It serves 2 differents domains. I've recently installed pigeonhole for fc17, and managed to configure managesieve plugin in roundcube successfully. Users can now manage filters from roundcube. The problem is that filters are not applied when new mails arrives. I've modified dovecot.conf to activate sieve plugin, and the configuration is as follow : # dovecot -n# 2.1.16: /etc/dovecot/dovecot.conf# OS: Linux 3.8.13-100.fc17.x86_64 x86_64 Fedora release 17 (Beefy Miracle) log_path = /var/log/dovecot.logmail_debug = yesmail_location = mbox:~/mail:INBOX=/var/spool/mail/%umanagesieve_notify_capability = mailtomanagesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relationa! l regex imap4flags copy include variables body enotify environment mailbox date ihavembox_write_locks = fcntlnamespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = }passdb { driver = pam}plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve}protocols = imap pop3 lmtp sieveservice imap-login { service_count = 0}service lmtp { executable = lmtp -L}service pop3-login { service_count = 0}ssl_cert = divert(-1)dnl > include(`/usr/share/sendmail-cf/m4/cf.m4')dnl > VERSIONID(`setup for linux')dnl > OSTYPE(`linux')dnl > define(`confLOG_LEVEL', `15')dnl > define(`confDEF_USER_ID', ``8:12'')dnl > define(`confTO_CONNECT', `5m')dnl > define(`confTRY_NULL_MX_LIST', `True')dnl > define(`confDONT_PROBE_INTERFACES', `True')dnl > define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl > define(`ALIAS_FILE', `/etc/aliases')dnl > define(`STATUS_FILE', `/var/log/mail/statistics')dnl > define(`UUCP_MAILER_MAX', `2000000')dnl > define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl > define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl > define(`confAUTH_OPTIONS', `A')dnl > define(`confMIN_QUEUE_AGE', `15m')dnl > define(`confTO_QUEUERETURN', `5m')dnl > define(`confMAX_MESSAGE_SIZE', `15000000')dnl > define(`confDONT_BLAME_SENDMAIL', `forwardfileingroupwritabledirpath,ForwardFileInUnsafeDirPath,ForwardFileInUnsafeDirPathSafe')dnl > define(`confTO_IDENT', `0')dnlFEATURE(`no_default_msa', `dnl')dnl > FEATURE(`smrsh', `/usr/sbin/smrsh')dnl > FEATURE(`mailertable', `hash -o /etc/mail/mailertable.db')dnl > FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable.db')dnl > FEATURE(`genericstable',`hash -o /etc/mail/genericstable.db')dnlGENERICS_DOMAIN_FILE(`/etc/mail/generics-domains')dnlFEATURE(redirect)dnl > FEATURE(always_add_domain)dnl > FEATURE(use_cw_file) > FEATURE(use_ct_file)dnl > FEATURE(local_procmail, `', `procmail -t -Y -a $h -d $u')dnl > FEATURE(`access_db', `hash -T -o /etc/mail/access.db')dnl > FEATURE(`blacklist_recipients')dnlEXPOSED_USER(`root')dnl > DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnlFEATURE(`accept_unresolvable_domains')dnl > FEATURE(`relay_hosts_only')dnl > FEATURE(`dnsbl', `ipwhois.rfc-ignorant.org',`"550 Mail from " $&{client_addr} " refused. Rejected for bad WHOIS info on IP of your SMTP server - see http://www.rfc-ignorant.org/"') > FEATURE(`dnsbl', `proxies.blackholes.easynet.nl', `"550 5.7.1 ACCESS DENIED to OPEN PROXY SERVER "$&{client_name}" by easynet.nl DNSBL (http://proxies.blackholes.easynet.nl/errors.html)"', `') > FEATURE(`dnsbl', `bl.spamcop.net', `"450 Mail from " $`'&{client_addr} " refused - see http://spamcop.net/bl.shtml"') > FEATURE(`dnsbl',`sbl.spamhaus.org',`Rejected - see http://spamhaus.org/') > MAILER(smtp)dnl > MAILER(procmail)dnl I've created a /etc/procmailrc file in /etc to activate dovecot but this doesn't work and users can't get any mails : # cat /etc/procmailrc.old > # file: /etc/procmailrc > # system-wide settings for procmail > DROPPRIVS=YES > SHELL="/bin/bash" > SENDMAIL="/usr/sbin/sendmail -oi -t" > LOGFILE="/var/log/procmail.log" > DELIVER="/usr/libexec/dovecot/deliver" > # fallback: > DEFAULT="$HOME/mail/" > MAILDIR="$HOME/mail/" > :0 w > * ^X-Spam-Status: Yes > | $DELIVER -m spam > :0 w > | $DELIVER As it is a production server, I'm not confident to make modifications in all directions, and would need some help to process safely this update on my mail server. > I think I'm missing some parameters somewhere, but the question is... where ? so any help would be appreciated. RegardsFranck. What are the log messages from the Dovecot LDA? Maybe, add mail_debug=yes - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9DLHXz1H7kL/d9rAQIP+gf+NsAgryy5RZPl70mtENJRso5A7GBHVtIg j0+QiOnxRuFmkg77jeSsycPlLBYVL0qtc9737bqT/tuvPRv7K1m4/lsQlnWP1rKS HLT7y7BcmQOjJOSAAElfcrilrpmyzQ1Ao7uWZBPlKLWN0sz6/COm5TFl0m3Jmjzd Fy0thv5yVFjTTYiPdWHV4RaTXyE/C1Bn4nbuzCm5FVCeTx5V2cUPXuwahMi7upSK dRHrUYv0e8u5e4b5gPGKy/dlPij3iQrt5RkGJDCd7yos+WFKiumTVcNTPFoEQJ72 04rpouDcB5YCr80b14/Rt5MIVumMZq//0AbVFe27X5+Gpvv1YxHtBA== =+igM -----END PGP SIGNATURE----- From bluewind at xinu.at Thu Jul 24 09:10:08 2014 From: bluewind at xinu.at (Florian Pritz) Date: Thu, 24 Jul 2014 11:10:08 +0200 Subject: FTS lucene indexer-worker segfaulting In-Reply-To: <53D0C974.5010607@xinu.at> References: <53D0C974.5010607@xinu.at> Message-ID: <53D0CD70.6040100@xinu.at> On 24.07.2014 10:53, Florian Pritz wrote: > I've just set up fts-lucene and when I run searches on my inbox or when > I run the indexer (`doveadm index INBOX`) I get the following segfault. > I've run it multiple times and noticed that the data value is different > each time so I guess it doesn't always crash at the same point. I ran it a couple more times and once I got this backtrace. On the next run it completed just fine and now it doesn't run very long anymore so I guess it's fully indexed. Any way to get it to rebuild the whole index? Removing $mail_location/lucene-indexes doesn't seem to do anything. > #0 0xb7c23860 in __wcslen_sse2 () from /usr/lib/libc.so.6 > #1 0xb7a79b5f in ?? () from /usr/lib/libclucene-core.so.1 > #2 0xb7a7a233 in ?? () from /usr/lib/libclucene-core.so.1 > #3 0xb7a7a660 in ?? () from /usr/lib/libclucene-core.so.1 > #4 0xb7a6fe44 in ?? () from /usr/lib/libclucene-core.so.1 > #5 0xb7aa906d in lucene::index::IndexWriter::addDocument(lucene::document::Document*, lucene::analysis::Analyzer*) () > from /usr/lib/libclucene-core.so.1 > #6 0xb7b7099a in lucene_index_build_flush (index=index at entry=0x80cbea8) at lucene-wrapper.cc:516 > #7 0xb7b7124a in lucene_index_build_more (index=0x80cbea8, uid=3149, part_idx=0, > data=0x82a91e8 "", size=29, hdr_name=0x82efea8 "Return-Path") at lucene-wrapper.cc:536 > #8 0xb7b6ff47 in fts_backend_lucene_update_build_more (_ctx=0x80e5d88, data=0x82a91e8 "", > size=29) at fts-backend-lucene.c:415 > #9 0xb7fc9cda in fts_backend_update_build_more (ctx=0x80e5d88, data=0x82a91e8 "", size=29) > at fts-api.c:193 > #10 0xb7fcb1a8 in fts_build_unstructured_header (ctx=, hdr=, hdr=) > at fts-build-mail.c:94 > #11 fts_build_mail_header (block=, block=, ctx=) at fts-build-mail.c:122 > #12 fts_build_mail_real (mail=, update_ctx=) at fts-build-mail.c:345 > #13 fts_build_mail (update_ctx=0x80e5d88, mail=0x80db658) at fts-build-mail.c:386 > #14 0xb7fd08cc in fts_mail_index (_mail=) at fts-storage.c:451 > #15 fts_mail_precache (_mail=0x80db658) at fts-storage.c:468 > #16 0xb7ea0e5b in mail_precache (mail=0x80db658) at mail.c:350 > #17 0x0805a9a4 in cmd_index_box_precache (box=) at doveadm-mail-index.c:69 > #18 cmd_index_box (info=, info=, ctx=) at doveadm-mail-index.c:118 > #19 cmd_index_run (_ctx=0x80c61f8, user=0x80cd628) at doveadm-mail-index.c:189 > #20 0x08056200 in doveadm_mail_next_user (ctx=0x80c61f8, input=, error_r=0xbffffb68) at doveadm-mail.c:314 > #21 0x08056ede in doveadm_mail_cmd (argv=0x80bf1e0, argc=, cmd=) at doveadm-mail.c:525 > #22 doveadm_mail_try_run (cmd_name=0x80bf1f9 "index", argc=2, argv=0x80bf1dc) at doveadm-mail.c:617 > #23 0x08055d93 in main (argc=2, argv=0xbffffd44) at doveadm.c:398 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From blackvoid+dovecot at fantas.in Thu Jul 24 09:45:29 2014 From: blackvoid+dovecot at fantas.in (BlackVoid) Date: Thu, 24 Jul 2014 11:45:29 +0200 Subject: Multiple passwords with sql authentication In-Reply-To: <53D09B50.5060908@tengu.ch> References: <20140723110717.Horde.HtZDlexGdW3k_ozRrLsTlg2@www.vfemail.net> <53CFE2E3.2030105@fantas.in> <20140723114033.Horde.Pb1TJxxyK9BgTVSVZqQmew6@www.vfemail.net> <53D0051D.1040409@fantas.in> <20140723142301.Horde.SqlMmtnpCshTTeGosL4DbA5@www.vfemail.net> <53D02EF4.70908@fantas.in> <53D09B50.5060908@tengu.ch> Message-ID: <53D0D5B9.7030003@fantas.in> On 2014-07-24 07:36, C?dric Jeanneret wrote: > On 07/23/2014 11:53 PM, BlackVoid wrote: >> On 2014-07-23 21:23, Rick Romero wrote: >>> Quoting BlackVoid : >>> >>>> On 2014-07-23 18:40, Rick Romero wrote: >>>>> Quoting BlackVoid : >>>>> >>>>>> On 2014-07-23 18:07, Rick Romero wrote: >>>>>>> Quoting BlackVoid : >>>>>>> >>>>>>>> I'm currently working on a control panel which is using postfix, >>>>> >>>>> dovecot >>>>>>>> and other applications and I want to add application specific >>>>>>>> passwords >>>>>>>> to increase security. >>>>>>>> >>>>>>>> I found one solution [1], however it requires the password to be >>>>>>>> included in the query which is something I do not want to do, because >>>>>>>> the query may be written in clear-text to log-files. So I'm wondering >>>>> >>>>> if >>>>>>>> there is a way to have multiple passwords with dovecot without >>> risking >>>>>>>> passwords being leakied in clear-text to log-files. >>>>> >>>>> >>> [1]http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server >>> >>>>> >>>>>>> You can run your query by host (or port - not sure if that variable is >>>>>>> available in the query) and make it complex.. >>>>>>> >>>>>>> For example - (MySQL) >>>>>>> SELECT if ('%r'!='127.0.0.1', webmail_pass, enc_password) as password >>>>>>> from >>>>>>> user where userid = %u >>>>>>> >>>>>>> http://komlenic.com/254/mysql-nested-if-in-select-queries/ >>>>>>> >>>>>>> If you're using Dovecot as an auth backend for your control panel, I'd >>>>>>> use >>>>>>> a custom port only accessible from the web server(s) like 145 for >>>>>>> IMAP+Control Panel. >>>>>>> Rick >>>>>> >>>>>> The control panel uses the database to authenticate, however I want >>>>>> users to be able to use applications specific passwords when >>>>>> authentication via SMTP, IMAP and POP3. The issue with the solution I >>>>>> found is as I said that the password will be logged in clear-text in >>> the >>>>>> query log. >>>>>> >>>>>> Perhaps I was no clear enough with what I'm trying to achieve. On >>> Google >>>>>> you can have application-specific passwords. This means you can sign in >>>>>> either with your primary password or an application-specific password >>>>>> and this is what I'm trying to do. I could solve it using the solution >>>>>> in my first mail, but that is a security risk, because if someone gains >>>>>> access to my server for whatever reason, all the person has to do is >>>>>> check the mysql query log to see everyone's password in clear-text. If >>> I >>>>>> did not explain it good enough, perhaps this will help. >>>>>> https://support.google.com/mail/answer/1173270?hl=en >>>>>> >>>>>> So I'm looking for a solution where the dovecot fetches all encrypted >>>>>> passwords for the user who is trying to sign in and checks if any of >>> the >>>>>> returned hashes matched with the entered password and the risk is >>>>>> non-existent that the password is logged in clear-text. >>>>> >>>>> Close. The query returns a single hash, not all of them. The hash >>>>> returned is specific to the app requesting it due to the complex query. >>>>> Dovecot then compares the returned hash with the one submitted by the >>>>> user >>>>> (which will be specific to the app the user is using). >>>>> >>>>> Optimally you shouldn't be storing clear text passwords. The query will >>>>> never contain the password submitted by the user, it will only return a >>>>> password to compare. If you are using CRYPT, then Dovecot will hash >>> the >>>>> submitted password and compare hashes. >>>>> >>>>> Rick >>>> >>>> Yes, I know that. The passwords are hashed in SHA-512-CRYPT. As I've >>>> explained in previous mails, the issue is that only one result can be >>>> returned, so either I expose the password in the query, the password is >>>> hashed n-times (number of passwords the user has) and it gets logged >>>> (security risk) or I have to give up my idea to implement >>>> application-specific passwords and keep having only one password. You >>>> can't hash the password and use it in the query either, because the >>>> password needs to be hashed with the correct salt. So from what I >>>> cansee there is no good solution to this unless I'm missing something. >>> >>> I'm assuming you have a field for each application password. I don't use >>> a custom salt. >>> >>> So your table is like: >>> CREATE TABLE users ( userid VARCHAR(128) NOT NULL, domain >>> VARCHAR(128) NOT NULL, password_imap VARCHAR(64) NOT NULL, >>> password_pop VARCHAR(64) NOT NULL, password_web VARCHAR(64) NOT NULL, >>> password VARCHAR(64) NOT NULL, home VARCHAR(255) NOT NULL, uid >>> INTEGER NOT NULL, gid INTEGER NOT NULL ); >>> in order to return password_web, when the user is using the webmail system, >>> I would use: >>> >>> SELECT >>> if ( '%r' = '127.0.0.1' AND password_web != " ", >>> password_web, >>> if ( '%s' = 'imap' AND password_imap != " >>> ", password_imap, >>> if (password_pop != "", >>> password_pop, password) ) ) >>> from users where userid = %u >>> >>> So if the remote system is 'localhost', and password_web exists, return >>> password_web. >>> If not, then if the remote system is using imap, and password_imap >>> exists return password_imap. >>> If not imap, then return password_pop if password_pop exists, >>> otherwise return password. >>> >>> And so on and so forth... I plan on doing the same, just haven't gotten >>> to it. >>> >>> I guess I don't see what the problem would be... am I oversimplifying it >>> somehow? This has been in the back of my head for a while, and even >>> starting to put it on paper it looks fine for any purpose, even outside of >>> Dovecot. Obviously it'll be a complex query. Just write it out >>> logically first. If you're allowing only particular applications, you'll >>> have to make sure whatever doesn't have a password falls through to >>> 'password'.. Or, maybe have your 'app password' creation code just >>> ensure any apps without specific passwords have a copy of the 'password' >>> field... Or maybe have a boolean field to check if app specific passwords >>> are on and make that the first if() in the query checks that.... >>> >>> Rick >> >> That's not a bad solution, however I don't want it to be restricted to >> specific protocols. For example I have one application-specific password >> used on my phone, one on my laptop, one on my desktop and I can use it >> on multiple devices, so it's like an extra password. So that's where the >> issue lies. The only way I can think of is to prefix your username with >> an unique id to identify which password should be compared, however >> that's not practical nor a good solution in my opinion. >> > > Hello, > > maybe a stupid question, but why log queries? Just drop that log. > > Also, if I understand correctly Dovecot working scheme, it should hash > the password in the query directly if you remove the PLAIN mechanism? > > Another solution (and probably the best): Dovecot should provide another > variable than %w, like %W which will be the hashed password according to > the password schema defined in the configuration? > > Your idea is really interesting by the way. Was thinking about it for > some times now, never had the time to really try something? > > C. > The passwords looks like this in the database: $6$qwerty$wZZxE91RvJb4ETR0svmCb69rVCevicDV1Fw.Y9Qyg9idcZUioEoYmOzAv23wyEiNoyMLuBLGXPSQbd5ETanmq/ where 6 is the hashing method, qwerty is the salt and after the last $ is the hash. So it's impossible for the entered password to be hashed in the query since it needs to be hashed with the correct salt to yield the same hash. I could drop query logging, but it's useful for debugging errors in production as well as it is bad practice to encrypt the password in the query [1] in my opinion, because it leaves the application in clear-text. I rather not support application-specific passwords than having the password in clear-text in the query. [1] http://stackoverflow.com/questions/20295778/how-to-use-bcrypt-algorithm-within-encrypt-function-in-mysql-for-verifying-p From lukas.mika at web.de Thu Jul 24 09:59:22 2014 From: lukas.mika at web.de (Lukas Mika) Date: Thu, 24 Jul 2014 11:59:22 +0200 Subject: Problems with custom plugin Message-ID: <53D0D8FA.3070000@web.de> Hi everybody, I wrote a plugin for Dovecot 2.1.something which was based on the information found at http://wiki2.dovecot.org/Design/Storage/Plugins and by studying the mail_log plugin. My plugin can be found here: https://github.com/dim-0/dovecot-mbc It takes the notify plugin's information, that a new mailbox has been created (or an old one been renamed) in order to trigger a custom script (which in my case sets default ACLs for shared mailboxes). This plugin went quite well for a while, but then I recently upgraded Dovecot to version 2.2.9 and now I cannot build my plugin anymore. I get two error messages which both describe the same thing: src/mbc-plugin.c: In function ?mbc_mailbox_create?: /usr/include/dovecot/src/lib/module-context.h:46:67: error: ?struct mbc_user_module? has no member named ?reg? COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE(OBJ_REGISTER(obj), (id_ctx).reg) src/mbc-plugin.c: In function ?mbc_mail_user_created?: /usr/include/dovecot/src/lib/module-context.h:46:67: error: ?struct mbc_user_module? has no member named ?reg? COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE(OBJ_REGISTER(obj), (id_ctx).reg) Obviously the module context nowadays expects another attribute/struct named "reg". However, I cannot find any information about this within the documentation and plugin mentioned above. The only clue I have got yet is the definition in module-context.h: union STRUCT_NAME_module_context { struct STRUCT_NAME_module_register *reg; // it's allowed to have some structure here so it won't waste space. // for example: struct STRUCT_NAME_vfuncs super; }; However, I still cannot make any sense of it (yet). Could you please help me in filling the gap and understanding, what has to be changed? Thanks a lot in advance for an awesome piece of software and any input on this topic, Lukas From fc193 at hotmail.com Thu Jul 24 10:10:39 2014 From: fc193 at hotmail.com (Franck CALLEJA) Date: Thu, 24 Jul 2014 12:10:39 +0200 Subject: Sieve plugin (fc17 + sendmail + roundcube) In-Reply-To: References: , Message-ID: Hello, Here are the filtered extract from the log file as off 3rd July (the day I made the test), I should give another try if I have some progress on this thread. Jul 03 16:27:45 lda: Debug: Loading modules from directory: /usr/lib64/dovecot Jul 03 16:27:45 lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Jul 03 16:27:45 lda: Debug: auth input: fcalleja system_groups_user=fcalleja uid=500 gid=100 home=/home/fcalleja Jul 03 16:27:45 lda(fcalleja): Debug: Effective uid=500, gid=100, home=/home/fcalleja Jul 03 16:27:45 lda(fcalleja): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/fcalleja Jul 03 16:27:45 lda(fcalleja): Debug: fs: root=/home/fcalleja/mail, index=, control=, inbox=/var/spool/mail/fcalleja, alt= Jul 03 16:27:45 lda(fcalleja): Debug: none: root=, index=, control=, inbox=, alt= Jul 03 16:27:45 lda(fcalleja): Debug: Destination address: fcalleja at servfc.audis-consulting.fr (source: user at hostname) Jul 03 16:27:45 lda(fcalleja): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 03 16:27:45 lda(fcalleja): Debug: sieve: using the following location for user's Sieve script: /home/fcalleja/.dovecot.sieve Jul 03 16:27:45 lda(fcalleja): Debug: sieve: opening script /home/fcalleja/.dovecot.sieve Jul 03 16:27:45 lda(fcalleja): Debug: sieve: script `main script' from /home/fcalleja/.dovecot.sieve successfully compiled Jul 03 16:27:45 lda(fcalleja): Debug: sieve: executing script from /home/fcalleja/.dovecot.sieve Jul 03 16:27:45 lda(fcalleja): Info: sieve: msgid=: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=, and no additional `:addresses' are specified) Jul 03 16:27:45 lda(fcalleja): Info: sieve: msgid=: stored mail into mailbox 'INBOX' Jul 03 16:30:19 lda: Debug: Loading modules from directory: /usr/lib64/dovecot Jul 03 16:30:19 lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Jul 03 16:30:19 lda: Debug: auth input: fcalleja system_groups_user=fcalleja uid=500 gid=100 home=/home/fcalleja Jul 03 16:30:19 lda(fcalleja): Debug: Effective uid=500, gid=100, home=/home/fcalleja Jul 03 16:30:19 lda(fcalleja): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/fcalleja Jul 03 16:30:19 lda(fcalleja): Debug: fs: root=/home/fcalleja/mail, index=, control=, inbox=/var/spool/mail/fcalleja, alt= Jul 03 16:30:19 lda(fcalleja): Debug: none: root=, index=, control=, inbox=, alt= Jul 03 16:30:19 lda(fcalleja): Debug: Destination address: fcalleja at servfc.audis-consulting.fr (source: user at hostname) Jul 03 16:30:19 lda(fcalleja): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 03 16:30:19 lda(fcalleja): Debug: sieve: using the following location for user's Sieve script: /home/fcalleja/.dovecot.sieve Jul 03 16:30:19 lda(fcalleja): Debug: sieve: opening script /home/fcalleja/.dovecot.sieve Jul 03 16:30:19 lda(fcalleja): Debug: sieve: script binary /home/fcalleja/.dovecot.svbin is not up-to-date Jul 03 16:30:19 lda(fcalleja): Debug: sieve: script `main script' from /home/fcalleja/.dovecot.sieve successfully compiled Jul 03 16:30:19 lda(fcalleja): Debug: sieve: executing script from /home/fcalleja/.dovecot.sieve Jul 03 16:30:19 lda(fcalleja): Info: sieve: msgid=: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=, and no additional `:addresses' are specified) Jul 03 16:30:19 lda(fcalleja): Info: sieve: msgid=: stored mail into mailbox 'INBOX' Jul 03 16:31:21 lda: Debug: Loading modules from directory: /usr/lib64/dovecot Jul 03 16:31:21 lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Jul 03 16:31:21 lda: Debug: auth input: netw-fcalleja system_groups_user=netw-fcalleja uid=529 gid=100 home=/home/netw-fcalleja Jul 03 16:31:21 lda(netw-fcalleja): Debug: Effective uid=529, gid=100, home=/home/netw-fcalleja Jul 03 16:31:21 lda(netw-fcalleja): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/netw-fcalleja Jul 03 16:31:21 lda(netw-fcalleja): Debug: fs: root=/home/netw-fcalleja/mail, index=, control=, inbox=/var/spool/mail/netw-fcalleja, alt= Jul 03 16:31:21 lda(netw-fcalleja): Debug: none: root=, index=, control=, inbox=, alt= Jul 03 16:31:21 lda(netw-fcalleja): Debug: Destination address: netw-fcalleja at servfc.audis-consulting.fr (source: user at hostname) Jul 03 16:31:21 lda(netw-fcalleja): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 03 16:31:21 lda(netw-fcalleja): Debug: sieve: using the following location for user's Sieve script: /home/netw-fcalleja/.dovecot.sieve Jul 03 16:31:21 lda(netw-fcalleja): Debug: sieve: opening script /home/netw-fcalleja/.dovecot.sieve Jul 03 16:31:21 lda(netw-fcalleja): Debug: sieve: script `main script' from /home/netw-fcalleja/.dovecot.sieve successfully compiled Jul 03 16:31:21 lda(netw-fcalleja): Debug: sieve: executing script from /home/netw-fcalleja/.dovecot.sieve Jul 03 16:31:21 lda(netw-fcalleja): Info: sieve: msgid=: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=, and no additional `:addresses' are specified) Jul 03 16:31:21 lda(netw-fcalleja): Info: sieve: msgid=: stored mail into mailbox 'INBOX' Jul 03 16:31:46 lda: Debug: Loading modules from directory: /usr/lib64/dovecot Jul 03 16:31:46 lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Jul 03 16:31:46 lda: Debug: auth input: ygarot system_groups_user=ygarot uid=518 gid=100 home=/home/ygarot Jul 03 16:31:46 lda(ygarot): Debug: Effective uid=518, gid=100, home=/home/ygarot Jul 03 16:31:46 lda(ygarot): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/ygarot Jul 03 16:31:46 lda(ygarot): Debug: fs: root=/home/ygarot/mail, index=, control=, inbox=/var/spool/mail/ygarot, alt= Jul 03 16:31:46 lda(ygarot): Debug: none: root=, index=, control=, inbox=, alt= Jul 03 16:31:46 lda(ygarot): Debug: Destination address: ygarot at servfc.audis-consulting.fr (source: user at hostname) Jul 03 16:31:46 lda(ygarot): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 03 16:31:46 lda(ygarot): Debug: sieve: script file /home/ygarot/.dovecot.sieve not found Jul 03 16:31:46 lda(ygarot): Debug: sieve: user's script ~/.dovecot.sieve doesn't exist (using default script location instead) Jul 03 16:31:46 lda(ygarot): Debug: sieve: no default script configured for user Jul 03 16:31:46 lda(ygarot): Debug: sieve: user has no valid location for a personal script Jul 03 16:31:46 lda(ygarot): Debug: sieve: no scripts to execute: reverting to default delivery. Jul 03 16:31:46 lda(ygarot): Info: msgid=<002301cf96cb$7e79e940$7b6dbbc0$@groupe-a3a.com>: saved mail to INBOX Going through the users home directory I've noticed that the structure of the mail directory tree could be different using dovecot or procmail, no ? Look the tree extract of my user directory, some folders have been created the 3rd July : 2# tree -aD . ??? [Jul 22 13:03]? &AMk-l&AOk-ments\ envoy&AOk-s ??? [Dec 10? 2012]? &AMk-l&AOk-ments\ supprim&AOk-s ??? [Feb 13? 2013]? .AppleDouble ??? ??? [Dec 10? 2012]? &AMk-l&AOk-ments\ envoy&AOk-s ??? ??? [Dec 10? 2012]? &AMk-l&AOk-ments\ supprim&AOk-s ??? ??? [Dec 10? 2012]? AUDIS\ NETWORKING ??? ??? [Dec 10? 2012]? Brouillons ??? ??? [Dec 10? 2012]? Courrier\ ind&AOk-sirable ??? ??? [Dec 10? 2012]? Deleted\ Messages ??? ??? [Dec 10? 2012]? Drafts ??? ??? [Dec 10? 2012]? DRH\ Audis ??? ??? [Dec 13? 2012]? .imap ??? ??? ??? [Dec 13? 2012]? &AMk-l&AOk-ments\ envoy&AOk-s ??? ??? ??? ??? [Dec 13? 2012]? dovecot.index.log ??? ??? ??? [Dec 13? 2012]? &AMk-l&AOk-ments\ supprim&AOk-s ??? ??? ??? ??? [Dec 13? 2012]? dovecot.index.log ??? ??? ??? [Dec 13? 2012]? AUDIS\ NETWORKING ??? ??????? ??? [Dec 13? 2012]? dovecot.index.log ??? ??? [Dec 10? 2012]? Informatique\ Interne ??? ??? [Dec 10? 2012]? Log\ Watch ??? ??? [Dec 10? 2012]? Notes ??? ??? [Mar? 6 22:15]? .Parent ??? ??? [Dec 10? 2012]? Personnels ??? ??? [Dec 10? 2012]? Projet\ -\ Audit\ Informatique ??? ??? [Dec 10? 2012]? Projet\ -\ Forfaitisation ??? ??? [Dec 10? 2012]? Projet\ -\ The\ BOX ??? ??? [Dec 10? 2012]? Recrutement ??? ??? [Dec 10? 2012]? Sent\ Messages ??? ??? [Feb 13? 2013]? .subscriptions ??? ??? [Feb 13? 2013]? Trash ??? [Jul 18 16:05]? Brouillons ??? [Jul? 9? 9:18]? Courrier\ ind&AOk-sirable ??? [Jul? 3 16:55]? cur ??? [Jul? 9? 9:17]? Drafts ??? [Jul? 9? 9:18]? .imap ??? ??? [Jul 15? 9:49]? &AMk-l&AOk-ments\ envoy&AOk-s ??? ??? ??? [Jul? 9 12:37]? dovecot.index ??? ??? ??? [Jul 23 14:48]? dovecot.index.cache ??? ??? ??? [Jul 22 13:03]? dovecot.index.log ??? ??? [Jun? 5? 2012]? &AMk-l&AOk-ments\ supprim&AOk-s ??? ??? ??? [Dec? 1? 2011]? dovecot.index ??? ??? ??? [Dec 10? 2012]? dovecot.index.cache ??? ??? ??? [Jul? 2 16:47]? dovecot.index.log ??? ??? [Dec 10? 2012]? .AppleDouble ??? ??? ??? [Dec 10? 2012]? .Parent ??? ??? [Jul? 9 11:40]? Brouillons ??? ??? ??? [Jul? 9 11:40]? dovecot.index ??? ??? ??? [Jul 18 16:05]? dovecot.index.cache ??? ??? ??? [Jul 18 16:05]? dovecot.index.log ??? ??? [Jul? 6 13:15]? Courrier\ ind&AOk-sirable ??? ??? ??? [Jul? 3 14:48]? dovecot.index ??? ??? ??? [Jul? 9? 9:18]? dovecot.index.cache ??? ??? ??? [Jul? 9? 9:18]? dovecot.index.log ??? ??? [Jul? 9? 9:17]? dovecot.mailbox.log ??? ??? [Jul? 9? 9:18]? dovecot-uidvalidity ??? ??? [Jul? 2 17:14]? dovecot-uidvalidity.53b421ef ??? ??? [Jul? 9? 9:18]? Drafts ??? ??? ??? [Jul? 9 11:12]? dovecot.index.log ??? ??? [Jul 15? 9:49]? INBOX ??? ??? ??? [Jul 23 17:43]? dovecot.index ??? ??? ??? [Jul 24? 9:36]? dovecot.index.cache ??? ??? ??? [Jul 24? 9:36]? dovecot.index.log ??? ??? [Jul? 9? 9:18]? Sent ??? ??? ??? [Jul? 9 11:12]? dovecot.index.log ??? ??? [Jul 15? 9:49]? Trash ??????? ??? [Jul? 9 10:27]? dovecot.index ??????? ??? [Jul? 9 10:27]? dovecot.index.cache ??????? ??? [Jul? 9 10:27]? dovecot.index.log ??? [Jul? 6 13:15]? new ??? ??? [Jul? 3 16:55]? 1404399347.6970_0.servfc.audis-consulting.fr ??? ??? [Jul? 3 17:05]? 1404399952.7428_0.servfc.audis-consulting.fr ??? ??? [Jul? 3 17:12]? 1404400377.7638_0.servfc.audis-consulting.fr ??? ??? [Jul? 6 13:15]? .imap ??????? ??? [Jul? 6 13:15]? 1404399347.6970_0.servfc.audis-consulting.fr ??????? ??? ??? [Jul? 9? 9:20]? dovecot.index.log ??????? ??? [Jul? 6 13:15]? 1404399952.7428_0.servfc.audis-consulting.fr ??????? ??? ??? [Jul? 7? 9:54]? dovecot.index.log ??????? ??? [Jul? 6 13:15]? 1404400377.7638_0.servfc.audis-consulting.fr ??????????? ??? [Jul? 7? 9:54]? dovecot.index.log ??? [Jul? 9? 9:17]? Sent ??? [Jul? 9? 9:17]? .subscriptions ??? [Jul? 3 17:12]? tmp ??? [Jul? 9 10:27]? Trash ?Regards Franck. > > What are the log messages from the Dovecot LDA? Maybe, add mail_debug=yes > > - -- > Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > What are the log messages from the Dovecot LDA? Maybe, add mail_debug=yes > > - -- > Steffen Kaiser From skdovecot at smail.inf.fh-brs.de Thu Jul 24 10:20:54 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 24 Jul 2014 12:20:54 +0200 (CEST) Subject: Sieve plugin (fc17 + sendmail + roundcube) In-Reply-To: References: , Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 24 Jul 2014, Franck CALLEJA wrote: > Jul 03 16:27:45 lda(fcalleja): Debug: sieve: executing script from /home/fcalleja/.dovecot.sieve You see: Sieve is active. > Jul > 03 16:27:45 lda(fcalleja): Info: sieve: > msgid=: > discarding vacation response for implicitly delivered message; no known > (envelope) recipient address found in message headers > (recipient=, and no > additional `:addresses' are specified) Here you see the error, why no vacation notification is sent: You do not have no :addresses specified. See: http://tools.ietf.org/html/rfc5230#section-4.8 - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9DeBnz1H7kL/d9rAQLdiggAsxk5wanmWw0Ce5znX+FyldZYls9dspwo efugreLGyhmQOzm+Lt/RzCL5f9CG1nOukmRuhVpQWsuPYXecgMimoZHcwLL5KA+q pTiPHfHTZS0mofvq+uvAlJ67aVMz/q8bJgFSqcIYdV/qNzlbQ1VdhNpsYw9It68M JeSpYUnvVzCYj3l7Bxgm46co+0E4dJyN20vj1D6RyveqseHg3jZmEbaY/AiX2ubk xAgscZckiOcD4G8Uwtu8VSV3QhhU+KexTrA/SEQC8PWaQZZS73H96AKKPdD7USwT J4A1FDlpdVr76hFeWXZTzjXaLOFLKLlU8OZk3RNc8HJ/Aq4el7oucw== =TemN -----END PGP SIGNATURE----- From django at nausch.org Thu Jul 24 10:40:30 2014 From: django at nausch.org (Django [BOfH]) Date: Thu, 24 Jul 2014 12:40:30 +0200 Subject: doveconf option "-e" Message-ID: <53D0E29E.1060005@nausch.org> Hi Timo, If I could tell you a little smart wish, I've one for you. ;) Today I'm writing my own configurationdocumentation 'bout Dovecot in my dokuwiki and for documentation purposes I changing some options several times a day. Postfix supports on its own postconf an option -e. So I can set up mostly every configuration-option on the fly. Dovecot's doveconf has no such option. So, I changed the configuration-files and reload my dovecot-daemon. It were grait if doveconf has a similar function, like postconf's option "-e". Maybe you can make a little update to doveconf in one of the upcomming releases? ;) Best regards Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django From h.reindl at thelounge.net Thu Jul 24 10:46:14 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 24 Jul 2014 12:46:14 +0200 Subject: Sieve plugin (fc17 + sendmail + roundcube) In-Reply-To: References: Message-ID: <53D0E3F6.7020100@thelounge.net> > The mail server is running fine since 5 years > I've recently installed pigeonhole for fc17 are you aware that Fedora 17 is EOL long ago? the currently last supported version is F19 i will never understand why people using a bleeding edge distribution if they can't cope with updates and ignore security completly P.S.: that said while all my servers are on Fedora for years -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From eduardo at freedominterface.org Thu Jul 24 12:01:33 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Thu, 24 Jul 2014 09:01:33 -0300 Subject: Multiple servers and NFS In-Reply-To: <53D035D8.9080905@walnut.gen.nz> References: <53D035D8.9080905@walnut.gen.nz> Message-ID: <53D0F59D.1030606@freedominterface.org> Hi Richard, You can use one or more instances of Dovecot on the same machine, as you can see here (http://wiki2.dovecot.org/RunningDovecot) "Running Multiple Invocations of Dovecot". The problem with DNS round-robind is that if you server goes down, DNS continues resolving for it. I would recommend use some balancer like LVS+keepalived. Consider that multi layer solution: -------------------- -------------------- | LVS + keepalived | | LVS + keepalived | -------------------- -------------------- | | -------------- -------------- | Director 1 | | Director 2 | -------------- -------------- | | ----------------- ----------------- | IMAP/POP/LMTP | | IMAP/POP/LMTP | | Backend | | Backend | ----------------- ----------------- \ / \ / \ ------------ / -------| NetAPP |--------- ------------ Remember, directors and backends could run on the same machine. I have a lab running that way. Maybe I can help you deploy. On 07/23/2014 07:23 PM, Richard Hector wrote: > Hi all, > > For some reason, I didn't go to http://wiki2.dovecot.org/NFS until > now, and I'm starting to get worried ... > > The plan was to have multple servers (MXes) receiving mail, and > delivering via LMTP to multiple backend dovecot servers (with amavis > in front of dovecot; LMTP both sides). Then we'd have multiple servers > for clients to use IMAP or POP3. > > This is more or less how the system already works, except with Courier > IMAP, and postfix on the backends, delivering to maildirs with procmail. > > But with the recommendation to use the Director for both IMAP/POP3 and > LMTP - that starts to sound like I need a whole bunch more servers to > run Directors and proxies, and even then it might not be a good idea > to have different servers running lmtp and imap/pop. > > One possible mitigating point is that our 'load balancing' is DNS > round-robin, so a given client will probably stick with a single > imap/pop server anyway, but if the user has multiple clients > (desktop/mobile etc) then they may still hit different servers. > > Can someone clarify best practice for a setup needing multiple servers > for load balancing and redundancy? > > Is Courier already likely to have been suffering these problems? > > Oh, the NFS server is a NetApp Filer, if that matters. > > I'm using dovecot 2.2.9 from debian wheezy backports, in order to get > the quota policy daemon support. > > Thanks, > Richard From stephan at rename-it.nl Thu Jul 24 12:44:27 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Thu, 24 Jul 2014 14:44:27 +0200 Subject: Pigeonhole Sieve LDAP support Message-ID: <53D0FFAB.4090309@rename-it.nl> Hi, Yesterday, I committed two important and rather big changes to the Pigeonhole repository. The first creates a generic interface for implementing Sieve script storages. It was already possible to some extent to read Sieve scripts from other sources than the local filesystem, such as Dovecot dict, but that was still pretty limited, as it was not possible to do this with sieve_before/sieve_after. This is now supported. But, more importantly, ManageSieve did not support storing Sieve scripts on locations other than the local filesystem. Now, alternatives can be implemented. Still, I haven't actually implemented write access to a storage other than the local filesystem yet, but now this would be much easier to achieve. The second creates an LDAP script storage implementation. Much like the dict storage, it is still read-only. It can be compiled directly into the Sieve interpreter, and, alternatively, it can also be compiled as a plugin called sieve_storage_ldap. I've updated the documentation in the sources. For all Xi repository users: I added compilation of LDAP storage as a plugin. Read the INSTALL files and other files referenced therein for more information about how to use the plugin. The plugin is installed as part of the dovecot-ldap package. This is a rather big change, but it should all be backwards compatible in terms of configuration. If you have problems (I heard about one so far), please don't hesitate to notify me. Regards, Stephan. From fc193 at hotmail.com Thu Jul 24 13:55:14 2014 From: fc193 at hotmail.com (Franck CALLEJA) Date: Thu, 24 Jul 2014 15:55:14 +0200 Subject: Sieve plugin (fc17 + sendmail + roundcube) In-Reply-To: References: , , , , Message-ID: Hello I'm confused, this is effectively not a correct mail address, the "servfc" keyword shouldn't be in the address?? : (recipient=, But, I can't find anywhere in dovecot, sendmail, roundcube or client mail where this could be misconfigured (I searched 'localhost' in all confs to see if it was specified elsewhere than in a "host" like parameter without success. This name is effectively precised in /etc/hosts file. Regards. Franck. >> Jul >> 03 16:27:45 lda(fcalleja): Info: sieve: >> msgid=: >> discarding vacation response for implicitly delivered message; no known >> (envelope) recipient address found in message headers >> (recipient=, and no >> additional `:addresses' are specified) > From eagle.base at gmx.net Thu Jul 24 14:01:26 2014 From: eagle.base at gmx.net (Andre Dietrich) Date: Thu, 24 Jul 2014 16:01:26 +0200 Subject: IMAP forward boxes Message-ID: <53D111B6.8000104@gmx.net> Hi all, since a few weeks I'm experimenting with some "IMAP forward boxes", but I didn't find a satisfactory solution yet. Target function is a directory structure like following in a shared mailbox: /intern/users/fred /intern/users/ted /intern/users/alice The idea is, that a mail, moved to the directory "/intern/users/fred" via IMAP-client will be forwarded to "fred at test.domain" without modifying the mail (except the header line "delivered to:"). So if you get a mail in your inbox and want fred to answer it, you drag'n'drop it to /intern/users/fred. Fred gets the mail in his inbox and can answer it. To share all inboxes, to drop mails directly to them, is not an option, because I don't want everybody to see all other inboxes mails. Only to apply "-w-" ACL rights isn't an option either, because it seems to irritate the mail clients. Some month ago I had a partially working solution using a cron bash script. The script read the mails in the cur and new folders, processed the folders path and passed it to sendmail. It's ok, but it has to run quite often to get an adequate forwarding time and on sendmail errors mails got lost without any notification. It would be nice to have a dot-forward file in this subfolder (like in the qmail mailbox root), which is processed by dovecot when a mail is dropped in. Is it possible to solve this with a sieve script, a dot-forward file, or something similar ? I'm grateful for all solutions / ideas ! thx! Andre From dave at icdsoft.com Thu Jul 24 14:30:38 2014 From: dave at icdsoft.com (David Davidov) Date: Thu, 24 Jul 2014 17:30:38 +0300 Subject: After upgrade from 2.1 to 2.2.13 clients can create folders with names containing slash character on a Linux system Message-ID: <53D1188E.6070303@icdsoft.com> We have following issue: After upgrade from 2.1 to 2.2.13 clients can create folders with names containing slash character. This was not possible with our previous version 2.1. Tested. Our Dovecot runs on Debian Wheezy system. According http://wiki2.dovecot.org/Plugins/Listescape this should be disabled on a Posix system. We use the usual separator '.' as you can see in the config file later. Issue can be reproduced using outlook 2013. On the file system this is the representation of the "Family/Friends" folder /home/vpopmail/domains/0/example.org/steve/Maildir/.Family/Friends /home/vpopmail/domains/0/example.org/steve/Maildir/.Family/Friends/new /home/vpopmail/domains/0/example.org/steve/Maildir/.Family/Friends/tmp /home/vpopmail/domains/0/example.org/steve/Maildir/.Family/Friends/cur Doveadm does not lists properly the folder doveadm mailbox list -usteve at alltimes.com |grep -i Family INBOX.Family This is the server configuration: ----------------------- dovecot -n # 2.2.13: /dovecot/etc/dovecot/dovecot.conf # OS: Linux 3.2.59-grsec x86_64 Debian 7.6 auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890@!#$&\'*+=?^_`{|}~.-" base_dir = /var/run/dovecot/ disable_plaintext_auth = no listen = * login_log_format_elements = user=<%u> method=%m rip=%r lip=%l pid=%p %c mail_access_groups = vchkpw mail_fsync = never mail_plugins = quota stats namespace { inbox = yes location = maildir:~/Maildir:INDEX=/home/vpopmail/dovecot-indexes/%d/%n prefix = INBOX. separator = . type = private } passdb { args = /home/vpopmail/bin/chkpw driver = checkpassword } plugin { acl = vfile:/dovecot/acls quota = maildir quota_rule = INBOX.Trash:ignore stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 64 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours } protocols = imap pop3 service imap-login { executable = /dovecot/libexec/dovecot/imap-login inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_min_avail = 16 service_count = 0 } service imap { executable = /dovecot/libexec/dovecot/imap-ld-hack process_limit = 1500 vsz_limit = 256 M } service pop3-login { process_min_avail = 16 service_count = 0 } service pop3 { executable = /dovecot/libexec/dovecot/pop3-ld-hack process_limit = 1500 vsz_limit = 256 M } service stats { fifo_listener stats-mail { mode = 0600 user = vpopmail } } ssl_ca = References: , , , , Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 24 Jul 2014, Franck CALLEJA wrote: > I'm confused, this is effectively not a correct mail address, the "servfc" keyword shouldn't be in the address?? : > > (recipient=, > > But, I can't find anywhere in dovecot, sendmail, roundcube or client mail where this could be misconfigured (I searched 'localhost' in all confs to see if it was specified elsewhere than in a "host" like parameter without success. > > This name is effectively precised in /etc/hosts file. You mean, it's the hostname? You can test the rewriting, IMHO, with: sendmail -bt 3,0,4 fcalleja at audis-consulting.fr # Display sendmail's hostname $j >>> Jul >>> 03 16:27:45 lda(fcalleja): Info: sieve: >>> msgid=: >>> discarding vacation response for implicitly delivered message; no known >>> (envelope) recipient address found in message headers >>> (recipient=, and no >>> additional `:addresses' are specified) >> > > > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9EbO3z1H7kL/d9rAQK0Wwf/c9eC6/z9MEbES03dlbLs2z0GKZ051qOH 7msRUUIEIjzLv0Axnzr9/Uyw2qWAt2ofD16aEetq9tUIyIVg4FVvHKj3hzhoOKo5 lXeWq0Q8ceg7HBAmiMCCOi9dvALoh6Mp7Qy4mEGTKT/36JHo88MN0PEfYrdBHZY6 CaWKTH87jv5Zutm6X0l3EisfoRdqPrdSzk2Z5UJ8uX08gaX4q/MPFiTFyndamVgg 2Ui4zCYCS6LO9q7/KTd/sxylDvW7y6jIwfN26cqnez83M6RTKU6EtDSF797MEJh5 TMmfuyQoZ0wkd/ooLqCgNAXpoihnYjNkjN3U7HkiP8b7N7gawbgZlw== =H5wl -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Thu Jul 24 14:48:43 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 24 Jul 2014 16:48:43 +0200 (CEST) Subject: Sieve plugin (fc17 + sendmail + roundcube) In-Reply-To: References: , , , , Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 24 Jul 2014, Steffen Kaiser wrote: > On Thu, 24 Jul 2014, Franck CALLEJA wrote: > >> I'm confused, this is effectively not a correct mail address, the "servfc" >> keyword shouldn't be in the address?? : >> >> (recipient=, >> >> But, I can't find anywhere in dovecot, sendmail, roundcube or client mail >> where this could be misconfigured (I searched 'localhost' in all confs to >> see if it was specified elsewhere than in a "host" like parameter without >> success. >> >> This name is effectively precised in /etc/hosts file. > > You mean, it's the hostname? > > You can test the rewriting, IMHO, with: > > sendmail -bt > 3,0,4 fcalleja at audis-consulting.fr > # Display sendmail's hostname > $j sendmail -bv fcalleja at audis-consulting.fr BTW: Maybe it's "always_add_domain": "Include the local host domain even on locally delivered mail. Normally it is not added on unqualified names. However, if you use a shared message store but do not use the same user name space everywhere, you may need the host name on local names. An optional argument specifies another domain to be added than the local. " >>>> Jul >>>> 03 16:27:45 lda(fcalleja): Info: sieve: >>>> msgid=: >>>> discarding vacation response for implicitly delivered message; no known >>>> (envelope) recipient address found in message headers >>>> (recipient=, and no >>>> additional `:addresses' are specified) - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9Ecy3z1H7kL/d9rAQISqgf9F0oLEryV9yHLTYSH8hSZZ7aGgaNOc8hk 63NNK5zEyYZQHhtX9SIQmhE+AUVNtlTkW9MHsFBSJ7C0jYbsBjNGi+m98MrxfLNY kef/QvBArq0vhIyC3woqsz4g6X1pblg939rMGatuI6WjSp+oX3mntrVylkVSqJzi sYlEMRVvAX3P7d8lNfB2FnlSMGK9wlfe0JGAh7+9afv3roxtwNYXEFwNypf7u4Rx c5+YpFL9V3i5iEKIkyZEQ76iVuJ1kl0ycgY1Q/RL3yHLr8e1jGYycDYzYNQVxqW2 Kr7HkkapUsziSem8C6i8mMSOQ40BfHsYuHSAENUZxrZ5ieUiFivoYw== =d6as -----END PGP SIGNATURE----- From nathan at schultheiss.fr Thu Jul 24 17:09:07 2014 From: nathan at schultheiss.fr (Nathan Schultheiss) Date: Thu, 24 Jul 2014 19:09:07 +0200 (CEST) Subject: Multiple servers and NFS In-Reply-To: <53D0F59D.1030606@freedominterface.org> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> Message-ID: <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> Hi Eduardo, Since I few day I try to setup this config 2, but I've really problem with the NFS. We come from Google Apps :) I several people on the hospital have large mailbox. For example 96000 mails in the INBOX folder, when I do "ls" that is quick for display mail, but with dovecot... I need wait 1 minuts the first time and after display the amount of mail it's quick. We don't have NetAPP, we've Dell Equallogic with SATA2 7200rpm, gigabits ports. The Equallogic it's just for store email, and index file. My config: Dell Equallogic |-> VMWare ESXI (iscsi mount in VMware with VMWare VMFS 5 format 4To) |--> Mounted as slave disk on a VM Ubuntu and exported with this options "(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async)" and formated as ReiserFS (I've read it's the best for many small files). |---> My 2 Dovecot Backend mount the NFS (fstab) to my previous VM with this options "nfs defaults 0 0" |----> Mail it's stored in MailDir format "mail_location = maildir:%h" When I go on Roundcube with a mailbox who I've 96000 in the INBOX "cur" folder, the first time I need 1 minutes waiting. The second time it's a little more quick 10 seconds... But when I go back again (after a few hours) it's slow again... And we'are just 5 users at the moment for test... I've not setup director for the moment I try first dovecot on my lab befor add director and move mailbox from Google... Have you recommandation for tune or make NFS more quickly, because with Google it's really fast (ok it's google) but if we move to a more slow system, the user on the hospital would no be happy. I've try many config, but no really success for have a fast NFS, I don't know if the problem it's VMWARE or if the problem it's just my NFS options. I'm not pettry good with linux, I'm most good with Windows server, I'm not a good man Google, Microsoft, I know it's devil for every linux sysadmin :) Thanks, Nathan ----- Mail original ----- De: "Eduardo Ramos" ?: dovecot at dovecot.org Envoy?: Jeudi 24 Juillet 2014 14:01:33 Objet: Re: Multiple servers and NFS Hi Richard, You can use one or more instances of Dovecot on the same machine, as you can see here (http://wiki2.dovecot.org/RunningDovecot) "Running Multiple Invocations of Dovecot". The problem with DNS round-robind is that if you server goes down, DNS continues resolving for it. I would recommend use some balancer like LVS+keepalived. Consider that multi layer solution: -------------------- -------------------- | LVS + keepalived | | LVS + keepalived | -------------------- -------------------- | | -------------- -------------- | Director 1 | | Director 2 | -------------- -------------- | | ----------------- ----------------- | IMAP/POP/LMTP | | IMAP/POP/LMTP | | Backend | | Backend | ----------------- ----------------- \ / \ / \ ------------ / -------| NetAPP |--------- ------------ Remember, directors and backends could run on the same machine. I have a lab running that way. Maybe I can help you deploy. On 07/23/2014 07:23 PM, Richard Hector wrote: > Hi all, > > For some reason, I didn't go to http://wiki2.dovecot.org/NFS until > now, and I'm starting to get worried ... > > The plan was to have multple servers (MXes) receiving mail, and > delivering via LMTP to multiple backend dovecot servers (with amavis > in front of dovecot; LMTP both sides). Then we'd have multiple servers > for clients to use IMAP or POP3. > > This is more or less how the system already works, except with Courier > IMAP, and postfix on the backends, delivering to maildirs with procmail. > > But with the recommendation to use the Director for both IMAP/POP3 and > LMTP - that starts to sound like I need a whole bunch more servers to > run Directors and proxies, and even then it might not be a good idea > to have different servers running lmtp and imap/pop. > > One possible mitigating point is that our 'load balancing' is DNS > round-robin, so a given client will probably stick with a single > imap/pop server anyway, but if the user has multiple clients > (desktop/mobile etc) then they may still hit different servers. > > Can someone clarify best practice for a setup needing multiple servers > for load balancing and redundancy? > > Is Courier already likely to have been suffering these problems? > > Oh, the NFS server is a NetApp Filer, if that matters. > > I'm using dovecot 2.2.9 from debian wheezy backports, in order to get > the quota policy daemon support. > > Thanks, > Richard From eduardo at freedominterface.org Thu Jul 24 17:27:50 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Thu, 24 Jul 2014 14:27:50 -0300 Subject: Multiple servers and NFS In-Reply-To: <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> Message-ID: <53D14216.8080703@freedominterface.org> Hi Nathan! I think you can consider about your index files. By default dovecot stores index files in mailbox, but you can define another location. Local disk could be better choice. Take I look at this: http://wiki2.dovecot.org/MailLocation http://wiki2.dovecot.org/MailLocation/SharedDisk http://wiki2.dovecot.org/IndexFiles I think it will help you. On 07/24/2014 02:09 PM, Nathan Schultheiss wrote: > Hi Eduardo, > > Since I few day I try to setup this config 2, but I've really problem with the NFS. > > We come from Google Apps :) I several people on the hospital have large mailbox. > For example 96000 mails in the INBOX folder, when I do "ls" that is quick for display mail, but with dovecot... I need wait 1 minuts the first time and after display the amount of mail it's quick. > > We don't have NetAPP, we've Dell Equallogic with SATA2 7200rpm, gigabits ports. > The Equallogic it's just for store email, and index file. > > My config: > > Dell Equallogic > |-> VMWare ESXI (iscsi mount in VMware with VMWare VMFS 5 format 4To) > |--> Mounted as slave disk on a VM Ubuntu and exported with this options "(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async)" and formated as ReiserFS (I've read it's the best for many small files). > |---> My 2 Dovecot Backend mount the NFS (fstab) to my previous VM with this options "nfs defaults 0 0" > |----> Mail it's stored in MailDir format "mail_location = maildir:%h" > > When I go on Roundcube with a mailbox who I've 96000 in the INBOX "cur" folder, the first time I need 1 minutes waiting. > The second time it's a little more quick 10 seconds... But when I go back again (after a few hours) it's slow again... And we'are just 5 users at the moment for test... > > I've not setup director for the moment I try first dovecot on my lab befor add director and move mailbox from Google... > > Have you recommandation for tune or make NFS more quickly, because with Google it's really fast (ok it's google) but if we move to a more slow system, the user on the hospital would no be happy. > I've try many config, but no really success for have a fast NFS, I don't know if the problem it's VMWARE or if the problem it's just my NFS options. > > I'm not pettry good with linux, I'm most good with Windows server, I'm not a good man Google, Microsoft, I know it's devil for every linux sysadmin :) > > Thanks, > Nathan > > ----- Mail original ----- > De: "Eduardo Ramos" > ?: dovecot at dovecot.org > Envoy?: Jeudi 24 Juillet 2014 14:01:33 > Objet: Re: Multiple servers and NFS > > Hi Richard, > > You can use one or more instances of Dovecot on the same machine, as you > can see here (http://wiki2.dovecot.org/RunningDovecot) "Running Multiple > Invocations of Dovecot". > > The problem with DNS round-robind is that if you server goes down, DNS > continues resolving for it. I would recommend use some balancer like > LVS+keepalived. > > Consider that multi layer solution: > -------------------- -------------------- > | LVS + keepalived | | LVS + keepalived | > -------------------- -------------------- > | | > -------------- -------------- > | Director 1 | | Director 2 | > -------------- -------------- > | | > ----------------- ----------------- > | IMAP/POP/LMTP | | IMAP/POP/LMTP | > | Backend | | Backend | > ----------------- ----------------- > \ / > \ / > \ ------------ / > -------| NetAPP |--------- > ------------ > > Remember, directors and backends could run on the same machine. I have a > lab running that way. Maybe I can help you deploy. > On 07/23/2014 07:23 PM, Richard Hector wrote: >> Hi all, >> >> For some reason, I didn't go to http://wiki2.dovecot.org/NFS until >> now, and I'm starting to get worried ... >> >> The plan was to have multple servers (MXes) receiving mail, and >> delivering via LMTP to multiple backend dovecot servers (with amavis >> in front of dovecot; LMTP both sides). Then we'd have multiple servers >> for clients to use IMAP or POP3. >> >> This is more or less how the system already works, except with Courier >> IMAP, and postfix on the backends, delivering to maildirs with procmail. >> >> But with the recommendation to use the Director for both IMAP/POP3 and >> LMTP - that starts to sound like I need a whole bunch more servers to >> run Directors and proxies, and even then it might not be a good idea >> to have different servers running lmtp and imap/pop. >> >> One possible mitigating point is that our 'load balancing' is DNS >> round-robin, so a given client will probably stick with a single >> imap/pop server anyway, but if the user has multiple clients >> (desktop/mobile etc) then they may still hit different servers. >> >> Can someone clarify best practice for a setup needing multiple servers >> for load balancing and redundancy? >> >> Is Courier already likely to have been suffering these problems? >> >> Oh, the NFS server is a NetApp Filer, if that matters. >> >> I'm using dovecot 2.2.9 from debian wheezy backports, in order to get >> the quota policy daemon support. >> >> Thanks, >> Richard From pw at wk-serv.de Thu Jul 24 17:56:26 2014 From: pw at wk-serv.de (Patrick Westenberg) Date: Thu, 24 Jul 2014 19:56:26 +0200 Subject: Multiple servers and NFS In-Reply-To: <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> Message-ID: <53D148CA.4000503@wk-serv.de> Nathan Schultheiss schrieb: > My config: > > Dell Equallogic > |-> VMWare ESXI (iscsi mount in VMware with VMWare VMFS 5 format 4To) > |--> Mounted as slave disk on a VM Ubuntu and exported with this options "(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async)" and formated as ReiserFS (I've read it's the best for many small files). > |---> My 2 Dovecot Backend mount the NFS (fstab) to my previous VM with this options "nfs defaults 0 0" > |----> Mail it's stored in MailDir format "mail_location = maildir:%h" I don't understand your setup esp. that your backend servers mount something from the "previous VM"? Patrick From nathan at schultheiss.fr Thu Jul 24 20:00:50 2014 From: nathan at schultheiss.fr (Nathan Schultheiss) Date: Thu, 24 Jul 2014 22:00:50 +0200 (CEST) Subject: Multiple servers and NFS In-Reply-To: <53D148CA.4000503@wk-serv.de> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> <53D148CA.4000503@wk-serv.de> Message-ID: <1945577290.551213.1406232050315.JavaMail.zimbra@schultheiss.fr> Hallo Patrick, I've a Dell Equallogic, I make one "volume" with 4 To capacity. This volume have a iscsi key, I had this key to VMWare for link VMware with this "volume". After on VMware I format this volume with the VMFS5 format, VMware add it "Datastore2". I make a first VM (storage VM) with 2 Hard Drive: First Hardrive (located in Datastore1) with 20Go capacity, I setup on it the ubuntu system. Second Hardrive (located in Datastore2) with 4To capacity, That's my slave hard drive formated in ReiserFS and mounted has /home/vmail I setup nfs-server service with this options in my "export" file (rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async), the /home/vmail it's the export point. I setup now 2 new VM (Dovecot Backend) with just one local Hard Drive (20Go). After the setup, I install nfs-client and mount /home/vmail to my "storage VMAIL". Dovecot would store mail in /home/vmail/user I've just 1 domain, it's why I store direct in user directore (ex: /home/vmail/nathan.schultheiss ). The storage VM it's here because I can't mount the ISCSI session on the 2 Backend server. I mount this "volume" first on VMWare because it's more easy for manage it and setup it on a Virtual Server (my storage server in this case). It's not impossible that I make a total wrong archi... But I've think, easy, I mount the ISCSI session on my 2 backend in /home/vmail, that work for 1 but not for the second, and I receive many error. I think Equallogic don't like that 2 Virtual Server wrote on the same time to the same ISCSI session. Freundliche Gr??e aus Frankreich, Nathan ----- Mail original ----- De: "Patrick Westenberg" ?: dovecot at dovecot.org Envoy?: Jeudi 24 Juillet 2014 19:56:26 Objet: Re: Multiple servers and NFS Nathan Schultheiss schrieb: > My config: > > Dell Equallogic > |-> VMWare ESXI (iscsi mount in VMware with VMWare VMFS 5 format 4To) > |--> Mounted as slave disk on a VM Ubuntu and exported with this options "(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async)" and formated as ReiserFS (I've read it's the best for many small files). > |---> My 2 Dovecot Backend mount the NFS (fstab) to my previous VM with this options "nfs defaults 0 0" > |----> Mail it's stored in MailDir format "mail_location = maildir:%h" I don't understand your setup esp. that your backend servers mount something from the "previous VM"? Patrick From nathan at schultheiss.fr Thu Jul 24 20:09:33 2014 From: nathan at schultheiss.fr (Nathan Schultheiss) Date: Thu, 24 Jul 2014 22:09:33 +0200 (CEST) Subject: Multiple servers and NFS In-Reply-To: <53D14216.8080703@freedominterface.org> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> <53D14216.8080703@freedominterface.org> Message-ID: <71065138.551247.1406232573123.JavaMail.zimbra@schultheiss.fr> Hello Eduardo, Thank for your reply. 2 days ago I've try to setup the "INDEX" and "CONTROL" file on my local Harddrive (outside the NFS who the maildir it's stored). That was my config line: maildir:%h:INDEX=/opt/dovecot/indexes/%u:CONTROL=/opt/dovecot/indexes/%u But that was allway slow on the first access, I've think the "cache" expire after 1h for example and Dovecot need make a new "cache" after and that's the reason why the first access need 60 sec. and the next access need just 10 sec. I've read the dovecot doku, she's really more clear that postfix doku... really :) It's easy to read it and understand the doc because we learn step by step and when we're in one step we learn everything about it and don't need to go in another section and come back again for finish the step... Now I think my config (NFS mount/options) it's just a little poor and that's the reason why it's slow. Bests Regards, Nathan ----- Mail original ----- De: "Eduardo Ramos" ?: dovecot at dovecot.org Envoy?: Jeudi 24 Juillet 2014 19:27:50 Objet: Re: Multiple servers and NFS Hi Nathan! I think you can consider about your index files. By default dovecot stores index files in mailbox, but you can define another location. Local disk could be better choice. Take I look at this: http://wiki2.dovecot.org/MailLocation http://wiki2.dovecot.org/MailLocation/SharedDisk http://wiki2.dovecot.org/IndexFiles I think it will help you. On 07/24/2014 02:09 PM, Nathan Schultheiss wrote: > Hi Eduardo, > > Since I few day I try to setup this config 2, but I've really problem with the NFS. > > We come from Google Apps :) I several people on the hospital have large mailbox. > For example 96000 mails in the INBOX folder, when I do "ls" that is quick for display mail, but with dovecot... I need wait 1 minuts the first time and after display the amount of mail it's quick. > > We don't have NetAPP, we've Dell Equallogic with SATA2 7200rpm, gigabits ports. > The Equallogic it's just for store email, and index file. > > My config: > > Dell Equallogic > |-> VMWare ESXI (iscsi mount in VMware with VMWare VMFS 5 format 4To) > |--> Mounted as slave disk on a VM Ubuntu and exported with this options "(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async)" and formated as ReiserFS (I've read it's the best for many small files). > |---> My 2 Dovecot Backend mount the NFS (fstab) to my previous VM with this options "nfs defaults 0 0" > |----> Mail it's stored in MailDir format "mail_location = maildir:%h" > > When I go on Roundcube with a mailbox who I've 96000 in the INBOX "cur" folder, the first time I need 1 minutes waiting. > The second time it's a little more quick 10 seconds... But when I go back again (after a few hours) it's slow again... And we'are just 5 users at the moment for test... > > I've not setup director for the moment I try first dovecot on my lab befor add director and move mailbox from Google... > > Have you recommandation for tune or make NFS more quickly, because with Google it's really fast (ok it's google) but if we move to a more slow system, the user on the hospital would no be happy. > I've try many config, but no really success for have a fast NFS, I don't know if the problem it's VMWARE or if the problem it's just my NFS options. > > I'm not pettry good with linux, I'm most good with Windows server, I'm not a good man Google, Microsoft, I know it's devil for every linux sysadmin :) > > Thanks, > Nathan > > ----- Mail original ----- > De: "Eduardo Ramos" > ?: dovecot at dovecot.org > Envoy?: Jeudi 24 Juillet 2014 14:01:33 > Objet: Re: Multiple servers and NFS > > Hi Richard, > > You can use one or more instances of Dovecot on the same machine, as you > can see here (http://wiki2.dovecot.org/RunningDovecot) "Running Multiple > Invocations of Dovecot". > > The problem with DNS round-robind is that if you server goes down, DNS > continues resolving for it. I would recommend use some balancer like > LVS+keepalived. > > Consider that multi layer solution: > -------------------- -------------------- > | LVS + keepalived | | LVS + keepalived | > -------------------- -------------------- > | | > -------------- -------------- > | Director 1 | | Director 2 | > -------------- -------------- > | | > ----------------- ----------------- > | IMAP/POP/LMTP | | IMAP/POP/LMTP | > | Backend | | Backend | > ----------------- ----------------- > \ / > \ / > \ ------------ / > -------| NetAPP |--------- > ------------ > > Remember, directors and backends could run on the same machine. I have a > lab running that way. Maybe I can help you deploy. > On 07/23/2014 07:23 PM, Richard Hector wrote: >> Hi all, >> >> For some reason, I didn't go to http://wiki2.dovecot.org/NFS until >> now, and I'm starting to get worried ... >> >> The plan was to have multple servers (MXes) receiving mail, and >> delivering via LMTP to multiple backend dovecot servers (with amavis >> in front of dovecot; LMTP both sides). Then we'd have multiple servers >> for clients to use IMAP or POP3. >> >> This is more or less how the system already works, except with Courier >> IMAP, and postfix on the backends, delivering to maildirs with procmail. >> >> But with the recommendation to use the Director for both IMAP/POP3 and >> LMTP - that starts to sound like I need a whole bunch more servers to >> run Directors and proxies, and even then it might not be a good idea >> to have different servers running lmtp and imap/pop. >> >> One possible mitigating point is that our 'load balancing' is DNS >> round-robin, so a given client will probably stick with a single >> imap/pop server anyway, but if the user has multiple clients >> (desktop/mobile etc) then they may still hit different servers. >> >> Can someone clarify best practice for a setup needing multiple servers >> for load balancing and redundancy? >> >> Is Courier already likely to have been suffering these problems? >> >> Oh, the NFS server is a NetApp Filer, if that matters. >> >> I'm using dovecot 2.2.9 from debian wheezy backports, in order to get >> the quota policy daemon support. >> >> Thanks, >> Richard From stan at hardwarefreak.com Thu Jul 24 20:22:48 2014 From: stan at hardwarefreak.com (Stan Hoeppner) Date: Thu, 24 Jul 2014 15:22:48 -0500 Subject: Multiple servers and NFS In-Reply-To: <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> Message-ID: <53D16B18.30408@hardwarefreak.com> On 7/24/2014 12:09 PM, Nathan Schultheiss wrote: ... > |----> Mail it's stored in MailDir format "mail_location = maildir:%h" > > When I go on Roundcube with a mailbox who I've 96000 in the INBOX "cur" folder, the first time I need 1 minutes waiting. > The second time it's a little more quick 10 seconds... But when I go back again (after a few hours) it's slow again... And we'are just 5 users at the moment for test... This is a caching problem, not an NFS problem. See /etc/roundcube/main.inc.php // enable caching of messages and mailbox data in the local database. // this is recommended if the IMAP server does not run on the same // machine $rcmail_config['enable_caching'] = FALSE; Change that to TRUE. You will also need a database configured on the RC host, such as sqlite or mysql. Cheers, Stan From richard at walnut.gen.nz Thu Jul 24 20:51:13 2014 From: richard at walnut.gen.nz (Richard Hector) Date: Fri, 25 Jul 2014 08:51:13 +1200 Subject: Maildir migration - using separate INDEX and CONTROL directories? In-Reply-To: References: <53D02B17.9030402@walnut.gen.nz> Message-ID: <53D171C1.2060008@walnut.gen.nz> On 24/07/14 18:18, Steffen Kaiser wrote: > On Thu, 24 Jul 2014, Richard Hector wrote: > >> Is there a handy tool to move the files to the right places? Or is >> there a complete list of what files need to go where? > > IMHO: move all dovecot* files the migration script generates and the > "subscriptions" file into the control directories, some INBOX-related > files probably go to /.INBOX, dovecot-keywords and > dovecot-uidlist - maybe more. The migration scripts I saw til today > never create any indexes, so the assumption should be fine. And test it > with one account, move some messages around, add some subscriptions and > ACLs, ... Thanks - seems straightforward enough. Richard From richard at walnut.gen.nz Thu Jul 24 21:12:37 2014 From: richard at walnut.gen.nz (Richard Hector) Date: Fri, 25 Jul 2014 09:12:37 +1200 Subject: Multiple servers and NFS In-Reply-To: <53D0F59D.1030606@freedominterface.org> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> Message-ID: <53D176C5.3030604@walnut.gen.nz> On 25/07/14 00:01, Eduardo Ramos wrote: > You can use one or more instances of Dovecot on the same machine, as you > can see here (http://wiki2.dovecot.org/RunningDovecot) "Running Multiple > Invocations of Dovecot". > > The problem with DNS round-robind is that if you server goes down, DNS > continues resolving for it. I would recommend use some balancer like > LVS+keepalived. > > Consider that multi layer solution: > -------------------- -------------------- > | LVS + keepalived | | LVS + keepalived | > -------------------- -------------------- > | | > -------------- -------------- > | Director 1 | | Director 2 | > -------------- -------------- > | | > ----------------- ----------------- > | IMAP/POP/LMTP | | IMAP/POP/LMTP | > | Backend | | Backend | > ----------------- ----------------- > \ / > \ / > \ ------------ / > -------| NetAPP |--------- > ------------ Thanks. Presumably each LVS (in VRRP setup?) has to talk to both directors, and the directors each have to talk to both backends. ASCII art is tricky :-) I accept that I could run multiple dovecots on the same machine, true. And keepalived/LVS is a good plan, thanks. The key point I wanted to confirm is that I need to run the lmtpds on the same set of backend machines as the imapd/popds, and behind the same directors, so that all sessions relating to the same user can be directed to the same backend. Correct? Rather than trying to draw increasingly complex diagrams in ASCII, I've put some here (without the LVS layer): https://walnut.gen.nz/mail-architectures.png I suspect that A is what I need, though the docs suggest that if I turn off writing of index files in lmtp, I could get away with one of the others, right? What disadvantages are there in that? One concern is the ability to scale up to more servers for some particular parts of the chain as load dictates - we're concerned that amavis might be a significant candidate. I assume amavis could go either in front of or behind the director. Thanks, Richard From richard at walnut.gen.nz Fri Jul 25 00:25:49 2014 From: richard at walnut.gen.nz (Richard Hector) Date: Fri, 25 Jul 2014 12:25:49 +1200 Subject: Multiple servers and NFS In-Reply-To: <53D176C5.3030604@walnut.gen.nz> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> Message-ID: <53D1A40D.1090303@walnut.gen.nz> On 25/07/14 09:12, Richard Hector wrote: > Rather than trying to draw increasingly complex diagrams in ASCII, I've > put some here (without the LVS layer): > https://walnut.gen.nz/mail-architectures.png I've come up with a revised plan - I think we can do without LVS; SMTP should just work with multiple MX records, and IMAP/POP should be fine as well with RRDNS - the machines should be up most of the time, and if a customer has to click to reconnect every now and then on the rare occasions when they're not it's not a huge deal. Otherwise, we could also do load balancing on our routers. Anyway - any comments on the sanity of this diagram most welcome :-) https://walnut.gen.nz/mail-architecture-2.png Richard From eduardo at freedominterface.org Fri Jul 25 03:30:07 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Fri, 25 Jul 2014 00:30:07 -0300 Subject: Multiple servers and NFS In-Reply-To: <53D1A40D.1090303@walnut.gen.nz> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> Message-ID: <53D1CF3F.9020201@freedominterface.org> Hi Richard, In fact I thought it a little confusing. I had some bad experience with DNS RR when one of my IMAP server got down. Clients continued trying connect to broken server and it caused some problems. But when everything is ok, it works well. I drew a diagram with my idea. What do you think? https://dl.dropboxusercontent.com/u/41373531/mail.png On 07/24/2014 09:25 PM, Richard Hector wrote: > On 25/07/14 09:12, Richard Hector wrote: >> Rather than trying to draw increasingly complex diagrams in ASCII, I've >> put some here (without the LVS layer): >> https://walnut.gen.nz/mail-architectures.png > > I've come up with a revised plan - I think we can do without LVS; SMTP > should just work with multiple MX records, and IMAP/POP should be fine > as well with RRDNS - the machines should be up most of the time, and > if a customer has to click to reconnect every now and then on the rare > occasions when they're not it's not a huge deal. Otherwise, we could > also do load balancing on our routers. > > Anyway - any comments on the sanity of this diagram most welcome :-) > > https://walnut.gen.nz/mail-architecture-2.png > > Richard From richard at walnut.gen.nz Fri Jul 25 04:58:18 2014 From: richard at walnut.gen.nz (Richard Hector) Date: Fri, 25 Jul 2014 16:58:18 +1200 Subject: Multiple servers and NFS In-Reply-To: <53D1CF3F.9020201@freedominterface.org> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> Message-ID: <53D1E3EA.5040705@walnut.gen.nz> On 25/07/14 15:30, Eduardo Ramos wrote: > Hi Richard, > > In fact I thought it a little confusing. I had some bad experience with > DNS RR when one of my IMAP server got down. Clients continued trying > connect to broken server and it caused some problems. But when > everything is ok, it works well. > > I drew a diagram with my idea. What do you think? > > https://dl.dropboxusercontent.com/u/41373531/mail.png Interesting, thanks. I'd forgotten to draw in the director ring. As I said, if we need load balancing we can do that on the router, which as I understand it will do more or less the same thing as LVS. It might be Cisco SLB, but I'm not sure; I'm not the router guy :-) But what interests me most is that your diagram shows the mx servers connecting directly to the backend servers, rather than going through the proxy director - I thought that was a no-no. Oh, and I don't think we want to load down our front-end MX servers with amavis, either. Thanks for your input :-) Richard From jk at jkart.de Fri Jul 25 09:23:49 2014 From: jk at jkart.de (Jim Knuth) Date: Fri, 25 Jul 2014 11:23:49 +0200 Subject: Error after Upgrade Message-ID: <53D22225.6030903@jkart.de> Hello, after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I?ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine. What?s wrong? Any ideas or solution greatly appreciated. Thanks. Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 postfix/lmtp[25617]: 20773D10003: to=, orig_to=, relay=server1.art-domains.de[private/dovecot-lmtp], delay=0.05, delays=0.03/ 0/0.01/0.02, dsn=4.4.2, status=deferred (lost connection with server1.art-domains.de[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) Jul 25 11:03:01 server2 amavis[25541]: (25541-01) Passed CLEAN {RelayedInbound}, [213.203.238.6]:53401 [193.175.143.182] -> , Queue-I D: 62B8BD10001, Message-ID: <53D21B91.2070109 at fh-landshut.de>, mail_id: AE71HPGl9ZR5, Hits: -5, size: 13518, queued_as: 20773D10003, 2771 ms Jul 25 11:03:01 server2 amavis[25541]: (25541-01) Passed CLEAN, -> , Hits: -5, tag=-9999.9, tag2=2.5, kill=3, queued_as: 20773D10003, L/Y/0/0 Jul 25 11:03:01 server2 postfix/lmtp[25607]: 62B8BD10001: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=3.9, delays=1.2/0/0.01/2.8, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[ 127.0.0.1]:10025): 250 2.0.0 Ok: queued as 20773D10003) Jul 25 11:03:01 server2 postfix/qmgr[25508]: 62B8BD10001: removed Jul 25 11:03:02 server2 postfix/lmtp[25615]: 20773D10003: to=, orig_to=, relay=server1.art-domains.de[private/dovecot-lmtp], delay=0.06, del ays=0.03/0/0.03/0.01, dsn=4.4.2, status=deferred (lost connection with server1.art-domains.de[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) Jul 25 11:03:02 server2 dovecot: lmtp(25653): Connect from local Jul 25 11:03:02 server2 dovecot: lmtp(25653): Fatal: master: service(lmtp): child 25653 killed with signal 11 (core dumps disabled) -- Mit freundlichen Gr??en, with kind regards, Jim Knuth --------- Die Freiheit der Rede hat den Nachteil, da? immer wieder Dummes, H??liches und B?sartiges gesagt wird. Wenn wir aber alles in allem nehmen, sind wir doch eher bereit, uns damit abzufinden, als sie abzuschaffen. [Churchill] From h.reindl at thelounge.net Fri Jul 25 09:38:00 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 25 Jul 2014 11:38:00 +0200 Subject: Error after Upgrade In-Reply-To: <53D22225.6030903@jkart.de> References: <53D22225.6030903@jkart.de> Message-ID: <53D22578.6000609@thelounge.net> Am 25.07.2014 11:23, schrieb Jim Knuth: > after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 > I discovered that in my log and all mails stuck in the Queue. > I?ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine > What?s wrong? the Debian package > Any ideas or solution greatly appreciated. Thanks. downgrade > Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core > dumps disabled) > Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local > Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core > dumps disabled) http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 Core Invalid memory reference -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From jk at jkart.de Fri Jul 25 09:49:26 2014 From: jk at jkart.de (Jim Knuth) Date: Fri, 25 Jul 2014 11:49:26 +0200 Subject: Error after Upgrade In-Reply-To: <53D22578.6000609@thelounge.net> References: <53D22225.6030903@jkart.de> <53D22578.6000609@thelounge.net> Message-ID: <53D22826.3000701@jkart.de> am 25.07.14 11:38 schrieb Reindl Harald : > > > Am 25.07.2014 11:23, schrieb Jim Knuth: >> after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 >> I discovered that in my log and all mails stuck in the Queue. >> I?ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine >> What?s wrong? > > the Debian package thanks, but that is from deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main > >> Any ideas or solution greatly appreciated. Thanks. > > downgrade > >> Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core >> dumps disabled) >> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local >> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core >> dumps disabled) > > http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 > SIGSEGV 11 Core Invalid memory reference > -- Mit freundlichen Gr??en, with kind regards, Jim Knuth --------- Better to reign in hell, than to serve in heaven! (John Milton) From nathan at schultheiss.fr Fri Jul 25 10:08:02 2014 From: nathan at schultheiss.fr (Nathan Schultheiss) Date: Fri, 25 Jul 2014 12:08:02 +0200 (CEST) Subject: Pigeonhole Sieve LDAP support In-Reply-To: <53D0FFAB.4090309@rename-it.nl> References: <53D0FFAB.4090309@rename-it.nl> Message-ID: <1041343464.570594.1406282882550.JavaMail.zimbra@schultheiss.fr> Hi Stephan, Yesterday I've make a update with your repo and now I've the 2.2.13 (e07f504f1040) And today I've error on my LDA: 2014-07-25 11:29:43 LDA(nathan at schultheiss.fr): Panic: file sieve-storage.c: line 471 (sieve_storage_unref): assertion failed: (storage->refcount > 0) 2014-07-25 11:29:43 LDA(nathan at schultheiss.fr): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x710bf) [0x7f0a74a3f0bf] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0a74a3f19a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0a749f47fe] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x2c9e9) [0x7f0a720bb9e9] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x2c80) [0x7f0a7232ec80] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x44) [0x7f0a74fd3464] -> /usr/lib/dovecot/dovecot-lda(main+0x3b2) [0x402a92] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f0a7462f76d] -> /usr/lib/dovecot/dovecot-lda() [0x40333d] I use: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main deb-src http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main On my dovecot I've for sieve: plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /home/vmail/.sieve/virus.sieve } That working without problem since the update. After the update, account with sieve rule work with the LDA and without does not work with the error listed. I've found, if I add on the plugin section: sieve_default = /home/vmail/.sieve/default.sieve That work again without errors :) Evtl. this fix can help people who they have the same error :) I've no entry on my default.sieve it's just here for "fix" the "Panic" error. Bests Regards, Nathan ----- Mail original ----- De: "Stephan Bosch" ?: "Dovecot Mailing List" Envoy?: Jeudi 24 Juillet 2014 14:44:27 Objet: Pigeonhole Sieve LDAP support Hi, Yesterday, I committed two important and rather big changes to the Pigeonhole repository. The first creates a generic interface for implementing Sieve script storages. It was already possible to some extent to read Sieve scripts from other sources than the local filesystem, such as Dovecot dict, but that was still pretty limited, as it was not possible to do this with sieve_before/sieve_after. This is now supported. But, more importantly, ManageSieve did not support storing Sieve scripts on locations other than the local filesystem. Now, alternatives can be implemented. Still, I haven't actually implemented write access to a storage other than the local filesystem yet, but now this would be much easier to achieve. The second creates an LDAP script storage implementation. Much like the dict storage, it is still read-only. It can be compiled directly into the Sieve interpreter, and, alternatively, it can also be compiled as a plugin called sieve_storage_ldap. I've updated the documentation in the sources. For all Xi repository users: I added compilation of LDAP storage as a plugin. Read the INSTALL files and other files referenced therein for more information about how to use the plugin. The plugin is installed as part of the dovecot-ldap package. This is a rather big change, but it should all be backwards compatible in terms of configuration. If you have problems (I heard about one so far), please don't hesitate to notify me. Regards, Stephan. From h.reindl at thelounge.net Fri Jul 25 10:14:13 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 25 Jul 2014 12:14:13 +0200 Subject: Error after Upgrade In-Reply-To: <53D22826.3000701@jkart.de> References: <53D22225.6030903@jkart.de> <53D22578.6000609@thelounge.net> <53D22826.3000701@jkart.de> Message-ID: <53D22DF5.5060206@thelounge.net> Am 25.07.2014 11:49, schrieb Jim Knuth: > am 25.07.14 11:38 schrieb Reindl Harald : > >> Am 25.07.2014 11:23, schrieb Jim Knuth: >>> after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 >>> I discovered that in my log and all mails stuck in the Queue. >>> I?ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine >>> What?s wrong? >> >> the Debian package > > thanks, but that is from > deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main how does it matter from where it is? so what - you updated, the new version leads in SEGFAULTS so that binary is at least on your machine broken and unstable the answer to "what's wrong" remains: that package >>> Any ideas or solution greatly appreciated. Thanks. >> >> downgrade >> >>> Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core >>> dumps disabled) >>> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local >>> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core >>> dumps disabled) >> >> http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 >> SIGSEGV 11 Core Invalid memory reference -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From jk at jkart.de Fri Jul 25 10:33:44 2014 From: jk at jkart.de (Jim Knuth) Date: Fri, 25 Jul 2014 12:33:44 +0200 Subject: Error after Upgrade In-Reply-To: <53D22DF5.5060206@thelounge.net> References: <53D22225.6030903@jkart.de> <53D22578.6000609@thelounge.net> <53D22826.3000701@jkart.de> <53D22DF5.5060206@thelounge.net> Message-ID: <53D23288.3060303@jkart.de> am 25.07.14 12:14 schrieb Reindl Harald : > > > Am 25.07.2014 11:49, schrieb Jim Knuth: >> am 25.07.14 11:38 schrieb Reindl Harald : >> >>> Am 25.07.2014 11:23, schrieb Jim Knuth: >>>> after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 >>>> I discovered that in my log and all mails stuck in the Queue. >>>> I?ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine >>>> What?s wrong? >>> >>> the Debian package >> >> thanks, but that is from >> deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main > > how does it matter from where it is? > > so what - you updated, the new version leads in SEGFAULTS > so that binary is at least on your machine broken and unstable > > the answer to "what's wrong" remains: that package yes, I know. ;) But my question goes also to the Maintainer. > >>>> Any ideas or solution greatly appreciated. Thanks. >>> >>> downgrade >>> >>>> Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core >>>> dumps disabled) >>>> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local >>>> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core >>>> dumps disabled) >>> >>> http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 >>> SIGSEGV 11 Core Invalid memory reference > -- Mit freundlichen Gr??en, with kind regards, Jim Knuth --------- ?Jesus wurde gekreuzigt, weil er bemerkt wurde. Deswegen verschwinde ich h?ufig von der Bildfl?che.? Bob Dylan From toni at solu.fi Fri Jul 25 12:12:40 2014 From: toni at solu.fi (Toni Mattila) Date: Fri, 25 Jul 2014 15:12:40 +0300 Subject: 2.2.13 + hg: Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (fd >= 0) Message-ID: <53D249B8.6020503@solu.fi> Hi, Found this in logfiles: Jul 25 14:12:38 dovecot: pop3(cen at so.red): Error: UIDL: File name lookup failed: Message was expunged Jul 25 14:12:38 dovecot: pop3(cen at so.red): Disconnected: POP3 UIDLs couldn't be listed top=187/356348, retr=0/0, del=0/1207, size=789346199 Jul 25 14:12:38 dovecot: pop3(cen at so.red): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (fd >= 0) Jul 25 14:12:38 dovecot: pop3(cen at so.red): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xbdfc1f] -> /usr/lib/dovecot/libdovecot.so.0 [0xbdfc9d] -> /usr/lib/dovecot/libdovecot.so.0 [0xbdf514] -> /usr/lib/dovecot/libdovecot.so.0 [0xbf162d] -> /usr/lib/dovecot/libdovecot.so.0(io_add_istream+0x3f) [0xbf272f] -> dovecot/pop3 [0x804d149] -> /usr/lib/dovecot/libdovecot.so.0 [0xbff17a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0xbf1d88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0xbf375f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x1e) [0xbf1e2e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0xbf1eb8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2d) [0xb9842d] -> dovecot/pop3(main+0x2a9) [0x804b3b9] -> /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x6f7dec] -> dovecot/pop3 [0x804aeb1] Jul 25 14:12:38 dovecot: pop3(cen at so.red): Fatal: master: service(pop3): child 27510 killed with signal 6 (core dumped) (gdb) bt #0 0x00b1a402 in __kernel_vsyscall () #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 #3 0x00bdfc14 in default_fatal_finish (type=, status=0) at failures.c:193 #4 0x00bdfc9d in i_internal_fatal_handler (ctx=0xbf82cd34, format=0xc0c784 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf82cd54 "\202\232?") at failures.c:657 #5 0x00bdf514 in i_panic (format=0xc0c784 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:267 #6 0x00bf162d in io_add_file (fd=-1, condition=IO_READ, source_linenum=816, callback=0x804d150 , context=0x83ba628) at ioloop.c:40 #7 0x00bf272f in io_add_istream (input=0x83ba960, source_linenum=816, callback=0x804d150 , context=0x83ba628) at ioloop.c:86 #8 0x0804d149 in client_output (client=0x83ba628) at pop3-client.c:815 #9 0x00bff17a in stream_send_io (fstream=0x83baa48) at ostream-file.c:468 #10 0x00bf1d88 in io_loop_call_io (io=0x83baaf8) at ioloop.c:441 #11 0x00bf375f in io_loop_handler_run_internal (ioloop=0x83a5498) at ioloop-epoll.c:220 #12 0x00bf1e2e in io_loop_handler_run (ioloop=0x83a5498) at ioloop.c:488 #13 0x00bf1eb8 in io_loop_run (ioloop=0x83a5498) at ioloop.c:465 #14 0x00b9842d in master_service_run (service=0x83a53c0, callback=0x804b4e0 ) at master-service.c:566 #15 0x0804b3b9 in main (argc=Cannot access memory at address 0x0 ) at main.c:277 (gdb) Thanks, Toni From django at nausch.org Fri Jul 25 12:58:39 2014 From: django at nausch.org (Django [BOfH]) Date: Fri, 25 Jul 2014 14:58:39 +0200 Subject: dovecot-2.2.13 and CentOS 7 Message-ID: <53D2547F.4040404@nausch.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI, if someone need/want dovecot-2.2.13 rpms for CentOS 7 here're some one: http://wiki.mailserver.guru/doku.php/centos:mailserver.guru ttyl Django - -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJT0lR2AAoJEAdOz2FQpr/tNmQP/3Mrd+cQs6S/UDfUpTYIqRIY dcZrxUvwoktz1JN/kkmZOVOpCw6hnz0HHIb3Dq/ncKCYnSa2qlJRpLaswQPjWERJ KFNuHeRqqpQPe49PwBVZjkAn4JJv5DhF/+ggM1ATSfWp7JFt82+9r+ozrWeIjNXH QiaLSahyxo6/sjqOhZftRsRcZQkxulb1Opc8vC1nCBDlJ/8z9ZDyhxFNmyCCfLtD FDyDzzruqKv9ozQMFz/+kw0eQS7Q7LHM3ZeCd6y495u/6xR/sIiCUDVlUplsaEFi hVQdZFXtH58io94ILHhTHjf9qfczlLWMNI/cZsbChg5XEnk3SmWxTYW6zbXC5L2t Ry0OpZwL6iQ9erA1av2y4ez+Y+sSYdgHpXX/BhyD6qN3hSTbqJPL5jgEHeFDEYS7 j0j3AYRjYzRHpfW1LyFNFtrFWqJMRqyPjVisJfztcSV3rO4tEybZjYdxL86ngB8x kZByvHBbyqG44Wj+6kqBtsBCPOkfrwBOmjU+zMlJAfd2/F30M2vQ8rSJql1NUqA3 FKqjuyxV22NL3NR53AKakMR2aX/eRgZTX9DYod+iIhVELcAQmmE3OLeRwfRfIGNx lVlfOWkMbOQ85Jzg7pUAxLvmjyktIiHHLxlCryV/SZ3di3vp/eYPvVbP7v+OPHhH 1W0gbYk6YXxQt0+Xr4sq =TgrN -----END PGP SIGNATURE----- From stephan at rename-it.nl Fri Jul 25 14:01:38 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Fri, 25 Jul 2014 16:01:38 +0200 Subject: Pigeonhole Sieve LDAP support In-Reply-To: <1041343464.570594.1406282882550.JavaMail.zimbra@schultheiss.fr> References: <53D0FFAB.4090309@rename-it.nl> <1041343464.570594.1406282882550.JavaMail.zimbra@schultheiss.fr> Message-ID: <53D26342.4020506@rename-it.nl> Hi Nathan, Nathan Schultheiss schreef op 25-7-2014 12:08: > Hi Stephan, > > Yesterday I've make a update with your repo and now I've the 2.2.13 (e07f504f1040) > > And today I've error on my LDA: > 2014-07-25 11:29:43 LDA(nathan at schultheiss.fr): Panic: file sieve-storage.c: line 471 (sieve_storage_unref): assertion failed: (storage->refcount > 0) > 2014-07-25 11:29:43 LDA(nathan at schultheiss.fr): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x710bf) [0x7f0a74a3f0bf] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0a74a3f19a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0a749f47fe] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x2c9e9) [0x7f0a720bb9e9] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x2c80) [0x7f0a7232ec80] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x44) [0x7f0a74fd3464] -> /usr/lib/dovecot/dovecot-lda(main+0x3b2) [0x402a92] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f0a7462f76d] -> /usr/lib/dovecot/dovecot-lda() [0x40333d] This should fix the assert: http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/e3d3d7a5f642 Regards, Stephan. From eduardo at freedominterface.org Fri Jul 25 14:12:30 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Fri, 25 Jul 2014 11:12:30 -0300 Subject: Multiple servers and NFS In-Reply-To: <53D1E3EA.5040705@walnut.gen.nz> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> <53D1E3EA.5040705@walnut.gen.nz> Message-ID: <53D265CE.2000108@freedominterface.org> Hi Richard, I think its better balance with a router too. Is there any problem with use postfix+amavis in the front-end? I did not understand what the advantage of use dovecot LMTP with director too. On 07/25/2014 01:58 AM, Richard Hector wrote: > On 25/07/14 15:30, Eduardo Ramos wrote: >> Hi Richard, >> >> In fact I thought it a little confusing. I had some bad experience with >> DNS RR when one of my IMAP server got down. Clients continued trying >> connect to broken server and it caused some problems. But when >> everything is ok, it works well. >> >> I drew a diagram with my idea. What do you think? >> >> https://dl.dropboxusercontent.com/u/41373531/mail.png > Interesting, thanks. I'd forgotten to draw in the director ring. > > As I said, if we need load balancing we can do that on the router, which > as I understand it will do more or less the same thing as LVS. It might > be Cisco SLB, but I'm not sure; I'm not the router guy :-) > > But what interests me most is that your diagram shows the mx servers > connecting directly to the backend servers, rather than going through > the proxy director - I thought that was a no-no. Oh, and I don't think > we want to load down our front-end MX servers with amavis, either. > > Thanks for your input :-) > > Richard From rs at sys4.de Fri Jul 25 14:19:13 2014 From: rs at sys4.de (Robert Schetterer) Date: Fri, 25 Jul 2014 16:19:13 +0200 Subject: Multiple servers and NFS In-Reply-To: <53D265CE.2000108@freedominterface.org> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> <53D1E3EA.5040705@walnut.gen.nz> <53D265CE.2000108@freedominterface.org> Message-ID: <53D26761.1080109@sys4.de> Am 25.07.2014 um 16:12 schrieb Eduardo Ramos: > I did not understand what the advantage of use dovecot LMTP with > director too. in "very short" words... with nfs ,the director should avoid concurrent events which may happen with lmtp too, depending to multiple server setup Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From eagle.base at gmx.net Sat Jul 26 10:41:57 2014 From: eagle.base at gmx.net (Andre Dietrich) Date: Sat, 26 Jul 2014 12:41:57 +0200 Subject: IMAP forward boxes In-Reply-To: <53D111B6.8000104@gmx.net> References: <53D111B6.8000104@gmx.net> Message-ID: <53D385F5.1020303@gmx.net> Hi again, sorry for the disturbance. I originally came from courier-imap and missed the rich set of dovecot-plugins (http://wiki2.dovecot.org/Plugins). That's what I've been looking for. I think snarf or notify will help me. Thx. Andre On 24.07.2014 16:01, Andre Dietrich wrote: > Hi all, > > since a few weeks I'm experimenting with some "IMAP forward boxes", but > I didn't find a satisfactory solution yet. > > Target function is a directory structure like following in a shared mailbox: > > /intern/users/fred > /intern/users/ted > /intern/users/alice > > The idea is, that a mail, moved to the directory "/intern/users/fred" > via IMAP-client will be forwarded to "fred at test.domain" without > modifying the mail (except the header line "delivered to:"). > > So if you get a mail in your inbox and want fred to answer it, you > drag'n'drop it to /intern/users/fred. Fred gets the mail in his inbox > and can answer it. > > > To share all inboxes, to drop mails directly to them, is not an option, > because I don't want everybody to see all other inboxes mails. Only to > apply "-w-" ACL rights isn't an option either, because it seems to > irritate the mail clients. > > > Some month ago I had a partially working solution using a cron bash > script. The script read the mails in the cur and new folders, processed > the folders path and passed it to sendmail. It's ok, but it has to run > quite often to get an adequate forwarding time and on sendmail errors > mails got lost without any notification. > > It would be nice to have a dot-forward file in this subfolder (like in > the qmail mailbox root), which is processed by dovecot when a mail is > dropped in. > > > Is it possible to solve this with a sieve script, a dot-forward file, or > something similar ? > > > I'm grateful for all solutions / ideas ! thx! > > > Andre > From laeeth at laeeth.com Sat Jul 26 22:52:19 2014 From: laeeth at laeeth.com (Laeeth Isharc) Date: Sat, 26 Jul 2014 23:52:19 +0100 Subject: struggling with pigeonhole date extensions Message-ID: <68150136-f00f-410e-81c2-4a270ff97adf@getmailbird.com> I am struggling with how to use the date extension for Dovecot/Pigenhole implementation of Sieve email filtering language. I have read RFC 5260 several times and tried different things with no luck. I would like to place all messages this year up till the end of March into the specified mail folder. What the snippet below actually seems to do is take any messages this year (whether before or after March). Any thoughts? if allof(date :value "eq" :originalzone "date" "year" "2014", date :value "le" :originalzone "date" "month" "3") { fileinto "INBOX/2014 up to Mar"; stop; } Incidentally, it's puzzling how sparse the ecosystem seems to be for managing sieve scripts given the importance of email and the unmanageability of volumes these days without rules. What would be nice to have is something like the Outlook rule manager as a front end and server side sieve scripts on the back. I looked at Modoboa (which seems to be the only standalone option), but it's a bit heavy for my taste and I struggled to configure it in the time I had available. Thanks in advance. From trashcan at odo.in-berlin.de Sun Jul 27 12:21:57 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Sun, 27 Jul 2014 14:21:57 +0200 Subject: [pigeonhole] disregards --with-ldap=no during compilation Message-ID: Hi -- I can't get current dovecot and pigeonhole compiled; compilation stops with: | sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found Ok, because my dovecot isn't compiled with ldap (--without-ldap), I tried to apply "--with-ldap=no" with configure as advertised in the INSTALL file of pigeonhole, but without success: [...] | ./sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found | #include | ^ | 1 error generated. | gmake[5]: *** [sieve-ldap-db.lo] Error 1 | gmake[5]: Leaving directory `/usr/local/etc/dovecot/SOURCE/dovecot-2.2-pigeonhole/src/lib-sieve/storage/ldap' [...] | gmake: *** [all] Error 2 My configure run logfile shows: [...] | config.status: creating src/lib-sieve/storage/ldap/Makefile [...] | script drivers . : file dict | : -ldap This happens at FreeBSD-STABLE (clang 3.4.1, gmake 3.82) with dovecot at 2d2d75ac6715 and pigeonhole at 1475892e8cff. Any ideas what went wrong? (I'm back to pigeonhole 0.4.3 (1c6130ff5dd6) for the time being.) Thanks and regards, Michael From jerry at seibercom.net Sun Jul 27 12:46:59 2014 From: jerry at seibercom.net (Jerry) Date: Sun, 27 Jul 2014 08:46:59 -0400 Subject: [pigeonhole] disregards --with-ldap=no during compilation /usr/ports/mail/dovecot2 In-Reply-To: References: Message-ID: <20140727084659.3e66df7f@scorpio> On Sun, 27 Jul 2014 14:21:57 +0200, Michael Grimm stated: >Hi -- > >I can't get current dovecot and pigeonhole compiled; compilation stops with: > >| sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found > >Ok, because my dovecot isn't compiled with ldap (--without-ldap), I tried to >apply "--with-ldap=no" with configure as advertised in the INSTALL file of >pigeonhole, but without success: > >[...] >| ./sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found >| #include >| ^ >| 1 error generated. >| gmake[5]: *** [sieve-ldap-db.lo] Error 1 >| gmake[5]: Leaving directory >`/usr/local/etc/dovecot/SOURCE/dovecot-2.2-pigeonhole/src/lib-sieve/storage/ldap' [...] >| gmake: *** [all] Error 2 > >My configure run logfile shows: > >[...] >| config.status: creating src/lib-sieve/storage/ldap/Makefile >[...] >| script drivers . : file dict >| : -ldap > >This happens at FreeBSD-STABLE (clang 3.4.1, gmake 3.82) with dovecot at >2d2d75ac6715 and pigeonhole at 1475892e8cff. > >Any ideas what went wrong? > >(I'm back to pigeonhole 0.4.3 (1c6130ff5dd6) for the time being.) > >Thanks and regards, >Michael Are you using "/usr/ports/mail/dovecot2-pigeonhole" and "/usr/ports/mail/dovecot2" from the FreeBSD ports system or trying to compile from source? If from source, you can expect those problems. If you are not using the ports system, why not? -- Jerry From trashcan at odo.in-berlin.de Sun Jul 27 12:56:46 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Sun, 27 Jul 2014 14:56:46 +0200 Subject: [pigeonhole] disregards --with-ldap=no during compilation /usr/ports/mail/dovecot2 In-Reply-To: <20140727084659.3e66df7f@scorpio> References: <20140727084659.3e66df7f@scorpio> Message-ID: <182E2127-C28A-4C8B-8368-3D98A336C82D@odo.in-berlin.de> On 27.07.2014, at 14:46, Jerry wrote: On Sun, 27 Jul 2014 14:21:57 +0200, Michael Grimm stated: >> I can't get current dovecot and pigeonhole compiled; compilation stops with: > > Are you using "/usr/ports/mail/dovecot2-pigeonhole" and > "/usr/ports/mail/dovecot2" from the FreeBSD ports system or trying to compile > from source? I am compiling postfix and dovecot/pigeonhole from source for years now. > If from source, you can expect those problems. Well, I ran into some issues once in a while, but I could solve them. > If you are not using the ports system, why not? I like to have full control over those applications, and sometimes, I want to test new features not available in ports, yet. My production system runs in a jail with postfix/dovecot/pigeonhole at stable releases, my testing jail runs bleeding edge versions. And here I ran into that issue reported today. Regards, Michael From jerry at seibercom.net Sun Jul 27 14:00:56 2014 From: jerry at seibercom.net (Jerry) Date: Sun, 27 Jul 2014 10:00:56 -0400 Subject: [pigeonhole] disregards --with-ldap=no during compilation /usr/ports/mail/dovecot2bra@fsn.hu In-Reply-To: <182E2127-C28A-4C8B-8368-3D98A336C82D@odo.in-berlin.de> References: <20140727084659.3e66df7f@scorpio> <182E2127-C28A-4C8B-8368-3D98A336C82D@odo.in-berlin.de> Message-ID: <20140727100056.2fca56af@scorpio> On Sun, 27 Jul 2014 14:56:46 +0200, Michael Grimm stated: >On 27.07.2014, at 14:46, Jerry wrote: >On Sun, 27 Jul 2014 14:21:57 +0200, Michael Grimm stated: > >>> I can't get current dovecot and pigeonhole compiled; compilation stops >>> with: >> >> Are you using "/usr/ports/mail/dovecot2-pigeonhole" and >> "/usr/ports/mail/dovecot2" from the FreeBSD ports system or trying to >> compile from source? > >I am compiling postfix and dovecot/pigeonhole from source for years now. > >> If from source, you can expect those problems. > >Well, I ran into some issues once in a while, but I could solve them. > >> If you are not using the ports system, why not? > >I like to have full control over those applications, and sometimes, I want >to test new features not available in ports, yet. My production system runs >in a jail with postfix/dovecot/pigeonhole at stable releases, my testing >jail runs bleeding edge versions. And here I ran into that issue reported >today. I have no idea what "features" you are referring to since you did not list them. However, I might suggest that either you contact the port maintainer for dovecot or pigeonhole and express your concerns to them or , create a separate port which produces the results you want and then submit it to the FreeBSD ports crew. I have done similar things in the past and had rather good success with it. -- Jerry From delrio at mie.utoronto.ca Sun Jul 27 14:01:34 2014 From: delrio at mie.utoronto.ca (Oscar del Rio) Date: Sun, 27 Jul 2014 10:01:34 -0400 Subject: struggling with pigeonhole date extensions In-Reply-To: <68150136-f00f-410e-81c2-4a270ff97adf@getmailbird.com> References: <68150136-f00f-410e-81c2-4a270ff97adf@getmailbird.com> Message-ID: <53D5063E.5090309@mie.utoronto.ca> On 26/07/2014 6:52 PM, Laeeth Isharc wrote: > I would like to place all messages this year up till the end of March into the specified mail folder. What the snippet below actually seems to do is take any messages this year (whether before or after March). > Any thoughts? > if allof(date :value "eq" :originalzone "date" "year" "2014", date :value "le" :originalzone "date" "month" "3") { fileinto "INBOX/2014 up to Mar"; stop; } > just guessing, I have not tried... "month" is always 2 digits, so compare with "03" instead of "3" or force numeric comparison with :comparator "i;ascii-numeric" From nima at ikp.uni-koeln.de Thu Jul 24 12:16:04 2014 From: nima at ikp.uni-koeln.de (Nima Saed-Samii) Date: Thu, 24 Jul 2014 14:16:04 +0200 Subject: Migration from mbox/maildir++ to mdbox Message-ID: <1406204164.2309.8.camel@vimes.ikp.uni-koeln.de> Dear list, dovecot version: 2.1.7 I have an old mail server that uses mboxes for the INBOX and maildirs for subfolders. I want to migrate our mail handling to a new setup using mdboxes for everything. The current config looks like this: # 2.1.7: /etc/dovecot/dovecot.conf doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1127) # OS: Linux 3.2.0-0.bpo.4-686-pae i686 Debian 6.0.10 auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 114 log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = mbox:~/Mail/MBox:INBOX=/var/mail/%u mail_max_userip_connections = 30 mail_privileged_group = mail namespace { hidden = yes inbox = yes list = no location = prefix = "#mbox/" separator = / } namespace { location = maildir:~/Mail/Maildir prefix = separator = / } passdb { args = dovecot driver = pam } protocols = imap service auth { client_limit = 1024 user = root } service imap-login { inet_listener imap { port = 0 } process_limit = 1024 } ssl_cert = I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to finish up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other email in ~/Maildir/cur/ . Evidently there is some step I have omitted to take. I give the output of "sudo doveconf -n" below. The file ~/.dovecot.sieve reads: ------------------------------ # Sieve Filter require ["fileinto","regex","envelope","vacation"]; if header :contains "X-Spam-Flag" "YES" { fileinto "/home/tim/Maildir/.Spam/"; } ------------------------------ When I run "sudo systemctl restart dovecot" I see the line Jul 27 18:54:23 alfred dovecot: master: Dovecot v2.2.10 starting up for imap, pop3, lmtp, sieve (core dumps disabled) in /var/log/maillog Output of "sudo doveconf -n > dovecot.conf" ------------------------------ # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-123.4.4.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Core) listen = * mail_debug = yes mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve ssl = required ssl_cert = References: <140652077.8eX1Maq3as@rose.gayleard.eu> Message-ID: <53D533D4.1070402@localhost.localdomain.org> On 07/27/2014 05:08 PM, Timothy Murphy wrote: > I'm running postfix + dovecot + dovecot-pigeonhole > on my CentOS-7 home server. > I would like spam to finish up in ~/Maildir/.Spam/ . > Spam is being marked, but is not separated - > it ends up with all the other email in ~/Maildir/cur/ . > Evidently there is some step I have omitted to take. > > I give the output of "sudo doveconf -n" below. > The file ~/.dovecot.sieve reads: > ------------------------------ > # Sieve Filter > > require ["fileinto","regex","envelope","vacation"]; > > if header :contains "X-Spam-Flag" "YES" { > fileinto "/home/tim/Maildir/.Spam/"; ^^^^^^^^^^^^^^^^^^^ > } > ------------------------------ Check the example in Dovecot wiki again: http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#Direct_filtering_using_message_header It uses: fileinto "Spam"; > > When I run "sudo systemctl restart dovecot" > I see the line > Jul 27 18:54:23 alfred dovecot: master: Dovecot v2.2.10 starting up > for imap, pop3, lmtp, sieve (core dumps disabled) > in /var/log/maillog > You can enable 'mail_debug=yes" and Dovecot will log some interesting information, for example about your fileinto "/full/path/to/.maildir". Regards, Pascal -- The trapper recommends today: f007ba11.1420819 at localdomain.org From tom at talpey.com Sun Jul 27 18:29:44 2014 From: tom at talpey.com (Tom Talpey) Date: Sun, 27 Jul 2014 14:29:44 -0400 Subject: Dovecot pigeonhole help sought In-Reply-To: <53D533D4.1070402@localhost.localdomain.org> References: <140652077.8eX1Maq3as@rose.gayleard.eu> <53D533D4.1070402@localhost.localdomain.org> Message-ID: <53D54518.6000000@talpey.com> On 7/27/2014 1:16 PM, Pascal Volk wrote: > On 07/27/2014 05:08 PM, Timothy Murphy wrote: >> I'm running postfix + dovecot + dovecot-pigeonhole >> on my CentOS-7 home server. >> I would like spam to finish up in ~/Maildir/.Spam/ . >> Spam is being marked, but is not separated - >> it ends up with all the other email in ~/Maildir/cur/ . >> Evidently there is some step I have omitted to take. >> >> I give the output of "sudo doveconf -n" below. >> The file ~/.dovecot.sieve reads: >> ------------------------------ >> # Sieve Filter >> >> require ["fileinto","regex","envelope","vacation"]; >> >> if header :contains "X-Spam-Flag" "YES" { >> fileinto "/home/tim/Maildir/.Spam/"; > ^^^^^^^^^^^^^^^^^^^ >> } >> ------------------------------ > > Check the example in Dovecot wiki again: > http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#Direct_filtering_using_message_header > > It uses: fileinto "Spam"; I believe you may need a "stop;" directive after the fileinto. Later rules can move the message again, otherwise. Other possibility is that .Spam/ doesn't exist. Enabling autocreate can help if so, or just create it manually. > >> >> When I run "sudo systemctl restart dovecot" >> I see the line >> Jul 27 18:54:23 alfred dovecot: master: Dovecot v2.2.10 starting up >> for imap, pop3, lmtp, sieve (core dumps disabled) >> in /var/log/maillog >> > > You can enable 'mail_debug=yes" and Dovecot will log some interesting > information, for example about your fileinto "/full/path/to/.maildir". > > > Regards, > Pascal > From jcea at jcea.es Sun Jul 27 23:23:31 2014 From: jcea at jcea.es (Jesus Cea) Date: Mon, 28 Jul 2014 01:23:31 +0200 Subject: mdbox "doveadm purge" strategy Message-ID: <53D589F3.1090303@jcea.es> Hi there. I am using mdbox storage with great success but I am seeing something I find strange and I would like to compare notes with you. When doing "doveadm purge", "m.*" files with non deleted messages are left alone, but "m.*" files with deleted messages copy the "non deleted" messages to a newly created "m.*" file and delete the original. Good so far. What surprises me is that the newly created "m.*" files are not fullsize. they can be "small" files, not using the 2MB max size I have configured for mdbox storage. Moreover, those files stay in that size forever, no new messages are appended ever. I guess each old "m.*" file with deleted messages generates a new independent "m.*" containing only the non deleted messages. I wonder if that is the case and if that is a fundamental issue that can't be changed. I would like my "m.*" files to use the full configured mdbox size, instead of having quite a few of new SMALL "m.*" files. Thanks for your time and attention!. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Sun Jul 27 23:30:49 2014 From: jcea at jcea.es (Jesus Cea) Date: Mon, 28 Jul 2014 01:30:49 +0200 Subject: "Corrupted dbox file [...] purging found mismatched offsets" Message-ID: <53D58BA9.2050309@jcea.es> Doing a "doveadm purge" today I got this: """ doveadm(jcea): Error: Corrupted dbox file /home/jcea/.thunderbird/dovecot/storage/m.686 (around offset=1385772): purging found mismatched offsets (1385742 vs 1380664, 185/275) doveadm(jcea): Warning: fscking index file /home/jcea/.thunderbird/dovecot/storage/dovecot.map.index doveadm(jcea): Warning: mdbox /home/jcea/.thunderbird/dovecot/storage: rebuilding indexes doveadm(jcea): Error: Purging namespace '' failed: Internal error occurred. Refer to server log for more information. [2014-07-28 01:17:10] """ Checking the log I get this: """ Jul 28 01:17:18 ubuntu dovecot: imap(jcea): Error: /home/jcea//.thunderbird/dovecot/mailboxes/proveedores/dovecot/DbOx-mAiLs/dovecot.index reset, view is now inconsistent Jul 28 01:17:19 ubuntu dovecot: imap(jcea): Error: /home/jcea//.thunderbird/dovecot/mailboxes/varios/OpenStreetMap/osm-newbies/DbOx-mAiLs/dovecot.index reset, view is now inconsistent Jul 28 01:17:20 ubuntu dovecot: imap(jcea): Error: /home/jcea//.thunderbird/dovecot/mailboxes/varios/esc&AOk-pticos/DbOx-mAiLs/dovecot.index reset, view is now inconsistent """ Subsequent "doveadm purge" don't show anything. What happened and why?. Consequences?. Did I lose email? -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Sun Jul 27 23:34:37 2014 From: jcea at jcea.es (Jesus Cea) Date: Mon, 28 Jul 2014 01:34:37 +0200 Subject: "Corrupted dbox file [...] purging found mismatched offsets" In-Reply-To: <53D58BA9.2050309@jcea.es> References: <53D58BA9.2050309@jcea.es> Message-ID: <53D58C8D.3000900@jcea.es> On 28/07/14 01:30, Jesus Cea wrote: > Doing a "doveadm purge" today I got this: > > """ > doveadm(jcea): Error: Corrupted dbox file I am using Dovecot 2.2.13. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From dovecot-list at mohtex.net Mon Jul 28 02:01:29 2014 From: dovecot-list at mohtex.net (Tamsy) Date: Mon, 28 Jul 2014 09:01:29 +0700 Subject: Dovecot pigeonhole help sought In-Reply-To: <140652077.8eX1Maq3as@rose.gayleard.eu> References: <140652077.8eX1Maq3as@rose.gayleard.eu> Message-ID: <53D5AEF9.4020002@mohtex.net> Timothy Murphy wrote on 28.07.2014 00:08: > I'm running postfix + dovecot + dovecot-pigeonhole > on my CentOS-7 home server. > I would like spam to finish up in ~/Maildir/.Spam/ . > Spam is being marked, but is not separated - > it ends up with all the other email in ~/Maildir/cur/ . > Evidently there is some step I have omitted to take. > > I give the output of "sudo doveconf -n" below. > The file ~/.dovecot.sieve reads: > ------------------------------ > # Sieve Filter > > require ["fileinto","regex","envelope","vacation"]; > > if header :contains "X-Spam-Flag" "YES" { > fileinto "/home/tim/Maildir/.Spam/"; > } > ------------------------------ > > When I run "sudo systemctl restart dovecot" > I see the line > Jul 27 18:54:23 alfred dovecot: master: Dovecot v2.2.10 starting up > for imap, pop3, lmtp, sieve (core dumps disabled) > in /var/log/maillog > > Output of "sudo doveconf -n > dovecot.conf" > ------------------------------ > # 2.2.10: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.0-123.4.4.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Core) > listen = * > mail_debug = yes > mail_location = maildir:~/Maildir > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress > comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify > environment mailbox date ihave > mbox_write_locks = fcntl > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > driver = pam > } > plugin { > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > } > protocols = imap pop3 lmtp sieve > ssl = required > ssl_cert = ssl_key = userdb { > driver = passwd > } > protocol lmtp { > mail_plugins = " sieve" > } > protocol lda { > mail_plugins = " sieve" > } > ------------------------------ > > Any advice or suggestions gratefully received. Simply: require ["fileinto"]; if anyof (header :contains "X-Spam-Flag" "YES") { fileinto "Spam"; stop; } From reuben-dovecot at reub.net Mon Jul 28 02:16:42 2014 From: reuben-dovecot at reub.net (Reuben Farrelly) Date: Mon, 28 Jul 2014 12:16:42 +1000 Subject: [pigeonhole] disregards --with-ldap=no during compilation /usr/ports/mail/dovecot2bra@fsn.hu In-Reply-To: <20140727100056.2fca56af@scorpio> References: <20140727084659.3e66df7f@scorpio> <182E2127-C28A-4C8B-8368-3D98A336C82D@odo.in-berlin.de> <20140727100056.2fca56af@scorpio> Message-ID: <53D5B28A.2000402@reub.net> On 28/07/2014 12:00 AM, Jerry wrote: > On Sun, 27 Jul 2014 14:56:46 +0200, Michael Grimm stated: > >> On 27.07.2014, at 14:46, Jerry wrote: >> I like to have full control over those applications, and sometimes, I want >> to test new features not available in ports, yet. My production system runs >> in a jail with postfix/dovecot/pigeonhole at stable releases, my testing >> jail runs bleeding edge versions. And here I ran into that issue reported >> today. > > I have no idea what "features" you are referring to since you did not list > them. However, I might suggest that either you contact the port maintainer > for dovecot or pigeonhole and express your > concerns to them or , create a separate port which produces the results you > want and then submit it to the FreeBSD ports crew. I have done similar things > in the past and had rather good success with it. There's no point in him contacting the ports maintainer, since he's stated he's running "bleeding edge" builds, obviously direct from Dovecot HG. They probably aren't in the ports tree. For what it's worth, I have the same problem, ie I'm seeing the latest builds in hg fail to compile also, on a Gentoo box. On another system with openldap installed, it compiles through, but on this one without openldap, it fails to compile: libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728 -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-dict -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-dns -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-http -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-mail -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-imap -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-fs -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-charset -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-auth -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-master -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-ssl-iostream -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-compression -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-settings -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-test -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-index -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-storage -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-storage/list -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-storage/index -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/lib-storage/index/raw -I/var/tmp/portage/net-mail/dovecot-2.2.13_p20140728/work/dovecot-2.2.13.p20140728/src/plugins/quota -I../../../.. -I../../../../src/lib-sieve -O0 -g -pipe -march=corei7 -mtune=native -c sieve-ldap-script.c -fPIC -DPIC -o .libs/sieve-ldap-script.o In file included from sieve-ldap-storage.h:11:0, from sieve-ldap-script.c:7: sieve-ldap-db.h:19:18: fatal error: ldap.h: No such file or directory #include ^ compilation terminated. In file included from sieve-ldap-storage.h:11:0, from sieve-ldap-db.c:8: sieve-ldap-db.h:19:18: fatal error: ldap.h: No such file or directory #include ^ compilation terminated. Makefile:517: recipe for target 'sieve-ldap-script.lo' failed Looks like some auto-* magic might be required in hg to not try to build with openldap headers if the headers aren't detected on the system. Reuben From stephan at rename-it.nl Mon Jul 28 07:29:14 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 28 Jul 2014 09:29:14 +0200 Subject: [pigeonhole] disregards --with-ldap=no during compilation In-Reply-To: References: Message-ID: <53D5FBCA.6030808@rename-it.nl> On 7/27/2014 2:21 PM, Michael Grimm wrote: > Hi -- > > I can't get current dovecot and pigeonhole compiled; compilation stops with: > > | sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found > > Ok, because my dovecot isn't compiled with ldap (--without-ldap), I tried to apply "--with-ldap=no" with configure as advertised in the INSTALL file of pigeonhole, but without success: > > [...] > | ./sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found > | #include > | ^ > | 1 error generated. > | gmake[5]: *** [sieve-ldap-db.lo] Error 1 > | gmake[5]: Leaving directory `/usr/local/etc/dovecot/SOURCE/dovecot-2.2-pigeonhole/src/lib-sieve/storage/ldap' > [...] > | gmake: *** [all] Error 2 > > My configure run logfile shows: > > [...] > | config.status: creating src/lib-sieve/storage/ldap/Makefile > [...] > | script drivers . : file dict > | : -ldap > > This happens at FreeBSD-STABLE (clang 3.4.1, gmake 3.82) with dovecot at 2d2d75ac6715 and pigeonhole at 1475892e8cff. > > Any ideas what went wrong? Me not paying attention with adding new features as it seems. > (I'm back to pigeonhole 0.4.3 (1c6130ff5dd6) for the time being.) Fixed: http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/5117ffc8b151 Regards, Stephan. From michael.pierce08 at gmail.com Mon Jul 28 09:01:54 2014 From: michael.pierce08 at gmail.com (Michael Pierce) Date: Mon, 28 Jul 2014 10:01:54 +0100 Subject: Fwd: Disconnected (no auth attempts) In-Reply-To: References: Message-ID: Hi, Firstly, I'd like to apologise if this is really simple or the answers available easily. I have searched and tried to solve this alone but with no success. I'm having an issue with dovecot to which its reporting "Disconnected (no auth attempts)" in the info log file. From what I understand this is usually due to SSL not being enabled (however, ssl = required is in the config). I hope someone can help. I have included config file, and log file information below. Please and Thanks, Michael Pierce ps, apologies if I was supposed to pastebin these, I was not sure. *dovecot -n* # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 3.10.9-xxxx-grs-ipv6-64 x86_64 CentOS release 6.5 (Final) auth_debug_passwords = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 200 info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_gid = 12 mail_uid = 200 passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap ssl = required ssl_cert = References: Message-ID: <53D613FF.2000904@thelounge.net> Am 28.07.2014 11:01, schrieb Michael Pierce: > Firstly, I'd like to apologise if this is really simple or the answers > available easily. I have searched and tried to solve this alone but with > no success. > > I'm having an issue with dovecot to which its reporting "Disconnected (no > auth attempts)" in the info log file. From what I understand this is > usually due to SSL not being enabled (however, ssl = required is in the > config). I hope someone can help. I have included config file, and log > file information below. the client did not make any auth attempt dovecot just logs what is happening mostly when that happens the client is configured for a auth mech like CRAM-MD5 and the server does not support it, so the client connects, get from the server the list of supported auth-mechs and says "hm it don't support what the user configured, bye" > ps, apologies if I was supposed to pastebin these, I was not sure. > *dovecot -n* > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.9-xxxx-grs-ipv6-64 x86_64 CentOS release 6.5 (Final) > auth_debug_passwords = yes > base_dir = /var/run/dovecot/ > disable_plaintext_auth = no > first_valid_uid = 200 > info_log_path = /var/log/dovecot-info.log > log_path = /var/log/dovecot.log > mail_gid = 12 > mail_uid = 200 > passdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > protocols = imap > ssl = required > ssl_cert = ssl_key = userdb { > driver = prefetch > } > userdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > > *dovecot-sql.conf* > driver = mysql > connect = host=/var/run/mysqld/mysqld.sock dbname=mailreader_mail > user=[removed] password=[removed] > default_pass_scheme = SHA512 > password_query = SELECT email as user, password, > 'maildir:/home/mail'||maildir as userdb_mail FROM users WHERE email = '%u' > > dovecot-info.conf > Jul 28 10:58:50 master: Info: Dovecot v2.0.9 starting up (core dumps > disabled) > Jul 28 10:58:59 auth: Debug: Loading modules from directory: > /usr/lib64/dovecot/auth > Jul 28 10:58:59 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libauthdb_ldap.so > Jul 28 10:58:59 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_mysql.so > Jul 28 10:58:59 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_sqlite.so > Jul 28 10:58:59 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libmech_gssapi.so > Jul 28 10:58:59 auth: Debug: auth client connected (pid=22493) > Jul 28 10:59:00 imap-login: Info: Disconnected (no auth attempts): > rip=[removed], lip=[removed] > -- Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofm?hlgasse 17 CTO / CISO / Software-Development m: +43 (676) 40 221 40, p: +43 (1) 595 3999 33 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From simon.gareste at gareste.fr Mon Jul 28 07:44:53 2014 From: simon.gareste at gareste.fr (Simon Gareste) Date: Mon, 28 Jul 2014 09:44:53 +0200 Subject: Segfault dovecot 2.2.9 Message-ID: <53D5FF75.9020906@gareste.fr> Hi all, When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped) Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped) Looking at syslog, I see doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] I tried but couldn't find the core dump anywhere on the server. Any help on this would be appreciated too. I (trying to ) run it with postfix, on an Ubuntu 14.04 (Linux mail2.arturia.com 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux), brand new server. What troubles me even more is that I just set up successfully another mail server a week ago, with the same configuration (diffing the conf folders) except for log or mailbox paths (driver and stuff are the same). In the google search I've done, I saw some stuff about openssl: both servers are running 1.0.1f, since one is running fine, I guess this is not the culprit. One difference I noticed between the two servers is that on the failing one, there is no /var/run/dovecot. I presume this folder and its files are created once dovecot is launched, so that's why it's not present, and is only a symptom of the failure, not a cause? Thanks for your help, and please tell me what other information I could provide to help. Simon From h.reindl at thelounge.net Mon Jul 28 10:14:15 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 28 Jul 2014 12:14:15 +0200 Subject: Segfault dovecot 2.2.9 In-Reply-To: <53D5FF75.9020906@gareste.fr> References: <53D5FF75.9020906@gareste.fr> Message-ID: <53D62277.6090702@thelounge.net> Am 28.07.2014 09:44, schrieb Simon Gareste: > When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line > (simply execute 'dovecot') results in the error message: > Segmentation fault (core dumped) > > Trying dovecot -n results in pretty much the same: > # 2.2.9: /etc/dovecot/dovecot.conf > Segmentation fault (core dumped) > > Looking at syslog, I see > doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] current is 2.2.13 so don't report problems with a outdated version instead just upgrade - there where bugfixes between 2.2.9 and 2.2.13 in context of segfaults here and there -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From h.reindl at thelounge.net Mon Jul 28 10:21:33 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 28 Jul 2014 12:21:33 +0200 Subject: Segfault dovecot 2.2.9 In-Reply-To: <53D5FF75.9020906@gareste.fr> References: <53D5FF75.9020906@gareste.fr> Message-ID: <53D6242D.80807@thelounge.net> Am 28.07.2014 09:44, schrieb Simon Gareste: > One difference I noticed between the two servers is that on the failing one, there is > no /var/run/dovecot. I presume this folder and its files are created once dovecot is > launched, so that's why it's not present, and is only a symptom of the failure, > not a cause? no, it is supposed to be created by package install and on modern systems where /var/run is a symlink to /run which is a tmpfs everytime at boot [root at mail:~]$ cat /usr/lib/tmpfiles.d/dovecot.conf d /run/dovecot 0755 root dovecot - -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From simon.gareste at gareste.fr Mon Jul 28 10:33:44 2014 From: simon.gareste at gareste.fr (Simon Gareste) Date: Mon, 28 Jul 2014 12:33:44 +0200 Subject: Segfault dovecot 2.2.9 In-Reply-To: <53D62277.6090702@thelounge.net> References: <53D5FF75.9020906@gareste.fr> <53D62277.6090702@thelounge.net> Message-ID: <53D62708.6010402@gareste.fr> Le 28/07/2014 12:14, Reindl Harald a ?crit : > Am 28.07.2014 09:44, schrieb Simon Gareste: >> When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line >> (simply execute 'dovecot') results in the error message: >> Segmentation fault (core dumped) >> >> Trying dovecot -n results in pretty much the same: >> # 2.2.9: /etc/dovecot/dovecot.conf >> Segmentation fault (core dumped) >> >> Looking at syslog, I see >> doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] > current is 2.2.13 > > so don't report problems with a outdated version instead > just upgrade - there where bugfixes between 2.2.9 and > 2.2.13 in context of segfaults here and there > Thank you. This outdated version is the one packaged in Ubuntu LTS 14.04.1, which I believe I'm not the only one using. Updating the dovecot packages provided by Ubuntu would certainly help. I understand that the version I'm using is roughly 9 months old, but then the LTS was released 3 months ago, why doesn't it include the 2.2.11 or 2.2.12? And I found the solution in the end, the problem comes from auth_debug_passwords=yes being the right thing, and auth_debug_passwords=plain being source of segfault. I don't know where I got the "plain" value in the first place, but I certainly should have read more carefully some docs. I also don't know if this was fixed later, but shouldn't there be a verification on some values of some variables, when there are limited values to which they can be defined? Anyway, dovecot is running, all my apologizes for the unwanted spam. Simon From h.reindl at thelounge.net Mon Jul 28 10:40:12 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 28 Jul 2014 12:40:12 +0200 Subject: Segfault dovecot 2.2.9 In-Reply-To: <53D62708.6010402@gareste.fr> References: <53D5FF75.9020906@gareste.fr> <53D62277.6090702@thelounge.net> <53D62708.6010402@gareste.fr> Message-ID: <53D6288C.5080701@thelounge.net> Am 28.07.2014 12:33, schrieb Simon Gareste: > Le 28/07/2014 12:14, Reindl Harald a ?crit : >> Am 28.07.2014 09:44, schrieb Simon Gareste: >>> When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line >>> (simply execute 'dovecot') results in the error message: >>> Segmentation fault (core dumped) >>> >>> Trying dovecot -n results in pretty much the same: >>> # 2.2.9: /etc/dovecot/dovecot.conf >>> Segmentation fault (core dumped) >>> >>> Looking at syslog, I see >>> doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in >>> libc-2.19.so[7fbb93c04000+1bc000] >> current is 2.2.13 >> >> so don't report problems with a outdated version instead >> just upgrade - there where bugfixes between 2.2.9 and >> 2.2.13 in context of segfaults here and there >> > Thank you. This outdated version is the one packaged in Ubuntu > LTS 14.04.1, which I believe I'm not the only one using that's the problem with all that LTS packages nobody knows what fixes they may have backported and what are missing, so the version number no longer says anything which makes it also impossible for the upstream developer to know the patchlevel that's why i build packages for server software the last 7 years on my own infrastructure from upstream sources Updating the dovecot packages provided by Ubuntu would certainly help. I understand that the version I'm > using is roughly 9 months old, but then the LTS was released 3 months ago, why doesn't it include the 2.2.11 or > 2.2.12? > > And I found the solution in the end, the problem comes from auth_debug_passwords=yes being the right thing, and > auth_debug_passwords=plain being source of segfault. I don't know where I got the "plain" value in the first place, > but I certainly should have read more carefully some docs. I also don't know if this was fixed later, but shouldn't > there be a verification on some values of some variables, when there are limited values to which they can be defined? http://comments.gmane.org/gmane.mail.imap.dovecot/76231 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From nick.z.edwards at gmail.com Mon Jul 28 11:09:01 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Mon, 28 Jul 2014 21:09:01 +1000 Subject: Multiple servers and NFS In-Reply-To: <53D26761.1080109@sys4.de> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> <53D1E3EA.5040705@walnut.gen.nz> <53D265CE.2000108@freedominterface.org> <53D26761.1080109@sys4.de> Message-ID: On 7/26/14, Robert Schetterer wrote: > Am 25.07.2014 um 16:12 schrieb Eduardo Ramos: >> I did not understand what the advantage of use dovecot LMTP with >> director too. > > in "very short" words... > with nfs ,the director should avoid concurrent events > which may happen with lmtp too, depending to multiple server setup > A few of us run large NFS based systems without director, however mostly 99% pop3, not using director on imap has little impact either from our tests, remember, director is only a couple years at most old, people have been doing NFS mailstorage for decades, and with relation to dovecot, ten years or so, the sky never collapsed back then, it hasnt now either thus far :-> using director was considered in risk assessment as its another point of failure, and weighed against its claimed benefit, the decision was made its not justified. note: we dont use lmtp, each mx mounts/stores directly to EMC storgage with dovecot-lda, 14 front ends = 14 direct storages, sure, means dovecot needs to be installed on each mx (but not listening), but it eliminates the need for dedicated back ends to send to, each mx is that backend. 12 pop3 servers, of note however, we use index:memory on pop3 and smtp's mail_location = maildir:/mail/%1n/%1.1n/%2.1n/%n/Maildir:INDEX=MEMORY only 3 imaps one of which is webmail, and of course we do not use index:memory on them, these are behind real (serveriron's) load balancers, so if using pretend load balancers :-> YMMV From rs at sys4.de Mon Jul 28 11:26:02 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 28 Jul 2014 13:26:02 +0200 Subject: Multiple servers and NFS In-Reply-To: References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> <53D1E3EA.5040705@walnut.gen.nz> <53D265CE.2000108@freedominterface.org> <53D26761.1080109@sys4.de> Message-ID: <53D6334A.2070702@sys4.de> Am 28.07.2014 um 13:09 schrieb Nick Edwards: > On 7/26/14, Robert Schetterer wrote: >> Am 25.07.2014 um 16:12 schrieb Eduardo Ramos: >>> I did not understand what the advantage of use dovecot LMTP with >>> director too. >> >> in "very short" words... >> with nfs ,the director should avoid concurrent events >> which may happen with lmtp too, depending to multiple server setup >> > > A few of us run large NFS based systems without director, however > mostly 99% pop3, not using director on imap has little impact either > from our tests, remember, director is only a couple years at most old, > people have been doing NFS mailstorage for decades, and with relation > to dovecot, ten years or so, the sky never collapsed back then, it > hasnt now either thus far :-> > using director was considered in risk assessment as its another point > of failure, and weighed against its claimed benefit, the decision was > made its not justified. > > note: we dont use lmtp, each mx mounts/stores directly to EMC storgage > with dovecot-lda, 14 front ends = 14 direct storages, sure, means > dovecot needs to be installed on each mx (but not listening), but it > eliminates the need for dedicated back ends to send to, each mx is > that backend. > > 12 pop3 servers, of note however, we use index:memory on pop3 and smtp's > > mail_location = maildir:/mail/%1n/%1.1n/%2.1n/%n/Maildir:INDEX=MEMORY > > only 3 imaps one of which is webmail, and of course we do not use > index:memory on them, these are behind real (serveriron's) load > balancers, so if using pretend load balancers :-> YMMV > That looks fine but now whats the problem ? For sure there are many ways to goal. do what you like. I also have no director setup using cluster file systems with loadbalancers working fine. Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From trashcan at odo.in-berlin.de Mon Jul 28 13:53:32 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Mon, 28 Jul 2014 15:53:32 +0200 Subject: [pigeonhole] disregards =?UTF-8?Q?--with-ldap=3Dno=20during?= =?UTF-8?Q?=20compilation?= In-Reply-To: <53D5FBCA.6030808@rename-it.nl> References: <53D5FBCA.6030808@rename-it.nl> Message-ID: <3be8f620d7606d5086cd186d42f9b942@mx1.enfer-du-nord.net> On 2014-07-28 9:29, Stephan Bosch wrote: > On 7/27/2014 2:21 PM, Michael Grimm wrote: >> I can't get current dovecot and pigeonhole compiled; compilation stops >> with: >> >> | sieve-ldap-db.h:19:10: fatal error: 'ldap.h' file not found > Fixed: > > http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/5117ffc8b151 Yep. I can confirm that "--wiht-ldap=no" is regarded, now. Thanks and regards, Michael From tss at iki.fi Mon Jul 28 14:25:28 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 28 Jul 2014 17:25:28 +0300 Subject: After upgrade from 2.1 to 2.2.13 clients can create folders with names containing slash character on a Linux system In-Reply-To: <53D1188E.6070303@icdsoft.com> References: <53D1188E.6070303@icdsoft.com> Message-ID: <4B64977A-45F5-49E5-A050-232FB98FBD4E@iki.fi> On 24 Jul 2014, at 17:30, David Davidov wrote: > We have following issue: After upgrade from 2.1 to 2.2.13 clients can create folders with names containing slash character. > This was not possible with our previous version 2.1. Tested. Oops, fixed: http://hg.dovecot.org/dovecot-2.2/rev/4b8a098a70b7 From tss at iki.fi Mon Jul 28 14:29:59 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 28 Jul 2014 17:29:59 +0300 Subject: Multiple servers and NFS In-Reply-To: <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <1648231143.548013.1406221747457.JavaMail.zimbra@schultheiss.fr> Message-ID: <53FAC032-C8C4-40F4-BE12-C882AA4D6923@iki.fi> On 24 Jul 2014, at 20:09, Nathan Schultheiss wrote: > When I go on Roundcube with a mailbox who I've 96000 in the INBOX "cur" folder, the first time I need 1 minutes waiting. > The second time it's a little more quick 10 seconds... But when I go back again (after a few hours) it's slow again... And we'are just 5 users at the moment for test... See if maildir_very_dirty_syncs=yes helps. From tss at iki.fi Mon Jul 28 14:35:36 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 28 Jul 2014 17:35:36 +0300 Subject: ACLs on Top level mailboxes. In-Reply-To: References: Message-ID: On 24 Jul 2014, at 01:22, Dan Carroll wrote: > I?m in the process of migrating a mail server to new hardware. At the same time, I?ve made the decision to switch from courier to dovecot (v2.2.13) and from what I have seen so far I?m pretty happy. > I have two questions for the list. > > I?d like my users mailboxes (Maildir format) to look like this: > > Inbox > UserCreatedSubFolder1 > UserCreatedSubFolder2 > ? > Sent > UserCreatedSubFolder3 > Drafts > Trash > Junk > Archives > > > The Top level folders (Sent, Drafts etc) are all ?Special? and I do not wish the users to be able to delete them. > I also don?t want them to create new Top level folders. > > This will force all custom folders to be under a Top Level folder. .. > I also tried some global-acl file settings but I could not make that work either. I think global ACL file would work. Use something like: * INBOX.* (I don't remember the rights strings exactly now.) > My second question relates to migration. Is it enough that I copy the Maildir structure and simply delete the courier files or is it a lot better to use a courier->dovecot migration tool? > I realise folder subscriptions would be lost but that?s OK, I?ll recreate them manually anyway. IMAP clients will redownload their local mail cache if you don't use migration tool. Doesn't necessarily matter with few users. From tss at iki.fi Mon Jul 28 14:51:27 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 28 Jul 2014 17:51:27 +0300 Subject: Multiple passwords with sql authentication In-Reply-To: <53CFD997.9030708@fantas.in> References: <53CFD997.9030708@fantas.in> Message-ID: On 23 Jul 2014, at 18:49, BlackVoid wrote: > I'm currently working on a control panel which is using postfix, dovecot > and other applications and I want to add application specific passwords > to increase security. > > I found one solution [1], however it requires the password to be > included in the query which is something I do not want to do, because > the query may be written in clear-text to log-files. So I'm wondering if > there is a way to have multiple passwords with dovecot without risking > passwords being leakied in clear-text to log-files. There's an old patch to support this, but it was never finished: http://dovecot.org/patches/2.0/auth-multi-password-2.0.diff I had a newer idea about encoding the passwords into a single field, such as {MULTI}hash1:hash2:hash3 but that doesn't exist either yet. For now the only possibility would be to create multiple passdbs, each one returning a different password field. That could work if you have only a couple of different passwords. From juanpablo83 at openmailbox.org Mon Jul 28 17:58:21 2014 From: juanpablo83 at openmailbox.org (Juan Pablo) Date: Mon, 28 Jul 2014 17:58:21 +0000 Subject: identify MUA =?UTF-8?Q?connecting=3F?= Message-ID: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> Hello I am using dovecot 1.2.15 on ubuntu. Is it possible to somehow log the MUA information that is connecting to Dovecot? The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones. From h.reindl at thelounge.net Mon Jul 28 18:14:32 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 28 Jul 2014 20:14:32 +0200 Subject: identify MUA connecting? In-Reply-To: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> Message-ID: <53D69308.8090307@thelounge.net> Am 28.07.2014 19:58, schrieb Juan Pablo: > Hello I am using dovecot 1.2.15 on ubuntu. > > Is it possible to somehow log the MUA information that is connecting to Dovecot? > > The reason I am wanting to do this is I would like to know if people are getting their email on personal devices > instead of work secured / standardized phones from where should that information come? dovecot has IP, auth-method, username, passwword, TLS that is logged - there is no more information available grep the logs and analyze IP's reslove the PTR's and you get some useful informations -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From juanpablo83 at openmailbox.org Mon Jul 28 18:26:24 2014 From: juanpablo83 at openmailbox.org (Juan Pablo) Date: Mon, 28 Jul 2014 18:26:24 +0000 Subject: identify MUA =?UTF-8?Q?connecting=3F?= In-Reply-To: <53D69308.8090307@thelounge.net> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> Message-ID: <9500589947b436c837034316ea1e0762@openmailbox.org> On 2014-07-28 18:14, Reindl Harald wrote: > from where should that information come? That is what I was not sure. I did not know what information was possible available. I was thinking or hoping something same as http logs > dovecot has IP, auth-method, username, passwword, TLS > that is logged - there is no more information available I see unfortunate but thank you for this information > grep the logs and analyze IP's > reslove the PTR's and you get some useful informations not of use as their business device can be used from home where also their personal device may be From user+dovecot at localhost.localdomain.org Mon Jul 28 18:38:28 2014 From: user+dovecot at localhost.localdomain.org (Pascal Volk) Date: Mon, 28 Jul 2014 18:38:28 +0000 Subject: identify MUA connecting? In-Reply-To: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> Message-ID: <53D698A4.6040500@localhost.localdomain.org> On 07/28/2014 05:58 PM, Juan Pablo wrote: > Hello I am using dovecot 1.2.15 on ubuntu. UPGRADE! Dovecot < 2.x is no longer supported. > Is it possible to somehow log the MUA information that is connecting to > Dovecot? In the Dovecot v2.0 tree there was the following commit: changeset: 9123:edcafb3efbbf branch: HEAD user: Timo Sirainen date: Thu Apr 16 19:14:23 2009 -0400 summary: Added imap_idle_notify_interval setting. Some time later in the v2.1 tree there was fix: changeset: 14197:32ffa616f249 user: Timo Sirainen date: Sat Feb 25 07:29:15 2012 +0200 summary: imap-login: imap_id_* settings were ignored pre-login. So, if you would use Dovecot v2.1.x you would be able to log some information about the connected client. BUT not all mail clients are supporting RFC2971 [http://tools.ietf.org/html/rfc2971]. The settings for this feature are configured in conf.d/20-imap.conf: * imap_id_log * imap_id_send > The reason I am wanting to do this is I would like to know if people are > getting their email on personal devices instead of work secured / > standardized phones. That depends on the used software, see above Regards, Pascal -- The trapper recommends today: beeffeed.1420920 at localdomain.org From user+dovecot at localhost.localdomain.org Mon Jul 28 18:50:12 2014 From: user+dovecot at localhost.localdomain.org (Pascal Volk) Date: Mon, 28 Jul 2014 18:50:12 +0000 Subject: identify MUA connecting? In-Reply-To: <53D698A4.6040500@localhost.localdomain.org> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D698A4.6040500@localhost.localdomain.org> Message-ID: <53D69B64.4050107@localhost.localdomain.org> On 07/28/2014 06:38 PM, Pascal Volk wrote: > In the Dovecot v2.0 tree there was the following commit: > > changeset: 9123:edcafb3efbbf > branch: HEAD > user: Timo Sirainen > date: Thu Apr 16 19:14:23 2009 -0400 > summary: Added imap_idle_notify_interval setting. > ? Oops, that was the wrong one. :-) Bad grep-voodoo, sorry. So you will need Dovecot v2.1.1 at least. Regards, Pascal -- The trapper recommends today: beeffeed.1420920 at localdomain.org From rick at havokmon.com Mon Jul 28 18:57:27 2014 From: rick at havokmon.com (Rick Romero) Date: Mon, 28 Jul 2014 13:57:27 -0500 Subject: identify MUA connecting? In-Reply-To: <53D69308.8090307@thelounge.net> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> Message-ID: <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> Quoting Reindl Harald : > Am 28.07.2014 19:58, schrieb Juan Pablo: >> Hello I am using dovecot 1.2.15 on ubuntu. >> >> Is it possible to somehow log the MUA information that is connecting to >> Dovecot? >> >> The reason I am wanting to do this is I would like to know if people >> are getting their email on personal devices >> instead of work secured / standardized phones > > from where should that information come? > > dovecot has IP, auth-method, username, passwword, TLS > that is logged - there is no more information available > > grep the logs and analyze IP'sreslove the PTR's and you get some useful > informations IMHO, client certificates would work work well here.? I think Dovecot supports it. Rick From nima at ikp.uni-koeln.de Mon Jul 28 19:08:43 2014 From: nima at ikp.uni-koeln.de (Nima Saed-Samii) Date: Mon, 28 Jul 2014 21:08:43 +0200 Subject: Migration from mbox/maildir++ to mdbox Message-ID: <1406574523.23832.14.camel@vimes.ikp.uni-koeln.de> Dear list, dovecot version: 2.1.7 I have an old mail server that uses mboxes for the INBOX and maildirs for subfolders. I want to migrate our mail handling to a new setup using mdboxes for everything. The current config looks like this: # 2.1.7: /etc/dovecot/dovecot.conf doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1127) # OS: Linux 3.2.0-0.bpo.4-686-pae i686 Debian 6.0.10 auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 114 log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = mbox:~/Mail/MBox:INBOX=/var/mail/%u mail_max_userip_connections = 30 mail_privileged_group = mail namespace { hidden = yes inbox = yes list = no location = prefix = "#mbox/" separator = / } namespace { location = maildir:~/Mail/Maildir prefix = separator = / } passdb { args = dovecot driver = pam } protocols = imap service auth { client_limit = 1024 user = root } service imap-login { inet_listener imap { port = 0 } process_limit = 1024 } ssl_cert = References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> Message-ID: <53D6A166.8070804@thelounge.net> Am 28.07.2014 20:57, schrieb Rick Romero: > Quoting Reindl Harald : > >> Am 28.07.2014 19:58, schrieb Juan Pablo: >>> Hello I am using dovecot 1.2.15 on ubuntu. >>> >>> Is it possible to somehow log the MUA information that is connecting to >>> Dovecot? >>> >>> The reason I am wanting to do this is I would like to know if people >>> are getting their email on personal devices >>> instead of work secured / standardized phones >> >> from where should that information come? >> >> dovecot has IP, auth-method, username, passwword, TLS >> that is logged - there is no more information available >> >> grep the logs and analyze IP'sreslove the PTR's and you get some useful >> informations > > IMHO, client certificates would work work well here. I think Dovecot > supports it yes, but you accept them or not that's a different story than "log the MUA information" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From pch at myzel.net Mon Jul 28 20:40:48 2014 From: pch at myzel.net (Peter Chiochetti) Date: Mon, 28 Jul 2014 22:40:48 +0200 Subject: identify MUA connecting? In-Reply-To: <53D6A166.8070804@thelounge.net> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> <53D6A166.8070804@thelounge.net> Message-ID: <53D6B550.3050007@myzel.net> Am 2014-07-28 um 21:15 schrieb Reindl Harald: > Am 28.07.2014 20:57, schrieb Rick Romero: >>> Am 28.07.2014 19:58, schrieb Juan Pablo: >>>> The reason I am wanting to do this is I would like to know if people >>>> are getting their email on personal devices >>>> instead of work secured / standardized phones >> >> IMHO, client certificates would work work well here. I think Dovecot >> supports it > > yes, but you accept them or not > that's a different story than "log the MUA information" Yes, it is a means to stop people from using insecure devices. So possibly a useful hint the OP may be interested in! Might well be that its the reason for learning which MUA was used? -- peter From fxmulder at gmail.com Mon Jul 28 21:43:29 2014 From: fxmulder at gmail.com (James Devine) Date: Mon, 28 Jul 2014 16:43:29 -0500 Subject: doveadm json formatter Message-ID: Any thoughts to adding a json formatter to the doveadm output? From blackvoid+dovecot at fantas.in Mon Jul 28 22:12:37 2014 From: blackvoid+dovecot at fantas.in (BlackVoid) Date: Tue, 29 Jul 2014 00:12:37 +0200 Subject: Multiple passwords with sql authentication In-Reply-To: References: <53CFD997.9030708@fantas.in> Message-ID: <53D6CAD5.8040006@fantas.in> On 2014-07-28 16:51, Timo Sirainen wrote: > On 23 Jul 2014, at 18:49, BlackVoid wrote: > >> I'm currently working on a control panel which is using postfix, dovecot >> and other applications and I want to add application specific passwords >> to increase security. >> >> I found one solution [1], however it requires the password to be >> included in the query which is something I do not want to do, because >> the query may be written in clear-text to log-files. So I'm wondering if >> there is a way to have multiple passwords with dovecot without risking >> passwords being leakied in clear-text to log-files. > > There's an old patch to support this, but it was never finished: http://dovecot.org/patches/2.0/auth-multi-password-2.0.diff > > I had a newer idea about encoding the passwords into a single field, such as {MULTI}hash1:hash2:hash3 but that doesn't exist either yet. > > For now the only possibility would be to create multiple passdbs, each one returning a different password field. That could work if you have only a couple of different passwords. > Well that's unfortunate. Looks like I have to scrap the idea until either the old patch or your idea is implemented. I don't think having multiple passdbs is a choice, because the amount of application specific passwords a user can have is not finite. Thanks for the help though. From h.reindl at thelounge.net Mon Jul 28 22:49:37 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 29 Jul 2014 00:49:37 +0200 Subject: identify MUA connecting? In-Reply-To: <53D6B550.3050007@myzel.net> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> <53D6A166.8070804@thelounge.net> <53D6B550.3050007@myzel.net> Message-ID: <53D6D381.9040402@thelounge.net> Am 28.07.2014 22:40, schrieb Peter Chiochetti: > Am 2014-07-28 um 21:15 schrieb Reindl Harald: >> Am 28.07.2014 20:57, schrieb Rick Romero: >>>> Am 28.07.2014 19:58, schrieb Juan Pablo: >>>>> The reason I am wanting to do this is I would like to know if people >>>>> are getting their email on personal devices >>>>> instead of work secured / standardized phones >>> >>> IMHO, client certificates would work work well here. I think Dovecot >>> supports it >> >> yes, but you accept them or not >> that's a different story than "log the MUA information" > > Yes, it is a means to stop people from using insecure devices. a client certificate hadrly makes a device secure if the device is compromised your cert is gone > So possibly a useful hint the OP may be interested in! Might well be that > its the reason for learning which MUA was used? well, "what client is used" is impossible there is no user-agent like HTTP and even for HTTP the header is not mandatory and rqeuire it will break your web-app for anybody who cares for privacy while gain nothing -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From kabelpada at kabelmail.de Mon Jul 28 23:42:06 2014 From: kabelpada at kabelmail.de (Daniel Parthey) Date: Tue, 29 Jul 2014 01:42:06 +0200 Subject: Segfault dovecot 2.2.9 In-Reply-To: <53D62708.6010402@gareste.fr> References: <53D5FF75.9020906@gareste.fr> <53D62277.6090702@thelounge.net> <53D62708.6010402@gareste.fr> Message-ID: <20140728234206.GA30594@daniel.localdomain> Simon Gareste wrote: > This outdated version is the one packaged in Ubuntu LTS 14.04.1, > which I believe I'm not the only one using. Updating the dovecot packages > provided by Ubuntu would certainly help. If Ubuntu packages segfault, you should file a bug report at Ubuntu Launchpad: https://help.ubuntu.com/community/ReportingBugs Regards Daniel From kabelpada at kabelmail.de Mon Jul 28 23:59:17 2014 From: kabelpada at kabelmail.de (Daniel Parthey) Date: Tue, 29 Jul 2014 01:59:17 +0200 Subject: Multiple servers and NFS In-Reply-To: References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> <53D1E3EA.5040705@walnut.gen.nz> <53D265CE.2000108@freedominterface.org> <53D26761.1080109@sys4.de> Message-ID: <20140728235917.GA32411@daniel.localdomain> Nick Edwards wrote: > On 7/26/14, Robert Schetterer wrote: > > Am 25.07.2014 um 16:12 schrieb Eduardo Ramos: > >> I did not understand what the advantage of use dovecot LMTP with > >> director too. > > > > in "very short" words... > > with nfs ,the director should avoid concurrent events > > which may happen with lmtp too, depending to multiple server setup > > using director was considered in risk assessment as its another point > of failure, and weighed against its claimed benefit, the decision was > made its not justified. > > mail_location = maildir:/mail/%1n/%1.1n/%2.1n/%n/Maildir:INDEX=MEMORY With maildir you won't have data-loss without the director, since the index files are auto-regenerated without any problem. With mdbox on NFS and no director, you will have data-loss sooner or later: http://wiki2.dovecot.org/MailboxFormat/dbox One of the main reasons for dbox's high performance is that it uses Dovecot's index files as the only storage for message flags and keywords, so the indexes don't have to be "synchronized". Dovecot trusts that they're always up-to-date (unless it sees that something is clearly broken). This also means that you must not lose the dbox index files, they can't be regenerated without data loss. Regards Daniel From jcea at jcea.es Tue Jul 29 00:06:43 2014 From: jcea at jcea.es (Jesus Cea) Date: Tue, 29 Jul 2014 02:06:43 +0200 Subject: "Corrupted dbox file [...] purging found mismatched offsets" In-Reply-To: <20140728232120.GA29716@daniel.localdomain> References: <53D58BA9.2050309@jcea.es> <20140728232120.GA29716@daniel.localdomain> Message-ID: <53D6E593.5040707@jcea.es> On 29/07/14 01:21, Daniel Parthey wrote: > Are you using dovecot director and a shared filesystem like NFS? > > You not only need to run imap and pop3 service via director, > but also the doveadm service, otherwise different hosts might > access the mdbox simultaneously, which will corrupt your index > files and you will lose flags. No, this is a dovecot server running in my own laptop. I guess some computer crash left the mail in an inconsistent state, and I need to assert the extend of the problem. A well designed system should not lose email, even when crashes are involved. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From kabelpada at kabelmail.de Tue Jul 29 00:07:16 2014 From: kabelpada at kabelmail.de (Daniel Parthey) Date: Tue, 29 Jul 2014 02:07:16 +0200 Subject: Error after Upgrade In-Reply-To: <53D23288.3060303@jkart.de> References: <53D22225.6030903@jkart.de> <53D22578.6000609@thelounge.net> <53D22826.3000701@jkart.de> <53D22DF5.5060206@thelounge.net> <53D23288.3060303@jkart.de> Message-ID: <20140729000716.GA741@daniel.localdomain> Hi Jim, Jim Knuth wrote: > Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) You should try to get a core dump and a gdb backtrace with debug symbols package installed. The following article describes how to get one: http://www.dovecot.org/bugreport.html Regards Daniel From ben at indietorrent.org Tue Jul 29 00:36:35 2014 From: ben at indietorrent.org (Ben Johnson) Date: Mon, 28 Jul 2014 20:36:35 -0400 Subject: Exit status code 134; what is it, in the context of Dovecot Antispam plug-in? Message-ID: <53D6EC93.8000503@indietorrent.org> Hello! I just migrated from Ubuntu 12.04 LTS to 14.04 LTS and thereby from Dovecot 2.0.19 to 2.2.9. I've been using dovecot-antispam plugin with great success for the past year with 2.0.19, but after this migration, I've been seeing the exit status code 134 in the syslog when attempting to debug the Dovecot Antispam plugin not working after the migration. I have some debugging output in my pipe script; the output looks something like this: Copying message contents to temporary file for debugging purposes; file is: /tmp/sendmail-msg-7662.txt Checking if the command-line input argument string (--spam) contains the string "ham" or "spam" Mode is "SPAM" Calling (as user vmail) '/usr/lib/dovecot/deliver -d "sa-training at example.com" -m "Training.SPAM" -p "/tmp/sendmail-msg-7662.txt"' Exit status was 134 Yet, I'm able to copy the above command and execute it manually, via the command-line, and it works (and by "works", I mean to say that the behavior is correct and exactly as expected; I receive the "Spam" email at the designated mailbox). Here's how I'm calling it when it works perfectly well (as "root"): # su -c '/usr/lib/dovecot/deliver -d "sa-training at example.com" -m "Training.HAM" -p "/tmp/sendmail-msg-7460.txt"' vmail Any idea what status 134 might be or how to work around it? It looks to be some kind of "temporary failure exception", but that is less than informative in this context. "doveconf -n" output is appended. Thanks for any help! -Ben # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-32-generic x86_64 Ubuntu 14.04.1 LTS auth_mechanisms = plain login disable_plaintext_auth = no listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_privileged_group = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /bin/bash antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_rule2 = Trash:storage=+100M quota_rule3 = Junk:ignore quota_rule4 = INBOX:storage=+100M quota_warning = storage=100%% quota-reached 100 %u %d quota_warning2 = storage=95%% quota-warning 95 %u %d quota_warning3 = storage=80%% quota-warning 80 %u %d quota_warning4 = -storage=100%% quota-below below %u %d sieve = /var/vmail/%d/%n/.sieve } postmaster_address = postmaster at example.com protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service config { unix_listener config { group = vmail mode = 0600 user = vmail } } service imap-login { client_limit = 1000 process_limit = 500 } service quota-below { executable = script /usr/local/bin/quota-below.sh unix_listener quota-below { group = vmail mode = 0666 user = vmail } user = vmail } service quota-reached { executable = script /usr/local/bin/quota-reached.sh unix_listener quota-reached { group = vmail mode = 0666 user = vmail } user = vmail } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0666 user = vmail } user = vmail } ssl_cert = References: <140652077.8eX1Maq3as@rose.gayleard.eu> Message-ID: <20140729004122.GA3738@daniel.localdomain> Timothy Murphy wrote: > I'm running postfix + dovecot + dovecot-pigeonhole > on my CentOS-7 home server. > I would like spam to end up in ~/Maildir/.Spam/ . > Spam is being marked, but is not separated - > it ends up with all the other email in ~/Maildir/cur/ . > Evidently there is some step I have omitted to take. You need to pass your mail through dovecot-lda or lmtp in order to make the SIEVE filters work. Postfix may not write directly to ~/Maildir/cur/. Regards Daniel From jtam.home at gmail.com Tue Jul 29 01:06:26 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Mon, 28 Jul 2014 18:06:26 -0700 (PDT) Subject: identify MUA connecting? In-Reply-To: References: Message-ID: Juan Pablo writes: > That is what I was not sure. I did not know what information was > possible available. I was thinking or hoping something same as http logs My dovecot 2 installation logs this information. E.g. Jul 26 07:13:02 server dovecot: imap(user): ID sent: name=iPad Mail, version=11D201, os=iOS, os-version=7.1.1 (11D201) Jul 26 07:13:38 server dovecot: imap-login: ID sent: name=com.google.android.email, os=android, os-version=4.4.4; KTU84P, vendor=LGE, x-android-device-model=Nexus 4, x-android-mobile-net-operator=Koodo, AGUID=...: user=<>, rip={client-ip}, lip={server-ip}, TLS, session= If you want this info, upgrade, as a later poster suggests. Joseph Tam From dovecot-list at mohtex.net Tue Jul 29 03:10:51 2014 From: dovecot-list at mohtex.net (Tamsy) Date: Tue, 29 Jul 2014 10:10:51 +0700 Subject: dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b Message-ID: <53D710BB.2050007@mohtex.net> Just a report to Stephan: I tried to compile two builds from the Mercurial: - dovecot-2-2-pigeonhole-92405f753f6a - dovecot-2-2-pigeonhole-77e6a42bff9b Both builds fail to compile with the same following error: ---------------- 8< ---------------- ../../src/lib-sieve-tool/.libs/libsieve-tool.a(sieve-tool.o): In function `sieve_tool_open_output_stream': /usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/lib-sieve-tool/sieve-tool.c:518: undefined reference to `o_stream_create_fd_autoclose' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `i_stream_create_fd_autoclose' collect2: ld returned 1 exit status make[3]: *** [sievec] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/sieve-tools' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b' make: *** [all] Error 2 Server OS: 2 servers, both running on Ubuntu 10.04 32 Bit Rgds Tamsy From frank at moltke28.B.Shuttle.DE Tue Jul 29 07:08:00 2014 From: frank at moltke28.B.Shuttle.DE (Frank Elsner) Date: Tue, 29 Jul 2014 09:08:00 +0200 Subject: identify MUA connecting? In-Reply-To: <53D6D381.9040402@thelounge.net> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> <53D6A166.8070804@thelounge.net> <53D6B550.3050007@myzel.net> <53D6D381.9040402@thelounge.net> Message-ID: <20140729090800.7b71264fbb506009227a8a1b@moltke28.B.Shuttle.DE> On Tue, 29 Jul 2014 00:49:37 +0200 Reindl Harald wrote: > > Am 28.07.2014 22:40, schrieb Peter Chiochetti: > > Am 2014-07-28 um 21:15 schrieb Reindl Harald: > >> Am 28.07.2014 20:57, schrieb Rick Romero: > >>>> Am 28.07.2014 19:58, schrieb Juan Pablo: > >>>>> The reason I am wanting to do this is I would like to know if people > >>>>> are getting their email on personal devices > >>>>> instead of work secured / standardized phones > >>> > >>> IMHO, client certificates would work work well here. I think Dovecot > >>> supports it > >> > >> yes, but you accept them or not > >> that's a different story than "log the MUA information" > > > > Yes, it is a means to stop people from using insecure devices. > > a client certificate hadrly makes a device secure > if the device is compromised your cert is gone > > > So possibly a useful hint the OP may be interested in! Might well be that > > its the reason for learning which MUA was used? > > well, "what client is used" is impossible > > there is no user-agent like HTTP and even for HTTP the header is not > mandatory and rqeuire it will break your web-app for anybody who cares > for privacy while gain nothing Not in general: cyrus/imaps[9143]: client id: "name" "Thunderbird" "version" "24.6.0" I guess, dovecot simply must learn it. --Frank Elsner From skdovecot at smail.inf.fh-brs.de Tue Jul 29 07:13:50 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 29 Jul 2014 09:13:50 +0200 (CEST) Subject: Exit status code 134; what is it, in the context of Dovecot Antispam plug-in? In-Reply-To: <53D6EC93.8000503@indietorrent.org> References: <53D6EC93.8000503@indietorrent.org> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 28 Jul 2014, Ben Johnson wrote: > I have some debugging output in my pipe script; the output looks How does your script looks like? > Copying message contents to temporary file for debugging purposes; file > is: /tmp/sendmail-msg-7662.txt > Checking if the command-line input argument string (--spam) contains the > string "ham" or "spam" > Mode is "SPAM" > Calling (as user vmail) '/usr/lib/dovecot/deliver -d > "sa-training at example.com" -m "Training.SPAM" -p > "/tmp/sendmail-msg-7662.txt"' > Exit status was 134 Check out your local /usr/include/sysexits.h, if the exit code is defined there. It's not in mine. > Yet, I'm able to copy the above command and execute it manually, via the > command-line, and it works (and by "works", I mean to say that the > behavior is correct and exactly as expected; I receive the "Spam" email > at the designated mailbox). Here's how I'm calling it when it works > perfectly well (as "root"): > > # su -c '/usr/lib/dovecot/deliver -d "sa-training at example.com" -m > "Training.HAM" -p "/tmp/sendmail-msg-7460.txt"' vmail > > Any idea what status 134 might be or how to work around it? It looks to > be some kind of "temporary failure exception", but that is less than > informative in this context. > > # 2.2.9: /etc/dovecot/dovecot.conf > # OS: Linux 3.13.0-32-generic x86_64 Ubuntu 14.04.1 LTS > plugin { > antispam_backend = pipe > antispam_debug_target = syslog > antispam_pipe_program = /bin/bash > antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh > antispam_pipe_program_notspam_arg = --ham > antispam_pipe_program_spam_arg = --spam > antispam_pipe_tmpdir = /tmp > antispam_spam_pattern_ignorecase = SPAM;JUNK > antispam_trash_pattern_ignorecase = trash;Deleted * > antispam_verbose_debug = 1 > } > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9dJrnz1H7kL/d9rAQIskggAt2Otvh4sHZPrmYNm2aSiUwJqarmZmiLV KrXuMwuvDs33Wd60Bihqjykw96fwz3v+jQuqx+t/V+uN/jRffFpp98aUA4rR9rZ6 AJ3HJfPTyf11Pi9cCG8EhqmY9amPRFrp1Ox+NCg4Jt2liUPzmdtPe6+OUR+QlUdR Dr2Q6nyH+0sA948mnihJRVERf/oY+7/1s/UTLtCyyGGm4nXy9yoFWVeGxIybXF8G HMH0I1CYCvKVtmh3o/6IaqJD7IIvJGcUPcEiSNtoKAUC5hu1IhwwkbZnD9IEiigG HPDL0JIBZBleU8/6SC+e7eP7SF6deu4db1E/I45JVNOZLsZjzgtIVA== =5sDi -----END PGP SIGNATURE----- From al-dovecot at none.at Tue Jul 29 07:52:26 2014 From: al-dovecot at none.at (Aleksandar Lazic) Date: Tue, 29 Jul 2014 09:52:26 +0200 Subject: identify MUA =?UTF-8?Q?connecting=3F?= In-Reply-To: <20140729090800.7b71264fbb506009227a8a1b@moltke28.B.Shuttle.DE> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> <53D6A166.8070804@thelounge.net> <53D6B550.3050007@myzel.net> <53D6D381.9040402@thelounge.net> <20140729090800.7b71264fbb506009227a8a1b@moltke28.B.Shuttle.DE> Message-ID: <40c231555a34b0ec0c78f8f6db9f2087@none.at> Am 29-07-2014 09:08, schrieb Frank Elsner: > On Tue, 29 Jul 2014 00:49:37 +0200 Reindl Harald wrote: >> >> Am 28.07.2014 22:40, schrieb Peter Chiochetti: >> > Am 2014-07-28 um 21:15 schrieb Reindl Harald: >> >> Am 28.07.2014 20:57, schrieb Rick Romero: >> >>>> Am 28.07.2014 19:58, schrieb Juan Pablo: >> >>>>> The reason I am wanting to do this is I would like to know if people >> >>>>> are getting their email on personal devices >> >>>>> instead of work secured / standardized phones >> >>> >> >>> IMHO, client certificates would work work well here. I think Dovecot >> >>> supports it >> >> >> >> yes, but you accept them or not >> >> that's a different story than "log the MUA information" >> > >> > Yes, it is a means to stop people from using insecure devices. >> >> a client certificate hadrly makes a device secure >> if the device is compromised your cert is gone >> >> > So possibly a useful hint the OP may be interested in! Might well be that >> > its the reason for learning which MUA was used? >> >> well, "what client is used" is impossible >> >> there is no user-agent like HTTP and even for HTTP the header is not >> mandatory and rqeuire it will break your web-app for anybody who cares >> for privacy while gain nothing > > Not in general: > > cyrus/imaps[9143]: client id: "name" "Thunderbird" "version" "24.6.0" > > I guess, dovecot simply must learn it. But this depend on if some Mailheader (X-mailer, User-Agent (k9), ...) are set. I'm sure this could be logged with sieve. I haven't seen a option on http://wiki2.dovecot.org/Variables for normal dovecot log, maybe there is one. Cheers Aleks From dovecot at list-post.mks-mail.de Tue Jul 29 08:50:49 2014 From: dovecot at list-post.mks-mail.de (=?ISO-8859-1?Q?Markus_Sch=F6nhaber?=) Date: Tue, 29 Jul 2014 10:50:49 +0200 Subject: identify MUA connecting? In-Reply-To: <20140729090800.7b71264fbb506009227a8a1b@moltke28.B.Shuttle.DE> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> <53D69308.8090307@thelounge.net> <20140728135727.Horde.GbFO6vtsKF2HdOZ_7wmACQ2@www.vfemail.net> <53D6A166.8070804@thelounge.net> <53D6B550.3050007@myzel.net> <53D6D381.9040402@thelounge.net> <20140729090800.7b71264fbb506009227a8a1b@moltke28.B.Shuttle.DE> Message-ID: <53D76069.6080206@list-post.mks-mail.de> 29.07.2014 09:08, Frank Elsner: > Not in general: > > cyrus/imaps[9143]: client id: "name" "Thunderbird" "version" "24.6.0" > > I guess, dovecot simply must learn it. Dovecot already knows about the ID fields a client sends. It just doesn't log them by default. This default, of course, can be changed - by setting imap_id_log appropriately. For example imap_id_log = * will log all ID info a client sends. Obviously, if a client doesn't send ID info, there's nothing dovecot can do about it, though. -- Regards mks From tss at iki.fi Tue Jul 29 11:09:55 2014 From: tss at iki.fi (Timo Sirainen) Date: Tue, 29 Jul 2014 14:09:55 +0300 Subject: dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b In-Reply-To: <53D710BB.2050007@mohtex.net> References: <53D710BB.2050007@mohtex.net> Message-ID: <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> On 29 Jul 2014, at 06:10, Tamsy wrote: > Just a report to Stephan: > > I tried to compile two builds from the Mercurial: > - dovecot-2-2-pigeonhole-92405f753f6a > - dovecot-2-2-pigeonhole-77e6a42bff9b > > Both builds fail to compile with the same following error: > > ---------------- 8< ---------------- > ../../src/lib-sieve-tool/.libs/libsieve-tool.a(sieve-tool.o): In > function `sieve_tool_open_output_stream': > /usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/lib-sieve-tool/sieve-tool.c:518: > undefined reference to `o_stream_create_fd_autoclose' > ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to > `i_stream_create_fd_autoclose' You need to compile against a newer Dovecot hg version. From tss at iki.fi Tue Jul 29 11:16:10 2014 From: tss at iki.fi (Timo Sirainen) Date: Tue, 29 Jul 2014 14:16:10 +0300 Subject: Dovecot mailstore performance tuning In-Reply-To: <2b2d5f1633171ece02e0ade6abe3c56aba7927ee@webmail.westnet.com.au> References: <2b2d5f1633171ece02e0ade6abe3c56aba7927ee@webmail.westnet.com.au> Message-ID: <96838D95-7741-4828-AC7E-A65156404D84@iki.fi> On 22 Jul 2014, at 04:57, Murray Trainer wrote: > We have a couple of dovecot director proxies and six backed mailstores > each accessing mailboxes stored on five NFSv4 filsystems with about > 1TB of mail on each in maildir format. We have about 800 max users > on each mailstore at peak times and performance appears to starting to > degrade at these times. The mailstores are pretty recent hardware > with 64GB of RAM and 24 cores. The NFS storage is EMC VNX and we > are doing about 250 I/O per sec upto max of 500 on each > filesystem. I need to squeeze more performance out of these > servers whether that is in the NFS client, Dovecot or Linux OS/kernel > areas. We use LDAP for auth and I am doing some tuning in that > area. The NFS filesystems are mounted with the options below: > > 10.11.0.238:/mailbox_store_01 on /home1 type nfs4 > (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,nordirplus,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.11.0.96,local_lock=none,addr=10.11.0.238) Does relatime work with NFS? If yes, changing it to noatime would save some I/O. maildir_very_dirty_syncs=yes should be helpful. > # 2.2.9: /etc/dovecot/dovecot.conf mailbox_list_index=yes might be useful, although it has had some further performance improvements since v2.2.13. I should try to make v2.2.14 soon.. > quota = maildir Dict file quota would be a bit faster than maildir++ quota. From dovecot-list at mohtex.net Tue Jul 29 12:01:02 2014 From: dovecot-list at mohtex.net (Tamsy) Date: Tue, 29 Jul 2014 19:01:02 +0700 Subject: dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b In-Reply-To: <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> References: <53D710BB.2050007@mohtex.net> <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> Message-ID: <53D78CFE.1010500@mohtex.net> Timo Sirainen wrote on 29.07.2014 18:09: > On 29 Jul 2014, at 06:10, Tamsy wrote: > >> Just a report to Stephan: >> >> I tried to compile two builds from the Mercurial: >> - dovecot-2-2-pigeonhole-92405f753f6a >> - dovecot-2-2-pigeonhole-77e6a42bff9b >> >> Both builds fail to compile with the same following error: >> >> ---------------- 8< ---------------- >> ../../src/lib-sieve-tool/.libs/libsieve-tool.a(sieve-tool.o): In >> function `sieve_tool_open_output_stream': >> /usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/lib-sieve-tool/sieve-tool.c:518: >> undefined reference to `o_stream_create_fd_autoclose' >> ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to >> `i_stream_create_fd_autoclose' > You need to compile against a newer Dovecot hg version. Thank you for the hint. On Dovecot 2.2.13 now but will upgrade soonest to the latest HG and let you know. From nick.z.edwards at gmail.com Tue Jul 29 12:32:03 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Tue, 29 Jul 2014 22:32:03 +1000 Subject: Multiple servers and NFS In-Reply-To: <20140728235917.GA32411@daniel.localdomain> References: <53D035D8.9080905@walnut.gen.nz> <53D0F59D.1030606@freedominterface.org> <53D176C5.3030604@walnut.gen.nz> <53D1A40D.1090303@walnut.gen.nz> <53D1CF3F.9020201@freedominterface.org> <53D1E3EA.5040705@walnut.gen.nz> <53D265CE.2000108@freedominterface.org> <53D26761.1080109@sys4.de> <20140728235917.GA32411@daniel.localdomain> Message-ID: On 7/29/14, Daniel Parthey wrote: > Nick Edwards wrote: >> On 7/26/14, Robert Schetterer wrote: >> > Am 25.07.2014 um 16:12 schrieb Eduardo Ramos: >> >> I did not understand what the advantage of use dovecot LMTP with >> >> director too. >> > >> > in "very short" words... >> > with nfs ,the director should avoid concurrent events >> > which may happen with lmtp too, depending to multiple server setup >> >> using director was considered in risk assessment as its another point >> of failure, and weighed against its claimed benefit, the decision was >> made its not justified. >> >> mail_location = maildir:/mail/%1n/%1.1n/%2.1n/%n/Maildir:INDEX=MEMORY > > With maildir you won't have data-loss without the director, > since the index files are auto-regenerated without any problem. > disagree, if we'd had data loss we would have a case to use director, we also had none when we were using qmail and vpopmail, if dovecot did, and as said we are yet to see it, but if it did have data loss, than thats dovecots design issue, but I have no doubt it is that much of an issue. and from memory the only difference is some messages that just arrive may or may not appear immediately, this is only a problem with imap, and of all the users, we have a some total of about 200 that bother with imap, the other 100K plus use pop3 > With mdbox on NFS and no director, you will have data-loss sooner or later: irrelevant, we use Maildir, it is time proved. > > From jogi at mur.at Tue Jul 29 13:31:48 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Tue, 29 Jul 2014 15:31:48 +0200 Subject: problem migrating shared folders from cyrus to dovecot Message-ID: <53D7A244.4090301@mur.at> Hi all, We face a problem migrating shared mailboxes from an old cyrus server to dovecot. Whereas migrating regular users works like a charm, the shared mailboxes cannot be migrated. dsync/doveadm states: "Error: Failed to access mailbox INBOX: Mailbox does not exist". This is somehow true since the shared mailboxes live not under user.mailbox but rather under shared.mailbox (cyrus special). Has anyone a solution for this peculiar problem? Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From jogi at mur.at Tue Jul 29 13:39:06 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Tue, 29 Jul 2014 15:39:06 +0200 Subject: incremental mailbox syncs for quick migration Message-ID: <53D7A3FA.4060006@mur.at> Hi all, We are facing quite large mailboxes (>10GB) in our migration from cyrus to dovecot. I did a test on one mailbox and repeated the sync a couple of times with the expected result that the second, third, etc. sync took only seconds compared to minutes for the first sync. We use this command to sync a mailbox: doveadm backup -R -u USER imapc: Are there any problems to be expected when we first do a sync for all mailboxes but do not migrate the users right away but instead do the actual migration using a second sync? Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From jogi at mur.at Tue Jul 29 13:48:55 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Tue, 29 Jul 2014 15:48:55 +0200 Subject: LMTP during dsync migration Message-ID: <53D7A647.30602@mur.at> Hi all, Another question regarding migration. While migrating a mailbox with dsync is it safe to deliver mail via LMTP to the new (target) mailbox or is it wiser to deactivate LMTP delivery to this mailbox until it's fully migrated? And what methods could I use to stop delivery to a mailbox during migration? Our user data is stored on an LDAP server. Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From tim at titan21.co.uk Tue Jul 29 13:50:49 2014 From: tim at titan21.co.uk (Tim) Date: Tue, 29 Jul 2014 14:50:49 +0100 Subject: Missing IMAP Subfolders Message-ID: <53D7A6B9.3040506@titan21.co.uk> I've recently encountered an issue with my IMAP folders on Dovecot 2.0.19. When I telnet into my account and perform a list, I get the following response: A list "" "*" * LIST (\Unmarked) "." "INBOX" A OK List completed. However I know there are subfolders here and have examined the server directly via SSH and strangely: a select INBOX.Clients * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1394028715] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest a OK [READ-WRITE] Select completed. When I also subscribe to a couple if these which I am able to to do despite not being able to "LIST" them, I get this with LIST-EXTENDED: a04 LIST (SUBSCRIBED RECURSIVEMATCH) "*" "*" * LIST (\Subscribed \NonExistent) "." "INBOX" (CHILDINFO ("SUBSCRIBED")) * LIST (\Subscribed \NonExistent) "." "INBOX.Clients" (CHILDINFO ("SUBSCRIBED")) * LIST (\Subscribed \NonExistent) "." "INBOX.Clients.Bob" a04 OK List completed. Just not sure why a LIST is not giving me a full list as it's causing problems subscribing to these with Mail Clients. Any help is appreciated! From bourek at thinline.cz Tue Jul 29 14:13:11 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 29 Jul 2014 16:13:11 +0200 Subject: LMTP during dsync migration In-Reply-To: <53D7A647.30602@mur.at> References: <53D7A647.30602@mur.at> Message-ID: <53D7ABF7.8000405@thinline.cz> On 29.7.2014 15:48, Jogi Hofm?ller wrote: > Hi all, > > Another question regarding migration. While migrating a mailbox with > dsync is it safe to deliver mail via LMTP to the new (target) mailbox or > is it wiser to deactivate LMTP delivery to this mailbox until it's fully > migrated? > > And what methods could I use to stop delivery to a mailbox during > migration? Our user data is stored on an LDAP server. > > Cheers, > Considering you're planning to use doveadm backup, you can't deliver into the new mailbox. From dsync man page: backup - Backup mails from default mail location to location2 (or vice versa, if -R parameter is given). No changes are ever done to the source location. Any changes done in destination are discarded. Unless I misunderstood something, this means that if you deliver messages to the new mailbox, next run of doveadm backup will remove them. From wrosenauer at gmail.com Tue Jul 29 14:58:26 2014 From: wrosenauer at gmail.com (Wolfgang Rosenauer) Date: Tue, 29 Jul 2014 16:58:26 +0200 Subject: [Dovecot] Converting old emails to compressed format In-Reply-To: <530FC7CB.1040200@allard.it> References: <530FC7CB.1040200@allard.it> Message-ID: Hi, On Fri, Feb 28, 2014 at 12:18 AM, Renaud Allard wrote: > > I know this question has already been asked, but I would really like a > solution here as I tried all I could find on the wiki or mail archives > I am now running dovecot 2.2.12 > Compression works fine for new mails, so zlib works > Mails are currently stored using dbox > > So I tried for testing > dsync -D -v mirror -u user -m Archives dbox:~/temp > dsync -o "plugin/zlib_save=xz" -D -v mirror -u user -m Archives dbox:~/temp > dsync -o "plugin/zlib_save=" -D -v mirror -u user -m Archives dbox:~/temp > dsync -o "plugin/zlib_save=" -D -v mirror -u user -m Archives maildir:~/temp > dsync -o "plugin/zlib_save=xz" -D -v mirror -u user -m Archives > maildir:~/temp > > And also converting again those maildir messages to dbox (just in case it > wouldn't work from dbox format) > And also with backup instead of mirror > > None of this actually works, mails are indeed copied, but not compressed > > So I am wondering if there is a way to compress those mails? I'm now facing the same issue with 2.2.13. zlib is working for new mails but as opposed to some information I found dsync (backup) does not convert old mails to compressed. For example this post suggests that it should happen: http://thr3ads.net/dovecot/2013/07/2663810-dsync-backup-mails-compressed and also some Dovecot book also states to convert the mailbox just use dsync backup after zlib is enabled. Still I'm not able to make it work. Any hints? Thanks, Wolfgang From crohmann at netcologne.de Tue Jul 29 15:13:49 2014 From: crohmann at netcologne.de (Christian Rohmann) Date: Tue, 29 Jul 2014 17:13:49 +0200 Subject: [Dovecot] Converting old emails to compressed format In-Reply-To: References: <530FC7CB.1040200@allard.it> Message-ID: <53D7BA2D.8040206@netcologne.de> Hello Wolfgang, On 29.07.2014 16:58, Wolfgang Rosenauer wrote: > I'm now facing the same issue with 2.2.13. > zlib is working for new mails but as opposed to some information I > found dsync (backup) does not convert old mails to compressed. > For example this post suggests that it should happen: > http://thr3ads.net/dovecot/2013/07/2663810-dsync-backup-mails-compressed > and also some Dovecot book also states to convert the mailbox just use > dsync backup after zlib is enabled. > Still I'm not able to make it work. You have to set the compression type with the zlib_save option. i.e.: "-o plugin/zlib_save=gz" Regards Christian From rs at sys4.de Tue Jul 29 15:14:02 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 29 Jul 2014 17:14:02 +0200 Subject: [Dovecot] Converting old emails to compressed format In-Reply-To: References: <530FC7CB.1040200@allard.it> Message-ID: <53D7BA3A.9020509@sys4.de> Am 29.07.2014 um 16:58 schrieb Wolfgang Rosenauer: > I'm now facing the same issue with 2.2.13. > zlib is working for new mails but as opposed to some information I > found dsync (backup) does not convert old mails to compressed. i guess this is by design, perhaps a "-force" should be introduced Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From me at junc.eu Tue Jul 29 15:14:31 2014 From: me at junc.eu (Benny Pedersen) Date: Tue, 29 Jul 2014 17:14:31 +0200 Subject: identify MUA connecting? In-Reply-To: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> References: <26fa20c03ac0e0796abe6258bb15d58b@openmailbox.org> Message-ID: <14782afdff0.27e5.d475fad7b14312f5d8424e35e39f7512@junc.eu> On 28. jul. 2014 19.59.07 Juan Pablo wrote: > Hello I am using dovecot 1.2.15 on ubuntu. dovecot -n is more usefull for more help ignore this maillist of unsupported version here is what settings i have in pluging section mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_group_events = no mail_log_fields = uid box msgid size Sent with AquaMail for Android http://www.aqua-mail.com From ben at indietorrent.org Tue Jul 29 15:20:53 2014 From: ben at indietorrent.org (Ben Johnson) Date: Tue, 29 Jul 2014 11:20:53 -0400 Subject: Exit status code 134; what is it, in the context of Dovecot Antispam plug-in? In-Reply-To: References: <53D6EC93.8000503@indietorrent.org> Message-ID: <53D7BBD5.7080106@indietorrent.org> On 7/29/2014 3:13 AM, Steffen Kaiser wrote: > On Mon, 28 Jul 2014, Ben Johnson wrote: > >> I have some debugging output in my pipe script; the output looks > > How does your script looks like? > http://pastebin.com/nh8SwQtw >> Copying message contents to temporary file for debugging >> purposes; file is: /tmp/sendmail-msg-7662.txt Checking if the >> command-line input argument string (--spam) contains the string >> "ham" or "spam" Mode is "SPAM" Calling (as user vmail) >> '/usr/lib/dovecot/deliver -d "sa-training at example.com" -m >> "Training.SPAM" -p "/tmp/sendmail-msg-7662.txt"' Exit status was >> 134 > > Check out your local /usr/include/sysexits.h, if the exit code is > defined there. It's not in mine. > Exit code 134 is not defined in /usr/include/sysexits.h on my system. >> Yet, I'm able to copy the above command and execute it manually, >> via the command-line, and it works (and by "works", I mean to >> say that the behavior is correct and exactly as expected; I >> receive the "Spam" email at the designated mailbox). Here's how >> I'm calling it when it works perfectly well (as "root"): > >> # su -c '/usr/lib/dovecot/deliver -d "sa-training at example.com" -m >> "Training.HAM" -p "/tmp/sendmail-msg-7460.txt"' vmail > >> Any idea what status 134 might be or how to work around it? It >> looks to be some kind of "temporary failure exception", but that >> is less than informative in this context. > >> # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-32-generic >> x86_64 Ubuntu 14.04.1 LTS plugin { antispam_backend = pipe >> antispam_debug_target = syslog antispam_pipe_program = /bin/bash >> antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh >> antispam_pipe_program_notspam_arg = --ham >> antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = >> /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK >> antispam_trash_pattern_ignorecase = trash;Deleted * >> antispam_verbose_debug = 1 } > > > -- Steffen Kaiser Is it possible that this is some kind of apparmor restriction? I ask because apparmor is indeed installed on this machine. If you examine the script source (cited above), you will see that I've had to use "the hammer that is strace" to debug issues with Dovecot + Antispam before... maybe it's worth trying in this case. Happy to hear any further suggestions. Thanks again, -Ben From wrosenauer at gmail.com Tue Jul 29 15:22:12 2014 From: wrosenauer at gmail.com (Wolfgang Rosenauer) Date: Tue, 29 Jul 2014 17:22:12 +0200 Subject: [Dovecot] Converting old emails to compressed format In-Reply-To: <53D7BA2D.8040206@netcologne.de> References: <530FC7CB.1040200@allard.it> <53D7BA2D.8040206@netcologne.de> Message-ID: Hi Christian, On Tue, Jul 29, 2014 at 5:13 PM, Christian Rohmann wrote: > > You have to set the compression type with the zlib_save option. > > i.e.: "-o plugin/zlib_save=gz" been there: dsync -o plugin/zlib_save=gz backup -u testy maildir:/srv/dovecot/testy/maildir.new doesn't make a difference unfortunately. My mailboxes are in maildir format and besides enabling zlib I do not change the format. My testmailbox has only one message but this still is uncompressed after dsync. Where is Peer who wrote in his book that this should just work? Thanks, Wolfgang From rs at sys4.de Tue Jul 29 15:25:03 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 29 Jul 2014 17:25:03 +0200 Subject: [Dovecot] Converting old emails to compressed format In-Reply-To: <53D7BA2D.8040206@netcologne.de> References: <530FC7CB.1040200@allard.it> <53D7BA2D.8040206@netcologne.de> Message-ID: <53D7BCCF.3050102@sys4.de> Am 29.07.2014 um 17:13 schrieb Christian Rohmann: > Hello Wolfgang, > > On 29.07.2014 16:58, Wolfgang Rosenauer wrote: >> I'm now facing the same issue with 2.2.13. >> zlib is working for new mails but as opposed to some information I >> found dsync (backup) does not convert old mails to compressed. >> For example this post suggests that it should happen: >> http://thr3ads.net/dovecot/2013/07/2663810-dsync-backup-mails-compressed >> and also some Dovecot book also states to convert the mailbox just use >> dsync backup after zlib is enabled. >> Still I'm not able to make it work. > > > You have to set the compression type with the zlib_save option. > > i.e.: "-o plugin/zlib_save=gz" > > > > Regards > > Christian > thx for info i missed that Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From rs at sys4.de Tue Jul 29 15:37:16 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 29 Jul 2014 17:37:16 +0200 Subject: [Dovecot] Converting old emails to compressed format In-Reply-To: References: <530FC7CB.1040200@allard.it> <53D7BA2D.8040206@netcologne.de> Message-ID: <53D7BFAC.6000205@sys4.de> Am 29.07.2014 um 17:22 schrieb Wolfgang Rosenauer: > Hi Christian, > > On Tue, Jul 29, 2014 at 5:13 PM, Christian Rohmann > wrote: >> >> You have to set the compression type with the zlib_save option. >> >> i.e.: "-o plugin/zlib_save=gz" > > been there: > dsync -o plugin/zlib_save=gz backup -u testy > maildir:/srv/dovecot/testy/maildir.new > > doesn't make a difference unfortunately. > My mailboxes are in maildir format and besides enabling zlib I do not > change the format. > My testmailbox has only one message but this still is uncompressed after dsync. > > Where is Peer who wrote in his book that this should just work? > > > Thanks, > Wolfgang > perhaps its a version bug, is see, i have to test it my own for verify Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From list-dovecot at jack.org.uk Tue Jul 29 15:43:34 2014 From: list-dovecot at jack.org.uk (Jack) Date: Tue, 29 Jul 2014 16:43:34 +0100 Subject: PAM and YubiKeys Message-ID: <178263ecf39695f24abe658ec56173e0@home.jack.org.uk> Hi List, I am trying to get authentication to Dovecot with a Yubikey OTP. I have the PAM modules installed and can successfully authenticate to ssh with the Yubikey, so I am confident that the network level and Yubikey configuration is correct. I can also authenticate to Dovecot via PAM using a plain password, however when I try to use the Yubikey authentication with Dovecot things don't go well. Network monitoring reveals that the software does not even attempt to connect to the authentication servers. My Dovecot authentication is configured as follows :- passdb { driver = pam args = failure_show_msg=yes dovecot override_fields = proxy host=1.2.3.4 master=XXXXXX pass=XXXXXX } userdb { driver = passwd-file args = username_format=%u /etc/dovecot/users } The dovecot Pam config file is :- auth sufficient pam_yubico.so id=99999 key="xxxxxxxxxxx" authfile=/etc/yubikey_mappings debug @include common-auth @include common-account @include common-session When failing to authenticate with Dovecot, the PAM debug log shows :- [../pam_yubico.c:parse_cfg(761)] called. [../pam_yubico.c:parse_cfg(762)] flags 0 argc 4 [../pam_yubico.c:parse_cfg(764)] argv[0]=id=xxxxxx [../pam_yubico.c:parse_cfg(764)] argv[1]=key="xxxxxx" [../pam_yubico.c:parse_cfg(764)] argv[2]=authfile=/etc/yubikey_mappings [../pam_yubico.c:parse_cfg(764)] argv[3]=debug [../pam_yubico.c:parse_cfg(765)] id=xxxxxx [../pam_yubico.c:parse_cfg(766)] key="xxxxxxxxx" [../pam_yubico.c:parse_cfg(767)] debug=1 [../pam_yubico.c:parse_cfg(768)] alwaysok=0 [../pam_yubico.c:parse_cfg(769)] verbose_otp=0 [../pam_yubico.c:parse_cfg(770)] try_first_pass=0 [../pam_yubico.c:parse_cfg(771)] use_first_pass=0 [../pam_yubico.c:parse_cfg(772)] authfile=/etc/yubikey_mappings [../pam_yubico.c:parse_cfg(773)] ldapserver=(null) [../pam_yubico.c:parse_cfg(774)] ldap_uri=(null) [../pam_yubico.c:parse_cfg(775)] ldapdn=(null) [../pam_yubico.c:parse_cfg(776)] user_attr=(null) [../pam_yubico.c:parse_cfg(777)] yubi_attr=(null) [../pam_yubico.c:parse_cfg(778)] yubi_attr_prefix=(null) [../pam_yubico.c:parse_cfg(779)] url=(null) [../pam_yubico.c:parse_cfg(780)] capath=(null) [../pam_yubico.c:parse_cfg(781)] token_id_length=12 [../pam_yubico.c:parse_cfg(782)] mode=client [../pam_yubico.c:parse_cfg(783)] chalresp_path=(null) [../pam_yubico.c:pam_sm_authenticate(823)] get user returned: jack [../pam_yubico.c:pam_sm_authenticate(929)] conv returned 44 bytes [../pam_yubico.c:pam_sm_authenticate(947)] Skipping first 0 bytes. Length is 44, token_id set to 12 and token OTP always 32. [../pam_yubico.c:pam_sm_authenticate(954)] OTP: ccccccbcitfdueencldivbcjvghvikdtrnujbgubirru ID: ccccccbcitfd [../pam_yubico.c:pam_sm_authenticate(985)] ykclient return value (101): Could not parse server response [../pam_yubico.c:pam_sm_authenticate(1038)] done. [Authentication service cannot retrieve authentication info] A successful authentication (via ssh) looks like [../pam_yubico.c:parse_cfg(761)] called. [../pam_yubico.c:parse_cfg(762)] flags 1 argc 4 [../pam_yubico.c:parse_cfg(764)] argv[0]=id=xxxx [../pam_yubico.c:parse_cfg(764)] argv[1]=key="xxxxxxxxxxxxxxxxxx" [../pam_yubico.c:parse_cfg(764)] argv[2]=authfile=/etc/yubikey_mappings [../pam_yubico.c:parse_cfg(764)] argv[3]=debug [../pam_yubico.c:parse_cfg(765)] id=xxxxxx [../pam_yubico.c:parse_cfg(766)] key="xxxxxxxxxxxxxxxxxxx" [../pam_yubico.c:parse_cfg(767)] debug=1 [../pam_yubico.c:parse_cfg(768)] alwaysok=0 [../pam_yubico.c:parse_cfg(769)] verbose_otp=0 [../pam_yubico.c:parse_cfg(770)] try_first_pass=0 [../pam_yubico.c:parse_cfg(771)] use_first_pass=0 [../pam_yubico.c:parse_cfg(772)] authfile=/etc/yubikey_mappings [../pam_yubico.c:parse_cfg(773)] ldapserver=(null) [../pam_yubico.c:parse_cfg(774)] ldap_uri=(null) [../pam_yubico.c:parse_cfg(775)] ldapdn=(null) [../pam_yubico.c:parse_cfg(776)] user_attr=(null) [../pam_yubico.c:parse_cfg(777)] yubi_attr=(null) [../pam_yubico.c:parse_cfg(778)] yubi_attr_prefix=(null) [../pam_yubico.c:parse_cfg(779)] url=(null) [../pam_yubico.c:parse_cfg(780)] capath=(null) [../pam_yubico.c:parse_cfg(781)] token_id_length=12 [../pam_yubico.c:parse_cfg(782)] mode=client [../pam_yubico.c:parse_cfg(783)] chalresp_path=(null) [../pam_yubico.c:pam_sm_authenticate(823)] get user returned: jack [../pam_yubico.c:pam_sm_authenticate(929)] conv returned 44 bytes [../pam_yubico.c:pam_sm_authenticate(947)] Skipping first 0 bytes. Length is 44, token_id set to 12 and token OTP always 32. [../pam_yubico.c:pam_sm_authenticate(954)] OTP: ccccccbcitfdetdfkbjrtfbuhgbtjgethkdebcgthgde ID: ccccccbcitfd [../pam_yubico.c:pam_sm_authenticate(985)] ykclient return value (0): Success [../pam_yubico.c:authorize_user_token(221)] Using system-wide auth_file /etc/yubikey_mappings [../pam_yubico.c:check_user_token(178)] Authorization line: jack:ccccccbcitfd [../pam_yubico.c:check_user_token(182)] Matched user: jack [../pam_yubico.c:check_user_token(187)] Authorization token: ccccccbcitfd [../pam_yubico.c:check_user_token(190)] Match user/token as jack/ccccccbcitfd [../pam_yubico.c:pam_sm_authenticate(1038)] done. [Success] I have just noticed that the 'flags' is set to 1 by ssh. I don't know where (or if) I can control how Dovecot sets that flag or if it has any relevance. The Pam configuration line for Yubikey is identical in the ssh configuration. Does anyone have any idea what is going wrong? Thanks in advance, Jack From dovecot-list at mohtex.net Wed Jul 30 03:38:29 2014 From: dovecot-list at mohtex.net (Tamsy) Date: Wed, 30 Jul 2014 10:38:29 +0700 Subject: dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b In-Reply-To: <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> References: <53D710BB.2050007@mohtex.net> <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> Message-ID: <53D868B5.5070407@mohtex.net> Timo Sirainen wrote on 29.07.2014 18:09: > On 29 Jul 2014, at 06:10, Tamsy wrote: > >> Just a report to Stephan: >> >> I tried to compile two builds from the Mercurial: >> - dovecot-2-2-pigeonhole-92405f753f6a >> - dovecot-2-2-pigeonhole-77e6a42bff9b >> >> Both builds fail to compile with the same following error: >> >> ---------------- 8< ---------------- >> ../../src/lib-sieve-tool/.libs/libsieve-tool.a(sieve-tool.o): In >> function `sieve_tool_open_output_stream': >> /usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/lib-sieve-tool/sieve-tool.c:518: >> undefined reference to `o_stream_create_fd_autoclose' >> ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to >> `i_stream_create_fd_autoclose' > You need to compile against a newer Dovecot hg version. To Report back on this matter: After upgrading Dovecot to the latest HG version, Pigeonhole compiled nicely. Thank you Timo. From jogi at mur.at Wed Jul 30 09:10:38 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 30 Jul 2014 11:10:38 +0200 Subject: LMTP during dsync migration In-Reply-To: <53D7ABF7.8000405@thinline.cz> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> Message-ID: <53D8B68E.5080603@mur.at> Hi Jiri, all, Thanks for your reply. Am 2014-07-29 16:13, schrieb Jiri Bourek: > Considering you're planning to use doveadm backup, you can't deliver > into the new mailbox. From dsync man page: Yes, this is the way we plan to migrate the mailboxes. > backup - Backup mails from default mail location to location2 (or vice > versa, if -R parameter is given). No changes are ever done to the source > location. Any changes done in destination are discarded. > Unless I misunderstood something, this means that if you deliver > messages to the new mailbox, next run of doveadm backup will remove them. We are not planning on multiple runs of doveadm backup. The question is what to do with LMTP _while_ the doveadm backup migration is happening? At the time when mailbox X get's migrated, the settings used for the proxy will be removed, so user X cannot access the mailbox on the old server anymore. Given the size of some of the mailboxes chances are quite high that there will be delivery attempts _during_ the migration process. That's what I am thinking about. Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From h.reindl at thelounge.net Wed Jul 30 09:27:43 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 30 Jul 2014 11:27:43 +0200 Subject: LMTP during dsync migration In-Reply-To: <53D8B68E.5080603@mur.at> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> Message-ID: <53D8BA8F.4060004@thelounge.net> Am 30.07.2014 11:10, schrieb Jogi Hofm?ller: > We are not planning on multiple runs of doveadm backup. The question is > what to do with LMTP _while_ the doveadm backup migration is happening? just shutdown the MTA so you don't receive new mail senders will defer and deliver later -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From bourek at thinline.cz Wed Jul 30 10:02:20 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Wed, 30 Jul 2014 12:02:20 +0200 Subject: LMTP during dsync migration In-Reply-To: <53D8BA8F.4060004@thelounge.net> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> Message-ID: <53D8C2AC.3090209@thinline.cz> On 30.7.2014 11:27, Reindl Harald wrote: > > > Am 30.07.2014 11:10, schrieb Jogi Hofm?ller: >> We are not planning on multiple runs of doveadm backup. The question is >> what to do with LMTP _while_ the doveadm backup migration is happening? > > just shutdown the MTA so you don't receive new mail > senders will defer and deliver later > > Or better - disable LMTP service in Dovecot. Incoming mail will stay on your MTA and when you're done, you just tell it to deliver everything that piled up in the queue in the meantime From tim at tree-of-life.co.uk Wed Jul 30 10:12:33 2014 From: tim at tree-of-life.co.uk (Tim Dickson) Date: Wed, 30 Jul 2014 11:12:33 +0100 Subject: dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b In-Reply-To: <53D868B5.5070407@mohtex.net> References: <53D710BB.2050007@mohtex.net> <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> <53D868B5.5070407@mohtex.net> Message-ID: <53D8C511.7010406@tree-of-life.co.uk> Is there any chance that the current dovecot-2-2-pigeonhole (hg) can be "released" so that there is a released version (eg 0.4.4) that works with the current released version of dovecot (2.2.13) ? thanks. Tim On 30/07/2014 04:38, Tamsy wrote: > Timo Sirainen wrote on 29.07.2014 18:09: >> On 29 Jul 2014, at 06:10, Tamsy wrote: >> >>> Just a report to Stephan: >>> >>> I tried to compile two builds from the Mercurial: >>> - dovecot-2-2-pigeonhole-92405f753f6a >>> - dovecot-2-2-pigeonhole-77e6a42bff9b >>> >>> Both builds fail to compile with the same following error: >>> >>> ---------------- 8< ---------------- >>> ../../src/lib-sieve-tool/.libs/libsieve-tool.a(sieve-tool.o): In >>> function `sieve_tool_open_output_stream': >>> /usr/local/src/dovecot-2-2-pigeonhole-77e6a42bff9b/src/lib-sieve-tool/sieve-tool.c:518: >>> undefined reference to `o_stream_create_fd_autoclose' >>> ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to >>> `i_stream_create_fd_autoclose' >> You need to compile against a newer Dovecot hg version. > To Report back on this matter: > After upgrading Dovecot to the latest HG version, Pigeonhole compiled > nicely. > Thank you Timo. > From stephan at rename-it.nl Wed Jul 30 10:34:44 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Wed, 30 Jul 2014 12:34:44 +0200 Subject: dovecot-2-2-pigeonhole-92405f753f6a - 77e6a42bff9b In-Reply-To: <53D8C511.7010406@tree-of-life.co.uk> References: <53D710BB.2050007@mohtex.net> <0FE8BB91-6FAF-4DFE-9D3C-1A30A005AA15@iki.fi> <53D868B5.5070407@mohtex.net> <53D8C511.7010406@tree-of-life.co.uk> Message-ID: <53D8CA44.4050205@rename-it.nl> On 7/30/2014 12:12 PM, Tim Dickson wrote: > Is there any chance that the current dovecot-2-2-pigeonhole (hg) can > be "released" so that there is a released version (eg 0.4.4) that > works with the current released version of dovecot (2.2.13) ? > thanks. Pigeonhole 0.4.3 is released for Dovecot 2.2.13. Are you having issues? Regards, Stephan. From jogi at mur.at Wed Jul 30 14:39:24 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 30 Jul 2014 16:39:24 +0200 Subject: LMTP during dsync migration In-Reply-To: <53D8C2AC.3090209@thinline.cz> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> Message-ID: <53D9039C.4010108@mur.at> Hi all, Thanks for your replies. Am 2014-07-30 12:02, schrieb Jiri Bourek: > On 30.7.2014 11:27, Reindl Harald wrote: >> just shutdown the MTA so you don't receive new mail >> senders will defer and deliver later I would like to stay away from this option since we plan on doing a transparent migration that will take a few nights. Turning MTA off every night seems a bit drastic. > Or better - disable LMTP service in Dovecot. Incoming mail will stay on > your MTA and when you're done, you just tell it to deliver everything > that piled up in the queue in the meantime Better but still not perfect ;) We have users that work late and I am sure they would complain when they don't receive email during migration nights. Still thinking ... Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From h.reindl at thelounge.net Wed Jul 30 15:36:49 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 30 Jul 2014 17:36:49 +0200 Subject: LMTP during dsync migration In-Reply-To: <53D9039C.4010108@mur.at> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> Message-ID: <53D91111.7070306@thelounge.net> Am 30.07.2014 16:39, schrieb Jogi Hofm?ller: > Am 2014-07-30 12:02, schrieb Jiri Bourek: >> Or better - disable LMTP service in Dovecot. Incoming mail will stay on >> your MTA and when you're done, you just tell it to deliver everything >> that piled up in the queue in the meantime > > Better but still not perfect ;) We have users that work late and I am > sure they would complain when they don't receive email during migration > nights normally you announce a mainantaince window for such migrations why do you need dsync at all for such a migration? * HOT: rsync --delete-after -tPrlpogEAX /datadir/ root at new:/datadir/ * stop services * COLD: rsync --delete-after -tPrlpogEAX /datadir/ root at new:/datadir/ * start services on new machine the second rsync is damned fast because it only cares about changes and in case of really large data repeat the hot run multiple times to reduce the overall differences nobody right in his mind starts such tasks while the servers are online because if something goes wrong you can throw your mandatory backups out of the window given you can choose what data you more like to loose - the one happened by errors while migration or the one received between backup and restore > Still thinking ... you asked "The question is what to do with LMTP _while_ the doveadm backup migration is happening?" and there is not much to think -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From gedalya at gedalya.net Wed Jul 30 17:40:23 2014 From: gedalya at gedalya.net (Gedalya) Date: Wed, 30 Jul 2014 13:40:23 -0400 Subject: LMTP during dsync migration In-Reply-To: <53D9039C.4010108@mur.at> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> Message-ID: <53D92E07.3030709@gedalya.net> On 07/30/2014 10:39 AM, Jogi Hofm?ller wrote: > I would like to stay away from this option since we plan on doing a > transparent migration that will take a few nights. Turning MTA off > every night seems a bit drastic. What I do is I implement a delivery lock in the database. I like to use exim + mysql, but I think you can probably figure something out with postfix + whatever, too. In exim-ese: mailbox_locked: debug_print = "R: mailbox_locked for $local_part@$domain" driver = redirect allow_defer verify = false retry_use_local_part = true domains = +virtual_domains condition = ${lookup mysql{select locked from mailbox where localpart='${quote_mysql:$local_part}' and domain='${quote_mysql:$domain}' and locked=1 and active}} data = :defer: Delivery deferred, mailbox is locked From trashcan at odo.in-berlin.de Wed Jul 30 18:29:23 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Wed, 30 Jul 2014 20:29:23 +0200 Subject: =?iso-8859-1?Q?Die_H=FCtchen-Spiel_Mafia_wird_das_nicht_gerne_se?= =?iso-8859-1?Q?hen=2E_Diese_Katze_ist_Profi!?= Message-ID: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> http://heftig.co/katze-mit-huetchen/ From trashcan at odo.in-berlin.de Wed Jul 30 18:55:58 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Wed, 30 Jul 2014 20:55:58 +0200 Subject: =?utf-8?Q?=E2=96=B6_Leopard_Is_Getting_Relaxed_big_cat_purrs_-_Y?= =?utf-8?Q?ouTube?= Message-ID: <65173484-73E8-4200-93E5-50FDD4C7F2A3@odo.in-berlin.de> Whow! In einer Auffangstation f?r Wildtiere in den USA laut Spiegel.de http://www.youtube.com/watch?v=4BLoHyeevcU From h.reindl at thelounge.net Wed Jul 30 19:03:09 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 30 Jul 2014 21:03:09 +0200 Subject: stop that list-spam In-Reply-To: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> References: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> Message-ID: <53D9416D.9020207@thelounge.net> Account gehackt oder Volltrottel? Am 30.07.2014 20:29, schrieb Michael Grimm: > http://heftig.co/katze-mit-huetchen/ Am 30.07.2014 20:55, schrieb Michael Grimm: > Whow! In einer Auffangstation f?r Wildtiere in den USA laut Spiegel.de > > http://www.youtube.com/watch?v=4BLoHyeevcU -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From trashcan at odo.in-berlin.de Wed Jul 30 19:20:02 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Wed, 30 Jul 2014 21:20:02 +0200 Subject: stop that list-spam In-Reply-To: <53D9416D.9020207@thelounge.net> References: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> <53D9416D.9020207@thelounge.net> Message-ID: Hi -- My sincerest apologies to all, but ... On 30.07.2014, at 21:03, Reindl Harald wrote: > Account gehackt oder Volltrottel? ... that was simply one of those mistakes that do happen to human beings once in a while. Regards, Michael From h.reindl at thelounge.net Wed Jul 30 19:40:24 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Wed, 30 Jul 2014 21:40:24 +0200 Subject: stop that list-spam In-Reply-To: References: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> <53D9416D.9020207@thelounge.net> Message-ID: <53D94A28.5030702@thelounge.net> Am 30.07.2014 21:20, schrieb Michael Grimm: > My sincerest apologies to all, but ... accepted > On 30.07.2014, at 21:03, Reindl Harald wrote: > >> Account gehackt oder Volltrottel? > > ... that was simply one of those mistakes that do happen to human beings once in a while like send something to the whole adressbook? unacceptable the same way as feed it to linked-in and friends especially if somebody seems to be mailserver admin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From mildred-ml at mildred.fr Wed Jul 30 20:18:56 2014 From: mildred-ml at mildred.fr (Mildred Ki'Lya) Date: Wed, 30 Jul 2014 22:18:56 +0200 Subject: Issue with exim and auth protocol Message-ID: <53D95330.2080901@mildred.fr> Hi, I'm trying to set up exim (4.83) as a submission server, and need to set up the dovecot authentication in exim. I'm having an issue with that (documented at ) The problem is that exim doesn't follow the handshake as described here: . The wiki page says that the client should start the handshake, but exim waits for the server to start and to receive the DONE command until it starts its own handshake. What I actually get is: exim connects to dovecot auth dovecot VERSION 1 1 dovecot SPID 48 And then, dovecot stops (I presume it waits for the client handshake, VERSION and CPID). Exim on its side waits for the DONE. This results in the SMTP connection by exim never replying to the AUTH PLAIN command. This is exim 4.80 (or 4.83) and dovecot 2.1.7. I have another server set up almost exactly the same (but with dovecot 2.1.17) where it does work. In that case, dovecot finishes the handshake before exim starts its handshake. It results in: exim connects to dovecot auth dovecot VERSION 1 1 dovecot MECH PLAIN plaintext dovecot SPID 10905 dovecot CUID 1 dovecot COOKIE d3861d29441f06d962490eab8549fd46 dovecot DONE exim VERSION 1 0 exim CPID 10619 exim AUTH 1 PLAIN service=smtp secured rip=82.247.184.53 lip=80.67.179.36 nologin resp= I don't understand what could change the dovecot behaviour in that regard. Is there a solution that would only require modifying the configuration? Thank you, Mildred From gedalya at gedalya.net Wed Jul 30 21:32:49 2014 From: gedalya at gedalya.net (Gedalya) Date: Wed, 30 Jul 2014 17:32:49 -0400 Subject: Issue with exim and auth protocol In-Reply-To: <53D95330.2080901@mildred.fr> References: <53D95330.2080901@mildred.fr> Message-ID: <53D96481.6060408@gedalya.net> Could it be related to something in your dovecot configuration (which you didn't post)? Despite the fact that an interesting conversation is developing in the exim bug report, this setup does usually work, including on one of your servers as you have indicated. On my end, I never had issues between dovecot 2.1.7 and 2.2.13, using the exact same authenticator config in exim. On 07/30/2014 04:18 PM, Mildred Ki'Lya wrote: > Hi, > > I'm trying to set up exim (4.83) as a submission server, and need to set > up the dovecot authentication in exim. I'm having an issue with that > (documented at ) > > The problem is that exim doesn't follow the handshake as described here: > . The wiki page says that > the client should start the handshake, but exim waits for the server to > start and to receive the DONE command until it starts its own handshake. > > What I actually get is: > > exim connects to dovecot auth > dovecot VERSION 1 1 > dovecot SPID 48 > > > And then, dovecot stops (I presume it waits for the client handshake, > VERSION and CPID). Exim on its side waits for the DONE. This results in > the SMTP connection by exim never replying to the AUTH PLAIN command. > > This is exim 4.80 (or 4.83) and dovecot 2.1.7. > > I have another server set up almost exactly the same (but with dovecot > 2.1.17) where it does work. In that case, dovecot finishes the handshake > before exim starts its handshake. It results in: > > exim connects to dovecot auth > dovecot VERSION 1 1 > dovecot MECH PLAIN plaintext > dovecot SPID 10905 > dovecot CUID 1 > dovecot COOKIE d3861d29441f06d962490eab8549fd46 > dovecot DONE > exim VERSION 1 0 > exim CPID 10619 > exim AUTH 1 PLAIN service=smtp secured > rip=82.247.184.53 lip=80.67.179.36 nologin resp= encoded string> > > > I don't understand what could change the dovecot behaviour in that > regard. Is there a solution that would only require modifying the > configuration? > > Thank you, > > Mildred From nick.z.edwards at gmail.com Thu Jul 31 00:31:56 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Thu, 31 Jul 2014 10:31:56 +1000 Subject: stop that list-spam In-Reply-To: References: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> <53D9416D.9020207@thelounge.net> Message-ID: Es ist in Ordnung, nichts dagegen Reindl, er ist so perfekt und macht nie einen Fehler seit der Geburt :-> On 7/31/14, Michael Grimm wrote: > Hi -- > > My sincerest apologies to all, but ... > > On 30.07.2014, at 21:03, Reindl Harald wrote: > >> Account gehackt oder Volltrottel? > > ... that was simply one of those mistakes that do happen to human beings > once in a while. > > Regards, > Michael > From skdovecot at smail.inf.fh-brs.de Thu Jul 31 06:39:12 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 31 Jul 2014 08:39:12 +0200 (CEST) Subject: LMTP during dsync migration In-Reply-To: <53D9039C.4010108@mur.at> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 30 Jul 2014, Jogi Hofm?ller wrote: >> Or better - disable LMTP service in Dovecot. Incoming mail will stay on >> your MTA and when you're done, you just tell it to deliver everything >> that piled up in the queue in the meantime > > Better but still not perfect ;) We have users that work late and I am > sure they would complain when they don't receive email during migration > nights. > > Still thinking ... In your original post you've wrote "While migrating a mailbox". So you migrate one user after another. Also, if you want to disable LMTP for that user, you want to disable IMAP and POP3, too, for the very same reason -> or at least put them in read-only mode. 1) So, IMHO, your goal is to make the mail storage of one user read-only. Experiment with ACLs. Make all the mailboxes of the user read-only. After migration remove the ACLs. 2) Make the mail storage inaccessable during backup for just one user: How about adding another userdb { driver = passwd-file args = /.../%s/file } as the first one, which disables the access to the one user's mail storage currently migrated. %s would be lmtp, imap, pop3 and doveadm, IMHO. Make sure, doveadm sees no user in this userdb, but the others do, e.g. symlink the appropriate files and keep /.../doveadm/file zero-length, in order to fall back to LDAP always. In short: doveadm must know the real path, all other services a faked one. The migration of one user would be: put user in /.../{imap,pop3,lmtp}/file # or overwrite file with user doveadm auth cache flush # make sure, user info is not cached already migrate remove user from /.../file a) Besides the %s-way, there must be a way to have doveadm override the settings in: userdb { driver = passwd-file args = /.../file } in the line of: doveadm -o userdb[*]/args=/dev/null .... [*] IMHO you can specify which userdb section is meant by a number or something like that. b) Instead of to put/remove the user, you can overwrite the file, if there is just one user, and remove the file at the very end. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9nkkHz1H7kL/d9rAQJ+VQf+Ns/nm/T95z0iq+LC7YlYZTZi7JShHLhh DOAfLZ/DEl2ca1S7ed3SzdHYJu6JLZyU6U//BcRzCCtjmrgHMURNPSlpzFDHKi0O 2kRstMoj0DfMb7r9YO1YG4EQkhWpkkie2ORtN0pubAowcucpwieOPnEcDDipp+Wo lDlxzZ1gTP+hInYGQLvB8cWF8QN2MuwNuUPXBCq3AUrOAoSRh91ALWbEJJ4TXqZE Y3SbGkkZF5cEPqtMULAm+kEd7bKjty0Drsa52LSdlcrQvje+QZmqfe6t3E60tz/I GrNzi2EPMbw5iJqHeYVupqPJWslopxDIZdSP5kboX1eNeaoEJFUGMw== =N8uo -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Thu Jul 31 07:11:06 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 31 Jul 2014 09:11:06 +0200 (CEST) Subject: LMTP during dsync migration In-Reply-To: References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 31 Jul 2014, Steffen Kaiser wrote: > On Wed, 30 Jul 2014, Jogi Hofm?ller wrote: > >>> Or better - disable LMTP service in Dovecot. Incoming mail will stay on >>> your MTA and when you're done, you just tell it to deliver everything >>> that piled up in the queue in the meantime >> >> Better but still not perfect ;) We have users that work late and I am >> sure they would complain when they don't receive email during migration >> nights. >> >> Still thinking ... > > In your original post you've wrote "While migrating a mailbox". So you > migrate one user after another. Also, if you want to disable LMTP for that > user, you want to disable IMAP and POP3, too, for the very same reason -> > or at least put them in read-only mode. > > 1) So, IMHO, your goal is to make the mail storage of one user read-only. > Experiment with ACLs. Make all the mailboxes of the user read-only. After > migration remove the ACLs. > > 2) Make the mail storage inaccessable during backup for just one user: > > How about adding another userdb { driver = passwd-file args = /.../%s/file > } as the first one, which disables the access to the one user's mail > storage currently migrated. %s would be lmtp, imap, pop3 and doveadm, > IMHO. Make sure, doveadm sees no user in this userdb, but the others do, > e.g. symlink the appropriate files and keep /.../doveadm/file > zero-length, in order to fall back to LDAP always. > > In short: doveadm must know the real path, all other services a faked one. > > The migration of one user would be: > put user in /.../{imap,pop3,lmtp}/file # or overwrite file with user > doveadm auth cache flush # make sure, user info is not cached already > migrate > remove user from /.../file > > a) > Besides the %s-way, there must be a way to have doveadm override the > settings in: > > userdb { > driver = passwd-file > args = /.../file > } > > in the line of: > doveadm -o userdb[*]/args=/dev/null .... > > [*] IMHO you can specify which userdb section is meant by a number or > something like that. > > b) > Instead of to put/remove the user, you can overwrite the file, if there is > just one user, and remove the file at the very end. Maybe, you need not no other userdb, but you can make use of %s in your LDAP userdb - filter, e.g. user_filter = (&(objectClass=posixAccount)(uid=%u)(!(deniedService=%Ls))) however, you must test, if Dovecot's auth caching does honor the different values of %s in this case. I mean, if doveadm queries the user data, the result will be cached, if the LMTP service queries next: does it get the result of doveadm or not. I suppose, this applies to both variants. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9nsCnz1H7kL/d9rAQIO9ggAuDB4ZlbD0kaZ6GmLILyHZZGCFX/+pldL sciBDsi4i+jzhx9b+QyRZQBafl4SsbzDa+8Aima40HqfE4ixKptx/3y1k0ftcP02 ZWgs6jj8pgkY5x1s/hhhDoE5RRE2wXwNJTd9O96XiaryFxhBgMDWy2qiiUXBVILt njB5udoU1WNH9TfdYPQVAHrC7YJbMAYzCb+7jM0HxFiwpwpiw9o59h7YwDx7D5/e 8hINfOTSWcU8tVBDNhjXRP3moawEGU2gkeBcA9ql6LCekLZm9f9mqZYrcbzdkWQJ kkJHTChZ+RP+Rgf6auP+rxzpnuvzk5+gSDBtJixvCPslji6thsW+Sg== =Khy7 -----END PGP SIGNATURE----- From mildred-ml at mildred.fr Thu Jul 31 07:33:10 2014 From: mildred-ml at mildred.fr (Mildred Ki'Lya) Date: Thu, 31 Jul 2014 09:33:10 +0200 Subject: Issue with exim and auth protocol [Solution found] In-Reply-To: <53D96481.6060408@gedalya.net> References: <53D95330.2080901@mildred.fr> <53D96481.6060408@gedalya.net> Message-ID: <53D9F136.4040006@mildred.fr> On 30/07/2014 23:32, Gedalya wrote: > Could it be related to something in your dovecot configuration (which > you didn't post)? > Despite the fact that an interesting conversation is developing in the > exim bug report, this setup does usually work, including on one of > your servers as you have indicated. On my end, I never had issues > between dovecot 2.1.7 and 2.2.13, using the exact same authenticator > config in exim. See at the end of the e-mail my dovecot configuration (my /etc/dovecot/local.conf). This configuration is included by the default dovecot configuration (as packaged by Debian, but I think there are not so many changes made by Debian). I agree that it could be related to my configuration, but I don't see how the changes I made could have altered how the auth server is working. I'm looking at the dovecot sources and found two different implementation for the auth protocol. One in auth-master-connection.c and one in auth-client-connection.c. One seems to send SPID and VERSION and wait for further commands before continuing. The other send the complete handshake. I think I'm connecting to a socket speaking the wrong protocol. exim is configured to use socket /var/run/dovecot/auth-userdb dovecot has the following configuration in 10-master.conf: service auth { # ... some comments removed ... unix_listener auth-userdb { #mode = 0666 #user = #group = } } I think I completely misunderstood how dovecot sockets were configured ... If I set up exim to connect to auth-client instead of auth-userdb, it fixes the problem (I get a meaningful error message, probably because things are not configured properly elsewhere). What I don't understand is that the socket auth-client is nowhere to be found in the configuration. Where is it specified? Also, I don't understand because the production server I have currently running have the following configuration in 10-master.conf: service auth { unix_listener auth-userdb { mode = 0660 user = vmail group = vmail } #SASL unix_listener auth-client { mode = 0660 user = vmail group = vmail } } And exim is configured to use auth-client socket, and everything works. I naively thought that I could remove auth-client and use auth+userdb instead when I was looking at this configuration. Could someone enlighten me how sockets are configured in dovecot? Thanks, Mildred ##### /etc/dovecot/local.conf ##### !include conf.d/auth-passwdfile.conf.ext log_path = /dev/stderr # FIXME: remove debug log auth_verbose = yes auth_verbose_passwords = plain auth_debug = yes auth_debug_passwords = yes mail_location = maildir:~/Maildir first_valid_uid = 1 ssl_cert = References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> <53D91111.7070306@thelounge.net> Message-ID: <53DA14DC.3020907@mur.at> Hi Harald, all, Am 2014-07-30 17:36, schrieb Reindl Harald: > normally you announce a mainantaince window for such migrations That's what we do. > why do you need dsync at all for such a migration? Migrating from cyrus to dovecot in a transparent manner. Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From skdovecot at smail.inf.fh-brs.de Thu Jul 31 10:31:55 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 31 Jul 2014 12:31:55 +0200 (CEST) Subject: Issue with exim and auth protocol [Solution found] In-Reply-To: <53D9F136.4040006@mildred.fr> References: <53D95330.2080901@mildred.fr> <53D96481.6060408@gedalya.net> <53D9F136.4040006@mildred.fr> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 31 Jul 2014, Mildred Ki'Lya wrote: > On 30/07/2014 23:32, Gedalya wrote: >> Could it be related to something in your dovecot configuration (which >> you didn't post)? >> Despite the fact that an interesting conversation is developing in the >> exim bug report, this setup does usually work, including on one of >> your servers as you have indicated. On my end, I never had issues >> between dovecot 2.1.7 and 2.2.13, using the exact same authenticator >> config in exim. > > > See at the end of the e-mail my dovecot configuration (my > /etc/dovecot/local.conf). This configuration is included by the default > dovecot configuration (as packaged by Debian, but I think there are not > so many changes made by Debian). > > I agree that it could be related to my configuration, but I don't see > how the changes I made could have altered how the auth server is working. > > I'm looking at the dovecot sources and found two different > implementation for the auth protocol. One in auth-master-connection.c > and one in auth-client-connection.c. One seems to send SPID and VERSION > and wait for further commands before continuing. The other send the > complete handshake. > > I think I'm connecting to a socket speaking the wrong protocol. > > exim is configured to use socket /var/run/dovecot/auth-userdb > dovecot has the following configuration in 10-master.conf: > > service auth { > # ... some comments removed ... > unix_listener auth-userdb { > #mode = 0666 > #user = > #group = > } > } > > > > I think I completely misunderstood how dovecot sockets were configured ... > If I set up exim to connect to auth-client instead of auth-userdb, it > fixes the problem (I get a meaningful error message, probably because > things are not configured properly elsewhere). > > What I don't understand is that the socket auth-client is nowhere to be > found in the configuration. Where is it specified? > > Also, I don't understand because the production server I have currently > running have the following configuration in 10-master.conf: > > service auth { > unix_listener auth-userdb { > mode = 0660 > user = vmail > group = vmail > } > > #SASL > unix_listener auth-client { > mode = 0660 > user = vmail > group = vmail > } > } > > And exim is configured to use auth-client socket, and everything works. > I naively thought that I could remove auth-client and use auth+userdb > instead when I was looking at this configuration. > > Could someone enlighten me how sockets are configured in dovecot? Well, first of all auth-userdb and auth-client are completely different things. exim must connect to auth-client and _not_ auth-userdb. 2nd: If the config does not enlist auth-client, look at the full config: doveconf -a There you see all effective settings. hence, I guess you need to replicate the setting from your running server into your local.conf in order to get exim access permissions. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9obG3z1H7kL/d9rAQJ/owf9G8F1D4yaO6kGn+BB3gC+U0ZEwRmZp6DE kKkoIWBk82SCPsmwc7LIcpAbh+zhEPx0A2Sk2Vw4qlXAd+xp8awGXjifeN5cyS7H vDNRQ4BeeaH1rrqjpRugAp+Sk5i8dhlMI14/lWUFzz1JZyOzBwwdUbOaKeB7v54Q BUBsjCVjOH1R4Qc/QKMPSrRdsrC5HQ3lE357z4O0DQsqK88+aQZvfbHZe64+IhE8 fE5QRJ0Jn7OvpWCyEfFFF1pCAZkaYdJlyD1gkmw/P8geZ5PPZ+ljRpsrrarh+/ka cj4tS9BWOAr6kKfodHlYTal6n4wkDkg6w1MwPQ9brEdBJR3gSUCcfA== =DeKm -----END PGP SIGNATURE----- From bourek at thinline.cz Thu Jul 31 10:33:28 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Thu, 31 Jul 2014 12:33:28 +0200 Subject: LMTP during dsync migration In-Reply-To: <53DA14DC.3020907@mur.at> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> <53D91111.7070306@thelounge.net> <53DA14DC.3020907@mur.at> Message-ID: <53DA1B78.5070403@thinline.cz> On 31.7.2014 12:05, Jogi Hofm?ller wrote: > Hi Harald, all, > > Am 2014-07-30 17:36, schrieb Reindl Harald: > >> normally you announce a mainantaince window for such migrations > > That's what we do. > >> why do you need dsync at all for such a migration? > > Migrating from cyrus to dovecot in a transparent manner. > > Cheers, > As far as I know you can do the warm - cold with dsync too. First you do backup on live (i.e. accessible for both imap and delivery) mailbox. This takes a long time on big mailbox, but that should not be an issue since the mailbox can be used normally. When it's done, you disable the mailbox (again, both imap and delivery) and repeat the backup, which should be relatively fast now. When that's done, enable mailbox on new storage and you're done. I don't think it's possible to have the mailbox available all the time during migration. Well, it's possible, but it seems like recipe for trouble. From mildred-ml at mildred.fr Thu Jul 31 11:01:22 2014 From: mildred-ml at mildred.fr (Mildred Ki'Lya) Date: Thu, 31 Jul 2014 13:01:22 +0200 Subject: How does unix_listener works? [Was: Issue with exim and auth protocol] In-Reply-To: References: <53D95330.2080901@mildred.fr> <53D96481.6060408@gedalya.net> <53D9F136.4040006@mildred.fr> Message-ID: <53DA2202.5050304@mildred.fr> > > Well, first of all auth-userdb and auth-client are completely > different things. > > exim must connect to auth-client and _not_ auth-userdb. > > 2nd: If the config does not enlist auth-client, look at the full config: > > doveconf -a > > There you see all effective settings. hence, I guess you need to > replicate the setting from your running server into your local.conf in > order to get exim access permissions. Thank you. What I don't understand is how unix_listener works and how to specify independently the socket file used and the protocol spoken on the socket. For example, to get postfix to work (I was using postfix before I used exim), we configure the auth service this way: service auth { unix_listener /var/spool/postfix/private/auth { ... } } What I deduced from this is that the unix_listener command took a file path as argument and the permissions inside the {} block. Now, when I look at the configuration for auth-userdb and auth-client, I see: service auth { unix_listener auth-client {... } unix_listener auth-userdb { ... } } Using the rule deduced above, I see two sockets being declared. auth-client is a path relative to /var/run/dovecot, and auth-userdb is also a path in /var/run/dovecot. I see no difference between the two, except the file path. I deduce then that those two sockets respond to the same protocol provided by the service auth. Obviously, I am wrong. Then, how does the auth service knows which protocol to speak on /var/run/dovecot/auth-userdb, /var/run/dovecot/auth-client and /var/spool/postfix/private/auth? This is not specified in the configuration (even doveconf -a). If I specify: service auth { unix_listener some-socket-file {... } } I suppose I'll find a socket in /var/run/dovecot/some-socket-file. Which protocol does it speak? More generally, is there somewhere when the configuration file is documented? I always wondered what happened when I redefined a section ("service auth" for example). Will it replace completely the previous section or will it only overwrite the variables specified? Thank you Mildred From trashcan at odo.in-berlin.de Thu Jul 31 11:25:06 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Thu, 31 Jul 2014 13:25:06 +0200 Subject: LMTP during dsync migration In-Reply-To: <53DA14DC.3020907@mur.at> References: "\"<53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net>" <53D8C2AC.3090209@thinline.cz>" <53D9039C.4010108@mur.at> <53D91111.7070306@thelounge.net> <53DA14DC.3020907@mur.at> Message-ID: <0d27f19774c686f94824992a94536eff@mx1.enfer-du-nord.net> Hi -- On 2014-07-31 12:05, Jogi Hofm?ller wrote: > Am 2014-07-30 17:36, schrieb Reindl Harald: >> why do you need dsync at all for such a migration? > > Migrating from cyrus to dovecot in a transparent manner. And additionaly, if one wants to switch mailbox formats whilst migration. Dsync is great in that scenario. I did so, migrating from a dovecot 1.2.x to 2.x server in the past. Not many users, not many mail involved. Technically I did what has been proposed already: Running an initial dsync run, running periodic differential sync until final switch. During switch I had had to shut down dovecot for a short time. In the meantime I use something like to block users during maintainance: passdb { From jogi at mur.at Thu Jul 31 11:30:19 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Thu, 31 Jul 2014 13:30:19 +0200 Subject: LMTP during dsync migration In-Reply-To: <53DA1B78.5070403@thinline.cz> References: <53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz> <53D8B68E.5080603@mur.at> <53D8BA8F.4060004@thelounge.net> <53D8C2AC.3090209@thinline.cz> <53D9039C.4010108@mur.at> <53D91111.7070306@thelounge.net> <53DA14DC.3020907@mur.at> <53DA1B78.5070403@thinline.cz> Message-ID: <53DA28CB.5020806@mur.at> Hi Jiri, all, Am 2014-07-31 12:33, schrieb Jiri Bourek: > As far as I know you can do the warm - cold with dsync too. First you do > backup on live (i.e. accessible for both imap and delivery) mailbox. > This takes a long time on big mailbox, but that should not be an issue > since the mailbox can be used normally. That's exactly what I was trying to describe in one of my previous emails (subject: incremental mailbox syncs for quick migration). Great to hear that this solution seems viable :) > When it's done, you disable the mailbox (again, both imap and delivery) > and repeat the backup, which should be relatively fast now. When that's > done, enable mailbox on new storage and you're done. Right, just as I thought. > I don't think it's possible to have the mailbox available all the time > during migration. Well, it's possible, but it seems like recipe for > trouble. Agreed. Just trying to keep the downtime as short as possible. Cheers, -- j.hofm?ller http://thesix.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From trashcan at odo.in-berlin.de Thu Jul 31 11:34:54 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Thu, 31 Jul 2014 13:34:54 +0200 Subject: LMTP during dsync migration In-Reply-To: <0d27f19774c686f94824992a94536eff@mx1.enfer-du-nord.net> References: "\"\\\"\\\\\\\"<53D7A647.30602@mur.at> <53D7ABF7.8000405@thinline.cz>" <53D8B68E.5080603@mur.at>" "<53D8BA8F.4060004@thelounge.net>\" \"" <53D8C2AC.3090209@thinline.cz>\" <53D9039C.4010108@mur.at> <53D91111.7070306@thelounge.net> "<53DA14DC.3020907@mur.at>\"" <0d27f19774c686f94824992a94536eff@mx1.enfer-du-nord.net> Message-ID: <8ff44e97c82dc8fe2f1eae59b7f4c811@mx1.enfer-du-nord.net> [sent to early, sorry] On 2014-07-31 12:05, Jogi Hofm?ller wrote: > Am 2014-07-30 17:36, schrieb Reindl Harald: > why do you need dsync at all for such a migration? > > Migrating from cyrus to dovecot in a transparent manner. And additionaly, if one wants to switch mailbox formats whilst migration. Dsync is great in that scenario. I did so, migrating from a dovecot 1.2.x to 2.x server in the past. Not many users, not many mail involved. Technically I did what has been proposed already: Running an initial dsync run, running periodic differential sync until final switch. During switch I had had to shut down dovecot for a short time. In the meantime I use something like to block users during maintainance: # temporary blocks passdb { driver = passwd-file deny = yes args = /path/to/deny-users } # regular passwd { driver = sql args = /path/to/dovecot-sql.conf } /path/to/deny-users holds username to block. But, I have to admit: that doesn't work for all of my users, I never found out why. Thst's why I finally decided for a hard shotdown of dovecot for the final switch. Regards and good luck, Michael From skdovecot at smail.inf.fh-brs.de Thu Jul 31 12:25:10 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 31 Jul 2014 14:25:10 +0200 (CEST) Subject: How does unix_listener works? [Was: Issue with exim and auth protocol] In-Reply-To: <53DA2202.5050304@mildred.fr> References: <53D95330.2080901@mildred.fr> <53D96481.6060408@gedalya.net> <53D9F136.4040006@mildred.fr> <53DA2202.5050304@mildred.fr> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 31 Jul 2014, Mildred Ki'Lya wrote: >> >> Well, first of all auth-userdb and auth-client are completely >> different things. >> >> exim must connect to auth-client and _not_ auth-userdb. >> >> 2nd: If the config does not enlist auth-client, look at the full config: >> >> doveconf -a >> >> There you see all effective settings. hence, I guess you need to >> replicate the setting from your running server into your local.conf in >> order to get exim access permissions. > > Thank you. > > What I don't understand is how unix_listener works and how to specify > independently the socket file used and the protocol spoken on the socket. > > For example, to get postfix to work (I was using postfix before I used > exim), we configure the auth service this way: > > service auth { > unix_listener /var/spool/postfix/private/auth { ... } > } > > What I deduced from this is that the unix_listener command took a file > path as argument and the permissions inside the {} block. > > Now, when I look at the configuration for auth-userdb and auth-client, I > see: > > service auth { > unix_listener auth-client {... } > unix_listener auth-userdb { ... } > } > > Using the rule deduced above, I see two sockets being declared. > auth-client is a path relative to /var/run/dovecot, and auth-userdb is > also a path in /var/run/dovecot. I see no difference between the two, > except the file path. I deduce then that those two sockets respond to > the same protocol provided by the service auth. > > Obviously, I am wrong. > > Then, how does the auth service knows which protocol to speak on > /var/run/dovecot/auth-userdb, /var/run/dovecot/auth-client and > /var/spool/postfix/private/auth? This is not specified in the > configuration (even doveconf -a). See http://wiki2.dovecot.org/Services#auth "With UNIX listeners the client type is selected based on the filename after the last "-" in the filename. For example "anything-userdb" is of "userdb" type. The default type is "client" for inet insteners and unrecognized UNIX listeners. " - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU9o1pnz1H7kL/d9rAQJHDAf/YQkjw3JktdxLq/5444UrBda1+dP15uQa 4yV4ocJOe2pvYok41saxB7qYvHHKIWjOMKVTPSyntjyzNklwNzCNB3k3UptBKlFn cRomJp2UXbn91xc1Z1JnBDlzPWOSh8DOqBo/pQhwFf+PhgyzDNz/YVclf9XhnD5b rLR/OPkQPtoEi7/m14riKjqSzIJVn2RDm9gX91V0jMcWjjSFybBid9dnQtzXElin W48im0izEYr/K9nT4RBdIh6kTcXwm7nzCjCe5zfXL8I1pn10Ij+6yIDXDNZqQM4M TAArRfhWCyPXdxHzut9Za3R6zD+qh6r2SO8hQCGn24Um45Jdq8Q6ug== =hNGK -----END PGP SIGNATURE----- From h.reindl at thelounge.net Thu Jul 31 14:20:03 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Thu, 31 Jul 2014 16:20:03 +0200 Subject: stop that list-spam In-Reply-To: References: <96FDED18-C9D5-4852-9DA6-AA00538ACECC@odo.in-berlin.de> <53D9416D.9020207@thelounge.net> Message-ID: <53DA5093.10500@thelounge.net> Am 31.07.2014 um 02:31 schrieb Nick Edwards: > Es ist in Ordnung, nichts dagegen Reindl, er ist so perfekt und macht > nie einen Fehler seit der Geburt :-> since *you* filter out my messages and so have no context just shut up especially as long you are unable to distinct between firstname and lastname it's not a matter of never making mistakes it's a matter of making *exactly the same* mistake within 30 minutes twice which indicates a hacked account or dunkness 30.07.2014 20:29 30.07.2014 20:55 > On 7/31/14, Michael Grimm wrote: >> >> My sincerest apologies to all, but ... >> >> On 30.07.2014, at 21:03, Reindl Harald wrote: >> >>> Account gehackt oder Volltrottel? >> >> ... that was simply one of those mistakes that do happen to human beings >> once in a while. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 246 bytes Desc: OpenPGP digital signature URL: From uothrawn at yahoo.com Thu Jul 31 14:52:47 2014 From: uothrawn at yahoo.com (G H) Date: Thu, 31 Jul 2014 07:52:47 -0700 Subject: Solr 4+ schema.xml? Message-ID: <1406818367.3431.YahooMailNeo@web161404.mail.bf1.yahoo.com> Does anyone have a Solr 4+ compatible schema.xml for dovecot indexing? I am trying to test to see if regex-based FTS searching works through IMAP, but Solr 4.9.0 is throwing an error, "SolrException: undefined field text", on startup with the schema.xml included with Dovecot 2.2.9. Thanks. G H From mildred-ml at mildred.fr Thu Jul 31 15:06:14 2014 From: mildred-ml at mildred.fr (Mildred Ki'Lya) Date: Thu, 31 Jul 2014 17:06:14 +0200 Subject: How does unix_listener works? [Was: Issue with exim and auth protocol] In-Reply-To: References: <53D95330.2080901@mildred.fr> <53D96481.6060408@gedalya.net> <53D9F136.4040006@mildred.fr> <53DA2202.5050304@mildred.fr> Message-ID: <53DA5B66.9020706@mildred.fr> On 31/07/2014 14:25, Steffen Kaiser wrote: > > See http://wiki2.dovecot.org/Services#auth > > "With UNIX listeners the client type is selected based on the filename > after the last "-" in the filename. For example "anything-userdb" is > of "userdb" type. The default type is "client" for inet insteners and > unrecognized UNIX listeners. " Thank you, I understand better now. From uothrawn at yahoo.com Thu Jul 31 15:20:04 2014 From: uothrawn at yahoo.com (G H) Date: Thu, 31 Jul 2014 08:20:04 -0700 Subject: Solr 4+ schema.xml? In-Reply-To: <1406818367.3431.YahooMailNeo@web161404.mail.bf1.yahoo.com> References: <1406818367.3431.YahooMailNeo@web161404.mail.bf1.yahoo.com> Message-ID: <1406820004.10774.YahooMailNeo@web161404.mail.bf1.yahoo.com> The issue was the df parameter in solrconfig.xml was referencing field text. I changed it to reference subject. ----- Original Message ----- From: G H To: "dovecot at dovecot.org" Cc: Sent: Thursday, July 31, 2014 10:52 AM Subject: Solr 4+ schema.xml? Does anyone have a Solr 4+ compatible schema.xml for dovecot indexing? I am trying to test to see if regex-based FTS searching works through IMAP, but Solr 4.9.0 is throwing an error, "SolrException: undefined field text", on startup with the schema.xml included with Dovecot 2.2.9. Thanks. G H From matthias at familie-sitte.org Thu Jul 31 15:23:22 2014 From: matthias at familie-sitte.org (Matthias Sitte) Date: Thu, 31 Jul 2014 10:23:22 -0500 Subject: INBOX subfolders not showing up Message-ID: <53DA5F6A.9000304@familie-sitte.org> Hi, I have a problem with INBOX subfolders and subscriptions which I can't solve... Maybe somebody has seen this, too... I can create regular subfolders (not in INBOX) and (un-)subscribe to them with Thunderbird. If I create subfolders in the INBOX with TB this seems to work now in v31 (just found this out), but with v24.6 neither INBOX subfolder creation nor subscriptions worked. When I modified the `subscriptions' file manually on the server, the folders would show up in TB, though. Maybe this was a TB bug, but quite similarly INBOX subfolders don't show up on iPhones (iOS up-to-date), but all other subfolders do. Any ideas what's going on? Best, Matthias ====================================================================== # dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 ext4 hostname = familie-sitte.org log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/srv/mail/%d/%n/Maildir:LAYOUT=fs managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster at familie-sitte.org protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } ssl_cert = References: <1406818367.3431.YahooMailNeo@web161404.mail.bf1.yahoo.com> <1406820004.10774.YahooMailNeo@web161404.mail.bf1.yahoo.com> Message-ID: Doesn't that mean it will ONLY search the subject and not the entire message? On Thu, Jul 31, 2014 at 10:20 AM, G H wrote: > The issue was the df parameter in solrconfig.xml was referencing field > text. I changed it to reference subject. > > > > ----- Original Message ----- > From: G H > To: "dovecot at dovecot.org" > Cc: > Sent: Thursday, July 31, 2014 10:52 AM > Subject: Solr 4+ schema.xml? > > Does anyone have a Solr 4+ compatible schema.xml for dovecot indexing? I > am trying to test to see if regex-based FTS searching works through IMAP, > but Solr 4.9.0 is throwing an error, "SolrException: undefined field text", > on startup with the schema.xml included with Dovecot 2.2.9. > > Thanks. > G H > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 From uothrawn at yahoo.com Thu Jul 31 16:46:51 2014 From: uothrawn at yahoo.com (G H) Date: Thu, 31 Jul 2014 09:46:51 -0700 Subject: solr_add_definite_query quotes queries Message-ID: <1406825211.53599.YahooMailNeo@web161401.mail.bf1.yahoo.com> So Solr 4.0 and higher supports regular expressions in searching. However, Dovecot is quoting search queries in solr_add_definite_query (via solr_add_str_arg). This breaks regex searching. I do a sample search for emails with "merged" in their body via the query /merg.*/. If you look at the Solr logs, it is sending: ? q=body:"/merg.*/" which is converted to body:\"/merg.*/\" inside Solr. but if it had sent only: ? q=body:/merg.*/ then regex would have worked. Is regular expression searching on the dashboard? I'm considering patching fts-backend-solr.c to not quote-enclose the search, but am looking for any better suggestions. Or perhaps not quote-enclose if the search is prefixed with RX: (ie: "RX:/merg.*/")... Thanks, G H From jelmer at debian.org Thu Jul 31 21:57:53 2014 From: jelmer at debian.org (Jelmer Vernooij) Date: Thu, 31 Jul 2014 23:57:53 +0200 Subject: [PATCH] Fix typo in src/imap-urlauth/imap-urlauth-worker.c In-Reply-To: <20140719225043.GA956@jelmer.co.uk> References: <20140719225043.GA956@jelmer.co.uk> Message-ID: <20140731215753.GA20356@jelmer.co.uk> On Sun, Jul 20, 2014 at 12:50:43AM +0200, Jelmer Vernooij wrote: > The attached trivial patch fixes a typo in src/imap-urlauth/imap-urlauth-worker.c. Ping? > diff -r fd0616d553b0 -r 6fabd9046558 src/imap-urlauth/imap-urlauth-worker.c > --- a/src/imap-urlauth/imap-urlauth-worker.c Fri Jul 11 16:49:35 2014 +0300 > +++ b/src/imap-urlauth/imap-urlauth-worker.c Sun Jul 20 00:29:35 2014 +0200 > @@ -478,7 +478,7 @@ > } > if (client_run_url(client) < 0) { > client_abort(client, > - "Session aborted: Fatal failure while transfering URL"); > + "Session aborted: Fatal failure while transferring URL"); > return 0; > } > } -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From Alfred.Pimminger at gmx.at Mon Jul 28 14:59:31 2014 From: Alfred.Pimminger at gmx.at (Pimminger Alfred) Date: Mon, 28 Jul 2014 14:59:31 +0000 Subject: not able to compile deleted_to_trash Plugin Message-ID: <490991D6720B3F44BC4230600E34A546018EAB984C@srv01.sma.local> Following version and content of .conf file ---------------------------------------------------------------------------------------- root at ABCD:/CavE/download/delete_to_trash# dovecot --version 2.2.9 root at ABCD:/CavE/download/delete_to_trash# dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-32-generic x86_64 Ubuntu 14.04.1 LTS auth_mechanisms = plain login log_path = /var/log/dovecot/dovecot.log mail_location = maildir:~/Maildir:LAYOUT=fs namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Gesendete { auto = subscribe special_use = \Sent } mailbox Junk { special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { driver = pam } passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = flags & NAMESPACE_FLAG_INBOX) ^ deleted-to-trash-plugin.c:19:21: note: each undeclared identifier is reported only once for each function it appears in deleted-to-trash-plugin.c: In function 'search_deleted_id': deleted-to-trash-plugin.c:40:14: error: 'struct last_copy_info' has no member named 'src_mailbox_name' if(last_copy.src_mailbox_name != NULL && strcmp(_mail->box->name, last_copy.src_mailbox_name) == 0) ^ deleted-to-trash-plugin.c:40:77: error: 'struct last_copy_info' has no member named 'src_mailbox_name' if(last_copy.src_mailbox_name != NULL && strcmp(_mail->box->name, last_copy.src_mailbox_name) == 0) ^ In file included from /usr/include/dovecot/module-context.h:4:0, from /usr/include/dovecot/mail-storage-private.h:4, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:46:34: error: 'struct last_copy_info' has no member named 'mail_id' mail_ids = array_get(&last_copy.mail_id, &count); ^ /usr/include/dovecot/array.h:44:12: note: in definition of macro 'ARRAY_TYPE_CAST_CONST' (typeof(*(array)->v)) ^ deleted-to-trash-plugin.c:46:14: note: in expansion of macro 'array_get' mail_ids = array_get(&last_copy.mail_id, &count); ^ deleted-to-trash-plugin.c:46:34: error: 'struct last_copy_info' has no member named 'mail_id' mail_ids = array_get(&last_copy.mail_id, &count); ^ /usr/include/dovecot/array.h:192:44: note: in definition of macro 'array_get' ARRAY_TYPE_CAST_CONST(array)array_get_i(&(array)->arr, count) ^ deleted-to-trash-plugin.c:58:28: error: 'struct last_copy_info' has no member named 'mail_id' if(array_count(&last_copy.mail_id) > 0) ^ /usr/include/dovecot/array.h:143:18: note: in definition of macro 'array_count' array_count_i(&(array)->arr) ^ deleted-to-trash-plugin.c:60:25: error: 'struct last_copy_info' has no member named 'mail_id' array_free(&last_copy.mail_id); ^ /usr/include/dovecot/array.h:111:17: note: in definition of macro 'array_free' array_free_i(&(array)->arr) ^ deleted-to-trash-plugin.c:61:27: error: 'struct last_copy_info' has no member named 'mail_id' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ /usr/include/dovecot/array.h:103:19: note: in definition of macro 'array_create' array_create_i(&(array)->arr, pool, element_size, init_count) ^ /usr/include/dovecot/array.h:38:2: note: in expansion of macro 'p_array_init' p_array_init(array, default_pool, init_count) ^ deleted-to-trash-plugin.c:61:4: note: in expansion of macro 'i_array_init' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ deleted-to-trash-plugin.c:61:27: error: 'struct last_copy_info' has no member named 'mail_id' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ /usr/include/dovecot/array.h:103:38: note: in definition of macro 'array_create' array_create_i(&(array)->arr, pool, element_size, init_count) ^ /usr/include/dovecot/array.h:38:2: note: in expansion of macro 'p_array_init' p_array_init(array, default_pool, init_count) ^ deleted-to-trash-plugin.c:61:4: note: in expansion of macro 'i_array_init' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ deleted-to-trash-plugin.c:63:15: error: 'struct last_copy_info' has no member named 'src_mailbox_name' if(last_copy.src_mailbox_name != NULL) ^ In file included from /usr/include/dovecot/lib.h:29:0, from deleted-to-trash-plugin.h:4, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:65:20: error: 'struct last_copy_info' has no member named 'src_mailbox_name' i_free(last_copy.src_mailbox_name); ^ /usr/include/dovecot/mempool.h:89:33: note: in definition of macro 'p_free' (pool)->v->free(pool, mem); \ ^ deleted-to-trash-plugin.c:65:4: note: in expansion of macro 'i_free' i_free(last_copy.src_mailbox_name); ^ deleted-to-trash-plugin.c:65:20: error: 'struct last_copy_info' has no member named 'src_mailbox_name' i_free(last_copy.src_mailbox_name); ^ /usr/include/dovecot/mempool.h:90:12: note: in definition of macro 'p_free' (mem) = NULL; \ ^ deleted-to-trash-plugin.c:65:4: note: in expansion of macro 'i_free' i_free(last_copy.src_mailbox_name); ^ deleted-to-trash-plugin.c:66:13: error: 'struct last_copy_info' has no member named 'src_mailbox_name' last_copy.src_mailbox_name = NULL; ^ deleted-to-trash-plugin.c: In function 'mailbox_open_or_create': deleted-to-trash-plugin.c:79:43: error: 'MAILBOX_OPEN_FAST' undeclared (first use in this function) box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT | MAILBOX_OPEN_NO_INDEX_FILES); ^ deleted-to-trash-plugin.c:79:63: error: 'MAILBOX_OPEN_KEEP_RECENT' undeclared (first use in this function) box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT | MAILBOX_OPEN_NO_INDEX_FILES); ^ deleted-to-trash-plugin.c:79:90: error: 'MAILBOX_OPEN_NO_INDEX_FILES' undeclared (first use in this function) box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT | MAILBOX_OPEN_NO_INDEX_FILES); ^ deleted-to-trash-plugin.c:79:2: warning: passing argument 1 of 'mailbox_open' from incompatible pointer type [enabled by default] box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT | MAILBOX_OPEN_NO_INDEX_FILES); ^ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: /usr/include/dovecot/mail-storage.h:479:5: note: expected 'struct mailbox *' but argument is of type 'struct mail_storage **' int mailbox_open(struct mailbox *box); ^ deleted-to-trash-plugin.c:79:2: error: too many arguments to function 'mailbox_open' box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT | MAILBOX_OPEN_NO_INDEX_FILES); ^ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: /usr/include/dovecot/mail-storage.h:479:5: note: declared here int mailbox_open(struct mailbox *box); ^ deleted-to-trash-plugin.c:79:6: warning: assignment makes pointer from integer without a cast [enabled by default] box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT | MAILBOX_OPEN_NO_INDEX_FILES); ^ deleted-to-trash-plugin.c:86:4: warning: implicit declaration of function 'mail_storage_mailbox_create' [-Wimplicit-function-declaration] if(mail_storage_mailbox_create(storage, name, FALSE) >= 0) ^ deleted-to-trash-plugin.c:89:5: warning: passing argument 1 of 'mailbox_open' from incompatible pointer type [enabled by default] box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT); ^ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: /usr/include/dovecot/mail-storage.h:479:5: note: expected 'struct mailbox *' but argument is of type 'struct mail_storage **' int mailbox_open(struct mailbox *box); ^ deleted-to-trash-plugin.c:89:5: error: too many arguments to function 'mailbox_open' box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT); ^ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: /usr/include/dovecot/mail-storage.h:479:5: note: declared here int mailbox_open(struct mailbox *box); ^ deleted-to-trash-plugin.c:89:9: warning: assignment makes pointer from integer without a cast [enabled by default] box = mailbox_open(&storage, name, NULL, MAILBOX_OPEN_FAST | MAILBOX_OPEN_KEEP_RECENT); ^ deleted-to-trash-plugin.c: In function 'copy_deleted_mail_to_trash': deleted-to-trash-plugin.c:104:52: error: 'struct mail_storage' has no member named 'ns' ns = get_users_inbox_namespace(_mail->box->storage->ns->user); ^ deleted-to-trash-plugin.c:127:3: warning: implicit declaration of function 'mailbox_keywords_free' [-Wimplicit-function-declaration] mailbox_keywords_free(trash_box, &keywords); ^ deleted-to-trash-plugin.c:140:3: warning: passing argument 1 of 'mailbox_close' from incompatible pointer type [enabled by default] mailbox_close(&trash_box); ^ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: /usr/include/dovecot/mail-storage.h:483:6: note: expected 'struct mailbox *' but argument is of type 'struct mailbox **' void mailbox_close(struct mailbox *box); ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_mail_update_flags': deleted-to-trash-plugin.c:178:53: error: 'struct mail_storage' has no member named 'ns' ns = get_users_inbox_namespace(_mail->box->storage->ns->user); ^ deleted-to-trash-plugin.c:181:113: error: 'struct mail_storage' has no member named 'ns' if(new_flags & MAIL_DELETED && !(strcmp(_mail->box->name, trashfolder_name) == 0 && strcmp(_mail->box->storage->ns->prefix, ns->prefix) == 0)) ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_copy': deleted-to-trash-plugin.c:229:112: error: 'struct last_copy_info' has no member named 'src_mailbox_name' i_info("from %s to %s, previous action from %s", mail->box->name, save_ctx->transaction->box->name, last_copy.src_mailbox_name); ^ deleted-to-trash-plugin.c:230:73: error: 'struct last_copy_info' has no member named 'src_mailbox_name' if(last_copy.transaction_context == save_ctx->transaction && last_copy.src_mailbox_name != NULL && strcmp(last_copy.src_mailbox_name, mail->box->name) == 0) ^ deleted-to-trash-plugin.c:230:118: error: 'struct last_copy_info' has no member named 'src_mailbox_name' if(last_copy.transaction_context == save_ctx->transaction && last_copy.src_mailbox_name != NULL && strcmp(last_copy.src_mailbox_name, mail->box->name) == 0) ^ In file included from /usr/include/dovecot/module-context.h:4:0, from /usr/include/dovecot/mail-storage-private.h:4, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:232:27: error: 'struct last_copy_info' has no member named 'mail_id' array_append(&last_copy.mail_id, &mail->uid, 1); ^ /usr/include/dovecot/array.h:152:19: note: in definition of macro 'array_append' array_append_i(&(array)->arr + ARRAY_TYPE_CHECK(array, data), \ ^ In file included from /usr/include/dovecot/lib.h:25:0, from deleted-to-trash-plugin.h:4, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:232:27: error: 'struct last_copy_info' has no member named 'mail_id' array_append(&last_copy.mail_id, &mail->uid, 1); ^ /usr/include/dovecot/macros.h:155:26: note: in definition of macro 'COMPILE_ERROR_IF_TRUE' (sizeof(char[1 - 2 * !!(condition)]) - 1) ^ /usr/include/dovecot/array.h:48:2: note: in expansion of macro 'COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE' COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE( \ ^ /usr/include/dovecot/array.h:152:33: note: in expansion of macro 'ARRAY_TYPE_CHECK' array_append_i(&(array)->arr + ARRAY_TYPE_CHECK(array, data), \ ^ deleted-to-trash-plugin.c:232:4: note: in expansion of macro 'array_append' array_append(&last_copy.mail_id, &mail->uid, 1); ^ In file included from /usr/include/dovecot/module-context.h:4:0, from /usr/include/dovecot/mail-storage-private.h:4, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:233:42: error: 'struct last_copy_info' has no member named 'mail_id' i_info("nr %i", array_count(&last_copy.mail_id)); ^ /usr/include/dovecot/array.h:143:18: note: in definition of macro 'array_count' array_count_i(&(array)->arr) ^ deleted-to-trash-plugin.c:238:29: error: 'struct last_copy_info' has no member named 'mail_id' if(array_count(&last_copy.mail_id) > 0) ^ /usr/include/dovecot/array.h:143:18: note: in definition of macro 'array_count' array_count_i(&(array)->arr) ^ deleted-to-trash-plugin.c:240:26: error: 'struct last_copy_info' has no member named 'mail_id' array_free(&last_copy.mail_id); ^ /usr/include/dovecot/array.h:111:17: note: in definition of macro 'array_free' array_free_i(&(array)->arr) ^ deleted-to-trash-plugin.c:241:28: error: 'struct last_copy_info' has no member named 'mail_id' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ /usr/include/dovecot/array.h:103:19: note: in definition of macro 'array_create' array_create_i(&(array)->arr, pool, element_size, init_count) ^ /usr/include/dovecot/array.h:38:2: note: in expansion of macro 'p_array_init' p_array_init(array, default_pool, init_count) ^ deleted-to-trash-plugin.c:241:5: note: in expansion of macro 'i_array_init' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ deleted-to-trash-plugin.c:241:28: error: 'struct last_copy_info' has no member named 'mail_id' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ /usr/include/dovecot/array.h:103:38: note: in definition of macro 'array_create' array_create_i(&(array)->arr, pool, element_size, init_count) ^ /usr/include/dovecot/array.h:38:2: note: in expansion of macro 'p_array_init' p_array_init(array, default_pool, init_count) ^ deleted-to-trash-plugin.c:241:5: note: in expansion of macro 'i_array_init' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ deleted-to-trash-plugin.c:246:28: error: 'struct last_copy_info' has no member named 'mail_id' array_append(&last_copy.mail_id, &mail->uid, 1); ^ /usr/include/dovecot/array.h:152:19: note: in definition of macro 'array_append' array_append_i(&(array)->arr + ARRAY_TYPE_CHECK(array, data), \ ^ In file included from /usr/include/dovecot/lib.h:25:0, from deleted-to-trash-plugin.h:4, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:246:28: error: 'struct last_copy_info' has no member named 'mail_id' array_append(&last_copy.mail_id, &mail->uid, 1); ^ /usr/include/dovecot/macros.h:155:26: note: in definition of macro 'COMPILE_ERROR_IF_TRUE' (sizeof(char[1 - 2 * !!(condition)]) - 1) ^ /usr/include/dovecot/array.h:48:2: note: in expansion of macro 'COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE' COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE( \ ^ /usr/include/dovecot/array.h:152:33: note: in expansion of macro 'ARRAY_TYPE_CHECK' array_append_i(&(array)->arr + ARRAY_TYPE_CHECK(array, data), \ ^ deleted-to-trash-plugin.c:246:5: note: in expansion of macro 'array_append' array_append(&last_copy.mail_id, &mail->uid, 1); ^ deleted-to-trash-plugin.c:247:14: error: 'struct last_copy_info' has no member named 'src_mailbox_name' last_copy.src_mailbox_name = i_strdup(mail->box->name); ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_transaction_commit': deleted-to-trash-plugin.c:267:2: warning: passing argument 2 of 'lbox->super.transaction_commit' from incompatible pointer type [enabled by default] int ret = lbox->super.transaction_commit(t, uid_validity_r, first_saved_uid_r, last_saved_uid_r); ^ deleted-to-trash-plugin.c:267:2: note: expected 'struct mail_transaction_commit_changes *' but argument is of type 'uint32_t *' deleted-to-trash-plugin.c:267:2: error: too many arguments to function 'lbox->super.transaction_commit' deleted-to-trash-plugin.c: At top level: deleted-to-trash-plugin.c:284:107: warning: 'enum mailbox_open_flags' declared inside parameter list [enabled by default] deleted_to_trash_mailbox_open(struct mail_storage *storage, const char *name, struct istream *input, enum mailbox_open_flags flags) ^ deleted-to-trash-plugin.c:284:107: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default] deleted-to-trash-plugin.c:284:126: error: parameter 4 ('flags') has incomplete type deleted_to_trash_mailbox_open(struct mail_storage *storage, const char *name, struct istream *input, enum mailbox_open_flags flags) ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_mailbox_open': deleted-to-trash-plugin.c:290:23: error: 'struct mail_storage_vfuncs' has no member named 'mailbox_open' box = lstorage->super.mailbox_open(storage, name, input, flags); ^ deleted-to-trash-plugin.c:298:29: warning: assignment from incompatible pointer type [enabled by default] box->v.transaction_commit = deleted_to_trash_transaction_commit; ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_mail_storage_created': deleted-to-trash-plugin.c:327:12: error: 'struct mail_storage_vfuncs' has no member named 'mailbox_open' storage->v.mailbox_open = deleted_to_trash_mailbox_open; ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_plugin_init': deleted-to-trash-plugin.c:364:28: error: lvalue required as left operand of assignment hook_mail_storage_created = deleted_to_trash_mail_storage_created; ^ deleted-to-trash-plugin.c:367:28: error: lvalue required as left operand of assignment hook_mailbox_list_created = deleted_to_trash_mailbox_list_created; ^ In file included from /usr/include/dovecot/module-context.h:4:0, from /usr/include/dovecot/mail-storage-private.h:4, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:370:25: error: 'struct last_copy_info' has no member named 'mail_id' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ /usr/include/dovecot/array.h:103:19: note: in definition of macro 'array_create' array_create_i(&(array)->arr, pool, element_size, init_count) ^ /usr/include/dovecot/array.h:38:2: note: in expansion of macro 'p_array_init' p_array_init(array, default_pool, init_count) ^ deleted-to-trash-plugin.c:370:2: note: in expansion of macro 'i_array_init' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ deleted-to-trash-plugin.c:370:25: error: 'struct last_copy_info' has no member named 'mail_id' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ /usr/include/dovecot/array.h:103:38: note: in definition of macro 'array_create' array_create_i(&(array)->arr, pool, element_size, init_count) ^ /usr/include/dovecot/array.h:38:2: note: in expansion of macro 'p_array_init' p_array_init(array, default_pool, init_count) ^ deleted-to-trash-plugin.c:370:2: note: in expansion of macro 'i_array_init' i_array_init(&last_copy.mail_id, TRASH_LIST_INITSIZE); ^ deleted-to-trash-plugin.c:371:11: error: 'struct last_copy_info' has no member named 'src_mailbox_name' last_copy.src_mailbox_name = NULL; ^ deleted-to-trash-plugin.c: In function 'deleted_to_trash_plugin_deinit': deleted-to-trash-plugin.c:377:28: error: lvalue required as left operand of assignment hook_mail_storage_created = deleted_to_trash_next_hook_mail_storage_created; ^ deleted-to-trash-plugin.c:378:28: error: lvalue required as left operand of assignment hook_mailbox_list_created = deleted_to_trash_next_hook_mailbox_list_created; ^ deleted-to-trash-plugin.c:380:14: error: 'struct last_copy_info' has no member named 'src_mailbox_name' if(last_copy.src_mailbox_name != NULL) ^ In file included from /usr/include/dovecot/lib.h:29:0, from deleted-to-trash-plugin.h:4, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:382:19: error: 'struct last_copy_info' has no member named 'src_mailbox_name' i_free(last_copy.src_mailbox_name); ^ /usr/include/dovecot/mempool.h:89:33: note: in definition of macro 'p_free' (pool)->v->free(pool, mem); \ ^ deleted-to-trash-plugin.c:382:3: note: in expansion of macro 'i_free' i_free(last_copy.src_mailbox_name); ^ deleted-to-trash-plugin.c:382:19: error: 'struct last_copy_info' has no member named 'src_mailbox_name' i_free(last_copy.src_mailbox_name); ^ /usr/include/dovecot/mempool.h:90:12: note: in definition of macro 'p_free' (mem) = NULL; \ ^ deleted-to-trash-plugin.c:382:3: note: in expansion of macro 'i_free' i_free(last_copy.src_mailbox_name); ^ In file included from /usr/include/dovecot/module-context.h:4:0, from /usr/include/dovecot/mail-storage-private.h:4, from deleted-to-trash-plugin.h:5, from deleted-to-trash-plugin.c:2: deleted-to-trash-plugin.c:384:23: error: 'struct last_copy_info' has no member named 'mail_id' array_free(&last_copy.mail_id); ^ /usr/include/dovecot/array.h:111:17: note: in definition of macro 'array_free' array_free_i(&(array)->arr) ^ make: *** [lib_deleted_to_trash_plugin.so] Fehler 1 ---------------------------------------------------------------------------------------- First I thought that something with the path setting in the Makefile is wrong. The only thing I've seen is than only the folder /usr/include/dovecot .exists - not the following subdirectories : -I/usr/include/dovecot/src \ -I/usr/include/dovecot/src/lib \ -I/usr/include/dovecot/src/lib-storage \ -I/usr/include/dovecot/src/lib-mail \ -I/usr/include/dovecot/src/lib-imap \ -I/usr/include/dovecot/src/lib-index Has anyone some suggestions for my problem?