- dovecot - dovecot.org

[Dovecot] CVS forked into development/stable branches
by Timo Sirainen 08 May '06

08 May '06

New branch created to CVS: branch_1_0 It's going to stabilize into v1.0 Dovecot, hopefully somewhat soon. I'll start adding new larger features into HEAD, so you might want to switch to branch_1_0 if you're currently using Dovecot from CVS. You can do this with: cvs up -r branch_1_0 The nightly snapshots are from branch_1_0, at least for now.

1 0

[Dovecot] different login_greeting for pop3 & imap?
by Geert Hendrickx 08 May '06

08 May '06

Hi, I have a tiny feature request for Dovecot: could it optionally have different login_greetings for pop3 and imap connections? e.g. I want it to say "Dovecot on pop.mycompany.com ready" on pop3 connections and "Dovecot on imap.mycompany.com ready" on imap connections. Would that be possible? TIA, Geert

3 5

[Dovecot] configuring dovecot-lda takes forever...
by Joseba Torre 08 May '06

08 May '06

Hi, I want to try dovecot-lda, but the ./configure doesn't seem to finish... I've followed the installation instructions: cvs -d :pserver:anonymous@dovecot.org:/home/cvs co dovecot-lda cd dovecot-lda/ ./autogen.sh ./configure --with-dovecot=../dovecot (dovecot source tree -from cvs- is in ../dovecot) Everything seems to go ok but the message config.status: creating Makefile never ends. The problem seems to be in this process: sed -f ./confstatn25334/subs-3.sed (i can attach the file if needed). Any hint? Aaaaaaaaaaagur.

3 3

[Dovecot] dovecot error: unrecognized event
by dovecot＠bengrimm.net 07 May '06

07 May '06

If you're using the FreeBSD port: Go to /usr/ports/mail/dovecot Edit Makefile Find the line: .if !defined(WITHOUT_KQUEUE) Change it into: .if defined(WITH_KQUEUE) Then: make deinstall && make install Worked for me.

1 0

[Dovecot] Dovecot EOF bug on FreeBSD 6.0
by Matt Bostock 06 May '06

06 May '06

Hello, We're running Dovecot 1.0.7 on FreeBSD 6.0. Now and then I'll see a POP error ('EOF'), which is remedied simply by restarting Dovecot. Is this a known issue? Kind regards, Matt

1 0

[Dovecot] rebuilding dovecot 1.0 beta7 at.src.rpm mysql error
by dave 06 May '06

06 May '06

