- dovecot - dovecot.org

[Dovecot] Configure/install path overrides
by Remy Zandwijk 30 Sep '07

30 Sep '07

Hi, I'm building and installing dovecot on a Solaris 10 machine and therefore I want to install Dovecot in /opt/dovecot. Thus, I start configure with --prefix=/opt/dovecot. I also override things like 'libexecdir', 'docdir', etc. When calling make install, Dovecot is installed in /opt/dovecot, but for example the binary user files are installed in /opt/dovecot/bin/dovecot. The same for the docs, which are installed in /opt/dovecot/share/doc/dovecot. I think that's not quite nice and neat, so I call 'make install' like: make docdir=/opt/dovecot/share/doc install. But even then, the wiki stuff is still installed in /opt/dovecot/share/doc/dovecot/wiki in stead of /opt/dovecot/share/doc/wiki. Very anoying. My point is that ./configure should be able to override all paths, but since some paths are somehow hard-coded in the Makefile, this is impossible. Any chance this will (be) change(d) sometime? -Remy

2 1

[Dovecot] deliver w/quotas - MDN after accept mail?
by Ken A 30 Sep '07

30 Sep '07

I'm testing deliver with sendmail and fs quotas. On an over quota condition, deliver accepts the mail, deletes it, then issues a MDN immediately. Is there a way to get deliver to soft fail like procmail does with a 400 error and queue the mail, then let sendmail handle the MDN, following it's "confTO_QUEUEWARN" and "confTO_QUEUERETURN" ? Thanks, Ken -- Ken Anderson Pacific.Net

3 5

[Dovecot] Auto create folder(s)
by Lars Stavholm 30 Sep '07

30 Sep '07

Hi All, does anyone know of a way to automatically create user folder(s)? Like creating a Spam folder on login if not already there. I've googled a bit but couldn't find anything relevant. Any advice appreciated R /Lars

3 2

[Dovecot] Proxy setup between two servers
by Abhijit Hoskeri 30 Sep '07

30 Sep '07

Hi, I am trying to set up a proxy between two dovecot servers. I have the following set up here. Dovecot version: 1.0.rc15 dovecot -n: # /etc/dovecot/dovecot.conf info_log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 imap 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 mail_extra_groups: mail mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: prefetch In dovecot-ldap.conf: hosts = localhost dn = <dn> dnpass = <dnpass> sasl_bind = no auth_bind = yes ldap_version = 2 base = <ldap-base-dn> pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid, gidNumber=userdb_gid,mailQuota=quota,mailHost=proxy If I set the mailHost attribute for a user as "localhost" or "127.0.0.1", I get the following error message in syslog: mail.err: Sep 27 13:01:06 dovecot: auth(default): Master request 5534.1 not found and at the same time, in info_log_path (/var/log/dovecot.log), I get the following messages: Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=<hidden> Info: auth(default): ldap(hoskeri,127.0.0.1): bind search: base=dc=deeproot,dc=co,dc=in filter=(&(objectClass=posixAccount)(uid=hoskeri)) Info: auth(default): ldap(hoskeri,127.0.0.1): result: uid(user)=hoskeri uidNumber(userdb_uid)=1004 homeDirectory(userdb_home)=/home/hoskeri mailHost(proxy)=127.0.0.1 gidNumber(userdb_gid)=1000 Info: auth(default): ldap(hoskeri,127.0.0.1): bind: dn=uid=hoskeri,ou=People,dc=deeproot,dc=co,dc=in Info: auth(default): client out: OK 1 user=hoskeri proxy pass=<hidden> # I notice that in the above line, proxy does not any value associated with it. Can't understand why. Info: auth(default): master in: REQUEST 1 5534 1 Info: auth(default): master out: NOTFOUND 1 Info: imap-login: Internal login failure: user=<hoskeri>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured I have not yet tried to proxy to some other host. Also, I have another question. In the setup I need to do, I need to use the hostname itself for the mailhost, and not IPs, but I understand that it is not implemented and only IP addresses are acceptable. Any major reason why this is so? Could I help implement it? Thanks in advance... -Abhijit

3 3

[Dovecot] Testing sieve filter
by Cliff Meece 28 Sep '07

28 Sep '07

Hi, I am trying to get sieve working with dovecot. Dovecot itself is working fine, and I have the following config: root@master:/var/log# dovecot --version 1.0.rc2 root@master:/var/log# dovecot -n # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail default_mail_env: maildir:/var/mail/%u auth default: passdb: driver: pam userdb: driver: passwd I have this in my lda protocol: mail_plugins = cmusieve And I have created a .dovecot.sieve in both ~ and /var/mail/$user/ that looks like this: require "fileinto"; if exists "X-Spam-Flag" { fileinto "Junk"; } No mail gets moved to the junk folder, nut it does arrive in my inbox with the X-SPAM-Flag: Yes header. How do I troubleshoot this? I don't see anywhere in the logs any errors or any mention whatsoever of filtering activity or failure. I have seen numerous pages on how to set this up, but they invariably focus on setting up virtual users, which I do not need, so it isn't clear which steps I can safely ignore. thanks in advance, Cliff

2 4

Re: [Dovecot] Testing sieve filter
by Cliff Meece 28 Sep '07

28 Sep '07

I'll upgrade if I need to, but that is the most current dpkg for my distribution, and I'd really rather not compile from source if I don't have to. Charles Marcus wrote: > On 9/28/2007, Cliff Meece (cliff(a)cliffandkim.org) wrote: >> I am trying to get sieve working with dovecot. Dovecot itself is >> working fine, and I have the following config: >> >> root@master:/var/log# dovecot --version >> 1.0.rc2 >> root@master:/var/log# dovecot -n > > Stop - upgrade - repeat... > > This is too old to be messing with... >

