- dovecot - dovecot.org

[Dovecot] Changed URL of the Sieve Mercurial repository.
by Stephan Bosch 19 Jul '09

19 Jul '09

Hi, I've changed the name of the Sieve Mercurial repository form dovecot-libsieve to dovecot-1.2-sieve, to signify the Dovecot version it applies to. The URL thus looks as follows: http://hg.rename-it.nl/dovecot-1.2-sieve Note that there are already dovecot-2.0-sieve and dovecot-2.0-managesieve repositories, but these are still somewhat broken in multiple ways and I wouldn't call these ready for testing yet. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] dsync - one or two ways?
by Timo Sirainen 18 Jul '09

18 Jul '09

dsync in Dovecot v2.0 tree is a new utility for syncing a mailbox in two locations. Some things it can be used for: - Initially transfer a mailbox to another server via SSH - A faster sync done to an existing mailbox, sending only changes - A superfast sync based on modification sequences. - Source and destination mailboxes can use different formats (convert-tool will be history) dsync can handle all kinds of conflicts in mailboxes, handle mailbox deletions, renames, etc. So it's safe to sync even if both source and destination mailboxes have had all kinds of changes. Now, the question is: Does anyone want dsync to only sync changes from source to destination, instead of doing a full two-way sync? I think in typical cases where you'd think you would want only one-way sync are also the cases where there's no changes coming the other way in any case.

7 23

[Dovecot] SMTP Auth Issue for non /etc/passwd accounts
by Mark R. Baith 17 Jul '09

17 Jul '09

Folks - With Dovecot 1.0.7, we're seemingly unable to authenticate users for out-going SMTP access who are not residing directly within the main system passwd/shadow files. (I.e. the users seeded within our non-system "dovecot" userdbs & passwd files have no "smtp-auth" joy! (Ye olde "Relaying denied. Proper authentication required") I've mucked around with this from several different angles and clearly saslauthd is the sticking point in terms of "locking-in" on the /etc system files ONLY for smtp-auth. Our defined dovecot user/passwd files are entirely ignored. Can anyone provide a direction regarding the appropriate smtp-auth in-road? Thanks, -M Regards, M

3 5

[Dovecot] Question regarding layout.
by Johan Hendriks 17 Jul '09

17 Jul '09

Hello all. I have a question regarding my mail flow. We have some users who are in a mail group (alias), and these alias receives a lot of attached documents. So i have the document in all the mailboxes of the alias. If the attached document is 2MB and that is not rare, i have 10 times 2 MB on my mail server. Is there a way to tackle this. Maybe by making the alias a mailbox itself and give other users acces or are there other options. Also i have very lame and lazy users. They refuse to clean thrash cans (i asked about that earlier,and got that tackled through the expire plugin.),also the do not remove old mail not even reading it. So is there also a option to remove mail that is not been opened, and is older than xx days or weeks. Thanks -- _______________________ *Johan Hendriks* *Schavemaker Transport* Tel: +31 (0)251 229098 Fax: +31 (0)251 212016 email: j.hendriks(a)schavemaker.com <mailto:j.hendriks@schavemaker.com> web: http://www.schavemaker.com _______________________

2 2

[Dovecot] exim4 dovecot sasl problem
by Tristan Rex Santiago 17 Jul '09

17 Jul '09

hi! i'm trying to do smtp authentication using dovecot and exim4 by following this guide http://wiki.dovecot.org/HowTo/EximAndDovecotSASL. for the exim4 part, i got an authenticator dovecot: cannot find authenticator driver "dovecot" error after i entered the codes in /etc/exim4/exim4.conf.template and reloaded exim4 with the update-exim4.conf command. i'm running debian lenny. here's the authentication section of exim4.conf.template: begin authenticators cram_md5: driver = cram_md5 public_name = CRAM-MD5 client_name = ${extract{1}{:}{${lookup{$ host}nwildlsearch{CONFDIR/passwd.client}{$value}fail}}} client_secret = ${extract{2}{:}{${lookup{$host}nwildlsearch{CONFDIR/passwd.client}{$value}fail}}} PASSWDLINE=${sg{\ ${lookup{$host}nwildlsearch{CONFDIR/passwd.client}{$value}fail}\ }\ {\\N[\\^]\\N}\ {^^}\ } plain: driver = plaintext public_name = PLAIN .ifndef AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS client_send = "<; ${if !eq{$tls_cipher}{}\ {^${extract{1}{:}{PASSWDLINE}}\ ^${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}\ }fail}" .else client_send = "<; ^${extract{1}{:}{PASSWDLINE}}\ ^${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}" .endif login: driver = plaintext public_name = LOGIN .ifndef AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS # Return empty string if not non-TLS AND looking up $host in passwd-file # yields a non-empty string; fail otherwise. client_send = "<; ${if and{\ {!eq{$tls_cipher}{}}\ {!eq{PASSWDLINE}{}}\ }\ {}fail}\ ; ${extract{1}{::}{PASSWDLINE}}\ ; ${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}" .else # Return empty string if looking up $host in passwd-file yields a # non-empty string; fail otherwise. client_send = "<; ${if !eq{PASSWDLINE}{}\ {}fail}\ ; ${extract{1}{::}{PASSWDLINE}}\ ; ${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}" .endif dovecot_login: driver = dovecot public_name = LOGIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 How can I fight insomnia? Discover how on Yahoo! Answers. http://ph.answers.yahoo.com

