Re: [Dovecot] 1.0(.14) vs 1.1.2 performance
On Tue, Aug 05, 2008 at 06:40:00PM -0400, Timo Sirainen wrote: Do you use POP3? Yes. I don't have the stats right now but I'd say, on 2500 users, 60% are using IMAP, 40% POP3. But I had the feeling that it was the IMAP processes which were causing the load, particulary because some IMAP users were complaining about low speed while moving messages from mailboxes (I'm talking 1.0.14 here). However, I don't know if it was a cause or a consequence... That should work better. A lot indeed. There are also less reads/ writes to index files. And dovecot-uidlist is usually updated by appending to it instead of rewriting it. So no big architectural changes ? Or maybe changes in the locking code ? What about the upcomming 2.0 ? Is the new master expected to provide load improvement ? Great work anyway ! ;-) Thanks. -- Thomas Hummel | Institut Pasteur [EMAIL PROTECTED] | Pôle informatique - systèmes et réseau
[Dovecot] Can't connect to IMAP
Hi all, This is my first post here so i hope this will reach you :) My problem since a few days back is that IMAP doesn't seem to be started. The logfiles says's everything is in order, but port 143 isn't up and Squirrelmail can't connect, i have no clue what's causing this everything runned smoothly a couple of days ago. Im using postfix/amavis spamassasin. Here's some information Dovecot v1.1.2 # 1.1.2: /etc/dovecot/dovecot.conf protocols = imap imaps log_timestamp: %Y-%m-%d %H:%M:%S listen: disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 106 mail_access_groups: mail mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n auth default: mechanisms: digest-md5 plain passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf And once again. I don't get any errors in the logfiles. Mail.log last 5 lines after a restart :10024, delay=1414, delays=1402/0.01/0/12, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=04139-03, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as C4FD1406024) Aug 6 07:47:58 localhost postfix/qmgr[4630]: E956E40604A: removed Aug 6 07:47:58 localhost postfix/virtual[32190]: C4FD1406024: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=virtual, delay=0.07, delays=0.03/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) Aug 6 07:47:58 localhost postfix/qmgr[4630]: C4FD1406024: removed Aug 6 10:55:56 localhost dovecot: Killed with signal 15 Aug 6 10:55:56 localhost dovecot: Dovecot v1.1.2 starting up Aug 6 10:55:57 localhost dovecot: auth-worker(default): mysql: Connected to localhost (postfix) syslog / mail.err / .warn info doesn't say anything about errors eithers. Any clue?
Re: [Dovecot] mbox empty messages in Sent folder
On Mon, Aug 4, 2008 at 4:17 PM, Timo Sirainen [EMAIL PROTECTED] wrote: Maybe this helps? http://hg.dovecot.org/dovecot-1.1/rev/8ab845d3c96d It seems so, thanks Timo. With this patch, by now, all sent mails are correctly written in Sent folder, I'let you know if I've just been lucky :) BTW I didn't succeed in reproducing this issue with imaptest, what was the trick to trigger it?
Re: [Dovecot] Can't connect to IMAP
Hi David, Am 06.08.2008 10:59 schrieb David Hall: … My problem since a few days back is that IMAP doesn't seem to be started. The logfiles says's everything is in order, but port 143 isn't up and Squirrelmail can't connect, i have no clue what's causing this everything runned smoothly a couple of days ago. Im using postfix/amavis spamassasin. Is Dovecot really running on your system? Please show the output from `ps -ef | grep dovecot` and `netstat -tlpn | egrep ':(143|993)`. How do you try to connect to the imapd? http://wiki.dovecot.org/TestInstallation Here's some information Dovecot v1.1.2 [output from `dovecot -n` snipped ] And once again. I don't get any errors in the logfiles. Mail.log last 5 lines after a restart … Aug 6 07:47:58 localhost postfix/virtual[32190]: C4FD1406024: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=virtual, delay=0.07, delays=0.03/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) … This Mail was delivered with Postfix's virtual transport, not with Dovecot's LDA http://wiki.dovecot.org/LDA/Postfix() Aug 6 10:55:56 localhost dovecot: Killed with signal 15 Aug 6 10:55:56 localhost dovecot: Dovecot v1.1.2 starting up Aug 6 10:55:57 localhost dovecot: auth-worker(default): mysql: Connected to localhost (postfix) Looks good. Regards, Pascal
[Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
Hi, This small mail to share my observation about a recent move of mailboxes between two servers and ask about explanation and/or improvement about UIDL in dovecot. SV1 : Dovecot 0.99.14 / Red Hat Fedore Core 4 SV2 : Dovecot 1.07 / CentOS 5.2 Mailboxes in /var/spool/mail on the twoo servers. Test will be done with outlook express with option leave message on server checked. Goal is simply to move users mailboxes from SV1 to SV2 without re-downloading all messages. Try 1: - Stop dovecot on SV2 - Clear all dovecot indexes on SV2 - Rsync of my mailbox - Start dovecot on SV2 - Update pop setting in outlook and send/receive Result : = starting to download 3000 mails... After some debug, I discovered that UIDL where not of the same format = put pop3_uidl_format = %v.%u in dovecot.conf of SV2. Try 2: Same operations as Try1 Result : = starting to download 3000 mails... UIDL's where of the same format but values where not corresponding... Teleting on SV1 and asking UIDL, last value is xx.85878. On SV2, xx.85879 was the FIRST value of the list. Conclusion for the moment, Dovecot has a problem with the detection of existing UID of the moved mailbox. Comparaison of first header found from the two mailboxes show ... differences ! SV1 give the following : (...) X-UID: 70570 Content-Length: 1561 X-IMAPbase: xx 85845 $MDNSent X-Keywords: (...) SV2 give the following (after first POP attempt) : (...) Content-Length: 1561 X-IMAPbase: xx 089204 $MDNSent X-Keywords: X-UID: 85846 (...) Observation : X-UID: 85846 is not at the same place in the header. Try 3: - Stop dovecot on SV2 - Clear all dovecot indexes on SV2 - Rsync of my mailbox - Edit mailbox and move X-UID header after the X-Keywords header - Start dovecot on SV2 - Update pop setting in outlook and send/receive Result : = OK. Is that normal that dovecot is impacted by the position of the headers ? Maybe some improvement possible ? Maybe theyre is another method to make my migration ? Any observation or comment is welcome... -- Benoît Desloges Network Engineer
Re: [Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
On 8/6/2008, Benoît DESLOGES ([EMAIL PROTECTED]) wrote: Goal is simply to move users mailboxes from SV1 to SV2 without re-downloading all messages. If you're going to go through all of this trouble, you really should go ahead and update to latest version - now at 1.1.2... rpms for centos available on atrpms.net -- Best regards, Charles
Re: [Dovecot] Can't connect to IMAP
Pascal Volk skrev: Hi David, Am 06.08.2008 10:59 schrieb David Hall: … My problem since a few days back is that IMAP doesn't seem to be started. The logfiles says's everything is in order, but port 143 isn't up and Squirrelmail can't connect, i have no clue what's causing this everything runned smoothly a couple of days ago. Im using postfix/amavis spamassasin. Is Dovecot really running on your system? Please show the output from `ps -ef | grep dovecot` and `netstat -tlpn | egrep ':(143|993)`. How do you try to connect to the imapd? http://wiki.dovecot.org/TestInstallation Here's some information Dovecot v1.1.2 [output from `dovecot -n` snipped ] And once again. I don't get any errors in the logfiles. Mail.log last 5 lines after a restart … Aug 6 07:47:58 localhost postfix/virtual[32190]: C4FD1406024: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=virtual, delay=0.07, delays=0.03/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) … This Mail was delivered with Postfix's virtual transport, not with Dovecot's LDA http://wiki.dovecot.org/LDA/Postfix() Aug 6 10:55:56 localhost dovecot: Killed with signal 15 Aug 6 10:55:56 localhost dovecot: Dovecot v1.1.2 starting up Aug 6 10:55:57 localhost dovecot: auth-worker(default): mysql: Connected to localhost (postfix) Looks good. Regards, Pascal Problem solved. it was listen = and not listen = * that caused it. strange thing is that i haven't changed those lines.
Re: [Dovecot] mbox empty messages in Sent folder
On Aug 6, 2008, at 6:11 AM, Diego Liziero wrote: On Mon, Aug 4, 2008 at 4:17 PM, Timo Sirainen [EMAIL PROTECTED] wrote: Maybe this helps? http://hg.dovecot.org/dovecot-1.1/rev/8ab845d3c96d It seems so, thanks Timo. With this patch, by now, all sent mails are correctly written in Sent folder, I'let you know if I've just been lucky :) BTW I didn't succeed in reproducing this issue with imaptest, what was the trick to trigger it? I'm not sure if there's an easy way to reproduce it. You'd have to cause the first read to return EAGAIN but the second read that comes only microseconds later to return the entire message. Perhaps if imaptest sent first the APPEND command, then did a small pause and after that sent the message. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] 1.0(.14) vs 1.1.2 performance
On Aug 6, 2008, at 4:56 AM, Thomas Hummel wrote: On Tue, Aug 05, 2008 at 06:40:00PM -0400, Timo Sirainen wrote: Do you use POP3? Yes. I don't have the stats right now but I'd say, on 2500 users, 60% are using IMAP, 40% POP3. But I had the feeling that it was the IMAP processes which were causing the load, particulary because some IMAP users were complaining about low speed while moving messages from mailboxes (I'm talking 1.0.14 here). However, I don't know if it was a cause or a consequence... Well, one change is that by default copying messages is now done using hard links, but you could have done that with v1.0 also by changing a setting. So no big architectural changes ? Or maybe changes in the locking code ? Not really. What about the upcomming 2.0 ? Is the new master expected to provide load improvement ? No. It's mostly about making the master more modular. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Can't connect to IMAP
on 8-6-2008 7:18 AM David Hall spake the following: Pascal Volk skrev: Hi David, Am 06.08.2008 10:59 schrieb David Hall: … My problem since a few days back is that IMAP doesn't seem to be started. The logfiles says's everything is in order, but port 143 isn't up and Squirrelmail can't connect, i have no clue what's causing this everything runned smoothly a couple of days ago. Im using postfix/amavis spamassasin. Is Dovecot really running on your system? Please show the output from `ps -ef | grep dovecot` and `netstat -tlpn | egrep ':(143|993)`. How do you try to connect to the imapd? http://wiki.dovecot.org/TestInstallation Here's some information Dovecot v1.1.2 [output from `dovecot -n` snipped ] And once again. I don't get any errors in the logfiles. Mail.log last 5 lines after a restart … Aug 6 07:47:58 localhost postfix/virtual[32190]: C4FD1406024: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=virtual, delay=0.07, delays=0.03/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) … This Mail was delivered with Postfix's virtual transport, not with Dovecot's LDA http://wiki.dovecot.org/LDA/Postfix() Aug 6 10:55:56 localhost dovecot: Killed with signal 15 Aug 6 10:55:56 localhost dovecot: Dovecot v1.1.2 starting up Aug 6 10:55:57 localhost dovecot: auth-worker(default): mysql: Connected to localhost (postfix) Looks good. Regards, Pascal Problem solved. it was listen = and not listen = * that caused it. strange thing is that i haven't changed those lines. Did you recently upgrade from the 1.0 tree? That setting now has different defaults then the 1.0 branch -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
Quoting Charles Marcus [EMAIL PROTECTED]: rpms for centos available on atrpms.net Sadly not for Centos 3.x, only for Centos 4/5... :( Anyone know about Dovecot 1.1.x rpms for Centos/RHEL 3.x? -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
Re: [Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
On 8/6/2008, Eric Rostetter ([EMAIL PROTECTED]) wrote: Anyone know about Dovecot 1.1.x rpms for Centos/RHEL 3.x? I'd be more interested in upgrading the server to a reasonably recent version of the distro... OT This is one huge reason why I like gentoo so much. As long as I update it regularly, I never have to worry about a massive update that breaks everything. /OT -- Best regards, Charles
Re: [Dovecot] 1.0(.14) vs 1.1.2 performance
On Wed, Aug 06, 2008 at 10:30:09AM -0400, Timo Sirainen wrote: Well, one change is that by default copying messages is now done using hard links, but you could have done that with v1.0 also by changing a setting. Yes, that's what I did at the time I was running 1.0.14. -- Thomas Hummel | Institut Pasteur [EMAIL PROTECTED] | Pôle informatique - systèmes et réseau
Re: [Dovecot] expire-plugin: configuration dict-server
Hi Jens, Ive got the same problem with you. The expire plugin not work. Nothing happened even I delete email from a mail client. And the expire table on mysql never updated. Thanks, Dino Jens Meyer wrote: Hello Eric, thank you very much for your prompt and helpful reply! The connect seem to work fine now. Please allow me two additional questions: Is it correct that this database-table is only a caching-table which is empty at first and will be filled later? It is not necessary to adapt the SQL-statement to my user-configuration, is it?! Is it necessary to reference the foldernames with INBOX.Trash or only Trash? For Sieve I have to use INBOX.Trash. Actually nothing happens when trying the plugin with dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test. Thank you again, kind regards! Jens Eric Toczek schrieb: Jens Meyer wrote: Unfortunately I have problems with the dictionary: -- dovecot: Aug 05 13:30:25 Error: dict: Unknown dict module: db dovecot: Aug 05 13:30:25 Error: dict: Failed to initialize dictionary 'expire' Looking at the rpm it doesn't look like it has bdb support built in. But it sounds like you want to use Mysql so that's alright. Are there any further tipps how to use the expire-plugin with mysql-connection (i.e. database-scheme, SQL-Select)? You will need to setup your configuration like this: dovecot.conf: dict { ... expiredict = mysql:/opt/dovecot/etc/dovecot-dict-expire.conf ... } plugin { ... expire = Trash 7 Trash/* 7 Spam 3 Junk 3 expire_dict = proxy::expiredict ... } dovecot-dict-expire.conf: connect = host=host dbname=db user=username password=password table = expire select_field = timestamp where_field = path username_field = username Then you'll want to create the table like so: create table expire( username varchar(255) not null, path varchar(100) not null, timestamp integer, primary key (username, path))engine=innodb; That should work for you. Of course enter in your correct config location and your specific expire settings. -Eric
[Dovecot] Dovecot proxying results in too many open files
Hi, Some words about my Dovecot setup: - 10 dovecot servers - each server has some local mailboxes - each server has proxying enabled to seamlessly connect to another host if the mailbox is not local Running Dovecot 1.1.1 on FreeBSD 6.3-RELEASE-p3. First of all, local mailbox access is fine. Proxying works also as expected. Now for the actual problem: Shortly after startup, Dovecot starts throwing errors concerning connection which should be proxied. Here are some examples from the logs: Aug 6 15:49:10 dovecot: imap-login: socket() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: proxy(XYZ): connect(1.2.3.4, 143) failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: accept() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: socket() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: proxy(XYZ): connect(1.2.3.4, 143) failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: socket() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: proxy(XYZ): connect(1.2.3.4, 143) failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: socket() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: proxy(XYZ): connect(1.2.3.4, 143) failed: Too many open files Aug 6 15:49:11 dovecot: imap-login: socket() failed: Too many open files [..] Aug 6 16:00:05 dovecot: imap-login: accept() failed: Too many open files Aug 6 16:00:08 dovecot: imap-login: accept() failed: Too many open files Aug 6 16:00:11 dovecot: imap-login: accept() failed: Too many open files Aug 6 16:00:13 dovecot: imap-login: accept() failed: Too many open files As from the context it seems to be a file descriptor issue, as such I have done the following: - added a 'limits -e -n 32768 -U dovecot' to dovecot startup file to ensure it has enough FD's - additionally, I've checked my kernel file limits, however I always set it through loader and sysctl to be as large as 64k # sysctl -a |grep files kern.maxfiles: 65535 kern.maxfilesperproc: 32768 kern.openfiles: 1632 - also checked the limits of the dovecot user like this: # su -c dovecot root -c 'ulimit -a' core file size (blocks, -c) unlimited data seg size (kbytes, -d) 1048576 file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 32768 pipe size(512 bytes, -p) 1 stack size (kbytes, -s) 131072 cpu time (seconds, -t) unlimited max user processes (-u) 5547 virtual memory (kbytes, -v) unlimited - done some monitoring of file descriptor usage for the dovecot user, though somewhat inacurate, like this: while [ : ]; do date; fstat -u dovecot |wc -l; sleep 1; done this gave me these results while tailing the logfile: Wed Aug 6 15:44:12 CEST 2008 585 Wed Aug 6 15:44:13 CEST 2008 579 Wed Aug 6 15:44:14 CEST 2008 582 Wed Aug 6 15:44:15 CEST 2008 582 Wed Aug 6 15:44:16 CEST 2008 586 Wed Aug 6 15:44:17 CEST 2008 585 Wed Aug 6 15:44:18 CEST 2008 582 So it didn't seem to be anywhere near the theoretical upper limit I've set at 32k. On the other hand, when restarting Dovecot, it works for a few minutes for at least as long as the FD usage as reported above stays at around 500. I remember from the docs that dovecot-login would require the double amount of file descriptors to run. Assuming my report is somewhat inaccurate and lags behind, I could imagine that upon a proxy requests it would effectively peak our at some 500 x 2 FDs. Thus effectively reaching the 1024 FD barrier. I conclude this from the fact that I currently have some 350 - 450 logins in parallel, most of which can and shell be proxied. From the error message in the logs I got the impression, that only proxied connections are affected. I was not able to reproduce the issue with non-proxied logins to local mailboxes. Some further steps I've done from the configuration side to no avail: - disabled imaps/pop3s/ssl - changed between login_process_per_connection yes/no - played around with login_max_connections et all (raised/lowered) limits - tried with/without plugins enabled - tried with SQL-based and passwd-file based userdb/passdb, single and mixed Dovecot config: # dovecot -n # 1.1.1: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 listen: *, [::] ssl_disable: yes ssl_cert_file: /usr/local/etc/postfix/tls/server.crt ssl_key_file: /usr/local/etc/postfix/tls/server.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 16
Re: [Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
Quoting Charles Marcus [EMAIL PROTECTED]: On 8/6/2008, Eric Rostetter ([EMAIL PROTECTED]) wrote: Anyone know about Dovecot 1.1.x rpms for Centos/RHEL 3.x? I'd be more interested in upgrading the server to a reasonably recent version of the distro... Unfortunately, it isn't a redundant setup, so an upgrade is downtime. I've thought about doing an on-line (e.g., yum) upgrade from 3 to 4, but I'm not sure 4 would qualify as reasonably recent and it would still require a reboot, but this is an option and would get me the new dovecot rpms at least... Since there is no good way to do an on-line upgrade from CentOS/RHEL 3 to CentOS/RHEL 5, that isn't really an option at this time (too much downtime). I've also had machines that were hardware frozen at older OS versions... Though that is not the case in this instance (was for my print server I had to recently deal with). This is one huge reason why I like gentoo so much. It has nothing to do with gentoo, IMHO. As long as I update it regularly, I never have to worry about a massive update that breaks everything. Same can be said for most distros, but I can't afford the downtime of the constant upgrades which mean constant reboots... That is why people pick a enterprise solution like RHEL/CentOS, so they can have better uptime (with support) than a non-enterprise systems... I regularly have machines with 2 or 3 years of uptime before I need to reboot them for an upgrade (they are behind firewalls, in case you wonder how I get along on such old kernels). Obviously, RHEL/CentOS 3.x will end of life, and I'll need to upgrade eventually because of that, but the more I can put it off, then better... But sometimes you just need to bite the bullet, and that day may be close at hand for this server... Or, I can just roll my own RHEL/CentOS 3 rpm package also... :) Which is less work than an OS upgrade at least... Best regards, Charles -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
Re: [Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
On Aug 6, 2008, at 9:28 AM, Benoît DESLOGES wrote: Try 3: - Stop dovecot on SV2 - Clear all dovecot indexes on SV2 - Rsync of my mailbox - Edit mailbox and move X-UID header after the X-Keywords header The important change was that X-UID: came after X-IMAPbase: header. - Start dovecot on SV2 - Update pop setting in outlook and send/receive Result : = OK. Is that normal that dovecot is impacted by the position of the headers ? Maybe some improvement possible ? I did think about previously if it should work like this, but it seemed like a lot more extra work to support this kind of a situation properly and I thought it shouldn't happen normally anyway. I guess v0.99.x then wrote them in wrong order.. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot proxying results in too many open files
On Aug 6, 2008, at 10:29 AM, Gianpaolo Del Matto wrote: Aug 6 15:49:10 dovecot: imap-login: socket() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: proxy(XYZ): connect(1.2.3.4, 143) failed: Too many open files Login processes change the fd limits themselves, but looks like the value wasn't calculated correctly for SSL connections. This should help: http://hg.dovecot.org/dovecot-1.1/rev/ea6aea0a4cbb PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot proxying results in too many open files
Hi again, Here's some more information on the case. In the meanwhile I tried the same setup with Dovecot 1.1.2, still the same result As I saw in fstat on FreeBSD memory mapped files are ommited, so I did some further yet inaccurate monitoring with mmaped files included. while [ : ]; do date; fstat -m -u dovecot |wc -l; sleep 1; done Wed Aug 6 18:37:05 CEST 2008 918 Wed Aug 6 18:37:06 CEST 2008 923 Wed Aug 6 18:37:07 CEST 2008 917 Wed Aug 6 18:37:08 CEST 2008 911 Wed Aug 6 18:37:09 CEST 2008 912 Wed Aug 6 18:37:10 CEST 2008 914 Wed Aug 6 18:37:11 CEST 2008 913 Wed Aug 6 18:37:13 CEST 2008 912 Wed Aug 6 18:37:14 CEST 2008 911 Wed Aug 6 18:37:15 CEST 2008 909 Wed Aug 6 18:37:16 CEST 2008 912 Wed Aug 6 18:37:17 CEST 2008 910 So actually I am very close to the 1024 FD barrier, so the question remains, if Dovecot inherits FD_SETSIZE from libc and if this might be the cause of the whole trouble. During testing I did also a build of both 1.1.1 and 1.1.2 without SSL and mysql libraries, so basically just plain Dovecout without anything, though that made no difference at all. Greetings, Gianpaolo
Re: [Dovecot] expire-plugin: configuration dict-server
* Eric Toczek, 2008-08-06 11:39 Thomas Zajic wrote: Hi, Same problem here - dovecot never adds any records to the expire table, although the database connection is fine. All it ever does is query for existing records when a message gets moved to Trash or Junk, so at least that part is working. Do you use namespaces? Since Timo just discovered they may not be working with expire properly. Looking at the code it looks like the expire plugin ignores the namespace prefix but expire-tool requires it, so it probably won't work.. No, I'm not using namespaces, or at least not intentionally. Here's the output of 'dovecot -n' and other possibly relevant stuff: [EMAIL PROTECTED]:~# dovecot -n # 1.1.2: /usr/local/etc/dovecot.conf login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes mail_max_userip_connections: 20 verbose_proctitle: yes mail_location: maildir:/home/%u/Maildir:INBOX=/home/%u/Maildir/.INBOX fsync_disable: yes mail_plugins: expire fts fts_squat auth default: mechanisms: plain digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd socket: type: listen master: path: /usr/local/var/run/dovecot/auth-master mode: 384 plugin: expire: Trash 30 Junk 60 expire_dict: proxy::expire fts: squat fts_squat: partial=4 full=6 dict: expire: mysql:/usr/local/etc/dovecot-sql-expire.conf [EMAIL PROTECTED]:~# cat /usr/local/etc/dovecot-sql-expire.conf driver = mysql connect = host=/var/run/mysql/mysql.sock user=XXX password=YYY dbname=dovecot table = expire select_field = when where_field = path username_field = username [EMAIL PROTECTED]:~# mysql -p dovecot Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 900 Server version: 5.0.51 Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql describe expire; +--+--+--+-+-+---+ | Field| Type | Null | Key | Default | Extra | +--+--+--+-+-+---+ | username | varchar(64) | NO | PRI | NULL| | | path | varchar(255) | NO | PRI | NULL| | | when | varchar(64) | NO | | NULL| | +--+--+--+-+-+---+ [EMAIL PROTECTED]:~# Do you see any obvious errors and/or problems? Thanks, Thomas
Re: [Dovecot] Dovecot 1.1.1 + zlib plugin + mbox crash
Chris Wakelin wrote: Oh, unless there are some bugs in your zlib version, such as related to seeking.. Could be, I imagine it's as prehistoric as the bzlib :) Right, I've tried dovecot-1.1.2 using my own zlib-1.2.3 (and bzlib-1.0.5) build on Solaris 8: ldd lib20_zlib_plugin.so gives libz.so = /opt/RDGzlib/lib/libz.so libbz2.so = /opt/RDGbzlib/lib/libbz2.so ... and get the same problems. I've been testing zlib again in Dovecot 1.1.1 (plus assert-crash fix) and 1.1.2 and I'm beginning to think it may be some sort of race condition (the Solaris 8 box is significantly slower than the SuSE one!). If I leave a few seconds pause between the FETCH uid BODY[] commands, it seems not to crash, even with the same sequence. Mind you, I wouldn't have expected to be able to type quickly enough to cause problems! Is that plausible? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, [EMAIL PROTECTED] IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Re: [Dovecot] Server update strategies (was: Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.0 7 = Improvement possible)
Hi, it's always interesting to observe and discuss the different update strategies (although not entirely on-topic)... On Wed, 06 Aug 2008 11:25:59 -0500, Eric Rostetter [EMAIL PROTECTED] wrote: Quoting Charles Marcus [EMAIL PROTECTED]: On 8/6/2008, Eric Rostetter ([EMAIL PROTECTED]) wrote: Anyone know about Dovecot 1.1.x rpms for Centos/RHEL 3.x? I'd be more interested in upgrading the server to a reasonably recent version of the distro... Unfortunately, it isn't a redundant setup, so an upgrade is downtime. I've thought about doing an on-line (e.g., yum) upgrade from 3 to 4, but I'm not sure 4 would qualify as reasonably recent and it would still require a reboot, but this is an option and would get me the new dovecot rpms at least... Since there is no good way to do an on-line upgrade from CentOS/RHEL 3 to CentOS/RHEL 5, that isn't really an option at this time (too much downtime). How can such an important system be a non-redundant setup? Hardware breakage (or a cracker, see below) would cause minutes or probably even hours of downtime... I've also had machines that were hardware frozen at older OS versions... Though that is not the case in this instance (was for my print server I had to recently deal with). This is one huge reason why I like gentoo so much. It has nothing to do with gentoo, IMHO. It has in that way, that there are no releases, no big jumps with lots of breakage and config file syntax changes... But I definitely wouldn't say Gentoo is a good distribution for systems that need to be highly available. (I'm using Gentoo myself on desktops and servers, but none of them do run really critical stuff). As long as I update it regularly, I never have to worry about a massive update that breaks everything. Same can be said for most distros, but I can't afford the downtime of the constant upgrades which mean constant reboots... That is why people pick a enterprise solution like RHEL/CentOS, so they can have better uptime (with support) than a non-enterprise systems... Enterprise system - surely sounds professional and all ;) But not rebooting (during scheduled maintenance on a time of week/day where the least clients will be affected) for a new kernel that fixes a critical security issue definitely does not. IMHO. I regularly have machines with 2 or 3 years of uptime before I need to reboot them for an upgrade (they are behind firewalls, in case you wonder how I get along on such old kernels). Maybe you should upgrade your security knowledge along with your kernels ;) Many (if not most) attacks come from the inside (e.g. via trojans/viruses/rootkits on client (laptop) computers). Thus, the concept of something being secure because behind firewalls is at least partly obsolete. Obviously, RHEL/CentOS 3.x will end of life, and I'll need to upgrade eventually because of that, but the more I can put it off, then better... But sometimes you just need to bite the bullet, and that day may be close at hand for this server... Build it with redundancy this time. At least software-wise (for example using virtualisation), so that you have a test system on which you can simulate a pending update before you roll it out on the production system. Patrick. -- STAR Software (Shanghai) Co., Ltd.http://www.star-group.net/ Phone:+86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005
[Dovecot] Dovecot auto vacation with sieve doesn't work
Guys, I'm running out of hair to pull out ;). Can anyone out there say that this does work?? To me this is looking like a bug and I'm not sure whether it's the sieve plugin or the dovecot deliver program. I have also had no luck the the reject sending any reply back to the sender. My setup: OS: Solaris 10 sparc platform postfix: 2.5.2 dovecot: 1.1.2 sieve plugin: 1.1.5 I'm going back forth between procmail and sieve and having no luck. procmail will send the reply to the sender but doesn't deliver the message to the recipient. Sieve will deliver the message to the recipient but doesn't send the reply to the sender. Now if I can just combine the two, I'll be in business. Postfix mail command: mailbox_command = /userM/mail-services/dovecot/libexec/dovecot/deliver -d $USER* * Dovecot -n (I've made some changes from my previous posting namely with the master_auth settings) # 1.1.2: /userM/mail-services/dovecot/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /userM/mail-services/dovecot/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /userM/mail-services/dovecot/var/run/dovecot/login login_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3-login login_greeting: Cyrus ready. login_max_processes_count: 1024 max_mail_processes: 1024 mail_location: mbox:~/:INBOX=/userM/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_index: yes mail_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /userM/mail-services/dovecot/lib/dovecot/pop3 auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /userM/mail-services/postfix/var/private/auth mode: 432 user: postfix group: postfix master: path: /userM/mail-services/dovecot/var/run/dovecot/auth-master mode: 384 user: postfix group: postfix My .dovecot.sieve file: require [vacation]; if header :matches subject * { vacation :days 30 :addresses [EMAIL PROTECTED] :subject Automatic response to: ${1} I'm away -- send mail to foo in my absence; } I made some modifications to the vacation reply base on the following URL: http://ietfreport.isoc.org/idref/draft-ietf-sieve-vacation/ In my testing I know the sieve plugin is reading my .dovecot.sieve script and creating the .dovecot.sievec, but that is as for as it goes. The .dovecot.lda-dupes file is not being created (or any .dovecot.sieve.err file) and no reply is even being attempted from the logs: Aug 6 11:30:51 mail2.engr.colostate.edu dovecot: [ID 107833 mail.info] auth(def ault): new auth connection: pid=27187 Aug 6 11:30:51 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] connect from akron.colostate.edu[129.82.103.160] Aug 6 11:30:51 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] setting up TLS connection from akron.colostate.edu[129.82.103.160] Aug 6 11:30:51 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] Anonymous TLS connection established from akron.colostate.edu[129.82.103.16 0]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits) Aug 6 11:30:52 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] 16E2059984: client=akron.colostate.edu[129.82.103.160] Aug 6 11:30:52 mail2.engr.colostate.edu postfix/cleanup[27192]: [ID 197553 mail .info] 16E2059984: message-id=[EMAIL PROTECTED] .engr.colostate.edu Aug 6 11:30:52 mail2.engr.colostate.edu postfix/smtpd[27187]: [ID 197553 mail.i nfo] disconnect from akron.colostate.edu[129.82.103.160] Aug 6 11:30:52 mail2.engr.colostate.edu postfix/qmgr[18021]: [ID 197553 mail.in fo] 16E2059984: from=[EMAIL PROTECTED], size=1877, nrcpt=1 (queue act ive) Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 315030 mail.info] Lo ading modules from directory: /userM/mail-services/dovecot/lib/dovecot/lda Aug 6 11:30:52 mail2.engr.colostate.edu deliver(cjay): [ID 619685 mail.info] Mo dule loaded:
Re: [Dovecot] Dovecot auto vacation with sieve doesn't work
On Aug 6, 2008, at 1:57 PM, CJ Keist wrote: My .dovecot.sieve file: require [vacation]; if header :matches subject * { vacation :days 30 :addresses [EMAIL PROTECTED] :subject Automatic response to: ${1} I'm away -- send mail to foo in my absence; } You can't use ${1} since variables extension isn't supported by cmusieve. In my testing I know the sieve plugin is reading my .dovecot.sieve script and creating the .dovecot.sievec, but that is as for as it goes. The .dovecot.lda-dupes file is not being created (or any .dovecot.sieve.err file) and no reply is even being attempted from the logs: Then it means that Dovecot decided it shouldn't reply to the mail. There are several reasons for that listed in http://wiki.dovecot.org/LDA/Sieve (would be nice if it logged the exact reason though - hopefully the Sieve rewrite will do that :) PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot proxying results in too many open files
Hello Timo Well, that was fast indeed. Thank you! I applied the patch to 1.1.2 and recompiled it, so far it did not happen within the last 30 minutes. I will let you know what it looks like in a day or two. Am 06.08.2008 um 18:55 schrieb Timo Sirainen: On Aug 6, 2008, at 10:29 AM, Gianpaolo Del Matto wrote: Aug 6 15:49:10 dovecot: imap-login: socket() failed: Too many open files Aug 6 15:49:10 dovecot: imap-login: proxy(XYZ): connect(1.2.3.4, 143) failed: Too many open files Login processes change the fd limits themselves, but looks like the value wasn't calculated correctly for SSL connections. This should help: http://hg.dovecot.org/dovecot-1.1/rev/ea6aea0a4cbb Greetings, Gianpaolo
Re: [Dovecot] Dovecot PAM sessions with Maildir
On Aug 6, 2008, at 2:03 PM, Sean Smitz wrote: I am configuring a new mail server on RHEL 5 x64. I have configured dovecot as follows: ... protocols = imaps ... ssl_cert_file = /etc/pki/dovecot/certs/mailserver.cer ssl_key_file = /etc/pki/dovecot/private/mailserver.pem ... login_process_size = 64 ... mail_location = maildir:~/Maildir ... passdb pam { args = session=yes cache_key=%u%s dovecot } ... I'm getting the following error messages in /var/log/maillog: Aug 5 20:57:45 [hostname] dovecot: imap-login: Aborted login: rip=:::128.8.244.15, lip=:::[server], TLS Aug 5 21:01:34 [hostname] dovecot: imap-login: Aborted login: user=[me], method=PLAIN, rip=:::[server], lip=:::[server], TLS You could see if auth_debug=yes shows more. Although debugging PAM problems is annoying because PAM's logging is so bad. I find the message in the audit.log interesting because I configured the connection with SSL not TLS, but if I use TLS the result is the same. I think you're confusing SSL and TLS with imaps port and STARTTLS command (and so do many client UIs..). You're going to be using TLS connections in any case. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot auto vacation with sieve doesn't work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo, I removed the ${1} variable but still no luck. I read the reasons why deliver would not send a reply but I don't think any should be true. Below is the header of one of the messages, let me know if you see something that is causing sieve not to send the reply. - From [EMAIL PROTECTED] Wed Aug 06 12:59:28 2008 Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from bird.ACNS.ColoState.EDU (bird.acns.colostate.edu [129.82.100.165] ) by mail2.engr.colostate.edu (Postfix) with ESMTPS id 0D01C59984 for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:27 -0600 (MDT) Received: from parker.ACNS.ColoState.EDU (parker.colostate.edu [129.82.103.125]) by bird.ACNS.ColoState.EDU (8.12.11.20060308/8.12.11) with ESMTP id m76I xJDX014096 for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:19 -0600 Received: from goku.engr.colostate.edu (goku.engr.colostate.edu [129.82.224.16]) by parker.ACNS.ColoState.EDU (AIX5.3/8.13.4/8.11.0) with ESMTP id m76IxJ wC909674 for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:19 -0600 Received: from webmail.engr.colostate.edu (sunbeam.engr.colostate.edu [129.82.22 4.8]) by goku.engr.colostate.edu (Postfix) with ESMTP id 23AE126AAF for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:20 -0600 (MDT) Received: from 129.82.224.6 (SquirrelMail authenticated user joeblow) by webmail.engr.colostate.edu with HTTP; Wed, 6 Aug 2008 12:59:19 -0600 (MDT) Message-ID: [EMAIL PROTECTED] u Date: Wed, 6 Aug 2008 12:59:19 -0600 (MDT) Subject: test 9 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7160:2.4.4,1.2.40,4.0.166 definitions=2008-08-06_05:2008-08-05,2008-08-06,2008-08-06 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipsco re=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx e ngine=5.0.0-080509 definitions=main-0808060075 X-UID: 33 Status: RO X-Keywords: Content-Length: 33 Timo Sirainen wrote: On Aug 6, 2008, at 1:57 PM, CJ Keist wrote: My .dovecot.sieve file: require [vacation]; if header :matches subject * { vacation :days 30 :addresses [EMAIL PROTECTED] :subject Automatic response to: ${1} I'm away -- send mail to foo in my absence; } You can't use ${1} since variables extension isn't supported by cmusieve. In my testing I know the sieve plugin is reading my .dovecot.sieve script and creating the .dovecot.sievec, but that is as for as it goes. The .dovecot.lda-dupes file is not being created (or any .dovecot.sieve.err file) and no reply is even being attempted from the logs: Then it means that Dovecot decided it shouldn't reply to the mail. There are several reasons for that listed in http://wiki.dovecot.org/LDA/Sieve (would be nice if it logged the exact reason though - hopefully the Sieve rewrite will do that :) - -- C. J. Keist Email: [EMAIL PROTECTED] UNIX/Network ManagerPhone: 970-491-0630 Engineering Network ServicesFax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFImfl8A29OFr7C6jcRAsXVAKCJ64/SNiwVO6COtJpE0p53bzQhTACgjDYz Y4zRsKKYCKQEUYXUDvhq18w= =HpD2 -END PGP SIGNATURE-
[Dovecot] Maildir Index Question
We have several hundred mailboxes that have thousands of files in them (spam boxes) We currently run a find command and remove the files that are over 7 days old but still have boxes with upto 60k messages in them. I know that dovecot will update the index files for each mailbox when the boxes is accessed by an IMAP client(Webmail using Squirrel)but that can take quite a while to index. What I would like to do is via a cron job after the old file remove is to force dovecot to reindex these boxes. That way when the users login to the webmail interface it is quicker. Does anyone know if a script is available to do this? Thanks Ron Culler
Re: [Dovecot] Maildir Index Question
On Aug 6, 2008, at 3:44 PM, Ron Culler wrote: We currently run a find command and remove the files that are over 7 days old but still have boxes with upto 60k messages in them. With v1.1 you could use expire plugin. http://wiki.dovecot.org/Plugins/Expire I know that dovecot will update the index files for each mailbox when the boxes is accessed by an IMAP client(Webmail using Squirrel)but that can take quite a while to index. What I would like to do is via a cron job after the old file remove is to force dovecot to reindex these boxes. That way when the users login to the webmail interface it is quicker. Are you sure the slowdown is because of deleting messages? The syncing after that should be about instantaneous even for huge mailboxes. Or could the problem be for example that the messages' headers (etc) just haven't been indexed for the mailbox and it takes a while to do that when the mailbox is opened? PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot PAM sessions with Maildir
I able to connect to the mail server with a MUA (Thunderbird) via SSL prior to attempting to set up the session and Maildir options /var/log/audit/audit.log type=USER_AUTH msg=audit(1217992493.198:389): user pid=8022 uid=0 auid=10243 subj=user_u:system_r:dovecot_auth_t:s0 msg='PAM: authentication acct=[me] : exe=/usr/libexec/dovecot/dovecot-auth (hostname=:::[client], addr=:::[client], terminal=dovecot res=success)' type=USER_ACCT msg=audit(1217992493.199:390): user pid=8022 uid=0 auid=10243 subj=user_u:system_r:dovecot_auth_t:s0 msg='PAM: accounting acct=[me] : exe=/usr/libexec/dovecot/dovecot-auth (hostname=:::[client], addr=:::[client], terminal=dovecot res=success)' type=USER_START msg=audit(1217992493.199:391): user pid=8022 uid=0 auid=10243 subj=user_u:system_r:dovecot_auth_t:s0 msg='PAM: session open acct=[me] : exe=/usr/libexec/dovecot/dovecot-auth (hostname=:::[client], addr=:::[client], terminal=dovecot res=failed)' /var/log/maillog Aug 5 23:14:37 mailserv1 dovecot: Dovecot v1.0.7 starting up Aug 5 23:14:38 mailserv1 dovecot: auth(default): new auth connection: pid=8014 Aug 5 23:14:38 mailserv1 dovecot: auth(default): new auth connection: pid=8013 Aug 5 23:14:38 mailserv1 dovecot: auth(default): new auth connection: pid=8015 Aug 5 23:14:46 mailserv1 dovecot: auth(default): new auth connection: pid=8016 Aug 5 23:14:52 mailserv1 dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAPsecured lip=:::[server] rip=:::[client] Aug 5 23:14:52 mailserv1 dovecot: auth(default): client out: CONT 1 Aug 5 23:14:52 mailserv1 dovecot: auth(default): client in: CONThidden Aug 5 23:14:52 mailserv1 dovecot: auth(default): pam([me],:::[client]): lookup service=dovecot Aug 5 23:14:52 mailserv1 dovecot: auth(default): pam([me],:::[client]): pam_open_session() failed: Cannot make/remove an entry for the specified session Aug 5 23:14:53 mailserv1 dovecot: auth(default): client out: FAIL 1 user=[me] Aug 5 23:14:53 mailserv1 dovecot: auth(default): client in: AUTH 2 PLAIN service=IMAPsecured lip=:::[server] rip=:::[client] resp=hidden Aug 5 23:14:53 mailserv1 dovecot: auth(default): pam([me],:::[client]): lookup service=dovecot Aug 5 23:14:53 mailserv1 dovecot: auth(default): pam([me],:::[client]): pam_open_session() failed: Cannot make/remove an entry for the specified session Aug 5 23:14:55 mailserv1 dovecot: auth(default): client out: FAIL 2 user=[me] Aug 5 23:14:58 mailserv1 dovecot: imap-login: Aborted login: user=[me], method=PLAIN, rip=:::[client], lip=:::[server], TLS
Re: [Dovecot] Dovecot PAM sessions with Maildir
On Aug 6, 2008, at 4:15 PM, Sean Smitz wrote: I able to connect to the mail server with a MUA (Thunderbird) via SSL prior to attempting to set up the session and Maildir options .. Aug 5 23:14:53 mailserv1 dovecot: auth(default): pam([me],::: [client]): pam_open_session() failed: Cannot make/remove an entry for the specified session Why do you need to open the session? That's clearly the reason why it's failing. But I've no idea why, and I doubt there's anything on Dovecot's side you can do to fix it (other than disabling the session=yes of course). PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Experience moving mailboxes from Dovecot 0.99.14 to Dovecot 1.07 = Improvement possible
Hi, On Wed, Aug 06, 2008 at 10:55:08AM -0500, Eric Rostetter wrote: Quoting Charles Marcus [EMAIL PROTECTED]: rpms for centos available on atrpms.net Sadly not for Centos 3.x, only for Centos 4/5... :( Anyone know about Dovecot 1.1.x rpms for Centos/RHEL 3.x? You could try to rebuild from ATrpms' src.rpm, but to spare some trouble this is what I had with 1.1.rc4 4 months ago: checking for auth_userokay... no checking for krb5-config... YES configure: error: Can't build with GSSAPI support: v1.2 library not supported Maybe one could patch the specfile/package up to support RHEL3, and if you want to you could maintain this at ATrpms. -- Axel.Thimm at ATrpms.net pgpYJlsQIeRAS.pgp Description: PGP signature
Re: [Dovecot] Dovecot auto vacation with sieve doesn't work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, Trying to do some debugging of the sieve code. So I have found that it is failing on sending the reply in the following code area: bc_eval.c Line: 324 /* ok, we're willing to respond to the sender. but is this message to me? that is, is my address in the [Resent]-To, [Resent]-Cc or [Resent]-Bcc fields? */ But I haven't pin-pointed yet why it's not seeing the message as being for me?? CJ Keist wrote: Timo, I removed the ${1} variable but still no luck. I read the reasons why deliver would not send a reply but I don't think any should be true. Below is the header of one of the messages, let me know if you see something that is causing sieve not to send the reply. - From [EMAIL PROTECTED] Wed Aug 06 12:59:28 2008 Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from bird.ACNS.ColoState.EDU (bird.acns.colostate.edu [129.82.100.165] ) by mail2.engr.colostate.edu (Postfix) with ESMTPS id 0D01C59984 for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:27 -0600 (MDT) Received: from parker.ACNS.ColoState.EDU (parker.colostate.edu [129.82.103.125]) by bird.ACNS.ColoState.EDU (8.12.11.20060308/8.12.11) with ESMTP id m76I xJDX014096 for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:19 -0600 Received: from goku.engr.colostate.edu (goku.engr.colostate.edu [129.82.224.16]) by parker.ACNS.ColoState.EDU (AIX5.3/8.13.4/8.11.0) with ESMTP id m76IxJ wC909674 for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:19 -0600 Received: from webmail.engr.colostate.edu (sunbeam.engr.colostate.edu [129.82.22 4.8]) by goku.engr.colostate.edu (Postfix) with ESMTP id 23AE126AAF for [EMAIL PROTECTED]; Wed, 6 Aug 2008 12:59:20 -0600 (MDT) Received: from 129.82.224.6 (SquirrelMail authenticated user joeblow) by webmail.engr.colostate.edu with HTTP; Wed, 6 Aug 2008 12:59:19 -0600 (MDT) Message-ID: [EMAIL PROTECTED] u Date: Wed, 6 Aug 2008 12:59:19 -0600 (MDT) Subject: test 9 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7160:2.4.4,1.2.40,4.0.166 definitions=2008-08-06_05:2008-08-05,2008-08-06,2008-08-06 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipsco re=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx e ngine=5.0.0-080509 definitions=main-0808060075 X-UID: 33 Status: RO X-Keywords: Content-Length: 33 Timo Sirainen wrote: On Aug 6, 2008, at 1:57 PM, CJ Keist wrote: My .dovecot.sieve file: require [vacation]; if header :matches subject * { vacation :days 30 :addresses [EMAIL PROTECTED] :subject Automatic response to: ${1} I'm away -- send mail to foo in my absence; } You can't use ${1} since variables extension isn't supported by cmusieve. In my testing I know the sieve plugin is reading my .dovecot.sieve script and creating the .dovecot.sievec, but that is as for as it goes. The .dovecot.lda-dupes file is not being created (or any .dovecot.sieve.err file) and no reply is even being attempted from the logs: Then it means that Dovecot decided it shouldn't reply to the mail. There are several reasons for that listed in http://wiki.dovecot.org/LDA/Sieve (would be nice if it logged the exact reason though - hopefully the Sieve rewrite will do that :) - -- C. J. Keist Email: [EMAIL PROTECTED] UNIX/Network ManagerPhone: 970-491-0630 Engineering Network ServicesFax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFImi3AA29OFr7C6jcRAqOuAJ9N5dVnDxA7PU5A66i/A4OAgrl04gCeLCKj cA/+AxmAB7I+vDtj7tqhl1A= =Whfo -END PGP SIGNATURE-
[Dovecot] Unlimited quota in 1.1?
How do I set an unlimited quota for a user in 1.1? Setting it to 0 bytes worked in 1.0, but doesn't seem to work in 1.1 :-( david
Re: [Dovecot] Unlimited quota in 1.1?
David Reid [EMAIL PROTECTED] wrote: How do I set an unlimited quota for a user in 1.1? Setting it to 0 bytes worked in 1.0, but doesn't seem to work in 1.1 :-( http://wiki.dovecot.org/Quota/1.1 -- Sahil Tandon [EMAIL PROTECTED]
[Dovecot] Purpose of files under .imap
I've got a user with an unusable account. Tbird just sits in a loop endlessly logging in over and over when a particular folder is selected. What files under .imap associated with that folder can be safely deleted? What's stored in all of them? I see all of these: .customflags dovecot.index dovecot.index.cache dovecot.index.log .imap.index .imap.index.data .imap.index.log .imap.index.tree
Re: [Dovecot] Purpose of files under .imap
On Aug 6, 2008, at 9:53 PM, Kenneth Porter wrote: I've got a user with an unusable account. Tbird just sits in a loop endlessly logging in over and over when a particular folder is selected. What files under .imap associated with that folder can be safely deleted? What's stored in all of them? What Dovecot version? What do you see in Dovecot's logs? Instead of deleting move the files so that if it's a new bug that I haven't fixed I could take a look at the indexes to see if I can get it fixed. I see all of these: .customflags v0.99-only, delete. dovecot.index dovecot.index.cache dovecot.index.log All of these are safe to delete. .imap.index .imap.index.data .imap.index.log .imap.index.tree These are v0.99-only, delete. So I guess you're using mbox? There it's safe to delete everything. If you're using maildir you should keep dovecot-uidlist and dovecot- keywords. PGP.sig Description: This is a digitally signed message part
[Dovecot] Next message unexpectedly lost
Using 1.1.2. I'm getting the above message over and over in the error log. Dovecot drops the connection and the client (Tbird) just keeps retrying in an endless loop. Using Wireshark to sniff the exchange, it looks like the command that fails looks like this: 5 UID fetch 1:9749,9751:9763,9765:9930,9932,9934:9942 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)]) Dovecot seems to be shutting down after receiving this. Mulberry doesn't seem to have the problem, presumably because it's sending a different command sequence that doesn't stroke this. Here's the failing code, in i_stream_raw_mbox_read : if (stream-istream.v_offset - rstream-hdr_offset + new_pos rstream-mail_size) { /* istream_raw_mbox_set_next_offset() used invalid cached next_offset? */ i_error(Next message unexpectedly lost from %PRIuUOFF_T, rstream-hdr_offset + rstream-mail_size); rstream-eof = TRUE; rstream-corrupted = TRUE; return -1; } I've tried deleting the associated .imap/folder contents but it must regenerate the same bad data as it happens again.