- dovecot - dovecot.org

[Dovecot] IMAP QUOTA
by Arun Gupta 30 May '13

30 May '13

Hi, I configured imap quota on dovecot-2.0 with backend Maildir++, after exceeding user quota the sender receiving bounce mails, Is there any way that after exceeding user quota the mail will deliver somewhere else like user spool area? so that after increasing quota user will get the mails. -- Regards, Arun Kumar Gupta ------------------------------------------------------------------------------------------------------------------------------- This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. -------------------------------------------------------------------------------------------------------------------------------

4 3

Re: [Dovecot] IMAP QUOTA
by Arun Gupta 30 May '13

30 May '13

Hi, Thanks for replying... Dear Steffen I search about "slurp" plugin but didn't get it if possible kindly provde me the doc, link etc for the same. Regards, Arun Gupta On Tue, 28 May 2013, Arun Gupta wrote: > I configured imap quota on dovecot-2.0 with backend Maildir++, after > exceeding user quota the sender receiving bounce mails, Is there any way that > after exceeding user quota the mail will deliver somewhere else like user > spool area? so that after increasing quota user will get the mails. Check out the "slurp" plugin and let your MTA deliver mails to, say, /var/mail/<uid> . You will have no Sieve rules then, I think. However, some sort of quota enforcing you will need there, too. - -- Steffen Kaiser ------------------------------------------------------------------------------------------------------------------------------- This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. -------------------------------------------------------------------------------------------------------------------------------

4 4

[Dovecot] Sieve/pigeonhole with Exim and Dovecot LDA
by Sebastian Arcus 30 May '13

30 May '13

I am trying to configure my Dovecot installation to provide Vacation/Out-of-the-office emails using the Sieve plugin. My setup is a little bit peculiar: Internet Internet | ^ V | Provider's POP3 server Provider's SMTP server | ^ V | -------------- getmail | my server | | V | Dovecot LDA ---> Sieve/vacation -----> Exim | V Dovecot my server --------------- Sorry for the ASCII art above - I thought it would be quicker than trying to explain. The trouble I'm having is getting the Dovecot LDA to send successfully through the local exim instance out-of-office replies back to the provider's smtp server - when receiving fresh email from the provider (through getmail). Dovecot LDA tries to send the replies - but Exim freezes them because they don't contain the sender data in the format Exim wants it. Exim can either receive sender info: 1. On the command line, after the "-f" command line switch (but only when called by root or other users passed under "trusted_users" in exim.conf). 2. In the header of the email - in the "From:" field - but only, apparently, if it was called with the "-t" switch. Full exim command line documentation here: http://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_exim_comman… I can't figure out what command line options the Dovecot LDA is using when calling exim. I also couldn't find a way to get Dovecot LDA to pass extra options to exim, when trying to send email. The exim log has the following: 2013-05-20 15:35:15 1UeRBB-0001xc-Ar Frozen (message created with -f <>) I've inspected the frozen message - and it has the correct sender in the "From:" field - but it seems that exim isn't using that, because it wasn't called with the "-t" option. In dovecot.conf, I have the following for Dovecot LDA and sieve: protocols = imap sieve protocol lda { log_path = /var/log/dovecot/dovecot-deliver.log info_log_path = /var/log/dovecot/dovecot-deliver-info.log postmaster_address = admin(a)mydomain.co.uk hostname = mydomain.co.uk mail_plugins = sieve mail_plugin_dir = /usr/lib/dovecot sendmail_path = /usr/sbin/exim } service managesieve-login { inet_listener sieve { port = 4190 } } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } Dovecot LDA is called by getmail using the vmail user - and using the same user it is trying to call exim to deliver the out-of-office replies. I'm using Dovecot 2.2.1 with pigeonhole 0.4.0. I can post the rest of dovecot.conf if it would help. I've read through the stuff at dovecot.org - but all the Dovecot LDA and exim info refers to Exim passing email to Dovecot using Dovecot LDA - not Dovecot LDA sending email out using Exim.

2 8

Re: [Dovecot] Dovecot 2.2 build rpm on Centos6
by Burak GÜRER 30 May '13

30 May '13

