- dovecot - dovecot.org

[Dovecot] RESOLVED: strange quota behaviour with dovecot 1.1.7
by listacc＠gmx.de 15 Jul '09

15 Jul '09

Hi, I just wanted to tell you that my problems are resolved now. Seems that Timo had the essential hint for me. Thank you very much!! :-) On 27.06.2009 23:40, Timo Sirainen wrote: >> passdb: >> driver: pam >> passdb: >> driver: sql >> args: /etc/dovecot/dovecot-sql.conf > > Do you really want to have system users too? No, I don´t want to :-) I switched this off. >> password_query = SELECT username AS user, password, '/drbd/mail/vmail/%d/%n' AS userdb_home, 'maildir:/drbd/mail/vmail/%d/%n' AS userdb_mail, 5001 AS userdb_uid, 5001 AS userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' > > You're also not using userdb prefetch, so all these usedb_* fields are > ignored here. > Seems that was it! Now quota works very fine! > After growing quota, mails to the account are accepted again. But my Thunderbird with Quota plugin continues showing the old quota setting. When more mails are sent to this account, it shows a quota > 100%. > (...) > If I try now, as a user, to delete mails from the "overfilled" Inbox, it is denied with a "quota exceeded" message. But I´m able to send further mails to this account. The only way to get the account working properly again is to delete the messages directly on the server´s filesystem. > This happens again even after correcting the MySQL query, but it´s very easy to fix when the user logs out and in again (e.g. closes and reopens his Thunderbird) :-) Thank you very much for the fix and this very nice imap server!!! Andreas -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Dovecot] v3.0 architecture
by Timo Sirainen 15 Jul '09

15 Jul '09

