- dovecot - dovecot.org

[Dovecot] 'doveadm quota get' dictionary SQL query ignores specified '@domain' part of username. bad config or bug?
by Rich 19 Oct '11

19 Oct '11

Hi, I'm setting up SQL quota usage in Dovecot2. I've created a MAILBOX parameter table, 'PARAMS', that contains unique <user>@<domain> pairs, with quota data. mysql> select * from PARAMS; +----+------------------------+------------+-------------+------------+ | ai | MAILBOX_user_domain | quota | quota_bytes | quota_msgs | +----+------------------------+------------+-------------+------------+ | 1 | myuser(a)domain1.com | 1073741824 | 0 | 0 | | 2 | myuser(a)domain2.com | 1000000000 | 0 | 0 | +----+------------------------+------------+-------------+------------+ 2 rows in set (0.00 sec) I've specified dict usage for quota, /etc/dovecot/dovecot.conf !include conf.d/*.conf protocols = imap lmtp dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } created the maps, /etc/dovecot/dovecot-dict-sql.conf.ext connect = host=/var/run/mysql/mysql.sock dbname=my_db user=my_user password=my_pass map { pattern = priv/quota/storage table = PARAMS username_field = MAILBOX_user_domain value_field = quota_bytes } map { pattern = priv/quota/messages table = PARAMS username_field = MAILBOX_user_domain value_field = quota_msgs } assigned the global values and backend, /etc/dovecot/conf.d/90-quota.conf plugin { quota = dict:User Quota::proxy::quota quota_rule = *:storage=1GB:messages=10000 quota_rule2 = Trash:storage=+10%% } and specified the user iteration query /etc/dovecot/sql/virtmail-userdb-sql.cf driver = mysql connect = host=/var/run/mysql/mysql.sock dbname=my_db user=my_user password=my_pass user_query = CALL UserDBQuery('%n','%d'); iterate_query = SELECT `MAILBOX_user_domain` AS user FROM `PARAMS`; Verifying operation with with `doveadm`, I get a result from a !error query, doveadm quota get -u myuser(a)domain1.com Quota name Type Value Limit % User quota STORAGE 0 1048576 0 User quota MESSAGE 0 10000 0 doveadm quota get -u myuser(a)domain2.com Quota name Type Value Limit % User quota STORAGE 0 1048576 0 User quota MESSAGE 0 10000 0 But notice that there's no specificity by *domain*. Despite being provided the full <user>@<domain>, matched to the map, username_field = MAILBOX_user_domain the Dovecot dict query seems to ignore the <domain> part, and simply matches on the first of the tow identical <user> parts. Specifying "-A" doesn't help, doveadm quota get -A Username Quota name Type Value Limit % myuser(a)domain1.com User quota STORAGE 0 1048576 0 myuser(a)domain1.com User quota MESSAGE 0 10000 0 myuser(a)domain2.com User quota STORAGE 0 1048576 0 myuser(a)domain2.com User quota MESSAGE 0 10000 0 What needs to be done to get domain-specificity in the 'doveadm quota get' query? Is my configuration off, or incomplete, or is this a bug? Thanks, Rich

1 1

Re: [Dovecot] "doveadm log reopen" don't reopen separate lmtp log
by Henrik Larsson 18 Oct '11

18 Oct '11

I still see the issue below. Is there anyone running separate LMTP logging that could check if they experience the same issue? Best regards Henrik Larsson -------- Original Message -------- Subject: "doveadm log reopen" don't reopen separate lmtp log Date: Sun, 25 Sep 2011 00:23:49 +0200 From: Henrik Larsson <dovecot-user(a)spambox.dk> To: dovecot(a)dovecot.org Dear all I have setup separate pop3/imap log "/var/log/dovecot" and lmtp delivery log "/var/log/dovecot-deliver". After rotating logfiles, i run "doveadm log reopen". I see that my pop3/imap log "/var/log/dovecot" is used straight away, but my lmpt log "/var/log/dovecot-deliver" isn't used at first. After some time, usually a few minutes, logs are being written to this file anyway. But if I compare this to my maillog, it misses some deliveries just after the log rotation. Is there any problems with this configuration that should be corrected? --cut-- # doveconf -n # 2.0.15: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-STABLE amd64 auth_mechanisms = plain login digest-md5 cram-md5 first_valid_uid = 125 hostname = mail.larsson.it listen = * log_path = /var/log/dovecot mail_plugins = fts fts_squat zlib mail_privileged_group = postfix mail_temp_dir = /var/db/dovecot managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date namespace { inbox = yes location = prefix = separator = . type = private } namespace { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = squat fts_squat = partial=4 full=10 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { unix_listener /home/mail/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service lmtp { executable = lmtp -L unix_listener /home/mail/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/mail-chained.crt ssl_key = </etc/ssl/mail.key userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { log_path = /var/log/dovecot-deliver mail_plugins = fts fts_squat zlib sieve } protocol lda { mail_plugins = fts fts_squat zlib sieve } protocol imap { mail_plugins = fts fts_squat zlib imap_zlib } --cut-- Best regards Henrik Larsson

2 3

[Dovecot] mail_location in LDAP and variables
by Joseba Torre 18 Oct '11

18 Oct '11

Hi, Is it posible to use variables in mail_location when taken from ldap? How? I've tried mdbox:/buzones2/'%n'/mdbox mdbox:/buzones2/"%n"/mdbox mdbox:/buzones2/%n/mdbox but %n is never replaced by its value. Thanks! -- Joseba Torre. Vicegerencia de TICs, área de Explotación

2 2

[Dovecot] LDA/Postfix with quotas and without LMTP
by Steve Fatula 18 Oct '11

18 Oct '11

Reading the wiki page for dovecot2 and LDA/Postfix, the system users section (all mail delivery goes to system users)... It shows you can simply use postfix mailbox_command. There is this additional comment: "This command doesn't do a userdb lookup. If you want that (e.g. for per-user quota lookups) you need to add -d "$USER" parameter." So, i added that. Once adding it, I find I get an error: dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied Using mailbox_command in Postfix means that dovecot-lda is running as the system user getting the mail. Which means it can't access the socket file. Of course, one can simply use mode 666 on it, but, then people can use it to find out information according to the doc, which I do not want. So, I am not sure why the doc says to add -d for per user quotas, without also mentioning the problem with doing that. I don't see how it can work? Assuming I need per user quotas, and I don't want to use LMTP, is there a good way around this without the security issue? Steve

2 2

[Dovecot] Syntax to specify sdbox: mail_location path?
by mephistopheles＠operamail.com 18 Oct '11

18 Oct '11

I'm implementing sdbox. In conf.d/10-mail.conf, with "maildir:" mail_location = maildir:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/new/ With "sdbox:" mail_location = sdbox:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/mailboxes/INBOX/dbox-Mails. How do I get rid of the '/mailboxes/' and '/dbox-Mails/' path components so sdbox stores in: /my_mailbox_path/%d/%n/INBOX @ wiki2.dovecot.org/MailboxFormat/dbox#Alternate_storage points out that 'ALT=' can change the *lookup* location, and messages can be *moved* to ALT storage using 'doveadm altmove'. Unclear what TAGS are available/used for 'sdbox'.

2 1

[Dovecot] Rare error with concurrent users searching with fts-solr
by Antonio Perez-Aranda 18 Oct '11

18 Oct '11

Hi all, If I start two o more connections with diferent users that make a search text to solr I get this message many times: Error: fts_solr: Query didn't return uid If I repeat the test about 2000 times, with only one user concurrent, with 60 diferent users, without concurrent, I get between 0. If I repeat the test about 2000 times, with 2 users concurrent, I get between 3 or 10 errors. If I repeat the test about 2000 times, with 4 users concurrent, I get between 10-20 errors. After see this error, I set a tcpdump to try to watch the SOLR XML and GET, I can watch that Solr send a xml like this: <response></response> with 200 as http status When the normal response is like this <response> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">1</int> <lst name="params"> <str name="fl">uid,score</str> <str name="sort">uid asc</str> <str name="q">BLABLABLA</str> <str name="fq">+user:"ANYUSER" +uidv:1208469916 +box:"ANYFOLDER" -ns:[* TO *]</str> <str name="rows">1</str> </lst> </lst> <result name="response" numFound="0" start="0" maxScore="0.0"/> </response> At first, I think that the problems it's in Solr, but after get all GET from tcpdump, I make a python script with urllib2 and send it all to Solr with the same concurrency and I can't get any error or "empty response" Have someone made a intensive concurrency tests over Dovecot + Solr ? -- Antonio Pérez-Aranda Alcaide aperezaranda(a)yaco.es Yaco Sistemas S.L. http://www.yaco.es/ C/ Rioja 5, 41001 Sevilla Teléfono +34 954 50 00 57 Fax +34 954 50 09 29

2 1

[Dovecot] 2.1 Plans
by Steve Fatula 18 Oct '11