2 1

[Dovecot] user unknown with deliver
by Nikolay Shopik 16 Jul '09

16 Jul '09

I'm getting user unknown when trying to deliver to Sent folder messages. My master.cf part is: copy2sent unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${sasl_username} -m Sent But it still won't work. I'm running 1.0.15 pluto postfix/pipe[30934]: 7470890C4DA: to=<bcc(a)bcc.example.com>, relay=copy2sent, delay=0.03, delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (user unknown)

3 10

[Dovecot] Can Dovecot Proxy GMail?
by Paul Carter-Brown 16 Jul '09

16 Jul '09

Hi, We are using gmail (google apps) across our company with most users using outlook (windoze) or evolution (linux) and imap/pop based on user preference. We are having issues in that our internet links are fairly slow and when users download mails they get frustrated with the time it takes and often get timeouts and issues where outlook fails to fetch a mail yet gmail thinks it was retrieved - users then complain of "missing" emails. Is there a way that we could use dovecot (or similar?) to act as an imap "proxy" and users connect to dovecot while dovecot connects to gmail? Thanks Paul

3 2

[Dovecot] sieve / managesieve: unknown Sieve capability 'imapflags'
by Ralf Hildebrandt 15 Jul '09

15 Jul '09

$HOME/.dovecot.sieve.log reports: main_script: line 8: error: require command: unknown Sieve capability 'imapflags'. main_script: line 8: error: require command: unknown Sieve capability 'notify'. main_script: error: validation failed. I'm using sieve (not cmusieve) and managesieve with dovecot-1.2. SquirrelMail 1.4 is using the avelsieve plugin to created/edit the sieve rules. What am I doing wrong here? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

4 7

[Dovecot] Expire plugin - where to start?
by Frank Leonhardt 15 Jul '09

15 Jul '09

I'm running Dovecot 1.1.3 on FreeBSD 7.0 with procmail 3.22 sorting the output of Spamassassin. Just for me and a few friends. I didn't like the ageing 'standard' IMAP implementation so I thought I'd give Dovecot a try and it's really impressive. However, I'm a complete newbie to its inner workings. Spamassassin is able to find plenty to chew on so the "Probable spam" mbox (note) fills up fast. I obviously want to zap the old stuff in there automatically. It seems to me that the expire plugin is the thing I need BUT reading the documentation: http://wiki.dovecot.org/Plugins/Expire Leaves me to scared to try anything. It's all working and I don't want to break it or delete anyone's mail. The problem that the wiki isn't accurate to the version I'm running. For example /usr/libexec/dovecot/expire-tool.sh doesn't exist. Okay, this isn't Linux, and there's something likely where I'd expect it on BSD (/usr/local/...) - but it's a binary, not a shell script. It may be a direct replacement AFAIK, but it may not. I've been reading the old mailing list about problems with 1.2 and this reinforces the feeling that the wiki is out-of-sync. Am I being paranoid? Possibly, but I don't want to be posting a "Help! I've wrecked my config and deleted all my friend's mail" type message. (Okay, I'd take a backup first). So could some kind person point me at the latest documentation? Thanks, Frank.

2 2

[Dovecot] multiple authentication mechanisms/passwords for same account
by Tapani Tarvainen 15 Jul '09

15 Jul '09

This may be trivial but reading the documentation I can't find a clear answer: If multiple authentication mechanisms (or multiple databases for one) are defined, does it allow one user account to have several (at least two) alternative passwords (so that any of them would work)? Or does it first map an account to a fixed authentication mechanism/password and if it fails, others won't be tried? -- Tapani Tarvainen

2 3

