- dovecot - dovecot.org

Re: [Dovecot] Can imap IDLE be disabled?
by Timo Sirainen 17 Jan '09

17 Jan '09

On Jan 17, 2009, at 2:14 PM, Ed Ewing wrote: >> Are you sure disabling IDLE helps with that? AFAIK most clients >> keep persistent connections to server regardless of their ability >> to IDLE. >> >> > No expert here but netstat shows persistent established connections > for users with blackberrys. Ah, ok. I think blackberry is an exception here. But actually you can disable IDLE by changing imap_capability setting manually. Set it to the default CAPABILITY reply you get from Dovecot, just remove IDLE.

1 0

Re: [Dovecot] Can imap IDLE be disabled?
by Timo Sirainen 17 Jan '09

17 Jan '09

On Jan 17, 2009, at 2:03 PM, Ed Ewing wrote: > On 1/17/2009 10:58 AM, Timo Sirainen wrote: >> On Jan 17, 2009, at 1:56 PM, Ed Ewing wrote: >> >>> Have looked through all of the config options in the wiki and >>> don't see a reference to turning off IDLE similar to courier's >>> capability. >>> Is it possible? >> >> No. Why do you want to disable it? >> > Prefer not having persistent connections to the server. > May sound backwards but simple as that. Are you sure disabling IDLE helps with that? AFAIK most clients keep persistent connections to server regardless of their ability to IDLE.

1 0

[Dovecot] Can imap IDLE be disabled?
by Ed Ewing 17 Jan '09

17 Jan '09

Have looked through all of the config options in the wiki and don't see a reference to turning off IDLE similar to courier's capability. Is it possible? Thanks for any pointers. Using version 1.1.6

2 1

[Dovecot] Procmail + Dovecot
by Mark Nyqvist Hjarding 17 Jan '09

17 Jan '09

I have been trying to set up procmail but I am running into some issues with using deliver. I am running Debian Etch with Dovecot 1.1.8 compiled from the Debian Experimental source package. ##### Start .procmailrc ##### # System-wide settings for procmail SHELL="/bin/bash" SENDMAIL="/usr/sbin/sendmail -oi -t" LOGFILE="/var/log/procmail.log" DELIVER="/usr/lib/dovecot/deliver" # Set to yes when debugging VERBOSE=yes # Some news clients, such as slrn & nn, use $HOME/News DEFAULT="$HOME/" MAILDIR="$HOME/" # Directory for storing procmail-related files PMDIR=$HOME/Procmail # Put ## before LOGFILE if you want no logging (not recommended) LOGFILE=$PMDIR/log :0 w * ^(From|Cc|To).*(suspend2|tuxonice) | /usr/lib/dovecot/deliver -m .mail.tuxonice ##### End .procmailrc ##### When I receive a matching email I get the following in my Procmail log: procmail: Match on "^(From|Cc|To).*(suspend2|tuxonice)" procmail: Executing "/usr/lib/dovecot/deliver,-m,.mail.tuxonice" procmail: Error while writing to "/usr/lib/dovecot/deliver" procmail: Program failure (78) of "/usr/lib/dovecot/deliver" procmail: Assigning "LASTFOLDER=/usr/lib/dovecot/deliver -m .mail.tuxonice" The email then ends up in my INBOX instead. Can anyone help me how to fix this? /Mark

3 3

[Dovecot] mkdir permissions denied
by maillists＠gimo.co.uk 16 Jan '09

16 Jan '09