On 30-05-2013 10:52, Arto Saraniva wrote: > >> -----Original Message----- >> From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] >> On Behalf Of Burak GÜRER >> Sent: Thursday, May 30, 2013 10:34 AM >> To: Nikolaos Milas >> Cc: Dovecot Mailing List >> Subject: Re: [Dovecot] Dovecot 2.2 build rpm on Centos6 >> >> On 27-05-2013 16:56, Nikolaos Milas wrote: >>> On 27/5/2013 1:07 μμ, Birta Levente wrote: >>> >>>> I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos >>>> 6.4 >>> You may want to try: >>> >>> dovecot-2.2.2-2.noa.el6.src.rpm >>> >>> which produces: >>> >>> dovecot-2.2.2-2.noa.el6.x86_64.rpm >>> dovecot-debuginfo-2.2.2-2.noa.el6.x86_64.rpm >>> dovecot-devel-2.2.2-2.noa.el6.x86_64.rpm >>> dovecot-mysql-2.2.2-2.noa.el6.x86_64.rpm >>> dovecot-pgsql-2.2.2-2.noa.el6.x86_64.rpm >>> dovecot-pigeonhole-2.2.2-2.noa.el6.x86_64.rpm >>> >>> available at: http://www.noa.gr/rpmfiles/ >>> >>> This package is using LTB Project's Openldap RPMs for LDAP linking: >>> >>> http://ltb-project.org/wiki/download#openldap >>> >>> The above Dovecot SRPM has evolved from fakessh's rpms: >>> http://ns.fakessh.eu/rpms/ and I like it because it is clean and >> clear >>> (to me, at least). >>> >>> Nick >> another question.. anybody built dovecot 2.2 on rhel/centos 5 >> >> there is any knowhow or any builded pack > http://www.city-fan.org/ftp/contrib/mail/ > > -arto > thanks arto

1 0

[Dovecot] Dovecot 2.2 build rpm on Centos6
by Birta Levente 30 May '13

30 May '13

Hi list, I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 rpmbuild --define 'rhel 64' -ba dovecot-2.2.spec I get this error: checking for C compiler default output file name... configure: error: in `/home/builder/rpmbuild/BUILD/dovecot-2.2.2': configure: error: C compiler cannot create executables See `config.log' for more details. (config.log attached) What I missing? I'm not totally beginner, built dovecot 2.1 rpm-s many times same way like this, but not know mutch about building rpms and with this I just can get to work. Thank you! Levi

6 10

[Dovecot] Perfect LDAP tree
by Evgeny Basov 30 May '13

30 May '13

Hello everybody and Timo. I have the next problem. With LDAP tree like ou=mail | - dc=example1.com,ou=Mail | - mail=box1(a)example1.com,dc=example1.com,ou=Mail | - mail=box2(a)example1.com,dc=example1.com,ou=Mail … | - dc=example2.com,ou=Mail | - mail=box1(a)example2.com,dc=example2.com,ou=Mail | - mail=box2(a)example2.com,dc=example2.com,ou=Mail … and settings in dovecot configuration files auth_bind = yes auth_bind_userdn = mail=%u,dc=%d,ou=mail base = ou=mail user_attrs = \ =home=/var/vmail/%Ld/%Ln, \ =quota_rule=*:storage=%{ldap:mailQuota}M user_filter = (&(objectClass=mailUser)(accountStatus=active)(mail=%u)) pass_attrs = \ =user=%{ldap:mail}, \ =proxy_maybe=yes, \ =host=%{ldap:mailHost}, \ =userdb_home=/var/vmail/%Ld/%Ln, \ =userdb_quota_rule=*:storage=%{ldap:mailQuota}M pass_filter = (&(objectClass=mailUser)(accountStatus=active)(mail=%u)) iterate_attrs = mail=user iterate_filter = (&(objectClass=mailUser)(accountStatus=active)) all works fine. But my soul of perfectionist do not like this configuration because in every mailbox record duplicated information about domain: mail=box1(a)example2.com and dc=example2.com I want to set next LDAP tree ou=mail | - dc=example1.com,ou=Mail | - mail=box1,dc=example1.com,ou=Mail | - mail=box2,dc=example1.com,ou=Mail … | - dc=example2.com,ou=Mail | - mail=box1,dc=example2.com,ou=Mail | - mail=box2,dc=example2.com,ou=Mail … but I don't understand how to limit query to box1(a)example1.com in dc=example1.com,ou=mail without using base=dc=%d,ou=Clients,o=m and how to get working iterate query for all boxes to get list box1(a)example1.com box2(a)example1.com box1(a)example2.com box2(a)example2.com in some command like doveadm quota recalc -A. Is it possible? How to take it?

2 2

[Dovecot] imap/pop problem
by MP Netsai 30 May '13

30 May '13