[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

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

13 Jul '09

On Må, 2009-07-13, 14:01 wrote Steffen Kaiser: > On Sat, 11 Jul 2009, Glenn Remstedt wrote: > >> here are the output from dovecot-log: >> Info: imap-login: Disconnected (no auth attempts): rip=192.168.1.220, lip=192.168.1.220, TLS handshaking: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol >> * any hint or pointers are more then welcome > > 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 > > > Are both demons use the same OpenSSL library version? >

2 1

[Dovecot] getting Apple Mail and dovecot/IMAP to co-operate
by Jim Reid 13 Jul '09

13 Jul '09

Hi. I've been fighting a losing battle to get Apple Mail and dovecot to play nice. When dovecot is told to use mbox-style mailboxes, it's not possible to create child mailboxes. Apple Mail whines "The IMAP command “CREATE” failed with server error: Mailbox doesn't allow inferior mailboxes.". I've looked through the documentation, the wiki and searched the mail archives without finding a solution. Can anyone help? I've tried (and failed) to get a hybrid maildir/mbox setup to work like that shown on http://wiki.dovecot.org/Namespaces. When that gets plugged into dovecot.conf, Apple Mail blocks, with the Activity window saying "waiting for login" or something like that, even though a valid imaps connection and login has been established. There's nothing getting logged by dovecote for both of these problems, even when syslog is turned all the way to debug priority. Here's the current configuration info: shaun# dovecot -n # 1.1.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE amd64 ufs base_dir: /var/run/dovecot/ syslog_facility: local4 protocols: imaps listen: *, [::] ssl_cert_file: /usr/local/etc/ssl/certs/dovecot.pem ssl_key_file: /usr/local/etc/ssl/private/dovecot.pem ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_max_processes_count: 8 login_max_connections: 32 max_mail_processes: 32 mail_privileged_group: mail mail_location: mbox:/mail/imap/%u:INBOX=/var/mail/%u mail_debug: yes mbox_write_locks: fcntl auth default: mechanisms: cram-md5 verbose: yes debug: yes passdb: driver: pam passdb: driver: passwd-file args: /usr/local/etc/dovecot-md5 userdb: driver: passwd shaun# dovecot --version 1.1.16

3 8

[Dovecot] imap-login: Disconnected
by Glenn Remstedt 13 Jul '09

13 Jul '09

trying to login squirrelmail using dovecot-1.1.17 on a qmail-server with vpopmail setup has also running your: courier-dovecot-migrate.pl --recursive --convert --overwrite here are the output from dovecot-log: Info: imap-login: Disconnected (no auth attempts): rip=192.168.1.220, lip=192.168.1.220, TLS handshaking: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol * any hint or pointers are more then welcome cat dovecot.conf base_dir = /usr/local/var/run/dovecot/ protocols = imap imaps pop3s disable_plaintext_auth = no shutdown_clients = yes ## ## Logging ## log_path = /dev/stderr info_log_path = /dev/stderr log_timestamp = "" ## ## SSL settings - Self-Signed SSL Certificate 'openssl' ## ssl_disable = no ssl_cert_file = /var/qmail/control/servercert.pem ssl_key_file = /var/qmail/control/servercert.pem ssl_cipher_list = ALL:!LOW verbose_ssl = yes ## ## Login processes ## login_dir = /usr/local/var/run/dovecot/login login_user = dovecot login_process_per_connection = yes login_processes_count = 3 #login_max_processes_count = 128 login_max_processes_count = 140 #login_greeting = Dovecot ready. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c ## ## Mailbox locations and namespaces ## mail_location = maildir:~/Maildir namespace private { separator = . prefix = INBOX. inbox = yes } namespace private { separator = . prefix = INBOX. inbox = no hidden = yes list = no # for v1.1+ } ## ## Mail processes ## verbose_proctitle = yes first_valid_uid = 89 last_valid_uid = 89 ## ## Maildir-specific settings ## maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no ## ## IMAP specific settings ## protocol imap { # non-encrypted IMAP: 127.0.0.1 (webmail) is secure by definition # # in the name of all that is good in the world, PLEASE # don't allow your users to use IMAP without encryption! # listen = 192.168.1.220:143 # SSL-encrypted IMAP on port 993 ssl_listen = 192.168.1.220:993 imap_max_line_length = 65536 login_greeting_capability = yes } ## ## POP3 specific settings ## protocol pop3 { # in the name of all that is good in the world, PLEASE # don't allow your users to use POP3 without encryption! # listen = 192.168.1.220:110 # SSL-secured POP3 on port 995 ssl_listen = 192.168.1.220:995 pop3_no_flag_updates = no pop3_uidl_format = %v-%u } ## ## Authentication processes ## auth default { mechanisms = plain passdb vpopmail { args = } userdb vpopmail { } user = vpopmail count = 1 ssl_require_client_cert = no }

2 1

[Dovecot] Possible fix to an old Thunderbird related problem
by Marc Perkel 13 Jul '09

13 Jul '09

I think I might have finally fixed it. The problem was that the max_cached_connections in Thunderbird defaults to 25 and I had login process count set to 10. I think raising it to 25 ill fix it. Just posting this in case others are having this problem. What was happening was that the message counts were increasing but the messages didn't show up in the list. Or messages would appear to be empty. Restarting Dovecot or restarting Thunderbird fixes the problem temporarily. I'm hoping this annoyance will go away now.

6 11

[Dovecot] v1.2.1 released
by Timo Sirainen 13 Jul '09

13 Jul '09

http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz.sig Mainly fixes to some issues found by people when upgrading to v1.2.0. * GSSAPI: Changed logging levels and improved the messages. Changed the way cross-realm authentication handling is done, hopefully it's working now for everyone. * imap/pop3 logins now fail if home directory path is relative. v1.2.0 deliver was already failing with these and they could have caused problems even with v1.1. * IMAP: Custom authentication failure messages are now prefixed with [ALERT] to get more clients to actually show them. + Improved some error messages. - pop3: AUTH PLAIN was broken when SASL initial response wasn't given. - mbox: New mailboxes were created with UIDVALIDITY 1. - quota-fs was defaulting to group quota instead of user quota. - Fixed ACLs to work with mbox. - Fixed fchmod(-1, -1) errors with BSDs - convert plugin / convert-tool: Fixed changing hierarchy separators in mailbox names when alt_hierarchy_char isn't set.

8 9