Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99
On Aug 17, 2009, at 2:01 AM, Phillip Macey wrote: On 17/08/2009 3:36 PM, Timo Sirainen wrote: On Aug 17, 2009, at 1:31 AM, Phillip Macey wrote: Also you could check if you have any mails with CRs in them: perl -ne 's/\r$//;print if /\r/' * This didn't print anything - I was sort of expecting it to at least print something (especially since your update seemed to fix the crash...) Hmm. That is strange. What about in the destination mailbox where you copied the messages? I'm now wondering if there's still a data corruption bug. Ok, I don't know what I did wrong the first time around - this time it printed a whole heap of stuff for both the source and destination mailboxes. Sorry about the false alarm. Great, thanks. Time for v1.2.4 tomorrow then I guess. :)
Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99
On 17/08/2009 3:36 PM, Timo Sirainen wrote: On Aug 17, 2009, at 1:31 AM, Phillip Macey wrote: Also you could check if you have any mails with CRs in them: perl -ne 's/\r$//;print if /\r/' * This didn't print anything - I was sort of expecting it to at least print something (especially since your update seemed to fix the crash...) Hmm. That is strange. What about in the destination mailbox where you copied the messages? I'm now wondering if there's still a data corruption bug. Ok, I don't know what I did wrong the first time around - this time it printed a whole heap of stuff for both the source and destination mailboxes. Sorry about the false alarm. -- Thanks, Phill Macey (CiSRA IT Services)
Re: [Dovecot] GSSAPI Authentication in v1.2.1
On 15/08/2009 2:08 AM, Timo Sirainen wrote: On Fri, 2009-08-14 at 16:46 +1000, Phillip Macey wrote: I also needed to change src/master/master-login-interface.h #define MASTER_LOGIN_MAX_DATA_SIZE (8192*2) Will these changes be included in the next release or is this something that we will need to maintain for ourselves? -- Thanks, Phill Macey (CiSRA IT Services)
[Dovecot] install sieve without any dovecot sources
Hi all I have dovecot 1.1.16 (dovecot-1.1.16-0_94.el5 x86-64) installed on a Red Hat Enterprise v.5. I am already using Dovecot's deliver for virtual users local delivery and need to install the cmusieve plugin for the filtering capabilities. I don't have any sources, since I installed Dovecot from a binary package. Is there any way to install the cmusieve plugin? Thanks in advance Dimitrios Karapiperis
Re: [Dovecot] More Migration Questions
Hello, OK, I've found the problem... If i migrate all email from one server to another, preserving msg UIDs, then the msg UIDs are ignored by the POP3 client if it has it's hostname/IP changed in order to point to the new server. So... mail client points to 192.168.1.1. mail is all downloaded but left on server. migration to new server occurs, preserving msg UIDs. mail client IP adjusted to point to 192.168.1.2. All mail downloaded again, duplicates now exist. The way to get around this is to either set your mail client to hostname in the first place, and then make the change in DNS, or to remove all msgs from the server before migration, so the msg UIDs are irrelevant. It's also annoying that you cannot fix the problem before migration because if i tell people to change from the old mail server's IP to the old mail server's hostname, then again - the mail client will download all their mail again and duplicate it! Anyway... i'm glad i've found the problem, even if it does make the migration a little annoying! :-) Regards, Richard. Richard Hobbs wrote: Hello, We've also tried setting the size of the msgs to be the same, just in case that made a difference. Here is some output from our old mail server during the test: == uidl +OK uidl command accepted. 1 a==!(3N!D'!87D! 2 _fg!!)%!!Ic!!-@'! 3 Yh]!!Zlk!QfA!Lj1!! . list +OK 3 visible messages (42852 octets) 1 28359 2 2918 3 11575 . == Here are the same commands against the new server during our test: == uidl +OK 1 a==!(3N!D'!87D! 2 _fg!!)%!!Ic!!-@'! 3 Yh]!!Zlk!QfA!Lj1!! . list +OK 3 messages: 1 28359 2 2918 3 11575 . == As far as i can tell, they are identical. If i setup the old server in my mail client, it downloads all 3 msgs. If i then mark them all as read and change the hostname of the mail server to point to the new server, it then downloads the same 3 msgs so i end up with duplicates in my inbox, despite them having the same UIDLs! The only difference i can see is that the old mail server has the X-UIDL header towards the end of the headers, and the new server puts the X-UIDL header right at the top above all other headers. Does anyone know what on earth is going on here? Thanks again! Richard. Richard Hobbs wrote: Hello, Thanks again - your reply will help greatly. I have a rather more annoying problem at the moment, best described by my conversation in the dovecot IRC channel... i've telnetted to 110 on old server the uidl command shows 3 UIDLs uidl command also shows 3 UIDLs from new server... trouble is, despite seeing the same 3 UIDLs on the old mail server *and* the new mail server, when issuing the uidl command through port 110 after logging in, i just setup the account in my mail client against the old server, downloaded 3 msgs, changed the config for the new server, and it downloaded the same msgs again! ok, on the old server, in the received email, towards the bottom of the headers, i see this: X-UIDL: a==!(3N!D'!87D! on the new server, in the duplicate received email, right at the top, before any other headers, i see this: X-UIDL: a==!(3N!D'!87D! whaton earth is going on here... both now have the same X-UIDL, but are being downloaded separately! So... does anyone have any ideas? Thanks again! Richard. Timo Sirainen wrote: On Fri, 2009-08-14 at 15:39 +, Richard Hobbs wrote: That's better actually, you don't then have to add those ~/mail/ compabilitity namespaces. Well, i haven't added any ~/mail/ compatibility namespaces knowingly... i guess they might be in the default config (my version has been built for debian), but how would i check? Basically, the problem is that some users have their folders in ~/mail/ and others have their folders in ~/. This is kind of what I meant by the compatibility namespaces. If some users have ~/mail/ and whatelse, you'll probably want to add such namespaces to Dovecot. See http://wiki.dovecot.org/Namespaces#Backwards_Compatibility:_UW-IMAP I want to convert both, and also and up with a standard location in the maildir setup. I guess the best way to do this is to just copy everyone's mailboxes from ~/ into ~/mail/ before i run the conversion, right? That should work, as long as you can find all the mailboxes (or are all files in ~/ mailboxes?) As long as people don't object to their folders potentially changing places within their IMAP client, everything will be OK, right? With the compatibility namespace it should be pretty transparent to clients. Also you'll probably want to set separator=/ in all the namespaces. -- Richard Hobbs (IT Specialist) Toshiba Research Europe Ltd. - Cambridge
Re: [Dovecot] BUG: mbox_snarf causes message duplication when two IMAP connections are open
On Fri, Aug 7, 2009 at 20:32, Timo Sirainent...@iki.fi wrote: On Fri, 2009-08-07 at 15:31 -0400, Timo Sirainen wrote: Does the attached patch help? Although it makes performance slightly worse.. Probably not noticeably. If it works, I'll just commit it to the next release. Sorry, I messed up the patch. Should have used hg diff, not hg export tip :) Attached a working one this time. Hello, The patch applied fine to the latest release and fixed the issue for us, thanks again :)
Re: [Dovecot] Quota question.
On Sun, 2009-08-16 at 09:09 -0400, Tom Diehl wrote: Actually it should be possible to just delete the row and let Dovecot recalculate the quota on next update, but currently this isn't working. I've a half-finished patch to make it work, but it's a pretty big change. v1.2.4 anyway hopefully has it. Looks like it doesn't make it for v1.2.4. v1.2.5 then. I am looking fwd to this fix. I have several thousand mailboxes to migrate in the next few weeks. Not something that is really practical to do by hand. Maybe I could script something using expect and a modified db query so that I do not have to know all of the users passwds. Do all your users use the same UID? There's an easier way to do this then: echo 1 getquotaroot inbox | USER=username dovecot --exec-mail imap signature.asc Description: This is a digitally signed message part
[Dovecot] v1.2.4 released
http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root directory. + imap/pop3 proxy: If proxy destination is known to be down, fail connections to it immediately. + imap/pop3 proxy: Added proxy_timeout passdb extra field to specify proxy's connect timeout. - Fixed a crash in index file handling. - Fixed a crash in saving messages where message contained a CR character that wasn't followed by LF (and the CR happened to be the last character in an internal buffer). - v1.2.3 crashed when listing shared namespace prefix. - listescape plugin: Several fixes. - autocreate plugin: Fixed autosubscribing to mailboxes in subscriptions=no namespaces. signature.asc Description: This is a digitally signed message part
[Dovecot] Dovecot and LDAP-Quotas
Hi all, I have configured Dovecot as a POP/IMAP-Server in front of a Postfix-Server. Every thing works without one thing: LDAP-quotas The main-quota-rule works: quota_rule: *:storage=8M Only the LDAP-quota won't be used by Dovecot: user_attrs = msRADIUSFramedIPAddress=quota_rule=*:storage=%$k I have to use the special LDAP-field msRADIUSFramedIPAddress because my W2003 domain controller don't have a regular quota field. This LDAP-field is the only free integer LDAP-field. Could anyone please give me a hint? Greetings Paul #dovecot -n # 1.2.3: /etc/dovecot.conf # OS: Linux 2.6.18-128.4.1.el5 x86_64 CentOS release 5.3 (Final) ext3 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps listen(default): 123.456.789.71 listen(imap): 123.456.789.71 listen(pop3): 123.456.789.72 ssl_listen(default): ssl_listen(imap): ssl_listen(pop3): 123.456.789.72:995 ssl_ca_file: /etc/pki/dovecot/certs/pop_core_uk/trustcenter_intermediate.crt ssl_cert_file: /etc/pki/dovecot/certs/pop_core_uk/server.crt ssl_key_file: /etc/pki/dovecot/private/pop_core_uk/server.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: maildir:/home/vmail/%Lu/Maildir/ mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: debug: yes postmaster_address: postms...@core.uk hostname: smtp.core.uk mail_plugins: quota quota_full_tempfail: yes log_path: /var/log/dovecot-deliver.log log_timestamp: %b %d %H:%M:%S rejection_reason: Ihre Nachricht an %t wurde automatisiert abgewiesen:%n%r auth default: mechanisms: plain login username_translation: @_._ verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: static args: uid=500 gid=500 home=/home/vmail/%Lu allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: postfix plugin: quota: maildir:User quota quota_rule: *:storage=8M quota_warning: storage=90%% /usr/local/bin/quota-warning.sh 90 quota_warning2: storage=75%% /usr/local/bin/quota-warning.sh 75 dovecot-ldap.conf - hosts = 123.456.789.123 123.456.789.124 base = OU=one,OU=two,OU=London,OU=GB,OU=User Accounts,DC=three,DC=core,DC=uk ldap_version = 3 auth_bind = yes auth_bind_userdn = %...@core.uk user_filter = ((objectClass=person)(cn=%u)) user_attrs = msRADIUSFramedIPAddress=quota_rule=*:storage=%$k _ Get your FREE TheDoghouseMail email address at http://www.thedoghousemail.com
Re: [Dovecot] Dovecot and LDAP-Quotas
On Mon, 2009-08-17 at 08:59 -0700, south africa wrote: user_attrs = msRADIUSFramedIPAddress=quota_rule=*:storage=%$k This requires using userdb ldap. userdb: driver: passwd userdb: driver: static args: uid=500 gid=500 home=/home/vmail/%Lu allow_all_users=yes But you're using only passwd and static. (And you probably don't really want to use userdb passwd anyway.) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Quota question.
On Mon, 17 Aug 2009, Timo Sirainen wrote: On Sun, 2009-08-16 at 09:09 -0400, Tom Diehl wrote: Actually it should be possible to just delete the row and let Dovecot recalculate the quota on next update, but currently this isn't working. I've a half-finished patch to make it work, but it's a pretty big change. v1.2.4 anyway hopefully has it. Looks like it doesn't make it for v1.2.4. v1.2.5 then. :-( I am looking fwd to this fix. I have several thousand mailboxes to migrate in the next few weeks. Not something that is really practical to do by hand. Maybe I could script something using expect and a modified db query so that I do not have to know all of the users passwds. Do all your users use the same UID? There's an easier way to do this Yes, they do. then: echo 1 getquotaroot inbox | USER=username dovecot --exec-mail imap That is really cool!! Thanks for the help. I really appreciate it. Enjoy your vacation!! Regards, -- Tom Diehl tdi...@rogueind.com Spamtrap address mtd...@rogueind.com
Re: [Dovecot] Postfix : lda problem
denis a écrit : Ok, here is a configuration that works fine but without success to retrieve the correct gid in the database. In fact, aliases no longer work In trying with alias_maps or virtual_alias_maps and in both cases the following error: User unknown in virtual mailbox table Any Ideas ? Thanks Denis ## /etc/postfix/main.cf alias_maps =proxy:mysql:/etc/postfix/myalias.cf, hash:/etc/aliases virtual_mailbox_base = /var/alternc/mail virtual_mailbox_maps = proxy:mysql:/etc/postfix/myvirtual.cf virtual_mailbox_domains = mysql:/etc/postfix/mydomain.cf default_privs = www-data virtual_uid_maps = static:33 virtual_gid_maps = static:33 virtual_transport = dovecot dovecot_destination_recipient_limit = 1 ## /etc/postfix/myalias.cf user = xyz password = xyz hosts = 10.0.112.1 dbname = alternc table = mail_alias select_field = alias where_field = mail
Re: [Dovecot] GSSAPI Authentication in v1.2.1
On 15/08/2009 2:08 AM, Timo Sirainen wrote: On Fri, 2009-08-14 at 16:46 +1000, Phillip Macey wrote: I also needed to change src/master/master-login-interface.h #define MASTER_LOGIN_MAX_DATA_SIZE (8192*2) Will these changes be included future releases or is this something that we will need to maintain for ourselves? -- Thanks, Phill Macey (CiSRA IT Services)
Re: [Dovecot] Gotchas in switching from one server to another without impacting users?
On Fri, Aug 14, 2009 at 5:17 PM, Sahil Tandonsa...@tandon.net wrote: On Fri, 14 Aug 2009, Timo Sirainen wrote: On Aug 14, 2009, at 12:36 AM, Gary Chodos wrote: We have to replace one mail store (foo.example.org) with another (bar.example.org). I rsync'd the maildirs from foo to bar today and the plan is to hold all delivery (in the SMTP server) on foo over the weekend, rsync again (this time it should be much faster since the large xfer already occurred today), then flush the SMTP queue on foo towards bar, direct all new deliveries to bar.example.org. Users currently access their IMAP mailboxes via imap.example.org. I plan to just 'flip the switch' at DNS so imap.example.org points to bar.example.org (instead of foo.example.org) so users don't have to change anything on their end and should not even notice this change. And I guess you also thought about the DNS cache TTLs? The OP should also consider killing dovecot during the rsync (similar to what another member of this list suggested). Then restart with a new configuration that proxies incoming IMAP connections towards the new server in case some clients still hit the old server before full DNS propagation. To make the proxy feature work I had to allow plaintext auth on 143 from old - new server. I use firewall rules to prohibit anyone except the old server from accessing the new one on port 143. Does this pose a security issue? Is there something else I should do to prevent security holes?
Re: [Dovecot] v1.2.4 released
dovecot-1.2-managesieve-0.11.8 fails to compile with dovecot 1.2.4 and sieve 0.1.11, following versions were used: drwxrwxrwx 4 root root 4096 18. Aug 07:31 dovecot-1.2.4 drwxrwxrwx 4 root root 4096 18. Aug 07:34 dovecot-1.2-managesieve-0.11.8 drwxrwxrwx 6 root root 4096 18. Aug 07:33 dovecot-1.2-sieve-0.1.11 config was created as follows: ./configure \ --prefix=/opt/dovecot \ --with-dovecot=/usr/src/dovecot-1.2.4 \ --with-dovecot-sieve=/usr/src/dovecot-1.2-sieve-0.1.11 \ host:/usr/src/dovecot-1.2-managesieve-0.11.8# make make all-recursive make[1]: Entering directory `/usr/src/dovecot-1.2-managesieve-0.11.8' Making all in src make[2]: Entering directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src' Making all in lib-managesieve make[3]: Entering directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/lib-managesieve' make[3]: Für das Ziel »all« ist nichts zu tun. make[3]: Leaving directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/lib-managesieve' Making all in lib-sievestorage make[3]: Entering directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/lib-sievestorage' make[3]: Für das Ziel »all« ist nichts zu tun. make[3]: Leaving directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/lib-sievestorage' Making all in managesieve make[3]: Entering directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/managesieve' make[3]: Für das Ziel »all« ist nichts zu tun. make[3]: Leaving directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/managesieve' Making all in managesieve-login make[3]: Entering directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/managesieve-login' gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot-1.2.4 -I/usr/src/dovecot-1.2.4/src/lib -I/usr/src/dovecot-1.2.4/src/lib-auth -I/usr/src/dovecot-1.2.4/src/lib-mail -I/usr/src/dovecot-1.2.4/src/lib-index -I/usr/src/dovecot-1.2.4/src/lib-storage -I/usr/src/dovecot-1.2.4/src/login-common -I../../src/lib-managesieve -I/usr/src/dovecot-1.2-sieve-0.1.11 -I/usr/src/dovecot-1.2-sieve-0.1.11/src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT managesieve-proxy.o -MD -MP -MF .deps/managesieve-proxy.Tpo -c -o managesieve-proxy.o managesieve-proxy.c managesieve-proxy.c:492:40: error: macro login_proxy_new requires 7 arguments, but only 6 given managesieve-proxy.c: In function ‘managesieve_proxy_new’: managesieve-proxy.c:491: warning: assignment from incompatible pointer type make[3]: *** [managesieve-proxy.o] Fehler 1 make[3]: Leaving directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src/managesieve-login' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/usr/src/dovecot-1.2-managesieve-0.11.8/src' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/usr/src/dovecot-1.2-managesieve-0.11.8' make: *** [all] Fehler 2 host:/usr/src/dovecot-1.2-managesieve-0.11.8# config dovecot 1.2.4: ./configure \ --prefix=/opt/dovecot \ --enable-asserts \ --enable-header-install \ --enable-largefile \ --with-ldap=yes \ --with-zlib \ --with-bzlib \ --with-libcap \ --with-ssl=openssl \ --with-gc \ --with-storages=maildir,mbox,dbox,cydir \ config dovecot-1.2-sieve-0.1.11: ./configure \ --prefix=/opt/dovecot \ --with-dovecot=/usr/src/dovecot-1.2.4 \ Of cource diff for dovecot 1.2.4 was applied. That patch was for 1.2.3, but patch did not complain. Is there any reason not to include that patch into Dovecot with option to select/deselect by configure ? regards Christian Powered bei http://freemail.taunusstein.net
[Dovecot-news] v1.2.4 released
http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root directory. + imap/pop3 proxy: If proxy destination is known to be down, fail connections to it immediately. + imap/pop3 proxy: Added proxy_timeout passdb extra field to specify proxy's connect timeout. - Fixed a crash in index file handling. - Fixed a crash in saving messages where message contained a CR character that wasn't followed by LF (and the CR happened to be the last character in an internal buffer). - v1.2.3 crashed when listing shared namespace prefix. - listescape plugin: Several fixes. - autocreate plugin: Fixed autosubscribing to mailboxes in subscriptions=no namespaces. signature.asc Description: This is a digitally signed message part ___ Dovecot-news mailing list Dovecot-news@dovecot.org http://dovecot.org/cgi-bin/mailman/listinfo/dovecot-news
