- dovecot - dovecot.org

[Dovecot] Dovecot discards mail over quota
by Gary V 27 Jan '09

27 Jan '09

I'm new to Dovecot, using 1.1.8 and I just wanted to verify that what I am observing is the intended behavior. I'm using Maildir++ quota. When a message is delivered to a mailbox that cannot accept the message because it would place them over the quota limit, deliver states to the MTA that the messsage was delivered successfully (example using postfix): Jan 17 12:05:31 msa postfix/pipe[13983]: 088C5B9D47: to=<test(a)example.com>, relay=dovecot, delay=0.72, delays=0.34/0.02/0/0.36, dsn=2.0.0, status=sent (delivered via dovecot service) But in actuality the mail is discarded (dropped). Then a bounce is created stating the mail was rejected: Your message to <test(a)example.com> was automatically rejected: Quota exceeded (mailbox for user is full). Question: is it possible (without changing code) to alter this to where deliver would instead tempfail or something. Somehow it seems wrong to me to tell the MTA that everything is good, and then silently discard messages - regardless of the fact dovecot creates a bounce. This is not necessarily ideal either, but I _am_ wondering if this is configurable or not. deliver(test(a)example.com): 2009-01-17 12:05:31 Info: msgid=<1293474859.20090117120812(a)example.com>: save failed to INBOX: Quota exceeded (mailbox for user is full) deliver(test(a)example.com): 2009-01-17 12:05:31 Info: sieve runtime error: Keep: Generic Error deliver(test(a)example.com): 2009-01-17 12:05:31 Error: sieve_execute_bytecode(/var/sieve/global.sievec) failed deliver(test(a)example.com): 2009-01-17 12:05:31 Info: msgid=<1293474859.20090117120812(a)example.com>: rejected: Quota exceeded (mailbox for user is full) deliver(garyv(a)example.com): 2009-01-17 12:05:31 Info: msgid=<dovecot-1232219131-401523-0@msa>: saved mail to INBOX -- Gary V

12 29

[Dovecot] behavior of dovecot with Openldap
by Masaharu Kawada 27 Jan '09

27 Jan '09

Dear team, I'm sorry if this is a stupid question, but I'd like to know the behavior of dovecot in a particular stuation. My questions are as follows. In /etc/dovecot-ldap.conf, 'hosts=' field is the one which can be used to specify availabled ldap server to access from the clients to authorize. And also sevral ldap servers can be specified in 'hosts =' field as shown like below. hosts = ldap-server1.example.com ldap-server2.example.com ※both server have the same configuration and available to replication ldap-server1(master) to ldap-server2(slave). If this is right, how does dovecot know which ldap server is currently used? and if the master dies, how does dovecot know and switch to slave one? In addition, which one is the exact behavior of dovecot in case master server dies? 1. only swithcing to the slave server 2. switching to the slave server, and once the master server is reactive then switch back to the master server automatically OS：RHEL4 U3 kernel 2.6.9-34.ELsmp openldap-2.2.13-12.el4 Thanks in advance, Masaharu Kawada ------------------- 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

5 11

[Dovecot] FOLDER INTERNAL DATA (uw pine header)
by Charles Gregory 26 Jan '09

26 Jan '09

Hello! I run Dovecot on CentOS 4 (dovecot-1.1.4-0_81.el4), and I *also* run the "Alpine" mail system that comes with that OS. Alpine still writes out the 'FOLDER INTERNAL DATA' pseudo-message at the beginning of each user's mbox, but dovecot does not. I make use of that record as a simle/quick way to verify when a user actually last read their e-mail (for administrative purposes, identifying stale/unused accounts), so is there any way to configure/command dovecot to write (or update) these hidden messages? (Note: I tried looking in the archives, but most references seemed to be about this message being a 'side effect' of transferring *from* UW IMAP, and how to get 'rid' of it. Not what I need. :) Apologies if this was covered before in a different thread.) - Charles

2 6

[Dovecot] uint_cmp bug
by Mike Abbott 26 Jan '09

26 Jan '09

In reviewing the differences between 1.1.8 and 1.1.9 I saw a probable bug in the new function uint_cmp() in src/lib-storage/index/maildir/ maildir-sync-index.c: if (*i1 < *i2) return -1; else if (*i1 > *i2) return -1; else return 0; The second case should return 1 not -1.

2 1

[Dovecot] Released ManageSieve v0.10.5 for Dovecot v1.1.9
by Stephan Bosch 26 Jan '09

26 Jan '09