Hi I am having problems with a new server that I'm setting up. For some reason it doesn't want to create the directories for the users. I'm getting a permissions denied error when logging into the server. Here is the info I could find, the weird thing is that I have two other servers where this configuration is working 100% # dovecot -n # 1.1.8: /etc/dovecot.conf # OS: Linux 2.6.18-92.1.22.el5 i686 CentOS release 5.2 (Final) ext3 base_dir: /var/run/dovecot/ listen: * ssl_cert_file: /etc/pki/dovecot/cert.pem ssl_key_file: /etc/pki/dovecot/key.pem login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Ready. verbose_proctitle: yes first_valid_uid: 89 first_valid_gid: 89 mail_privileged_group: mail mail_location: maildir:/var/virtual/%d/%n/ mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/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/lib/dovecot/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 verbose: yes debug: 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 # grep -v '^ *$#.*$\?$' /etc/dovecot-sql.conf driver = mysql connect = host=localhost dbname=postfix user=user password=passwd default_pass_scheme = MD5 password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT 89 AS uid, 89 AS gid, maildir FROM mailbox WHERE username = '%u' AND active = '1' # telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK Ready. user user1(a)domain.com +OK pass userpass +OK Logged in. -ERR [IN-USE] Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2009-01-16 14:47:16] Connection closed by foreign host. # tail -F /var/log/maillog Jan 16 14:46:53 host dovecot: auth(default): new auth connection: pid=15501 Jan 16 14:47:15 host dovecot: auth(default): client in: AUTH 1 PLAIN service=pop3 secured lip=127.0.0.1 rip=127.0.0.1 lport=110 rport=50795 resp=<hidden> Jan 16 14:47:15 host dovecot: auth-worker(default): mysql: Connected to localhost (postfix) Jan 16 14:47:15 host dovecot: auth-worker(default): sql(user1(a)domain.com,127.0.0.1): query: SELECT password FROM mailbox WHERE username = 'user1(a)domain.com' Jan 16 14:47:16 host dovecot: auth(default): client out: OK 1 user=user1(a)domain.com Jan 16 14:47:16 host dovecot: auth(default): master in: REQUEST 2 15427 1 Jan 16 14:47:16 host dovecot: auth-worker(default): sql(user1(a)domain.com,127.0.0.1): SELECT 89 AS uid, 89 AS gid, maildir FROM mailbox WHERE username = 'user1(a)domain.com' AND active = '1' Jan 16 14:47:16 host dovecot: auth(default): master out: USER 2 user1(a)domain.com uid=89 gid=89 maildir=domain.com/user1/ Jan 16 14:47:16 host dovecot: pop3-login: Login: user=<user1(a)domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 16 14:47:16 host dovecot: POP3(user1(a)domain.com): Effective uid=89, gid=89 Jan 16 14:47:16 host dovecot: POP3(user1(a)domain.com): maildir: data=/var/virtual/domain.com/user1/ Jan 16 14:47:16 host dovecot: POP3(user1(a)domain.com): maildir++: root=/var/virtual/domain.com/user1/, index=, control=, inbox=/var/virtual/domain.com/user1/ Jan 16 14:47:16 host dovecot: POP3(user1(a)domain.com): mkdir(/var/virtual/domain.com/user1/cur) failed: Permission denied Jan 16 14:47:16 host dovecot: POP3(user1(a)domain.com): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2009-01-16 14:47:16] Jan 16 14:47:16 host dovecot: POP3(user1(a)domain.com): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 # ll /var/ drwxrwx--- 2 postfix postfix 4096 Jan 16 13:14 virtual # grep 89 /etc/passwd postfix:x:89:89::blablabla:/sbin/nologin # grep 89 /etc/group postfix:x:89: Can anyone please shed some light on where my problem lies? I'm at a total loss about this because like I said before, I have two other server and they have no problems. Thanks Reinhold ----- This email and any of its attachments are strictly confidential. They may contain privileged information and are intended for named addressee(s) only. Any copy, review, transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipients is prohibited. If you have received this communication in error, please delete it immediately from your system and contact us on the above telephone number or email the sender. Global Interactive Marketing On-Line Limited is neither liable for the proper and complete transmission of the information contained in the communication nor for any delay in its receipt. Although this email and any of its attachments have been checked for the presence of computer viruses and we believe, but do not warrant, they are virus free, we do not accept any responsibility for the eventual adverse effect on systems or data that could result from the opening or use of this message and any attachment. You must therefore take full responsibility of checking for viruses. Global Interactive Marketing On-Line Ltd reserves the right to monitor all email communications. Global Interactive Marketing Online Ltd is registered in England and Wales by the Companies House, Cardiff. The company registration number is 5779675. Global Interactive Marketing Online Ltd, 14 Bonhill Street, London, EC2A 4BX, United Kingdom.