18 Oct '11

Back in early 2010, Timo posted about a potential 2.1 feature to in essence reduce the number of imap/pop3 processes using various techniques since the code already supports multiple connections. It even went as far as moving all idle connections. I don't see this on the 2.1 roadmap. Is it still planned perhaps for 2.1? Thousands of imap processes going away is a great thing for me! So, just curious. Reference: http://dovecot.org/list/dovecot/2010-January/046148.html Steve

2 1

[Dovecot] Convert-tool maildir > mbox
by Bertrand Jacquin 18 Oct '11

18 Oct '11

Timo, Is seems that this commit broke convertion from Maildir to Mbox using dovecot 1.2 convert-tool binary : 2009-07-09 Timo Sirainen <tss(a)iki.fi> * src/plugins/convert/convert-storage.c: convert plugin: Fixed changing hierarchy separators in mailbox names when alt_hierarchy_char isn't set. [a9f719f9a509] <HEAD> Since, I get the following : $ convert-tool user1 /var/mail/example.com/user1 Maildir:/var/mail/example.com/user1 mbox:/var/mail/example.com/user1-mbox alt_hierarchy_char=_ Error: Mailbox conversion: Couldn't create mailbox Sent/test: Mailbox doesn't allow inferior mailboxes Error: Internal failure Strace give show me a failure after : access("/var/mail/example.com/user1/.Sent.test/cur", W_OK) = 0 stat("/var/mail/example.com/user1-mbox/Sent/test", 0x7fff843e73b0) = -1 ENOTDIR (Not a directory) write(2, "Error: Mailbox conversion: Couldn"..., 103Error: Mailbox conversion: Couldn't create mailbox Sent/test: Mailbox doesn't allow inferior mailboxes ) = 103 lstat("/var/mail/example.com/user1/.dovecot.convert.lock", {st_mode=S_IFREG|0644, st_size=12, ...}) = 0 unlink("/var/mail/example.com/user1/.dovecot.convert.lock") = 0 Is that somethinh known ? Didn't find anything interesting in archives. Maybe that kind of conversion have evolved since 2.0 ? Thanks, Beber

2 1

[Dovecot] doveadm mailbox list shows file system directories as mailboxes
by Jürgen Obermann 18 Oct '11

18 Oct '11

Hello. In our dovecvot we use mbox format with the default filesystem layout. Therefore it is not possible to have mailboxes which are subfolders of other mailboxes containing messages. The command "doveadm mailbox list" includes the file system directories, that contain only subfolders, as normal mailboxes in the output: archiv archiv/daemon archiv/dovecot Did I miss something in the dovecot configuration or is there a bug in the command "doveadm mailbox list"? # 2.0.13: /opt/local/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4v auth_verbose = yes disable_plaintext_auth = no listen = imap.hrz.uni-giessen.de localhost mail_fsync = always mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = mail_log notify managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = yes list = no location = prefix = Mail/ separator = / subscriptions = yes type = private } Thanks, Jürgen -- Hochschulrechenzentrum der | Mail: Juergen.Obermann(a)hrz.uni-giessen.de Justus-Liebig-Universitaet | WWW: http://www.uni-giessen.de/obermann/ Heinrich-Buff-Ring 44 | Tel: 0641-99-13054 (0641-99-13001) D-35392 Giessen, Germany | Fax: 0641-99-13009

3 2

Re: [Dovecot] Spammers attempting SASL Auth
by Tom Pawlowski 17 Oct '11

17 Oct '11

Take a look at: http://hg.dovecot.org/dovecot-2.0/file/962df5d9413a/src/auth/auth-request.c on line 536. That's the auth service catching illegal characters and rejecting the attempt. It'll happen with or without a valid user. So, working as it should. As for spammers trying to brute force valid logins, yep, pretty common. Higher rate of success if they can mail from a known good server and account. * Simon Brereton <simon.brereton(a)buongiorno.com> [2011-10-17 11:51:15 -0400]: > On 17 October 2011 11:31, Robert Schetterer <robert(a)schetterer.org> wrote: > > Am 17.10.2011 17:16, schrieb Simon Brereton: > >> Hi > >> > >> This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. > >> > >> Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] > >> Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars > >> Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 > >> Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known > >> > >> > >> Simon > >> > > > > this maybe a brute force attack,or more easy someone missconfigured his > > client , you may use fail2ban etc to block it > > not directly related to dovecot > > 17 queries in 30 seconds is not a misconfigured client :) > > And I'm already using Fail2Ban - but as someone on this list pointed > out recently, that doesn't apply if they try X attempts on the same > connection. Although, I don't think that was case here - maybe I > should update my dovecot jail with that illegal chars line. But, be > that as it may - all these attempts failed because the user didn't > exist. What if the user exists though? Does this illegal chars make > a hole for them to enter through? > > Simon > -- Tom Pawlowski OIT-CSS System Administrator office: Hill 147 email: tompru(a)jla.rutgers.edu phone: (732) 445-2634

2 1

Re: [Dovecot] Spammers attempting SASL Auth
by Robert Schetterer 17 Oct '11

17 Oct '11

Am 17.10.2011 17:51, schrieb Simon Brereton: > On 17 October 2011 11:31, Robert Schetterer <robert(a)schetterer.org> wrote: >> Am 17.10.2011 17:16, schrieb Simon Brereton: >>> Hi >>> >>> This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. >>> >>> Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] >>> Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars >>> Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 >>> Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known >>> >>> >>> Simon >>> >> >> this maybe a brute force attack,or more easy someone missconfigured his >> client , you may use fail2ban etc to block it >> not directly related to dovecot > > 17 queries in 30 seconds is not a misconfigured client :) > > And I'm already using Fail2Ban - but as someone on this list pointed > out recently, that doesn't apply if they try X attempts on the same > connection. Although, I don't think that was case here - maybe I > should update my dovecot jail with that illegal chars line. But, be > that as it may - all these attempts failed because the user didn't > exist. What if the user exists though? Does this illegal chars make > a hole for them to enter through? > > Simon > as i posted you offlist, this is a smtp attack, look at your i.e fail2ban postfix rules, fail2ban dovecot ruel is for banning pop3/imap brute force -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

Re: [Dovecot] Spammers attempting SASL Auth
by Robert Schetterer 17 Oct '11

17 Oct '11

Am 17.10.2011 17:16, schrieb Simon Brereton: > Hi > > This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. > > Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] > Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars > Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 > Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known > > > Simon > this maybe a brute force attack,or more easy someone missconfigured his client , you may use fail2ban etc to block it not directly related to dovecot -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 1

[Dovecot] Spammers attempting SASL Auth
by Simon Brereton 17 Oct '11

17 Oct '11

Hi This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known Simon

1 0

[Dovecot] dovecot-antispam – Debian package
by Philipp Haselwarter 17 Oct '11

17 Oct '11

Dovecot2 has been around for a bit now but Eugene Paskevich's antispam plugin unfortunately still doesn't seem to have a tagged release. Has anyone by any chance rolled a .deb for the plugin that works on current Debian sid? -- Philipp Haselwarter

1 0

[Dovecot] lmtp performance
by Juan Carlos Sanchez 17 Oct '11

17 Oct '11

Hello: In the process of migration from version 1.2 to 2.0 have tried to use lmtp instead of lda as delivery agent. But unfortunately througput we get is poor with lmtp compared to lda. In peak times with lda we are able to deliver over 1800 messages/minute (high I/O but not affecting service) but if we switch to lmtp cannot deliver more than 300 mess/minute (very low I/O). This is enough for normal work but low under heavy load (distribution lists messages sometimes stay queued for 4 hours before deliver). We have arround 50000 boxes and use postfix as MTA How to increase lmtp performance? dovecot config for lda and lmtp: protocol lda { auth_socket_path = /usr/local/var/run/dovecot/auth-master info_log_path = /var/log/mail/dovecot_deliver.log log_path = /var/log/mail/dovecot_deliver.log mail_plugins = quota sieve zlib postmaster_address = postmaster(a)upm.es sendmail_path = /usr/lib/sendmail } protocol lmtp { info_log_path = /var/log/mail/dovecot_deliver.log log_path = /var/log/mail/dovecot_deliver.log mail_plugins = quota sieve zlib postmaster_address = postmaster(a)upm.es sendmail_path = /usr/lib/sendmail } In postfix I have: mailbox_transport = lmtp:unix:private/dovecot-lmtp Thanks in advance. -- ------------------------------------------------------ Juan Carlos Sanchez Hernandez Universidad Politecnica de Madrid ------------------------------------------------------

1 0

[Dovecot] Problems Configuring Pigeonhole/Seve
by Ian Barton 17 Oct '11

17 Oct '11