Hello Dovecot users, Because there was a crash bug in the ManageSieve v0.10.4 login daemon, I made a new release of the ManageSieve service for Dovecot v1.1. This release includes two other small fixes as well. Changelog v0.10.5: - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed maximum permissions for uploaded scripts; was 0777. This was shielded however by the default umask (not documented to be configurable), so the actual permissions would never have been 0777. - Fixed handling of ~/ in use of mail-data for script location The following files are released: ManageSieve package: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.5.tar.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.5.tar.gz.s… ManageSieve patch: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.9-managesieve-0.10.5.diff.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.9-managesieve-0.10.5.diff.g… Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

1 0

Re: [Dovecot] troubles with 1.1.8 and squirrelmail over HTTPS
by Frank Bonnet 26 Jan '09

26 Jan '09

Hello Jack Setting up imapproxy on a third machine greatly improve performances on my mailhub which doesn't refuse connexions anymore. Thanks a lot for your help ! Frank Jack Stewart wrote: > > > Frank Bonnet wrote: >> Timo Sirainen wrote: >>> On Thu, 2009-01-15 at 16:25 +0100, Frank Bonnet wrote: >>>> I had to increase the max_mail_processes to 8192 >>>> to have a functionnal IMAP server with normal clients AND >>>> squirrelmail clients >>>> >>>> 8192 sounds enormous to me , any infos welcome ! >>> >>> How many imap processes have you running typically? >>> >> > > Hi, > > I don't know if this will help or not - I'm taking my comments offline > because it isn't clear if they are related to your core problem. Also, > they seem to be specific to high usage servers/people. > > We're not 1.1.8 yet but I've spent a reasonable amount of time tweaking > the Linux side. > > We run at about ~1300 processes per server. > > Squirrelmail does a login/logout on every single page that is clicked. > So I've found that running an imap proxy (such as the one at > imapproxy.org really helps). It creates some additional connections but > they get re-used pretty frequently. > > If 1.1.8 isn't logging out quickly, or not cleanly shutting down the > connection, or something similar, that could explain additional > connections. What does netstat -an show? On some O/S's the process will > disappear from ps but not be fully released until the socket/connection > disappears (in this case tcp). If you have a bunch of WAIT/FIN_WAIT's > something like this seems pretty likely. > > I've found that going through localhost allows you to bypass TLS while > still enforcing TLS for non-localhost connections. It's pretty nice for > overhead/connect speed. Also, an imap proxy may need a non-encrypted > connection. > > Besides the dovecot max_ ... settings, in our system you need to tweak > limits.conf and bump up the limits via the ulimit command in the dovecot > init script. Open file descriptors and process limits seem to be the > main settings. > > After this, you get into kernel tuning such as inotify settings. > > Let me know if you have any questions. If some of this helps, we might > want to feed it back into the list. > > ---Jack > >

1 0

[Dovecot] help writeing rule for preventin spam
by Sophia Alikhani 26 Jan '09

26 Jan '09

I used dovecot-1.1.7 + qmail-jms1-7+ vpopmail + ... everyday , everyuser has many spams from his/her mail to his/her for example in Bulk folder there are many spam e-mails that the sender is ourselves (from mymail@mydomain to myself@mydomain) how can i prevent these types of spam -- with regards Sophia Alikhani WorkPhone: +98-21-8497057 Mobile : +98-912-3361036

3 2

[Dovecot] dovecot 1.2 latest copy delete etc perfomance slowed down extremly works partly
by Robert Schetterer 26 Jan '09

26 Jan '09

Hi Timo, with dovecot 1.2 copy delete etc imap funktions get slow down extremly log shows that the copy command is done right but takes extremly log to perform sometimes goes into timeout --log dovecot: Jan 20 15:48:48 Info: IMAP(huber(a)schetterer.com): copy: uid=5, box=Drafts, dest=Trash, msgid=<20090120140432.516062360C0(a)master.schetterer.com>, size=748 dovecot: Jan 20 15:48:48 Info: auth(default): new auth connection: pid=28816 Timeout leak: 0x80a9720 --- after restart dovecot the imap function i.e. delete is done and deleted mails are shown up in i.e the trash folder any idea whats happening after the last patcheswhich might be envolved? any hint to get more info out of the logs for debug ? client was latest thunderbird stable -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 4

[Dovecot] userdb didn't return a home directory with v1.1.7
by Ivars Strazdiņš 26 Jan '09

26 Jan '09