1 1

[Dovecot] Patch to deliver
by Allan Cassaro 16 Jan '09

16 Jan '09

Hi Timo! I wrote a little patch to add the capability of the deliver to customize the "subject" of the rejection messages. Now is possibly to translate the body and subject! In dovecot.conf: rejection_reason_subject = Automatically rejected mail to %t rejection_reason = Your message to <%t> was automatically rejected:%n%r Please, review the patch! :D

4 13

[Dovecot] Enforcing STARTTLS for all mechs while disabling imaps
by Durk Strooisma 16 Jan '09

16 Jan '09

Hi all, Is there a way to enforce STARTTLS for all connections, regardless their authentication mechanism? disable_plaintext_auth only takes care of the auth conversation, but I would like to have all communication encrypted. As far as I can see, this would only be possible when using imaps and disabling imap. However, I would like to have the other way around; disabling imaps and using imap for all communication (with enforced STARTTLS). Am I missing something? Durk

4 9

[Dovecot] [dovecot] INDEX variable and mbox_snarf plugin
by Jonathan Siegle 15 Jan '09

15 Jan '09

Is there a way to tell the dovecot mbox_snarf plugin to use an alternate location for the index/cache files? It doesn't seem to want to use the INDEX variable. I'm guessing the answer is no because of all the ties in lib-storage/index/mbox/*c to the directory where the file(that is the inbox) lives. The filesystem where I keep the inbox file doesn't have a directory for the user to own. The user only owns the mbox file. Thanks, Jonathan

2 3

[Dovecot] dovecot 1.2 shared namespace/mailboxes %%u expands only to %
by Robert Schetterer 15 Jan '09

15 Jan '09

Hi Timo, with dovecot --version 1.2.alpha5 namespace shared { separator = / prefix = "shared/%d/%%u/" subscriptions = yes list = yes } and dovecot-acl authenticated lr in /usr/local/virtual/schetterer.com %%u seems not expand to other existing users instead it expands to % i expected showing all other maildir beyond dovecot: Jan 06 23:53:14 Info: IMAP(robert(a)schetterer.com): acl vfile: file /var/run/dovecot/user-not-found/%/dovecot-acl not found dovecot: Jan 06 23:53:14 Info: IMAP(robert(a)schetterer.com): Namespace shared/schetterer.com/%/: Permission lookup failed from /var/run/dovecot/user-not-found/% i am not clear if its my fault, or some bug -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 14

Re: [Dovecot] managesieve-login and segfault
by Timo Sirainen 15 Jan '09

15 Jan '09

You can also write to mailing list without subscribing. Anyway, I haven't written managesieve-login code, Ccing Stephan. On Thu, 2009-01-15 at 17:00 +0100, Wolfgang.Friebel(a)desy.de wrote: > Hi, > > sorry that do not write to the list, I am not subscribed yet. I have read > the november 2008 thread where managesieve-login does a segfault. As it > happened to me as well and there was no backtrace provided yet I thought > I could produce it. Please find the backtrace in the attached file. > > After having seen the output I believe, my authentication does not succeed > as I have chosen to use plaintext for sieve (and SSL for IMAP). I did > disable plaintext login in the config. > > I guess I know now what to change in my configuration which hopefully > then will allow me to login without a segfault. > > Although the segfault seems to occur when a wrong configuration is chosen, > it should not result in a segfault. > > I am running Scientific Linux 5 (this is basically Redhat Enterprise Linux > 5) on a 64 bit PC in 64 bit mode. I am using dovecot 1.1.8, managesieve > 0.10.4 and sieve 1.1.5 > > -- > Wolfgang Friebel Deutsches Elektronen-Synchrotron DESY > Phone/Fax: +49 33762 77372/216 Platanenallee 6 > Mail: Wolfgang.Friebel AT desy.de D-15738 Zeuthen Germany

4 3