I am moving my email server from Ubuntu Lucid to Arch. The Arch server is running Dovecot V2.0.15. Email is working fine, but I can't get Pigeonhiole/sieve to work. My dovecot.conf is: protocols = imap sieve ssl = yes ssl_cert = </etc/ssl/certs/mail2.wilkesley.net.crt ssl_key = </etc/ssl/private/mail2.wilkesley.net.key first_valid_uid = 5000 first_valid_gid = 5000 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ namespace { location = maildir:/home/vmail/%d/%n/Maildir type = private prefix = INBOX. inbox = yes hidden = yes } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } protocol lda { postmaster_address = ian(a)wilkesley.net hostname = wilkesley.org sendmail_path = /usr/sbin/sendmail mail_plugins = $mail_plugins sieve } protocol sieve { # Nothing to do here as defaults are OK } plugin { sieve = ~/.dovecot.sieve sieve_global_path = /home/vmail/globalsieverc sieve_dir = ~/ } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } I have created the sieve dir in the virtual users folder. However sieve doesn't appear to be working. I have tried logging in manually to see if sieve is running, but get the following error: ian:~/ $ gnutls-cli --starttls -p 143 mail2.wilkesley.net [8:32:22] Resolving 'mail2.wilkesley.net'... Connecting to '127.0.0.1:143'... - Simple Client Mode: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. STARTTLS STARTTLS BAD Error in IMAP command received by server. According to the Dovecot wiki this should reply with the capabilities of my server, Note the server sends and receives mail OK using starttls. So what am I doing wrong?

2 1

[Dovecot] Question about ionice & dovecot-deliver
by Maria Arrea 16 Oct '11

16 Oct '11

Hello We are running dovecot 2.0.13 with mdbox on RHEL 5.7 x64, ext4 filesystem. Sometimes we have a big load increase because a mailing list server send 16.000 32k messages in less than 3 minutes. We want to "slow down" delivery, we prefer slow delivery instead of logging out webmail users. I have the following line en /etc/postfix/master.cf: flags=DRhu user=userid argv=/usr/libexec/dovecot/deliver -d ${user} And in /etc/postfix/main.cf mailbox_command = /usr/libexec/dovecot/deliver I would like to add ionice to the equation, prefixing /usr/bin/ionice -c2 -n6 before the deliver lines in postfix config. Is there any other way of slowing down delivery speed vs imap access? Regards Maria

3 2

[Dovecot] Issue after upgrading to Ubuntu Server 11.10
by Chris Vanden Berghe 14 Oct '11

14 Oct '11

Hi all, After upgrading to Ubuntu Server 11.10 my mail setup stopped working. The error message I get is: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +r perm: /var/run/dovecot/auth-userdb, euid is not dir owner) Does anybody have an idea how to solve this? Thanks, Chris. --- # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-12-generic x86_64 Ubuntu 11.10 ext3 auth_verbose = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/vmail/%u mail_privileged_group = mail maildir_stat_dirs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { fts = squat fts_squat = partial=4 full=10 } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { address = localhost port = 143 } inet_listener imaps { address = * port = 993 } } ssl_cert = </etc/ssl/private/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/var/vmail/%u driver = static } protocol imap { mail_max_userip_connections = 50 mail_plugins = fts fts_squat } protocol lda { mail_plugins = sieve }

1 1

Re: [Dovecot] Dovecot not processing through Sieve
by Stephan Bosch 13 Oct '11

13 Oct '11

Please reply to the list as well. On 10/13/2011 3:28 PM, Steven Kiehl wrote: > > On Thu, Oct 13, 2011 at 9:21 AM, Stephan Bosch <stephan(a)rename-it.nl > <mailto:stephan@rename-it.nl>> wrote: > > Are you sure you are using the Dovecot LDA (deliver)? Did you > follow these instructions in the wiki? > > http://wiki1.dovecot.org/LDA > http://wiki1.dovecot.org/LDA/Postfix > > From the looks of things, your Postfix currently still does its > own mail delivery instead of using the Dovecot LDA. You should see > entries in your log relating to LDA/deliver and Sieve, especially > since you enabled mail_debug. To test whether Sieve is configured > correctly (and to see what the Dovecot LDA normally logs), you can > also manually execute /usr/lib/dovecot/deliver and feed it a message. > > I am using Dovecot deliver to perform mail delivery. I'm absolutely > certain of this because I get spam scores and it is SpamAssassin that > actually hands the mail over to deliver. Here is my postfix master.cf > <http://master.cf> entry for spamc/deliver: > > dovespam unix n n n - - pipe > flags=DRhu user=dovemail:dovemail argv=/usr/bin/spamc -f -e > /usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -f ${sender} -d > ${user}@${nexthop} -n -m ${extension} Ok, then what do your logs say about delivery? Even when things are filed in INBOX, the logs should show that deliver and sieve are being executed and putting the mail there. http://wiki1.dovecot.org/Logging Regards, Stephan

2 1

[Dovecot] Sieve and UserDB/SQL support
by ben＠benweblife.fr 13 Oct '11

13 Oct '11

Hi, I would like to know if plugins of sieve support UserDB/SQL backend. For example, for the vacation plugin, is it possible to retrieve a field like "sieve_vacation_days", "sieve_vacation_reason", and so on.. on user_query? Or, there is a plan for implement this? Thanks ------ dovecot version: 2.0.13

2 1

[Dovecot] Dovecot not processing through Sieve
by Steven Kiehl 13 Oct '11

13 Oct '11

Hello everyone, I'm fairly new to Dovecot, but I've gotten the majority of things working except for Sieve. I'm running Dovecot 1.2.9 coupled with Postfix and SpamAssassin all with a virtual domains setup. I am receiving mail and it is being processed by all the plugins that operate through Postfix. The quota configured in Dovecot appears to be working because my mail client shows the configured quota. But the Sieve rules are not processing. I created a rule as follows to filter spam: require ["fileinto"]; # rule:[global-spam] if anyof (header :contains "Subject" "[SPAM]", header :contains "X-Spam-Flag" "YES") { fileinto "Junk"; } If I mail myself a message with [SPAM] in the title, it goes into my inbox regardless. I've run 'sieve-test' with the same email and it says it will file it into Junk. The Junk folder exists. I even tried adding :create and the "mailbox" plugin, but that didn't do anything either. Here is the relevant majority of my dovecot configuration: 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 login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:/home/dovecot/mail/domains/%d/%n/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): 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 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: *mail_plugins: quota sieve* quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r auth default: mechanisms: cram-md5 plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: dovemail group: dovemail socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix plugin: convert_mail: maildir:/home/dovecot/mail/domains/%d/%u/Maildir * sieve: /etc/dovecot/sieve/domains/%d/%n.sieve* * sieve_global_dir: /etc/dovecot/sieve/global/* quota: maildir:User quota_rule: INBOX:storage=500M quota_rule2: INBOX.Trash:storage=100M The sieve plugin exists in /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so, so I would assume I'd have to use *mail_plugin: sieve* as my configuration setting. Like I said, I am receiving emails to my domains without any problem, but sieve rules are not being processed. I can see the rules set up by using the Roundcube plugin, and I can create and edit rules through Roundcube, but nothing different happens when I send myself an email. It all just delivers to the inbox. Thanks for your help, Steve K.

2 1

[Dovecot] Auth Worker failures
by Simon Brereton 12 Oct '11

12 Oct '11

Hi I have a script that checks the logs each day and mails me invalid user attempts and authentication failures for the previous day. (I use fail2ban to ban multiple attempts in a short space of time). For some reason, this appears every day: Oct 11 06:25:12 mail dovecot: auth-worker(default): sql(simon(a)mydomain.net,127.0.0.1): Password mismatch Oct 11 06:25:19 mail dovecot: auth-worker(default): sql(simon(a)mydomain.net,127.0.0.1): Password mismatch Oct 11 06:25:31 mail dovecot: auth-worker(default): sql(simon(a)mydomain.net,127.0.0.1): Password mismatch Oct 11 06:25:48 mail dovecot: auth-worker(default): sql(simon(a)mydomain.net,127.0.0.1): Password mismatch Oct 11 06:26:10 mail dovecot: imap-login: Aborted login (auth failed, 4 attempts): user=<simon(a)mydomain.net>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Of all the accounts on the box, it's only mine that throws this up. Since its LIP is localhost, it could really only be for webmail - but I don't always leave the webmail open, so I'm curious to know how this gets there and what it is. Any suggestions? I find it difficult to believe I have an IMAP process in a script somewhere (especially with my user account - the postmaster account, I could believe, but not with my personal one).. The log time is UTC, so watching the process list at 2.24 is less than appealing! Simon

1 0

[Dovecot] dovecot2 auth-worker socket perms ignoring assigned ownership settings in conf.d/10-master.conf?
by mephistopheles＠operamail.com 12 Oct '11

12 Oct '11