1 0

[Dovecot] Documentation to create plugins.
by "Fábio M. Catunda" 28 Sep '07

28 Sep '07

hi! Is there any documentation to guide me how to create a dovecot plugin? I'm trying to read the code, but I'm not a good C programmer. I have been able to copy the mail-log plugin into copy-log, edited about 4 lines of code, then I edited Makefiles and configure, now I'm able to compile, install and use my "new" plugin. Anyway, any help is appreciated. Thankz! !DSPAM:46fd34b1153407177711712!

1 0

Re: [Dovecot] v1.0 vs 1.1b re: Postfix and Dovecot LDA
by Jerry Yeager 28 Sep '07

28 Sep '07

>>> From: Bill Cole <dovecot-20061108(a)billmail.scconsult.com> (stuff cut out) > > That looks like a bug. A program that calls setgroups() must be > running as root. It seems to me that a code path leading to such a > call should probably be able to identify that issue before the call > and provide a better failure message than translating EPERM into its > standard meaning.... > > The interesting question would be: why does deliver want to call > setgroups() at all? > > I am not sure why it would need to do this either. It (deliver) is not handing things off to another app to finish things up. <snip><snip> > > I'd love to take credit, but I thought that was about the LDA with > Sendmail, which is rather different, and Rich was running 1.0.3... > > In any event, I won't go so far as to say that running deliver as > setuid root is actively dangerous, but it feels wrong to me and I > wouldn't do it. That may be from too much exposure to bizarre attacks > through delivery agents in the Dark Ages. > > That it works without being setuid on Linux is a touch odd. > > The mystery deepens! I have it (deliver) in a restricted access folder as a standard safety precaution, but as most of these "jails" end up being only safe for a short time I have again gone back to using Postfix as the deliver. Timo has from time to time mentioned that he was thinking that deliver needed to be rewritten. hmmm. I still give you and Rich credit though, if you had not mentioned the ideas behind Sendmail and LDA, it would most likely taken much longer before I read that wiki entry and gave that approach a try, instead of trying to find the missing setting for changing groups that the error message wants fixed. > -- > Bill Cole > bill(a)scconsult.com > > > > ------------------------------ > > Message: 7 > Date: Thu, 27 Sep 2007 17:07:28 -1000 (HST) > From: Julian Cowley <julian(a)lava.net> > Subject: [Dovecot] Dovecot raw backtrace when copying to folder > To: dovecot(a)dovecot.org > Message-ID: <alpine.LRH.0.9999.0709271646190.28814(a)taurus.cesta.com> > Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII > > Seeing a problem with a certain user causing dovecot to crash when > copying > mail to a folder. This looks similar to a bug someone on the > mailing list > posted recently. > > Since the backtrace mentions the index, I tried deleting all of the > index > files for the user (including subfolders) but it had no effect. > Seems that > the bug still happens when creating the index for the first time. > > Unfortunately, I can't pin down if there is a particular message > causing > the problem but I'll see if I can track it using strace. > > Lines are broken for clarity. This is dovecot 1.0.5 on CentOS 4.5. > > Sep 27 16:41:42 cookie dovecot: imap-login: Login: user=<user@domain>, > method=PLAIN, rip=::ffff:xx.xx.xx.xx, lip=::ffff:yy.yy.yy.yy, TLS > Sep 27 16:41:53 cookie dovecot: IMAP(user@domain): Trying to > allocate 0 bytes > Sep 27 16:41:53 cookie dovecot: IMAP(user@domain): Raw backtrace: > imap [0x80ad7d4] -> > imap [0x80ad239] -> > imap [0x80b5624] -> > imap(i_malloc+0x1b) [0x80b0e1b] -> > imap [0x8083037] -> > imap [0x80833e6] -> > imap(index_storage_search_init+0xf4) [0x80836f4] -> > imap(cmd_copy+0x145) [0x8056d15] -> > imap(cmd_uid+0x7c) [0x805a74c] -> > imap [0x805b2d5] -> > imap [0x805b25e] -> > imap(_client_input+0x8c) [0x805b43c] -> > imap(io_loop_handler_run+0x169) [0x80b3e09] -> > imap(io_loop_run+0x28) [0x80b3178] -> > imap(main+0x49f) [0x806384f] -> > /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x506de3] -> > imap [0x8055db1] > Sep 27 16:41:53 cookie dovecot: child 26079 (imap) killed with > signal 6 > > > ------------------------------ > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > End of dovecot Digest, Vol 53, Issue 77 > ***************************************

1 0

Re: [Dovecot] Auto create folder(s)
by Lars Stavholm 27 Sep '07

27 Sep '07

Thomas Mueller wrote: > hi lars Hi. > if you're using PAM as pass-db: have a look at pam_mkhomedir.so I will. > if not -> maybe this is for you:http://wiki.dovecot.org/PostLoginScripting Even better. Thanks /Lars PS. Please keep on list. > Lars Stavholm schrieb: >> Hi All, >> >> does anyone know of a way to automatically create user folder(s)? >> Like creating a Spam folder on login if not already there. >> I've googled a bit but couldn't find anything relevant. >> >> Any advice appreciated >> >> R >> /Lars

7 10

[Dovecot] dovecot IMAPS + kmail
by Timothy Murphy 27 Sep '07

27 Sep '07

I notice that kmail does not allow an IMAP sub-folder to be created (from an IMAPS client). When I try, kmail says this cannot be done for one of the following reasons: Your access permissions may be inadequate to perform the requested operation on this resource. The location where the folder was to be created may not exist. A protocol error or incompatibility may have occurred. Is there any simple way of getting round this? KMail has no problem creating top-level IMAP folders.

3 5