Dear All, I hope you can help me on this trouble i am getting. I cant seem to get email even though i have given the correct directory for mail location. Here is my config: ===== # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0 ext4 auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 1001 last_valid_uid = 1001 mail_debug = yes mail_gid = exim mail_location = maildir:/var/mail/virtual/%d/%n mail_uid = exim namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" service auth { unix_listener auth-userdb { group = exim mode = 0600 user = exim } } ssl_cert = </usr/local/etc/exim/exim.cert ssl_key = </usr/local/etc/exim/exim.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } ===== the virtual email directory is as follows: ===== root@peyote:/var/mail/virtual# ls -l drwx------ 9691 exim exim 266240 May 28 16:17 mydomain.co.zw ===== Mail is moving ok, into the virtual directory. I just cant seem to pop them out of there. I hope someone can get to point me in the right direction. Regards,

2 2

Re: [Dovecot] system account delivery userdb authentication
by Ben Morrow 29 May '13

29 May '13

[Please keep replies on the list.] At 6AM +0200 on 29/05/13 you (Yann Shukor) wrote: > > Although simpler to set up, I chose to steer clear of the single user > representing 'all' because I liked the idea of giving users access to > Usermin allowing them to manage their own password and vacation msg > (+filtering, ...) and furthermore they could login with their username > (domain-less). While it's often convenient to make a distinction between 'system' and 'virtual' users, Dovecot doesn't actually know the difference. It just looks users up in the passdb and userdb you have configured. This means it's perfectly straightforward to do a completely 'virtual user' setup, and then change the passdb to 'pam', which will let the users log in with their ordinary Unix password. To allow users to log in with just a username, all you need to do is make sure the users in the userdb and passdb are listed that way. Userdb passwd and passdb pam naturally are, but there's nothing to stop you using other userdbs if you want to. The only trick here is that if you're using LDA/LMTP then incoming deliveries will (or, at least, usually should) be addressed to a full email address, so you need auth_username_format to trim that back to a username. I don't know anything about Usermin, but if it is trying to set up traditional procmail filtering and vacation(1), you may be in trouble. Or, at least, you may have to give up on using Dovecot to deliver the mail and let Postfix's local(8) and procmail deliver it into maildirs themselves. If you're happy with this, this isn't a problem for Dovecot, but it might be better to go with Sieve filtering instead. Sieve is a newish mail filtering language, designed primarily to be safe (procmail has a nasty habit of letting users run arbitrary programs). Dovecot's LDA has a pretty complete sieve implementation called Pigeonhole (you may need to install it separately), which also supports a protocol called ManageSieve designed for uploading sieve scripts remotely. There are plugins for some webmail systems (and some desktop mail clients, for that matter) which let the user edit their filters in a gooey way; this includes setting up vacation messages. I use Roundcube webmail for this purpose; it also has a perfectly good PAM password- changing plugin. Ben

1 0

[Dovecot] dsync
by Erik Colson 29 May '13

29 May '13

Hi Is dovecot dsync considered an alternative to offlineimap (or others) when both distant and local are IMAP dovecot servers ? I used offlineimap for this, but somehow offlineimap got messed up (more than once, but without me able to explain how it happened). So I'm considering dsync for this purpose... Thanks! -- erik

1 0

[Dovecot] Enable IMAP only for certain users/IP
by Simone Marx :: Edinet Srl 29 May '13

29 May '13

Hi, I'm trying to config dovecot to enable IMAP protocol only for certain IPs and users. The logical steps I've followed are: 1. If a user is trying to login from an IP that I've authorized ( listed in a file) the request is authorized. 2. If not, if the user is listed in a second file the request is authorized. 3. If also this check fails the request is rejected. I'm using PAM for passdb and a passwd-file for userdb: passdb { driver = pam args = session=yes failure_show_msg=yes max_requests=16 cache_key=%u%r%l dovecot-%s } userdb { driver = passwd-file args = /etc/passwd-dovecot } In /etc/pam.d/ there are two files: dovecot-pop3 dovecot-imap dovecot-pop3: #%PAM-1.0 @include common-auth @include common-account @include common-session (for this protocol everything works fine, I don't want to limit it.) dovecot-imap: #%PAM-1.0 @include common-auth auth sufficient pam_listfile.so item=rhost sense=allow file=/etc/dovecot/imaphosts onerr=fail auth required pam_listfile.so item=user sense=allow file=/etc/dovecot/imapusers onerr=fail @include common-account @include common-session If I'm not wrong, once the user is authenticated, PAM checks if the remote IP address is in imaphosts; if it's true, it returns PAM_SUCCESS and stops the execution of the auth block, else if it's false, PAM executes the next line, verifying the presence of the username in imapusers file; if found, then return PAM_SUCCESS, else fail. If this can work, I've a problem with pam_listfile.so and IP addresses: I want to do something smarter than specifying 2^11 IP addresses instead a /21 or IP/netmask Are there alternatives for doing it better? Thanks. Sincerely, Simone Marx.

2 4