I have Dovecot2 auth setup to run as user = doveauth group = dovecot configured in, vi conf.d/10-master.conf ... service auth { unix_listener /var/spool/postfix/private/auth { user = postfix group = postfix mode = 0660 } user = doveauth group = dovecot } service auth-worker { user = doveauth group = dovecot } ... When I start Dovecot, ls -al /var/run/dovecot/auth-* /bin/ls: No match. service dovecot-custom start Starting Dovecot ... done Dovect's auth-process sockets are created with different ownership than what I specified, ls -al /var/run/dovecot/auth-* srw------- 1 root root 0 Oct 11 19:30 /var/run/dovecot/auth-client srw------- 1 dovecot root 0 Oct 11 19:30 /var/run/dovecot/auth-login srw------- 1 root root 0 Oct 11 19:30 /var/run/dovecot/auth-master srw------- 1 root root 0 Oct 11 19:30 /var/run/dovecot/auth-userdb srw------- 1 dovecot root 0 Oct 11 19:30 /var/run/dovecot/auth-worker Which causes problems when I test AUTH, telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. a login "xxx(a)domain.loc" "testpass" a NO [UNAVAILABLE] Temporary authentication failure. * OK Waiting for authentication process to respond.. In logs, ==> /var/log/dovecot/dovecot-debug.log <== Oct 11 19:32:11 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/modules/auth Oct 11 19:32:11 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libauthdb_ldap.so Oct 11 19:32:11 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_mysql.so Oct 11 19:32:11 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_pgsql.so Oct 11 19:32:11 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_sqlite.so Oct 11 19:32:11 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libmech_gssapi.so Oct 11 19:32:11 auth: Debug: auth client connected (pid=2397) Oct 11 19:32:17 auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1lport=143 rport=47016 resp=<hidden> ==> /var/log/dovecot/dovecot.log <== Oct 11 19:32:17 auth: Fatal: net_connect_unix(auth-worker) in directory /var/run/dovecot failed: Permission denied (euid=1101(doveauth) egid=305(dovecot) missing +r perm: /var/run/dovecot/auth-worker, dir owned by 305:305 mode=0755) What needs to change to get those sockets created with correct/assigned ownership & perms?

2 5

[Dovecot] To query two SQL tables for user verification over LMTP, should I use (a) two separate lookups? or (b) just one lookup with a boolean query?
by jake0534＠airpost.net 12 Oct '11

12 Oct '11

Hey all I've been running a Dovecot 1X server for awhile. Most of the config was pretty simple using flat files. I'm switching to Dovecot 2X now, and want to switch to using SQL for lookups so I can share info with the Postfix front end. For starters I setup two SIMPLE SQL tables -- a 'users' table and a 'aliases' table, where each user can have many aliases. I want to have Postfix check Dovecot's SASL/LMTP passdb to see if a <user>@<domain> exists. If yes, deliver through LMTP. If NO, reject it. Here are the table definitions so far, CREATE TABLE user ( userid TINYINT, user VARCHAR(64), domain VARCHAR(128), password VARCHAR(64), PRIMARY KEY (userid), UNIQUE (user,domain) ); CREATE TABLE alias ( aliasid TINYINT, alias VARCHAR(64), user VARCHAR(64), domain VARCHAR(128), PRIMARY KEY (aliasid), UNIQUE (domain,user,alias), CONSTRAINT fk_alias1 FOREIGN KEY (user) REFERENCES user (user) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT fk_alias2 FOREIGN KEY (domain) REFERENCES user (domain) ON DELETE NO ACTION ON UPDATE NO ACTION ); With flat file and just one table, 'users', I get how to setup LMTP. I can get Postfix delivering/rejecting over LMTP depending on if the user exists in the Dovecot passdb or not. I don't get how to do the SQL query in Dovecot if I have the TWO tables. An inbound <user>@<domain> needs to be auth'd as valid if it exists in EITHER 'user' OR 'alias' table. Do I need to use a single lookup for passdb with some sort of "IF EXISTS IN TABLE 'user' OR TABLE 'alias'" query? Or do I need to have TWO lookups, the main one for 'user' and a fallback one for 'alias' (like talked about here http://wiki2.dovecot.org/Authentication/MultipleDatabases)? Cheers! Jake

2 5

[Dovecot] using ecc-certificates (ellyptic curve) will not establish connection
by Fresel Michal - hi competence e.U. 11 Oct '11

11 Oct '11

hi I want to use ECC(ellyptic curve cryptography) for SSL-connections but somehow dovecot doesn't like my ECC-certificates :( I tried to test using following scenario: machine: debian 6 (x64) dovecot 2.0.15-0~auto+21 ((f6a2c0e8bc03) from http://xi.rename-it.nl/debian openssl 1.0.0e-2 from testing (as the default 0.9.8o-4squeeze3 needs also the parameter -cipher ECCdraft for testing) creating keys+cert for ecc (i.e. curves prime192v1, secp521r1) # openssl ecparam -name prime192v1 -genkey -out prime192v1.key # openssl req -new -key prime192v1.key -out prime192v1.csr # openssl req -x509 -in prime192v1.csr -key prime192v1.key -out prime192v1.crt testing these in 2 windows # openssl s_server -cert prime192v1.crt -key prime192v1.key -www # openssl s_client note: when using the default openssl version 0.9.8o-4squeeze3 you need to append -cipher ECCdraft output (cut) ... New, TLSv1/SSLv3, Cipher is ECDHE-ECDSA-AES256-SHA Server public key is 192 bit Secure Renegotiation IS supported Compression: zlib compression Expansion: zlib compression SSL-Session: Protocol : SSLv3 Cipher : ECDHE-ECDSA-AES256-SHA Session-ID: xxxxx Session-ID-ctx: Master-Key: xxxxx Key-Arg : None PSK identity: None PSK identity hint: None Compression: 1 (zlib compression) Start Time: xxxxx Timeout : 7200 (sec) Verify return code: 18 (self signed certificate) looks promising - also for the secp521r1 curve but when changing dovecot.conf to use these keys and certificates it won't use them and return errors # openssl s_client -port 993 CONNECTED(00000003) 140543456835240:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:1195:SSL alert number 40 140543456835240:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:591: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 0 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE SSL-Session: Protocol : SSLv3 Cipher : 0000 Session-ID: Session-ID-ctx: Master-Key: Key-Arg : None PSK identity: None PSK identity hint: None Start Time: xxxxx Timeout : 7200 (sec) Verify return code: 0 (ok) --- and the log gives (using verbose_ssl = yes in dovecot.conf) ==> /var/log/mail.log <== dovecot: imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [127.0.0.1] ==> /var/log/mail.info <== dovecot: imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [127.0.0.1] ==> /var/log/mail.warn <== dovecot: imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [127.0.0.1] ==> /var/log/mail.log <== dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [127.0.0.1] ==> /var/log/mail.info <== dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [127.0.0.1] ==> /var/log/mail.warn <== dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [127.0.0.1] ==> /var/log/mail.log <== dovecot: imap-login: Warning: SSL alert: where=0x4008, ret=552: fatal handshake failure [127.0.0.1] ==> /var/log/mail.info <== dovecot: imap-login: Warning: SSL alert: where=0x4008, ret=552: fatal handshake failure [127.0.0.1] ==> /var/log/mail.warn <== dovecot: imap-login: Warning: SSL alert: where=0x4008, ret=552: fatal handshake failure [127.0.0.1] ==> /var/log/mail.log <== dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client hello C [127.0.0.1] ==> /var/log/mail.info <== dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client hello C [127.0.0.1] ==> /var/log/mail.warn <== dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client hello C [127.0.0.1] ==> /var/log/mail.log <== dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client hello C [127.0.0.1] dovecot: imap-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher ==> /var/log/mail.info <== dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client hello C [127.0.0.1] dovecot: imap-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher ==> /var/log/mail.warn <== dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client hello C [127.0.0.1] from doveconf -a: ssl = required ssl_ca = ssl_cert = </etc/ssl/certs/prime192v1.crt ssl_cert_username_field = commonName ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_key = </etc/ssl/certs/prime192v1.key ssl_key_password = ssl_parameters_regenerate = 168 ssl_verify_client_cert = no Has anybody already tested this and made it working? Or do i have just to recompile everything to make it work? Greetings Mike

1 1

[Dovecot] inbox issue
by Eric Broch 10 Oct '11

10 Oct '11

