[Dovecot] cluster with dsync mirror
I have an idea for running a pair of redundant dovecot mail servers that may be odd but it might work. I'm interested in any thoughts on the topic. Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other dedicated NFS server in a simple environment with a limited number of users. Everything else about the systems could be identical. Both could receive mail using Postfix with dovecot LDA. Thank you. Bryan
Re: [Dovecot] cluster with dsync mirror
On 16.8.2010, at 7.33, Bryan Vyhmeister wrote: Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other dedicated NFS server in a simple environment with a limited number of users. Everything else about the systems could be identical. Both could receive mail using Postfix with dovecot LDA. Thank you. Were you thinking about master/slave or multi-master setup? Multi-master might work ok with director, as long as dsyncing is done often enough. If you don't have many users, then maybe dsyncing once a minute is enough. A more optimal version would go something like: - create a dsyncing server process - create a Dovecot plugin (using notify plugin, similar to mail_log) that notifies dsyncing process every time some user's mailbox changes - based on that information, dsyncing process either runs dsync or delays it a bit. like maybe flag changes and expunges would be delayed a bit, but new mails would be immediately synced - run a full dsync for every user once in a while anyway, just in case some notifications were missed - implement a QRESYNC-like syncing for dsync to improve performance and reduce network traffic
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 15/08/2010 22:49, Marc Perkel wrote: On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named dovenull to work. Please create user dovenull and try again. No. The first sentence of your proposed message is FALSE. On 15/08/2010 17:10, Timo Sirainen wrote: - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. Dovecot does NOT need a user named dovenull to work. The second sentence is predicated on the first and as such also falls down. Dovecot needs a user named by the default_login_user setting in order to work. Whilst this defaults to dovenull, there is nothing to stop you setting it to something else (e.g. flibble). The point is that the answer is more of a commentary and the right solution depends on the situation. Rather than try to squeeze solution summaries into every error message, I would suggest having a link (perhaps into the Dovecot wiki) in the error message, e.g. Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see http://wiki2.dovecot.org/Errors/NoDefaultLoginUser) (Note that the above URL is hypothetical.) Then have a commentary and suggested solutions in the wiki. Alternatively, the link could rooted at a notional documentation root like: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see documentation Errors/NoDefaultLoginUser) so that users could refer to a local copy of the documentation rather than encouraging load on the Dovecot wiki server(s). Bill
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-15 12:03 PM, Marc Perkel m...@perkel.com wrote: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary. It would be a lot smoother (and this probably applies to all other software you use) if you would spend at least 5 SECONDS doing a little research before wasting everyone's (especially Timo's) time with questions that you can easily answer yourself: http://www.lmgtfy.com/?q=dovenull For dovecot stuff, I've found that simply adding the word 'wiki' after the other search term will almost always provide the link to the wiki page describing whatever it is: http://www.lmgtfy.com/?q=dovenull+wiki Yes, this is a pet peeve of mine... -- Best regards, Charles
Re: [Dovecot] Forcing users to change passwords
Marc Perkel wrote: Suppose I have users with a default password like change-my-password and I want to detect users who haven't changed their password and alert (nag) them about changing it. How would I do that? How is this a dovecot question? The answer depends on what you use for your passdb backend, and whether or not whatever you use to manage your users supports such a thing - if not, you'd have to script it. -- Best regards, Charles
[Dovecot] pigeonhole
Hi, I'm trying to compile the last mercurial release of dovecot-pigeonhole 2.0 and get this error: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a ./debug/.libs/libsieve_ext_debug.a /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-storage/.libs/libdovecot-storage.so /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-lda/.libs/libdovecot-lda.so /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,--rpath -Wl,/usr/lib/dovecot ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_stringlist_get_length' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_stringlist_read_all' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_single_stringlist_create_cstr' collect2: ld returned 1 exit status make[4]: *** [sievec] Error 1 any idea? thanks Xavier
Re: [Dovecot] pigeonhole
hi, what os/distro? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] cluster with dsync mirror
I used a setup like this, to sync mail between 3 different datacenters, in a multimaster setup. For this I used unison, running every 28seconds. And it worked well for two years, before I changed to a better approach. Older versions of dovecot didn't like the moves very much (pre 1.0), but when I upgraded it to 1.0.x versions, it seemed to be happy. I discontinued it before 1.1 was out. Quoting Bryan Vyhmeister dove...@bsdjournal.net: I have an idea for running a pair of redundant dovecot mail servers that may be odd but it might work. I'm interested in any thoughts on the topic. Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other dedicated NFS server in a simple environment with a limited number of users. Everything else about the systems could be identical. Both could receive mail using Postfix with dovecot LDA. Thank you. Bryan
[Dovecot] Split number of imap-login and pop3-login processes
Hi All, Is there a way to define the number for imap-login processes and pop3-login processes separately? My mail server is getting more IMAP clients and much less POP3 clients these days and it continues to run out of authentication processes. I have been increasing login_max_processes_count the last couple of days and I noticed that it's split between IMAP and POP3. All 129 imap-login processes are tied up while there are only 3 of the 129 pop3-login processes in use. Any help would be greatly appreciated! Thanx!! Mischa mail:~ # dovecot --version 1.2.12 mail:~ # dovecot -n # 1.2.12: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.1-RELEASE amd64 zfs base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s listen(default): *,[::]:143 listen(imap): *,[::]:143 listen(pop3): *,[::]:110 ssl_listen(default): *,[::]:993 ssl_listen(imap): *,[::]:993 ssl_listen(pop3): *,[::]:995 ssl_ca_file: /usr/local/etc/certs/gd_bundle.crt ssl_cert_file: /usr/local/etc/certs/cert.crt ssl_key_file: /usr/local/etc/certs/key.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_processes_count: 256 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(pop3): 6 verbose_proctitle: yes first_valid_uid: 144 first_valid_gid: 144 mail_access_groups: postfix mail_location: maildir:/var/mail/virtual/%u/ mbox_write_locks: fcntl mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: sql args: /usr/local/etc/dovecot-mysql.conf userdb: driver: sql args: /usr/local/etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix @mail:~ # grep -v '^ *\(#.*\)\?$' dovecot-mysql.conf driver = mysql default_pass_scheme = CRYPT connect = host=* dbname=postfix user=postfix password= password_query = SELECT password FROM mailbox WHERE username='%u' AND active='1' user_query = SELECT maildir, 144 AS uid, 144 AS gid FROM mailbox WHERE username='%u' AND active='1'
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On Aug 15, 2010, at 9:04 PM, Jim wrote: On Aug 15, 2010, at 4:01 PM, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. Or in the case of OS X, dscl... Documenting this is good, but perhaps the configure script could check if the user exists, and instruct the user to create this manually before going any further? And some may be building binaries packages for distribution so forcing user creation on a build server would be extra unhelpful work. On thing I was considering was if patching to allow configure to set -- default_login_user=_dovenull and --default_internal_user=_dovecot. I don't think this is a big deal but it would allow package builders to build packages with default names that match their distributions. BTW, things are fine the way they are. The fewer options that meet the needs the better. Regards, Bradley Giesbrecht
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/16/2010 2:45 AM, William Blunn wrote: On 15/08/2010 22:49, Marc Perkel wrote: On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named dovenull to work. Please create user dovenull and try again. No. The first sentence of your proposed message is FALSE. On 15/08/2010 17:10, Timo Sirainen wrote: - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. Dovecot does NOT need a user named dovenull to work. The second sentence is predicated on the first and as such also falls down. Dovecot needs a user named by the default_login_user setting in order to work. Whilst this defaults to dovenull, there is nothing to stop you setting it to something else (e.g. flibble). The point is that the answer is more of a commentary and the right solution depends on the situation. Rather than try to squeeze solution summaries into every error message, I would suggest having a link (perhaps into the Dovecot wiki) in the error message, e.g. Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see http://wiki2.dovecot.org/Errors/NoDefaultLoginUser) (Note that the above URL is hypothetical.) Then have a commentary and suggested solutions in the wiki. Alternatively, the link could rooted at a notional documentation root like: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see documentation Errors/NoDefaultLoginUser) so that users could refer to a local copy of the documentation rather than encouraging load on the Dovecot wiki server(s). Bill Maybe dovecot could use the nobody user if dovenull doesn't exist?
Re: [Dovecot] Split number of imap-login and pop3-login processes
On Mon, 2010-08-16 at 15:31 +0200, Mischa Peters wrote:
Hi All,
Is there a way to define the number for imap-login processes and pop3-login
processes separately?
My mail server is getting more IMAP clients and much less POP3 clients these
days and it continues to run out of authentication processes.
I have been increasing login_max_processes_count the last couple of days and
I noticed that it's split between IMAP and POP3.
All 129 imap-login processes are tied up while there are only 3 of the 129
pop3-login processes in use.
You can probably put the settings inside protocol pop3 {} and protocol
imap {}. But maybe you should switch to high-performance mode:
http://wiki.dovecot.org/LoginProcess
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On Mon, 2010-08-16 at 07:16 -0700, Marc Perkel wrote: Maybe dovecot could use the nobody user if dovenull doesn't exist? The entire point of dovenull user is that it's not used by anything else. The only things I'm going to change here is to make the error message somewhat better for v2.0.1 and add a note about this user to NEWS file / release announcement.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-16 07:16:46 -0700, Marc Perkel wrote: Maybe dovecot could use the nobody user if dovenull doesn't exist? you could just read the warning message, create the user and stop worrying? and no ... it shouldnt fallback to nobody. a broken set up is a broken setup and needs to be fixed. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
[Dovecot] Standards of expectations for software installs
On 8/16/2010 4:11 AM, Charles Marcus wrote: On 2010-08-15 12:03 PM, Marc Perkelm...@perkel.com wrote: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary. It would be a lot smoother (and this probably applies to all other software you use) if you would spend at least 5 SECONDS doing a little research before wasting everyone's (especially Timo's) time with questions that you can easily answer yourself: http://www.lmgtfy.com/?q=dovenull For dovecot stuff, I've found that simply adding the word 'wiki' after the other search term will almost always provide the link to the wiki page describing whatever it is: http://www.lmgtfy.com/?q=dovenull+wiki Yes, this is a pet peeve of mine... Timo's software standards, and mine, are higher than the average open source project. When an install id done right then you don't have to go to the wiki for anything. You run it and it just works. That's why people pay for Windows and Macs and more people use it than Linux because it just works. You start an upgrade anf click NEXT AGREE NEXT NEXT NEXT FINISH and everything just works. That's the way Linux should be. So - even though something might be a minor detail, when you get the minor details right then you get software the it just works which is in my opinion the highest thing one can say about a program. And it's who dovecot is so popular.
Re: [Dovecot] cluster with dsync mirror
What do you use now? On 8/16/2010 6:27 AM, Patrick Domack wrote: I used a setup like this, to sync mail between 3 different datacenters, in a multimaster setup. For this I used unison, running every 28seconds. And it worked well for two years, before I changed to a better approach. Older versions of dovecot didn't like the moves very much (pre 1.0), but when I upgraded it to 1.0.x versions, it seemed to be happy. I discontinued it before 1.1 was out. Quoting Bryan Vyhmeister dove...@bsdjournal.net: I have an idea for running a pair of redundant dovecot mail servers that may be odd but it might work. I'm interested in any thoughts on the topic. Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other dedicated NFS server in a simple environment with a limited number of users. Everything else about the systems could be identical. Both could receive mail using Postfix with dovecot LDA. Thank you. Bryan
Re: [Dovecot] dovecot: Killed with signal 15 (by pid=14267
On Sun, 2010-08-15 at 17:56 -0400, Jerrale G wrote: I don't know if dovecot 2.0 will have this already or not but, when dovecot is stopped or started, it would be nice to have the PID reported in the log for various uses. v2.0 does have it: master: Warning: Killed with signal 15 (by pid=3293 uid=0 code=kill)
Re: [Dovecot] Standards of expectations for software installs
On Mon, Aug 16, 2010 at 07:23:50AM -0700, Marc Perkel wrote: Timo's software standards, and mine, are higher than the average open source project. When an install id done right then you don't have to go to the wiki for anything. You run it and it just works. That's why people pay for Windows and Macs and more people use it than Linux because it just works. You start an upgrade anf click NEXT AGREE NEXT NEXT NEXT FINISH and everything just works. That's the way Linux should be. So - even though something might be a minor detail, when you get the minor details right then you get software the it just works which is in my opinion the highest thing one can say about a program. And it's who dovecot is so popular. So are you saying a server software which brings a lot of new features to cope with complex environments shall tweak itself by magic, as any good software should upgrade without user intervention? You wouldn't even need documentation as the new features would be self-explanatory? *NO FRIGGIN' WAY*
Re: [Dovecot] Standards of expectations for software installs
Em 16/08/2010 11:23, Marc Perkel escreveu: Timo's software standards, and mine, are higher than the average open source project. When an install id done right then you don't have to go to the wiki for anything. You run it and it just works. That's why people pay for Windows and Macs and more people use it than Linux because it just works. You start an upgrade anf click NEXT AGREE NEXT NEXT NEXT FINISH and everything just works. That's the way Linux should be. So - even though something might be a minor detail, when you get the minor details right then you get software the it just works which is in my opinion the highest thing one can say about a program. And it's who dovecot is so popular. hey Marc, you're not alone !!! As well as you, i also expect software updates to be always perfect and magic so i dont have to have a clue of what i'm real doing, as softwares will take care of all the inteligence that i should have. but, i think different from you, i understand and accept that there's no magic. upgrades on complex environment MUST be planned, new version features should be understood and in almost all cases, including some M$ updates of complex software/ environment, lots of pre-upgrade and post-upgrades actions should be taken. i would love to just click yes yes and everything works as magic but, unfortunelly, i accept that wont happen in the real (and most all the times complex) scenarios we have. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertru...@solutti.com.br My SPAMTRAP, do not email it
[Dovecot] v2.0.0 released
http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0 before upgrading from v1.x. Although there is automatic config conversion, it can't handle everything, so reserve some extra time for upgrading. If you find an upgrade problem that isn't listed on the wiki page, please add it there or email Dovecot mailing list about it. Pigeonhole Sieve and ManageSieve support can now be installed without patching Dovecot. Unfortunately there isn't a Pigeonhole release yet for v2.0, but its Mercurial code tree should be quite stable. See http://wiki2.dovecot.org/Pigeonhole There are no changes since v2.0.rc6. The largest changes since v1.2 are: * Dovecot uses two system users for internal purposes now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. * Global ACLs are now looked up using namespace prefixes. For example if you previously had INBOX. namespace prefix and a global ACL for INBOX.Sent, it's now looked up from INBOX.Sent file instead of Sent as before. * Maildir: File permissions are no longer based on dovecot-shared file, but the mailbox directory. + Redesigned master process. It's now more modular and there is less code running as root. + Configuration supports now per-local/remote ip/network settings. + dsync utility does a two-way mailbox synchronization. + LMTP server and proxying. + Added mdbox (multi-dbox) mail storage backend. + doveadm utility can be used to do all kinds of administration functions. Old dovecotpw and *view utilities now exist in its subcommands. + imap and pop3 processes can now handle multiple connections. + IMAP: COMPRESS=DEFLATE is supported by imap_zlib plugin + director service helps NFS installations to redirect users always to same server to avoid corruption
Re: [Dovecot] Standards of expectations for software installs
On Mon, 2010-08-16 at 11:42 -0300, Leonardo Rodrigues wrote: hey Marc, you're not alone !!! As well as you, i also expect software updates to be always perfect and magic so i dont have to have a clue of what i'm real doing, as softwares will take care of all the inteligence that i should have. Yes, that's what I expect distribution packages to do. But upstream packages can't do that. There are just way too many different ways people use them.
Re: [Dovecot] v2.0.0 released
On 16/08/2010 15:49, Timo Sirainen wrote: As promised last Friday, here's the v2.0.0 release finally. Brilliant work Timo! Bill
Re: [Dovecot] v2.0.0 released
On 8/16/10 10:49 AM, Timo Sirainen wrote: As promised last Friday, here's the v2.0.0 release finally. Congratulations, Timo! -Dave -- Dave McGuire Port Charlotte, FL
Re: [Dovecot] v2.0.0 released
On Mon, 2010-08-16 at 15:49 +0100, Timo Sirainen wrote: http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig Well, it didn't take long for someone to find the first bug: http://hg.dovecot.org/dovecot-2.0/rev/2156583b00e2 configure: v2.0.0 is no longer UNSTABLE development branch. --- a/configure.in Mon Aug 16 15:35:16 2010 +0100 +++ b/configure.in Mon Aug 16 16:07:01 2010 +0100 @@ -2739,6 +2739,3 @@ if test $not_sql_drivers != ; then echo :$not_sql_drivers fi - -echo -echo NOTE: This is the UNSTABLE development branch of Dovecot v2.0.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-16 07:16:46 -0700, Marc Perkel wrote: Maybe dovecot could use the nobody user if dovenull doesn't exist? you could just read the warning message, create the user and stop worrying? and no ... it shouldnt fallback to nobody. a broken set up is a broken setup and needs to be fixed. Wow. Well said. -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] v2.0.0 released
On Mon, Aug 16, 2010 at 5:49 PM, Timo Sirainen t...@iki.fi wrote: http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0 before upgrading from v1.x. Although there is automatic config conversion, it can't handle everything, so reserve some extra time for upgrading. If you find an upgrade problem that isn't listed on the wiki page, please add it there or email Dovecot mailing list about it. Pigeonhole Sieve and ManageSieve support can now be installed without patching Dovecot. Unfortunately there isn't a Pigeonhole release yet for v2.0, but its Mercurial code tree should be quite stable. See http://wiki2.dovecot.org/Pigeonhole There are no changes since v2.0.rc6. The largest changes since v1.2 are: * Dovecot uses two system users for internal purposes now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. * Global ACLs are now looked up using namespace prefixes. For example if you previously had INBOX. namespace prefix and a global ACL for INBOX.Sent, it's now looked up from INBOX.Sent file instead of Sent as before. * Maildir: File permissions are no longer based on dovecot-shared file, but the mailbox directory. + Redesigned master process. It's now more modular and there is less code running as root. + Configuration supports now per-local/remote ip/network settings. + dsync utility does a two-way mailbox synchronization. + LMTP server and proxying. + Added mdbox (multi-dbox) mail storage backend. + doveadm utility can be used to do all kinds of administration functions. Old dovecotpw and *view utilities now exist in its subcommands. + imap and pop3 processes can now handle multiple connections. + IMAP: COMPRESS=DEFLATE is supported by imap_zlib plugin + director service helps NFS installations to redirect users always to same server to avoid corruption It is yet another major milestone for Dovecot! Congratulations Timo. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube
Re: [Dovecot] v2.0.0 released
Congratulations Timo!:) SUSE packages are already building and can be found at [1] in a few minutes. though the package doesnt try to migrate the config yet. so users have to do that on their own. :) darix [1] http://download.opensuse.org/repositories/server:/mail/ dovecot20 dovecot20-backend-mysql dovecot20-backend-pgsql dovecot20-backend-sqlite dovecot20-fts-solr dovecot20-devel -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] v2.0.0 released
SUSE packages are already building and can be found at [1] in a few minutes. forgot to mention: the package ships with latest pigeonhole aswell. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] v2.0.0 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen said the following on 16/08/10 16:49: As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Congratulations Timo and thank you!!! Ciao, luigi - -- / +--[Luigi Rosa]-- \ Biggest Black Hole ever Found in Nearby Galaxy. EVERYBODY PAN..IC --fark.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxpX2YACgkQ3kWu7Tfl6ZSHBACfYqBFlpHe0Cc4pRMx+b2OZZL9 P0QAoIwCuMkwS6w4SQpusyWwJWUQY+SN =k0GJ -END PGP SIGNATURE-
Re: [Dovecot] v2.0.0 released
http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. cool .. .however .. should I see this message at the end of the configure stage : . . . passdbs : static passwd passwd-file shadow pam checkpassword ldap sql : -bsdauth -sia -vpopmail userdbs : static prefetch passwd passwd-file checkpassword ldap sql : -vpopmail -nss SQL drivers : mysql sqlite : -pgsql NOTE: This is the UNSTABLE development branch of Dovecot v2.0. ^ That won't go well with the Solaris crowd. Just FYI. -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] v2.0.0 released
On 08/16/2010 06:46 PM Dennis Clarke wrote: … NOTE: This is the UNSTABLE development branch of Dovecot v2.0. ^ See: http://dovecot.org/list/dovecot/2010-August/051736.html Regards, Pascal -- The trapper recommends today: cafefeed.1022...@localdomain.org
Re: [Dovecot] Standards of expectations for software installs
On 2010-08-16 10:23 AM, Marc Perkel m...@perkel.com wrote: That's why people pay for Windows and Macs and more people use it than Linux because it just works. You start an upgrade anf click NEXT AGREE NEXT NEXT NEXT FINISH and everything just works. That's the way Linux should be. You're not serious?? I can't count how many times an update of Windows or a windows program didn't go as expected or planned, but this has absolutely nothing to do with the fact that your question was posted to this list because you were too lazy to even make a half-hearted attempt to figure out the problem yourself. So - even though something might be a minor detail, when you get the minor details right then you get software the it just works which is in my opinion the highest thing one can say about a program. And it's who dovecot is so popular. Irrelevant. Sure, I'd love for it to just work like magic every time, but reality is very different, and if you are going to be too lazy to try to fix something yourself, you should expect the kind of responses you have gotten. -- Best regards, Charles
Re: [Dovecot] Subdomain Migration
On 8/16/2010 3:44 AM, ramesh wrote: Hi All, I would like have suggestion for changing subdomain (belongs to ISP) to own domain, the scenario as below. Presently we have subdomain from ISP ( @xxx.isp.net) email id : ram...@xxx.isp.net ISP charges huge amount,thou others ISP charges less. so we have planned to migrate to our own registered domain and terminate existing ISP. Now my requirement is email coming to ram...@xxx.isp.net (Mail server connected to present ISP) should forward to ram...@mydomain.co.in (Mail server connected to new ISP) Please send me suggestion to follow or URL's explain briefly. Thanks. Regards, Ramesh They have to send mail to y...@yournewdomain.com unless you plan on keeping your isp's subdomain Jerrale G. SC Senior Admin
Re: [Dovecot] pigeonhole
On 8/16/2010 8:22 AM, Marcus Rueckert wrote: hi, what os/distro? darix make sure you are using dovecot-2.0-rc6 Jerrale G. SC Senior Admin
Re: [Dovecot] v2.0.0 released
On 08/16/2010 06:46 PM Dennis Clarke wrote: ⦠NOTE: This is the UNSTABLE development branch of Dovecot v2.0. ^ See: http://dovecot.org/list/dovecot/2010-August/051736.html wow ... I was hoping I was the first :-\ -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] Standards of expectations for software installs
On 8/16/2010 7:37 AM, Thomas Leuxner wrote: On Mon, Aug 16, 2010 at 07:23:50AM -0700, Marc Perkel wrote: Timo's software standards, and mine, are higher than the average open source project. When an install id done right then you don't have to go to the wiki for anything. You run it and it just works. That's why people pay for Windows and Macs and more people use it than Linux because it just works. You start an upgrade anf click NEXT AGREE NEXT NEXT NEXT FINISH and everything just works. That's the way Linux should be. So - even though something might be a minor detail, when you get the minor details right then you get software the it just works which is in my opinion the highest thing one can say about a program. And it's who dovecot is so popular. So are you saying a server software which brings a lot of new features to cope with complex environments shall tweak itself by magic, as any good software should upgrade without user intervention? You wouldn't even need documentation as the new features would be self-explanatory? *NO FRIGGIN' WAY* No - I'm saying that an upgrade that does exactly the same thing as the earlier version should just work without having to research cryptic error messages you get after the new software fails to load. What I'm saying is that Linux should be as easy as Windows.
Re: [Dovecot] Subdomain Migration
On 16/08/2010 17:58, Jerrale G wrote: On 8/16/2010 3:44 AM, ramesh wrote: Hi All, I would like have suggestion for changing subdomain (belongs to ISP) to own domain, the scenario as below. Presently we have subdomain from ISP ( @xxx.isp.net) email id : ram...@xxx.isp.net ISP charges huge amount,thou others ISP charges less. so we have planned to migrate to our own registered domain and terminate existing ISP. Now my requirement is email coming to ram...@xxx.isp.net (Mail server connected to present ISP) should forward to ram...@mydomain.co.in (Mail server connected to new ISP) Please send me suggestion to follow or URL's explain briefly. Thanks. Regards, Ramesh They have to send mail to y...@yournewdomain.com unless you plan on keeping your isp's subdomain Is it just me or can anyone else NOT see the original message from ramesh? I've looked in my inbox, and viewed the mailing list archive both over the web and via the IMAP interface, and I can't see the original message. Bill
Re: [Dovecot] Standards of expectations for software installs
Am 16.08.2010 um 19:22 schrieb Marc Perkel: No - I'm saying that an upgrade that does exactly the same thing as the earlier version should just work without having to research cryptic error messages you get after the new software fails to load. What I'm saying is that Linux should be as easy as Windows. And that's the point. It does not do things like the earlier version as privileges have been removed from processes. All of that has been noted on the list during development and in the documentation. There was even a poll around the actual name to be used.
Re: [Dovecot] Master User Features I'd like to see
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Hi Timo,
I just tried the 2.0 official release and these variables return an
empty string.
Re: [Dovecot] pigeonhole
On 2010-08-16 13:02:37 -0400, Jerrale G wrote: make sure you are using dovecot-2.0-rc6 you mean the final 2.0.0 right?:p darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Master User Features I'd like to see
On Mon, 2010-08-16 at 10:49 -0700, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Hi Timo,
I just tried the 2.0 official release and these variables return an
empty string.
Works with me:
passdb {
driver = sql
master = yes
args = /usr/local/etc/dovecot/dovecot-sql-master.conf
pass = yes
}
password_query = \
SELECT user, password FROM masters \
WHERE user = '%u' and '%d' = '%{login_domain}'
auth: Debug: sql(mas...@dovecot.org,::1,master): query: SELECT user, password
FROM masters WHERE user = 'mas...@dovecot.org' and 'dovecot.org' =
'dovecot.org'
auth: Debug: sql(mas...@dovecot.org,::1,master): query: SELECT user, password
FROM masters WHERE user = 'mas...@dovecot.org' and 'dovecot.org' =
'foobar.org'
Re: [Dovecot] Master User Features I'd like to see
You can use checkpassword:
http://wiki.dovecot.org/AuthDatabase/CheckPassword
Works fine for me for master user authentication.
Emerson Pinter
On 15-08-2010 18:46, Marc Perkel wrote:
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not others. I think I could do what
I want with the right kinds of variable passing that doesn't yet
exist. Let me see if I can explain clearly.
From the example in the wiki:
auth_master_user_separator = *
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
userdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
Login looks like this:
# telnet localhost 143
* OK Dovecot ready.
1 login loginuser*masteruser masterpass
1 OK Logged in.
I'm assuming that the masteruser and masterpass is passed to the
master passdb and when doing so the variable %u is the master user. I
assume that %n and %d also represent the name and domain part of the
master user.
What I need is to also be able to have variables for the loginuser
passed to the master user query. Something like %lu, %ln, and %ld
perhaps. That way with MySQL tricks I might be able to see if the
master user is master for that particular login user. That way I can
give domain owners or owners of multiple domains the ability to manage
the email accounts within their scope of permission.
Re: [Dovecot] Master User Features I'd like to see
On 8/16/2010 11:04 AM, Timo Sirainen wrote:
On Mon, 2010-08-16 at 10:49 -0700, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Hi Timo,
I just tried the 2.0 official release and these variables return an
empty string.
Works with me:
passdb {
driver = sql
master = yes
args = /usr/local/etc/dovecot/dovecot-sql-master.conf
pass = yes
}
password_query = \
SELECT user, password FROM masters \
WHERE user = '%u' and '%d' = '%{login_domain}'
auth: Debug: sql(mas...@dovecot.org,::1,master): query: SELECT user, password FROM
masters WHERE user = 'mas...@dovecot.org' and 'dovecot.org' = 'dovecot.org'
auth: Debug: sql(mas...@dovecot.org,::1,master): query: SELECT user, password FROM
masters WHERE user = 'mas...@dovecot.org' and 'dovecot.org' = 'foobar.org'
Odd - wonder what I'm doing wrong then? My result:
Aug 16 10:44:43 auth: Debug: sql(supp...@junkemailfilter.com,127.0.0.1):
query: SELECT user_name, domain_name, password FROM users WHERE
user_name = 'support' AND domain_name = 'junkemailfilter.com' AND
owns_domain='1' AND 'junkemailfilter.com'=''
My query:
password_query = SELECT user_name, domain_name, password FROM users
WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1' AND
'%d'='%{login_domain}'
Re: [Dovecot] Master User Features I'd like to see
On Mon, 2010-08-16 at 11:17 -0700, Marc Perkel wrote:
Odd - wonder what I'm doing wrong then? My result:
Aug 16 10:44:43 auth: Debug: sql(supp...@junkemailfilter.com,127.0.0.1):
query: SELECT user_name, domain_name, password FROM users WHERE
user_name = 'support' AND domain_name = 'junkemailfilter.com' AND
owns_domain='1' AND 'junkemailfilter.com'=''
This is from passdb { master = yes } passdb? How are you logging in? I
used auth_master_user_separator=* and:
a login t...@dovecot.org*master@dovecot.org pass
b login t...@foobar.org*master@dovecot.org pass
Re: [Dovecot] Master User Features I'd like to see
On 8/16/2010 11:26 AM, Timo Sirainen wrote:
On Mon, 2010-08-16 at 11:17 -0700, Marc Perkel wrote:
Odd - wonder what I'm doing wrong then? My result:
Aug 16 10:44:43 auth: Debug: sql(supp...@junkemailfilter.com,127.0.0.1):
query: SELECT user_name, domain_name, password FROM users WHERE
user_name = 'support' AND domain_name = 'junkemailfilter.com' AND
owns_domain='1' AND 'junkemailfilter.com'=''
This is from passdb { master = yes } passdb? How are you logging in? I
used auth_master_user_separator=* and:
a login t...@dovecot.org*master@dovecot.org pass
b login t...@foobar.org*master@dovecot.org pass
auth_master_user_separator = *
passdb {
driver = sql
args = /etc/dovecot/dovecot-domain-owner-sql.conf
master = yes
pass = yes
}
I'm logging in les...@junkemailfilter.com*support@junkemailfilter.com
But the %{login_domain} evaluates to an empty string as you can see from
the results of the debug.
Aug 16 10:44:43 auth: Debug: sql(supp...@junkemailfilter.com,127.0.0.1):
query: SELECT user_name, domain_name, password FROM users WHERE
user_name = 'support' AND domain_name = 'junkemailfilter.com' AND
owns_domain='1' AND*'junkemailfilter.com'=''*
[Dovecot] Imap, flags. Dsync
Does dsync mirror follow up flags ? I am testing here, and if i flag an msg as follow up, dsync does not do anything. It suppouse to be like that ? Thanks! []'sf.rique
Re: [Dovecot] Master User Features I'd like to see
On 16.8.2010, at 22.01, Marc Perkel wrote:
But the %{login_domain} evaluates to an empty string as you can see from the
results of the debug.
What about %{login_user} or %{username}?
Re: [Dovecot] Imap, flags. Dsync
On 16.8.2010, at 22.11, Henrique Fernandes wrote: Does dsync mirror follow up flags ? There's no such standard flag in IMAP. Are you sure your client even sends it to IMAP server? It would show up as a keyword. You can check it by talking IMAP directly: telnet localhost 143 a login user pass b select INBOX c fetch 1:* flags Is it there? What is it called?
Re: [Dovecot] Master User Features I'd like to see
On 8/16/2010 2:24 PM, Timo Sirainen wrote:
On 16.8.2010, at 22.01, Marc Perkel wrote:
But the %{login_domain} evaluates to an empty string as you can see from the
results of the debug.
What about %{login_user} or %{username}?
Interestingly %{login_user} doesn't work either returning an empty
string. However %{username} works.
Re: [Dovecot] Master User Features I'd like to see
On 8/16/2010 2:24 PM, Timo Sirainen wrote:
On 16.8.2010, at 22.01, Marc Perkel wrote:
But the %{login_domain} evaluates to an empty string as you can see from the
results of the debug.
What about %{login_user} or %{username}?
Actually - spoke too soon. %{username} returned the wrong value. It
returned that name part of the master user.
Re: [Dovecot] Imap, flags. Dsync
Sorry, my bad, i guess this flags does not exits. It is an client feature, but is also in my webmail client. So i thought it might be an imap flags! Thanks! []'sf.rique On Mon, Aug 16, 2010 at 6:25 PM, Timo Sirainen t...@iki.fi wrote: On 16.8.2010, at 22.11, Henrique Fernandes wrote: Does dsync mirror follow up flags ? There's no such standard flag in IMAP. Are you sure your client even sends it to IMAP server? It would show up as a keyword. You can check it by talking IMAP directly: telnet localhost 143 a login user pass b select INBOX c fetch 1:* flags Is it there? What is it called?
Re: [Dovecot] Standards of expectations for software installs
On Mon, 2010-08-16 at 10:22 -0700, Marc Perkel wrote: a No - I'm saying that an upgrade that does exactly the same thing as the earlier version should just work without having to research cryptic error messages you get after the new software fails to load. What I'm saying is that Linux should be as easy as Windows. A new MAJOR version release should ring bells that you need to read for any possible problems. This is true for other widely popular software, ie: apache. I will admit, certain distro vendors such as debian/RH/Fedora/Ubuntu , do, do much software a dis-service by their hacks and non standard file locations, because people with problems come to us for support expecting us to fix a mess created by someone else. That I know annoys a lot of people trying to convert to linux from windows and you're right, then they say bugger it and go back to windows. but.. everyone wants to be special I suppose :)
Re: [Dovecot] v2.0.0 released
Well , configure looked good and the summary seemed fine :
Install prefix . : /opt/csw
File offsets ... : 64bit
I/O polling : poll
I/O notifys : none
SSL : yes (OpenSSL)
GSSAPI . : yes
passdbs : static passwd passwd-file shadow pam checkpassword ldap
sql
: -bsdauth -sia -vpopmail
userdbs : static prefetch passwd passwd-file checkpassword ldap sql
: -vpopmail -nss
SQL drivers : pgsql mysql sqlite
Everything was going swimmingly and then poof :
libtool: compile: /opt/studio/SOS11/SUNWspro/bin/cc -DHAVE_CONFIG_H -I.
-I../.. -I../../src/lib -I../../src/lib-test -I../../src/lib-charset
-I../../src/lib-mail
-I/opt/csw/include:/opt/csw/mysql51/include/mysql:/opt/csw/postgresql83/include
-I/opt/csw/include -xstrconst -xildoff -xarch=v8 -xnolibmil -Xa
-xcode=pic32 -xregs=no%appl -xlibmieee -g -xs -I/opt/csw/include
-I/opt/csw/mysql51/include/mysql -I/opt/csw/postgresql83/include
-D_TS_ERRNO -DSOLARIS2=8 -D_LARGEFILE64_SOURCE -I/opt/csw/include -c
imap-id.c -KPIC -DPIC -o .libs/imap-id.o
libtool: compile: /opt/studio/SOS11/SUNWspro/bin/cc -DHAVE_CONFIG_H -I.
-I../.. -I../../src/lib -I../../src/lib-test -I../../src/lib-charset
-I../../src/lib-mail
-I/opt/csw/include:/opt/csw/mysql51/include/mysql:/opt/csw/postgresql83/include
-I/opt/csw/include -xstrconst -xildoff -xarch=v8 -xnolibmil -Xa
-xcode=pic32 -xregs=no%appl -xlibmieee -g -xs -I/opt/csw/include
-I/opt/csw/mysql51/include/mysql -I/opt/csw/postgresql83/include
-D_TS_ERRNO -DSOLARIS2=8 -D_LARGEFILE64_SOURCE -I/opt/csw/include -c
imap-id.c -o imap-id.o /dev/null 21
source='imap-match.c' object='imap-match.lo' libtool=yes \
DEPDIR=.deps depmode=none /opt/csw/bin/bash ../../depcomp \
/opt/csw/bin/bash ../../libtool --tag=CC --mode=compile
/opt/studio/SOS11/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I../..
-I../../src/lib -I../../src/lib-test -I../../src/lib-charset
-I../../src/lib-mail
-I/opt/csw/include:/opt/csw/mysql51/include/mysql:/opt/csw/postgresql83/include
-I/opt/csw/include -xstrconst -xildoff -xarch=v8 -xnolibmil -Xa
-xcode=pic32 -xregs=no%appl -xlibmieee -g -xs -I/opt/csw/include
-I/opt/csw/mysql51/include/mysql -I/opt/csw/postgresql83/include
-D_TS_ERRNO -DSOLARIS2=8 -D_LARGEFILE64_SOURCE -I/opt/csw/include-c -o
imap-match.lo imap-match.c
libtool: compile: /opt/studio/SOS11/SUNWspro/bin/cc -DHAVE_CONFIG_H -I.
-I../.. -I../../src/lib -I../../src/lib-test -I../../src/lib-charset
-I../../src/lib-mail
-I/opt/csw/include:/opt/csw/mysql51/include/mysql:/opt/csw/postgresql83/include
-I/opt/csw/include -xstrconst -xildoff -xarch=v8 -xnolibmil -Xa
-xcode=pic32 -xregs=no%appl -xlibmieee -g -xs -I/opt/csw/include
-I/opt/csw/mysql51/include/mysql -I/opt/csw/postgresql83/include
-D_TS_ERRNO -DSOLARIS2=8 -D_LARGEFILE64_SOURCE -I/opt/csw/include -c
imap-match.c -KPIC -DPIC -o .libs/imap-match.o
imap-match.c, line 199: identifier redeclared: imap_match_dup
current : function(pointer to struct pool {pointer to const struct
pool_vfuncs {..} v, unsigned int alloconly_pool :1, unsigned int
datastack_pool :1}, pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}) returning pointer to struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}
previous: function(pointer to struct pool {pointer to const struct
pool_vfuncs {..} v, unsigned int alloconly_pool :1, unsigned int
datastack_pool :1}, pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}) returning pointer to struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data} : imap-match.h, line 33
imap-match.c, line 214: identifier redeclared: imap_match_globs_equal
current : function(pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}, pointer to const struct imap_match_glob {pointer
to struct pool {..} pool, pointer to struct imap_match_pattern
{..} patterns, char sep, array[-1] of char patterns_data})
returning _Bool
previous: function(pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}, pointer to const struct imap_match_glob {pointer
to struct pool {..} pool, pointer to struct imap_match_pattern
{..} patterns, char sep, array[-1] of char patterns_data})
returning _Bool : imap-match.h, line 36
cc: acomp failed for imap-match.c
gmake[3]: *** [imap-match.lo] Error 1
gmake[3]: Leaving directory
Re: [Dovecot] v2.0.0 released
On 16.8.2010, at 23.25, Dennis Clarke wrote: imap-match.c, line 199: identifier redeclared: imap_match_dup I think someone reported this problem earlier .. but I'm not sure. Anyway I've no idea why it would complain about this. So that stops me while I figure out what the issue is with imap-match.h and/or imap-match.c in the Solaris world while using Sun Studio 11. I heard it compiles ok with Sun Studio 12.1.
Re: [Dovecot] cluster with dsync mirror
On Mon, Aug 16, 2010 at 5:15 AM, Timo Sirainen t...@iki.fi wrote: On 16.8.2010, at 7.33, Bryan Vyhmeister wrote: Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other dedicated NFS server in a simple environment with a limited number of users. Everything else about the systems could be identical. Both could receive mail using Postfix with dovecot LDA. Thank you. Were you thinking about master/slave or multi-master setup? Multi-master might work ok with director, as long as dsyncing is done often enough. I was thinking about multi-master. I didn't think about director but that would solve the issue of not connecting to the same server each time and would cause dsync to not have to happen quite as often. If you don't have many users, then maybe dsyncing once a minute is enough. A more optimal version would go something like: - create a dsyncing server process - create a Dovecot plugin (using notify plugin, similar to mail_log) that notifies dsyncing process every time some user's mailbox changes - based on that information, dsyncing process either runs dsync or delays it a bit. like maybe flag changes and expunges would be delayed a bit, but new mails would be immediately synced - run a full dsync for every user once in a while anyway, just in case some notifications were missed - implement a QRESYNC-like syncing for dsync to improve performance and reduce network traffic I'll have to investigate this further. This sounds like an even better solution. Thank you! Bryan
Re: [Dovecot] v2.0.0 released
On 8/16/10 6:25 PM, Dennis Clarke wrote:
pool_vfuncs {..} v, unsigned int alloconly_pool :1, unsigned int
datastack_pool :1}, pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}) returning pointer to struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}
previous: function(pointer to struct pool {pointer to const struct
pool_vfuncs {..} v, unsigned int alloconly_pool :1, unsigned int
datastack_pool :1}, pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}) returning pointer to struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data} : imap-match.h, line 33
imap-match.c, line 214: identifier redeclared: imap_match_globs_equal
current : function(pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}, pointer to const struct imap_match_glob {pointer
to struct pool {..} pool, pointer to struct imap_match_pattern
{..} patterns, char sep, array[-1] of char patterns_data})
returning _Bool
previous: function(pointer to const struct imap_match_glob
{pointer to struct pool {..} pool, pointer to struct
imap_match_pattern {..} patterns, char sep, array[-1] of char
patterns_data}, pointer to const struct imap_match_glob {pointer
to struct pool {..} pool, pointer to struct imap_match_pattern
{..} patterns, char sep, array[-1] of char patterns_data})
returning _Bool : imap-match.h, line 36
cc: acomp failed for imap-match.c
gmake[3]: *** [imap-match.lo] Error 1
gmake[3]: Leaving directory
`/export/medusa/dclarke/build/dovecot/sparc/dovecot-2.0.0-sparcv8-001/src/lib-imap'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/export/medusa/dclarke/build/dovecot/sparc/dovecot-2.0.0-sparcv8-001/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/export/medusa/dclarke/build/dovecot/sparc/dovecot-2.0.0-sparcv8-001'
gmake: *** [all] Error 2
[mimas]
So that stops me while I figure out what the issue is with imap-match.h
and/or imap-match.c in the Solaris world while using Sun Studio 11.
Works fine here with the 12.1 compiler. Solaris 10 on UltraSPARC,
current patches, on both the OS and the compilers. My CFLAGS:
-fast -xtarget=ultra3 -m32 -xarch=sparcvis2
-Dave
--
Dave McGuire
Port Charlotte, FL
Re: [Dovecot] v2.0.0 released
On 16.8.2010, at 23.25, Dennis Clarke wrote: imap-match.c, line 199: identifier redeclared: imap_match_dup I think someone reported this problem earlier .. but I'm not sure. Anyway I've no idea why it would complain about this. So that stops me while I figure out what the issue is with imap-match.h and/or imap-match.c in the Solaris world while using Sun Studio 11. I heard it compiles ok with Sun Studio 12.1. I will try GCC and let you know what I see : [mimas] gcc --version gcc (Blastwave.org Inc. Mon Aug 9 07:10:45 GMT 2010) 4.5.1 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. No surprise that GCC works fine : [mimas] ls -lap ./src/master/.libs/dovecot -rwxr-xr-x 1 dclarke csw86388 Aug 17 00:09 ./src/master/.libs/dovecot [mimas] file ./src/master/.libs/dovecot ./src/master/.libs/dovecot: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, not stripped [mimas] elfdump -d ./src/master/.libs/dovecot Dynamic Section: .dynamic index tag value [0] NEEDED 0xe21 libdovecot.so.0 [1] NEEDED 0xe31 libintl.so.8 [2] NEEDED 0xe3e libdl.so.1 [3] NEEDED 0xe49 libnsl.so.1 [4] NEEDED 0xdf6 libsocket.so.1 [5] NEEDED 0xe55 libiconv.so.2 [6] NEEDED 0xe0e libc.so.1 [7] NEEDED 0xe63 librt.so.1 [8] INIT 0x1b71c [9] FINI 0x1b738 etc etc ... I did see a few odd messages fly by like this : *** Warning: Linking the shared library lib30_imap_zlib_plugin.la against the loadable module *** lib20_zlib_plugin.so is not portable! Not too sure what is up with that but I'll look into it. -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] v2.0.0 released
On 17.8.2010, at 1.28, Dennis Clarke wrote: *** Warning: Linking the shared library lib30_imap_zlib_plugin.la against the loadable module *** lib20_zlib_plugin.so is not portable! Not too sure what is up with that but I'll look into it. That's normal. It doesn't need to be portable.
Re: [Dovecot] v2.0.0 released
So that stops me while I figure out what the issue is with imap-match.h and/or imap-match.c in the Solaris world while using Sun Studio 11. Works fine here with the 12.1 compiler. Solaris 10 on UltraSPARC, current patches, on both the OS and the compilers. My CFLAGS: -fast -xtarget=ultra3 -m32 -xarch=sparcvis2 The is ye ol'production Solaris 8 and thus Sun Studio 11 is needed. Problem solved simply by using GCC 4.5.1 from Blastwave ( of course ). Question for you: why would you use -m32 with an -xarch=sparcvis2 ? Why not go for greatest possible portability and range of processors with something like this : CFLAGS=-m32 -Qy -Xa -xbuiltin=%none -xnolibmil -xnolibmopt -xcode=pic32 -xildoff -xregs=no%appl -xs -xstrconst -D_TS_ERRNO If you feel like some optimization then chuck in -xO3 and -xdepend however I'd test the resultant bins from a basic compile first. Just my 0.02 -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] v2.0.0 released
On 8/16/10 8:38 PM, Dennis Clarke wrote: Works fine here with the 12.1 compiler. Solaris 10 on UltraSPARC, current patches, on both the OS and the compilers. My CFLAGS: -fast -xtarget=ultra3 -m32 -xarch=sparcvis2 The is ye ol'production Solaris 8 and thus Sun Studio 11 is needed. Oh. Eeeew. :) Problem solved simply by using GCC 4.5.1 from Blastwave ( of course ). I wonder how GCCFSS would do. Will it even run under Solaris 8? Question for you: why would you use -m32 with an -xarch=sparcvis2 ? Why not go for greatest possible portability and range of processors with something like this : CFLAGS=-m32 -Qy -Xa -xbuiltin=%none -xnolibmil -xnolibmopt -xcode=pic32 -xildoff -xregs=no%appl -xs -xstrconst -D_TS_ERRNO Because I don't intend to run it on a range of processors. =) If you feel like some optimization then chuck in -xO3 and -xdepend however I'd test the resultant bins from a basic compile first. Just my 0.02 Fair enough, and I appreciate your advice. My goal in this case is to generate the fastest binaries possible on the machine it's being built on, which is identical to the machine it's going to be run on. There's zero need for portable binaries in this particular installation. -Dave -- Dave McGuire Port Charlotte, FL
Re: [Dovecot] v2.0.0 released
On 17.8.2010, at 1.28, Dennis Clarke wrote: *** Warning: Linking the shared library lib30_imap_zlib_plugin.la against the loadable module *** lib20_zlib_plugin.so is not portable! Not too sure what is up with that but I'll look into it. That's normal. It doesn't need to be portable. In that case ... awesome :-) I'll let you know when I get packages into testing QC and then for release. However I am going to rename the package to dovecot2 in order to separate it from dovecot 1.x installs. My idea there is to allow the user to continue with the dovecot 1.x line in the event of patch updates and further releases from that tree ( like dovecot 1.2.13 ) while also maintaining the ver 2.x family. However I don't think I'll support multiple instances of dovecot ( regardless of version ) in the same Solaris zone. If the user wants that then they can do all the uid/pid hackery themselves. -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] v2.0.0 released
On 8/16/10 8:38 PM, Dennis Clarke wrote: Works fine here with the 12.1 compiler. Solaris 10 on UltraSPARC, current patches, on both the OS and the compilers. My CFLAGS: -fast -xtarget=ultra3 -m32 -xarch=sparcvis2 The is ye ol'production Solaris 8 and thus Sun Studio 11 is needed. Oh. Eeeew. :) Hey, there are banks and telco places all over that are running it and they *refuse* to upgrade. I know of government sites that are still on old E450's because they have not died yet. No kidding. Some of that old Sun gear just WILL NOT bloody die. The way to justify the capital expenditure on a new Sun Sparc server is to spill a coffee on/in it. 8-P Problem solved simply by using GCC 4.5.1 from Blastwave ( of course ). I wonder how GCCFSS would do. Will it even run under Solaris 8? Why not ? It is a rock solid kernel and you can build it and see :-) Question for you: why would you use -m32 with an -xarch=sparcvis2 ? Why not go for greatest possible portability and range of processors with something like this : CFLAGS=-m32 -Qy -Xa -xbuiltin=%none -xnolibmil -xnolibmopt -xcode=pic32 -xildoff -xregs=no%appl -xs -xstrconst -D_TS_ERRNO Because I don't intend to run it on a range of processors. =) ah ... I am in a different world. If you feel like some optimization then chuck in -xO3 and -xdepend however I'd test the resultant bins from a basic compile first. Just my 0.02 Fair enough, and I appreciate your advice. My goal in this case is to generate the fastest binaries possible on the machine it's being built on, which is identical to the machine it's going to be run on. There's zero need for portable binaries in this particular installation. In that case run fpversion : fpversion A SPARC-based CPU is available. Kernel says CPU's clock rate is 900.0 MHz. Kernel says main memory's clock rate is 150.0 MHz. Sun-4 floating-point controller version 0 found. An UltraSPARC chip is available. Use -xtarget=ultra3cu -xcache=64/32/4:8192/512/2 code-generation option. See those compiler options ? Use them. Also put in -xO3 and -xdepend and then the compile will take a lot longer but you will be happy you waited. Sun Studio compilers can really rock if you know how to push them. -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] v2.0.0 released
I wonder how GCCFSS would do. Will it even run under Solaris 8? # which gcc /opt/csw/gcc4/bin/gcc # gcc --version gcc (Blastwave.org Inc. Mon Aug 9 07:10:45 GMT 2010) 4.5.1 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # uname -a SunOS mimas 5.8 Generic_127721-03 sun4u sparc SUNW,UltraAX-i2 # psrinfo -v Status of virtual processor 0 as of: 08/17/10 00:58:04 on-line since 07/06/10 12:03:37. The sparcv9 processor operates at 500 MHz, and has a sparcv9 floating point processor. Is that baseline Sparc enough for you ? ;-) -- Dennis Clarke dcla...@opensolaris.ca - Email related to the open source Solaris dcla...@blastwave.org - Email related to open source for Solaris
Re: [Dovecot] pigeonhole
Xavier Pons wrote: Hi, I'm trying to compile the last mercurial release of dovecot-pigeonhole 2.0 and get this error: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a ./debug/.libs/libsieve_ext_debug.a /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-storage/.libs/libdovecot-storage.so /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-lda/.libs/libdovecot-lda.so /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,--rpath -Wl,/usr/lib/dovecot ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_stringlist_get_length' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_stringlist_read_all' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_single_stringlist_create_cstr' collect2: ld returned 1 exit status make[4]: *** [sievec] Error 1 any idea? Did you rerun ./autogen.sh and ./configure ? Regards, Stephan.
[Dovecot] 2.0 and vpopmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Does 2.0 require a specific version of vpopmail? I'm getting this on my build attempt : /usr/src/redhat/BUILD/dovecot-2.0.0/src/auth/passdb-vpopmail.c:185: undefined reference to `vauth_load_module' Yes, it's an RPM, that's how I roll. I'm not finding vauth_load_module anywhere on my system.. I'm running vpopmail 5.4.30 which is, I believe the latest stable release.. Thanks, - --- Jason 'XenoPhage' Frisvold xenoph...@godshell.com - --- Any sufficiently advanced magic is indistinguishable from technology. - - Niven's Inverse of Clarke's Third Law -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkxp/6YACgkQ8CjzPZyTUTT0tACgi5WLR2IcGvhmvmIGlmZpeg1P tUQAn2zx6HuIR3QHIGt/aYCP7nRNBvJ7 =yYrj -END PGP SIGNATURE-
