August 2009 - dovecot

[Dovecot] Managesieve configuration problem
by listacc＠gmx.de 02 Aug '09

02 Aug '09

Hello! I'm trying for a lot of time to make managesieve working with dovecot 1.1.17 and virtual users on openSuSE 11.1. I think I'm doing some misconfiguration, but I can't figure it out. Perhaps it's something with the paths to the sieve scripts? In dovecot.conf I find in the comments: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ protocol managesieve { #(...) # Specifies the location of the symlink pointing to the active script in # the sieve storage directory. This must match the SIEVE setting used by # deliver (refer to http://wiki.dovecot.org/LDA/Sieve#location for more # info). Variable substitution with % is recognized. # Take care: if a file in a maildir: begins with a '.', it is recognized # as a folder; so, avoid this. #sieve=~/.dovecot.sieve sieve = /drbd/mail/vmail/%d/%n/dovecot.sieve } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "This must match the SIEVE setting used by deliver", so I have to take a look to LDA section, no? But there I don't find any hint for sieve settings: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)mydomain.tld # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. #hostname = # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. mail_plugins = cmusieve quota mail_plugin_dir = /usr/lib64/dovecot/modules/lda # If user is over quota, return with temporary failure instead of # bouncing the mail. #quota_full_tempfail = no # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. "saved to INBOX") # %m - Message-ID # %s - Subject # %f - From address #deliver_log_format = msgid=%m: %$ # Binary to use for sending mails. sendmail_path = /usr/lib/sendmail # Human readable error message for rejection mails. Use can use variables: # %n = CRLF, %r = reason, %s = subject, %t = recipient rejection_reason = Your message to <%t> was automatically rejected:%n%r # UNIX socket path to master authentication server to find users. # auth_socket_path = /drbd/mail/var/run/dovecot/auth-master auth_socket_path = /var/run/dovecot/auth-master } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I tried to log in to managesieve manually with gnutls-cli, and that was successfull. I was able to authenticate. But when I try to put the example script from dovecot wiki (http://wiki.dovecot.org/ManageSieve/Troubleshooting) ~~~~~~~~~~~~~~~~~~~~~~~~~~~ PUTSCRIPT "hutsefluts" {6+} keep; ~~~~~~~~~~~~~~~~~~~~~~~~~~~ I get no ~~~~~~~~~~~~~~~~~~~~~~~~~ OK "Putscript completed." ~~~~~~~~~~~~~~~~~~~~~~~~~ there happens nothing, managesieve seems to wait for something else. When I look now into the directory where the script should be stored (the folder has been created automatically) I don't find any script file but a folder "tmp" that contains a plaintext file with the script commands inside, eg. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ hutsefluts-12345678.M033562P2271.imap.sieve ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After disconnecting, this file disappears. In the dovecot.info log it looks like this: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ dovecot: Jul 30 14:51:56 Info: auth(default): master out: USER 16 test(a)mydomain.tld home=/drbd/mail/vmail/mydomain.tld/test mail=maildir:/drbd/mail/vmail/mydomain.tld/test uid=5001 gid=5001 quota_rule=*:storage=512000000B dovecot: Jul 30 14:51:56 Info: managesieve-login: Login: user=<test(a)mydomain.tld>, method=PLAIN, rip=192.168.200.39, lip=192.168.200.40, TLS dovecot: Jul 30 14:51:56 Info: MANAGESIEVE(test(a)mydomain.tld): Effective uid=5001, gid=5001, home=/drbd/mail/vmail/mydomain.tld/test dovecot: Jul 30 14:51:56 Info: MANAGESIEVE(test(a)mydomain.tld): sieve-storage: using active sieve script path: /drbd/mail/vmail/mydomain.tld/test/dovecot.sieve dovecot: Jul 30 14:51:56 Info: MANAGESIEVE(test(a)mydomain.tld): sieve-storage: using active sieve script path: /drbd/mail/vmail/mydomain.tld/test/dovecot.sieve dovecot: Jul 30 14:51:56 Info: MANAGESIEVE(test(a)mydomain.tld): sieve-storage: using sieve script storage directory: /drbd/mail/vmail/mydomain.tld/test/sieve dovecot: Jul 30 14:51:56 Info: MANAGESIEVE(test(a)mydomain.tld): sieve-storage: relative path to sieve storage in active link: sieve/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../vmail/mydomain.tld/test/dovecot.sieve is missing completely. Perhaps you can give me a small hint? And here is my "dovecot -n": ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # 1.1.7: /etc/dovecot/dovecot.conf Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 2256). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Linux 2.6.27.25-0.1-default x86_64 openSUSE 11.1 (x86_64) ext3 base_dir: /drbd/mail/var/run/dovecot/ log_path: /var/log/dovecot.err info_log_path: /var/log/dovecot.info protocols: imaps managesieve listen(default): * listen(imap): * listen(managesieve): 192.168.200.40:2000 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/certs/imap.crt ssl_key_file: /etc/ssl/private/imap.key verbose_ssl: yes login_dir: /drbd/mail/var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login max_mail_processes: 2000 mail_max_userip_connections(default): 30 mail_max_userip_connections(imap): 30 mail_max_userip_connections(managesieve): 10 first_valid_uid: 5001 last_valid_uid: 5001 mail_location: maildir:/drbd/mail/vmail/%d/%n mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/modules/managesieve managesieve_implementation_string(default): dovecot managesieve_implementation_string(imap): dovecot managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): /drbd/mail/vmail/%d/%n/sieve sieve(default): sieve(imap): sieve(managesieve): /drbd/mail/vmail/%d/%n/dovecot.sieve auth default: mechanisms: plain login cram-md5 user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/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: vmail plugin: quota: maildir ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By the way, I'm quite amazed how fast dovecot is developed at the moment, and it makes lots of fun to see it growing!! kind regards, Andreas -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Dovecot] imap error
by Jack Raats 02 Aug '09

02 Aug '09

This morning I tried to read my mail using squirrelmail. I cann't connect. I'll get the following error: Aug 2 07:51:44 hera dovecot: imap-login: Login: user=<jack>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Aug 2 07:51:44 hera dovecot: IMAP(jack): Disconnected: Logged out bytes=44/298 The pop3 is not affected. Can anyone give me a clue where to look for?? Thanks Jack

2 3

[Dovecot] Best way to get login protocol (pop3/imap) in post-login script
by Zhang Huangbin 02 Aug '09

02 Aug '09

Hi, all. I found doc here: http://wiki.dovecot.org/PostLoginScripting and use ${USER}, ${IP} to track last-login username and remote ip address, but how can i track the mail protocol it used? like pop3, pop3s, imap, imaps? Currently, i wrote shell script as post-login script, and use below command to get protocol: ---- $(basename ${MAIL_PLUGIN_DIR}) ---- But is it the best way to get it? Thanks very much. :) -- Best Regards. Zhang Huangbin - Open Source Mail Server Solution for Red Hat(R) Enterprise Linux, CentOS, Debian, Ubuntu: + http://code.google.com/p/iredmail/ + http://www.iredmail.org/forum/

1 0

[Dovecot] E-Mail Encryption
by Christian Felsing 01 Aug '09

01 Aug '09

Hello, I am new to Dovecot but installation was quite easy, so there is one more LDAP authenticated, Dovecot / Postfix mailbox online, but there is one question left: I would like to set up a configuration, which encrypts every user mail with a unique key. If user logs in, private key should be decrypted with user password and every mail user requests should be decrypted with users private key. If a mail comes in, it should be encrypted with users public key. That key pair should be used for that purpose only. Obviously a GnuPG plugin between deliver and rest of Dovecot is needed. best reagrds Christian

15 24