Hi all, I am running Dovecot v1.1.7 in a relatively quiet and calm environment. Suddenly overnight cron job has started throwing out errors like: /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool Error: userdb(user1(a)mail.example) didn't return a home directory Error: userdb(user2(a)mail.example) didn't return a home directory Indeed, running this command produces: ------------------------- $ sudo /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool --test Error: userdb(user1(a)mail.example) didn't return a home directory Info: User lookup failed: user1(a)mail.example Error: userdb(user2(a)mail.example) didn't return a home directory Info: User lookup failed: user2(a)mail.example ------------------------- Yet these mailboxes are valid, corresponding users can login, send and receive mail. Other mailboxes are OK, too. Where to to start looking? I found that similar error message with v1.1.6 is fixed in v1.1.7, but I am running v.1.1.7 already. Please see dovecot configuration below. Thank you for your time, Ivars # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-9-server i686 Ubuntu 8.10 ext3 base_dir: /var/run/dovecot/ syslog_facility: local1 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/certs/mail.mail.example.crt ssl_key_file: /etc/certs/mail.mail.example.key 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 login_user: postfix login_greeting: VDEAVK epasta serveris. login_processes_count: 2 first_valid_uid: 107 mail_location: maildir:/home/vmail/%d/%n 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): expire fts fts_squat antispam mail_plugins(imap): expire fts fts_squat antispam mail_plugins(pop3): expire 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 managesieve_implementation_string(default): dovecot managesieve_implementation_string(imap): dovecot managesieve_implementation_string(pop3): dovecot managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): /etc/dovecot/sieve/ sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): /home/vmail/sieve-scripts/%u.sieve auth default: mechanisms: PLAIN LOGIN user: vmail username_format: %n(a)mail.example verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: /home/vmail/sieve-scripts/%u.sieve expire: Trash 30 Trash/* 30 Spam 60 expire_dict: proxy::expire fts: squat antispam_signature: X-DSPAM-Signature antispam_trash: trash;Trash;Deleted Items antispam_spam: Spam antispam_dspam_binary: /usr/bin/dspam antispam_dspam_args: --deliver=;--user;%u;-s antispam_mail_tmpdir: /tmp antispam_mail_sendmail: /usr/sbin/sendmail antispam_mail_spam: spam-%u(a)mail.example antispam_mail_notspam: notspam-%u(a)mail.example antispam_crm_binary: /bin/false dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf root@mail:~# cat /etc/dovecot/dovecot-dict-expire.conf connect = host=127.0.0.1 dbname=postfix user=postfix password=removed table = expire select_field = timestamp where_field = path username_field = username root@mail:~# # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-9-server i686 Ubuntu 8.10 ext3 base_dir: /var/run/dovecot/ syslog_facility: local1 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/certs/mail.mail.example.crt ssl_key_file: /etc/certs/mail.mail.example.key 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 login_user: postfix login_greeting: VDEAVK epasta serveris. login_processes_count: 2 first_valid_uid: 107 mail_location: maildir:/home/vmail/%d/%n 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): expire fts fts_squat antispam mail_plugins(imap): expire fts fts_squat antispam mail_plugins(pop3): expire 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 managesieve_implementation_string(default): dovecot managesieve_implementation_string(imap): dovecot managesieve_implementation_string(pop3): dovecot managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): /etc/dovecot/sieve/ sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): /home/vmail/sieve-scripts/%u.sieve auth default: mechanisms: PLAIN LOGIN user: vmail username_format: %n(a)mail.example verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: /home/vmail/sieve-scripts/%u.sieve expire: Trash 30 Trash/* 30 Spam 60 expire_dict: proxy::expire fts: squat antispam_signature: X-DSPAM-Signature antispam_trash: trash;Trash;Deleted Items antispam_spam: Spam antispam_dspam_binary: /usr/bin/dspam antispam_dspam_args: --deliver=;--user;%u;-s antispam_mail_tmpdir: /tmp antispam_mail_sendmail: /usr/sbin/sendmail antispam_mail_spam: spam-%u(a)mail.example antispam_mail_notspam: notspam-%u(a)mail.example antispam_crm_binary: /bin/false dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf

3 3

[Dovecot] troubles with 1.1.8 and squirrelmail over HTTPS
by Frank Bonnet 26 Jan '09

26 Jan '09

Hello I noticed a problem after upgrading to 1.1.8 Users that access to their mailboxes using webmail squirrelmail and HTTPS using HTTP seems to work correctly but it not safe enough ... There is an error message saying the imap server send a BYE command ... I downgraded our Dovecot server to 1.1.7 then it works again ... Does somebody has the same problem ? -- Cordialement Frank Bonnet ESIEE Paris

4 8