hi all i'm trying to rebuild the 1.0 beta 7 src rpm from atrpms.net to use mysql 5, instead of mysql 4 but i'm having issues when it gets to the mysql part of the make i have mysql 5 installed (via mysql.com rpm's) i changed the spec file where it says Buildrequires to say MySQL-devel (instead of mysql-devel) but it always comes back with this error, and i don't know what it means, i also tried leaving it as mysql-devel, but still get the same error when i run rpmbuild -ba dovecot.spec && rpm -Uvh --force ../RPMS/i386/dovecot* am i doing this completely wrong, is there something else i need to do to be able to use mysql 5? /usr/lib/mysql/libmysqlclient.a(sha1.o)(.text+0x60): In function `sha1_result': : multiple definition of `sha1_result' ../lib/liblib.a(sha1.o)(.text+0x8e7):/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib/sha1.c:233: first defined here /usr/bin/ld: Warning: size of symbol `sha1_result' changed from 191 in ../lib/liblib.a(sha1.o) to 126 in /usr/lib/mysql/libmysqlclient.a(sha1.o) collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.84952 (%build) thanks dave -- http://dtracorp.com

1 0

[Dovecot] Sending email over IMAP?
by Marc Perkel 06 May '06

06 May '06

I'm advocating for a change in the IMAP specification to allow outgoing email to be sent over the same connection as incoming rather that having to separately configure outgoing SMTP email. There are two significant advantages to this concept. 1) It would greatly simplify setup for clients as they would only have to configure one connection rather than two. 2) Spam reduction by authentication. The sending of email over the same connection tells the server that the person who is the sender of the email also has demonstrated they have access to read the account. This would be a powerful whitelisting criteria for eliminating fake senders. So - my question. It seems that it would be easy to do this if there were a standard. Dovecot would merely hand incoming email off to the outgoing SMTP server. Besides the difficulty of getting a standard created, am I right on my assumptions?

11 26

[Dovecot] UID and GID problems
by Simon Windsor 06 May '06

06 May '06

Hi I have been using dovecot for a while now to support a number of virtual users via a postgres table. The dovecot user chown is dovecot:dovecot, and for each domain, I use a single GID, so for example domain1 is 1001:dovecot, domain2 is 2001:dovecot. All directories are owned by 1001:dovecot or 2001:dovecot. The works well most of the time, but occasionally, some user files are owned by dovecot:dovecot, and others by gid:dovecot. Is this a know issue? Any help would be appreciated. Simon -- Simon Windsor Eml: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07960 321599

1 0

[Dovecot] dovecot LDA w/virtual domains and postfix
by Leah Cunningham 05 May '06

05 May '06

Hi, I've been trying to follow the documentation that I am finding, but am running into trouble getting things set up correctly for postfix + virtual domains (using ldap) with dovecot LDA. I can get it to work without LDA, but I'm running into permissions problems when I try to run with LDA. I am wondering if anyone has any good examples of configuring this. I basically have a 'vmail' user (1015) that owns a /var/vmail/domains directory tree. I have set the following in postfix master.cf: # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -d ${recipient} In main.cf dovecot_destination_recipient_limit = 1 virtual_transport = dovecot virtual_mailbox_base = /var/vmail/domains virtual_mailbox_maps = ldap:/etc/postfix/ldap-mailbox.cf virtual_mailbox_domains = ldap:/etc/postfix/ldap-vdoms.cf virtual_uid_maps = static:1015 virtual_gid_maps = static:12 home_mailbox = Maildir/ and in dovecot.conf: protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = /etc/ssl/certs/sauerkraut.heinous.org.crt ssl_key_file = /etc/ssl/private/sauerkraut.heinous.org.key mail_extra_groups = mail valid_chroot_dirs = /var/vmail/domains default_mail_env = maildir:/var/vmail/domains/%d/%n/mail protocol lda { postmaster_address = postmaster(a)frauerpower.com } protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } user = root } auth default_with_listener { mechanisms = plain userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot-auth-master mode = 0600 user = vmail group = mail } } } plugin { } However, I must be missing something. I get the following when trying to send the user a message: setuid(1015) failed: Operation not permitted Doing 'postmap -q leah(a)frauerpower.com ldap:/etc/postfix/ldap-mailbox.cf' returns 'frauerpower.com/leah/mail/' which, in the non LDA mode worked okay, plonking the mail under /var/vmail/domains/frauerpower.com/leah/mail How is this sort of thing normally set up? Apologies in advance for my ignorance, I am pretty new to dovecot. Leah

2 5

Saving Direct to Shared Mailbox (Was: Re: [Dovecot] Sending email over IMAP?)
by Timothy White 05 May '06

05 May '06

Thinking along similar lines to this sending email via IMAP... What I am thinking, is using Shared Folders/Mailbox's, like mailing lists. We have the power of ACL's, and if you have the appropriate permissions, you can 'append' emails to the folder. Except, when you think of a mailing list, you usually just hit reply. One of the projects I am working on, will be setup with a number of shared folders, an 'official' folder that everyone has read access to, (probably thier own index files as well, so the Seen flag isn't global), and a few admins have write access to. The problem still comes, as to the easiest way to 'send emails' to the folder. I could set up a virtual user, that delivers to that folder, but then you need a second system of ACL's that determine who can send emails to the folder.... Unless, Dovecot LDA handles that.... So, other than lack of client support for saving directly to a folder, instead of sending to a folder... Can Dovecot LDA do what I want, or be made to do what I want? I have no problems having a 'virtual' user that people send the emails to, as long as Dovecot LDA will handle the ACL's for it as well. Any ideas of how to solve this problem, or if Dovecot LDA can/will do it? Tim -- Linux Counter user #273956

6 7