I just had a thought. It's probably going to be too big of a change for v2.0, so something to think about for v3.0: Supporting multiple UIDs is difficult. Currently expire-tool and v2.0's LMTP server are implemented in a way that it's always running as root and only temporarily dropping privileges. So any security hole in there gives the attacker root privileges. Not very nice. With a single UID it's possible (or will be) to just use that one UID for the process without running as root. User sharing mailboxes to another user with different UID is even more difficult. Currently the only practical way to implement this is to assign read-write permissions to some group and have all mail files owned by that group. Not very nice. Sharing mailboxes between users located in different servers is impossible if the disk isn't somehow shared. All of these can be solved the same way: 1. imap, pop3, lmtp, etc. processes will be running without any privileges, very much like imap/pop3-login nowadays. Nobody-chrooted to empty directory. 2. Create storage processes that are started as needed. They can be configured in different security/performance settings: One storage process per user, one storage process per UID, setuid-root style shared storage process for multiple UIDs. 3. Mail processes talk to storage processes via some protocol. They can talk via UNIX socket or TCP/IP. If an existing connection can't handle the target UID, a new connection is made that either reuses an existing storage proces or creates a new one. 4. IMAP can finally implement truly simultaneously running queries (where it makes sense) by creating more storage processes if existing ones are busy handling longer-running commands. This also allows using the same storage process for multiple simultaneous IMAP connections and mail deliveries (and etc). The storage processes can also hang around and keep mailboxes open after all connections have closed it (dynamically figured out when it makes sense) to handle webmail clients that create lots of short-living connections or POP3 clients who poll for new mail every minute. The big problem is what the protocol should be. Use some existing RPC protocol? It should be something extensible so that a plugin in imap process can talk to a plugin in storage process, without the base processes knowing anything about the details (e.g. imap-quota plugin asking quota usage from storage's quota plugin). In any case the client side API should be asynchronous. That can make it annoyingly difficult to use though. Wonder if I could switch to erlang or something for the imap/pop3 processes :)

9 13

[Dovecot] Sieve problem: No vacation message when mail is addressed to an alias of the mailbox.
by M. Bobkiewicz 15 Jul '09

15 Jul '09

Hi, I?m facing here a wierd problem: We have a vacation messaging system using sieve. When activated the system forwards incomming messages to a given address and sents an out of office reply to the sender. This works like a charm when the mail is addressed to mailbox@domain. When the incomming mail ist addressed to alias.to.mailbox@domain the mail is delivered to the mailbox, it is forwarded to the given reciepient but there is no auto reply going out to the sender! Our setup: CentOS 5.2 + postfix 2.5.6 + dovecot 1.1.11 with domain and accounts stored in a mysql database. The script: require ["fileinto", "vacation"]; redirect "mailbox2@domain"; keep; vacation :days 1 :subject "Out of Office reply" " The auto reply text. "; Any advice is welcome, Best regards, Mike

4 8

Re: [Dovecot] imap-login: Disconnected
by glenn＠remstedt.org 14 Jul '09

14 Jul '09

On Må, 2009-07-13, 15:43 wrote Steffen Kaiser: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 13 Jul 2009, glenn(a)remstedt.org wrote: > >> Date: Mon, 13 Jul 2009 15:40:59 +0200 (CEST) >> From: glenn(a)remstedt.org >> To: Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> >> Cc: dovecot(a)dovecot.org >> Subject: Re: [Dovecot] imap-login: Disconnected >> >> On Må, 2009-07-13, 15:35 wrote Steffen Kaiser: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Mon, 13 Jul 2009, glenn(a)remstedt.org wrote: >>> >>>>> Does squirrelmail connects to port 995, but is not using SSL? >>>> >>>> when testing SSL/TLS connections they all works i.e. >>>> >>>> # for pop: >>>> openssl s_client -connect localhost:995 >>>> >>>> # for imap: >>>> openssl s_client -connect localhost:993 >>>> >>>> openssl s_client -connect localhost:143 -starttls imap >>> >>> This reply does not answer the question, if Squirrelmail is using SSL. >> >> no it's not using SSL. > > then reconfigure Squirelmail to use port 143. > > On localhost there should be no reason to use SSL anyway. > ok, this is now working fine - but i've now also try to let client's from outside connect to our webmail, by setting the imap-ssl(993) enabled, but unfortunate this one does not work. * how could i debug this?

1 0

[Dovecot] Comments in sieve plugin section of dovecot-example.conf
by Edgar Fuß 14 Jul '09

14 Jul '09

The Wiki includes several comments about sieve_* variables which are not mentioned in dovecot-example.conf, especially sieve_{before,after} and sieve_extensions and sieve_subaddress_sep. Could these be added to the commented config file?

1 0

[Dovecot] sieve_execute_bytecode(/var/vmail/domain1/user/dovecot.sievec) failed
by Alejandro Vargas 14 Jul '09

14 Jul '09

I am trying to implement vacation with sieve in dovecot, but each time I try to use a sieve rule that sends a mail, like vacation or reject, I obtain this error code_ sieve_execute_bytecode(/var/vmail/domain1/user/dovecot.sievec) failed Checking syslog I found this message: sieve runtime error: Reject: No return-path for reply Googling I found a report of a problem like this but I can't found a solution. I'm using postfix+dovecot with virtual users only. # dovecot -n # 1.1.13: /etc/dovecot.conf # OS: Linux 2.6.29.3-desktop-1mnb i686 Mandriva Linux 2009.1 ext3 base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/marte/mail-cert.pem ssl_key_file: /etc/ssl/marte/mail-key.pem 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_process_per_connection: no first_valid_uid: 60000 first_valid_gid: 12 mail_access_groups: mail mail_location: maildir:/var/vmail/%d/%u/Maildir fsync_disable: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota autocreate antispam mail_plugins(imap): quota imap_quota autocreate antispam mail_plugins(pop3): quota 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 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 ntlm rpa apop user: nobody debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot-sql.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: 432 user: vmail group: mail plugin: quota: dict:::proxy::quotadict quota_rule: *:storage=0:messages=0 autocreate: Trash autocreate2: Spam autosubscribe: Spam antispam_signature: X-DSPAM-Signature antispam_signature_missing: move antispam_trash: trash; Trash; Deleted Items; Deleted Messages;Elementos eliminados;papelera antispam_spam: spam;SPAM;Spam;Correo no deseado;Correo electrónico no deseado;Correo electr&APM-nico no deseado antispam_dspam_binary: /usr/bin/dspam antispam_dspam_args: --deliver=;--user;%u antispam_dspam_result_header: X-DSPAM-Result antispam_dspam_result_blacklist: Virus antispam_mail_tmpdir: /tmp antispam_mail_sendmail: /usr/sbin/sendmail antispam_crm_binary: /bin/false dict: quotadict: mysql:/etc/dovecot-dict-quota.conf

2 1

[Dovecot] SSL_PARAMETERS_PERM_PATH
by Leo Baltus 14 Jul '09

14 Jul '09

Hi, I am not on this list so please CC me. Using dovecot-1.2.x it seems we can not configure the location of ssl- parameters.dat.tmp, it is hard coded to be in PKG_STATEDIR: ./src/master/master-settings.c: #define SSL_PARAMETERS_PERM_PATH PKG_STATEDIR"/"SSL_PARAMETERS_FILENAME This can lead to problems when you're running multiple instances on one machine. Apart from that, it would be very useful if wasn't hard- coded like that. Maybe it could be in base_dir or have a configuration option of its own? -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services /NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beheer(a)omroep.nl, 035-6773555 \/

2 7

[Dovecot] dovecot v1.2.1 expire-tool with mail_log enabled
by Nikita Koshikov 14 Jul '09

14 Jul '09

Hello list, Sorry, if it has been asked, but searching throught list not give possitive answers. After upgrade to dovecot version 1.2.1 expire-tool stoped working. I have changed database format and config file to appropriative 1.2 version but: expire-tool.sh fails with: # dovecot -c /etc/dovecot/dovecot.conf --exec-mail ext /usr/libexec/dovecot/expire-tool.sh Info: Loading modules from directory: /usr/lib/dovecot/imap Info: Module loaded: /usr/lib/dovecot/imap/lib10_quota_plugin.so Info: Module loaded: /usr/lib/dovecot/imap/lib11_trash_plugin.so Info: Module loaded: /usr/lib/dovecot/imap/lib20_expire_plugin.so Info: Module loaded: /usr/lib/dovecot/imap/lib20_fts_plugin.so Error: dlopen(/usr/lib/dovecot/imap/lib20_mail_log_plugin.so) failed: /usr/lib/dovecot/imap/lib20_mail_log_plugin.so: undefined symbol: imap_write_flags Fatal: Couldn't load required plugins When I diasabled mail_log plugin from imap section, everything start working, as expected and expire-tool delete old mail. dovecot -n gives: # 1.2.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-gentoo-r4 i686 Gentoo Base System release 1.12.11.1 log_path: /var/log/dovecot/dovecot-error.log info_log_path: /var/log/dovecot/dovecot.log protocols: imaps managesieve ssl_cert_file: /etc/ssl/dovecot/imaps.crt ssl_key_file: /etc/ssl/dovecot/imaps.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_greeting: Server ready. login_processes_count: 10 login_max_processes_count: 512 first_valid_uid: 8 last_valid_uid: 8 first_valid_gid: 12 last_valid_gid: 12 mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota trash fts fts_squat expire zlib mail_log mail_plugins(imap): quota imap_quota trash fts fts_squat expire zlib mail_log mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve auth default: mechanisms: plain login cache_size: 10240 cache_negative_ttl: 0 user: dovecot_auth master_user_separator: * worker_max_count: 50 passdb: driver: passwd-file args: /etc/dovecot/passdb/master.pwd master: yes passdb: driver: passwd-file args: /etc/dovecot/passdb/users.pwd passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot/dovecot-userdb-ldap.conf userdb: driver: passwd-file args: /etc/dovecot/passdb/users.pwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: mail group: dovecot_auth master: path: /var/run/dovecot/auth-master mode: 384 user: mail group: mail plugin: quota_warning: storage=95%% /etc/dovecot/plugins/quota_warning.sh 95 quota: maildir:Mailbox quota quota_rule: *:storage=500M quota_rule2: Trash:storage=10%% trash: /etc/dovecot/plugins/dovecot-trash.conf expire: Trash 1 Spam 30 expire_dict: proxy::expire sieve: ~/.dovecot.sieve sieve_storage: ~/sieve sieve_extensions: +imapflags +notify dict: expire: sqlite:/etc/dovecot/plugins/expire.conf cat /etc/dovecot/plugins/expire.conf #driver=sqlite connect = /var/mail/expire.db #v1.2 map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } If you need any addition information please tell.

4 5

[Dovecot] Released ManageSieve v0.10.7 for Dovecot v1.1.17
by Stephan Bosch 13 Jul '09

13 Jul '09

Hello Dovecot users, This release is entirely composed of bug fixes, most of which were found and fixed earlier in the implementation for Dovecot v1.2. Changelog ManageSieve v0.10.7: - Fixed generation of core dumps. - Fixed panic occurring when many errors are produced by the Sieve compiler (bug found by Pascal Volk). - Fixed potential memory leak in the PUTSCRIPT command. - Fixed CRLF line breaks in compile errors. - Improved handling of script truncation bugs: connection is now closed. (ManageSieve patch) - Forgot to add the managesieve_logout_format setting to the config file. Now it works (bug reported by Pascal Volk). -- The releases are available as follows: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.7.tar.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.7.tar.gz.s… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.17-managesieve-0.10.7.diff.… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.17-managesieve-0.10.7.diff.… -- 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

2 5

Re: [Dovecot] imap-login: Disconnected
by glenn＠remstedt.org 13 Jul '09

13 Jul '09

On Må, 2009-07-13, 15:35 wrote Steffen Kaiser: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 13 Jul 2009, glenn(a)remstedt.org wrote: > >>> Does squirrelmail connects to port 995, but is not using SSL? >> >> when testing SSL/TLS connections they all works i.e. >> >> # for pop: >> openssl s_client -connect localhost:995 >> >> # for imap: >> openssl s_client -connect localhost:993 >> >> openssl s_client -connect localhost:143 -starttls imap > > This reply does not answer the question, if Squirrelmail is using SSL. no it's not using SSL. >

2 1