I have dovecot 2.0.11 installed on a CentOS 5.7 email server. Two of the server email clients, one using Outlook and the other Thunderbird, have had all the contents of their inbox disappear only to reappear at a later time. One client's inbox email reappeared upon receiving a test email (to check if it would show up in the inbox) from another user. Has anyone heard of such a thing? Here's a dump of my dovecot configuration. # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.19.1.el5 i686 CentOS release 5.7 (Final) auth_anonymous_username = anonymous auth_cache_negative_ttl = 1 hours auth_cache_size = 32 M auth_cache_ttl = 1 hours auth_debug = no auth_debug_passwords = no auth_default_realm = auth_failure_delay = 2 secs auth_first_valid_uid = 500 auth_gssapi_hostname = auth_krb5_keytab = auth_last_valid_uid = 0 auth_master_user_separator = auth_mechanisms = plain login digest-md5 cram-md5 auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu auth_username_translation = auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth auth_worker_max_count = 30 base_dir = /var/run/dovecot config_cache_size = 1 M debug_log_path = default_client_limit = 1000 default_idle_kill = 60 default_internal_user = dovecot default_login_user = dovenull default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%m: %$ dict_db_config = director_doveadm_port = 0 director_mail_servers = director_servers = director_user_expire = 15 mins disable_plaintext_auth = no dotlock_use_excl = yes doveadm_socket_path = doveadm-server doveadm_worker_count = 0 first_valid_gid = 1 first_valid_uid = 89 hostname = imap_capability = imap_client_workarounds = imap_id_log = imap_id_send = imap_idle_notify_interval = 2 mins imap_logout_format = bytes=%i/%o imap_max_line_length = 64 k import_environment = TZ info_log_path = last_valid_gid = 0 last_valid_uid = 0 lda_mailbox_autocreate = no lda_mailbox_autosubscribe = no lda_original_recipient_header = libexec_dir = /usr/libexec/dovecot listen = *, :: lmtp_proxy = no lmtp_save_to_detail_mailbox = no lock_method = fcntl log_path = /var/log/dovecot.log log_timestamp = "%b %d %H:%M:%S " login_access_sockets = login_greeting = Dovecot toaster ready. login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c login_trusted_networks = mail_access_groups = mail_attachment_dir = mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k mail_cache_fields = flags mail_cache_min_mail_count = 0 mail_chroot = mail_debug = no mail_fsync = optimized mail_full_filesystem_access = no mail_gid = mail_home = mail_location = mail_log_prefix = "%s(%u): " mail_max_keyword_length = 50 mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = imap.envelope mail_nfs_index = no mail_nfs_storage = no mail_plugin_dir = /usr/lib/dovecot mail_plugins = mail_privileged_group = mail_save_crlf = no mail_temp_dir = /tmp mail_uid = mailbox_idle_check_interval = 30 secs mailbox_list_index_disable = no maildir_copy_with_hardlinks = yes maildir_stat_dirs = no maildir_very_dirty_syncs = no master_user_separator = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_min_index_size = 0 mbox_read_locks = fcntl mbox_very_dirty_syncs = no mbox_write_locks = dotlock fcntl mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 2 M mmap_disable = no namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = . subscriptions = yes type = private } namespace { hidden = no inbox = no list = yes location = maildir:/home/vpopmail/domains/acemt.com/shared/projects prefix = projects. separator = . subscriptions = yes type = public } passdb { args = cache_key=%u webmail=127.0.0.1 deny = no driver = vpopmail master = no pass = no } plugin/quota = maildir pop3_client_workarounds = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_format = %08Xu%08Xv postmaster_address = protocols = imap quota_full_tempfail = no recipient_delimiter = + rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s sendmail_path = /usr/sbin/sendmail service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 4096 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0600 user = } unix_listener login/login { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } unix_listener login/dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 ssl = no } inet_listener imaps { address = port = 993 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 64 M } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 0 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 0 } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 ssl = no } inet_listener pop3s { address = port = 995 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 64 M } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } shutdown_clients = yes ssl = yes ssl_ca = ssl_cert = </var/qmail/control/servercert.pem ssl_cert_username_field = commonName ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_key = </var/qmail/control/servercert.pem ssl_key_password = ssl_parameters_file = ssl-parameters.dat ssl_parameters_regenerate = 168 ssl_verify_client_cert = no submission_host = syslog_facility = mail userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q driver = vpopmail } valid_chroot_dirs = verbose_auth = no verbose_proctitle = no verbose_ssl = no version_ignore = no protocol imap { imap_client_workarounds = delay-newmail }

3 2

Re: [Dovecot] Filesystem quotas
by Joseph Tam 10 Oct '11

10 Oct '11

Timo Sirainen writes in response to Steve Fatula's query: > With imap_quota plugin it allows IMAP client to see how much quota is > used/left. You could also enable quota warnings. And configure the > quota exceeded error message. It could also prevent the catch-22 situation I wrote about earlier whereby a filesystem out-of-space condition will result in a user not being able get themselves out of that situation, since a mailbox operation (like a delete and expunge) will not be able to create a lockfile. Having quotas handled by the IMAP/LDA will allow extra room to handle this impasse. Disabling dotlock or using dotlock_try locking method are some other workarounds. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Timeout leak in get quota
by Danilo 10 Oct '11

10 Oct '11

Hello! I wrote perl script for read current quota usage, it works but when I run the program I receive a warning in Dovecot log: 2011-09-29 14:45:30 doveadm(guest(a)testmail.com): Warning: Timeout leak: 0x7f14800ad970 This is the script: =============================== #!/usr/bin/perl use strict; use Socket; use IO::Handle; socket(TSOCK, PF_UNIX, SOCK_STREAM,0); connect(TSOCK, sockaddr_un("/var/run/dovecot/doveadm-server")) or print("ERROR!"); print "VERSION\tdoveadm-server\t1\t0\n"; print "\tguest\(a)testmail.com\tquota get\n"; print "=" x 20 . "\n"; if (defined(my $messg = <TSOCK>)) { print $messg; print TSOCK "VERSION\tdoveadm-server\t1\t0\n"; TSOCK->flush; print TSOCK "\tguest\(a)testmail.com\tquota get\n"; TSOCK->flush; $messg = <TSOCK>; print $messg; $messg = <TSOCK>; print $messg; close TSOCK; } ============================= I hope someone could help me to fix the warning. Thanks in advance, Dany

3 3

Re: [Dovecot] Group ACL
by Daniel L. Miller 10 Oct '11

10 Oct '11

On 10/7/2011 11:08 PM, Daniel L. Miller wrote: > On 10/6/2011 8:38 AM, Daniel L. Miller wrote: >> Using Dovecot 2.0, LDAP userdb & passdb, with prefetch: >> >> [..] >> >> I have added permissions for "$allshared" to a mailbox's Inbox. It >> does not appear in the shared folders list. Other mailboxes, with >> explicit permission for a given username, work fine. What am I doing >> wrong? >> > Am I, as usual, doing something wrong? > Is there anything else I should supply to help diagnose the issue? -- Daniel

1 0

[Dovecot] Filesystem quotas
by Steve Fatula 10 Oct '11

10 Oct '11

I am wondering if I really need to use dovecot quota functions or not. Assume for the moment, that, each system user has a quota defined using Linux quotas, and that the Maildir is within their quota limited directory. So, any mail (or files created by the user etc) that would exceed the quota obviously can't be created. In such an environment, is there any advantage to implementing the same quota already defined in the filesystem via dovecot? Or, can I just make things simpler and ignore dovecot quotas? Assuming I keep the index and control files out of the quota limited directories. I presume if exceeding filesystem quota, the mail will not be delivered of course. If using lmtp, I presume it stays in the queue to retry later for some period of time. Steve

4 4

Re: [Dovecot] Group ACL
by Daniel L. Miller 08 Oct '11

08 Oct '11

On 10/6/2011 8:38 AM, Daniel L. Miller wrote: > Using Dovecot 2.0, LDAP userdb & passdb, with prefetch: > > [..] > > I have added permissions for "$allshared" to a mailbox's Inbox. It > does not appear in the shared folders list. Other mailboxes, with > explicit permission for a given username, work fine. What am I doing > wrong? > Am I, as usual, doing something wrong? -- Daniel

1 0

[Dovecot] lazy expunge namespaces
by Micah Anderson 07 Oct '11

07 Oct '11

I turned on lazy_expunge and configured a namespace following the wiki[0] instructions for mdbox configuration: namespace { inbox = yes location = prefix = separator = . } namespace { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } namespace { location = mdbox:~/mdbox:MAILBOXDIR=expunged prefix = EXPUNGED. separator = . } This created an EXPUNGED mailbox in my client (thunderbird), which was greyed out. When I deleted things, they got put in the EXPUNGED mailbox, as expected, but I could not access them to try and "restore" them. The server would say that the mailbox did not exist. micah 0. http://wiki2.dovecot.org/Plugins/Lazyexpunge --

1 0

[Dovecot] doveadm mailbox subscribe wildcard
by Micah Anderson 07 Oct '11

07 Oct '11

Hi, I noticed that wildcards work like the following, as described in the man page: # doveadm mailbox list -s -u bob dovecot* dovecot dovecot/pigeonhole dovecot/pigeonhole/2.0 however, wildcard subscriptions don't work: # doveadm mailbox subscribe -u bob dovecot* # doveadm mailbox list -s -u bob dovecot* dovecot dovecot* dovecot/pigeonhole dovecot/pigeonhole/2.0 It seems I subscribed the non-existant mailbox called 'dovecot*' -- is there a better way to handle this? thanks! micah --

3 3

