Re: sa-learn with remote Dovecot folders
Thanks for your reply. You got me thinking towards the antispam plugin which I have nto used before, but can you elaborate if my users are system users and the training is done only via a cron entry? Andreas On 03/04/15 16:27, Gedalya wrote: On 04/03/2015 06:13 AM, Andreas Kasenides wrote: Hi all! The set-up I have is a classic one: 1. one or more Dovecot relay/directors Postfix SMTP servers in DMZ 2. one or more backend IMAP/SMTP servers on the inside network 3. There may or may not be separate incoming or outgoing designated SMTP servers. Now the desired functionality is (of course): 1. relay machines receive messages from outside AND inside 2. relays check for all the bad things (spam, viruses etc). 3. for incoming messages relays check for valid local users and reject messages for invalid users 4. after all checks are done incoming messages are transferred to the backend systems where they are accessed via the Dovecot directors While all the above works nicely, the problem I have is how to train my spamassassin (used by amavisd) on the front ends when all messages are on the back ends. Of course transferring the spam detection procedures internally is not such a great option.Am I missing something? I tried googling for info but nothing substantial turned up. Thanks. I use ssh. The exact details depend on your setup, of course. Do you use system users of virtual users? What triggers the training? Is it the antispam plugin?
sa-learn with remote Dovecot folders
Hi all! The set-up I have is a classic one: 1. one or more Dovecot relay/directors Postfix SMTP servers in DMZ 2. one or more backend IMAP/SMTP servers on the inside network 3. There may or may not be separate incoming or outgoing designated SMTP servers. Now the desired functionality is (of course): 1. relay machines receive messages from outside AND inside 2. relays check for all the bad things (spam, viruses etc). 3. for incoming messages relays check for valid local users and reject messages for invalid users 4. after all checks are done incoming messages are transferred to the backend systems where they are accessed via the Dovecot directors While all the above works nicely, the problem I have is how to train my spamassassin (used by amavisd) on the front ends when all messages are on the back ends. Of course transferring the spam detection procedures internally is not such a great option.Am I missing something? I tried googling for info but nothing substantial turned up. Thanks. -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
Re: Dovecot Oy merger with Open-Xchange AG
On 03/04/15 16:09, Jerry wrote: On Fri, 03 Apr 2015 08:42:42 -0400, Charles Marcus stated: People, PLEASE do not engage Reindl on the list, it always results in this kind of garbage that the adults on the list could do without. If you feel compelled to 'call him out', then by all means do so, but do it PRIVATELY. It is not just Reindl. People like Nick who feel compelled to continue this persiflage are as bad as the originator. I have just created a sieve rule to send Reindl, Nick and a few other individuals who feel the need to try and show their immaturity to /dev/null. I read this forum to learn about Dovecot, not to listen to the rantings of a few Testosterone poisoned, immature posters. Please share. I know its easy to do, but share anyway! -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
Re: Dovecot Oy merger with Open-Xchange AG
On 26/03/15 13:05, Bernd Petrovitsch wrote: On Mon, 2015-03-23 at 16:08 +0200, Andreas Kasenides wrote: I am usually emotionally (at least) against of open-source projects loosing their independence to large corporations. Possibly due to bad OX-AG is a large corporation? Did I miss something? Kind regards, Bernd I have no idea how large is OX-AG. That is not what I said anyway. At least not what I meant. I was trying to emphasize large or larger commercial entities trying to take advantage of the OSS community. Which happened many times in the past. Andreas -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
Re: Dovecot Oy merger with Open-Xchange AG
I hate to have started this, especially the sister thread that has dissented into a flame war of what is OSS. Let me say that I believe there is nothing wrong trying to make money on ones efforts. Actually it is a must. How can anyone continue to put efforts into a project when there is no reward? Especially when most of the effort is by a single individual. Secondly there comes a point in time when any project needs help to advance. Any one individual will be unable to manage all the things that need to be done. It will either become a team effort of individuals employed elsewhere or somehow enter the commercial sector in some form. Both of these models have many examples out there and in the mean time maintaining their OSS root and community. What I was mostly worried about was a sudden and rapid commercialization of the project in such a way that it completely disappears from the OSS community. I will give you an extreme example that we had the pleasure to be involved as payed customers and debugging contributors: KnowledgeTree DMS. If you do not know the story you will simply not find it. After years of the community contributing to the project a sudden shift to complete commercialization destroyed the project entirely: ie sourceforge project closed, source code disappeared, mailing lists vanished even the domain name name closed down. If it wasn't for third party storage/downloading sites the project source code would have been practically non-existent. I consider such behavior firstly immoral since a project's success is not only its design but largely also its debugging, mostly done by thousands of unknown helpers writing their experiences and problems in mailing lists. I hope Timo manages well, keeps the community going but also makes a living (or a ton of money ) out of Dovecot. He deserves it. It is not impossible, others have done so successfully. On 25/03/15 22:46, Daniel Miller wrote: On 3/19/2015 3:26 AM, Timo Sirainen wrote: Hi all, Today I can finally announce that Dovecot Oy company has merged with Open-Xchange AG. This helps us to get more Dovecot developers, support people and so on. Most importantly, eventually it should allow me to get back to doing what I like the most: Designing new and interesting stuff for Dovecot and perfecting the old stuff :) OX is a great match to Dovecot going forward. They also really like open source and share our plans for the future. Nothing big will change as a result of this merger: Dovecot will stay Dovecot with its own name and release schedules. We're not going to force OX and Dovecot to be the same product, other than having a somewhat deeper integration between them. My initial impression is...sounds great! Then, after further thought, and watching the flame war, I've changed my mind to...sounds great! I'm operating under the assumption that you are continuing to be in charge of Dovecot and will choose what and how to implement changes and fixes. I'm further operating under the assumption that you may choose to have certain features, appropriate for larger installations, that you will want to receive compensation for from your users. And I'm assuming that by having OX behind you, those initial assumptions remain - Dovecot remains your baby, you will grow it as you see fit - but now you've got some financial backing that allows you more freedom to continue to develop Dovecot for general-purpose use while reasonably having certain features developed to support the paid model. If I'm mistaken then please correct me - but I'm seeing nothing but upside. Certainly for you, and if you were to abandon open source Dovecot today (which I've seen absolutely no indication) you've already provided a tool that has a significant user base and you deserve to be rewarded for it. But based on your previous actions and your original post, and I have no reason not to take you at your word, this sounds like a win/win for Dovecot developers and users. Congratulations!
Re: Dovecot Oy merger with Open-Xchange AG
I find it extremely interesting that no one has commented on the merger of Dovecot Oy and Open-Xchange AG as announced by Timo on the 19th. Is this something that was known a long time ago and I missed? OK checked the on-line archive of the mailing list, no comments there - its not my email set-up - LOL. I am usually emotionally (at least) against of open-source projects loosing their independence to large corporations. Possibly due to bad experiences in the past when OSS were driven from Open to Obscure in the process of trying to make money out of them. I have several examples in mind but I will not give names. At least that is the impression I have which might be entirely wrong since when big companies begin to ask for large sums of money we just have to move away due to the small budget. Anyway this is not to about judging the move. Which I cannot do since I have no knowledge whatsover of the Dovecot enterprise internals and the difficulties that come with managing a leading software product. And, secondly, since I am (my employer ie) a non paying customer!! I was just struck by the fact that no one has commented on it. I wish Dovecot the best in the new environment. Andreas On 19/03/15 12:26, Timo Sirainen wrote: Hi all, Today I can finally announce that Dovecot Oy company has merged with Open-Xchange AG. This helps us to get more Dovecot developers, support people and so on. Most importantly, eventually it should allow me to get back to doing what I like the most: Designing new and interesting stuff for Dovecot and perfecting the old stuff :) OX is a great match to Dovecot going forward. They also really like open source and share our plans for the future. Nothing big will change as a result of this merger: Dovecot will stay Dovecot with its own name and release schedules. We're not going to force OX and Dovecot to be the same product, other than having a somewhat deeper integration between them. Here are the press release links about it: http://www.dovecot.fi/open-xchange-and-dovecot-announce-merger-to-create-worlds-leading-open-source-messaging-software-provider/ http://www.open-xchange.com/dovecot http://www.open-xchange.com/announcements/18 -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
Re: Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
On 10/03/15 11:40, Timo Sirainen wrote: I think it's pure chance that it happens to crash that way. I don't see how the duplicate checking could have affected this crash. Oh! Do you mean Timo, that Computer Science is non-deterministic! Is there chance, therefore luck, to it? Just kidding! Thanks for all the the good work you and your associates are doing. For us in the education sector and with dwindling money supplies you are a life saver. Thanks. Andreas -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
users of dbox format
I am interested in finding out your experiences with using the dbox format (especially mdbox) if you use this format. I am contemplating changing my maildir setup to mdbox but I still need to make a case for it against maildir which has become a de-facto standard and provides sort of a secure basis in case of software changes. Your input will be appreciated. -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
dovecot´s multiple quota roots
I am trying to find out how Dovecot behaves when there are multiple
quota roots.
I could not find something authoritative on this.
For example, on a nicely running server that used fs quota I now have in
90-quota.conf
plugin {
quota = fs:Mail Quota:user:mount=/Mail
quota2 = maildir:Mail User Quota
}
When I do
doveadm quota get -u atrige01
Quota name TypeValue Limit
%
Mail Quota STORAGE 80036 204800
39
Mail User Quota STORAGE 79306 -
0
Mail User Quota MESSAGE 304 -
0
Apparently both STORAGE quotas values are the same. The question is
which of the two
is being used by Dovecot. If I insert a limit on the maildir quota which
of the two will be used?
I am using Dovecot 2.2.12.
thank you
Re: mail_location hashing lowercasing?
On 31-08-2014 16:12, Sven Hartge wrote: Ralf Hildebrandt r...@sys4.de wrote: * Sven Hartge s...@svenhartge.de: I have home=/srv/mail/%2NLn/%2.16NLn/%Ln/ in my auth-ldap.conf.ext and this gives me a path like this: /srv/mail/0/08/myusername I use version 2.2.13 of dovecot. I'm on 2.1.17 :( %N could be a 2.2 feature. Someone with besser memory of version changes will have to clarify this. S° %N requires a 2.2.3+ Dovecot. But %H will do the trick for previous versions. BUT %H will give a bad distribution if your %n ends in the same characters ex. username@your.domain. This can be rectified by reversing the string using %R. Have not tried this but could %2.256HRLu do the trick? Have fun Andreas
[Dovecot] Dovecot proxy and Postfix SASL
Can somebody please verify that currently (v 2.2.9) SMTP AUTH using SASL from Postfix with Dovecot proxy is still not supported as discussed in these threads (especially the first one)? http://www.dovecot.org/list/dovecot/2012-August/067977.html http://www.dovecot.org/list/dovecot/2011-May/059107.html As I understand it is possible to use saslauthd to do this by using the remote imap option (rimap). Such a facility is important since I am attempting to separate the outward facing servers (dovecot proxy, postfix relay) that have no knowledge of user databases from the backends. thanx Andreas
Re: [Dovecot] Dovecot proxy and Postfix SASL
To be fair on this: The main driver behind this is security and having front end systems in a DMZ with only minimal (if any) access to the back end servers. Of course saslauthd will need SOME access to the remote (back-end) IMAP (one IP port?). But this can also be accomplished by having the front end Postfix authenticate on the Dovecot back-end by setting it up to talk to the auth process via an ip-listener ALSO on just one IP port. Does this make sense? AM I missing something? Andreas On 17-12-2013 14:48, Andreas Kasenides wrote: Can somebody please verify that currently (v 2.2.9) SMTP AUTH using SASL from Postfix with Dovecot proxy is still not supported as discussed in these threads (especially the first one)? http://www.dovecot.org/list/dovecot/2012-August/067977.html http://www.dovecot.org/list/dovecot/2011-May/059107.html As I understand it is possible to use saslauthd to do this by using the remote imap option (rimap). Such a facility is important since I am attempting to separate the outward facing servers (dovecot proxy, postfix relay) that have no knowledge of user databases from the backends. thanx Andreas
[Dovecot] Enabling quota
Hello everybody. Sorry if this has been answered before, I just could not find any info. Just point me if that is so. Can somebody please explain why there is no option --with-quota (ot may be --with-fs-quota) for the configure command? As it stands now, at least for the fs back-end the only thing that tells us that Dovecot does not do quotas is after the build/configuration we get dovecot: imap(xxdxx): Error: quotactl(Q_GETQUOTA, csfs9.cs.ucy.ac.cy:/mail) failed: No such file or directory which essentially means that during the build no quota development libraries were found and therefore fs quota will not function. This is rather confusing and the above error does not help much. Note also that dovecot --build-options is also silent on this. I suppose other back-ends do not have this requirement since there is no need for such devel libraries. thankx Andreas
Re: [Dovecot] Failute to compile of pigeonhole-0.4.2 with Dovecot 2.2.7
On 26-11-2013 22:39, Stephan Bosch wrote: On 11/26/2013 3:27 PM, Andreas Kasenides wrote: On trying to compile pigeonhole-0.4.2 on Dovecot 2.2.7 on a CentOS 6.4 machine Linux xxx.xxx 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with ./configure --with-dovecot=/usr/local/lib/dovecot I get the following error: /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot -I../.. -I../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT sieve-storage.lo -MD -MP -MF .deps/sieve-storage.Tpo -c -o sieve-storage.lo sieve-storage.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot -I../.. -I../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT sieve-storage.lo -MD -MP -MF .deps/sieve-storage.Tpo -c sieve-storage.c -fPIC -DPIC -o .libs/sieve-storage.o sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_set': sieve-storage.c:702: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:702: error: (Each undeclared identifier is reported only once sieve-storage.c:702: error: for each function it appears in.) sieve-storage.c:702: error: expected ')' before string constant sieve-storage.c:693: warning: unused parameter 'name' sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_rename': sieve-storage.c:718: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:718: error: expected ')' before string constant sieve-storage.c:720: error: expected ')' before string constant sieve-storage.c:709: warning: unused parameter 'oldname' sieve-storage.c:709: warning: unused parameter 'newname' sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_unset': sieve-storage.c:738: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:738: error: expected ')' before string constant sieve-storage.c:729: warning: unused parameter 'name' make[3]: *** [sieve-storage.lo] Error 1 make[3]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2/src/lib-sievestorage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2' make: *** [all] Error 2 I tried this here and I cannot reproduce this problem. It looks as though your installed dovecot at /usr/local/lib/dovecot is older than 2.2.7. Can you verify? What happens if you point it directly at your compiled Dovecot source tree? Regards, Stephan. Thank you Stephan. You are right. This was a 2.2.4 Dovecot. Sorry. Upgrading solved this problem.Now on to the configuration. Andreas
Re: [Dovecot] Enabling quota
On 27-11-2013 18:59, Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 27 Nov 2013, Andreas Kasenides wrote: Sorry if this has been answered before, I just could not find any info. Just point me if that is so. Can somebody please explain why there is no option --with-quota (ot may be --with-fs-quota) for the configure command? As it stands now, at least for the fs back-end the only thing that tells us that Dovecot does not do quotas is after the build/configuration we get dovecot: imap(xxdxx): Error: quotactl(Q_GETQUOTA, csfsxxx.cs.ucy.ac.cy:/mail) failed: No such file or directory which essentially means that during the build no quota development libraries were found and therefore fs quota will not function. This is rather confusing and the above error does not help much. Note also that dovecot --build-options is also silent on this. I suppose other back-ends do not have this requirement since there is no need for such devel libraries. in which development library your system needs? I thought that error message means, that the file csfsxxx.cs.ucy.ac.cy:/mail does not exist (or that there is no quota there). - -- Steffen Kaiser Exactly here is the confusion. I have verified that this error is not related to the actual mount but the way Dovecot has been built. Actually the existence of the development libraries. In my case on a CentOS system it needs to find the quota-devel libraries which it finds and silently builds quota support for the fs back-end. Note that nothing afterwards tells you that that has happened!! I think!!! Andreas
[Dovecot] Failute to compile of pigeonhole-0.4.2 with Dovecot 2.2.7
On trying to compile pigeonhole-0.4.2 on Dovecot 2.2.7 on a CentOS 6.4 machine Linux xxx.xxx 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with ./configure --with-dovecot=/usr/local/lib/dovecot I get the following error: /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot -I../.. -I../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT sieve-storage.lo -MD -MP -MF .deps/sieve-storage.Tpo -c -o sieve-storage.lo sieve-storage.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot -I../.. -I../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT sieve-storage.lo -MD -MP -MF .deps/sieve-storage.Tpo -c sieve-storage.c -fPIC -DPIC -o .libs/sieve-storage.o sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_set': sieve-storage.c:702: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:702: error: (Each undeclared identifier is reported only once sieve-storage.c:702: error: for each function it appears in.) sieve-storage.c:702: error: expected ')' before string constant sieve-storage.c:693: warning: unused parameter 'name' sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_rename': sieve-storage.c:718: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:718: error: expected ')' before string constant sieve-storage.c:720: error: expected ')' before string constant sieve-storage.c:709: warning: unused parameter 'oldname' sieve-storage.c:709: warning: unused parameter 'newname' sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_unset': sieve-storage.c:738: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:738: error: expected ')' before string constant sieve-storage.c:729: warning: unused parameter 'name' make[3]: *** [sieve-storage.lo] Error 1 make[3]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2/src/lib-sievestorage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2' make: *** [all] Error 2 Dovecot 2.2.7 compiles and runs fine. Any help appreciated. Andreas
[Dovecot] Dovecot software testing and release practice
Since this, it seems, was lost in, the now infamous, 2.2.9 thread I would like to resubmit the following proposal for Timo's consideration. Thanks Timo for doing an excellent job. I believe that the following will add further value to Dovecot in the long run. Thankx Andreas On 23-11-2013 3:47, Noel Butler wrote: On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: * Thomas Leuxner t...@leuxner.net: * Ralf Hildebrandt ralf.hildebra...@charite.de 2013.11.22 09:44: Which patch? http://www.dovecot.org/list/dovecot/2013-November/093654.html Pigeonhole related patches. Damn. Those are biting me as well :/ These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most software does, or gets his devs and a community of official testerseach with wildly different configurations and set ups, ASF have an excellent model that could be followed, bunch of devs and testers who each report on different distros and configs, why? because no single dev can imagine and test every possible configuration. it might just save dovecot's good name, I recall a lot of damage was done to that in the circles I'm in when 2.0 was released with patches nearly every few days and weeks, I know a few ISP's and businesses that went back to courier or Wu's because major bugs were getting in often, though it has been a lot better since 2.1 series, until this release that is :) I second this and offer my services for two, three different system configs from Dovecot's plain old simple config with MAILDIR to slightly more complicated configurations with proxying/LDAP/dsync/mySQL etc based on virtualization with KVM. I also propose that upon employing above strategy that Timo should come up with a release cycles (long term, short term) with announced targets. Patches should be released as patches strictly as needed, not releases, and should be announced on a low traffic list like he is already doing with releases. OR something along these lines. I know these are growing pains but essential. Email systems are CRITICAL for most of us. Andreas
Re: [Dovecot] 2.2.9
On 23-11-2013 3:47, Noel Butler wrote: On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: * Thomas Leuxner t...@leuxner.net: * Ralf Hildebrandt ralf.hildebra...@charite.de 2013.11.22 09:44: Which patch? http://www.dovecot.org/list/dovecot/2013-November/093654.html Pigeonhole related patches. Damn. Those are biting me as well :/ These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most software does, or gets his devs and a community of official testers each with wildly different configurations and set ups, ASF have an excellent model that could be followed, bunch of devs and testers who each report on different distros and configs, why? because no single dev can imagine and test every possible configuration. it might just save dovecot's good name, I recall a lot of damage was done to that in the circles I'm in when 2.0 was released with patches nearly every few days and weeks, I know a few ISP's and businesses that went back to courier or Wu's because major bugs were getting in often, though it has been a lot better since 2.1 series, until this release that is :) I second this and offer my services for two, three different system configs from Dovecot's plain old simple config with MAILDIR to slightly more complicated configurations with proxying/LDAP/dsync/mySQL etc based on virtualization with KVM. I also propose that upon employing above strategy that Timo should come up with a release cycles (long term, short term) with announced targets. Patches should be released as patches strictly as needed, not releases, and should be announced on a low traffic list like he is already doing with releases. OR something along these lines. I know these are growing pains but essential. Email systems are CRITICAL for most of us. Andreas
Re: [Dovecot] 2.2.9
On 23-11-2013 19:56, Luuk wrote: On 23-11-2013 18:44, Andreas Kasenides wrote: On 23-11-2013 3:47, Noel Butler wrote: These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most I second this and offer my services for two, three different system What is the difference between a 'RC' and a new version? One should TEST this new version ALWAYS before using it in production (it does not matter if there was a 'RC' before it...) 2 cents ;) RC means exactly what is says Release Client :) NOT a release. So if you get bitten by it then do not come here complaining. Most software go through several RCs before issuing a normal release. Most administrators have test systems that can test RCs for basic functionality and report here of any problems to be fixed. Some though jump into a new release when one is available. An RC should at least show the red flag raised. Andreas
Re: [Dovecot] Getting back into Dovecot 2.2.5
On 02-09-2013 07:04, Kai Hendry wrote: On Mon, Sep 02, 2013 at 02:37:04AM +0300, Andreas Kasenides wrote: IIUC Postfix places by default mail in /var/mail/%u as an mbox. sg:/etc/postfix$ sudo postconf | grep mail_spool mail_spool_directory = /var/mail I think the solution from looking around is to use dovecot as an lda. http://wiki2.dovecot.org/LDA/Postfix Yes! Sorry for not saying that. While the Dovecot LDA is preferred (it will also do on-line indexing), it is not the only option. Postfix will also deliver into a maildir (both the local and virtual delivery agents) if you just add a / at the end of the delivery directory! I prefer the Dovecot LDA of course with necessary Postfix configs for it. By the way I consider mbox format to be a relic of the mail systems. But it may be what you are looking for a really small setup to get away from Gmail. Straight forward and simple. Andreas Solr is not the only option. The way I understand this is that this will heavily depend on your client, if it will make use of the Dovecot indexing, thefore speeding up operations. I use Thunderbird most of the time and I have no indexing on Dovecot. Searching is quite good. I use mutt Apple Mail IOS. http://www.flickr.com/photos/hendry/9652360692/ Thanks for replying! I will update https://github.com/webconverger/sg.webconverger.com with my setup in future.
Re: [Dovecot] Getting back into Dovecot 2.2.5
On 31-08-2013 13:07, Kai Hendry wrote:
However I found /usr/share/doc/dovecot/example-config/conf.d/ a little
scary, since I like to have my configs as minimalistic as possible,
e.g.
I suggest you forget all the options and concentrate on the ones you
intend to use.
Dovecot has defaults for most options that make sense.
I was kinda hoping for a Maildir, but this doesn't work:
mail_location = maildir:~/Maildir:LAYOUT=fs:INBOX=/var/mail/%u
I have
mail_location
=maildir:/Mail/%d/%n:INDEX=/Mail/dovecot/indexes/%d/%n:CONTROL=/Mail/dovecot/control/%d/%n
and it works nicely. So why don't you try
mail_location=maildir:/var/spool/mail/%u
first and see how it works before moving the INBOX separately from other
boxes
I do realise /var/mail/%u is a mbox, but I was wondering if there could
be some clever conversion.
/var/mail/%u is a directory. It only becomes an mbox if you say so in
Dovecot.
I was surprised something like INBOX=/var/mail/%u wasn't the default
btw. Also surprised dovecot seems to choke on single line syntax like
`passdb { driver = pam }` :-)
Actually Dovecot will even auto-discover your mail in
/var/mail/username among other locations (~Maildir,
/var/mail/username, ~/mail, ~/Mail) if you leave mail_location empty.
Verified for passdb { driver = pam }.
But this works:
userdb {
driver = sql; args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
}
This does not:
userdb { driver = sql; args =
/usr/local/etc/dovecot/dovecot-sql.conf.ext }
Not sure of the exact syntax though.
Next thing I'm confused about is the `namespace inbox {` stuff. Is it
really needed? I was expecting Dovecot to create the folders once I
defined them, but mutt couldn't see them until I created them myself.
Never touched namespace myself, did not have to. The default works
nicely.
Sorry never used mutt before.
The mail server is just for myself and a few colleagues. We will
probably use mutt as our MUA and Apple Mail on IOS when we are out
about. I next plan to integrate dspam, and work out how to sort mails
into folders like I previously effectively had with Gmail's labels.
I was confused to which mechanism I should be using to sort mail into
folders with rules. Sieve? Back to Procmail? Pigeonhole? I'm looking to
avoid complexity here.
Sieve. Which is actually a two part thing: 1) the sieve filter language
which
you can enable on the dovecot server and manually edit each folder OR 2)
the Sieve
server which enables you to edit the filters from the clients (with the
right plug-in/extension on the client.
On the topic of search, can I get away with not running a Solr server?
Since I shudder at the thought of running Tomcat.
http://wiki2.dovecot.org/Plugins/FTS
Solr is not the only option. The way I understand this is that this will
heavily depend on your client, if it will make use of the Dovecot
indexing, thefore speeding up operations. I use Thunderbird most of the
time and I have no indexing on Dovecot. Searching is quite good.
Hope this helps.
Andreas
Re: [Dovecot] Load Balancing and HA
On 31-05-2013 12:57, Patrick Westenberg wrote: Romer Ventura schrieb: Scenario1: This should allow any to lose any of the servers and clients still have access to their emails (although I am not sure how the indexes would react to this and sudden disconnection) - 2 Dovecot Proxy servers, using a virtual IP to where the clients will connect to from the WAN and LAN - 2 Dovecot+Postfix servers with local cache Your proxy won't reconnect a user to backend B if the backend A fails. But doesn't that depend on how the vitual IP is managed ie what kind of system is behind it? For example a simple heartbeat setup would correct this at the cost of one machine sitting idle. Other setups using load balancers can correct this. There is a better solution using the Director service of Dovecot where users are assigned to one of several bacend machines and disconnected when idle. Even, there is a script that monitors the health of the Director backends and adjusts accordingly (which I haven't personally tried yet). See http://wiki2.dovecot.org/Director http://www.dovecot.org/list/dovecot/2010-August/051946.html
Re: [Dovecot] Load Balancing and HA
I am actually going through the first stages of implementing your Scenario1. There is small difference: there will also be 2*Postfix relays also on the Dovecot Proxies. This allows placing them in a DMZ such that the real Dovecot/Postfix servers are placed away from the WAN. After much arguing and thinking I decided to go with this option as the most basic and possibly the simplest way to achieve MY goals: 1. fault tolerance of the entire system such that a failure will not impact mail delivery/access. 2. distribute users on at least two Dovecot servers to help when peak times arrive. 3. Ability to expand easily if demand rises 4. No use of custom hardware 5. Both internal (LAN) users and away from office (WAN) users will see the same setup to ease configuration (mostly done by users these days) I should say that other more complicated setups like full blown clusters and distributed file systems have been rejected due to their complexity (and the fact we do not have experience with them). Our user base is around 3-4K of heavy users. Andreas On 29-05-2013 00:23, Romer Ventura wrote: Hello, I've been thinking about the best way to achieve load balancing and making my mail servers highly available. So far I believe I have 2 scenarios: Scenario1: This should allow any to lose any of the servers and clients still have access to their emails (although I am not sure how the indexes would react to this and sudden disconnection) - 2 Dovecot Proxy servers, using a virtual IP to where the clients will connect to from the WAN and LAN - 2 Dovecot+Postfix servers with local cache - 2 NFS servers and synced with dsync (mirror, 1 server writes to its own NFS and changes synced to the other via dsync) Scenario2: Pretty much as above on the back end. However, with this there is no way to load balance users. - 2 Dovecot+Postfix server with local cache - 2 NFS servers synced with dsync - Make use of DNS MX record priority to provide access to secondary email server Anyone care to comment? Thanks.
Re: [Dovecot] Virtual Servers, or different authentication setups.
Look at Running Multiple Invocations of Dovecot at http://wiki2.dovecot.org/RunningDovecot Andreas On 23-05-2013 03:30, Joshua Gardner wrote: I want to know if there is any virtual server functionality in Dovecot? I would like to have two separate configurations, that access the same email, running in the same Dovecot instance. They would bind different ports and/or IPs, but have different authentication settings. In particular, one would use a PLAIN password scheme, the other SSHA. How would I go about setting up these virtual servers? Or, would I have to run separate instances of Dovecot? If I do have to run separate instances, how do I keep them from interfering with eachother? -Josh
Re: [Dovecot] v2.2.0 released
On 12-04-2013 20:33, Timo Sirainen wrote: http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz.sig Everything now seems to be stable and working in v2.2, so I can finally move onto developing great new interesting features for v2.3. :) [snip] Running happily here. Thank you and congrats. Andreas
Re: [Dovecot] thunderbird detach attachment
This looks to work on my 17.0.5 Thunderbird on CentOS 6.4 (I guess Dovecot is not involved but running on 2.2.beta1). It does detach the file, places it in the chosen folder, removes the option to detach or delete from the message menu but (nice indeed) remembers where you put the attachment and can still show it if you click on it or save it again if you want to!! But how do we know its been detached if it still shows in Thunderbird? Looking into the actual message file I see the following at the end: --020104000205010901050407 Content-Type: application/vnd.oasis.opendocument.text; name==?UTF-8?B?MjAxMzA0MDQtzpPOoy5vZHQ=?= Content-Disposition: attachment; filename=20130404-??.odt X-Mozilla-External-Attachment-URL: file:///LocalData/tmp/20130404-%CE%93%CE%A3.odt X-Mozilla-Altered: AttachmentDetached; date=Wed Apr 10 12:51:00 2013 You deleted an attachment from this message. The original MIME headers for the attachment were: Content-Type: application/vnd.oasis.opendocument.text; name==?UTF-8?B?MjAxMzA0MDQtzpPOoy5vZHQ=?= Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename*=UTF-8''%32%30%31%33%30%34%30%34%2D%CE%93%CE%A3%2E%6F%64%74 --020104000205010901050407-- Nice!! Andreas On 10/04/13 11:50, mourik jan heupink wrote: Hi all, Thunderbird has an option to detach attachments from (for example) sent items. I've tried it, and it does not work, and also in the dovecot logs I don't see anything interesting meanwhile. Before looking deeper into this: Does anyone here know if this option is known to work, or not? We're running dovecot 2.1.7 on debian wheezy. Removing unwanted attachments is a nice way to keep mail archives smaller... Thanks, MJ -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701
[Dovecot] Dovecot 2.2.beta1 errors
From the command
doveadm log errors
we get
Jan 31 15:41:12 imap(): Panic: Buffer full (8221 8192, pool
none) Jan 31 15:41:12 imap(): Error: Raw backtrace:
/usr/local/lib/dovecot/libdovecot.so.0(+0x5b83a) [0x7ffbaa3a783a] -
/usr/local/lib/dovecot/libdovecot.so.0(+0x5b886) [0x7ffbaa3a7886] -
/usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7ffbaa36adaf] -
/usr/local/lib/dovecot/libdovecot.so.0(+0x57cfc) [0x7ffbaa3a3cfc] -
/usr/local/lib/dovecot/libdovecot.so.0(+0x5134f) [0x7ffbaa39d34f] -
/usr/local/lib/dovecot/libdovecot.so.0(+0x4a02d) [0x7ffbaa39602d] -
/usr/local/lib/dovecot/libdovecot.so.0(+0x4a0ca) [0x7ffbaa3960ca] -
/usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0x64)
[0x7ffbaa3af924] - /usr/local/lib/dovecot/libdovecot.so.0(+0x6844c)
[0x7ffbaa3b444c] - /usr/local/lib/dovecot/libdovecot.so.0(+0x685f1)
[0x7ffbaa3b45f1] - /usr/local/lib/dovecot/libdovecot.so.0(+0x686d0)
[0x7ffbaa3b46d0] -
/usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0x64)
[0x7ffbaa3af924] -
/usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x52)
[0x7ffbaa3afc32] -
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0x987ba)
[0x7ffbaa69a7ba] -
/usr/local/lib/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x135)
[0x7ffbaa69ac45] -
/usr/local/lib/dovecot/libdovecot-storage.so.0(mail_get_binary_stream+0x61)
[0x7ffbaa674481] -
/usr/local/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0xb0)
[0x7ffbaa6cf980] - dovecot/imap() [0x418619] - dovecot/imap()
[0x4166e2] - dovecot/imap(imap_fetch_more+0x31) [0x416911] -
dovecot/imap(cmd_fetch+0x41f) [0x40cd9f] -
dovecot/imap(command_exec+0x3d) [0x414e2d] - dovecot/imap()
[0x41402e] - dovecot/imap(client_handle_input+0x11d) [0x41431d] -
dovecot/imap(client_input+0x6f) [0x41468f] -
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
[0x7ffbaa3b5fe6] -
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7)
[0x7ffbaa3b7027] -
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
[0x7ffbaa3b5f88] Jan 31 15:41:12 imap(): Fatal: master:
service(imap): child 2236 killed with signal 6 (core dumped)
where is the offending user name. The error repeats at random intervals, I
guess related to the activity.
Since we are using Horde 5 on the front end we get the following errors from it:
Jan 31 15:02:59 thalia HORDE: [imp] Mail server closed the connection
unexpectedly. [pid 6402 on line 390 of
/sys-data/WebData/horde/imp/lib/Imap.php] Jan 31 15:02:59 thalia
HORDE: [imp] Operation failed due to a lack of a secure connection.
[pid 6402 on line 390 of /sys-data/WebData/horde/imp/lib/Imap.php]
Jan 31 15:02:59 thalia HORDE: [imp] Operation failed due to a lack of
a secure connection. [pid 6402 on line 390 of
/sys-data/WebData/horde/imp/lib/Imap.php] Jan 31 15:02:59 thalia
HORDE: [imp] Operation failed due to a lack of a secure connection.
[pid 6402 on line 94 of
/sys-data/WebData/horde/imp/lib/Imap/Exception.php]
We believe these are related to the above Dovecot error since they happens
together.
Is this a Dovecot problem?
Config attached.
Thanx
--
Andreas Kasenides
Senior IT Officer
Dept. of Computer Science,
University of Cyprus
Tel: 22892714, Fax: 22892701
# 2.2.beta1: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-279.19.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) nfs
auth_anonymous_username = anonymous
auth_cache_negative_ttl = 1 hours
auth_cache_size = 0
auth_cache_ttl = 1 hours
auth_debug = no
auth_debug_passwords = no
auth_default_realm =
auth_failure_delay = 2 secs
auth_first_valid_uid = 500
auth_gssapi_hostname =
auth_krb5_keytab =
auth_last_valid_uid = 0
auth_master_user_separator =
auth_mechanisms = plain
auth_proxy_self =
auth_realms =
auth_socket_path = auth-userdb
auth_ssl_require_client_cert = no
auth_ssl_username_from_cert = no
auth_use_winbind = no
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
auth_username_format = %Lu
auth_username_translation =
auth_verbose = yes
auth_verbose_passwords = no
auth_winbind_helper_path = /usr/bin/ntlm_auth
auth_worker_max_count = 30
base_dir = /usr/local/var/run/dovecot
config_cache_size = 1 M
debug_log_path =
default_client_limit = 1000
default_idle_kill = 1 mins
default_internal_user = dovecot
default_login_user = dovenull
default_process_limit = 100
default_vsz_limit = 256 M
deliver_log_format = msgid=%m: %$
dict_db_config =
director_doveadm_port = 0
director_mail_servers =
director_servers =
director_user_expire = 15 mins
director_username_hash = %Lu
disable_plaintext_auth = no
dotlock_use_excl = yes
doveadm_allowed_commands =
doveadm_password =
doveadm_proxy_port = 0
doveadm_socket_path = doveadm-server
doveadm_worker_count = 0
dsync_alt_char = _
dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u
-l%{lock_timeout} -n%{namespace}
first_valid_gid = 1
first_valid_uid = 200
hostname =
imap_capability =
imap_client_workarounds =
imap_id_log
[Dovecot] Filesystem quotas
I could not determine if when using filesystem quotas (http://wiki2.dovecot.org/Quota/FS) Dovecot will use the reported quota and limits without the need of configuring them via quota_rules. Is this possible somehow? Such a feature would determine the quota limits automatically from the filesystem quotas thereby allowing to make use of them in quota warnings. Dovecot already knows the quota settings and limits. Here is evidence from the logs Nov 21 19:24:22 iolaos dovecot: imap(user): Debug: box=/Mail/ank mount=/newmail match=yes Nov 21 19:24:22 iolaos dovecot: imap(user): Debug: quota-fs: host=..ucy.xx.cy, path=/mail, uid=211, bytes Nov 21 19:24:22 iolaos dovecot: imap(user): Debug: quota-fs: uid=211, value=2779115520, limit=8388608000 I am using (testing) version 2.2alpha1. Thankx. -- Andreas Kasenides Senior IT Officer University of Cyprus, Dept. of Computer Science Tel: 22892714, Fax: 22892701
