[Dovecot] Intermittent certificate cannot be verified error
Hi guys, Not sure where to start looking for this. I've got a few users getting intermittent certificate cannot be verified messages when connecting through SSL to Dovecot. Connections go through haproxy to Dovecot 1.1.8 on the back end servers. I've got verbose_ssl and auth_debug enabled. All I'm seeing on the logs for the time the users reported the error is this: Jan 21 23:30:51 mink dovecot: auth(default): new auth connection: pid=28811 Jan 21 23:30:51 mink dovecot: IMAP(us...@domain1.net): Disconnected in IDLE bytes=73/4235 Jan 21 23:24:23 mink dovecot: auth(default): new auth connection: pid=28811 Jan 21 23:24:23 mink dovecot: imap-login: Disconnected (no auth attempts): rip=x.x.x.x, lip=x.x.x.x Jan 21 23:24:23 mink dovecot: auth(default): new auth connection: pid=28811 Jan 21 23:24:24 mink dovecot: IMAP(us...@domain1.net): Disconnected in IDLE bytes=89/920 Since it's so intermittent I'm not sure where to start. Since there are no real errors in the Dovecot logs I'm suspecting that haproxy is perhaps not routing every packet correctly leading to Dovecot not getting all the data needed for the connection. Are there any other possibilities I've missed? Thanks Guy r...@mink:/var/log/mail# dovecot -n # 1.1.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.24-23-server x86_64 Ubuntu 8.04.1 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_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem disable_plaintext_auth: no verbose_ssl: yes 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 login_process_per_connection: no login_processes_count: 5 login_max_processes_count: 256 max_mail_processes: 1024 verbose_proctitle: yes mail_location: maildir:%h/Maildir/ mail_full_filesystem_access: yes mmap_disable: yes dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/pop3 mail_process_size: 128 mail_plugins(default): imap_quota quota mail_plugins(imap): imap_quota quota mail_plugins(pop3): quota mail_log_max_lines_per_sec: 30 imap_client_workarounds: outlook-idle delay-newmail pop3_uidl_format: %08Xv%08Xu pop3_client_workarounds: outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: maildir:%h/Maildir/ hidden: yes subscriptions: yes auth default: cache_size: 2048 cache_ttl: 300 cache_negative_ttl: 1 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@' master_user_separator: * debug: yes worker_max_count: 5 passdb: driver: passwd-file args: /etc/dovecot/dovecot-master.pwd master: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf plugin: quota: maildir quota_rule: *:storage=100M quota_rule2: Trash:ignore -- Don't just do something...sit there!
Re: [Dovecot] help on writing a rule for perventing spam
On 1/21/2009, Giuliano Gavazzi (dev+li...@humph.com) wrote: The postfix backscatter readme is a good start, esppecially is you are using postfix - and if you aren't, why aren't you? ;) ... but the concepts can be applied to any MTA... I don't use postfix, because I use exim... And as I said... the CONCEPTS can be applied to ANY MTA...
[Dovecot] expire plugin error
Hi, I am using the db backend for the expire plugin and found the following error message in the logfile: dovecot: Jan 22 10:10:55 Error: dict: secondary db: unable to allocate space from the buffer cache dovecot: Jan 22 10:10:55 Error: dict: Failed to initialize dictionary 'expire' dovecot: Jan 22 10:10:55 Error: IMAP(xx): read(/var/dovecot/dict-server) failed: Remote disconnected Anyone know how to fix this? I do not want to use SQL as backend, that would be overkill. # ls -alFh /var/dovecot/dict-server srwxrwxrwx 1 root wheel -0B Jan 22 10:08 /var/dovecot/dict-server= # dovecot -n # 1.1.8: /etc/dovecot.conf # OS: OpenBSD 4.4 sparc64 ffs base_dir: /var/dovecot/ log_path: /var/log/dovecot.log protocols: imaps pop3s listen: ssl_ca_file: /etc/ssl/.ca ssl_cert_file: /etc/ssl/.crt ssl_key_file: /etc/ssl/private/.key login_dir: /var/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_user: _dovecot mail_max_userip_connections(default): 25 mail_max_userip_connections(imap): 25 mail_max_userip_connections(pop3): 5 first_valid_uid: 1 last_valid_uid: 1 first_valid_gid: 100 last_valid_gid: 100 mail_gid: 100 mail_location: mbox:/var/data/mail/%u/mbox:INBOX=/var/data/mail/%u/mbox/inbox:INDEX=/var/dovecot/index/%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_plugins(default): expire imap_quota quota trash zlib mail_plugins(imap): expire imap_quota quota trash zlib mail_plugins(pop3): expire quota zlib 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 netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail 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: passdb: driver: bsdauth userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs:user:noenforcing:mount=/var/data trash: /etc/dovecot-trash.conf expire: Trash 14 expire_dict: proxy:/var/dovecot/dict-server:expire dict: expire: db:/var/lib/dovecot/expire.db
Re: [Dovecot] Courier-dovecot migration script
2008/12/12 Timo Sirainen t...@iki.fi On Nov 12, 2008, at 3:01 PM, Warren Baker wrote: Where the first line is a header. So for example with 3 different kinds of Courier UIDLs: 3 V1196932607 N125574 1234 P1234 :1225386267.M230815P21206.host 1235 P1196932607-1235 :1225386268.M230815P21206.host 1236 P1225386269.M230815P21206.host :1225386269.M230815P21206.host I actually started adding this to your script already. As soon as I have a working copy I will send it on to you. Did you ever finish writing it? Sorry for the late reply, was on holiday. Yes although its been slightly customized for our environment and its a bit of a hack. I see John Lightsey version is way better than ours and that you have improved upon it. So wont bother sending ours. Thanks, Warren
Re: [Dovecot] imap-login: memory corruption
* Ralf Hildebrandt ralf.hildebra...@charite.de: * Ralf Hildebrandt ralf.hildebra...@charite.de: Did that and recompiled, deactivated valgrind, let's see what happens. Right now I don't see any more libc related crashes. Still no crashes. Your fix seems to be working -- Ralf Hildebrandt (ralf.hildebra...@charite.de) snick...@charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de My advice is simple: Boycott IE. It's a cancer on the Web that must be stopped. IE isn't secure and isn't standards-compliant, which makes it unworkable both for end users and Web content creators.
Re: [Dovecot] Shared mailboxes support status
On Wed, Jan 21, 2009 at 08:57:40PM +0100, Robert Schetterer wrote: I guess part of the answer is in the diffences between shared and public namespaces handling. yes and imap_acls My understanding of rfc2342 and dovecot is that : personnal namespace == private malboxes == mailboxes one's own other user's namespace == shared mailboxes == mailboxes one's own and somone else has access to shared namespace == public mailboxes == mailboxes everybody or only some user has access to but which don't belong to a particular user My understanding is that 1.1. support only personnal and shared namespaces (as defined in rfc2342) Am I correct ? Is the difference, feature wise, between 1.1. and 1.2, just the addition of shared namespaces in 1.2, and maybe, as you said ACLs ? What's changed regarding ACL ? In short : what exactly are the difference (at a feature level, not a coding level) between 1.1. and 1.2 regarding those concepts ? And is the support in 1.1. of personnal and shared namespace (as in rfc2342) stable ? Thanks. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
[Dovecot] Update dovecot-1.0.13_1 -- dovecot-1.1.8 (AS proxy)
Hello List! I´ve following problem after updating dovecot... Error: (Empty password returned without nopassword) Jan 21 15:56:15 test-mi dovecot: auth(default): new auth connection: pid=83362 Jan 21 15:56:15 test-mi dovecot: auth(default): client in: AUTH 7 PLAIN service=imaplip=192.168.0.32rip=192.168.0.86 lport=143 rport=2905 resp=AHRrdWV2NUBnb25lby5jb98AdGVzdHVzZXI1 Jan 21 15:56:15 test-mi dovecot: auth-worker(default): sql(t...@domain.com,192.168.0.86): query: SELECT NULL as password, mailhost as host, 'Y' AS proxy FROM mail_users WHERE username = 't...@domain.com' and status='ok' Jan 21 15:56:15 test-mi dovecot: auth-worker(default): sql(t...@domain.com,192.168.0.86): Empty password returned without nopassword # My config: dovecot -n # 1.1.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE-p3 i386 base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_disable: yes ssl_parameters_regenerate: 0 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_greeting: goneo mail ready. login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_process_size: 128 login_processes_count: 20 login_max_processes_count: 256 login_max_connections: 2048 max_mail_processes: 1024 verbose_proctitle: yes first_valid_gid: 0 mail_location: maildir:%h/mail/:INDEX=%h/index/:INBOX=%h/mail/.INBOX mail_debug: yes fsync_disable: yes 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: static args: uid=1000 gid=1000 home=/dev/null socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 438 -- grep -v '^ *\(#.*\)\?$' dovecot-sql.conf driver = mysql connect = host=192.168.0.3 dbname=email user=readonly password=93700 default_pass_scheme = PLAIN password_query = SELECT NULL as password, mailhost as host, 'Y' AS proxy FROM mail_users WHERE username = '%u' and status='ok' # Any ideas what I can do? Thanks for your help. Best regards, Thorben
Re: [Dovecot] help on writing a rule for perventing spam
On T 22 Jan, 2009, at 11:49 , Charles Marcus wrote: On 1/21/2009, Giuliano Gavazzi (dev+li...@humph.com) wrote: The postfix backscatter readme is a good start, esppecially is you are using postfix - and if you aren't, why aren't you? ;) ... but the concepts can be applied to any MTA... I don't use postfix, because I use exim... And as I said... the CONCEPTS can be applied to ANY MTA... well, first of all backscatter is not really the issue of this thread. Secondly the concepts are not all that good. In particular the one entitled: Blocking backscatter mail with forged sender information that states: Like many people I still have a few email addresses in domains that I used in the past. Mail for those addresses is forwarded to my current address. Most of the backscatter mail that I get claims to be sent from these addresses. Such mail is obviously forged and is very easy to stop. From what I understand he is rejecting backscatter that is sent to some of his old addresses (with an identical forged sender, but this is irrelevant) and from there forwarded to his mail server. Very bad. If you have configured forwarding somewhere you must be prepared to accept anything from there, or else you will be the cause of backscatter as the peer server is a genuine server and not a spambot. The old Postel rule Be conservative with what you send and liberal with what you receive (or something on those lines) might be too liberal in the current internet, but certainly should not be relaxed on the conservative part... The first thing an administrator should look for is to avoid generating spam of any sort, then he can think of ways to stop it (and even more responsibly to place a further burden on spammers with delays and the like, but this is something you can only do on an MTA). Giuliano
Re: [Dovecot] help on writing a rule for perventing spam
On 1/22/2009, Giuliano Gavazzi (dev+li...@humph.com) wrote: Like many people I still have a few email addresses in domains that I used in the past. Mail for those addresses is forwarded to my current address. Most of the backscatter mail that I get claims to be sent from these addresses. Such mail is obviously forged and is very easy to stop. From what I understand he is rejecting backscatter that is sent to some of his old addresses (with an identical forged sender, but this is irrelevant) and from there forwarded to his mail server. No... you're reading it wrong. He is talking about domains of HIS... so he CONTROLS them... in other words, the same server that is receiving the backscatter is the one rejecting the forged backscatter. You would be right if you were talking about an old hotmail account or something like that, but we're not. -- Best regards, Charles
[Dovecot] cmusieve don't works for me...
Ok, sorry to bother again, but i am going crazy to make work cmusieve with dovecot. I intend to use it for the vacation system, but...seems the system ignores the .dovecot.sieve file into the user dir... I am doing something wrong, but i don't know what... Here is my configs: I use OpenSuse 11.0. # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.25.20-0.1-pae i686 openSUSE 11.0 (i586) ext3 log_path: /var/log/dovecot-err.log info_log_path: /var/log/dovecot-inf.log protocols: imap imaps pop3 pop3s managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login first_valid_uid: 51 last_valid_uid: 51 first_valid_gid: 51 last_valid_gid: 51 mail_location: maildir:/var/mail/virtual/%d/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %Mf pop3_uidl_format(managesieve): %08Xu%08Xv sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): /var/mail/virtual/%d/%u/.dovecot.sieve auth default: passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota: maildir:user quota quota_warning: storage=80%% /usr/bin/quota_warning.sh 80 quota_warning2: storage=90%% /usr/bin/quota_warning.sh 90 quota_warning3: storage=99%% /usr/bin/quota_warning.sh 90 I have also created a .dovecot.sieve file into the user dir like this: ls -la .dovecot.sieve -rw-r--r-- 1 postfix postfix 149 Jan 24 07:59 .dovecot.sieve cat .dovecot.sieve require vacation; vacation :days 23 :addresses [t...@domain.pri] I'm away until October 19. ; If i try to send a mail, in dovecot-inf.log i read this: deliver(t...@domain.pri): Jan 24 09:00:32 Info: Loading modules from directory: /usr/lib/dovecot/modules/lda deliver(t...@domain.pri): Jan 24 09:00:32 Info: Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so deliver(t...@domain.pri): Jan 24 09:00:32 Info: Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so deliver(t...@domain.pri): Jan 24 09:00:32 Info: auth input: t...@domain.pri deliver(t...@domain.pri): Jan 24 09:00:32 Info: auth input: maildir=t...@domain.pri/ deliver(t...@domain.pri): Jan 24 09:00:32 Info: auth input: uid=51 deliver(t...@domain.pri): Jan 24 09:00:32 Info: auth input: gid=51 deliver(t...@domain.pri): Jan 24 09:00:32 Info: auth input: quota_rule=*:bytes=0 deliver(t...@domain.pri): Jan 24 09:00:32 Info: Quota root: name=user quota backend=maildir args= deliver(t...@domain.pri): Jan 24 09:00:32 Info: Quota rule: root=user quota mailbox=* bytes=0 (0%) messages=0 (0%) deliver(t...@domain.pri): Jan 24 09:00:32 Info: Quota warning: bytes=0 (80%) messages=0 (0%) command=/usr/bin/quota_warning.sh 80 deliver(t...@domain.pri): Jan 24 09:00:32 Info: Quota warning: bytes=0 (90%) messages=0 (0%) command=/usr/bin/quota_warning.sh 90 deliver(t...@domain.pri): Jan 24 09:00:32 Info: Quota warning: bytes=0 (99%) messages=0 (0%) command=/usr/bin/quota_warning.sh 90 deliver(t...@domain.pri): Jan 24 09:00:32 Info: maildir: data=/var/mail/virtual/domain.pri/t...@domain.pri deliver(t...@domain.pri): Jan 24 09:00:32 Info: maildir++: root=/var/mail/virtual/domain.pri/t...@domain.pri, index=, control=, inbox=/var/mail/virtual/domain.pri/t...@domain.pri deliver(t...@domain.pri): Jan 24 09:00:32 Info: msgid=49789612.7060...@atpss.net: saved mail to INBOX As u can see, the cmusieve module is loaded, but if i go to the mail dir of the user.. ls -la total 80 drwx-- 5 postfix postfix 4096 Jan 24 09:01 . drwx-- 3 postfix postfix 4096 Jan 14 23:07 .. -rw-r--r-- 1 postfix postfix 149 Jan 24 07:59 .dovecot.sieve drwx-- 2 postfix postfix 4096 Jan 23 06:59 cur -rw--- 1 postfix postfix 1727 Jan 24 09:00 dovecot-uidlist -rw--- 1 postfix postfix 8 Jan 14 23:07
Re: [Dovecot] Intermittent certificate cannot be verified error
Guy wrote: Hi guys, Not sure where to start looking for this. I've got a few users getting intermittent certificate cannot be verified messages when connecting through SSL to Dovecot. Connections go through haproxy to Dovecot 1.1.8 on the back end servers. I've got verbose_ssl and auth_debug enabled. It is SSL error. This error message indicates that the client was unable to validate the certificate chain, or that the public key that was used to validate the certificate signature is not the correct key.
Re: [Dovecot] cmusieve don't works for me...
On 22.01.2009 16:55 Claudio Prono wrote:
Ok, sorry to bother again, but i am going crazy to make work cmusieve
with dovecot. I intend to use it for the vacation system, but...seems
the system ignores the .dovecot.sieve file into the user dir... I am
doing something wrong, but i don't know what...
...
Put the .dovecot.sieve script in the (virtual) users home directory
(http://wiki.dovecot.org/UserDatabase). If your setup doesn't allow you
to specify a home directory you have to specify the sieve location in
the plugin section
(http://wiki.dovecot.org/LDA/Sieve#head-3940e226e2a575b992a4303c52b9253ae513668e)
If you want to get more details (e.g. what happens on delivery) add
maild_debug = yes to your lda {} section in dovecot.conf
Regards,
Pascal
--
Ubuntu is an ancient African word meaning “I can’t install Debian.”
-- unknown
Re: [Dovecot] Sieve filters forwarding erratic after upgrade to 1.1.8
On 22.01.2009 20:42 David Anderson wrote: Upon upgrading Dovecot from 1.1.7 to 1.1.8, one of my sieve filters (generated with avelsieve) no longer works. Please show the filter rule. The filter is intended to redirect to another address when the header from contains something like @example.com. However, it simply never performs the redirection. Here it works: Jan 22 21:49:15 vh3 deliver(u...@test.tld): Sending a forward to u...@example.org with return path john@example.com Jan 22 21:49:15 vh3 postfix/pickup[13961]: 5C3B165CF: uid=70005 from=john@example.com Jan 22 21:49:15 vh3 deliver(u...@test.tld): msgid=6zd0$2460.john@example.com: forwarded to u...@example.org Jan 22 21:49:15 vh3 deliver(u...@test.tld): msgid=6zd0$2460.john@example.com: saved mail to INBOX Tests show that if the filter also has the keep copy in mailbox as well as redirecting open on, then the copy is kept. If that option is off, then no redirection happens and no copy is kept- i.e. the mail is simply lost. Works also w/o explicit keep; Deleting and recreating the filter makes no difference, and neither does moving its order in the list of filters. In the same list of filters a vacation message works. On a second mailbox where a filter is redirecting all mail with header precedence not equal to list, the redirection always takes place, so this isn't a generic problem with all redirections. I also updated avelsieve from 1.9.7 (July 2007) to the latest SVN and this made no difference. I am using the dovecot-1.1.8-0_85.el5 and dovecot-sieve-1.1.5-8.el5 RPMs from http://atrpms.net. I'm using dovecot-sieve-1.1.6, compiled from source. Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown
[Dovecot] Migration question: .INBOX?
Hi, Not much left to fix in my migration script (moving between two dovecot servers). However, I discovered a mail folder .INBOX without cur, new and tmp subfolders, and the .imap.index files were rather old (feb 2006). Is this an old relic from early dovecot versions (I once ran 0.99 on this old server)? Or is it old client software? There are no data in it. TIA, Peter -- Peter Lindgren http://www.norrskenkonsult.com
Re: [Dovecot] Migration question: .INBOX?
On Thu, 2009-01-22 at 22:03 +0100, Peter Lindgren wrote: Hi, Not much left to fix in my migration script (moving between two dovecot servers). However, I discovered a mail folder .INBOX without cur, new and tmp subfolders, and the .imap.index files were rather old (feb 2006). Is this an old relic from early dovecot versions (I once ran 0.99 on this old server)? Yes. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Migration question: .INBOX?
Timo Sirainen skrev: On Thu, 2009-01-22 at 22:03 +0100, Peter Lindgren wrote: Is this an old relic from early dovecot versions (I once ran 0.99 on this old server)? Yes. Ok, that means the wiki QA needs a slight update (removal of .INBOX text). http://wiki.dovecot.org/QuestionsAndAnswers?highlight=(.INBOX) Particularly in the How does new mail get into the Maildir folders? section. /Peter -- Peter Lindgren http://www.norrskenkonsult.com
Re: [Dovecot] cmusieve don't works for me...
Claudio Prono schreef:
Ok, sorry to bother again, but i am going crazy to make work cmusieve
with dovecot. I intend to use it for the vacation system, but...seems
the system ignores the .dovecot.sieve file into the user dir... I am
doing something wrong, but i don't know what...
Here is my configs:
sieve(managesieve): /var/mail/virtual/%d/%u/.dovecot.sieve
plugin:
quota: maildir
quota: maildir:user quota
quota_warning: storage=80%% /usr/bin/quota_warning.sh 80
quota_warning2: storage=90%% /usr/bin/quota_warning.sh 90
quota_warning3: storage=99%% /usr/bin/quota_warning.sh 90
What can be my error?
You need to add a sieve= setting to the plugin {...} section as well for
Dovecot v1.1. So copy it to there from the protocol managesieve {...}
section. This duplicate configuration is removed for v1.2. With your
current configuration it is looking for the Sieve script in the user's
home directory (~/.dovecot.sieve) if he even has one.
Enable mail_debug to see what it is doing.
Regards,
--
Stephan Bosch
step...@rename-it.nl
Re: [Dovecot] Sieve regex match problem
Andy Howell wrote: Glad you like my creative use is 'fileinto. Thanks for the quick fix. Are there plans to make another release of 1.2 any time soon? Current code depends on unreleased changes in the Dovecot v1.2 tree. So, this will need to wait until Timo makes a new release. Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] cmusieve don't works for me...
On 22.01.2009 16:55 Claudio Prono wrote: ... plugin: ... quota_warning: storage=80%% /usr/bin/quota_warning.sh 80 quota_warning2: storage=90%% /usr/bin/quota_warning.sh 90 quota_warning3: storage=99%% /usr/bin/quota_warning.sh 90 ^^ ^^ Please check also the order of your quota warnings. See http://wiki.dovecot.org/Quota/1.1#head-03d8c4f6fb28e2e2f1cb63ec623810b45bec1734 for more details. Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown
Re: [Dovecot] behavior of dovecot with Openldap
Dear all, Thank you very much for your help. Any idea what Dovecot version? rhel4 had 1.0.rc15 I think? I know there were some LDAP bugs in it, but I don't really remember anymore. Did Dovecot really try to access the server2, or was it simply unable to reconnect to the LDAP server at all? If the latter, it's probably just rc15 bug. Since the customer has been using RHEL4.3, Dovecot version should be something in between dovecot-0.99.11-2.EL4.1 and 0.99.11-9.EL4. These are all for RHEL4. I'm sorry that I have not been provided the version. Yes, after server1 being unable to respond, Dovecotwas accessing to the server2. In addition, although, the server1 was re-starting ldap service which means that server1 should have been available to respond, Dovecot was still accessing to the server2. Shouldn't Dovecot reconnection to the server1 as its service become available? All I would like to know right now are that is as follows. 1. About the specification of dovecot for reconnection In case Dovecot switch to server2 due to server1 gets some problems such as service down, does the server2 never reconnect to the server1 even the server1 become available to respond again? Even if so, is it sure that if the server2 is down, then does Dovecot normally try to connect to the server1? 2. Configuration by 'hosts' and 'uris' parameter in dovecot-ldap.conf Is there any differences for the way to reconnectionś behavior between those parameter? I believe that both parameter can specify sevral ldap server, then I would like to know whether each parameter does the action for reconnection in the same way. Thanks, Masaharu Kawada Timo Sirainen wrote: On Tue, 2009-01-20 at 13:53 +0900, Masaharu Kawada wrote: -2008/11/16 The customer updated openldap package openldap-2.2.13-6.4E ⇒ openldap-2.2.13-12.el4 .. For this reason, the customer wants to know why dovecot accessed only server2 since ldap package was updated on 2008/11/16 and also wants to know why replication had been failed after updating the package. Any idea what Dovecot version? rhel4 had 1.0.rc15 I think? I know there were some LDAP bugs in it, but I don't really remember anymore. Did Dovecot really try to access the server2, or was it simply unable to reconnect to the LDAP server at all? If the latter, it's probably just rc15 bug. As you said, if both ldap servers are used ramdomly, That was only a guess. If the problem was with reconnection, it is (was) a Dovecot bug. If the problem is something else, it's because of OpenLDAP library which I don't really know much about. -- --- Masaharu Kawada Associate Global Support Engineer Red Hat K K Ebisu Neonato 8F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
Re: [Dovecot] behavior of dovecot with Openldap
Hello, Thank you very much for your respons. I have been keeping this thread on the latest mail sent by Timo-san. Regards, Masaharu Kawada geoffroy desvernay wrote: Masaharu Kawada a écrit : I'm pretty sure that configuration will simply use both the servers all the time more or less randomly. Unless OpenLDAP library has some code that does something similar to what you're talking about, but somehow I doubt that. Here we use uris parameter instead of hosts, and we seems to have expected behaviour: dovecot is always using the first listed uri except if it doesn't respond (switch to the second) We can check it simply: first listed server have more than 200 simultaneous connexions daily, 2nd have only one per slave (replication thread) (we use the slave as first uri) Hope this helps. -- --- Masaharu Kawada Associate Global Support Engineer Red Hat K K Ebisu Neonato 8F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
Re: [Dovecot] behavior of dovecot with Openldap
Hello, Thank you very much for your respons. I have been keeping this thread on the latest mail sent by Timo-san. Regards, Masaharu Kawada Joseba Torre wrote: El Martes, 20 de Enero de 2009 a las 08:47, geoffroy desvernay escribió: Here we use uris parameter instead of hosts, and we seems to have expected behaviour: dovecot is always using the first listed uri except if it doesn't respond (switch to the second) Same experience here (RHEL4 and several dovecot versions). Dovecot only uses the 1st ldap server in the uris variable, and only tries the other ones when this doesn't respond: we've had some problems with the primary server taking like 1 minute for each answer and dovecot didn't switch to the next one. -- --- Masaharu Kawada Associate Global Support Engineer Red Hat K K Ebisu Neonato 8F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
Re: [Dovecot] expire plugin error
Anyone know how to fix this? In reply to myself, some more info... Using Google I found some hints that maybe the cache size is too small... but how can that be fixed? Or... since this is BDB and the machine is a sparc64, it's some memory alignment issue? # l /var/lib/dovecot/ total 3116 drwxr-x--- 2 root wheel - 512B Jan 22 11:26 ./ drwxr-x--- 3 root wheel - 512B Jan 15 11:23 ../ -rw--- 1 root wheel - 24.0K Jan 23 07:13 __db.001 -rw--- 1 root wheel - 64.0K Jan 23 07:13 __db.002 -rw--- 1 root wheel - 264K Jan 23 07:13 __db.003 -rw--- 1 root wheel - 96.0K Jan 23 07:13 __db.004 -rw--- 1 root wheel - 56.0K Jan 23 07:13 __db.005 -rw--- 1 root wheel -0B Jan 15 12:01 auth-success -rw--- 1 root wheel - 32.0K Jan 22 13:58 expire.db -rw--- 1 root wheel - 10.0M Jan 22 23:03 log.01 -rw-r--r-- 2 root wheel - 236B Jan 22 11:26 ssl-parameters.dat # db4_stat -d /var/lib/dovecot/expire.db Fri Jan 23 08:30:19 2009Local time 53162 Btree magic number 9 Btree version number Big-endian Byte order Flags 2 Minimum keys per-page 16384 Underlying database page size 4079Overflow key/data size 1 Number of levels in the tree 1 Number of unique keys in the tree 1 Number of data items in the tree 0 Number of tree internal pages 0 Number of bytes free in tree internal pages (0% ff) 1 Number of tree leaf pages 16322 Number of bytes free in tree leaf pages (0% ff) 0 Number of tree duplicate pages 0 Number of bytes free in tree duplicate pages (0% ff) 0 Number of tree overflow pages 0 Number of bytes free in tree overflow pages (0% ff) 0 Number of empty pages 0 Number of pages on the free list # db4_stat -mh /var/lib/dovecot 260KB 832B Total cache size 1 Number of caches 1 Maximum number of caches 264KB Pool individual cache size 0 Maximum memory-mapped file size 0 Maximum open file descriptors 0 Maximum sequential buffer writes 0 Sleep after writing maximum sequential buffers 0 Requested pages mapped into the process' address space 302 Requested pages found in the cache (70%) 129 Requested pages not found in the cache 118 Pages created in the cache 53 Pages read into the cache 9 Pages written from the cache to the backing file 48 Clean pages forced from the cache 94 Dirty pages forced from the cache 0 Dirty pages written by trickle-sync thread 29 Current total page count 0 Current clean page count 29 Current dirty page count 37 Number of hash buckets used for page location 678 Total number of times hash chains searched for a page 13 The longest hash chain searched for a page 3792Total number of hash chain entries checked for page 0 The number of hash bucket locks that required waiting (0%) 0 The maximum number of times any hash bucket lock was waited for (0%) 0 The number of region locks that required waiting (0%) 0 The number of buffers frozen 0 The number of buffers thawed 0 The number of frozen buffers freed 362 The number of page allocations 16784 The number of hash buckets examined during allocations 266 The maximum number of hash buckets examined for an allocation 769 The number of pages examined during allocations 13 The max number of pages examined for an allocation 0 Threads waited on page I/O Pool File: unknown 8192Page size 0 Requested pages mapped into the process' address space 3 Requested pages found in the cache (75%) 1 Requested pages not found in the cache 2 Pages created in the cache 0 Pages read into the cache 0 Pages written from the cache to the backing file Pool File: unknown 8192Page size 0 Requested pages mapped into the process' address space 4 Requested pages found in the cache (80%) 1 Requested pages not found in the cache 2 Pages created in the cache 0 Pages read into the cache 0 Pages written from the cache to the backing file Pool File: unknown 8192Page size 0 Requested pages mapped into the process' address space 4 Requested pages found in the cache (80%) 1 Requested pages not found in the cache 2 Pages created in the cache 0 Pages read into the cache 0 Pages written from the cache to the backing file Pool File: unknown 8192Page size 0 Requested pages mapped into the process' address space 4 Requested pages found in the cache (80%) 1 Requested pages not found in the cache 2 Pages created in the cache 0 Pages read into the cache 0 Pages written from the cache to the backing file Pool File: unknown 8192Page size 0 Requested pages mapped into the process' address space 4 Requested pages found in the cache (80%) 1 Requested pages not found in the