[Dovecot] Using dsync to synchronize pop3 mailbox <-> pop3 mailbox
by Tristan Goguen 07 Oct '11

07 Oct '11

Hi All, We're trying to get dsync to synchronize pop3 mailboxes on multiple servers. Is this possible? Any hints are appreciated. Thanks, Tristan Tristan Goguen CEO, ILAP® T: 416-250-5600 ext. 205 F: 416-250-6755 tgoguen(a)ilap.com www.ilap.com

1 0

[Dovecot] I'm the ONLY user that can get mail
by Ed Hochman 06 Oct '11

06 Oct '11

Hi, I'm stumped. I can access the postfix server to read my mail. BUT I'm the only user that can. Everyone else get rejected. Here's the syslog entry for another user: ...dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<jmarino>, method=PLAIN, rip=192.168.0.51, lip=192.168.0.189 And here's an entry for me: ...dovecot: pop3-login: Login: user=<ed>, method=PLAIN, rip=192.168.0.51, lip=192.168.0.189 So ONLY I am able to get my mail. And this is consistent. The other users and passwords are valid. I've re-set them just to be sure. I suspect it's a rights issue but I've checked the rights for all /var/mail files and they're all the same except the owner of the file is the actual owner. I also checked all the rights for the files in /etc/dovecot. They all look OK and they all have root/root for the owner and user. Since I installed the system and did all the editing of the configuration files it's possible, but unlikely, that I'm the owner or group of some key file. I've looked for that but found nothing suspicious. Is it possible I may have given myself root access? I don't see how. My UID is 1000. Does the fact I'm the first user (per my UID) make a difference? I would think not. So I'm stumped. I don't have a clue as to where to look or what to do next. Any thoughts will be greatly appreciated. This is Dovecot 1.2.15 on Ubuntu 11.04. A new/clean install. Plaintext passwords are allowed. Here's dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.38-11-generic i686 Ubuntu 11.04 protocols: pop3 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: passwd passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd Thanks

2 1

[Dovecot] Only using LMTP-delivery, where should domain & user aliases be configured, Dovecot or MTA conf?
by mephistopheles＠operamail.com 06 Oct '11

06 Oct '11

I have my MTA (Postfix) check Dovecot2 LMTP for existing users. No other delivery is done; this is a virtual/LMTP-only setup. I define known users in a Dovecot passwd-file, specified in conf.d/10-auth.conf passdb { args = ... username_format=%n /stor01/vmail/auth.d/%d/passwd e.g., vi /stor01/vmail/auth.d/mx1.domain1.com/passwd myuser:{scheme}####:... mail to: myuser(a)mx1.domain1.com is correctly auth'd and stored. I want two things to happen: (1) all mail to existing-users "@domain1.com" gets re-routed to "@mx1.domain1.com", i.e., map: myuser(a)domain1.com -> myuser(a)mx1.domain1.com and is accepted/not-rejected ONLY if 'myuser' is defined as a user in mx1.domain1.com/passwd and, (2) specific 'user' aliasing/remapping within a given domain, i.e. map: whatever(a)mx1.domain1.com -> myuser(a)mx1.domain1.com as long as 'myuser' is a defined user in mx1.domain1.com In these cases, where should I assign domain & mail aliases, Dovecot or the MTA's conf ?

1 0

[Dovecot] trouble setting up director, "invalid argument" for connect() call
by Jim Lawson 05 Oct '11

05 Oct '11

Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The director on each node is listening on port 9090 just fine: > [root@imapdir1 ~]# nc imapdir2 9090 > VERSION director 1 0 > ME 127.0.0.1 9090 > [root@imapdir2 ~]# nc imapdir1 9090 > VERSION director 1 0 > ME 127.0.0.1 9090 "doveadm director ring status" always reports failure of the peer: > [root@imapdir1 ~]# doveadm director ring status > director ip port type last > failed > 127.0.0.1 9090 self > never > 132.198.100.150 9090 2011-10-04 > 13:28:55 > [root@imapdir2 ~]# doveadm director ring status > director ip port type last > failed > 127.0.0.1 9090 self > never > 132.198.100.149 9090 2011-10-04 > 13:24:08 Has anyone else seen this? FWIW, a single-node director works fine, proxying IMAP, LMTP and POP. I'm guessing I have a broken config, but if I do I can't figure it out. Hope I'm not missing something *too* obvious... Here's doveconf -n from imapdir1: # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.3.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.7 (Tikanga) base_dir = /var/run/dovecot/ director_mail_servers = penguina.uvm.edu penguinb.uvm.edu penguinc.uvm.edu director_servers = imapdir1.uvm.edu imapdir2.uvm.edu lmtp_proxy = yes login_trusted_networks = 132.198.101.211,132.198.101.212,132.198.101.213,132.198.101.214,132.198.101.215,132.198.101.216,132.198.100.45,132.198.100.46,132.198.100.47 passdb { args = proxy=y nopassword=y protocol=smtp driver = static } service auth { unix_listener auth-userdb { group = mail mode = 0660 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { client_limit = 1 inet_listener lmtp { port = 24 } unix_listener /var/lib/dovecot/lmtp-socket { group = root mode = 0600 user = root } } Best, Jim

1 1

[Dovecot] Dovecot + managesieve + ldap not working
by Philip Brechler 05 Oct '11

05 Oct '11

Hi, I want to use managesieve in my dovecot server which uses virtual users and a ldap for the users. This is in my dovecot.conf: # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-x86_64-jb1 x86_64 Debian 6.0.1 ext3 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): *:2000 disable_plaintext_auth: no login_dir: /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 mail_privileged_group: mail mail_uid: 5000 mail_gid: 5000 mail_location: maildir:/var/mail/%u/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve lda: postmaster_address: pbrechler(a)piratenfraktion-berlin.de mail_plugins: sieve mail_plugin_dir: /usr/lib/dovecot/modules/lda auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.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: 384 user: vmail group: vmail plugin: sieve_dir: /var/mail/sievescript/%u_scripts/ sieve_extensions: +imapflags And my ldap conf: hosts = ldap.piratenfraktion-berlin.de auth_bind = yes auth_bind_userdn = uid=%u,ou=people,dc=domain,dc=de ldap_version = 3 base = dc=domaindc=de deref = never scope = subtree user_attrs = uid=mail=maildir:/var/mail/%$/Maildir/ user_filter = (|(&(objectClass=organizationalPerson)(uid=%Ln))(&(objectClass=organizationalPerson)(mail=%Lu))) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=organizationalPerson)(uid=%u)) If I try to talk to managesieve with telnet this happens: Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "dovecot" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator- i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date imapflags" "SASL" "PLAIN LOGIN" "STARTTLS" "NOTIFY" "mailto" "VERSION" "1.0" OK "Dovecot ready." # ca. 2 Seconds pause AUTHENTICATE "PLAIN" "xxxxxxxxxxxxx" BYE "Internal error occured. Refer to server log for more information. [2011-10-02 00:48:09]" Connection closed by foreign host. Dies is a log reading 2011-10-02 00:48:09 MANAGESIEVE(user): Fatal: Failed to create sieve storage with data: /var/mail/sievescript/user_scripts But the permissions are 775 dovecot:dovecot and the system tells me that dovecot was the last user who had access to the directory. Can someone help me? Thanks! kind regards Philip Brechler

2 3

[Dovecot] doveadm(user001): Fatal: passdb lookup failed
by mailing lists 05 Oct '11

05 Oct '11

Hello all, why I can run whis command: imap1:~ # doveadm user user001 userdb: user001 mail : maildir:/var/maildir/vol04/4/46/user001 home : /var/mailfilter/vol04/4/46/user001 quota_rule: *:bytes=100000000 but not this one: imap1:~ # doveadm quota get -u user001 doveadm(user001): Error: user user001: Auth PASS lookup failed doveadm(user001): Fatal: passdb lookup failed what I'm missing ? /-------------------/ imap1:/etc/dovecot # grep ^[^#] dovecot-ldap.conf.ext uris = ldap://ldap.example.com dn = cn=admin,dc=example,dc=com dnpass = secret sasl_bind = no tls = no auth_bind = yes ldap_version = 3 base = dc=example,dc=com deref = never scope = subtree user_attrs = mailbox=mail=maildir:/var/maildir/%$,homeFilter=home,mailQuota=quota_rule=*:bytes=%$ user_filter = (&(objectClass=CourierMailAccount)(uid=%n)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=CourierMailAccount)(uid=%n)) iterate_filter = (objectClass=CourierMailAccount) imap1:/etc/dovecot # dovecot -n # 2.0.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no doveadm_proxy_port = 24244 doveadm_socket_path = localhost:24244 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_fsync = always mail_gid = 5000 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl quota notify quota = maildir:User Quota quota_exceeded_message = Quota exceded quota_rule2 = Trash:storage=+50M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { inbox = yes list = yes location = prefix = separator = . subscriptions = yes } namespace { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . subscriptions = no } namespace { list = children location = maildir:/var/virtual-maildir/%%n:INDEX=~/shared.%%n prefix = shared.%%n. separator = . subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/maildir/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid from subject size vsize flags mail_plugins = " mail_log notify" sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = nonresponse(a)example.com service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service doveadm { inet_listener { port = 24244 } } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { port = 24 } unix_listener lmtp { group = vmail mode = 0666 user = vmail } } service pop3-login { inet_listener pop3 { port = 110 } } service pop3 { process_limit = 1024 } service quota-warning { executable = script /etc/dovecot/quota-warning.sh user = vmail } ssl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = acl quota notify sieve } protocol lda { mail_plugins = acl quota notify sieve } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl quota notify imap_acl autocreate imap_quota } protocol pop3 { pop3_uidl_format = %v-%u } local 100.1.245.101/28/28 { doveadm_password = secret }

1 0

[Dovecot] sieve vacation reply
by Wojciech Giel 04 Oct '11

04 Oct '11

Hi, I'm configuring postfix with dovecot and roundcube. I'm using flat files as passwdb userdb. Everything works fine except sieve vacation reply. when i send mail from ex. user dennis to tytus I get "discarding vacation response for message implicitly delivered to". What Am i doing wrong? thanks sieve: using sieve path for user's script: /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: opening script /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: executing compiled script /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: msgid=<20110517155641.GA3452(a)badger.example.com>: discarding vacation response for message implicitly delivered to <tytus@badger> /etc/postfix/main.cf ... mailbox_command = /usr/lib/dovecot/deliver -n -m "${EXTENSION}" ... # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): 127.0.0.1:2000 ssl_ca_file: /etc/postfix/ssl/cacert.pem ssl_cert_file: /etc/postfix/ssl/servercrt.pem ssl_key_file: /etc/postfix/ssl/serverkey.pem ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /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 mail_location: maildir:~/Maildir:INDEX=~/Maildir/indexes mail_debug: yes mbox_write_locks: fcntl dotlock 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 autocreate mail_plugins(imap): quota imap_quota autocreate mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): tb-extra-mailbox-sep netscape-eoh delay-newmail outlook-idle imap_client_workarounds(imap): tb-extra-mailbox-sep netscape-eoh delay-newmail outlook-idle imap_client_workarounds(managesieve): lda: postmaster_address: postmaster mail_plugins: sieve quota autocreate quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r log_path: /var/log/sieve.log auth default: mechanisms: plain login cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd-file args: scheme=cram-md5 /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve autocreate: INBOX autocreate2: Sent autocreate3: Trash autocreate4: Drafts autocreate5: Junk autosubscribe: INBOX autosubscribe2: Sent autosubscribe3: Trash autosubscribe4: Drafts autosubscribe5: Junk quota: maildir:User quota quota_rule: Trash:storage=10M quota_warning: storage=85%% /usr/bin/dovecot-quota-warning.sh 85 quota_warning2: storage=90%% /usr/bin/dovecot-quota-warning.sh 90 quota_warning3: storage=95%% /usr/bin/dovecot-quota-warning.sh 95

5 7

[Dovecot] Missing man page for doveadm move
by Jeetu 04 Oct '11

04 Oct '11

Hi, i cant see man pages for doveadm-move, though the command "doveadm move ..." works on new version of dovecot. http://hg.dovecot.org/dovecot-2.0/rev/d7a02077d91f -- -Jeetu

2 2

[Dovecot] What best decision to make for flatfiles or SQL when I use Dovecot2 + Postfix together?
by terryjames9461＠mm.st 04 Oct '11

04 Oct '11

Hello, I'm moving my mail server from Exchange to an opensource one. After a bunch of reading, I decided on building a Dovecot2 + Postfix server in a VirtualUsers-only + Multiple-domains configuration. Since my messages will be stored by Dovecot, and the documentation is really good, I figured that it's smartest to configure Dovecot, then make Postfix 'fit' to it, sharing the data files that way. I read through lots of the Dovecot wiki for v2. There are many ways for storing the database data. My goal is to only have data in one instances, used by both Postfix & Dovecot. I'm a little confused about: to do that sharing-in-one-place, do I have to use SQL or can I use the flatfiles like passwd-db? I think for sure someone already decided the best approach for this, and maybe I'm not understanding the logic to it. The data I think I need to share are: users (user(a)domain.com) passwords user aliases (mapping user2(a)domain.com -> user1(a)domain.com) domains domain aliases (domain.com also receives email for domain2.com) And I think all of this can be in passwd-db in Dovecot. But I also want to make sure that Postfix ONLY accepts email for users/domains that exist, so it has to read that data too. Can I do this that way with the flatfiles? Or do I have to use the SQL approach? TJ

12 20

Re: [Dovecot] SSL only for external connections
by Joseph Tam 04 Oct '11

04 Oct '11

On Sun, 2 Oct 2011, Simon Brereton writes: > I don't have that file. Part of the problem is that I'm confused > between protocols and wrappers and interfaces :) Dick and Michael have > persuaded me that it's just easier to for Horde not to ask for TLS on > port 143 - because that's in fact what I was doing - and it's > pointless. > > Nonetheless, I think it would be nice to tell Dovecot listen on the > local interface for IMAP. Listen on the external interface for IMAP, > IMAPS, POP and POP3S. But if there's not simple way to do that I don't > have a valid use-case for doing it right now. I got into this thread rather late so maybe I missed something here. If you have different policies for your interface, you can run two different instances of dovecot (with 2 different base directories and sets of configuration files). I haven't tried it, but maybe it's also possible have interface specific CAPA strings and remove STARTTLS. Dovecot will support unencrypted sessions over the localhost interface, but your webmail seems to opportunistcally use it when offered, so don't offer it. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Intermittent authentication failures
by Eric Shubert 03 Oct '11

