July 2009 - dovecot - dovecot.org

[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] 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

[Dovecot] Fw: Shared mailboxes and INBOX
by Keith Edmunds 01 Aug '09

01 Aug '09

Should users of a shared mailbox be able to see both their personal inbox and that of the shared mailbox? Thanks, Keith Begin forwarded message: Date: Wed, 29 Jul 2009 17:50:08 +0100 From: Keith Edmunds <kae(a)midnighthax.com> To: dovecot(a)dovecot.org Subject: [Dovecot] Shared mailboxes and INBOX I'm trying to implement a shared mailbox: in other words, we have a generic email address ("security@") which we want a number of users to be able to monitor. The problem I have is that users can see folders under that shared mailbox but can't see the INBOX. All the users in question have their own INBOX in their private namespace, so does this raise a conflict with monitoring another mailbox's INBOX? Configuration: -------------------------------------------------------------------------------- # dovecot -n # 1.2.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.2 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: shared/ location: maildir:/home/publicfolders:INDEX=~/Maildir/public list: yes namespace: type: shared separator: / prefix: security/ location: maildir:/home/securitymailbox/Maildir:INDEX=~/Maildir/securitymailbox list: yes auth default: passdb: driver: pam userdb: driver: passwd -------------------------------------------------------------------------------- Thanks, Keith

1 0

[Dovecot] Solaris 10 dovecot-latest configure error
by Tomi Vainio 31 Jul '09

31 Jul '09

Hi, I've got latest source code from http://dovecot.org/nightly/dovecot-20090731.tar.gz It's a minor bug that mysql.h test fails because CFLAGS are missing from this test. Tomppa > checking for mysql_init in -lmysqlclient... yes > checking mysql.h usability... yes > checking mysql.h presence... no > configure: WARNING: mysql.h: accepted by the compiler, rejected by the preprocessor! > configure: WARNING: mysql.h: proceeding with the compiler's result > checking for mysql.h... yes > checking for mysql_ssl_set in -lmysqlclient... yes > configure:33185: checking mysql.h usability > configure:33197: cc -c -xO4 -I/usr/sfw/include/mysql -R/usr/sfw/lib:/usr/lib/sasl -L/usr/sfw/lib -L/usr/lib/sasl -I/usr/sfw/include conftest.c >&5 > configure:33203: $? = 0 > configure:33207: test -z > || test ! -s conftest.err > configure:33210: $? = 0 > configure:33213: test -s conftest.o > configure:33216: $? = 0 > configure:33226: result: yes > configure:33230: checking mysql.h presence > configure:33240: cc -E conftest.c > "conftest.c", line 127: cannot find include file: <mysql.h> > cc: acomp failed for conftest.c

4 4

[Dovecot] Clients and dovecot-uidlist
by Thomas Hummel 31 Jul '09

31 Jul '09

Hello, I'm trying to figure out what exactly (and why) are the consequences of a lost or removal of the dovecot-uidlist file on an IMAP client (Thunderbird for instance). I took for granted that it was that the client would download all messages again since it might be confused by some UID changes. But I don't really see why (on the IMAP protocol level) and I don't know how to reproduce it. My understanding is that . dovecot-uidlist is not recreated until some client selects the mailbox . the client does something like : x UID fetch 1:* (FLAGS) to begin with anyway. So I guess the problem does not occur when no new messages arrive on the mailbox since the same UIDs would be assigned to the same messages ? But why would that change ? In which situation ? But can you show me some IMAP protocol command exchange that would illustrate . when such a problem can occur . how the client would detect that there has been some UID corruption . how it would fix it Thanks -- Thomas Hummel

2 33

[Dovecot] sieve delivery to utf folders
by Nikita Koshikov 31 Jul '09

31 Jul '09

Hello list, Today, my users have noticed, that delivery to folders with non-english names is broken. For example, if I create russian directory, it correct encoded and display into mail-client program and my webmail: Encoded: Normal view .INBOX.&BEIENQRBBEI- русс This is part of sieve script, which routing delivery to russian folder. .... elsif allof (header :contains "Subject" "qwe") { fileinto "INBOX/&BEIENQRBBEI-"; } But, when actualy delivery take place, in logs I have Jul 30 17:13:49 deliver(koshikov.n(a)domain.com): Info: sieve: msgid=<4A71A9E6.5040301(a)domain.com>: stored mail into mailbox 'INBOX/&-BEIENQRBBEI- And folder .INBOX.&-BEIENQRBBEI- appears in users maildir. This folder can't be unencoded by mail-client program and user see exactly "&-BEIENQRBBEI-" under INBOX directory(also normaly encoded directory "&BEIENQRBBEI-" --> "русс" displays correct). Something breaks encoding and adds sing "-" to all words in utf encoded directory names. I can't tell exactly when this problem appear, but I remember that I have tested delivery to russian directories by sieve scripts and all worked fine. My current dovecot installation is 1.2.2, dovecot-sieve-0.1.9 and managesieve-0.11.7

4 6

Re: [Dovecot] whining
by A. van Harten 31 Jul '09

31 Jul '09