03 Oct '11

I'm running dovecot with vpopmail. Here's the configuration: [root@wong log]# dovecot -n # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.9.1.el5 i686 CentOS release 5.6 (Final) auth_cache_size = 32 M auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Lu first_valid_uid = 89 log_path = /var/log/dovecot.log login_greeting = Dovecot toaster ready. mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes mmap_disable = yes namespace { inbox = yes location = prefix = separator = . type = private } passdb { args = cache_key=%u webmail=127.0.0.1 driver = vpopmail } plugin/quota = maildir protocols = imap ssl_cert = </var/qmail/control/servercert.pem ssl_key = </var/qmail/control/servercert.pem userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q driver = vpopmail } protocol imap { imap_client_workarounds = delay-newmail } Most clients use TLS and PLAIN login for verification, which works flawlessly. I also run SquirrelMail that is slightly dated and has no TLS capability, so it is using CRAM-MD5. CRAM-MD5 works sometimes: Sep 30 08:15:43 imap-login: Info: Login: user=<userA(a)domain.com>, method=CRAM-MD5, rip=192.168.252.8, lip=192.168.252.14, mpid=20301 but (seemingly more frequently) the authentication fails: Sep 30 08:16:41 imap-login: Info: Aborted login (auth failed, 1 attempts): user=<userA(a)domain.com>, method=CRAM-MD5, rip=192.168.252.8, lip=192.168.252.14 I restarted dovecot, and that apparently cleared the problem for one user, but not others. Is this perhaps a bug in dovecot, or would the problem lie with vpopmail? TIA for any pointers. -- -Eric 'shubes'

2 6

[Dovecot] Multiple LDAP authentication servers
by Romer Ventura 03 Oct '11

03 Oct '11

Hello, We are performing a Domain migration and I was wondering if there was any way to get Dovecot to authenticate to more than 1 LDAP server? Currently dovecot is configure to query the "mail" attribute from Active Directory and when found it binds with the credentials the user provided. This works fine, but when migrating user accounts, they get disabled in the source domain so that the user can no longer log on to it. But disabling the account in the source domain, causes the user to be unable to use his email account. Is there any way to get dovecot to try a second LDAP server if the first one fails to authenticate..? ~# dovecot -n # 1.2.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-xs5.5.0.15 i686 Debian 5.0.4 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps imap ssl_cert_file: /etc/ssl/certs/smtpd.crt ssl_key_file: /etc/ssl/private/smtpd.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: postfix mail_privileged_group: mail mail_uid: vmail mail_gid: vmail mail_location: maildir:/srv/mail/vmail/%Ud/%Ln/Maildir mbox_write_locks: fcntl dotlock imap_client_workarounds: delay-newmail outlook-idle netscape-eoh lda: postmaster_address: postmaster(a)h-st.com auth_socket_path: /var/run/dovecot/auth-master log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver-info.log auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail Thanks -------- Romer Ventura

2 4

[Dovecot] clarifications on shared mailboxes
by Frank Bonnet 03 Oct '11

03 Oct '11

Hello I need some clarifications on shared mailboxes. Actually we use MBOX format with "real" unix users , but I've been asked to create some shared mailboxes for some users who need to have some for their working groups. What would be the best way to create those shared mailboxes ? Would it be possible to create some "shared space" on the server in maildir format to get advantage of the last seen flag ? If yes some config examples would be a great help. See attach the doveconf -n output ( certificates names have been obscured ;-) ) Thank you.

1 0

[Dovecot] 1.2.17 Program terminated with signal 11, Segmentation fault.
by Andrew Hearn 03 Oct '11

03 Oct '11

Hello, We've had seg faults a couple of times a day on our servers, we upgraded to 1.2.17 and still have them. running a coredump through dbg says: Reading symbols from /usr/local/libexec/dovecot/imap-login...done. [New Thread 27962] Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff083f4000 Core was generated by `imap-login -D'. Program terminated with signal 11, Segmentation fault. #0 0x000000000041388b in io_file_unlink (_io=<value optimized out>, closed=true) at ioloop.c:70 70 if (io->next != NULL) dovecot -n is at http://pastebin.ca/SQjrseJD (pass timo) Linux 2.6.18-274.3.1.el5 #1 SMP Tue Sep 6 20:13:52 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux We use NFS for mail store, and ramdisk for dovecot indexes. We do run the mail_log plugin. Let me know if you need any more info though. -- Andrew Hearn. AAISP Technical Support Team Leader Tel: 03333 400999

1 0

[Dovecot] problem with getting outlook to work with IMAP server
by Daminto Lie 03 Oct '11

03 Oct '11

Hi, I am having difficulty in getting the outlook 2010 to connect to my server running on Ubuntu Server 10.04. I can login to Squirrelmail webmail, and am able to send & receive emails through squirrelmail with no problem whatsoever. However, this morning, I was trying to add a new account for the same user on Outlook 2010 and I got the following error from outlook as follows Send test e-mail message: Your outgoing (SMTP) e-mail server has reported an internal error. The server responded: 554 5.7.7 No Spoofing Allowed. I then, went to check /var/log/mail.log and I found the following Oct 3 12:19:27 mymailServer dovecot: auth(default): ldap(sbernett,50.4.39.163): pass search: base=ou=accounts,dc=example,dc=com scope=subtree filter=(&(objectClass=posixAccount)(uid=sbernett)) fields=uid,userPassword,homeDirectory,uidNumber,gidNumber Oct 3 12:19:27 mymailServer dovecot: auth(default): ldap(sbernett,50.4.39.163): result: uid(user)=sbernett uidNumber(userdb_uid)=106 gidNumber(userdb_gid)=106 userPassword(password)={CRYPT}xGHI86Ktls homeDirectory(userdb_home)=/home/vmail/sbernett Oct 3 12:19:27 mymailServer dovecot: auth(default): client out: OK#0111#011user=sbernett Oct 3 12:19:27 mymailServer dovecot: auth(default): master in: REQUEST#0114#0112686#0111 Oct 3 12:19:27 mymailServer dovecot: auth(default): passwd(sbernett,50.4.39.163): lookup Oct 3 12:19:27 mymailServer dovecot: auth(default): passwd(sbernett,50.4.39.163): unknown user Oct 3 12:19:27 mymailServer dovecot: auth(default): master out: USER#0114#011sbernett#011uid=106#011gid=106#011home=/home/vmail/sbernett Oct 3 12:19:27 mymailServer dovecot: imap-login: Login: user=<sbernett>, method=PLAIN, rip=50.4.39.163, lip=50.4.39.164 Oct 3 12:19:27 mymailServer dovecot: IMAP(sbernett): Disconnected in IDLE bytes=9/292 Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: warning: No server certs available. TLS won't be enabled Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: connect from localhost[127.0.0.1] Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: 182292400AE: client=localhost[127.0.0.1] Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: lost connection after DATA (0 bytes) from localhost[127.0.0.1] Oct 3 12:19:27 mymailServer postfix/smtpd[2766]: disconnect from localhost[127.0.0.1] Next, I tried to see if there are any the difference in the mail.log when logging into the squirrelmail (which is working for me) Oct 3 12:31:32 mymailServer dovecot: auth(default): ldap(sbernett,127.0.0.1): pass search: base=ou=accounts,dc=example,dc=com scope=subtree filter=(&(objectClass=posixAccount)(uid=sbernett)) fields=uid,userPassword,homeDirectory,uidNumber,gidNumber Oct 3 12:31:32 mymailServer dovecot: auth(default): ldap(sbernett,127.0.0.1): result: uid(user)=sbernett uidNumber(userdb_uid)=106 gidNumber(userdb_gid)=106 userPassword(password)={CRYPT}xGHI86Ktls homeDirectory(userdb_home)=/home/vmail/sbernett Oct 3 12:31:32 mymailServer dovecot: auth(default): client out: OK#0111#011user=sbernett Oct 3 12:31:32 mymailServer dovecot: auth(default): master in: REQUEST#0114#0112485#0111 Oct 3 12:31:32 mymailServer dovecot: auth(default): passwd(sbernett,127.0.0.1): lookup Oct 3 12:31:32 mymailServer dovecot: auth(default): passwd(sbernett,127.0.0.1): unknown user Oct 3 12:31:32 mymailServer dovecot: auth(default): master out: USER#0114#011sbernett#011uid=1004#011gid=1004#011home=/home/vmail/sbernett Oct 3 12:31:32 mymailServer dovecot: imap-login: Login: user=<sbernett>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured The only thing I noticed different between the two is the IP addresses in rip and lip. Is there a way to tell the IMAP server to allow the remote IP addresses to connect. Here is my dovecot.conf # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-34-generic-pae i686 Ubuntu 10.04.3 LTS ext4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap listen: *:143 ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 106 last_valid_uid: 1000 mail_privileged_group: mail mail_location: maildir:/home/vmail/%u/Maildir mbox_write_locks: fcntl dotlock mail_plugins: quota imap_quota imap_client_workarounds: delay-newmail outlook-idle netscape-eoh lda: postmaster_address: postmaster(a)mailtest.dyndns-free.com mail_plugins: quota sendmail_path: /usr/lib/sendmail rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot-auth-master auth default: mechanisms: plain login username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: passwd userdb: driver: static args: uid=106 gid=106 home=/home/vmail/%u allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot-auth-master mode: 432 user: vmail group: vmail plugin: quota: maildir quota_rule: *:storage=3GB quota_rule2: Trash:storage=20%% quota_rule3: Spam:storage=10%% quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 Here is my postfix.cf myhostname = mymailserver mydomain = example.com mydestination = localhost.$mydomain,localhost,$mydomain,$myhostname local_recipient_maps = ldap:/etc/postfix/ldap-user-auth.cf virtual_transport = dovecot virtual_mailbox_domains = vexample.com virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual_mailboxes virtual_minimum_uid = 100 virtual_uid_maps = static:106 virtual_gid_maps = static:106 relayhost = mynetworks = 127.0.0.0/8, 192.168.1.0/24, 50.4.39.163, 50.4.39.164 mynetworks_style = subnet mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 mail_spool_directory = /var/spool/mail smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanomymous smtpd_tls_auth_only = yes smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,reject_sender_login_mismatch smtpd_sasl_local_domain = vexample.com dovecot_destination_recipient_limit = 1 Any help would be greatly appreciated. Thank you

1 0

Re: [Dovecot] FTS and compound searches
by Nikolai Schupbach 01 Oct '11

01 Oct '11

>> New subscriber here. I noticed that the FTS index is not used in compound searches. >> Is this expected? Tested in 2.0.0 and 2.0.8: > >Yep. It's been in TODO for a while. I know this thread is quite old, but we have the same issue with v2.0.14 and squat. Would this issue also affect the Solr FTS backend? Thanks, Nikolai.

2 1

Re: [Dovecot] Error message in log
by Joseph Tam 01 Oct '11

01 Oct '11

On Fri, 30 Sep 2011, Knute Johnson wrote: > I'm getting the following message in my log; > > dovecot: IMAP(knute): > fchown(/home/knute/mail/.imap/INBOX/dovecot.index.tmp, -1, 8(mail)) > failed: Operation not permitted (egid=1000(knute), group based on > /var/mail/knute): 4 Time(s) > > I got these once before on the /var/mail/user files and changed the > permissions to 600. /home/knute/mail/.imap/INBOX is 770 and the index > files are 600. Is this a problem with the directory privilege? Probably. This was discussed a few times before. Check the mailing list archives. Dovecot tries to retain the same file access for the indices as the mailbox/message file it indexes; if the permissions allow access to the group, but the owner is not part of that group, then the dovecot process (which sets UID to the owner) cannot recreate the same permissions, hence the error. Either change the group ownership of "/var/mail/knute", put user "knute" in group "mail", or chmod it to 0600. The last one is probably the best solution. And fix the problem that created these permissions in the first place. Check your other users (if you have any) for the same situation. Joseph Tam <jtam.home(a)gmail.com>

1 0