Be a man, Jim, and write this in public. [QUOTE] Jim Reid[/QUOTE] > On 31 Jul 2009, at 09:36, A. van Harten wrote: > >> Sorry, but the answers on this mail group are written with as few >> words as >> possible - if it was written in Finnish, I'd understand just as much >> as I >> do now. >> Googling on a Dovecot problems results always in www.dovecot.org or >> one of >> its child sites. Always. >> Googling on a Linux question results always in experts-exchange. >> Always. > > Clearly, dovecot is not for you. Now please go back to the linux world > you came from. You appear to be comfortable there. > > I am also disgusted and very annoyed with the tone of your recent > email: negative, childish, destructive and counter-productive. You did > not identify any particular problem, suggest other approaches or point > at areas where specific improvements could be made. You just whined > about the results of google searches. > -- Med venlig hilsen, Met vriendelijke groeten,

2 2

Re: [Dovecot] Several errors
by A. van Harten 31 Jul '09

31 Jul '09

Tried that, same result. dovecot: Jul 25 00:55:41 Info: Dovecot v1.0.7 starting up dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login processes, slowing down for now dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Info: Created login processes successfully, unstalling dovecot: Jul 25 00:55:42 Error: child 3850 (login) returned error 89 dovecot: Jul 25 00:55:42 Error: child 3851 (login) returned error 89 dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login processes, slowing down for now dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Error: child 3852 (login) returned error 89 dovecot: Jul 25 00:55:42 Info: Created login processes successfully, unstalling [root@nestorix etc]# dovecot -n # 1.2.1: /usr/local/etc/dovecot.conf Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. # OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot protocols: pop3 pop3s imap imaps ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap login_executable(imap): /usr/libexec/dovecot/imap login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Havecom Mailserver ready. valid_chroot_dirs: /var/mail/vhosts mail_location: maildir:/var/mail/vhosts/%d/%n/ mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/libexec/dovecot/dovecot-auth username_translation: "/$ verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@nestorix etc]# service dovecot stop Stopping Dovecot Imap: [ OK ] [root@nestorix etc]# gedit /var/log/dovecot [root@nestorix etc]# service dovecot start Starting Dovecot Imap: [ OK ] [root@nestorix etc]# gedit /var/log/dovecot ^C [root@nestorix etc]# dovecot -n # 1.2.1: /usr/local/etc/dovecot.conf Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. # OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot protocols: pop3 pop3s imap imaps ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap login_executable(imap): /usr/libexec/dovecot/imap login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Havecom Mailserver ready. valid_chroot_dirs: /var/mail/vhosts mail_location: maildir:/var/mail/vhosts/%d/%n/ mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/libexec/dovecot/dovecot-auth username_translation: "/$ verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@nestorix etc]# Albert [QUOTE] Timo Sirainen[/QUOTE] > On Sat, 2009-07-25 at 00:07 +0200, FraNL wrote: >> Running OS: CentOS 5.3 (2.6.18-128.2.1.el5) >> >> 1. >> My Linux distribution comes with Dovecot 1.0.7. After trying to make it running, I encoutnered many problems. So I decided to upgrade to 1.2.1. When running dovecot -r from CLI, it returns with version 1.2.1. But at the top of the log file it says: Info: Dovecot v1.0.7 starting up >> >> So I am not sure which version I am running. > > It means you're using some weird mix of both. Get rid of all of Dovecot v1.0 binaries (rpm -e dovecot or something) and your problems should go away. > > -- Med venlig hilsen, Met vriendelijke groeten, -- Med venlig hilsen, Met vriendelijke groeten,

4 15

Re: [Dovecot] Several errors
by A. van Harten 31 Jul '09

31 Jul '09

[QUOTE] Charles Marcus[/QUOTE] > > Who says you have to install it? Almost all the fora which are speaking of setting up a mail server tell me to install Dovecot > And who is it that you think owes you 'descent support' for free? When and where did I spoke about FREE? I never said I didn't want to pay for it!!! Please don't think for me... > That said, the support on the dovecot list is the best I've seen, even > when people get attitudes (like yours)... Attitudes? Since when is a normal business inquiry not appropriate? > If you want to learn linux, and learn how to admin a mail server, you're > expected to do some leg work yourself... no one expects you to be a > guru, but a little googling on how to change ownership of files in linux > would most likely answer this particular question. Sorry, but the answers on this mail group are written with as few words as possible - if it was written in Finnish, I'd understand just as much as I do now. Googling on a Dovecot problems results always in www.dovecot.org or one of its child sites. Always. Googling on a Linux question results always in experts-exchange. Always. > > Also, the attititude will most likely get surprising little response. If > you want to get help from someone for free, it helps to ask nicely. I don't agree. I know the way of asking isn't the most nice way - and I also apologise to them, who assisted me! But who cares if I agree with someone, who didn't assist me at all, but who only is capable of writing negatively about me? > Thats said, I wouldn't be surprised if Timo responds nicely anyway... > I've seen him respond to much worse emails than yours, and yours was > pretty bad... Pretty bad? You misunderstood me, my friend. Try to read reasonable next time. That helps! > > -- > > Best regards, > > Charles > -- Med venlig hilsen, Met vriendelijke groeten,

1 0

[Dovecot] Limiting user access
by Darvin Denmian 30 Jul '09

30 Jul '09

Hello, Is there a way to restrict clients access, for example: user1(a)domain.com -> only access pop3 user2(a)domain.com -> can access pop3 and imap in Dovecot? Thanks !!!

2 2